# US 2021/0344767 A1 · Push notifications for multiple user devices > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2021/0344767 A1 - Document ID: US20210344767A1 - Status: Published application - Kind: A1 - Application number: 17/305,719 - Filed: 2021-07-13 - Published: 2021-11-04 - Earliest claimed: 2016-11-03 - Assignees: Apple Inc. - Applicants: Apple Inc. - Inventors: Christopher M. BELL; Christoph PAASCH - Web page: https://patentgrep.com/patent/US20210344767A1 ## CPC - H04L 67/55: Push-based network services - H04L 12/1859: {adapted to provide push services, e.g. data channels} - H04L 12/1895: {for short real-time information, e.g. alarms, notifications, alerts, updates} - H04W 4/185: {by embedding added-value information into content, e.g. geo-tagging} - H04L 51/04: Real-time or near real-time messaging, e.g. instant messaging [IM] - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/306: User profiles - H04L 67/54: Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users - H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences - H04W 4/80: Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication - Y02D 30/70: in wireless communication networks - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) - Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE ## 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. ## Claims ### Claim 1 A method for delivering notifications to a delegating device by way of a delegate device, the method comprising, by the delegate device: providing, to a network server: information associated with a gateway proximate to the delegate device, and a user account identifier; receiving, from the gateway, a notification tap corresponding to a notification for the delegating device; and providing the notification tap to the delegating device, wherein the delegate device and the delegating device are both associated with the user account identifier. ### Claim 2 (depends on 1) The method of claim 1, further comprising: receiving, from the gateway, notification content associated with the notification for the delegating device; caching the notification content for subsequent delivery to the delegating device; and providing the notification content to the delegating device separately from the notification tap. ### Claim 3 (depends on 2) The method of claim 2, further comprising: receiving, from the delegating device, a request for the notification content associated with the notification after sending the notification tap to the delegating device, wherein the notification content is provided to the delegate device in response to receipt of the request for notification content. ### Claim 4 (depends on 1) The method of claim 1, further comprising: providing, to the network server, a globally unique identifier (GUID) for the delegate device. ### Claim 5 (depends on 4) The method of claim 4, further comprising: obtaining the GUID from the network server, wherein the GUID comprises a value leased by a wireless service provider from an original equipment manufacturer (OEM) of the delegate device. ### Claim 6 (depends on 1) The method of claim 1, wherein: the notification for the delegating device originates from an application server that stores a user account alias associated with the delegating device, and the user account alias is provided to the application server upon installation of an application on the delegating device. ### Claim 7 (depends on 1) The method of claim 1, wherein the information comprises a gateway address for the gateway. ### Claim 8 A non-transitory computer readable storage medium configured to store instructions that, when executed by a processor included in a delegate device, cause the delegate device to deliver notifications to a delegating device by way of the delegate device, by carrying out steps that include: providing, to a network server: information associated with a gateway proximate to the delegate device, and a user account identifier; receiving, from the gateway, a notification tap corresponding to a notification for the delegating device; and providing the notification tap to the delegating device, wherein the delegate device and the delegating device are both associated with the user account identifier. ### Claim 9 (depends on 8) The non-transitory computer readable storage medium of claim 8, wherein the steps further include: receiving, from the gateway, notification content associated with the notification for the delegating device; caching the notification content for subsequent delivery to the delegating device; and providing the notification content to the delegating device separately from the notification tap. ### Claim 10 (depends on 9) The non-transitory computer readable storage medium of claim 9, wherein the steps further include: receiving, from the delegating device, a request for the notification content associated with the notification after sending the notification tap to the delegating device, wherein the notification content is provided to the delegate device in response to receipt of the request for notification content. ### Claim 11 (depends on 8) The non-transitory computer readable storage medium of claim 8, wherein the steps further include: providing, to the network server, a globally unique identifier (GUID) for the delegate device. ### Claim 12 (depends on 11) The non-transitory computer readable storage medium of claim 11, wherein the steps further include: obtaining the GUID from the network server, wherein the GUID comprises a value leased by a wireless service provider from an original equipment manufacturer (OEM) of the delegate device. ### Claim 13 (depends on 8) The non-transitory computer readable storage medium of claim 8, wherein: the notification for the delegating device originates from an application server that stores a user account alias associated with the delegating device, and the user account alias is provided to the application server upon installation of an application on the delegating device. ### Claim 14 (depends on 8) The non-transitory computer readable storage medium of claim 8, wherein the information comprises a gateway address for the gateway. ### Claim 15 A delegate device configured to deliver notifications to a delegating device by way of the delegate device, the delegate device comprising a processor configured to cause the delegate device to carry out steps that include: providing, to a network server: information associated with a gateway proximate to the delegate device, and a user account identifier; receiving, from the gateway, a notification tap corresponding to a notification for the delegating device; and providing the notification tap to the delegating device, wherein the delegate device and the delegating device are both associated with the user account identifier. ### Claim 16 (depends on 15) The delegate device of claim 15, wherein the steps further include: receiving, from the gateway, notification content associated with the notification for the delegating device; caching the notification content for subsequent delivery to the delegating device; and providing the notification content to the delegating device separately from the notification tap. ### Claim 17 (depends on 16) The delegate device of claim 16, wherein the steps further include: receiving, from the delegating device, a request for the notification content associated with the notification after sending the notification tap to the delegating device, wherein the notification content is provided to the delegate device in response to receipt of the request for notification content. ### Claim 18 (depends on 15) The delegate device of claim 15, wherein the steps further include: providing, to the network server, a globally unique identifier (GUID) for the delegate device. ### Claim 19 (depends on 18) The delegate device of claim 18, wherein the steps further include: obtaining the GUID from the network server, wherein the GUID comprises a value leased by a wireless service provider from an original equipment manufacturer (OEM) of the delegate device. ### Claim 20 (depends on 15) The delegate device of claim 15, wherein: the notification for the delegating device originates from an application server that stores a user account alias associated with the delegating device, and the user account alias is provided to the application server upon installation of an application on the delegating device.