Network gatekeeper prioritizing method and system

• US 6,907,462 B1
• Filed: 06/04/2003
• Issued: 06/14/2005
• Est. Priority Date: 06/07/1999
• Status: Expired due to Fees

• Current Assignee: RPX Clearinghouse LLC (RPX Corporation)
• Original Assignee: Nortel Networks Limited (Nortel Networks Corporation)
• Inventors: Christie, IV, Samuel H., Li, Xuewen
• Primary Examiner(s): VU, VIET DUY
• Application Number:
  US10/454,208
• Time in Patent Office: 741 Days
• Field of Search: 709/223, 709/225, 709/226, 709/227, 709/238, 709/249, 709/250, 709/224, 709/229, 719/311, 719/313, 370/401
• US Class Current: 709/226
• CPC Class Codes: H04L 65/103 in the network
• CPC Class Codes: H04L 65/104 in the network
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related
• CPC Class Codes: H04L 65/80 Responding to QoS
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/61 taking into account QoS or priority requirements
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

Methods and systems for controlling network gatekeeper message processing include overload control routines executed by a network gatekeeper to prevent the network gatekeeper from crashing during overload conditions. The overload control routines are executed in a predetermined order so that messages relating to calls in progress are preferentially processed over messages relating to newly originating calls. Fault detection routines detect protocol stack and application level faults of a network gatekeeper.

Claims

1. A user profile prioritizer for identifying messages from priority users received by a network gatekeeper, the user profile prioritizer comprising computer executable instructions embodied in a computer readable medium for performing steps comprising:

(a) receiving a message from a user in a network;

(b) extracting an IP address of the user from the message;

(c) determining whether the user is a priority user; and

(d) in response to determining that the user is a priority user, processing the message using resoruces reserved for the user by bypassing overload control routines for controlling message processing during overload conditions.

2. The user profile prioritizer of claim 1, wherein receiving the message from the user includes receiving a RAS message from the user.

3. The user profile prioritizer of claim 2, wherein receiving the RAS message from the user includes receiving an Admissions Request message from the user.

4. The user profile prioritizer of claim 1, wherein receiving the message from the user includes receiving the message from an H.323 network.

5. A called party prioritizer for prioritizer for prioritizing processing of messages received by a network gatekeeper, the called party prioritizer comprising computer executable instructions embodied in a computer readable medium for performing steps comprising:

(a) receiving a message from a terminal managed by the network gatekeeper;

(b) extracting a called party address from the message;

(c) determining if the message should be given priority based on the called party address; and

(d) in response to determining that the message should be given priority, processing the message using resources reserved for the called party address by bypassing overload control routines for regulating call processing during overload conditions.

6. The called party prioritizer of claim 5, wherein receiving the message includes receiving a Setup message from the terminal.

7. The called party prioritizer of claim 5, wherein receiving the message includes receiving the message through an H.323 network.

8. A called party prioritizer for prioritizer for prioritizing processing of messages received by an media gateway control protocol (MGCP) call agent, the called party prioritizer comprising computer executable instructions embodied in a computer readable medium for performing steps comprising:

(a) receiving a message from a calling party in an MGCP-compliant network;

(b) extracting a called party address from the message;

(c) determining whether the message should be given priority based on the called party address; and

(d) in response to determining that the message should be given priority, processing the message using resources reserved for the called party address by bypassing overload control routines for regulating call processing during overload conditions.

9. A method of handling messages, comprising:

receiving a message from a terminal managed by a gatekeeper;

extracting an internet protocol (IP) address from the message;

examining the IP address;

determining, through said examining, if the IP address corresponds to a priority participant; and

processing, in response to said determining, using resources reserved for the priority participant by bypassing overload control routines for regulating call processing during overload conditions.

10. The method of claim 9, wherein examining the IP address comprising examining a source IP address.

11. The method of claim 9, wherein examining the IP address comprising examining a destination IP address.

12. The method of claim 9, wherein said method is implemented as a computer program stores on a computer readable medium.

13. The method of claim 9, wherein said method is implemented via control logic on the gatekeeper.

14. A method of handling messages, comprising:

receiving, at a network gatekeeper, a message from a user in a network;

extracting an internet protocol (IP) address of the user from the message;

determining whether the user is a priority user based on the IP address of the user; and

in response to determining that the user is a priority user, processing the message using resources reserved for the user by bypassing overload control routines for regulating call processing during overload conditions.

15. The method of claim 14, wherein said method is implemented via control logic on a gatekeeper.

16. A method of handling messages, comprising:

receiving a message from a terminal managed by a gatekeeper;

extracting a called party address from the message;

determining if the message should be given priority based on the called party address; and

in response to determining that the message should be given priority, processing the message using resources reserved for the called party address by bypassing overload control routines for regulating call processing during overload conditions.

17. The method of claim 16, wherein said method is implemented via control logic on the gatekeeper.

18. The method of claim 16, wherein receiving the message from the terminal managed by the gatekeeper comprises receiving a Setup message from the terminal.

19. The method of claim 16, further comprising performing said extracting, determining and processing only when a processing load on the gatekeeper exceeds a predetermined threshold.