IP Library Granted Patent US 10,779,156
Granted Patent B2
US 10,779,156 · App. 16/192,367 · Granted Sep 15, 2020

System and methods for data communications in a wireless communication system

Inventors: David Clark (Kitchener, CA); Allan David Lewis (New Dundee, CA); Barry Gilhuly (Waterloo, CA); David Bajar (Kitchener, CA); Nataliya Martsyna (Waterloo, CA); Robbie John Maurice (Waterloo, CA)
Assignee: BlackBerry Limited
H04W8/06H04L51/18H04L67/04H04L67/14H04L67/142H04L67/18H04L67/303H04W4/12H04L51/38H04W88/02
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,779,156
App. No.
16/192,367
Granted
Sep 15, 2020
Kind
B2
Abstract

Techniques for use by a mobile device configured to operate in a wireless network for the communication of data messages with a server are described. When the mobile device does not have an open session with the server, the mobile device receives from a service node via the wireless network a message which informs the mobile device that a data message has arrived at the server and needs to be retrieved. The message includes an identifier which identifies the data message at the server. In response to opening an application at the mobile device, the mobile device communicates directly with the server via the wireless network for retrieving the data message. This involves commencing an open session with the server, sending to the server a command for retrieving the data message, and receiving from the server the data message in response to sending the command. The mobile device may use the identifier for retrieving the data message from the server.

Claims (34)

1. A method of operating a mobile device comprising:

receiving an enable message indicating that a pending data message is available for retrieval from a host service; and

communicating directly with the host service to retrieve the pending data message from the host service after receiving the enable message and opening an application at the mobile device.

2. The method of claim 1 , wherein communicating directly with the host service comprises:

sending a fetch message directly to the host service to retrieve the pending data message from the host service; and

receiving the pending data message directly from the host service after sending the fetch message to the host service.

3. The method of claim 1 , wherein the application comprises an electronic mail application, wherein the method further comprises opening the electronic mail application at the mobile device subsequent to receiving the enable message.

4. The method of claim 1 , wherein the pending data message is an electronic mail message comprising a body of text.

5. The method of claim 1 , wherein the enable message is received from a relay services node.

6. The method of claim 1 , wherein the enable message comprises an identifier that identifies the pending data message.

7. The method of claim 1 , wherein communicating directly with the host service comprises retrieving a plurality of pending data messages from the host service after receiving the enable message.

8. A mobile device comprising:

a transceiver configured to receive an enable message indicating that a pending data message is available for retrieval from a host service; and

a processor coupled to the receiver and configured to communicate directly with the host service to retrieve the pending data message from the host service after opening an application at the mobile device.

9. The mobile device of claim 8 , wherein the application comprises a messaging application, and wherein the processor is further configured to open the messaging application subsequent to receiving the enable message and prior to communicating directly with the host service.

10. The mobile device of claim 8 , wherein the transceiver is further configured to receive the pending data message after the enable message is received.

11. The mobile device of claim 8 , wherein the transceiver is further configured to:

send a fetch message to the host service to retrieve the pending data message from the host service; and

receive the pending data message from the host service after sending the fetch message to the host service.

12. The mobile device of claim 8 , wherein the transceiver is further configured to send a data message after receiving the pending data message.

13. The mobile device of claim 8 , wherein the enable message comprises an identifier that identifies the pending data message.

14. A non-transitory computer readable medium storing instructions that enable communication with a mobile device via a wireless network, wherein the instructions that enable communication with the mobile device via the wireless network comprise:

sending an enable message to the mobile device, wherein the enable message identifies a pending data message at a host service; and

communicating directly with the mobile device to retrieve the pending data message from the host service after sending the enable message and opening an application at the mobile device.

15. The non-transitory computer readable medium of claim 14 , wherein the instructions that enable communication with the mobile device via the wireless network further comprise:

retrieving the pending data message subsequent to sending the enable message to the mobile device; and

transmitting the pending data message to the mobile device.

16. The non-transitory computer readable medium of claim 14 , wherein the instructions that enable communication with the mobile device via the wireless network further comprise:

receiving the pending data message before sending the enable message; and

storing the pending data message before sending the enable message.

17. The non-transitory computer readable medium of claim 14 , wherein the instructions that enable communication with the mobile device via the wireless network further comprise opening a data session with the mobile device after sending the enable message.

18. The non-transitory computer readable medium of claim 17 , wherein the instructions that enable communication with the mobile device via the wireless network further comprise using the data session to transmit the pending data message to the mobile device.

19. The non-transitory computer readable medium of claim 14 , wherein the enable message comprises an identifier that identifies the pending data message.

20. The non-transitory computer readable medium of claim 14 , wherein the instructions that enable communication with the mobile device via the wireless network further comprise receiving a fetch message from the mobile device for the pending data message, and wherein the pending data message is retrieved after receiving the fetch message.

Assignments (8)
CORRECTIVE ASSIGNMENT TO CORRECT THE ADDED PATENT NUMBER TO REMOVE PATENT NO. 8,873,407 AT PREVIOUSLY RECORDED ON REEL 64066 FRAME 1. ASSIGNOR(S) HEREBY CONFIRMS THE NUNC PRO TUNC ASSIGNMENT EFFECTIVE DATE MARCH 20, 2023. Recorded Feb 2, 2026
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 074921/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE COVER SHEET AT PAGE 50 TO REMOVE 12817157 PREVIOUSLY RECORDED ON REEL 063471 FRAME 0474. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 064806/0669 →
CORRECTIVE ASSIGNMENT TO CORRECT 12817157 APPLICATION NUMBER PREVIOUSLY RECORDED AT REEL: 064015 FRAME: 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064807/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064066/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 16, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064015/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 063471/0474 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 11, 2019
From: CLARK, DAVID; LEWIS, ALLAN DAVID; GILHULY, BARRY; BAJAR, DAVID; MARTSYNA, NATALIYA; MAURICE, ROB
To: RESEARCH IN MOTION LIMITED
Reel/Frame 047975/0490 →
CHANGE OF NAME Recorded Jan 11, 2019
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 048066/0995 →
Continuity (10)
Continuation 15716011 · Sep 26, 2017
Continuation 15333839 · Oct 25, 2016
Continuation 14213025 · Mar 14, 2014
Continuation 13673191 · Nov 9, 2012
Continuation 13302224 · Nov 22, 2011
Continuation 12957977 · Dec 1, 2010
Continuation 12622849 · Nov 20, 2009
Continuation 11303428 · Dec 16, 2005
Provisional Application 60734448 · Nov 8, 2005
Related Publication 20190104400A1 · Apr 4, 2019