The disclosed techniques enable selective forwarding and blocking of emails directed to an alias email address based on a whitelist, as well as text message alerts triggered by emails from unauthorized senders. More generally, the disclosed techniques enable an enterprise system to store contact emails for users (i.e., alias email addresses) while avoiding storing and managing personal email addresses for the user. For example, the enterprise system may forward personal email addresses to an aliasing server configured to generate alias email addresses based on the personal email addresses. The aliasing server may operate as a “middle man” that receives emails directed to the alias email addresses and that forwards the emails to the personal email addresses (when appropriate). The enterprise system may store and maintain the alias email addresses in lieu of the personal email addresses.

A system and method for creating custom domain name links is presented. A request is received by at least one server communicatively coupled to a network. The request is received from a user and is to create a custom domain name link to a third party service, the request identifying a custom domain name and the third party service. An entry is retrieved from a third party service link database for the third party service. The entry specifies how to create the custom domain name link for the third party service. The custom domain name link is created, by the at least one server, in accordance with the entry retrieved from the third party service link database.

The technology disclosed relates to resolution of conflicts between a requested internet service, requested by an internet service requesting server, and a package internet services. The method disclosed includes sending a conflict check result message to an internet service requesting server, indicating a presence of a conflict between a requested internet service requested by the requesting server and a package of internet services. The method includes receiving from the internet service requesting server a response including a selection from (i) an alternate internet service in the package of internet services to substitute for the requested internet service; (ii) a request to replace an existing connection with a service in the package of internet services with the requested internet service; and (iii) a request to initiate a custom resolution application. The method then responsively performs a respective conflict resolution step.

A network apparatus detects connection requests and extracts related data. The data is analyzed to determine whether the host is in an active state, whether the host matches a domain referrer and an amount of time from a last connection request. If it is detected that the host is not in an active state, the host is not matching the domain referrer and the amount of time from the last connection request exceeds a predetermined new session threshold, then a connection request is classified as a main request. If the amount of time from the last connection request is below a predetermined continuous session threshold, then any connection requests following the main request are classified as sub-requests. If the domain of host in the active state does not match current host for a sub-request, the sub-request is classified as a third-party request.

A system and method are provided for routing content requests. On a given server network, content requests comprising a character string may be routed up a hierarchical network topology until a linear chain, corresponding to the character string, is identified. Thus, the content request is forwarded up the hierarchy until an intersecting server network is reached. Then the content request is forwarded down the hierarchy until, along a published linear chain corresponding to the character string, until a content source is reached. Content is provided to the requestor along a reverse path of the content request.

A first terminal device may receive first address information which is a first IP address of the first communication device from the first communication device by using a communication network to which the first terminal device and a first communication device belong, and a first public key of the first communication device. The first terminal device may send a first authentication request in which the first public key is used to the first communication device with the first address information as a destination, and send first connection information to the first communication device with the first address information as a destination in a case where a first authentication response is received from the first communication device. The first connection information may be used by the first communication device to establish a first wireless connection between the first communication device and an external device.

A first terminal device may send address information which is an IP address of the first terminal device to the first communication device by using a communication network, and send a public key of the first terminal device to the first communication device by using the communication network. The first terminal device may receive a first authentication request in which the first public key is used from the first communication device by using the communication network. The first authentication request may be sent with the address information as a destination. The terminal device may send a first authentication response to the first communication device by using the communication network and send connection information to the first communication device by using the communication network. The connection information may be used by the first communication device to establish a first wireless connection between the first communication device and an external device.

A wireless device requests a network slice from a network by, first, identifying at least one network slice to be requested. Based on a mapping method that is specific to the wireless device, the wireless device forms a slice pseudonym for the or each network slice to be requested. The wireless device then transmits a request message to the network, wherein the request message comprises the or each slice pseudonym. The network node receives the request message sent by the wireless device, wherein the request message comprises at least one slice pseudonym. Based on a mapping method that is used by the wireless device and that is specific to the wireless device, the network node identifies at least one requested network slice from the or each received slice pseudonym. The network node then permits use of the requested network slice.

A wireless device requests a network slice from a network by, first, identifying at least one network slice to be requested. Based on a mapping method that is specific to the wireless device, the wireless device forms a slice pseudonym for the or each network slice to be requested. The wireless device then transmits a request message to the network, wherein the request message comprises the or each slice pseudonym. The network node receives the request message sent by the wireless device, wherein the request message comprises at least one slice pseudonym. Based on a mapping method that is used by the wireless device and that is specific to the wireless device, the network node identifies at least one requested network slice from the or each received slice pseudonym. The network node then permits use of the requested network slice.

Aspects relate to a physical cell identifier (PCI) change within a wireless network based on a primary synchronization signal (PSS) waveform. A scheduling entity, such as an integrated-access-backhaul (IAB) node within a radio access network (RAN), may communicate with a set of one or more scheduled entities, such as other IAB nodes and/or user equipment (UEs), utilizing a first PCI. The scheduling entity may then change from the first PCI to a second PCI, where the second PCI corresponds to a different PSS waveform than the first PCI. In some examples, the scheduling entity may change the PCI as a result of a PCI collision and/or PSS collision with a neighboring scheduling entity.