Arrangement for distributing and dispatching traffic in a network, especially H.323 generated traffic

• US 6,738,383 B1
• Filed: 08/31/1999
• Issued: 05/18/2004
• Est. Priority Date: 02/09/1999
• Status: Expired due to Term

• Current Assignee: Telefonaktiebolaget LM Ericsson
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Kliland, Kevin, Corneliussen, Knut Snorre Bach, Skjæran, Espen, Iveland, Espen
• Primary Examiner(s): Rao, Seema S.
• Assistant Examiner(s): ABELSON, RONALD B
• Application Number:
  US09/387,355
• Time in Patent Office: 1,722 Days
• Field of Search: 370/400, 370/401, 370/352, 370/389, 370/392, 370/356
• US Class Current: 370/401
• CPC Class Codes: H04L 12/1485 Tariff-related aspects
• CPC Class Codes: H04L 41/5029 Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related
• CPC Class Codes: H04L 65/80 Responding to QoS

Abstract

The present invention relates to an arrangement for distributing and dispatching traffic in a network, especially H.323 generated traffic, which arrangement comprises one or more gatekeepers, here designated as so-called external or real gatekeepers, and for the purpose of utilizing such real gatekeepers in a far more efficient and cost saving manner, and also for avoiding reconfiguration of endpoints depending on which gatekeepers with which they want to communicate, the present invention suggests a solution characterized by the introduction of one or more internal gatekeepers, here also designated as so-called internal lightweight gatekeepers, each such internal gatekeeper basically understanding any message used by any endpoint when registering to a real gatekeeper.

Claims

1. An internal gatekeeper for distributing and dispatching traffic in a network, wherein:

the traffic is based on ITU-T-recommendation H.323;

the internal gatekeeper is arranged in a specific domain and is adapted to put an endpoint of the specific domain in contact with an external real gatekeeper placed outside the specific domain, the external real gatekeeper supporting a full H.323 message set;

the internal gatekeeper supports a subset of the H.323 message set used by any endpoint when registering to an external real gatekeeper, the subset including GRQ (Gatekeeper Request), GCF (Gatekeeper Confirm), GRJ (Gatekeeper Reject), IRR (Information Request Response), IRQ (Information Request), RAI (Resource Availability Indication), RAC (Resource Availability Confirm), RRQ (Registration Request), RCF (Registration Confirm), and RRJ (Registration Reject);

the internal gatekeeper is arranged to maintain a list or table of valid real gatekeepers; and

the external real gatekeeper is arranged to register an internal gatekeeper during start-up.

2. The internal gatekeeper as claimed in claim 1, wherein said table is supplemented with resource information indicating the load on each particular real gatekeeper.

3. The internal gatekeeper as claimed in claim 2, wherein said table is supplemented with information relating to quality of service (QoS) and cost.

4. The internal gatekeeper as claimed in claim 3, wherein a proprietary non-StandardData field of the GCF and GRJ messages are used for exchanging information between the internal gatekeeper and any external real gatekeeper, the non-StandardData field being used to convey information used in supplementary fields of said table.

5. The internal gatekeeper as claimed in claim 4, wherein the proprietary non-StandardData field of the GRQ message is used to communicate at least one of a desired cost leveland type of QoS of the external real gatekeeper.

6. The internal gatekeeper as claimed in claim 4 or 5, wherein a first byte of the non-StandardData field in the GCF message is arranged to contain an integer indicating a load on the real gatekeeper.

7. The internal gatekeeper as claimed in claim 1, wherein the table is updated statically.

8. The internal gatekeeper as claimed in claim 1, wherein the table is updated dynamically on GCF, GRJ and RAI received from any external real gatekeeper.

9. The internal gatekeeper as claimed in any of claim 1, wherein the internal gatekeeper is adapted to put an endpoint in contact with an external real gatekeeper by forwarding the GRQ to a randomly picked external real gatekeeper.

10. The internal gatekeeper as claimed in claim 1, wherein the internal gatekeeper is adapted to communicate with a plurality of endpoints, said plurality of endpoints only knowing about said one internal gatekeeper and thereby avoiding reconfiguration.

11. The internal gatekeeper as claimed in claim 1, wherein the internal gatekeeper is adapted to put an endpoint in contact with an external real gatekeeper by forwarding the GRQ based on information in said internal table.