WO2007128190A1 - A method of making conference bridge context and call leg context incident and corresponding media gateway and system - Google Patents

Abstract

A method of making conference bridge context and call leg context incident, and corresponding to media gateway and system. In the conference bridge context and the call leg context, which are to be made incident, establishing a virtual (logical) termination separately, and by the characteristic information of conference bridge channel making what said virtual terminations with the same conference bridge channel incident.

Description

 Method, device and system for associating ^^ bridge context and calling leg context The present application claims to be submitted to the Chinese Patent Office on April 29, 2006, with the application number of 200610078058. 3, the invention name is "an associated conference bridge context" The priority of the Chinese Patent Application, which is incorporated herein by reference.

Technical equipment

 The present invention relates to the field of communications, and in particular, to a method, device and system for associating a conference bridge context and a call leg (Cal L Leg ) context.

Background technique

 The H.248 protocol was improved on the basis of the earlier Media Gateway Control Protocol (MGCP). The H.248 protocol is a gateway control protocol for connecting a media gateway (MGW) to a media gateway controller (MGC), and is applied between a media gateway and a media gateway controller and between a media gateway controller and an H.248 terminal. It is an important protocol that the Media Gateway Controller should support. The connection model defined by the H.248 protocol includes two main concepts: Terminator and Context. An endpoint is a logical entity in a media gateway that can send and receive one or more media. Endpoints can represent time division multiplexing (TDM) channels, analog telephone lines, and Real Time Transport Protocol (RTP) streams. Endpoint types mainly have semi-permanent endpoints (such as TDM channels or analog telephone lines) and temporary endpoints (such as RTP streams for carrying voice, data and video signals or various mixed signals). The attributes are represented by attributes, events, signals, and statistics, and the concept of a package is introduced in the protocol to combine various characteristic parameters of the endpoint into a package. At any time, an endpoint belongs to and can only belong to a context. A context is an association between endpoints. It describes the topology relationship between endpoints and the parameters of media mixing/swapping. It can be created with the ADD command, using Subtract or Move. The command is deleted.

In the process of implementing the present invention, the inventor has found that the third-generation partner's independent bearer circuit-switched core network (3GPP TS 23.205) protocol defines an option for implementing multi-party call and conference-type services according to a separate context, and the basic idea is : On the conference bridge resource gateway (corresponding to the aforementioned media gateway), place the conference bridge in a context, and each Ca ll Leg endpoint is placed in a different context; then the conference bridge context and Cal l Leg contexts are associated. By abstracting the Cal l Leg and the conference bridge independently, the separation of contexts brings flexibility and, to some extent, simplifies implementation, such as listening and playback can be done in the context of Cal l Leg, thus eliminating the need for conferences. Complex topology operations in the bridge context. However, this kind of conference bridge context and Cal l Leg The association of the text requires a specific implementation, and the agreement is not provided, and the prior art does not provide a related solution.

Summary of the invention

 An object of the embodiments of the present invention is to provide a method for associating a conference bridge context with a Cal l Leg context, a method for associating two contexts, an implementation device and a system, and providing a realistic and feasible association for separating a contextual multiparty call or conference. Program.

 An embodiment of the present invention provides a method for associating a conference bridge context and a call leg context, where the method includes: creating a virtual endpoint in a conference bridge context and a call leg Cal l Leg context to be associated, and The endpoints are associated with the same conference bridge channel through the feature information of the conference bridge channel.

 An embodiment of the present invention further provides a method for associating two contexts, where the method includes: creating a virtual endpoint in a first context and a second context that need to be associated, and passing the two virtual endpoints through the same physical entity. The feature information is associated.

 The embodiment of the present invention further provides a media gateway that implements association between two contexts, where the media gateway includes: a virtual endpoint creation unit, configured to respectively create a virtual endpoint in a first context and a second context that need to be associated; And an allocating unit, configured to associate the two virtual endpoints with feature information of the same physical entity.

 The embodiment of the present invention further provides a system for implementing association between two contexts, where the system includes a media gateway controller MGC and a media gateway MGW controlled by the MGC, and the media gateway specifically includes: a virtual endpoint creation unit, Creating a virtual endpoint respectively in a first context and a second context that need to be associated; a physical entity allocation unit to associate the two virtual endpoints with feature information of the same physical entity.

 It can be seen from the above embodiments of the present invention that a virtual endpoint is created in two contexts to be associated, and the two virtual endpoints are associated with the feature information of the same physical entity, and two contexts are provided. The specific implementation schemes associated with each other provide a practical means of implementation for separating contextual multiparty calls or conferences.

DRAWINGS

1 is a schematic diagram of a multi-party call using the method of the associated conference bridge context and the Cal l Leg context of the present invention; 2 is a flow chart of a first embodiment of a method for associating a conference bridge context and a Cal l Leg context by using the A side of FIG. 1;

 3 is a schematic diagram of a method for applying a conference bridge context and a Cal l Leg context according to the present invention.

 4 is a flowchart of an associated conference bridge context and a Cal 1 Leg context in the case of A in FIG. 3;

 FIG. 5 is a schematic structural diagram of a first embodiment of a media gateway for implementing two contexts according to the present invention; FIG. 6 is a schematic structural diagram of a second embodiment of a media gateway for implementing two contexts according to the present invention. detailed description

 The embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

 In the embodiment of the present invention, a virtual endpoint is separately created in the conference bridge context and the Cal 1 Leg context that need to be associated, and the two virtual endpoints are associated with the same conference bridge channel through the same conference bridge channel feature information, thereby Achieve the purpose of the associated conference bridge context and Ca 11 Leg context.

 An H.248 extension package can be predefined, and the feature information of the conference bridge channel for associating the two virtual endpoints is carried by the attributes of the extension package and passed between the two virtual endpoints. The feature information of the conference bridge channel includes but is not limited to the conference bridge channel identifier or the TDM slot number of the conference bridge channel. It will be readily understood by those skilled in the art that the feature information of the conference bridge channel can also be arbitrarily selected as long as the conference bridge channel can be uniquely identified.

 Please refer to FIG. 1 , which is a schematic diagram of a multi-party call using the associated conference bridge context and the Cal l Leg context method of the present invention; and FIG. 2 is an associated conference bridge context using the A side of FIG. 1 as an example. Method of the first embodiment flow chart of the Ca 11 Leg context. In this embodiment, the feature information of the conference bridge channel is carried by the attributes of the predefined H.248 extension package and passed between the two virtual endpoints.

 The identifier of the defined H.248 extension is sc_mpty and its attribute is identified as

As scCtr l lnfo, this attribute is used to carry the feature information of the conference bridge channel. The attribute is defined as a way to be transparent to the MGC, that is, the attribute value is selected as needed. And the MGC only needs to transparently transmit between the two virtual endpoints, and the specific content and meaning are interpreted by the MGW according to the attribute value. When the attribute value is CHOOSE (select), the MGW selects an available conference bridge channel to assign to the virtual endpoint; the attribute value is the conference bridge channel. When the information is collected, the MGW selects a conference bridge channel corresponding to the feature information and assigns it to the virtual endpoint. The following is an example of a participant in a multi-party call, the A party (other parties are similar), which illustrates the steps of the Call Leg context and the conference bridge context associated with the A party:

 Step 210: The MGC sends a request message ADD request to the MGW, and the request message carries the H.248 extension package sc-mpty, and the AsscCtrllnfo value of the sc_mpty value is CH00SE.

 The specific meaning of this step is that the MGC sends the request message to notify the MGW to create a virtual endpoint in the conference bridge context. When the AsscCtrllnfo value of the sc-mpty is CHOOSE, the MGW selects an available conference bridge channel to assign to the virtual endpoint. And update the AsscCtrllnfo value of sc_mpty.

 Step 220: The MGW creates a virtual endpoint added to the conference bridge context, assigns a temporary endpoint identifier to it, selects an available conference bridge channel to assign to the virtual endpoint according to the Sc_mpty AsscCtrllnfo value CHOOSE, and features the conference bridge channel. The information is assigned to AsscCtrllnfo of sc_tnpty, and then the response message ADD reply with the endpoint identifier and the H.248 extension packet sc_mpty is sent to the MGC.

 Assuming that the conference bridge channel selected by the MGW is Channel 1, then Channel 1 becomes the common physical entity corresponding to the Call Leg context and the conference bridge context of the associated A party. The feature information of the channel 1 is selected by the MGW. For example, the feature information of the selected conference bridge channel is "xxxx", and the feature information value can be used to globally uniquely identify the channel 1, and the assigned temporary endpoint identifier is T1, which is used to The virtual endpoint is identified.

 Step 230: The MGC sends a request message ADD request to the MGW, and the request message carries the H.248 extension packet sc_mpty, and the AsscCtrllnfo value of the sc-mpty value is the feature information "XXXX" of the conference bridge channel selected by the MGW in step 220.

 The specific meaning of this step is that the MGC sends the request message to notify the MGW to create a virtual endpoint in the Call Leg context, and informs the MGW to select the corresponding conference bridge channel to assign to the virtual endpoint according to the AsscCtrllnfo value "xxxx" of the sc-mpty.

Step 240: The MGW creates a virtual endpoint and adds it to the Call Leg context, assigns a temporary endpoint identifier to it, and selects the corresponding conference bridge channel according to the sc-mpty AsscCtrllnfo value "xxxx" to assign the virtual endpoint, in other words, This virtual endpoint in the Call Leg context is associated with the conference bridge channel with feature information "xxxx", and a response message ADD reply with the endpoint identifier is sent to the MGC. Assume that the temporary endpoint identifier assigned by the MGW to the virtual endpoint created in the Ca l 1 Leg context is T2, T2 is used to identify the virtual endpoint, and the MGW selects the conference bridge channel according to the Sc-mpty As scCtr l lnfo value "xxxx". Channel 1, assign the conference bridge channel to the virtual endpoint. In the above steps, the MGC does not process the sc_mpty as scCtr l lnf o value; only in the Ca ll Leg context, the MGW needs to address Channel 1 according to this value.

 It should be noted that, although the above embodiment is to simplify the implementation, a virtual endpoint is first created in the conference bridge context, and then a virtual endpoint is created in the Ca l Leg context. However, in practical applications, it is allowed to create a virtual endpoint in the Cal l Leg context first, and then create a virtual endpoint in the conference bridge context, which is more complicated in implementation than the former. Because the virtual endpoint in the context of the Cal l Leg cannot be directly associated with a specific conference bridge channel when it is created, it must wait until the MGW selects an available conference bridge channel to be assigned to the virtual endpoint in the conference bridge context, and the conference bridge is used by the MGW. The feature information of the channel is sent to the MGC, and the MGC sends a command to the MGW to implement the association between the virtual endpoint in the Cal l Leg context and the conference bridge channel that meets the above feature information.

 In addition, all conference bridge channels can be configured in the MGW and the MGC in advance, and each conference bridge channel is assigned two endpoint identifiers (Terminating Id), which are used as the feature information of the conference bridge channel. This will be described in detail below in conjunction with Figures 3 and 4.

Please refer to FIG. 3 , which is a schematic diagram of a multi-party call using the associated conference bridge context and the Ca ll Leg context method of the present invention, and please refer to FIG. 4 , which is an associated conference bridge context exemplified by the A side in FIG. 3 . Flowchart of the second embodiment of the method of Cal 1 Leg context. In this embodiment, all the conference bridge channels are configured in advance in the MGW and the MGC, and each conference bridge channel is assigned two endpoint identifiers, and the two endpoint identifiers are used as the feature information of the conference bridge channel. After the configuration, the two endpoint identifiers can uniquely identify and address the corresponding conference bridge channel in the MGW. The configurations in the MGC and the MGW must be the same. The final effect of the configuration is that the MGC must know the MGWs it manages. Which have the conference bridge channel resources and what is the pair of endpoint identifiers for each conference bridge channel. The process of feature information transfer is a process in which the MGC sends the two endpoint identifiers corresponding to the same conference bridge channel in the conference bridge context and the Ca ll Leg context of the MGW. The MGC sends a request message carrying the conference bridge channel endpoint identifier to the MGW, and the MGW creates two virtual endpoints according to this, and adds the two virtual endpoints respectively to the conference bridge context and the Ca ll leg context, and according to the endpoint identifier of the virtual endpoint Assign the corresponding conference bridge channel to the virtual endpoint. In this embodiment, two endpoint identifiers are configured for Channel 1 in the MGC and the MGW: T1 and T2. The following is an example of the participant of the multiparty party, which is similar to the other party, and illustrates the Cal l Leg context of the party A. Steps for conference bridge context association:

 Step 410: The MGC sends a request message ADD reques t to the MGW, where the request message carries the endpoint identifier T1.

 The specific meaning of this step is that the MGC sends the request to notify the MGW to add a virtual endpoint with the endpoint identifier T1 in the conference bridge context, and the MGW addresses the conference bridge channel Channel 1 according to the endpoint identifier and the saved configuration information, Channel 1 It becomes the physical entity corresponding to the conference bridge context and the Cal l Leg context where the associated A party is located.

 Step 420: The MGW creates a virtual endpoint with the endpoint identifier T1 added to the conference bridge context, assigns the conference bridge channel Channel 1 to the virtual endpoint according to the endpoint identifier T1, and sends a response message ADD reply with the endpoint identifier T1. To the MGC;

 Step 430: The MGC sends a request message ADD reques t to the MGW, and the request message carries the endpoint identifier T2.

 The specific meaning of this step is that the MGC sends the request to notify the MGW to add a virtual endpoint with the endpoint identifier T2 in the context of the Cal l Leg, and the MGW addresses the conference bridge channel Channel 1 according to the endpoint identifier T2 and the saved configuration information. .

 Step 440: The MGW creates an endpoint identifier for adding the T2 virtual endpoint to the Cal 1 Leg context, assigns the conference bridge channel Channel 1 to the virtual endpoint according to the endpoint identifier T2, and sends a response message ADD reply with the endpoint identifier T2 to MGC.

 It will be readily understood by those skilled in the art that in the above steps, a virtual endpoint may also be created in the context of the Cal l Leg, and then a virtual endpoint is created in the context of the conference bridge, wherein the delivery process of the feature information is similar.

 A person skilled in the art may understand that all or part of the steps in implementing the above method embodiments may be completed by a program instructing related hardware, and the program may be stored in a computer readable storage medium, the storage medium Such as: ROM / RAM, disk, CD, etc.

Both embodiments of the invention are simple and straightforward. In contrast, the first embodiment is more flexible, more scalable, and less manual intervention, while the second embodiment does not need to define an H.248 extension package, but requires more configuration work on the MGW and the MGC. Both of the embodiments directly use the virtual endpoint to abstract the conference bridge channel resources without occupying the actual bearer port resources. On the other hand, if the six endpoints T1-T6 in FIG. 1 or 2 adopt the real bearer endpoint, it is necessary to occupy the corresponding bearer port resources, and also involves the problem of bearer interworking in the MGW, which is difficult to implement. In addition, the manner in which the actual bearer port resources are occupied also has difficulties in handling certain problems, such as playing a conference. Many conference mixing algorithms use the maximum sound synthesis algorithm, which is usually handled specially for playback. That is, when playing a conference, the voices of other participants will be suppressed to a certain extent to highlight the content being played. When a multi-party call is implemented according to the separate context, in order to take advantage of the flexibility of the separate context, the playback request should be delivered to the Cal l Leg context, and if the Cal l Leg context and the conference bridge context are interoperable through the actual bearer port resources. , when the content played in the Ca 11 Leg context is passed to the conference bridge context, the conference bridge context cannot distinguish it from the speech from the Cal l Leg context, so that special processing during mixing cannot be achieved, and the content is played in extreme cases. It will be overwritten by the louder party voice. However, the method of the present invention does not have this problem, because the method of the present invention can directly extend the conference channel into the Cal l Leg context, and the conference channel playback can be differentiated in the context of the Ca ll Leg.

 Referring to FIG. 5, it is a schematic structural diagram of a first embodiment of a media gateway implementing two contexts. The media gateway of this embodiment includes a virtual endpoint creation unit 50 for creating a virtual endpoint in a first context and a second context that need to be associated, and a feature information for using the two virtual endpoints to pass the same physical entity. A physical entity allocation unit 51. The following describes the internal structure of the media gateway in combination with its specific working principle.

 Specifically, the virtual endpoint creation unit 50 includes a first creation subunit 501 and a second creation subunit 502, and the physical entity assignment unit 51 includes a first assignment subunit 511 and a second assignment subunit 512. First, the first creation sub-unit 501 creates a first virtual endpoint in the first context according to the first indication information of the MGC; then, the first allocation sub-unit 511 allocates the first physical entity that is available to the first virtual endpoint. And feeding back the feature information of the first physical entity to the MGC.

Then, the second creation sub-unit creates a second virtual endpoint in the second context according to the second indication information of the MGC, where the second indication information includes the first physical entity feature information. Further, the second allocation sub-unit 512 further allocates the first physical entity to the second virtual endpoint according to the first physical entity feature information in the second indication information. At this point, due to the first virtual endpoint and the second virtual The endpoints are assigned the same physical entity (such as the same conference bridge channel), so the two endpoints are associated, that is, the first context (such as the conference bridge context) and the second context (such as the call leg context) are associated. .

 Please refer to FIG. 6, which is a schematic structural diagram of a second embodiment of a media gateway implementing two contexts. The media gateway of this embodiment includes a virtual endpoint creation unit 60 for creating a virtual endpoint in the first context and the second context that need to be associated, respectively, to save a pair of endpoint identifiers and physical entities for each physical entity. Correspondence relationship storage unit 63 of the correspondence relationship, and physical entity allocation unit 61 for associating the virtual endpoint created by the virtual endpoint creation unit 60 with the feature information of the same physical entity according to the correspondence relationship provided by the correspondence relationship storage unit . In this embodiment, the feature information of the physical entity is a corresponding pair of endpoint identifiers. Specifically, the feature information of the first physical entity is a first endpoint identifier and a second endpoint identifier. The internal structure of the media gateway is further introduced below in conjunction with its specific working principle.

Specifically, the virtual endpoint creation unit 60 includes a first creation subunit 601 and a second creation subunit 60 ² , and the physical entity allocation unit 61 includes a first allocation subunit 611 and a second allocation subunit 61. First, created by the first The sub-unit 601 creates a first virtual endpoint in the first context according to the first endpoint identifier indicated by the MGC; then, the correspondence relationship provided by the first assignment sub-unit 611 according to the correspondence relationship storage unit 63 (the first endpoint identifier, the first The correspondence between the two endpoint identifiers and the first physical entity is to allocate the corresponding first physical entity to the first virtual endpoint.

 Then, the second creation sub-unit 602 creates a second virtual endpoint in the second context according to the second endpoint identifier indicated by the MGC; and further, the correspondence relationship provided by the second association sub-unit 612 according to the correspondence relationship storage unit 63. An endpoint identifier, a correspondence between the second endpoint identifier and the first physical entity, and a corresponding first physical entity is allocated to the second virtual endpoint. So far, since the first virtual endpoint and the second virtual endpoint are assigned the same physical entity (such as the same conference bridge channel), the two endpoints are associated, that is, the first context (such as the conference bridge context) and The second context (such as the call leg context) is associated.

 In addition, the present invention also discloses a system for implementing association between two contexts, the system comprising a media gateway controller MGC and a media gateway MGW controlled by the MGC, the media gateway may have specific ones in the above two embodiments structure.

As can be seen from the above various embodiments, when two different contexts need to be associated, By assigning a virtual endpoint to each of them, and then associating the two virtual endpoints with the feature information of the same physical entity, the purpose of associating the contexts of the two virtual endpoints is achieved.

 This scheme provides a specific implementation scheme for associating the two contexts. Moreover, since the virtual endpoint is used instead of the real bearer endpoint, the corresponding bearer port resources are not required to be occupied, and thus less involved in the MGW. The problem of carrying interoperability is therefore simple to implement. It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to be limiting, and those skilled in the art should understand that the technical solutions of the present invention may be modified or equivalently substituted without departing from the technical solutions of the present invention. The spirit of the scope should be covered by the scope of the claims of the present invention.

Claims

Rights request  A method of associating a conference bridge context and a call leg context, the method comprising:  A virtual endpoint is created in the context of the conference bridge context and the call leg that need to be associated, and the virtual endpoint is associated with the same conference bridge channel through the feature information of the conference bridge channel.  The method according to claim 1, wherein the method further comprises: pre-defining an H.248 extension package, and the attribute value of the extension package is a CHOOSE or conference bridge channel specific conference bridge channel feature information. Identifying that the conference bridge channel corresponding to the feature information is assigned to the virtual endpoint;  The specific process of creating a virtual endpoint in the context of the conference bridge context and the call leg that needs to be associated, and associating the two virtual endpoints with the same conference bridge channel feature information and the same conference bridge channel includes:  The media gateway controller MGC sends an add request ADD reques t message to the media gateway MGW, the request message carries an H.248 extension package, and the attribute value of the extension package is CHOOSE;  The MGW creates a virtual endpoint and adds it to the conference bridge context. According to the attribute value CHOOSE of the H.248 extension package, an available conference bridge channel is assigned to the virtual endpoint, and the feature information of the conference bridge channel is assigned to: Attribute, send the response message ADD reply with the H.248 extension package to the MGC;  The MGC sends a request message ADD reques t to the MGW, where the request message carries an H.248 extension packet, and the attribute value of the extension packet is the feature information of the conference bridge channel selected by the MGW.  The MGW creates a virtual endpoint and adds it to the Cal l Le context, and selects a corresponding conference bridge channel to allocate to the virtual endpoint according to the conference bridge channel feature information in the H.248 extension package attribute value.  The method according to claim 1, wherein the method further comprises: assigning two endpoint identifiers to each conference bridge channel in advance, and storing a correspondence between the endpoint identifiers and the conference bridge channels; The feature information of the conference bridge channel is two endpoint identifiers corresponding to the same conference bridge channel; the virtual conference is respectively created in the context of the conference bridge context and the call leg that need to be associated The specific process of associating the two virtual endpoints with the same conference bridge channel feature information and the same conference bridge channel includes:  The MGC sends two request messages, ADD reques t, to the MGW, which respectively carry an endpoint identifier of an available conference bridge channel;  The MGW creates two virtual endpoints to be added to the conference bridge context and the Cal l leg context respectively, and allocates a corresponding conference bridge channel to the virtual endpoint according to the endpoint identifier carried in the request message.  4. A method of associating two contexts, the method comprising:  A virtual endpoint is separately created in the first context and the second context that need to be associated, and the two virtual endpoints are associated by feature information of the same physical entity.  The method according to claim 4, wherein the specific process of creating two virtual endpoints and associating with feature information of the same physical entity includes:  The MGW creates a first virtual endpoint in the first context according to the first indication information of the MGC, and allocates the first physical entity that is available to the first virtual endpoint;  The MGW feeds back the feature information of the first physical entity to the MGC;  The MGW creates a second virtual endpoint in the second context according to the second indication information of the MGC, and allocates the first physical entity to the second virtual endpoint according to the first physical entity feature information in the second indication information.  The method according to claim 5, wherein the first indication information and the second indication information both comprise a predefined H.248 extension package, and the attribute value of the extension package is selected. CHOOSE or characteristic information of the physical entity.  The method according to claim 4, wherein the physical entity is specifically a conference bridge channel, and the feature information of the conference bridge channel is a conference bridge channel identifier or a time division multiplexing time slot number of the conference bridge channel.  The method according to claim 4, wherein the method further comprises: storing a correspondence between a pair of endpoint identifiers allocated to each physical entity and the physical entity, the characteristics of the physical entity The information is a pair of corresponding endpoint identifiers; The specific process of creating two virtual endpoints and associating with feature information of the same physical entity includes: The MGW creates a first virtual endpoint in the first context according to the first endpoint identifier indicated by the MGC, and allocates a corresponding first physical entity to the first virtual endpoint according to the first endpoint identifier;  The MG is configured to create a virtual endpoint in the second context according to the second endpoint identifier indicated by the MGC, and allocate a corresponding first physical entity to the first virtual endpoint according to the second endpoint identifier, where the second endpoint identifier is An endpoint is identified as characteristic information of a physical entity.  The method according to any one of claims 4 to 8, wherein the first context is specifically a conference bridge context, the second context is specifically a call leg context, and the physical entity is specifically a conference Bridge channel.  10. A media gateway implementing two contexts, wherein the media gateway comprises:  a virtual endpoint creation unit, configured to respectively create a virtual endpoint in the first context and the second context that need to be associated;  a physical entity allocation unit, configured to associate the two virtual endpoints with feature information of the same physical entity.  The media gateway according to claim 10, wherein the virtual endpoint creation unit comprises a first creation subunit and a second creation subunit, and the physical entity allocation unit comprises a first allocation subunit. And a second allocation subunit,  The first creating subunit is configured to create a first virtual endpoint in the first context according to the first indication information of the MGC; the first assigning subunit is configured to allocate the available first physical entity to the first virtual endpoint Feeding back, to the MGC, feature information of the first physical entity;  The second creating subunit is configured to create a second virtual endpoint in the second context according to the second indication information of the MGC, where the second assigning subunit is configured to use, according to the first physical entity feature information in the second indication information, The second virtual endpoint allocates a first physical entity.  The media gateway according to claim 10, wherein the media gateway further comprises a correspondence relationship storage unit, configured to store a correspondence between the pair of endpoint identifiers and the physical entity in advance for each physical entity. The characteristic information of the physical entity is a pair of corresponding endpoint identifiers thereof; The virtual endpoint creation unit specifically includes a first creation subunit and a second creation subunit, where the physical entity allocation unit specifically includes a first allocation subunit and a second allocation subunit. The first creating subunit is configured to create a first virtual endpoint in the first context according to the first endpoint identifier indicated by the MGC; the first assigning subunit is configured to use, according to the correspondence relationship provided by the corresponding relationship storage unit, Assigning, by the first virtual endpoint, a corresponding first physical entity;  The second creating subunit is configured to create a second virtual endpoint in the second context according to the second endpoint identifier indicated by the MGC; the second assigning subunit is configured to use the corresponding relationship storage unit as the second virtual The endpoint allocates a corresponding first physical entity, and the second endpoint identifier and the first endpoint identifier are feature information of the first physical entity.  The media gateway according to any one of claims 10 to 12, wherein the first context is specifically a conference bridge context, and the second context is specifically a call leg context, and the physical entity is specifically Conference bridge channel.  A system for implementing association between two contexts, the system comprising a media gateway controller MGC and a media gateway MGW controlled by the MGC, wherein the media gateway specifically includes: a virtual endpoint creation unit, configured to: Creating a virtual endpoint in the first context and the second context that need to be associated;  a physical entity allocation unit, configured to associate the two virtual endpoints with feature information of the same physical entity.  The system according to claim 14, wherein the virtual endpoint creation unit specifically includes a first creation subunit and a second creation subunit, and the physical entity allocation unit specifically includes a first allocation subunit and a Second allocation subunit,  The first creating subunit is configured to create a first virtual endpoint in the first context according to the first indication information of the MGC; the first assigning subunit is configured to allocate the first physical entity that is available to the first virtual endpoint Feeding back, to the MGC, feature information of the first physical entity;  The second creating subunit is configured to create a second virtual endpoint in the second context according to the second indication information of the MGC, where the second assigning subunit is configured to use, according to the first physical entity feature information in the second indication information, The second virtual endpoint allocates a first physical entity. The system according to claim 14, wherein the media gateway further includes a correspondence relationship storage unit, configured to store a correspondence between a pair of endpoint identifiers and the physical entity in advance for each physical entity. The feature information of the physical entity is a pair of corresponding endpoint identifiers. The virtual endpoint creation unit specifically includes a first created subunit and a second created subunit. The physical entity allocation unit specifically includes a first allocation subunit and a second allocation subunit.  The first creating subunit is configured to create a first virtual endpoint in the first context according to the first endpoint identifier indicated by the MGC; the first assigning subunit is configured to use, according to the correspondence relationship provided by the corresponding relationship storage unit, Assigning, by the first virtual endpoint, a corresponding first physical entity;  The second creating subunit is configured to create a second virtual endpoint in the second context according to the second endpoint identifier indicated by the MGC; the second assigning subunit is configured to allocate the second virtual endpoint according to the corresponding relationship storage unit Corresponding first physical entity, the second endpoint identifier and the first endpoint identifier are feature information of the first physical entity.