Method, apparatus and system for provisioning a push notification session

• US 8,407,776 B2
• Filed: 02/11/2011
• Issued: 03/26/2013
• Est. Priority Date: 02/11/2011
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Good Technology Corporation (Blackberry Limited)
• Inventors: Somani, Haniff, Quinlan, Sean Michael
• Primary Examiner(s): SIMITOSKI, MICHAEL J
• Application Number:
  US13/025,984
• Publication Number:
  US 20120210415A1
• Time in Patent Office: 774 Days
• Field of Search: 726/9, 709/226
• US Class Current: 726/9
• CPC Class Codes: H04L 63/0884 by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04L 65/1083 In-session procedures
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/1008 based on parameters of servers, e.g. available memory or workload monitoring of computer activity G06F11/30
• CPC Class Codes: H04L 67/1034 Reaction to server failures by a load balancer
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/145 avoiding end of session, e.g. keep-alive, heartbeats, resumption message or wake-up for inactive or interrupted session
• CPC Class Codes: H04L 67/55 Push-based network services
• CPC Class Codes: H04W 76/25 Maintenance of established connections

Abstract

A system and method for provisioning a push notification session via a communications network between an application on a client terminal and a server corresponding to the application. In one aspect, a push provisioning entity transmits a message to the client terminal, whereby to configure the client terminal into a state in which it is able to request a push notification session with the server. An application on the client terminal can then request establishment of a push notification session by transmitting a push notification session request message to the push provisioning entity. The push provisioning entity generates a token for use in validating the push notification session, associates the generated token with the application and transmits the token to the application, which uses it to establish the push notification session.

Claims

1. A method for provisioning a push notification session via a communications network between an application on a client terminal and a server corresponding to the application, the client terminal having a first operative state wherein said client terminal is enabled to request the push notification session with the server, and a second operative state, different to said first operative state, the method comprising:

responsive to receiving a push notification provisioning request message from the client terminal, transmitting a message to the client terminal, whereby to configure the client terminal into the first operative state;

thereafter

responsive to receiving a push notification session request message from said application, performing the steps of;

generating a first token for use in validating said push notification session,

associating the first token with the application, and

transmitting said first token to said application for use in establishing said push notification session;

thereafter

responsive to receiving a token validation request comprising a second token from the server, determining whether the second token corresponds to the first token;

selectively transmitting an authorisation message to the server in dependence on said determination, whereby to enable said push notification session between the server and the application;

thereafter

responsive to receiving a notification message comprising a third token from said server for delivery to said application, evaluating whether the third token corresponds to the first token; and

selectively transmitting said notification message to the client terminal for delivery to said application in dependence on said evaluation.

2. A method according to claim 1, in which the client terminal comprises a plurality of applications, each application being configured to request a push notification session, and the method comprises generating a different first token for each respective application in response to receipt of a push notification session request message originating therefrom.

3. A method according to claim 1, in which, responsive to receiving said push notification session request message, the method further comprises updating a record corresponding to the terminal, said record being maintained at a device remote from said client terminal and accessed prior to generating the first token.

4. A method according to claim 1, wherein the method comprises selectively generating said first token on the basis of a predetermined criterion.

5. A method according to claim 4, wherein said predetermined criterion comprises validation of a record corresponding to the server, said record being maintained at a device remote from said server and comprising data indicative of whether the server is authorised to conduct a said push notification session.

6. A method according to claim 4, wherein said predetermined criterion comprises verification of an authentication credential associated with said application.

7. A method according to claim 4, wherein said predetermined criterion comprises verification of an authentication credential associated with said server.

8. A method according to claim 1, comprising providing said first token from the application directly to the server, whereby to establish said push notification session.

9. A method according to claim 1, wherein, responsive to a server access request from said application, the method comprises identifying a network node to transmit the received server access request, and transmitting the server access request thereto.

10. A method according to claim 9, wherein said network node is the server.

11. A method according to claim 9, wherein said network node is a secure access provisioning entity associated with the server.

12. A method according to claim 11, wherein the method further comprises selectively provisioning said push notification session in dependence on an authorisation state associated therewith, said authorisation state being indicative of whether said application is authorised by said secure access provisioning entity to conduct said push notification session.

13. A method according to claim 12, wherein the method comprises selectively monitoring said authorisation state in dependence on a session state of said push notification session, whereby to control said push notification session.

14. A method according to claim 1, wherein the method comprises selectively updating a session state of the push notification session in dependence on said evaluation.

15. A method according to claim 1, further comprising determining an operational state of said server on the basis of a predetermined inactivity period associated therewith and/or data indicative of said operational state received from the server.

16. A method according to claim 1, further comprising determining a session state associated with said push notification session on the basis of a predetermined inactivity period associated therewith and/or a session status response message received from said server.

17. A method according to claim 16, wherein said session status response message is generated in response to transmission of a session status request message to the server.

18. A method according to claim 16, comprising deriving, from said session status response message, a state of the push notification session at the server and maintaining a validity of the first token in dependence on said derived state.

19. A method according to claim 16, comprising deriving, from said session status response message, a state corresponding to a plurality of push notification sessions, each said push notification session corresponding to a different application residing on a different client terminal and having a different first token associated therewith, and maintaining a validity of each of said different first tokens in dependence on said derived state.

20. A method according to claim 16, wherein, in the event that said session state is determined to be inoperable, the method comprises terminating said push notification session by marking a validity of said first token as invalid.

21. A method according to claim 16, comprising selectively transmitting a status notification message to said application in dependence on said derived session state, whereby to control said push notification session.

22. A method according to claim 1, the method further comprising scanning said notification message, whereby to detect a malicious notification message, and selectively transmitting said notification message to the client terminal in dependence on said scanning.

23. A method according to claim 1, wherein, on the basis of said notification message, the method further comprises generating an instruction associated with said push notification session, said instruction defining steps to be executed by said application on the client terminal, and transmitting said instruction to the client terminal for delivery to said application.

25. A non-transitory computer medium that stores executable program instructions that direct an apparatus to perform the method of claim 1.

24. A device comprising a processor and memory, further comprising a push provisioning entity for provisioning a push notification session via a communications network between an application on a client terminal and a server corresponding to the application, the client terminal having a first operative state wherein said client terminal is enabled to request the push notification session with the server, and a second operative state, different to said first operative state, the push provisioning entity comprising:

a provisioning module for receiving a push notification provisioning request message from the client terminal, and transmitting a message to the client terminal, whereby to configure the client terminal into the first operative state; and

a session provisioning module for performing a push provisioning process, said session provisioning module being responsive to receiving a push notification session request message from said application whereby to perform said push provisioning process in respect of the received push notification session request message, the push provisioning process comprising;

generating a first token for use in validating said push notification session;

associating the first token with the application;

transmitting said first token to said application for use in establishing said push notification session;

thereafter

responsive to receiving a token validation request comprising a second token from the server, determining whether the second token corresponds to the first token;

selectively transmitting an authorisation message to the server in dependence on said determination, whereby to enable said push notification session between the server and the application;

thereafter

responsive to receiving a notification message comprising a third token from said server for delivery to said application, evaluating whether the third token corresponds to the first token; and

selectively transmitting said notification message to the client terminal for delivery to said application in dependence on said evaluation.

26. A method for enabling a push notification session between an application on a client terminal and a server corresponding to the application via a communications network, the method comprising:

responsive to receiving a push notification session request message from the application, generating a first token associated with said push notification session for use in validating said push notification session;

transmitting said first token to the application;

responsive to receiving a token validation request comprising a second token from the server, determining whether the second token corresponds to the first token;

selectively transmitting an authorisation message to the server in dependence on said determination, whereby to enable said push notification session between the server and the application;

thereafter

responsive to receiving a notification message comprising a third token from said server for delivery to said application, evaluating whether the third token corresponds to the first token; and

selectively transmitting said notification message to the client terminal for delivery to said application in dependence on said evaluation.

27. A method according to claim 26, in which, responsive to said determination, the method further comprises updating a record corresponding to said push notification session, said record being maintained at a device remote from said server and accessed prior to transmission of a notification message associated with said push notification session to said application.

28. A method according to claim 27, wherein said record comprising data indicative of a session state of said push notification session.

29. A method according to claim 26, wherein the method further comprises selectively reserving communication network resources in dependence on said determination.

30. A method according to claim 26, wherein the method comprises selectively transmitting said authorisation message on the basis of a predetermined criterion.

31. A method according to claim 30, wherein said predetermined criterion comprises verification of an authentication credential associated with said server.

32. A method according to claim 30, wherein said predetermined criterion comprises validation of a record corresponding to the server, said record being maintained at a device remote from said server and comprising data indicative of whether the server is authorised to conduct a said push notification session.

33. A method according to claim 32, wherein, in the event of absence of said record, selectively transmitting a conditional authorisation message to said server, said conditional authorisation message instructing the server to perform a registration process so as to establish said push notification session, said registration process causing said record to be created at said device.

34. A method according to claim 30, wherein said predetermined criterion comprises verifying whether the server has been scanned for the presence of malicious software, the predetermined criterion being satisfied in the event that the scanning has occurred on the server.

35. A method according to claim 26, wherein in the event that said second token is determined to be conflicting with said first token, the method further comprising terminating the establishment of said push notification session by marking a validity of said first token as invalid.

36. A method according to claim 35, wherein the method further comprises transmitting a tear down message to said application, thereby terminating establishment of said push notification session.

38. A non-transitory computer medium that stores executable program instructions that direct an apparatus to perform the method of claim 26.

37. A device comprising a processor and memory, further comprising a push provisioning entity for enabling a push notification session between an application on a client terminal and a server corresponding to the application via a communications network, the push provisioning entity comprising:

a push provisioning module responsive to reception of a push notification session request message from the application, being arranged to generate a first token associated with said push notification session for use in validating said push notification session, and to transmit said first token to said application;

a token validation module responsive to reception of a token validation request comprising a second token from the server, being arranged to determine whether the second token corresponds to the first token, and to transmit an authorisation message to the server in dependence on said determination, whereby to enable said push notification session between the server and the application; and

a session provisioning module, responsive to a notification message comprising a third token from said server for delivery to said application to evaluate whether the third token corresponds to the first token, and to selectively transmit said notification message to the client terminal for delivery to said application in dependence on said evaluation.