Apparatus and method for converting megaco protocol

• US 20060109862A1
• Filed: 11/21/2005
• Published: 05/25/2006
• Est. Priority Date: 11/19/2004
• Status: Active Grant

• Current Assignee: Electronics and Telecommunications Research Institute
• Original Assignee: Electronics and Telecommunications Research Institute
• Inventors: Kim, Do-Young, Choi, Seung-Han
• Granted Patent: US 7,756,139 B2
• Time in Patent Office: Days
• US Class Current: 370/466
• CPC Class Codes: H04L 65/1033 Signalling gateways
• 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/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/1106 Call signalling protocols; H.323 and related

Abstract

An apparatus and a method for megaco protocol conversion is provided. The apparatus includes: a plurality of first protocol execution means for receiving a plurality of different protocol packets, executing operations according to the received protocols, analyzing the received protocols, and generating protocol execution parameters; a megaco protocol execution means for receiving a megaco protocol packet, executing operations according to the received protocol, analyzing the received protocol, and generating protocol execution parameters; databases for storing connection information between the objects and protocol conversion functions; and a protocol conversion means for interworking between the first protocol execution means and the megaco protocol execution means, searching for destination objects and the protocol conversion functions in the database, and converting the generated protocol execution parameters to protocol types of the destination objects, based on condition modes of objects which transmitted the protocol packets.

Claims

1. An apparatus for converting a megaco protocol to a different protocol, comprising:

a plurality of first protocol execution means for receiving a plurality of different protocol packets, executing operations according to the received protocols, analyzing the received protocols, and generating protocol execution parameters;

a megaco protocol execution means for receiving a megaco protocol packet, executing operations according to the received protocol, analyzing the received protocol, and generating protocol execution parameters;

databases for storing connection information between the objects and protocol conversion functions; and

a protocol conversion means for interworking between the first protocol execution means and the megaco protocol execution means, searching for destination objects and the protocol conversion functions in the database, and converting the generated protocol execution parameters to protocol types of the destination objects, based on condition modes of objects which transmitted the protocol packets.

2. The apparatus as recited in claim 1, further including:

a master mode control means for controlling the megaco protocol execution means to operate in master mode; and

a slave mode control means for controlling the megaco protocol execution means to operate in slave mode.

3. The apparatus as recited in claim 1, wherein the databases include:

an object information database including an object connection identifier for distinguishing connection relations between a master mode object and a slave mode object, an object IP address, an object condition mode for distinguishing an object mode and a protocol type of the object;

a terminal information database including a terminal subscriber'"'"'s information identifier, an object connection identifier for distinguishing connection relations between a master mode object and a slave mode object, a terminal IP address, and a protocol type of the terminal; and

a conversion function database including an input protocol type, an output protocol type and conversion functions.

4. The apparatus as recited in claim 2, wherein the databases include:

an object information database including an object connection identifier for distinguishing connection relations between a master mode object and a slave mode object, an object IP address, an object condition mode for distinguishing an object mode and a protocol type of the object;

a terminal information database including a terminal subscriber'"'"'s information identifier, an object connection identifier for distinguishing connection relations between a master mode object and a slave mode object, a terminal IP address, and a protocol type of the terminal; and

a conversion function database including an input protocol type, an output protocol type and conversion functions.

5. The apparatus as recited in claim 3, wherein the protocol conversion means includes:

means for determining an object mode from the object information database by utilizing the received protocol execution parameters;

means for determining a protocol type of a destination object from the terminal information database if the mode is master;

means for determining a protocol type of a destination object from the object information database if the mode is slave; and

means for converting the received protocol execution parameters to the determined protocol type of the destination object by utilizing the conversion functions stored in the conversion function database.

6. The apparatus as recited in claim 4, wherein the protocol conversion means includes:

means for determining an object mode from the object information database by utilizing the received protocol execution parameters;

means for determining a protocol type of a destination object from the terminal information database if the mode is master;

means for determining a protocol type of a destination object from the object information database if the mode is slave; and

means for converting the received protocol execution parameters to the determined protocol type of the destination object by utilizing the conversion functions stored in the conversion function database.

7. A method for megaco protocol conversion, comprising the steps of:

a) receiving a protocol packet and generating protocol execution parameters;

b) searching an object information database entry by utilizing the generated protocol execution parameters;

c) verifying an object condition mode of the searched object information database entry;

d) verifying a protocol type of a destination object by utilizing the generated protocol execution parameters, based on the verified object condition mode; and

e) converting the generated protocol execution parameters to the verified protocol type of the destination object by utilizing parameter conversion functions.

8. The method of claim 7, wherein said step b) is carried out by utilizing an object IP address from the generated protocol execution parameters as an index.

9. The method of claim 8, wherein the object information database entry includes:

an object connection identifier for distinguishing connection relations between a master mode object and a slave mode object;

an object IP address;

an object condition mode for distinguishing an object mode; and

a protocol type of the object.

10. The method of claim 7, wherein said step of d) includes the steps of:

searching a terminal information database entry by utilizing a terminal identifier from the generated protocol execution parameters and the object connection identifier from the object information database entry as an index, if an object condition mode is master;

searching an object information database entry of a master mode object by utilizing the object connection identifier of the object information database entry as an index, if the object condition mode is slave; and

verifying a protocol type of the searched database entry.

11. The method of claim 10, wherein the terminal information database entry includes:

a terminal subscriber'"'"'s information identifier;

an object connection identifier for distinguishing connection relations between a master mode object and a slave mode object;

a terminal IP address; and

a protocol type of the terminal.

12. The method of claim 7, wherein said step e) includes the steps of:

searching a parameter conversion function database entry by utilizing a protocol type of the generated protocol execution parameters as an input index, and the protocol type of the verified destination object as an output index; and

converting the generated protocol execution parameters to a protocol type of the destination object by utilizing the conversion functions of the searched parameter conversion function database entry.