IP Library Granted Patent US 10,038,755
Granted Patent B2
US 10,038,755 · App. 14/973,290 · Granted Jul 31, 2018

Method, apparatus and system for provisioning a push notification session

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,038,755
App. No.
14/973,290
Granted
Jul 31, 2018
Kind
B2
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 (42)

1. A method of controlling a push notification session, comprising:

provisioning, by a first server, a push notification session between an application on a mobile device and a second server, the second server providing a service to the application;

monitoring, by the first server, an operational status of the second server;

determining, by the first server, that the second server is inoperable; and

terminating, by the first server, the push notification session based on the determination that the second server is inoperable, wherein terminating the push notification session further comprises:

invalidating, by the first server, a token related to the push notification session; and

sending, from the first server to the application on the mobile device, a session teardown message.

2. The method of claim 1 , wherein monitoring the operational status of the second server further comprises:

enabling, by the first server, a monitoring interval; and

sending, from the first server to the second server, a status enquiry message within the monitoring interval, the status enquiry message relating to the second server.

3. The method of claim 2 , wherein determining that the second server is inoperable is based on not receiving a status update message from the second server in response to the status enquiry message sent to the second server.

4. The method of claim 1 , wherein determining that the second server is inoperable is based on a predetermined inactivity period associated with the second server.

5. The method of claim 1 , wherein determining that the second server is inoperable is based on the first server not being able to communicate with the second server.

6. The method of claim 1 , wherein determining that the second server is inoperable is based on receiving a status update message from the second server indicating that the second server is inoperable.

7. The method of claim 1 , wherein monitoring the operational status of the second server further comprises:

sending, from the first server to a proxy server, a status enquiry message, the status enquiry message intended for the second server, the proxy server being configured to establish the operational status of the second server on behalf of the first server; and

receiving, at the first server from the proxy server, a status update message regarding the second server.

8. The method of claim 1 , wherein terminating the push notification session further comprises: invalidating, by the first server, a token related to the push notification session.

9. The method of claim 1 , wherein terminating the push notification session further comprises: sending, from the first server to the application on the mobile device, a session teardown message.

10. A method of controlling a push notification session, comprising:

provisioning, by a first server, a push notification session between a second server and an application on a mobile device, the second server providing a service to the application;

monitoring, by the first server, an operational status of an application on the mobile device;

determining, by the first server, that the application on the mobile device is inoperable; and

terminating, by the first server, the push notification session based on the determination that the application on the mobile device is inoperable, wherein terminating the push notification session further comprises:

invalidating, by the first server, a token related to the push notification session; and

sending, from the first server to the application on the mobile device, a session teardown message.

11. The method of claim 10 , wherein monitoring the operational status of the application on the mobile device further comprises:

enabling, by the first server, a monitoring interval; and

sending, from the first server to the application on the mobile device, a status enquiry message within the monitoring interval, the status enquiry message relating to the application on the mobile device.

12. The method of claim 11 , wherein determining that the application on the mobile device is inoperable is based on not receiving, at the first server, a status update message from the application on the mobile device in response to the status enquiry message sent to the application on the mobile device within a predetermined period of time.

13. The method of claim 10 , wherein determining that the application on the mobile device is inoperable is based on a predetermined inactivity period associated with the application on the mobile device.

14. The method of claim 13 , wherein determining that the application on the mobile device is inoperable is based on receiving, at the first server, a status update message from the mobile device indicating that the application on the mobile device is inoperable.

15. The method of claim 13 , wherein terminating the push notification session further comprises: invalidating, by the first server, a token related to the push notification session.

16. The method of claim 13 , wherein terminating the push notification session further comprises: sending, from the first server to the application on the mobile device, a session teardown message.

17. The method of claim 10 , wherein determining that the application on the mobile device is inoperable is based on the first server not being able to communicate with the application on the mobile device.

18. A non-transitory computer-readable storage medium comprising computer-executable instructions which, when executed by a processor, cause a computing device to perform a method of controlling a push notification session, the method comprising:

provisioning, by a first server, a push notification session between an application on a mobile device and a second server, the second server providing a service to the application;

monitoring, by the first server, an operational status of the second server;

determining, by the first server, that the second server is inoperable; and

terminating, by the first server, the push notification session based on the determination that the second server is inoperable, wherein terminating the push notification session further comprises:

invalidating, by the first server, a token related to the push notification session; and

sending, from the first server to the application on the mobile device, a session teardown message.

Assignments (6)
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064271/0199 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064104/0103 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2018
From: GOOD TECHNOLOGY HOLDINGS LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 045196/0255 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2017
From: GOOD TECHNOLOGY CORPORATION
To: GOOD TECHNOLOGY HOLDINGS LIMITED
Reel/Frame 044832/0094 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2016
From: SOMANI, HANIFF; QUINLAN, SEAN MICHAEL
To: VISTO CORPORATION
Reel/Frame 037669/0151 →
CHANGE OF NAME Recorded Feb 4, 2016
From: VISTO CORPORATION
To: GOOD TECHNOLOGY CORPORATION
Reel/Frame 037703/0558 →
Cited By (1)
US 12,712,949