Abstract: A server network accepts asynchronous notification messages from multiple application servers and efficiently routes notification messages in the form of notification taps to a user device, which can operate in a low power mode. The user device may or may not be a cellular device. The server network maintains states for the user devices in terms of identifiers useful for routing. A network server proximate to the user device registers the identifiers useful for routing the notifications. When the server network receives a notification from a source application, the proximate network server determines a routing based on the registration and sends a notification tap to the user device. The user device can obtain notification content sourced by the source application. The user device can delegate the role of receiving notification taps to a delegate device, where the delegate device may have wall-power and/or a wired or wireless network connection.

Abstract: A server network accepts asynchronous notification messages from multiple application servers and efficiently routes notification messages in the form of notification taps to a user device, which can operate in a low power mode. The user device may or may not be a cellular device. The server network maintains states for the user devices in terms of identifiers useful for routing. A network server proximate to the user device registers the identifiers useful for routing the notifications. When the server network receives a notification from a source application, the proximate network server determines a routing based on the registration and sends a notification tap to the user device. The user device can obtain notification content sourced by the source application. The user device can delegate the role of receiving notification taps to a delegate device, where the delegate device may have wall-power and/or a wired or wireless network connection.

Abstract: A server network accepts asynchronous notification messages from multiple application servers and efficiently routes notification messages in the form of notification taps to a user device, which can operate in a low power mode. The user device may or may not be a cellular device. The server network maintains states for the user devices in terms of identifiers useful for routing. A network server proximate to the user device registers the identifiers useful for routing the notifications. When the server network receives a notification from a source application, the proximate network server determines a routing based on the registration and sends a notification tap to the user device. The user device can obtain notification content sourced by the source application. The user device can delegate the role of receiving notification taps to a delegate device, where the delegate device may have wall-power and/or a wired or wireless network connection.

Abstract: A server network accepts asynchronous notification messages from multiple application servers and efficiently routes notification messages in the form of notification taps to a user device, which can operate in a low power mode. The user device may or may not be a cellular device. The server network maintains states for the user devices in terms of identifiers useful for routing. A network server proximate to the user device registers the identifiers useful for routing the notifications. When the server network receives a notification from a source application, the proximate network server determines a routing based on the registration and sends a notification tap to the user device. The user device can obtain notification content sourced by the source application. The user device can delegate the role of receiving notification taps to a delegate device, where the delegate device may have wall-power and/or a wired or wireless network connection.

Abstract: A server network accepts asynchronous notification messages from multiple application servers and efficiently routes notification messages in the form of notification taps to a user device, which can operate in a low power mode. The user device may or may not be a cellular device. The server network maintains states for the user devices in terms of identifiers useful for routing. A network server proximate to the user device registers the identifiers useful for routing the notifications. When the server network receives a notification from a source application, the proximate network server determines a routing based on the registration and sends a notification tap to the user device. The user device can obtain notification content sourced by the source application. The user device can delegate the role of receiving notification taps to a delegate device, where the delegate device may have wall-power and/or a wired or wireless network connection.

Abstract: A communication device (UE) conducting wired and/or wireless communications may issue service requests using zero-round-trip-time (zero-RTT) connectivity. The UE may obtain, prior to initiating an application, an address corresponding to a service and a security credential for use in accessing the service. The UE may receive, after initiating the application, an instruction to issue a service request, and generate the service request that may include a service identifier corresponding to the service, the address corresponding to the service, and the security credential for use in accessing the service. The UE may then transmit the service request to an edge server associated with the service. The edge server may route the service according to the service identifier. Multiple data centers/servers may advertise their services to the edge server associated with the service, facilitating fast routing of the service request by the edge server associated with the service.

Abstract: A server network accepts asynchronous notification messages from multiple application servers and efficiently routes notification messages in the form of notification taps to a user device, which can operate in a low power mode. The user device may or may not be a cellular device. The server network maintains states for the user devices in terms of identifiers useful for routing. A network server proximate to the user device registers the identifiers useful for routing the notifications. When the server network receives a notification from a source application, the proximate network server determines a routing based on the registration and sends a notification tap to the user device. The user device can obtain notification content sourced by the source application. The user device can delegate the role of receiving notification taps to a delegate device, where the delegate device may have wall-power and/or a wired or wireless network connection.

Abstract: A server network accepts asynchronous notification messages from multiple application servers and efficiently routes notification messages in the form of notification taps to a user device, which can operate in a low power mode. The user device may or may not be a cellular device. The server network maintains states for the user devices in terms of identifiers useful for routing. A network server proximate to the user device registers the identifiers useful for routing the notifications. When the server network receives a notification from a source application, the proximate network server determines a routing based on the registration and sends a notification tap to the user device. The user device can obtain notification content sourced by the source application. The user device can delegate the role of receiving notification taps to a delegate device, where the delegate device may have wall-power and/or a wired or wireless network connection.

Abstract: A server network accepts asynchronous notification messages from multiple application servers and efficiently routes notification messages in the form of notification taps to a user device, which can operate in a low power mode. The user device may or may not be a cellular device. The server network maintains states for the user devices in terms of identifiers useful for routing. A network server proximate to the user device registers the identifiers useful for routing the notifications. When the server network receives a notification from a source application, the proximate network server determines a routing based on the registration and sends a notification tap to the user device. The user device can obtain notification content sourced by the source application. The user device can delegate the role of receiving notification taps to a delegate device, where the delegate device may have wall-power and/or a wired or wireless network connection.

Abstract: A communication device (UE) conducting wired and/or wireless communications may issue service requests using zero-round-trip-time (zero-RTT) connectivity. The UE may obtain, prior to initiating an application, an address corresponding to a service and a security credential for use in accessing the service. The UE may receive, after initiating the application, an instruction to issue a service request, and generate the service request that may include a service identifier corresponding to the service, the address corresponding to the service, and the security credential for use in accessing the service. The UE may then transmit the service request to an edge server associated with the service. The edge server may route the service according to the service identifier. Multiple data centers/servers may advertise their services to the edge server associated with the service, facilitating fast routing of the service request by the edge server associated with the service.