Managing notification messages

• US 9,985,917 B2
• Filed: 10/18/2016
• Issued: 05/29/2018
• Est. Priority Date: 02/25/2009
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Apple Inc.
• Inventors: Marcellino, Christopher
• Primary Examiner(s): Nealon, William
• Application Number:
  US15/296,553
• Publication Number:
  US 20170041273A1
• Time in Patent Office: 588 Days
• Field of Search: 4554121
• CPC Class Codes: H04L 51/214 using selective forwarding
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 67/141 Setup of application sessions admission control or resource allocation in data switching networks H04L47/70
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04W 36/385 of the core network
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/20 Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
• CPC Class Codes: H04W 4/21 for social networking applications
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

Methods and apparatuses that generate a subtopic identifier identifying a client application within a client device are described. The client application may be associated with a server application hosted in one or more application servers. Notification services may be registered with the application servers from the client application to forward identifiers associated with the client application to the server application to enable the server application to push notification messages to the client device selectively for the client application. When receiving a notification message from the application server, the notification message may be examined to forward the notification message directly to the client application without invoking other applications in the client device if the notification message carries a subtopic identifier of the client application.

Claims

1. A mobile device comprising:

a network interface; and

one or more processors communicatively coupled to the network interface and configured to;

generate a subtopic identifier that identifies an application configured to operate on the mobile device;

transmit, via the network interface, the subtopic identifier to an application server;

receive, via the network interface, a notification message comprising an embedded subtopic identifier that corresponds to the generated subtopic identifier; and

deliver the notification message to the application based at least in part on the embedded subtopic identifier and without invoking an other application operating on the mobile device.

2. The mobile device of claim 1, where the one or more processors are further configured to transmit a device token to the application server with the subtopic identifier.

3. The mobile device of claim 1, wherein the one or more processors are further configured to receive the notification message from a notification server that is separate from the application server.

4. The mobile device of claim 1, wherein the one or more processors are further configured to extract the embedded subtopic identifier from the notification message.

5. The mobile device of claim 1, wherein the embedded subtopic identifier identifies the application.

6. The mobile device of claim 1, wherein the one or more processors are further configured to:

receive an other notification message from the network interface;

determine that the other notification comprises no embedded subtopic identifier; and

forward the other notification message to each of a plurality of applications that subscribe to a topic associated with the other notification message.

7. The mobile device of claim 1, wherein the one or more processors are further configured to transmit, via the network interface, a request to register the application to the application server.

8. The mobile device of claim 1, wherein the one or more processors are further configured to receive, via the network interface, a topic identifier associated with the application server.

20. The mobile device of claim 1, wherein the one or more processors are configured to directly deliver the notification message to the application without invoking the other application.

9. A method of communicating using a mobile device via a network, the method comprising:

transmitting a request to an application server to register an application operating on the mobile device;

receiving a response from the application server comprising a string configured to be used to identify one or more messages pushed from the application server;

receiving a notification message from the application server;

determining that the notification message comprises the string; and

delivering the notification message to the application based at least in part on determining that the string is in the notification message and without invoking an other application operating on the mobile device.

10. The method of claim 9, wherein the notification message is delivered to an additional application based at least in part on determining that the string is in the received notification message.

11. The method of claim 9, further comprising:

transmitting an application identifier associated with the application to the application server;

receiving an other notification message comprising the application identifier; and

delivering the other notification message to the application based at least in part on determining that the application identifier in the other notification message.

12. The method of claim 11, wherein the other notification message is directly delivered to the application without invoking the other application.

19. The method of claim 9, further comprising:

receiving a topic identifier associated with the application server.

13. A method of communicating with a mobile device via a network, comprising:

receiving a request to register an application operating on the mobile device, wherein the request comprises an application identifier configured to identify the application;

transmitting a response to the request, wherein the response comprises a string configured to be used to identify messages pushed from the application server; and

transmitting a notification message to the mobile device, wherein the notification message comprises the string and the application identifier does not invoke an other application operating on the mobile device.

14. The method of claim 13, wherein transmitting the notification message comprises transmitting the notification message to a notification server for forwarding to the mobile device.

15. The method of claim 13, wherein the request to register the application comprises a device identifier.

16. The method of claim 13, further comprising:

establishing a network session with the mobile device in response to the notification message; and

performing one or more transactions over the network session.

17. The method of claim 13, further comprising:

transmitting an other notification message to the mobile device comprising the string but not the application identifier.

18. The method of claim 17, wherein the other notification message is intended for a plurality of applications operating on the mobile device.