THROTTLING SERVER COMMUNICATIONS IN A COMMUNICATION NETWORK

• US 20060286993A1
• Filed: 06/14/2006
• Published: 12/21/2006
• Est. Priority Date: 06/20/2005
• Status: Abandoned Application

• Current Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Original Assignee: Motorola, Inc. (Motorola Solutions, Inc.)
• Inventors: Hallin, Thomas G., Chen, Bonnie, Xie, Qiaobing
• Application Number:
  US11/424,018
• Publication Number:
  US 20060286993A1
• Time in Patent Office: Days
• US Class Current: 455/518
• CPC Class Codes: H04W 4/08 User group management
• CPC Class Codes: H04W 4/10 Push-to-Talk [PTT] or Push-On-Call services
• CPC Class Codes: H04W 76/45 for Push-to-Talk [PTT] or Push-to-Talk over cellular [PoC] services
• CPC Class Codes: H04W 8/12 between location registers or mobility servers

Abstract

An apparatus and method for throttling server communications in a communication network. Firstly, priorities are defined by a watcher for particular status events. These priorities are then mapped to a list of status events in an event filter. In response to a change of status event of a presentity, the status event is compared to the list of status events of the event filter. If the comparable status event has an associated higher priority, a notification is sent of the change of status event to the watcher with substantially no delay. If the comparable status notification event has an associated lower priority, the status event is filtered in the event filter, and sent to the watcher, as needed, during a predetermined interval. A unique priority code can be defined for events and/or a maximum delay for sending a notification of an event change can be defined for events.

Claims

1. A method for throttling communication messages in a communication network, the method comprising the steps of:

defining priorities of particular status events;

mapping the priorities to a list of status events in an event filter; and

in response to a change of status event of equipment, comparing the status event of the equipment to the list of status events of the event filter, wherein

if the comparable status event has an associated higher priority, sending a notification of the change of status event with substantially no delay, and

if the comparable status notification event has an associated lower priority, filtering the status event in the event filter.

2. The method of claim 1, wherein the defining step includes defining those status events where notification is not desired, and wherein the comparing step includes filtering out those lower priority status events where notification is not desired.

3. The method of claim 1, wherein the priorities are indicated in fields of a filter document for the event filter.

4. The method of claim 1, wherein priority is defined by associating a maximum delay with particular status events, wherein those events with substantially no maximum delay are higher priority events and those events with more than zero maximum delay are lower priority events, and wherein the event filter filters and sends the status event notification before the maximum delay expires.

5. The method of claim 1, further comprising the step of determining a Quality of Service (QoS) value for available channels in the network, wherein the notification for higher priority status events is sent on a channel with a higher QoS and the notification for lower priority status events are sent on a channel with a lower QoS.

6. The method of claim 1, wherein the notifications for filtered lower priority events are sent at predetermined periodic time intervals.

7. The method of claim 1, wherein for lower priority event notifications further comprising the step of establishing channel usage, wherein

if a channel is being used, the notification is sent between normal communication traffic, and

if a channel is not being used, the capacity of the network is used to decide whether to send the notification on the channel.

8. The method of claim 1, further comprising the step of adding a timer parameter to a notification packet for lower priority events, wherein if the notification packet is not sent before the timer expires then the notification packet is discarded.

9. The method of claim 1, wherein for lower priority events, if a packet queue of the server is full then a notification packet is discarded.

10. In a communication network, a server with throttled communications, the server comprising:

a receiver that receives defined priorities of particular status events from a watcher;

a transmitter to transmit status event notifications to the watcher;

an event filter operable to map the priorities to a list of status events; and

a controller coupled to the receiver, transmitter and event filter, the controller responds to a change of status event of a presentity of the communication network by comparing the status event of the equipment to the list of status events of the event filter, wherein

if the comparable status event has an associated higher priority, the controller directs the transmitter to send a notification of the change of status event with substantially no delay to the watcher, and

if the comparable status event has an associated lower priority, the controller directs the event filter to filter the status event.

11. The server of claim 10, wherein the receiver also receives those status events from the watcher where notification is not desired, and wherein the event filter filters out those lower priority status events where notification is not desired.

12. The server of claim 10, wherein the priorities are indicated in fields of a filter document for the event filter.

13. The server of claim 10, wherein priority is defined by the watcher which associates a maximum delay with particular status events, wherein the controller treats those events with substantially no maximum delay as higher priority events and those events with more than zero maximum delay as lower priority events, and wherein the event filter filters the status event and the transmitter sends the status event notification before the maximum delay expires.

14. The server of claim 10, wherein the controller determines a Quality of Service (QoS) value for available channels in the network, wherein the notification for higher priority status events is sent on a channel with a higher QoS and the notification for lower priority status events are sent on a channel with a lower QoS.

15. The server of claim 10, wherein the notifications for filtered lower priority events are sent by the transmitter at predetermined periodic time intervals.

16. The server of claim 10, wherein for lower priority event notifications the controller establishes channel usage, wherein

if a channel is being used, the notification is transmitted between normal communication traffic, and

if a channel is not being used, the capacity of the network is used to decide whether to transmit the notification on the channel.

17. The server of claim 10, wherein the controller adds a timer parameter to a notification packet for lower priority events, wherein if the notification packet is not transmitted before the timer expires then the notification packet is discarded by the controller.

18. The server of claim 10, wherein for lower priority events, if the controller determines that a packet queue of the server is full then a notification packet is discarded by the controller.