CN113747275B

CN113747275B - Virtual media gateway identification method and device

Info

Publication number: CN113747275B
Application number: CN202110932294.1A
Authority: CN
Inventors: 郭杰; 刘一凡; 唐雄辉; 程陆
Original assignee: Fiberhome Telecommunication Technologies Co Ltd
Current assignee: Fiberhome Telecommunication Technologies Co Ltd
Priority date: 2021-08-13
Filing date: 2021-08-13
Publication date: 2023-05-26
Anticipated expiration: 2041-08-13
Also published as: CN113747275A

Abstract

A virtual media gateway identification method and device relates to the PON access equipment voice technical field, the method includes: each VMG distributes unique VMG ID and IP address, each VMG creates a Socket according to IP address and port number, the physical media gateway creates VMGSockets table to manage the sockets of all VMGs; establishing a physical terminal node hash table, writing a physical terminal node ID and VMG ID binary group, and configuring an MGC corresponding to the VMG; identifying an uplink transaction request message according to the physical terminal node ID and VMG ID binary group; and inquiring the VMGSockets table according to the Socket receiving the downlink transaction request message, and identifying the downlink transaction request message. The invention does not need to set attribute parameters in the physical media gateway or MGC, and has stronger universality.

Description

Virtual media gateway identification method and device

Technical Field

The invention relates to the technical field of PON access equipment voice, in particular to a virtual media gateway identification method and device.

Background

In the H.248 media gateway control protocol, termination (Termination) and association (Context) are two main abstract objects that can be controlled by the media gateway controller (Media Gateway Controller, MGC), are business logic entities of the protocol connection model, the Termination carries various resources of the media gateway, including time division multiplexing (Time Division Multiplexing, TDM) channels and Real-time transport protocol (Real-time Transport Protocol, RTP) streams, wherein the physical Termination identifies the TDM channels, the media Termination identifies the RTP streams, and each Termination is assigned an identifier (Termination ID). The association is a set of interconnected end points describing the relationship between the end points, the media stream direction between the end points in the association being described by the topology of the association, each association being identified by an identifier (Context ID). In the h.248 media gateway control protocol, call service establishment is implemented by controlling two logical entities, namely a terminating point and an association, the command provides control of the finest granularity of the association and the terminating point, and eight kinds of related commands are included: add, modify, subtract, move, auditValue, auditCapabilities, notify, serviceChange. For example, by command, a endpoint can be added to an association, a endpoint in an association can be modified, an endpoint can be deleted from an association, an attribute of an association or endpoint can be audited, a detection event can be reported by a requesting endpoint, a tone can be played by a requesting endpoint, and a topology of an association can be modified. The set of commands is combined into a Transaction (Transaction), identified by a Transaction identifier (Transaction ID), which acts on a specified association.

In use of the present network, a physical Media Gateway (MG) having a large capacity POTS port can be partitioned into a plurality of virtual Media gateways (Virtual Media Gateway, VMG), each virtual Media Gateway being formed by a set of statically partitioned termination points. Different virtual media gateways are respectively assigned to different media gateway controllers, and each virtual media gateway appears as a complete media gateway to the media gateway controller. The method has the advantages that an operator can flexibly attribute voice users to different VMGs according to actual service demands, then access different soft switching platforms, so that one machine is multipurpose, resources of a physical media gateway can be utilized to the maximum extent, service access types of the physical media gateway are enriched, more perfect service capability is provided, and the purchasing cost of the operator is reduced to a certain extent because the voice users can access different soft switching platforms at the same time.

In a physical media gateway, other resources than the termination point cannot be statically allocated to the VMG, whereas a physical media gateway typically has only one network interface, which is shared by all VMGs. Therefore, when multiple VMGs establish a call through a shared network interface, the physical media gateway needs to identify the scope of call signaling, including signaling sent by the VMG and signaling received by the VMG from the MGC, and related to sender and receiver identification of signaling messages, identification of logical entities (association and termination points) of transaction requests, for example, uplink (VMG to MGC) transmission request messages (Notify and ServiceChange) are sent to which MGC through which VMG, related to which association, and which termination points are included in the association; the downstream (MGC to VMG) TransactionRequest message is received and processed by which VMG, acts on which association, which termination points are included in the association, etc.

The existing solution thinking is to identify the VMG by expanding an attribute parameter, and establish mapping between the VMG and the MGC according to the attribute parameter, so as to identify the VMG.

Disclosure of Invention

Aiming at the defects existing in the prior art, the invention aims to provide a virtual media gateway identification method and device, which do not need to set attribute parameters in a physical media gateway or an MGC and have strong universality.

To achieve the above object, in one aspect, a method for identifying a virtual media gateway is adopted, wherein a plurality of virtual media gateways VMGs are created in a physical media gateway, and the method includes:

each VMG distributes unique VMG ID and IP address, each VMG creates a Socket according to IP address and port number, the physical media gateway creates VMGSockets table to manage the sockets of all VMGs; establishing a physical terminal node hash table, writing a physical terminal node ID and a VMG ID binary group, and configuring a media gateway controller MGC corresponding to the VMG;

identifying an uplink transaction request message according to the physical terminal node ID and VMG ID binary group; and inquiring the VMGSockets table according to the Socket receiving the downlink transaction request message, and identifying the downlink transaction request message.

In some embodiments, the voice POTS ports of the PON access device are statically classified according to the requirement, each POTS port corresponds to a physical endpoint, the voice POTS ports are assigned to VMGs identified by VMG IDs by configuring a binary group of a physical endpoint ID and a VMG ID, and the physical media gateway monitors sockets of all VMGs through a polling mechanism.

In some embodiments, the identifying the uplink transaction request packet according to the physical endpoint ID and VMG ID tuple includes: and identifying the VMG to which the uplink transaction request message belongs, namely a sender of the uplink transaction request message, according to the binary group information of the physical terminal node ID and the VMG ID, and obtaining the MGC corresponding to the VMG, namely a receiver of the uplink transaction request message, according to the configuration.

In some embodiments, each VMG creates a Sender transaction hash table, and stores a transaction request message sent by the VMG, a VMG to which the message belongs, and corresponding MGC information;

each VMG creates an associated hash table that stores the topology between the physical and media endpoints in the association.

In some embodiments, after the uplink transaction request message is identified according to the physical endpoint ID and VMG ID tuple, the method further includes the step of sending the uplink transaction request message:

and acquiring the current association of the physical terminal node according to the association hash table, distributing a transaction request ID for the uplink transaction request message in the affiliated VMG, after finishing message grouping, writing message content, the affiliated VMG and corresponding MGC information into the Sender transaction hash table of the VMG by taking the transaction request ID as a keyword, and sending the uplink transaction request message to the corresponding MGC after caching.

In some embodiments, the method further includes the step of the physical media gateway identifying the MGC to send to the VMG response message:

the physical media gateway monitors that a certain Socket in the VMGSockets table receives the response message, acquires VMG to which the Socket belongs according to the VMGSockets table, and acquires a corresponding MGC according to the setting;

when the source IP of the response message is matched with the MGC IP corresponding to the current VMG, reading a Sender transaction hash table of the VMG, if the corresponding table entry is read, the MGC receives an uplink transaction request message sent by the VMG, and deleting the table entry corresponding to the transaction request ID from the Sender transaction hash table;

if the VMG does not receive the response message within the preset time, the VMG resends the uplink transaction request message to the corresponding MGC.

In some embodiments, each VMG creates a Receiver transaction hash table every time each MGC is configured, and stores a transaction request message received by the VMG, a VMG to which the message belongs, and corresponding MGC information;

the step of inquiring the VMGSockets table according to the Socket receiving the downlink transaction request message to identify the downlink transaction request message comprises the following steps:

the physical media gateway monitors that a certain Socket in the VMGSockets table receives a downlink task request message, acquires VMG to which the Socket belongs according to the VMGSockets table, and acquires a corresponding MGC according to the setting;

when the source IP of the downlink transaction request message is matched with the MGC IP corresponding to the current VMG, a Receiver transaction hash table of the VMG is read, and if the matched table item is read, the downlink transaction request message, the VMG to which the message belongs and the corresponding MGC information are written into the Receiver transaction hash table.

In some embodiments, after identifying the downlink transaction request packet, the method further includes:

when a downlink transaction request message requests to create an association, an association ID is allocated in the VMG, and topology information between a physical endpoint and a media endpoint is written into an association hash table of the VMG as a key word;

when the downlink transaction request message requests for modifying the association, reading the association hash table by taking the association ID as a key word, acquiring topology information between a physical terminal node and a media terminal node in a matching table item, and updating;

when the downlink transaction request message requests to delete the association, the association hash table is read by taking the association ID as a key word, the topology between the physical terminal node and the media terminal node in the matched table item is deleted, and the table item corresponding to the association ID is deleted in the association hash table.

and processing the downlink transaction request message, packaging the response message, sending the response message to the corresponding MGC by the VMG to which the downlink transaction request message belongs, and deleting the corresponding table entry from the Receiver transaction hash table.

In another aspect, there is provided an identification apparatus for a virtual media gateway, including:

a configuration module, configured to pre-configure MGCs corresponding to VMGs, and allocate unique VMG IDs and IP addresses to each VMG;

the management module is used for creating a Socket according to the IP address and the port number, creating a VMGSockets table in the physical media gateway and managing the sockets of all VMGs of the physical media gateway; the method is also used for establishing a physical terminal node hash table in the VMG and writing a physical terminal node ID and VMG ID binary group;

the identification module is used for identifying the uplink transaction request message according to the binary group of the physical terminal node ID and the VMG ID; and the VMGSockets table is also used for inquiring the VMGSockets table according to the Socket which receives the downlink transaction request message, and identifying the downlink transaction request message.

One of the above technical solutions has the following beneficial effects:

the VMG to which the transaction request message belongs, identifies the corresponding MGC according to the configuration, and completes the identification of the sender (which VMG) and the receiver (which MGC) of the uplink transaction request message sent by the physical media gateway. Inquiring a VMGSockets table according to a Socket receiving a downlink transaction request message, acquiring a VMG to which the Socket belongs, and identifying a corresponding MGC according to configuration; the identification of the sender (which MGC) and the receiver (which VMG) of the downlink message request received by the physical media gateway is completed. The identification of the uplink and downlink transaction request messages is independently judged through the physical media gateway, the setting of attribute parameters on the MGC is not needed, and for any MGC, the identification of the VMG can be realized only through the configuration of the physical media gateway, so that the universality is strong. And can be smoothly upgraded in the existing network equipment to support the service access scene of the VMG.

Drawings

Fig. 1 is a schematic diagram of a virtual media gateway identification method according to an embodiment of the present invention;

fig. 2 is a signaling flow chart of a virtual media gateway identification method according to an embodiment of the present invention.

Detailed Description

The present invention will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present invention more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the invention. In addition, the technical features of the embodiments of the present invention described below may be combined with each other as long as they do not collide with each other.

The invention provides a virtual media gateway identification method, which is based on creating a plurality of VMGs in a physical media gateway, and specifically comprises the following steps:

each VMG is assigned a globally unique VMG ID to identify the VGM, and is assigned a globally unique IP address, each VMG creates a Socket according to the IP address and port number, and the physical media gateway creates a VMGSockets table to manage the sockets of all VMGs. Further, the Socket ID is used as a key word to write a table and read a table into the VMGSockets table, the table entry stores VMG information to which the current Socket belongs, and the physical media gateway monitors the sockets of all VMGs through a polling mechanism.

Each VMG establishes a physical endpoint hash table, the table entry stores the information of the physical endpoint (including ROOT node) statically divided and attributed to the VMG, and the physical endpoint ID (Termination ID) is used as a key to write and read the table. And writing a < Termination ID, VMG ID > binary group into a physical Termination hash table of the VMG by taking the physical Termination ID as a key.

Specifically, according to the actual service requirement of the current network user, the voice POTS ports of the PON access device are statically divided, wherein each POTS port corresponds to a physical Termination point, and the voice POTS ports are assigned to VMGs identified by VMG IDs through configuration of < Termination ID, VMG ID > binary groups of the physical Termination points.

An upstream transaction request (TransactionRequest) message is identified based on the physical endpoint ID and VMG ID doublet. And inquiring the VMGSockets table according to the Socket receiving the downlink transaction request message, and identifying the downlink transaction request message.

Specifically, the upstream transaction request message refers to a message (only Notify and ServiceChange messages) sent by the VMG to the MGC, and is triggered by a physical termination point. According to the < Termination ID, VMG ID > binary group information of the physical Termination point (including the ROOT Termination point), identifying the VMG to which the transactionRequest message belongs, namely the sender of the uplink transactionRequest message, and because the configured VMG and MGC are in one-to-one correspondence, identifying the VMG, the MGC (currently registered MGC) corresponding to the VMG, namely the receiver of the uplink transactionRequest message, can be obtained according to the configuration.

The downstream message refers to a message sent by the MGC to the VMG. When the physical media gateway polling task monitors that a physical media gateway monitors that a certain Socket in the VMGSockets table receives a downlink transactionRequest message, reading a matching table entry of the VMGSockets table by taking a Socket ID as a key word, acquiring a VMG to which the Socket belongs, namely a receiver of the downlink transactionRequest message, and obtaining a corresponding MGC according to the setting, namely a sender of the downlink transactionRequest message.

As shown in fig. 1, based on the above embodiments, in some embodiments, a Sender transaction hash table may be created for each VMG, where an entry stores a TransactionRequest message sent by the VMG, a VMG to which the message belongs, and corresponding MGC information, and a transaction request ID (Transaction ID) is used as a key to write and read a table. And each VMG is configured with one (active or standby) MGC, a Receiver transaction hash table is created, a transactionRequest message received by the VMG, the VMG to which the message belongs and corresponding MGC information are stored, and the transaction request ID is used as a key word for writing and reading the table.

In addition, each VMG creates an association (Context) hash table, the entries store the topology between the physical endpoints in the association, and write and read tables using association ID (Context ID) as a key.

In some embodiments, after identifying the sender and the receiver of the uplink TransactionRequest message, the method further includes a step of sending an uplink transaction request message, which is specifically as follows:

and acquiring the current association of the physical terminal node according to the association hash table, acquiring an association ID, distributing a transaction request ID for the uplink transactionRequest message in the VMG to which the association ID belongs, after completing the grouping of the uplink transactionRequest message, writing the content of the uplink transactionRequest message, the VMG to which the message belongs and the corresponding MGC information into the Sender transaction hash table of the VMG by taking the transaction request ID as a key word, and then caching the uplink transactionRequest message and sending the uplink transactionRequest message to the MGC corresponding to the VMG. Further, a message retransmission timer may also be started.

After the MGC receives the uplink TransactionRequest message sent by the VMG, it replies a response message (TransactionReply) message to the VMG. In some embodiments, the physical media gateway identifies the TransactionReply message sent by the MGC to the VMG as follows:

when the polling task of the physical media gateway monitors that a Socket in the VMGSockets table receives the TransactionReply message, the physical media gateway will receive the TransactionReply message from the MGC with the destination address of the VMG under normal conditions. Reading a VMGSockets table by taking a Socket ID as a keyword, acquiring a VMG to which the Socket belongs after matching the table entry, and further acquiring an MGC corresponding to the VMG according to the setting. So far, the identification of the sender (which MGC) and the receiver (which VMG) of the TransactionReply message received by the physical media gateway is completed.

Analyzing the source IP of the TransactionReply message, and discarding the TransactionReply message if the source IP is not matched with the current corresponding MGC IP (i.e. the IP is different). If the source IP is matched with the MGC IP corresponding to the current VMG, reading a Sender transaction hash table of the VMG by taking a Reply ID carried by the TransactionReply message as a key. If the corresponding list item is read, it is indicated that the uplink TransactionRequest message sent by the VMG receives the TransactionReply message of the corresponding MGC, at this time, the TransactionRequest message retransmission timer can be stopped, the TransactionRequest message buffer is deleted, and the list item corresponding to the transaction request ID is deleted from the Sender transaction hash table; if the corresponding table entry is not read, the VMG considers that the received TransactionReply message is missent by the MGC, and discards the TransactionReply message.

In one case, if the TransactionReply message is not received within the preset time (the preset time can be set by the message retransmission timer), that is, the TransactionRequest message is still not received after the waiting message retransmission timer is overtime, the VMG resends the TransactionRequest message to the corresponding MGC. Specifically, a state machine mechanism can be set to judge whether a TransactionReply message is received within a preset time, and the mechanism is as follows: when the VMG receives the transactionRequest message and reads the corresponding table item in the Sender transaction hash table, the state of the transactionRequest message is set as [ sent and successfully received ]; if the preset time is overtime, rechecking that the state of the transmission of the TransactionRequest message is still [ transmitted but not received Reply ], indicating that the VMG transmits the TransactionRequest message to the MGC, and does not receive the corresponding TransactionRequest message within the preset time, and retransmitting the TransactionRequest message to the corresponding MGC.

In the above embodiment, after the physical media gateway identifies the downlink transaction request packet, the method may further include the following steps:

and analyzing the source IP of the downlink TransactionRequest message, and discarding the message if the source IP is not matched with the MGC IP corresponding to the current VMG.

If the source IP is matched with the MGC IP corresponding to the current VMG, the Receiver transaction hash table of the VMG is read by taking the transaction request ID carried by the downlink transactionRequest message as a key word. If the table entry cannot be read, the VMG receives a new downlink TransactionRequest, and the downlink TransactionRequest message content, the VMG to which the message belongs and the corresponding MGC are written into a Receiver transaction hash table of the VMG by taking the transaction request ID as a key.

Further, the VMG association hash table is obtained according to the VMG to which the downlink TransactionRequest message belongs, and the association descriptor (association ID) carried in the downlink TransactionRequest message is used as a key, so as to operate the association hash table according to different situations, which specifically includes:

when the downlink TransactionRequest message requests to create an association, an association ID is allocated in the VMG, and topology information between a physical terminal point and a media terminal point is written into an association hash table of the VMG by taking the association ID as a key word.

When the downlink TransactionRequest message requests to modify association, the association hash table of the VMG is read by taking the association ID as a key word, and topology information between a physical terminal and a media terminal in a matching table item is obtained and updated.

When the downlink TransactionRequest message requests to delete the association, the association hash table of the VMG is read by taking the association ID as a keyword, the topology between the physical terminal and the media terminal in the matched table entry is deleted, and the table entry corresponding to the association ID is deleted in the association hash table.

So far, the identification of the VMG logical entity (association and termination point) acted by the physical media gateway receiving the transaction request is completed.

After the VMG receives the downlink transactionRequest message sent by the MGC and carries out protocol processing, the VMG also comprises the step of replying the transactionReply message to the MGC, and the specific steps are as follows:

and performing a TransactionReply message group package, transmitting a TransactionReply message to the corresponding MGC by using the VMG to which the downlink transactionRequest message belongs, and then deleting the table item corresponding to the transaction request ID from the Receiver transaction hash table. So far, the identification of the sender (which VMG) and the receiver (which MGC) of the TransactionReply message sent by the physical media gateway is completed.

The invention also provides an embodiment of the identification device of the virtual media gateway, which can be used for realizing the identification method embodiment. The identification device comprises a configuration module, a management module and an identification module. The configuration module is used for pre-configuring MGCs corresponding to the VMGs and distributing unique VMG IDs and IP addresses for each VMG. The management module is used for creating a Socket according to the IP address and the port number, creating a VMGSockets table in the physical media gateway, and managing the sockets of all VMGs of the physical media gateway; and the method is also used for establishing a physical endpoint hash table in the VMG and writing a < Termination ID, VMG ID > binary group. The identification module is used for identifying the uplink transaction request message according to the < Termination ID, VMG ID >; and the VMGSockets table is also used for inquiring the VMGSockets table according to the Socket which receives the downlink transaction request message, and identifying the downlink transaction request message.

As shown in fig. 1, in this embodiment, the VMGSockets table is set in the physical media gateway, and the physical endpoint hash table is set in the VMG. The management module is further configured to create a Sender transaction hash table for each VMG, where the table entry stores a TransactionRequest message sent by the VMG, a VMG to which the message belongs, and corresponding MGC information, and write and read the table with the transaction request ID (Transaction ID) as a key word. The management module is further configured to create a Receiver transaction hash table when each VMG configures one (active or standby) MGC, store the TransactionRequest message received by the VMG, the VMG to which the message belongs, and the corresponding MGC information, and write and read the table by using the transaction request ID as a key word. In addition, the management module is further used for creating an association (Context) hash table for each VMG, and the table entries store the topology between the physical end points in the association, and write and read the table by taking the association ID (Context ID) as a key word. The Sender transaction hash table, receiver transaction hash table and associated hash table are both set in the VMG.

In the embodiment, different hash tables are set in the physical media network manager, and the TransactionRequest message and the TransactionReply message are identified according to the table items in the different hash tables, so that the sender and the receiver of the message are identified, and the attribute parameters are not required to be set in the MGC or adapted, thereby improving the universality of the identification device of the virtual media gateway.

As shown in fig. 2, the present invention is described in detail by a signaling interaction embodiment of an MGC1 with a VMG1 in a physical media gateway.

S1. create a virtual media gateway VMG1 (vmgid=1) on the physical media gateway. Configuring the IP of VMG1 to IP1:10.35.12.10, creating UDP Socket (e.g., socket id=970): 10.35.12.10.2944; and writing current Socket information and VMG1 identification information to which the current Socket information belongs into a VMGSockets table of the physical media gateway by taking the Socket ID as a keyword, and monitoring the Socket of the VMG1 by the physical media gateway through a polling mechanism. The primary MGC address of VMG1 is configured as MGC1:10.35.12.1.

S2, configuring Termination ID of POTS port 1 of the physical media gateway as aaln/1, carrying out static division on the physical terminal, statically dividing the port 1 to VMG1, and writing a < aaln/1,1> binary group into a hash table of the physical terminal of VMG1 by taking the Termination ID as a key.

S3, the user port 1 (aaln/1) is used as a calling off-hook.

S4, reading a hash table of a VMG1 physical Termination point by taking Termination ID as a key word, obtaining a < aaln/1,1> binary group, selecting VMG1 to which the Termination point aaln/1 belongs according to virtual media gateway identification VMG ID=1, obtaining the current association of the Termination point, obtaining an association ID, and then distributing a Transaction ID in the VMG 1. After the grouping of the user side event TransactionRequest message is completed, the transactionID is used as a keyword, the contents of the TransactionRequest message, VMG1 to which the message belongs and the corresponding MGC1 information are written into a Sender Transaction hash table of VMG1, then the TransactionRequest message is cached, and a Notify Transaction request message is sent to the corresponding MGC1 through a Socket1 (970) of VMG1, and the user side event is reported. Thus, the physical media gateway can correctly identify which VMG is transmitting the upstream transaction request and transmit it to which MGC.

For example, the report off-hook event message is as follows:

MEGACO/1[10.35.12.10]:2944

Transaction＝123{Context＝-{

Notify＝aaln/1{ObservedEvents＝2022{20110921T09232096:al/of{init＝False}}}

}}

s5, when a Socket polling task of the physical media gateway monitors that Socket1 in the VMGSockets table receives the TransactionReply message, firstly, the Socket ID (970) of the Socket1 is used as a keyword to read the VMGSockets table, the information of the VMG1 to which the Socket polling task belongs is obtained, and then the information of MGC1 corresponding to the VMG1 is obtained. Then analyzing the source IP of the TransactionReply message, and discarding the message if the source IP of the TransactionReply message received by Socket1 is not matched with MGC 1; if so, reading the Sender transaction hash table of the VMG1 by taking the Reply ID carried by the TransactionReply message as a key word.

If the entry is successfully read, the user side event reported by the VMG1 is indicated to receive the reply message of the MGC1, the Notify Transaction request message retransmission timer is stopped, the message cache is deleted, and the entry corresponding to the Transaction ID (123, for example) is deleted from the Sender Transaction hash table.

If the Notify transaction request still does not receive the reply message of the MGC1 after the retransmission waiting timer is overtime, retransmitting the Notify transaction request message to the corresponding MGC1 according to the VMG1 to which the message belongs.

Thus, the physical media gateway can correctly identify whether the received downlink TransactionReply message is from a legal MGC or not, and which VMG receives and processes the message.

S6, MGC1 sends an Add transaction request message to the physical media gateway to request the physical media gateway to create a channel, wherein the IP of the message is IP1:10.35.12.10, for example, the contents of a transactionRequest message are as follows:

！/1[10.35.12.1]:2944

T＝6068{C＝${A＝aaln/1,A＝${M{L{

v＝0

c＝IN IP4$

m＝audio$RTP/AVP 8

a＝ptime:20

},O{MO＝RC,nt/jit＝40}}}}}

s7, when the polling task of the physical media gateway monitors that a Socket1 in the VMGSockets table receives a transactionRequest message, firstly, reading the VMGSockets table by taking a Socket ID of the Socket1 as a key word, acquiring VMG1 information to which the Socket belongs, and further acquiring MGC1 information corresponding to the VMG 1.

Then analyzing the source IP of the transactionRequest message, if the source IP of the transactionRequest message received by Socket1 is not matched with MGC1, discarding the message. If so, reading the Receiver Transaction hash table of the VMG1 by taking the Transaction ID carried by the transactionRequest message as a key word. If the table entry cannot be read, the VMG1 receives a new TransactionRequest message, and then the TransactionRequest message content, the VMG1 to which the message belongs and the corresponding MGC1 information are written into the Receiver Transaction hash table of the VMG1 by using the transactionid as a key. Thus, the physical media gateway can correctly identify whether the received downlink TransactionRequest message is from a legal MGC or not, and which VMG receives and processes the message.

S8, acquiring a VMG1 association hash table according to the attribution of the Add transaction request message, and performing the following operations in the VMG1 by using an association descriptor (association ID= $) specified by the Add transaction request message:

1) VMG1 selects a media Termination RTP1 from the shared resource (Termination id=rtp/4044);

2) VMG1 assigns an association ID (e.g., context id=45), and writes the topology between physical endpoint aaln/1 and media endpoint RTP1 in the association hash table of VMG1 with the association ID as a key.

S9, after the VMG1 finishes processing the Add Transaction request message and completes the transactionReply message group package, replying the transactionReply message to the MGC1 corresponding to the VMG1, and deleting the entry corresponding to the transactionID=6068 in the Receiver Transaction hash table. Thus, the physical media gateway can correctly identify which VMG transmits the uplink transmission reply message and transmit the uplink transmission reply message to which MGC.

For example, the TransactionReply message replied by VMG1 is as follows:

MEGACO/1[10.35.12.10]:2944

Reply＝6068{Context＝45{Add＝aaln/1,Add＝RTP/4044{Media{Local{

v＝0

c＝IN IP4 10.35.12.10

m＝audio 20176RTP/AVP 8

a＝ptime:20

}}}}}

s10, MGC1 sends a modified transaction request message to the physical media gateway, and the IP of the message is IP1:10.35.12.10. For example, the TransactionRequest message content is as follows:

！/1[10.35.12.1]:2944

T＝6070{C＝45{MF＝aaln/1{SG{cg/rt}},MF＝RTP/4044{M{O{MO＝SR},R{

v＝0

c＝IN IP4 10.20.20.102

m＝audio 30240RTP/AVP 8

a＝ptime:20

}}}}}

s11, repeating the step S7, obtaining a VMG1 association hash table according to the attribution of the modified transaction request message, reading the association hash table of the VMG1 by taking an association descriptor (association ID=45) specified by the modified transaction request message as a key word, obtaining the topology between a physical termination point aaln/1 and a media termination point RTP1 in a matching table item, and updating.

S12, after VMG1 finishes processing the modified Transaction request message and completes the TransactionReply message group package, replying the TransactionReply message to the corresponding MGC1, and deleting the entry corresponding to the transactionID=6070 in the Receiver Transaction hash table. For example, the TransactionReply message replied by VMG1 is as follows:

！/1[10.35.12.10]:2944

Reply＝6070{Context＝45{Add＝aaln/1,

Add＝RTP/4044{Media{Local{

v＝0

c＝IN IP4 10.35.12.10

m＝audio 20176RTP/AVP 8

a＝ptime:20

}}}}}

s13, when the user aaln/1 hangs up, repeating the step S4, then sending a Notify transaction request message to the corresponding MGC1 through a Socket1 (970) of the VMG1, reporting the hang-up event of the user, and starting a retransmission timer, for example, reporting the hang-up event message as follows:

MEGACO/1[10.35.12.10]:2944

Transaction＝129{

Context＝45{

Notify＝aaln/1{ObservedEvents＝2024{20110921T09243507:al/on{init＝False}}}

}}

s14, MGC1 sends a sub transaction request message to the physical media gateway to release the resources of the media gateway, wherein the destination IP of the message is IP1:10.35.12.10, for example, the contents of a transactionRequest message are as follows:

！/1[10.35.12.1]:2944

T＝6085{C＝45{S＝aaln/1,S＝RTP/4044}}

s15, repeating the step S7, obtaining a VMG1 association hash table according to attribution of the sub transaction request message, reading the association hash table of the VMG1 by taking an association descriptor (association ID=45) specified by the sub transaction request message as a key word, deleting topology between a physical termination point aaln/1 and a physical termination point RTP1 in the matched table entry, and deleting the table entry corresponding to the association ID=45 from the VMG1 association table.

S16, after VMG1 completes processing the sub Transaction request message and completes the TransactionReply message group package, replying the TransactionReply message to the corresponding MGC1, and then deleting the entry corresponding to the transactionID=6085 in the Receiver Transaction hash table.

For example, the TransactionReply message replied by VMG1 is as follows:

MEGACO/1[10.35.12.10]:2944

Reply＝6085{Context＝45{

Subtract＝aaln/1{Statistics{amet/cpc＝0,amet/pcslr＝0}},

Subtract＝RTP/4044{Statistics{nt/or＝1280,nt/os＝60168,rtp/delay＝2,rtp/jit＝0,rtp/pl＝0,rtp/pr＝8,rtp/ps＝384}

}}}

through steps S8, S11, and S15 in the above embodiments, the physical media gateway can correctly identify which VMG the received transaction request acts on, and which logical entities (association and termination points) in the VMG.

The foregoing is illustrative of the present invention and is not to be construed as limiting thereof, but rather as providing for the use of additional embodiments and advantages of all such modifications, equivalents, improvements and similar to the present invention are intended to be included within the scope of the present invention as defined by the appended claims.

Claims

1. A method for identifying virtual media gateways, a plurality of virtual media gateways VMGs being created in a physical media gateway, the method comprising:

2. The method for identifying virtual media gateway according to claim 1, wherein voice POTS ports of PON access devices are statically divided according to requirements, each POTS port corresponds to a physical termination point, voice POTS ports are assigned to VMGs identified by VMG IDs by configuring a binary group of physical termination node IDs and VMG IDs, and physical media gateway monitors sockets of all VMGs by a polling mechanism.

3. The method for identifying a virtual media gateway according to claim 1, wherein the identifying the uplink transaction request message according to the physical endpoint ID and VMG ID tuple comprises: and identifying the VMG to which the uplink transaction request message belongs, namely a sender of the uplink transaction request message, according to the binary group information of the physical terminal node ID and the VMG ID, and obtaining the MGC corresponding to the VMG, namely a receiver of the uplink transaction request message, according to the configuration.

4. The method for identifying a virtual media gateway as recited in claim 1, wherein,

each VMG creates a Sender transaction hash table and stores a transaction request message sent by the VMG, the VMG to which the message belongs and corresponding MGC information;

5. The method for identifying a virtual media gateway as claimed in claim 4, wherein after the identifying the uplink transaction request message according to the physical endpoint ID and VMG ID tuple, the method further comprises the step of sending the uplink transaction request message:

6. The method for identifying a virtual media gateway as recited in claim 5, wherein the method further comprises the step of the physical media gateway identifying the MGC to send to the VMG response message:

7. The method for identifying virtual media gateway as recited in claim 4, wherein each VMG is configured with an MGC to create a Receiver transaction hash table, and store transaction request messages received by the VMG, the VMG to which the messages belong, and corresponding MGC information;

8. The method for identifying a virtual media gateway according to claim 7, further comprising, after identifying the downstream service request message:

9. The method for identifying a virtual media gateway according to claim 8, wherein after identifying the downstream transaction request message, further comprises:

10. An apparatus for identifying a virtual media gateway, comprising: