IP Library Granted Patent US 10,548,180
Granted Patent B2
US 10,548,180 · App. 16/245,625 · Granted Jan 28, 2020

Dynamic adjustment of keep-alive messages for efficient battery usage in a mobile network

Inventors: Ari Backholm (Los Altos, CA); Mikko Tervahauta (San Francisco, CA); Seppo Salorinne (Helsinski, FI); Jukka Ahonen (Lahti, FI); Mikko Daavittila (Espoo, FI); Andrew Everitt (Cambridge, GB); Lauri Vuornos (Helsinki, FI)
Assignee: Seven Networks, LLC
H04W76/25H04L43/0811H04L43/103H04L67/14H04L67/145H04W24/08H04W52/0212H04W52/0229H04W52/44H04W76/11H04W24/00H04W48/08H04W72/12H04W80/04Y02B70/30Y02D70/00Y02D70/124Y02D70/1224Y02D70/1262Y02D70/146
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,548,180
App. No.
16/245,625
Granted
Jan 28, 2020
Kind
B2
Abstract

A method for IP [=Internet Protocol] communication between a mobile terminal and its correspondent node in a mobile radio network. The method comprises establishing an IP connection between the mobile terminal and its correspondent node. After detecting a period of inactivity in the IP connection, keep-alive messages are sent via the IP connection at predetermined intervals, which are varied. The method comprises monitoring the lengths of several periods of inactivity at which the mobile radio network disconnects the IP connection.

Claims (81)

1. A method for network communication between a mobile terminal and a remote entity in a communications network, the method comprising:

establishing a first connection over a network between a mobile terminal and a remote entity;

exchanging keep-alive messages at varying intervals over the first connection based on periods of inactivity of the first connection;

wherein the first connection is disconnected after a first period of inactivity;

establishing a second connection over the network between the mobile terminal and the remote entity;

exchanging keep-alive messages at varying intervals over the second connection based on periods of inactivity of the second connection;

wherein the second connection is disconnected after a second period of inactivity; and

sending, from the mobile terminal, keep-alive messages at a safe interval via a subsequent connection over the network based on inactivity in the subsequent connection, wherein the safe interval is based on the first disconnection and the second disconnection.

2. The method of claim 1 , wherein at least one of the first and second connections is a TCP/IP connection.

3. The method of claim 1 , further comprising associating a network-specific safe interval with the network.

4. The method of claim 3 , wherein the network-specific safe interval is used for sending keep-alive messages when re-entering the network.

5. The method of claim 1 , wherein the safe interval is less than the first period of inactivity and the second period of inactivity by at least a safety margin.

6. The method of claim 1 , wherein the safe interval is based on the first period of inactivity and the second period of inactivity.

7. The method of claim 1 , wherein the first period of inactivity and the second period of inactivity are about a same length of time.

8. The method of claim 1 , wherein the safe interval is greater than a period of inactivity at which the first connection was not disconnected.

9. The method of claim 1 , wherein the first period of inactivity and the second period of inactivity are greater than a predetermined period.

10. The method of claim 1 , wherein the safe interval is between a period of inactivity at which the first and second connections of the network were not disconnected and the first and second periods of inactivity.

11. The method of claim 1 , wherein the safe interval is based on a number of periods of inactivity at which a connection is disconnected.

12. The method of claim 1 , wherein the safe interval is based on reducing battery consumption of the mobile terminal.

13. A method for network communication between a mobile terminal and a remote entity in a communications network, the method comprising:

establishing a first connection over a network between a mobile terminal and a remote entity;

exchanging keep-alive messages at varying intervals over the first connection based on periods of inactivity of the first connection;

wherein the first connection is disconnected after a first period of inactivity;

establishing a second connection over the network between the mobile terminal and the remote entity;

exchanging keep-alive messages at varying intervals over the second connection based on periods of inactivity of the second connection;

wherein the second connection is disconnected after a second period of inactivity; and

receiving, from the mobile terminal, keep-alive messages at a safe interval via a subsequent connection over the network based on inactivity in the subsequent connection, wherein the safe interval is based on the first disconnection and the second disconnection.

14. The method of claim 13 , wherein at least one of the first and second connections is a TCP/IP connection.

15. The method of claim 13 , further comprising associating a network-specific safe interval with the network.

16. The method of claim 15 , wherein the network-specific safe interval is used for sending keep-alive messages when re-entering the network.

17. The method of claim 13 , wherein the safe interval is less than the first period of inactivity and the second period of inactivity by at least a safety margin.

18. The method of claim 13 , wherein the safe interval is based on the first period of inactivity and the second period of inactivity.

19. The method of claim 13 , wherein the first period of inactivity and the second period of inactivity are about a same length of time.

20. The method of claim 13 , wherein the safe interval is greater than a period of inactivity at which the first connection was not disconnected.

21. The method of claim 13 , wherein the first period of inactivity and the second period of inactivity are greater than a predetermined period.

22. The method of claim 13 , wherein the safe interval is between a period of inactivity at which the first and second connections of the network were not disconnected and the first and second periods of inactivity.

23. The method of claim 13 , wherein the safe interval is based on a number of periods of inactivity at which a connection is disconnected.

24. The method of claim 13 , wherein the safe interval is based on reducing battery consumption of the mobile terminal.

25. A mobile terminal comprising:

a communications interface;

a battery;

the mobile terminal in conjunction with the communications interface is configured for:

establishing a first connection over a network between a mobile terminal and a remote entity;

exchanging keep-alive messages at varying intervals over the first connection based on periods of inactivity of the first connection;

wherein the first connection is disconnected after a first period of inactivity;

establishing a second connection over the network between the mobile terminal and the remote entity;

exchanging keep-alive messages at varying intervals over the second connection based on periods of inactivity of the second connection;

wherein the second connection is disconnected after a second period of inactivity; and

sending, from the mobile terminal, keep-alive messages at a safe interval via a subsequent connection over the network based on inactivity in the subsequent connection, wherein the safe interval is based on the first disconnection and the second disconnection.

26. The mobile terminal of claim 25 , wherein at least one of the first and second connections is a TCP/IP connection.

27. The mobile terminal of claim 25 , further comprising associating a network-specific safe interval with the network.

28. The mobile terminal of claim 27 , wherein the network-specific safe interval is used for sending keep-alive messages when re-entering the network.

29. The mobile terminal of claim 25 , wherein the safe interval is less than the first period of inactivity and the second period of inactivity by at least a safety margin.

30. The mobile terminal of claim 25 , wherein the safe interval is based on the first period of inactivity and the second period of inactivity.

31. The mobile terminal of claim 25 , wherein the first period of inactivity and the second period of inactivity are about a same length of time.

32. The mobile terminal of claim 25 , wherein the safe interval is greater than a period of inactivity at which the first connection was not disconnected.

33. The mobile terminal of claim 25 , wherein the first period of inactivity and the second period of inactivity are greater than a predetermined period.

34. The mobile terminal of claim 25 , wherein the safe interval is between a period of inactivity at which the first and second connections of the network were not disconnected and the first and second periods of inactivity.

35. The mobile terminal of claim 25 , wherein the safe interval is based on a number of periods of inactivity at which a connection is disconnected.

36. The mobile terminal of claim 25 , wherein the mobile terminal in conjunction with the communications interface is configured for reducing battery consumption.

37. A server comprising:

a communications interface;

the server in conjunction with the communications interface is configured for:

establishing a first connection over a network between a mobile terminal and the server;

exchanging keep-alive messages at varying intervals over the first connection based on periods of inactivity of the first connection;

wherein the first connection is disconnected after a first period of inactivity;

establishing a second connection over the network between the mobile terminal and the server;

exchanging keep-alive messages at varying intervals over the second connection based on periods of inactivity of the second connection;

wherein the second connection is disconnected after a second period of inactivity; and

receiving, from the mobile terminal, keep-alive messages at a safe interval via a subsequent connection over the network based on inactivity in the subsequent connection, wherein the safe interval is based on the first disconnection and the second disconnection.

38. The server of claim 37 , wherein at least one of the first and second connections is a TCP/IP connection.

39. The server of claim 37 , further comprising associating a network-specific safe interval with the network.

40. The server of claim 39 , wherein the network-specific safe interval is used for sending keep-alive messages when re-entering the network.

41. The server of claim 37 , wherein the safe interval is less than the first period of inactivity and the second period of inactivity by at least a safety margin.

42. The server of claim 39 , wherein the safe interval is based on the first period of inactivity and the second period of inactivity.

43. The server of claim 37 , wherein the first period of inactivity and the second period of inactivity are about a same length of time.

44. The server of claim 37 , wherein the safe interval is greater than a period of inactivity at which the first connection was not disconnected.

45. The server of claim 37 , wherein the first period of inactivity and the second period of inactivity are greater than a predetermined period.

46. The server of claim 37 , wherein the safe interval is between a period of inactivity at which the first and second connections of the network were not disconnected and the first and second periods of inactivity.

47. The server of claim 37 , wherein the safe interval is based on a number of periods of inactivity at which a connection is disconnected.

48. The server of claim 37 , wherein the safe interval is based on reducing battery consumption of the mobile terminal.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 15, 2019
From: TERVAHAUTA, MIKKO; BACKHOLM, ARI; SALORINNE, SEPPO; AHONEN, JUKKA; DAAVITTILA, MIKKO; EVERITT, ANDREW; VUORNOS, LAURI
To: SEVEN NETWORKS INTERNATIONAL OY
Reel/Frame 048002/0530 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 15, 2019
From: SEVEN NETWORKS INTERNATIONAL OY
To: SEVEN NETWORKS, INC.
Reel/Frame 048002/0575 →
ENTITY CONVERSION Recorded Jan 15, 2019
From: SEVEN NETWORKS, INC.
To: SEVEN NETWORKS, LLC
Reel/Frame 048071/0860 →
Continuity (12)
Continuation 16046946 · Jul 26, 2018
Continuation 15883436 · Jan 30, 2018
Continuation 15281704 · Sep 30, 2016
Continuation 15079089 · Mar 24, 2016
Continuation 14662161 · Mar 18, 2015
Continuation 14283193 · May 20, 2014
Continuation 13043425 · Mar 8, 2011
Continuation In Part 12853119 · Aug 9, 2010
Continuation 11471630 · Jun 21, 2006
Provisional Application 61408826 · Nov 1, 2010
Provisional Application 60707170 · Aug 11, 2005
Related Publication 20190208566A1 · Jul 4, 2019