EFFICIENT MESSAGING OVER INTERNET PROTOCOL

• US 20100099421A1
• Filed: 10/17/2008
• Published: 04/22/2010
• Est. Priority Date: 10/17/2008
• Status: Active Grant

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: Verizon Corporate Services Group Incorporated (Verizon Communications Inc.)
• Inventors: PATEL, Biren, SIVALINGHAM, Sanjeevan, KUPSH, Jerry
• Granted Patent: US 8,503,300 B2
• Time in Patent Office: Days
• US Class Current: 455/450
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 76/30 Connection release
• CPC Class Codes: H04W 80/06 Transport layer protocols, e.g. TCP [Transport Control Protocol] over wireless transmission control protocol/Internet protocol [TCP/IP] or user datagram protocol [UDP] H04L69/16

Abstract

A method for a client and server based messaging system efficiently exchanges messages over an IP connection in a wireless network. Also included is an automated method by which a messaging client can request intelligent and efficient presence updates from the wireless network by utilizing timers and adapt such timers based on load conditions in the wireless network.

Claims

1. A method comprising:

providing a timer for a mobile device and a timer for a messaging server, each of the timers measuring a time period less than a time period to trigger closing of an idle Transmission Control Protocol (TCP) connection within a network;

starting the timer for the mobile device whenever the mobile device determines that data is exchanged over a TCP connection between the mobile device and the messaging server;

starting the timer for the messaging server whenever the messaging server determines that data is exchanged over a TCP connection between the mobile device and the messaging server;

determining, by one of the mobile device or the messaging server, and based on one of the timers, if data is exchanged within the time period measured by the timers;

closing, by one of the mobile device or the messaging server, the TCP connection if data is not exchanged within the time period measured by the timers; and

re-establishing, by one of the mobile device or the messaging server, the TCP connection if a data exchange is necessary after closing the TCP connection.

2. The method of claim 1, further comprising:

re-establishing the TCP connection if an acknowledgement message is not received from a mobile application client operating on the mobile device.

3. The method of claim 1, where the closing the TCP connection is initiated by the messaging server.

4. The method of claim 1, where the closing the TCP connection is initiated by the mobile device.

5. The method of claim 1, further comprising:

obtaining an identifier for the mobile device, the identifier including information to permit communication with the mobile device outside of a TCP connection,

and where re-establishing the TCP connection includes sending, to the mobile device via the identifier, an indication to establish a new TCP connection.

6. The method of claim 5, further comprising:

storing the identifier for the mobile device at the messaging server.

7. The method of claim 5, where the identifier is one of a mobile directory number (MDN) or a unicast access terminal identifier (UATI).

8. The method of claim 5, where the indication to establish a new TCP connection is sent via short message service (SMS) or user datagram protocol (UDP).

9. A system, comprising:

an identifier manager to collect and store an identifier for a mobile device, the identifier including information to permit communication with the mobile device outside of a Transmission Control Protocol (TCP) connection;

a messaging manager to exchange data with the mobile device over a TCP connection in a network;

a TCP connection timer to measure an idle time between each data exchange, the TCP timer measuring a time period less than a time period to trigger closing of an idle TCP connection within the network; and

a processor to automatically close the TCP connection based on the TCP connection timer and to send an indicator, via the identifier, to the mobile device to initiate re-establishing the TCP connection.

12. The system of claim 9, where the identifier is one of a mobile directory number (MDN), a unicast access terminal identifier (UATI), or an IP address and user datagram protocol (UDP) port.

13. The system of claim 9, where the indicator is sent via short message service (SMS) or user datagram protocol (UDP).

14. The system of claim 9, where the time period measured by the TCP connection timer is a fixed value.

23. The system of claim 9, where the indicator further includes data to be displayed to a user of the mobile device.

10. (canceled)

11. (canceled)

15. A method, comprising:

receiving time-based load criteria identifying multiple load conditions of a network;

establishing time values for a frequency of automatic user presence update requests provided from a mobile device, each of the time values corresponding to one of the multiple load conditions;

identifying, based on the time-based load criteria, a load condition from one of the multiple load conditions of the network; and

sending, to the mobile device, the time value for a frequency of user presence update requests based on the identified load condition for the network, where the time value causes providing of less frequent presence update request during peak load conditions of the network.

16. The method of claim 15, further comprising:

determining a change in the identified load condition, and

sending, to the mobile device, a new value for a frequency of automatic user presence update requests based on the change in the determined load condition.

17. The method of claim 15, further comprising:

receiving user presence update requests from the mobile device at the frequency of automatic presence update requests based on the identified load condition for the network.

18. A method, comprising:

establishing, by a server via a network, a Transmission Control Protocol (TCP) connection with a mobile device;

measuring, by the server, a time interval for an idle period between each data exchange during the TCP connection, the idle period being less than a time period to trigger closing of an idle TCP connection within a network;

closing, by the server, the TCP connection if data is not exchanged within the time interval; and

sending, by the server, to the mobile device, an indication to re-establish the TCP connection if a data exchange is necessary after closing the TCP connection.

20. The method of claim 18, where the indication is sent via one of:

short message service (SMS) using a mobile directory number (MDN) associated with the mobile device, or

an intermediate entity that forwards the indication to a unicast access terminal identifier (UATI) associated with the mobile device.

24. The method of claim 18, where the indicator further includes data to be displayed to a user of the mobile device.

19. (canceled)

21. A system comprising:

means for measuring a time interval between each data exchange of an idle Transmission Control Protocol (TCP) connection with a mobile device, the time interval being less than a time period to trigger closing of an idle TCP connection within a network;

means for closing the TCP connection if data is not exchanged within the time interval; and

means for re-establishing the TCP connection if a data exchange is necessary after closing the TCP connection, where the re-establishing is initiated by an IP messaging server.

22. (canceled)