PUSH NOTIFICATION MIDDLEWARE

• US 20150026356A1
• Filed: 07/18/2013
• Published: 01/22/2015
• Est. Priority Date: 07/18/2013
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Kaplinger, Todd E., Rheinheimer, Michael R., White Eagle, Brian L.
• Granted Patent: US 9,699,625 B2
• Time in Patent Office: Days
• US Class Current: 709/230
• CPC Class Codes: H04L 12/1895 for short real-time information, e.g. alarms, notifications, alerts, updates
• CPC Class Codes: H04L 51/224 providing notification on incoming messages, e.g. pushed notifications of received messages
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 67/306 User profiles
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04L 69/08 Protocols for interworking; Protocol conversion
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements

Abstract

Embodiments relate to push notification middleware. A system includes a computer processor and a mobile platform server executable by the computer processor. The mobile platform server includes a notification service and a registry. The notification service is configured to receive a notification trigger including a payload to deliver to an endpoint and access the registry to determine a notification transport protocol associated with the endpoint. The notification service is further configured to select a channel plugin associated with the notification transport protocol to establish a notification channel with the endpoint and send the payload to the endpoint on the notification channel.

Claims

1. A system, comprising:

a computer processor; and

a mobile platform server executable by the computer processor, the mobile platform server comprising a notification service and a registry, the notification service configured to;

receive a notification trigger comprising a payload to deliver to an endpoint;

access the registry to determine a notification transport protocol associated with the endpoint;

select a channel plugin associated with the notification transport protocol to establish a notification channel with the endpoint; and

send the payload to the endpoint on the notification channel.

2. The system of claim 1, wherein the notification service further comprises a notification core configured to interface with a plurality of channel plugins associated a plurality of notification transport protocols.

3. The system of claim 1, wherein the notification trigger further comprises a tuple including a channel unique identifier, an application identifier, and a user identifier.

4. The system of claim 3, wherein the notification service is further configured to access the registry to determine a value for the channel unique identifier based on an omission of a specific value for the channel unique identifier in the notification trigger.

5. The system of claim 3, wherein the notification service is further configured to perform device registration by recording the channel unique identifier, the application identifier, and the user identifier in the registry based on a device registration request.

6. The system of claim 5, wherein the notification channel is established between the notification service and the endpoint through a gateway, and the device registration further comprises recording a device token for delivery through the gateway.

7. The system of claim 1, wherein the mobile platform server further comprises a publish/subscribe component, and the notification service further comprises a notification service application programming interface (API) accessible by both the publish/subscribe component and an application server external to the mobile platform server, the notification service API configured to receive the notification trigger.

8. The system of claim 7, wherein the publish/subscribe component further comprises publish/subscribe APIs accessible by the application server to publish to one or more topics and provide push notifications to a plurality of subscribed endpoints, and the publish/subscribe component is further configured to convert publish requests into notification triggers for each of the subscribed endpoints and send the notification triggers to the notification service API.

9. The system of claim 1, wherein the mobile platform server further comprises policies for push notification, and the notification service is configured to give preference to particular notification channels based on the policies.

10. The system of claim 1, wherein the notification service is further configured to generate and track statistics associated with push notification in a statistics data store.

11. A computer program product comprising a computer readable storage medium having program code embodied therewith, the program code executable by a processing device for:

receiving a notification trigger comprising a payload to deliver to an endpoint;

accessing a registry to determine a notification transport protocol associated with the endpoint;

selecting a channel plugin associated with the notification transport protocol to establish a notification channel with the endpoint; and

sending the payload to the endpoint on the notification channel.

12. The computer program product of claim 11, further comprising:

interfacing with a plurality of channel plugins associated a plurality of notification transport protocols from which the channel plugin is selected.

13. The computer program product of claim 11, wherein the notification trigger further comprises a tuple including a channel unique identifier, an application identifier, and a user identifier.

14. The computer program product of claim 13, further comprising:

accessing the registry to determine a value for the channel unique identifier based on an omission of a specific value for the channel unique identifier in the notification trigger.

15. The computer program product of claim 13, further comprising:

performing device registration by recording the channel unique identifier, the application identifier, and the user identifier in the registry based on a device registration request.

16. The computer program product of claim 15, wherein the notification channel is established between the notification service and the endpoint through a gateway, and the device registration further comprises recording a device token for delivery through the gateway.

17. The computer program product of claim 11, further comprising:

providing a notification service application programming interface (API) that is accessible by both a publish/subscribe component and an application server, the notification service API configured to receive the notification trigger.

18. The computer program product of claim 17, wherein the publish/subscribe component further comprises publish/subscribe APIs accessible by the application server to publish to one or more topics and provide push notifications to a plurality of subscribed endpoints, and the publish/subscribe component is further configured to convert publish requests into notification triggers for each of the subscribed endpoints and send the notification triggers to the notification service API.

19. The computer program product of claim 11, further comprising:

providing policies for push notification; and

giving preference to particular notification channels based on the policies.

20. The computer program product of claim 11, further comprising:

generating and tracking statistics associated with push notification.