Media gateway proxy

• US 6,766,377 B1
• Filed: 08/24/2000
• Issued: 07/20/2004
• Est. Priority Date: 08/24/2000
• Status: Expired due to Term

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Poplett, John, Ramakrishna, Sudhakar, Bekkerman, Boris, Grabelsky, David
• Primary Examiner(s): Dinh, Dung C.
• Assistant Examiner(s): BARQADLE, YASIN M
• Application Number:
  US09/645,247
• Time in Patent Office: 1,426 Days
• Field of Search: 709/238, 709/245, 709/236, 709/218, 709/219, 709/204, 709/203, 370/352, 370/353, 370/354.5
• US Class Current: 709/238
• CPC Class Codes: H04L 65/1043 Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
• CPC Class Codes: H04L 65/1101 Session protocols

Abstract

A Media Gateway proxy receives a message and parses the message. The message contains an attribute, sub-command, and a destination address. The proxy stores the message and the attributes. Each of the attributes corresponds to a selected one of a plurality of Media Gateways. Each of the gateways has an address. The proxy finds in the memory the address of the selected Media Gateway using the destination address and the attribute. The proxy then forms a message using said sub-command, said address, and said attribute and transmits the message to the destination Media Gateway.

Claims

1. A Media Gateway proxy logically positioned between a Media Gateway Controller (MGC) and a plurality of Media Gateways comprising:

a frontend for receiving a message from said MGC and parsing said message, said message containing an attribute, sub-command, and a destination address;

a memory, coupled to said frontend, for storing said message and said attributes, each of said attributes corresponding to a selected one of said plurality of Media Gateways, each of said gateways having an address;

middleware, coupled to said frontend, for finding in said memory said address of a said selected Media Gateway using said destination address and said attribute; and

an internal MGC, coupled to said middleware, for receiving the address of said gateway, said subcommand, and said attribute, and forming a plurality of other messages using said sub-command, said address, and said attribute.

2. The Media Gateway proxy of claim 1:

wherein said internal MGC receives replies from said plurality of MGs, each of said replies containing the transaction completion associated with a selected sub-command; and

wherein said middleware determines if said replies include all of said transaction completions and wherein said frontend transmits a message when all replies have been received.

3. The Media Gateway proxy of claim 2 wherein said messages include transactions conforming to a media gateway protocol.

4. The Media Gateway proxy of claim 3 wherein said protocol is MEGACO.

5. The Media Gateway proxy of claim 1 wherein said plurality of Media Gateways comprise a virtual grouping.

6. The Media Gateway proxy of claim 5 wherein said destination address is associated with said virtual grouping.

7. A method of transmitting and processing messages, comprising the steps of:

receiving a message and parsing said message, said message including an attribute, sub-command, and a destination address;

storing in memory said message and said attributes, each of said attributes corresponding to a selected one of said plurality of Media Gateways, each of said gateways having an address;

finding in said memory said address of a selected one of said Media Gateways using said destination address and said attribute; and

receiving the address of said gateway, said subcommand, and said attribute and forming a unique message for each of said sub-commands, said addresses, and said attributes.

8. The method of claim 7 comprising the further steps of:

receiving replies from said plurality of MGs, each of said replies including the transaction completion of selected one of said sub-commands;

determining if said replies include all of said transaction completions; and

transmitting a message when all replies have been received.

9. The method of claim 8 wherein said messages conform to a Media Gateway protocol.

10. The method of claim 9 wherein said protocol is MEGACO.

11. The method of claim 8 wherein said destination address is the address of a virtual Media Gateway.

12. A computer readable medium having stored therein instructions for causing a processing unit to execute the following method:

receiving a message and parsing said message, said message including an attribute, sub-command, and a destination address;

storing said message and said attributes, each of said attributes corresponding to a selected one of said plurality of Media Gateways, each of said gateways having an address;

finding in said memory said address of a selected one of said Media Gateways using said destination address and said attribute; and

receiving the address of said gateway, said subcommand, and said attribute and forming a unique message for each of said sub-commands, said addresses, and said attributes.

13. A device for transmitting and processing messages comprising:

a first receiver that receives a message and parses said message, said message containing an attribute, sub-command, and a destination address;

a memory, coupled to said first receiver, that stores said message and said attributes, each of said attributes corresponding to a selected one of said plurality of Media Gateways, each of said gateways having an address;

a locator, coupled to said memory, that finds in said memory said address of a said selected Media Gateway using said destination address and said attribute; and

a second receiver, coupled to said locator, that receives the address of said gateway, said subcommand, and said attribute and forms messages using said sub-command, said address, and said attribute.

14. The device of claim 13 further comprising:

a third receiver for receiving replies from said plurality of MGs, each reply containing transaction completions for a sub-command;

a determiner for determining if all of said sub-commands have been received; and

a transmitter for transmitting a message when all transaction completions of said sub-commands have been received.

15. A network comprising:

a Media Gateway Controller (MGC);

a Media Gateway proxy, said proxy coupled to said MGC and comprising;

a first receiver that receives a message and parses said message, said message containing an attribute, sub-command, and a destination address;

a memory, coupled to said first receiver, that stores said message and said attributes, each of said attributes corresponding to a selected one of said plurality of Media Gateways, each of said gateways having an address;

a locator, coupled to said memory, that finds in said memory said address of a said selected Media Gateway using said destination address and said attribute; and

a second receiver, coupled to said locator, that receives the address of said gateway, said subcommand, and said attribute and forms messages using said sub-command, said address, and said attribute; and

a plurality of Media Gateways coupled to said Media Gateway proxy.