Systems and methods of group distribution for latency sensitive applications

• US 7,738,900 B1
• Filed: 02/15/2007
• Issued: 06/15/2010
• Est. Priority Date: 02/15/2007
• Status: Active Grant

• Current Assignee: Nextel Communications Inc (Deutsche Telekom AG)
• Original Assignee: Nextel Communications Inc (Deutsche Telekom AG)
• Inventors: Choksi, Ojas, Manroa, Arun
• Primary Examiner(s): TRINH, TAN H
• Application Number:
  US11/706,218
• Time in Patent Office: 1,216 Days
• Field of Search: 455/518, 455/519, 455/414.1, 455/466, 455/426.1, 455/90.2, 455/416, 455/435, 370/270, 370/261, 709/206, 709/79, 709/100, 709/204, 709/205
• US Class Current: 455/519
• CPC Class Codes: H04L 12/1859 adapted to provide push services, e.g. data channels
• CPC Class Codes: H04L 12/1881 with schedule organisation, e.g. priority, sequence management
• CPC Class Codes: H04L 63/0281 Proxies

Abstract

Systems and methods for supporting group communications are provided. A group list management server (GLMS) stores communications group definitions in documents, such as extensible mark-up language (XML) documents. The communications group can include communication addresses for different types of communication applications, including electronic mail, voice telephone, data, instant messaging, voice dispatch, short messaging service (SMS), and multimedia service (MMS). Various methods for managing communications groups and features provided for communications groups are provided.

Claims

1. A method for supporting communications groups, the method comprising the acts of:

determining, by a group list management server, that an event for a communications group occurs;

determining, by the group list management server, that a member of the communications group is associated with a latency-sensitive application; and

distributing, by the group list management server, information associated with the event to a data distribution function,

wherein the data distribution function identifies one or more servers associated with the latency-sensitive application and the data distribution function distributes the information associated with the event to the identified one or more servers associated with latency-sensitive application.

2. The method of claim 1, wherein the latency sensitive application is a voice communications application.

3. The method of claim 2, wherein the voice communications application is a dispatch voice communication application.

4. The method of claim 1, wherein the event is creation of a communications group.

5. The method of claim 1, wherein the event is deletion of a communications group.

6. The method of claim 1, wherein the event is addition of the member associated with the latency-sensitive communications to an existing communications group.

7. A method for supporting communications groups, the method comprising the acts of:

determining that an event for a communications group occurs;

determining that a member of the communications group is associated with a latency-sensitive application; and

distributing information associated with the event to a server associated with the latency-sensitive application,

wherein the server is a data distribution server coupled to servers supporting latency-sensitive applications, and

wherein the data distribution server forwards the information associated with the event to a server supporting a particular latency-sensitive application.

8. The method of claim 7, wherein the server supporting the particular latency-sensitive application stores a local copy of the information associated with the event.

9. The method of claim 7, wherein the data distribution server uses a local copy of the information to maintain a synchronization state of the servers supporting latency-sensitive applications.

10. The method of claim 9, wherein the data distribution server uses the local copy of the information to provide a differential update to the servers supporting latency-sensitive applications.

11. The method of claim 9, wherein the data distribution server uses the local copy of the information to provide a complete update to the servers supporting latency-sensitive applications in case of cache loss or server restart.