WO2009024072A1

WO2009024072A1 - Method, system and apparatus for carrying out communication calling and releasing

Info

Publication number: WO2009024072A1
Application number: PCT/CN2008/072021
Authority: WO
Inventors: Jian Zhang; Xiaoqin Duan; Xiaobo Wu; Qingyu Li
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2007-08-19
Filing date: 2008-08-18
Publication date: 2009-02-26
Also published as: CN101370171B; CN101370171A

Abstract

A method for carrying out communication calling includes receiving the calling message from a user terminal; controlling the establishment of the media plane association between the evolution media gateway EMGW and the user terminal according to the calling message; controlling the establishment of the bearer between the user terminal and the packet switching domain gateway, where the bearer transmitting the analog circuit domain service data of the user terminal in the packet switching domain. And a releasing method, a user device, a packet switching control plane entity, a control entity at network side and a system for carrying out communication calling. When the terminal accesses the PS domain, it may call the CS domain in the PS domain or the opposite terminal in the fixed network, which enables the UMTS evolution network to be backward compatible with the current CS domain.

Description

Method, system and device for realizing communication call and release

This application claims priority to Chinese Patent Application No. 200710141458.9, entitled "Method and System for Realizing Communication Call and Release", filed on August 19, 2007, the entire contents of which are incorporated by reference. In this application.

Technical field

The present invention relates to the field of calls, and more particularly to a method and system and apparatus for implementing a communication call and release. Background technique

With the development of mobile communication technology, The 3rd Generation Partnership Project (The 3rd Generation

The Partnership Project, 3GPP) system needs to process the rapid growth of business data. In order to enhance the ability of 3GPP systems to handle rapidly growing Internet Protocol (IP) data services between networks, it is necessary to enhance the application of packet technology in 3GPP systems. That is, the packet technology in the 3GPP system is evolved, and the 3GPP system in the evolution process is called an evolved network.

The backward compatibility of the evolved network for the existing network is an important indicator in the evolution process. In order to protect the investment of the existing operator and make greater use of the entities of the existing circuit domain, an evolutionary network is proposed. Bearer in the Packet Switching (PS) domain ( Circuit

The data and signaling scheme of the Switching, CS) domain, with the proposal of the scheme, how to implement the terminal call in the analog circuit domain on the PS domain and release the call from the network side becomes an urgent problem to be solved. Summary of the invention

Embodiments of the present invention provide a method, system, and apparatus for implementing a communication call and release, so that users in the PS domain can call any CS domain or a user in a fixed network, thereby improving backward compatibility of the evolved network and protecting existing operations. Business investment.

An embodiment of the present invention provides a method for implementing a communication call, where the method includes:

Receiving a call message from the terminal;

Controlling, according to the call message, establishing a media plane association between the evolved media gateway EMGW and the terminal;

And controlling to establish a bearer between the terminal and the packet domain gateway according to the call message, where the loading is used to transmit analog circuit domain service data of the terminal in a packet domain.

The embodiment of the present invention further provides a method for releasing a communication call, the method comprising: after receiving a session release message from a peer, sending a message of a circuit domain release session to the terminal; And ending the media plane association between the EMGW and the terminal according to the message of releasing the session; releasing the bearer between the packet domain gateway and the terminal according to the message of releasing the session.

The embodiment of the invention further provides a user equipment, including:

a transmission unit, configured to perform message interaction with the packet domain control plane entity;

The encapsulating unit is configured to send the signaling to the transmission unit after the network non-access stratum message is sent, where the network non-access stratum message carries indication information, where the indication information is used by the packet domain control plane entity Determining whether the network non-access stratum message is sent to the network side call control entity;

And a decapsulation unit, configured to decapsulate the corresponding signaling from the message from the transmission unit and provide a peer-to-peer protocol layer entity at a transmission level between the terminal and the network side call control entity.

The embodiment of the invention further provides a packet domain control plane entity, including:

a receiving unit, configured to receive a message from the user equipment or the network side call control entity; the determining unit, configured to determine whether the message from the user equipment needs to be transparently transmitted to the network side call control entity, and whether the message from the network side call control entity needs to be Transparent transmission to the user equipment; generate control instructions if needed;

And a sending unit, configured to transparently transmit, by the network side call control entity, a message from the user equipment to the user equipment according to the control instruction.

The embodiment of the invention further provides a network side call control entity, including:

a receiving unit, configured to face the packet domain and the circuit domain, and receive the message of the circuit domain;

a control unit, configured to generate a control instruction according to the message of the circuit domain;

And a sending unit, configured to send corresponding data or signaling according to the control instruction.

The embodiment of the invention further provides a system for implementing a communication call, comprising:

a network side call control entity, configured to generate a control instruction for the packet domain and the circuit domain according to the message of the circuit domain;

An EMGW, configured to establish, according to the control instruction, a media plane association with the terminal, where the packet domain gateway is configured to establish, according to the control instruction, a bearer between the terminal and the terminal, where the bearer is used to transmit the terminal Analog circuit domain traffic data in a packet domain.

The method, the system and the device for implementing the communication call and the release provided by the embodiment of the present invention can call the CS domain or the peer end of the fixed network in the PS domain after the terminal (UE) accesses the PS domain, so that the UMTS The evolved network can be backward compatible with the existing CS domain. Most of the existing voice call operators' investments are on the CS domain call, thus protecting the existing operator's investment. The voice call in the CS domain to the PS domain. In the process of voice call transition, a method for implementing a call compatible with the CS domain and the PS domain is provided, so that the voice call of the CS domain smoothly transitions to the voice call of the PS domain.

DRAWINGS

1 is a schematic diagram of a network architecture A in an embodiment of the present invention;

2 is a schematic diagram of a network architecture B in an embodiment of the present invention;

3 is a schematic diagram of a network architecture C in an embodiment of the present invention;

4 is a flowchart of Embodiment 1 of a method for implementing a communication call according to the present invention;

FIG. 5 is a flowchart of Embodiment 2 of a method for implementing a communication call according to the present invention;

6 is a flowchart of Embodiment 3 of a method for implementing a communication call according to the present invention;

7 is a flowchart of Embodiment 4 of a method for implementing a communication call according to the present invention;

8 is a flowchart of Embodiment 5 of a method for implementing a communication call according to the present invention;

FIG. 9 is a flowchart of Embodiment 1 of a method for releasing a communication call according to the present invention;

FIG. 10 is a flowchart of Embodiment 2 of a method for releasing a communication call according to the present invention;

11 is a flowchart of Embodiment 3 of a method for releasing a communication call according to the present invention;

12 is a flowchart of Embodiment 4 of a method for releasing a communication call according to the present invention;

13 is a flowchart of Embodiment 5 of a method for releasing a communication call according to the present invention;

14 is a flowchart of Embodiment 6 of a method for releasing a communication call according to the present invention;

15 is a schematic structural diagram of an embodiment of a user equipment according to the present invention;

16 is a schematic structural diagram of an embodiment of a packet domain control plane entity according to the present invention;

17 is a schematic structural diagram of an embodiment of a network side call control entity according to the present invention;

FIG. 18 is a schematic structural diagram of a system embodiment for implementing a communication call according to the present invention.

detailed description

Referring to FIG. 1, FIG. 1 is an architecture A of an evolved network. In the architecture A, a network side call control entity is set to control a call. In the following embodiments, the network side call control entity may include an evolved system. Evolution Mobile-services Switching Centre (ECC), EMSC can include some functions of the Mobile-services Switching Centre (MSC) in the CS domain, IP Multimedia System (IP Multimedia) Subsystem, IMS) Part of the functions of the Media Gateway Control Function (MGCF) and the functions of the Application Server in the PS domain, EMSC and Policy and Charging Rules Function (PCRF) The Rx interface between the two is used to control the bearer of the PS domain, and the logical interface between the EMSC and the UE is used to simulate the signaling of the CS domain. The EMGW includes the functions of the IP Multimedia Media Gateway (IM-MGW) in the IMS. And the function of the Media Gateway (MGW) in the CS domain.

Referring to FIG. 2, FIG. 3 is an architecture B of an evolved network. The architecture B is different from the architecture A shown in FIG. 1 in that a packet domain control plane entity is set to forward signaling of a packet domain, in the following In an embodiment, the packet domain control plane entity may include an MME, and a Gs-like interface is introduced between the MME and the EMSC, and the interface is used for transmitting call related signaling, and is used for transmitting handover messages later for handover.

Referring to Figure 3, Figure 3 shows the architecture C of the evolved network. The architecture C is the same as the architecture shown in Figure 1. It is only the interface of the Policy and Charging Control (PCC) system in the architecture C. . A direct outbound interface between the EMSC and the packet domain gateway entity is used to control the packet domain bearer for establishing an analog circuit domain call. In the following embodiments, the packet domain gateway includes a PDN-GW. Under this architecture, an interface X between the EMSC and the PDN-GW is introduced, and the PDN-GW uses the interface to receive some control plane command messages of the EMSC.

In the above three architectures, the network side call control entity and the EMGW may be separate logical entities or the same logical entity.

Embodiment 1 A method for implementing a communication call, which is applied to simulate a CS domain call in a PS domain. In the architecture A shown in FIG. 1, the UE in the PS domain initiates a call to the CS domain or the opposite end of the fixed network. In this embodiment, the method for implementing the CS domain analog CS domain call is implemented, and the primary call flow is implemented through IP connectivity. .

After the UE is attached to the System Architecture Evolution (SAE) of the evolved network, a packet domain bearer that simulates CS domain registration, call, and the like is established;

The UE establishes a security association with the EMSC and registers with the EMSC. In order to ensure the validity and real-time of the security relationship, the EMSC/Visitor Location Register (VLR) will perform re-analysis of the analog circuit domain for the UE. After the authentication succeeds, the security association parameter of the UE in the circuit domain is saved in the EMSC/VLR, and the security association parameter may include an encryption calculation supported by the UE. Method, encryption key, etc., the security association parameter is used to simulate CS domain signaling data when switching in the PS domain and the CS domain, and the EMSC can notify the UE not to enable secure encryption of the simulated CS domain signaling data. If the parameters provided by the relevant Radio Network Controller (RNC) are required in the security association, the EMSC will generate the default parameters. During the registration process, the UE in the packet domain will provide the EMSC with the network side or wireless side capability of the relevant terminal. When a call occurs, the terminal also provides relevant capabilities to the EMSC, such as the parameters of classmark 2. These parameters will be used for subsequent switching.

Referring to Figure 4, the method includes:

The UE attaches to the network and performs registration of a simulated CS domain. During the registration process, some parameters of the terminal capabilities will be provided.

The terminal is ready to initiate a call. First, the service request message is encapsulated in the IP packet and transmitted to the EMSC according to the format of the intermediate layer protocol stack between the UE and the EMSC. The message carries parameters of the UE related capabilities. After receiving the message, the EMSC may initiate a CS domain re-authentication message to the UE; or trigger the EMSC to perform heavy security association negotiation on the data signaling carried by the UE on the packet domain. Or triggering security association negotiation between the EMGW and the UE for the transport layer media stream, such as renegotiating the UE and the EMSC in the IP-SEC and the SA between the UE and the EMGW.

The security association parameters are classified into the following three categories:

1) a security association at the transport level between the terminal and the EMSC, which is used to protect the security of the analog circuit domain between the terminal and the EMSC;

2) a security association at the transport level between the terminal and the EMGW, the association being used to protect the association between the terminal and the EMGW for transmitting media data streams at the transport level;

3) The analog circuit domain related security association parameter between the terminal and the EMSC, which is used for subsequent terminal handover to the circuit domain.

The circuit domain messages between the subsequent UE and the EMSC are transmitted through the IP layer between the UE and the EMSC in the format encapsulated above.

401. When the UE initiates a voice call, the EMSC receives the call setup of the UE. When the UE initiates a voice call, the Call Setup message is sent to the EMSC through a protocol (Internet Protocol, IP) connectivity between the networks. The destination address in the Call Setup message is the IP address of the EMSC. Because the media stream of the call is carried in the PS domain, the EMSC needs to know that the UE receives the address of the media plane and the listening port, and can negotiate the listening port of the UE in different ways:

The UE automatically subscribes to the listening port to the EMSC. For example, in the process of the terminal registering with the EMSC, the EMSC obtains the IP address and port of the terminal, and the terminal sends the signaling of the simulated CS domain registration to the EMSC through the IP address and the port, and the terminal will The IP address and the port are reported to the EMSC, and the reported IP address is used as the address of the terminal receiving the media plane. The terminal reserves the port of the receiving media according to the reported port. After receiving the reported port, the EMSC calculates the reserved port according to the same rule. The reserved port serves as the listening port of the terminal.

Or, when the terminal registers with the EMSC, the terminal actively reports the address of the receiving media plane and the listening port to the EMSC.

Alternatively, the terminal carries the address of the receiving media plane and the listening port in the call signaling.

Alternatively, the EMSC triggers the establishment of a dedicated bearer of the media plane through the PCC system, or the PDN-GW, and the data flow template (TFT) delivered by the PCRF or the PDN-GW carries the default terminal port number, and when the terminal receives the bearer setup, After the radio bearer (RB) message is found, the TFTs are found to carry the default parameters. Then, a real-time transport protocol (RTP) and a real-time transport control protocol (RTCP) are selected. The port number of the port is filled with the default parameter; the terminal responds to the RB message, and the message in the response carries the padded port number, and the message that the terminal responds finally returns to the EMSC, and the padded port serves as the listening port of the terminal.

Alternatively, the UE carries the information of the listening media plane in the non-access stratum message. Such as address, port number, etc., and sent to the EMSC through the packet domain control plane entity;

Or, the UE carries the information of the monitoring media plane in the middle layer that carries the call signaling above the IP layer. Such as address, port number, etc.

Because, in the process of the call, the voice data packet of the terminal will be encapsulated in the form of RTP. Therefore, the voice codec list supported by the terminal needs to be carried in the Call Setup message, and the format of the codec adopts an audio visual standard file (Profile of The format of the Audio Visual Profile, AVP Profile is reported. Or according to the voice codec format of the traditional circuit domain, after receiving the EMSC, the EMSC will map the codec of the traditional circuit domain into the codec of the packet domain according to a mapping relationship, and select an appropriate packet domain according to the selected condition. Decoding and notifying the UE, so that the terminal encapsulates the voice datagram in the packet domain, At the same time, the selected circuit domain codec is sent to the UE. Alternatively, the default codec can be used in the packet domain and the UE can be notified of the codec used in the circuit domain.

402. The EMSC responds to the call progress (Call Proceeding) message to the terminal.

403. The EMSO sends an initial address message (IAM) to the MSC in the CS domain according to the peer information in the call message, and the MSC feeds back the relevant parameters of the peer end to the EMSC according to the peer information in the IAM.

The EMGW includes two logical function modules IM-MGW and MGW. Correspondingly, the EMSC also includes two logical function modules Media Gateway Control Function (MGCF) and MSC; the CS domain service media stream is in the PS domain. On the upper bearer, the media plane data of the analog circuit domain service sent by the terminal on the packet domain will be sent to the IM-MGW module in the EMGW, IM-MGW

The MGW module may also establish an association with other MGWs in the CS domain. Here, an EMSC may be triggered to select the EMGW. After the MGCF in the EMSC selects the IM-MGW, the parameters of the IM-MGW are saved. The MSC in the EMSC uses the parameter to select the MGW to ensure that the selected MGW and the IM-MGW are in the same In the EMGW, the uniqueness of the MGW is guaranteed. The EMSC selects the EMGW according to the following conditions: based on user subscription data, network topology, device load, or operator policy, for example: the EMSC selects the EMGW that is contracted with the terminal or selects the EMGW with the smallest load.

In this step you need to choose an EMGW, which can be selected according to the following principles:

1) . EMSC entity ^ user subscription data selection EMGW;

2) The EMSC selects the EMGW according to the network topology and device load status;

3). Select EMGW according to the operator's strategy;

4) The EMSC queries the HSS for the user subscription data, and obtains the EMGW address when the user signs the contract from the user subscription data, and the EMSC corresponding to the EMGW address is the selected EMGW address;

5) The configuration data of the EMSC includes the address of the relevant EMGW;

6) The EMSC selects the EMGW from the EMGW pool according to relevant conditions (such as subscription data, operator preference, load, topology, etc.). This process may involve first selecting an EMGW pool and then selecting the EMGW from the pool;

7) The EMSC obtains the address of the EMGW from the call signaling from the peer entity, and the EMGW corresponding to the address of the EMGW is the EMGW selected by the network side call control entity.

404. The EMSC controls the EMGW to establish an association of the media stream. The media stream association includes media stream associations between the terminal and the EMGW at the IP level, such as the terminal needs to know the IP address of the EMGW, the port that monitors and controls the media stream (such as RTP, RTCP port), and the dual negotiation party. Speech codec. Vice versa, the EMGW also needs to have relevant parameters. In order to transmit the media stream association between the EMGW and the terminal, it is also necessary to establish a packet domain bearer for transmitting the IP layer media stream association between the terminal and the EMGW in the packet domain, and a bearer between the terminal and the packet domain gateway.

In addition, the EMGW and the EMSC can be one or separate logical entities.

The EMSC notifies the EMGW terminal of the IP address, the listening port number and the selected codec, or the EMSC notifies the EMGW terminal of the IP address, the listening port number and the default codec;

The EMSC establishes a media stream association of the EMGW to the terminal according to the address of the receiving media plane of the terminal and the listening port;

The bearer of the analog voice service is established by establishing a mode of the dedicated bearer in the evolved network; the process includes the following steps:

405-1. The EMSC pushes the newly defined service to the PCRF, where the message may include the address of the EMSC, such as the media stream rate, the codec used, the current service identifier, etc. Subsequent billing, etc.);

The PCRF generates related policies and QoS parameters according to the received service type, and the PCRF pushes down the relevant policies and QoS parameters to the PDN-GW. The label in the QoS parameters is used to distinguish the bearers of the analog circuit domain from the bearers of other PS domains. ;

405-2, the PCRF may also push the bearer setup request to the PDN-GW; the bearer setup request may include voice coding, an address of the EMSC, and the voice coding may include codec in the packet domain and codec in the circuit domain;

405-3. The PDN-GW determines the bearer QoS by using the received QoS policy value, and sends a bearer setup request to the Serving-GW. The message contains the codec of the voice, the special label defined, and the address of the EMSC. If the identifier of the circuit domain bearer cannot be defined by label, a different identifier is used to identify the bearer.

405-4. The serving gateway (Serving-GW) sends a bearer setup request to the MME, where the bearer setup request includes the above parameters. 405-5. The MME saves the address of the EMSC to the context for subsequent handover, and distinguishes the bearer of the service and the different PS domain bearer according to the label or the special identifier, so as to give the bearer high during subsequent handover. Priority to ensure priority when switching.

The MME establishes a session control parameter, and the MME sends a bearer setup request to the evolved base station (ENB), where the bearer setup request includes a session control parameter, and the session control parameter includes a voice codec used by the UE;

405-6. The ENB performs QoS mapping and saves relevant speech codecs to achieve better resource scheduling. Then, the UE sends a message to the UE, and the message carries the voice code (including the codec used in the circuit domain and/or the packet domain) required by the UE, and the UE responds to the radio bearer setup message.

405-7, the ENB responds to the bearer establishment message to the MME;

405-8, the MME responds to the bearer establishment message to the Serving-GW;

405-9, Serving - GW responds to the bearer setup message to the PDN-GW;

405-10. The PDN-GW responds to the bearer setup completion message to the PCRF, and reports the associated identifier of the current bearer, such as the bearer identifier, so that the PCRF performs the association between the bearer plane and the defined service plane.

In the process of establishing a dedicated bearer in steps 405-1 to 405-10 above:

The voice call parameters may be sent to the terminal, where the voice call parameters include the codec selected by the EMSC and the EMGW address and port number selected by the EMSC. The specific implementation may include: the EMSC defines the information of the control plane interface Rx, and sends the user media information for establishing the user media plane bearer to the PCRF, where the user media information carries the voice call parameter, and the PCRF uses the voice call parameter as the TFT in the TFT. The parameter is notified to the Packet Data Gateway (P-GW), and the P-GW is connected to the Serving Gateway (S-GW), the Mobility Management Entity (MME), and the evolved UMTS terrestrial radio. The signaling related to establishing a dedicated bearer between the evolved base stations (ENBs) in the UMTS Terrestrial Radio Access Network (EUTRAN) carries the voice call parameters, and the terminal obtains the relevant signaling from the ENB to establish a dedicated bearer. The voice call parameters.

Based on the instruction of receiving the circuit domain call, the EMSC analyzes parameters such as voice codec carried in the call message to define parameters of the service that interact with the policy charging system.

The EMSC will provide the value of the VoIP voice codec to the policy charging system and establish the parameters related to the bearer plane. The EMSC will provide the service upper layer identifier to the policy charging system for use as an associated charging system.

The EMSC will provide the policy charging system with the address of the EMGW and the port number of the receiving media plane.

The EMSC will discover the policy charging system based on the IP address provided by the terminal.

The EMSC will send an application service request to the policy charging system according to the defined new service type parameter, and trigger the policy charging system to establish a media plane bearer between the terminal and the packet domain gateway to the packet domain gateway entity.

The policy charging system will map the QoS parameters of the packet domain bearer according to the application service request message received from the EMSC, and deliver parameters for establishing the packet domain bearer requirements, such as QoS profile, voice codec and other parameters to the packet domain gateway. .

The QoS profile contains such as guaranteed rate, QoS label. The label of the QoS is defined according to the parameters of the service defined by the EMSC, the description of the service attribute, and the codec of the voice;

The QoS parameters mapped by the EMSC include a specially defined QoS identifier (label).

The packet domain gateway will push down these parameters to establish a packet domain bearer for the analog voice call, and issue a voice codec to the evolved base station, and the terminal. Here, the speech codec refers to the speech codec used by the terminal in the PS domain and the speech codec used by the terminal to switch to the circuit domain.

Of course, the voice codec can also be sent in other ways, for example:

The network side call control entity (EMSC) sends the high layer instruction to the terminal through the network side control entity, and the high layer instruction carries the voice codec used by the terminal and the media plane parameter of the EMGW;

Alternatively, the network side call control entity encapsulates relevant parameters of the analog voice call in the middle layer message of the IP layer and the voice call signaling layer, and the terminal obtains relevant parameters of the analog voice call from the middle layer message.

Alternatively, the circuit domain call signaling carries the voice codec used by the terminal and/or the media plane parameter of the EMGW.

The packet domain gateway will push down the QoS parameter to the packet domain control plane entity, which will classify the packet domain bearer of the analog voice call according to the parameter. For example, according to a specially defined label, or by adding some indications of the display, the bearer is described as a bearer of the simulated voice data stream.

For subsequent handover use, the MME needs to know the address of the EMSC.

The MME needs to know the address of the EMSC in the following way:

The terminal registers the address of the EMSC in the MME, and this step can be completed after the bearer is established; Alternatively, the packet domain control plane entity (MME) queries the logical entity module for the address of the network side call control entity, and the packet domain control plane entity stores the address of the queried network side call control entity; the logic module can be a home subscription user server (HSS) Entity, but not limited to the entity; or, in the process of establishing a packet domain bearer, the network side call control entity (EMC) notifies the packet domain control plane entity of the address of the network side call control entity;

Alternatively, the EMSC may obtain the address of the MME when acquiring the user subscription data.

After obtaining the address of the EMGW, the terminal may establish a security association of the media stream between the terminal and the EMGW to ensure the security of transmitting the voice call data.

In addition, the terminal can obtain parameters of the voice call, such as codec, in different ways. The voice call parameters can also be notified to the terminal through call signaling between the terminal and the EMSC. After obtaining the voice call parameter, the terminal encodes the media plane data according to the codec in the voice call parameter, and performs data transmission between the address and the port number in the voice call parameter and the EMGW.

The voice call parameter can also be notified to the terminal through network layer signaling between the terminal and the EMSC carrying analog call signaling. After obtaining the voice call parameter, the terminal encodes the media plane data according to the codec in the voice call parameter, and performs data transmission according to the address and port number in the voice call parameter and the EMGW.

The EMSC will possibly encapsulate the parameters of the analog CS domain voice call in the middle layer message of the IP layer and the voice call signaling layer, and notify the UE to use parameters such as voice coding, EMGW address and the like.

After the bearer is successfully established, the bearer identifier is reported to the EMSC entity.

406. After the bearer of the analog voice service is established, the PCRF returns a bearer acknowledgement (ACK) to the EMSC.

407. The EMSC controls the EMGW to modify the association of the media stream, and establish an inter-office media bearer.

The EMSC controls the association of the media stream between the IM-MGW and the MGW in the EMGW, and establishes an inter-office media bearer between the IM-MGW and the MGW. It is also possible to control the establishment of a Quality of Service (QoS) guarantee for the media stream between the P-GW and the IM-MGW through the PCC system.

Specific implementations of QoS guarantees may include:

The EMSC controls the P-GW to classify data that is uplinked from the terminal to the IM-MGW according to the IP flow; The EMSC controls the IM-MGW to classify the data destined for the terminal from the IM-MGW by the IP flow.

The step of the EMSC controlling the P-GW to classify the data from the terminal to the IM-MGW according to the IP flow may also be performed in the process of establishing an analog voice service bearer.

The method can also include:

408, the EMSC receives an address full message (ACM) from the peer MSC; the peer MSC is an MSC that controls the peer end;

409. The EMSC sends a ringing (Alerting) message to the terminal.

410. The EMSC receives an acknowledgement (ANM) message from the opposite MSC.

411. The EMSC triggers the modification of the media plane, and sends a Connect message to the terminal. If the codec selected by the EMSC is not notified to the terminal during the bearer process of establishing the analog voice service, the Alerting message may be sent to the terminal. Carry the codec in it.

412. The terminal replies to the EMSC with a Connect Ack message.

The terminal replies to the Connect Ack message, indicating that the media plane of the terminal to the EMGW has been established, and the terminal may send voice data to the EMGW; the terminal may also establish a security association to the EMGW, and then send voice data to the EMGW; the terminal may also first After the EMGW negotiates the relevant media plane parameters, it sends the voice data to the EMGW.

The second embodiment is a method for implementing a communication call. In this embodiment, a network access service (NAS) message in the SAE is used to encapsulate signaling for simulating a CS domain call. Referring to FIG. 5, in the architecture B shown in FIG. 2, the method for implementing the communication call in this embodiment is different from the steps in the first embodiment in that:

When the UE initiates the simulated CS attach, the attach parameter is transmitted through a Gs-like interface between the MME and the EMSC;

When the UE initiates a voice call, the call setup message is encapsulated in the NAS message according to the configuration of the upper layer module (or according to the indication of the network side entity at the time of attachment) and sent to the MME. An identifier is added to the NAS message, and the identifier is used to instruct the MME to send the part of the analog circuit domain call establishment message in the NAS to an EMSC.

If the EMSC initiates the authentication of the terminal, the EMSC encapsulates the authentication message in the upper layer protocol body, and adds an identifier to the high layer protocol body. According to the indication of the identifier, the MME receives the high layer association. After the negotiation, the authentication message is encapsulated into the NAS message and delivered to the terminal. The NAS message further adds an identifier, and the identifier in the NAS message is used to indicate that the CS domain module in the terminal processes the authentication message.

The CS domain call message sent by the EMSC to the end user is forwarded by the MME through the NAS message, and the MME adds the relevant identifier to each of the NAS messages, and the corresponding identifier in the terminal can process the related information encapsulated in the NAS message. The CS domain call message is simulated; the NAS message without the associated identifier can be directly processed by the MME.

In the first embodiment, the EMSC notifies the terminal of the related parameters of the packet domain by IP connectivity. In this embodiment, the EMSC notifies the terminal to establish an analog circuit domain call through the MME entity through a high layer (such as a NAS layer message). Related parameters carried by the packet domain, such as codec in the PS domain, codec in the CS domain, address of the EMGW, and port of the receiving media plane.

Different from the first embodiment, the terminal notifies the EMSC of the IP address of the terminal and the parameter of the receiving media plane through IP connectivity, that is, the terminal may notify the EMSC terminal of its own IP through the MME entity through a higher layer (such as a NAS layer message). Address and parameters that accept the sending media face, such as RTP, RTCP port, etc.

Different from the first embodiment, the EMSC will notify its own address parameters (such as IP address, etc.)

The MME, the MME, saves the address in the relevant context and notifies the new MME entity when a location change occurs.

Referring to FIG. 5, the method for implementing a communication call in Embodiment 2 includes:

The UE initiates the simulated CS attach, passing the attach parameters through a Gs-like interface between the EMSC and the MME.

501. When the UE needs to initiate a voice call, the call setup message is encapsulated in the NAS message and sent to the MME according to the configuration of the upper layer module (or the indication of the network side entity at the time of attachment). An identifier is added to the NAS message, and the identifier is used to instruct the MME to send the part of the analog circuit domain call setup message in the NAS to an EMSC.

The EMSC initiates authentication of the terminal, and the EMSC encapsulates the authentication message in the upper layer protocol body, and adds an identifier to the high-level protocol body, and the indication of the identifier is received by the MME after receiving the high-level protocol body. The weight message is encapsulated into the NAS message and delivered to the terminal. The NAS message further adds an identifier, and the identifier in the NAS message is used to indicate that the CS domain module in the terminal processes the authentication message.

502. The EMSC sends a Call Proceeding message to the terminal by using the NAS message through the MMW. 503. The EMS sends an initial address message (IAM) to the MSC in the CS domain according to the peer information in the call message, and the MSC feeds back related parameters carried by the peer end to the EMS C according to the peer information in the IAM.

504. The EMSC controls the EMGW to establish an association of the media stream.

505-1. The EMSC pushes the newly defined service to the PCRF, where the message may include user media information such as the address of the EMSC;

505-2, the PCRF may also push the bearer setup request to the PDN-GW; the bearer setup request may include voice coding, an address of the EMSC, and the voice coding may include codec in the packet domain and codec in the circuit domain;

505-3. The PDN-GW determines the bearer QoS by using the received QoS policy value, and sends a bearer setup request to the Serving-GW. The message contains the codec of the voice, the special label defined,

The address of the EMSC; if the identity of the circuit domain bearer cannot be defined by label, a different identifier will be used to identify the payload.

505-4. The serving gateway (Serving-GW) sends a bearer setup request to the MME, and the bearer setup request includes the above parameters.

505-5. The MME saves the address of the EMSC to the context for subsequent handover, and distinguishes the bearer of the service and the different PS domain bearer according to the label or the special identifier, so as to give the bearer high in subsequent handover. Priority to ensure priority when switching.

The MME establishes a session control parameter, and the MME sends a bearer setup request to the evolved base station (ENB), where the bearer setup request includes a session control parameter, and the session control parameter includes a voice codec used by the UE. 505-6, ENB performs QoS mapping, and saves relevant speech codec to achieve better resource scheduling. Then, the UE sends a message of the radio bearer setup to the UE, and the message carries the voice codec (including the codec used in the circuit domain and/or the packet domain) required by the UE, and the UE responds to the radio bearer setup message.

505-7, the ENB responds to the bearer establishment message to the MME;

505-8, the MME responds to the bearer establishment message to the Serving-GW;

505-9, Serving-GW responds to the bearer setup message to the PDN-GW;

505-10. The PDN-GW responds to the bearer setup completion message to the PCRF, and reports the associated identifier of the current bearer, such as the bearer identifier, so that the PCRF performs the association between the bearer plane and the defined service plane.

506. After the bearer of the simulated voice service is established, the PCRF returns an ACK message to the EMSC.

507. The EMSC controls the EMGW to modify the association of the media stream to establish an inter-office media bearer.

The method can also include:

508, the EMSC receives an address full message (ACM) from the peer MSC; the peer MSC is an MSC that controls the peer end;

509. The EMSC sends an Alerting message to the terminal by using the NAS message by the MMW.

510. The EMSC receives an acknowledgement (ANM) message from the peer MSC.

511. The EMSC triggers the modification of the media plane, and sends a Connect message to the terminal by using the NAS message through the MMW. If the codec selected by the EMSC is not notified to the terminal in the bearer process of establishing the simulated voice service, the device may send the message to the terminal. The codec is carried in the Alerting message.

512. The terminal sends a Connect Ack message to the EMSC by using the NAS message through the MMW.

The third embodiment is a method for implementing a communication call. In this embodiment, a UE initiates a process of establishing a bearer in a packet domain. Referring to FIG. 6, the method includes:

600, establishing a transmission analog CS domain call in the packet domain, and registering the PS domain bearer;

601, simulation of the attachment of the CS domain;

602. The UE initiates the simulated CS domain call according to the received indication of the upper layer network entity (eg, EMSC, MME, etc.). The call message simulating the CS domain can pass the IP level between the UE and the EMSC. The connection is sent to the EMSC; or the call message of the simulated CS domain is sent to the MME entity first, and then sent to the EMSC through the interface between the MME and the EMSC;

603. The EMSC establishes a media plane association of the call service between the UE and the EMGW according to the received call message.

604. After receiving the message from the EMSC, the UE initiates a bearer establishment process of the packet domain, where the bearer is used to transmit services such as simulated CS domain voice.

The bearer establishment process of the packet domain may include:

After receiving the call message, the EMSC will notify the terminal to establish a bearer for the analog circuit domain service on the packet domain, for example, by instructing the UE to establish a bearer through a displayed parameter indication. The EMSC notifies the terminal of the voice codec used by the terminal and the media plane parameters of the EMGW. The media plane parameters of the EMGW include the address, port number, and QoS parameters of the upper layer of the EMGW.

After receiving the message from the EMSC, the terminal triggers the establishment of a packet domain bearer that transmits the analog circuit domain service. The terminal may receive the message directly from the EMSC or receive the message from the EMSC through the packet domain control plane entity.

The terminal constructs a QoS, packet flow template and other parameters of the bearer establishment according to the message received from the EMSC to initiate a process of carrying the packet domain bearer of the analog circuit domain service.

The service gateway selected by the terminal is the service gateway to which the IP address of the EMSC belongs when the terminal is in the call message.

After the bearer is successfully established,

The UE may send the address of the "EMSC" to the MME in the process of successful bearer establishment or bearer establishment.

The method for implementing a communication call may further include:

605. Establish a security association between the terminal and the EMGW, where the security association is used to ensure data transmission security between the terminal and the EMGW.

The fourth embodiment, a method for implementing a communication call, in this embodiment, the MME initiates a process of establishing a packet domain bearer. Referring to FIG. 7, the method includes:

700. Establish a transport analog CS domain call in the packet domain, and register the PS domain bearer;

701. Simulating the attachment of the CS domain;

702. The UE initiates a simulated CS domain call. The call message simulating the CS domain may be sent to the EMSC through the IP plane connection between the UE and the EMSC, or through the MME entity, through the MME and the EMSC. The interface is sent to the EMSC;

703. The EMSC establishes a media plane association of the call service between the UE and the EMGW according to the received call message.

704. After receiving the message from the EMSC, the MME initiates a bearer establishment process of the packet domain, where the bearer is used to transmit services such as simulated CS domain voice.

The bearer establishment process of the packet domain may include:

After receiving the call message, the EMSC will notify the MME to establish a bearer for the analog circuit domain service on the packet domain. For example, the MME is notified of the establishment of the bearer by a displayed parameter indication, or the MME is notified of the bearer by a specific message. The EMSC notifies the MME of the EMGW address, port number, upper layer QoS parameters, voice codec and other parameters.

After receiving the message from the EMSC, the MME triggers the establishment of a packet domain bearer that transmits the analog circuit domain service. Based on the message received from the EMSC, the MME will construct the QoS, packet flow template and other parameters of the bearer to initiate a process of carrying the packet domain bearer of the analog circuit domain service. The service gateway selected by the MME is the service gateway to which the terminal reports to the EMSC's IP address when the call message is sent.

After the bearer is successfully established, the MME feeds back the bearer setup success message to the EMSC, and associates the bearer identifier.

The MME will save the address of the EMSC to the context for use in subsequent handovers.

The method for implementing a communication call may further include:

705. Establish a security association between the terminal and the EMGW, where the security association is used to ensure data security between the terminal and the EMGW.

Embodiment 5 is a method for implementing a communication call. In this embodiment, a PDN-GW initiates a process of establishing a packet domain bearer. Referring to FIG. 8, the method includes:

800, establishing a transmission analog CS domain call in the packet domain, and registering the PS domain bearer;

801, emulating the attachment of the CS domain;

802. The UE initiates an analog CS domain call. The call message of the simulated CS domain may be sent to the EMSC through the IP layer connection between the UE and the EMSC, or sent to the EMSC through the interface between the MME and the EMSC through the MME entity; 803. The EMSC establishes a media plane association of the call service between the UE and the EMGW according to the received call message.

804. The EMSC notifies the PDN-GW to initiate a bearer establishment process of the packet domain, where the bearer is used to transmit the simulated CS domain voice service.

The bearer establishment process of the packet domain may include:

After receiving the call message, the EMSC will inform the PDN-GW to establish a bearer for the analog circuit domain service on the packet domain. The EMSC notifies the PDN-GW of the EMGW address, port number, upper layer QoS parameters, voice codec parameters, and the EMSC address.

After receiving the message from the EMSC, the PDN-GW triggers the establishment of a packet domain bearer that transmits the analog circuit domain service. The PDN-GW will construct a packet domain bearer carrying the analog circuit domain service according to the message received from the EMSC, constructing the QoS, packet flow template and other parameters established by the bearer. The EMSC selects a correct packet domain data gateway according to the IP address of the terminal received at the time of the call message, or the terminal can also report the address of the packet domain gateway in the call message.

After the bearer is successfully established, the PDN-GW can carry the identity to the EMSC on the packet domain.

The PDN-GW notifies the MME, the MME of the EMSC's address and saves the EMSC's address as used in subsequent handovers.

The method for implementing a communication call may further include:

805. Establish a security association between the terminal and the EMGW, where the security association is used to ensure data transmission security between the terminal and the EMGW.

Embodiment 1 A method for releasing a communication call is implemented. A call is established between the terminal in the PS domain and the peer in the CS domain or the fixed network. In the architecture A shown in Figure 1, the call initiated by the network side is released. For example, if the peer entity hangs up actively, the terminal receives the call from the terminal. After the EMSC message, the terminal initiates the process of deleting the dedicated bearer carrying the CS domain call media plane.

Referring to FIG. 9, a method for releasing a communication call includes:

901. The EMSC receives a release message.

When the peer actively hangs up, the peer network fails, or the connection timeout with the peer network occurs, the EMSC receives the release message from the peer network.

902. The EMSC sends a disconnect message to the terminal through the IP layer. The disconnect message is encapsulated in the data protection layer of the IP layer according to the format of the intermediate adaptation layer of the signaling layer of the IP layer and the analog circuit domain call, and the destination address of the data packet is the IP address of the terminal;

903. The EMSC controls the EMGW to modify the associated media stream.

The EMGW modifies the media stream association to the terminal;

904, EMSC feedback release completion message;

The release completion message is used to respond to the release message in step 901;

905. The terminal sends a release (Rel) message to the EMSC.

906. The EMSC sends a radio link control (RLC) message to the terminal.

907. After receiving the RLC message, the terminal initiates a release process of the dedicated bearer, where the dedicated bearer is used to carry the CS domain call media plane data.

When the dedicated bearer is released, the behavior of guaranteeing the QoS of the media stream between the PDN-GW and the EMGW may be stopped.

908. The EMSC controls the EMGW to delete the related media stream. The EMSC will provide the address of the terminal and the receiving media plane port to the EMGW to release the media stream association between the terminal and the EMGW.

Upon release, or after the release, the UE or network side entity (such as EMSC) will inform the MME to delete the address of the EMSC stored in the relevant context.

After the terminal sends an Rd message to the EMSC in step 905, step 908 is performed.

Embodiment 2: A method for releasing a communication call is implemented. In the architecture B shown in FIG. 2, the network side initiates call release of the PS domain analog CS domain. Referring to FIG. 10, the method for releasing the communication call is different from the first embodiment for implementing the method for releasing the communication call:

The signaling between the terminal and the EMSC is transmitted through the NAS plane between the terminal and the MME and the signaling plane between the MME and the EMSC. The simulated CS domain signaling sent by the EMSC to the terminal is forwarded to the terminal through the NAS message of the MME. The MME adds a related identifier to the forwarded NAS message to distinguish the normal NAS message. According to the related identifier, the corresponding CS domain in the terminal The module processes the analog CS domain signaling in the NAS message.

In the first embodiment of the method for releasing the communication call, the EMSC sends a disconnect message to the terminal through the IP connectivity. In this embodiment, the EMSC sends a disconnect message to the terminal through the MME. In the first embodiment of the method for releasing the communication call, the terminal sends the Rel message to the EMSC through the IP connectivity. In this embodiment, the terminal sends the Rel message to the EMSC through the MME.

In the first embodiment of the method for releasing the communication call, the EMSC sends the RLC message to the terminal through the IP connectivity. In this embodiment, the EMSC sends an RLC message to the terminal through the MME.

Referring to FIG. 10, a method for releasing a communication call in Embodiment 2 includes:

1001. The EMSC receives a release message.

1002. The EMSC sends a disconnect message to the terminal by using the NAS message of the MME.

The EMSC encapsulates the disconnect message in the upper layer protocol body, and adds an identifier to the high-level protocol body. The MME receives the indication of the identifier, and after receiving the high-layer protocol body, the MME encapsulates the disconnect message into the NAS message and transmits the message to the terminal. The NAS message further adds an identifier, and the identifier in the NAS message is used to indicate that the CS domain module in the terminal processes the disconnect message.

1003. The EMSC controls the EMGW to modify the associated media stream.

The EMGW modifies the media stream association to the terminal;

1004, EMSC feedback release completion message;

The release completion message is used to respond to the release message in step 1001;

1005. The terminal sends a Rel message to the EMSC through the NAS message of the MME.

1006. The EMSC sends a radio link control RLC message to the terminal by using the NAS message of the MME.

1007. After receiving the RLC message, the terminal initiates a release process of the dedicated bearer, where the dedicated bearer is used to carry the CS domain call media plane data;

1008. The EMSC controls the EMGW to delete the related media stream.

When the bearer is released, or after the bearer is released, the UE or the network side entity (such as EMSC) will inform the MME to delete the address of the EMSC stored in the relevant context.

After the terminal sends a Rel message to the EMSC through the NAS message of the MME in step 1005, step 1008 is performed. Embodiment 3: A method for releasing a communication call is implemented. In the architecture A shown in FIG. 1, the network side initiates a call release of the PS domain analog CS domain.

Referring to FIG. 11, the method for releasing the communication call is different from the first embodiment for implementing the method for releasing the communication call. In this embodiment, the EMSC controls to delete the analog CS domain call media in the packet domain by using the PCC system. The exclusive bearer of the face.

In this embodiment, the EMSC will initiate a release process of the dedicated bearer by using the Rx interface to control the PCRF, and the dedicated bearer is used to carry the CS domain call media plane;

In this embodiment, the EMSC sends an application service deletion request through the Rx interface. The PCRF sends a request to delete the bearer to the PDN-GW according to the received request to delete the application service, and carries the number of the deleted bearer. The PDN-GW initiates a release procedure of the dedicated bearer according to the message received from the PCRF, and releases the media plane bearer for carrying the CS domain call between the tPDN-GW and the UE;

When the proprietary bearer is released, the behavior of QoS guarantee for the voice data is stopped between the P-GW and the IM-MGW.

Referring to FIG. 11, the method for releasing a communication call in Embodiment 3 includes:

1101. The EMSC receives a release message.

1102. The EMSC sends a disconnect message to the terminal.

The disconnect message is encapsulated in the data protection layer of the IP layer according to the format of the intermediate adaptation layer of the signaling layer of the IP layer and the analog circuit domain call, and the destination address of the data packet is the IP address of the terminal;

1103. The EMSC controls the EMGW to modify the associated media stream.

The EMGW modifies the media stream association to the terminal;

1104. The EMSC feedback release completion message;

The release completion message is used to respond to the release message in step 1101;

1105. The terminal sends a Rel message to the EMSC.

1106. The EMSC sends a radio link control RLC message to the terminal.

1107. The EMSC controls the PCRF to initiate a release process of the dedicated bearer by using the Rx interface, where the dedicated bearer is used to carry the CS domain call media plane data. When the dedicated bearer is released, the behavior of QoS guarantee for the media stream between the PDN-GW and the EMGW may be stopped.

1108. The EMSC controls the EMGW to delete the related media stream.

Alternatively, after the terminal sends a Rel message to the EMSC through the NAS message of the MME in step 1105, step 1108 is performed.

Embodiment 4: A method for releasing a communication call is implemented. In the architecture B shown in Fig. 2, the network side initiates call release of the PS domain analog CS domain.

Referring to Figure 12, the call release method for implementing communication differs from the first embodiment of the method for releasing a communication call in that: the EMSC controls the deletion of the dedicated bearer carrying the CS domain call media plane through the PCC system. In this embodiment, the EMSC sends an application service deletion request through the Rx interface. The PCRF sends a request to delete the bearer to the PDN-GW according to the received request for deleting the application service, and carries the number of the deleted bearer. The PDN-GW initiates a release procedure of the dedicated bearer according to the message received from the PCRF, and releases the media plane bearer for carrying the CS domain call between the PDN-GW and the UE; when releasing the dedicated bearer, the P-GW and the IM - The behavior of QoS guarantee for the voice data is stopped between the MGWs.

The difference from the third embodiment of the method for releasing the communication call is that the signaling between the terminal and the EMSC is transmitted through the NAS plane between the terminal and the MME and the signaling plane between the MME and the EMSC. The simulated CS domain signaling sent by the EMSC to the terminal is forwarded to the terminal through the NAS message of the MME. The MME adds a related identifier to the forwarded NAS message to distinguish the normal NAS message. According to the related identifier, the corresponding CS domain in the terminal The module processes the analog CS domain signaling in the NAS message.

In the first embodiment of the method for releasing a communication call, the EMSC sends a disconnect message to the terminal through the IP connectivity. In this embodiment, the EMSC sends a disconnect message to the terminal through the MME; and the method for releasing the communication call is implemented. In the first embodiment, the terminal sends the Rel message to the EMSC through the IP connectivity. In this embodiment, the terminal sends the Rel message to the EMSC through the MME. In the first embodiment of the method for releasing the communication call, the EMSC passes the IP connectivity. The difference is that the RLC sends the RLC message to the terminal. In this embodiment, the EMSC sends an RLC message to the terminal through the MME.

Referring to FIG. 12, a method for releasing a communication call in Embodiment 4 includes: 1201. The EMSC receives a release message.

When the peer actively hangs up, the network fails, or the connection timeout with the network occurs, the EMSC receives the release message from the peer network.

1202. The EMSC sends a disconnect message to the terminal by using the NAS message of the MME.

1203. The EMSC controls the EMGW to modify the associated media stream.

The EMGW modifies the media stream association to the terminal;

1204. The EMSC feedback release completion message;

The release completion message is used to respond to the release message in step 1201;

1205. The terminal sends a Rel message to the EMSC through the NAS message of the MME.

1206. The EMSC sends a radio link control RLC message to the terminal by using the NAS message of the MME.

1207. The EMSC controls the PCRF to initiate a release process of the dedicated bearer by using the Rx interface, where the dedicated bearer is used to carry the CS domain call media plane data.

When the dedicated bearer is released, the media stream between the PDN-GW and the EMGW can be stopped.

QoS guaranteed behavior.

1208. The EMSC controls the EMGW to delete the related media stream.

Alternatively, after the terminal sends a Rel message to the EMSC through the NAS message of the MME in step 1205, step 1208 is performed.

Embodiment 5, a method for releasing a communication call, see FIG. 13, the method includes:

1300. The terminal initiates a voice call in an analog circuit domain in the packet domain.

1301. The EMSC receives a call release message from an analog circuit domain of the network side or the terminal side.

1302. The EMSC will notify the UE and the EMGW and other entities to release the association of the relevant media planes;

1303. The EMSC notifies the MME entity to release the related packet domain bearer.

1304. The MME entity deletes or modifies the related packet domain bearer according to the received message.

The MME entity will delete or modify the related packet domain bearer according to the received message, which may include: The MME entity will store the EMSC address stored in the context to index an associated packet domain bearer.

The MME entity will delete or release the relevant packet domain bearer according to the bearer identifier provided by the EMSC. Embodiment 6, a method for releasing a communication call, see FIG. 14, the method includes:

1400. The terminal initiates a voice call in an analog circuit domain in the packet domain.

1401. The EMSC receives a call release message from a network side or a terminal side analog circuit domain;

1402, the EMSC will notify the UE and the EMGW and other entities to release the association of the relevant media plane; 1403, the EMSC will notify the PDN-GW entity to release the relevant packet domain;

1404. The PDN-GW entity will delete or modify the associated packet domain bearer based on the received message.

The PDN-GW entity will delete or modify the relevant packet domain bearer according to the received message. The information may include:

PDN - G^W^l^^^ According to the identifier of an received IP data stream, such as the quintuple parameter at the IP level, delete or modify a packet domain bearer.

The PDN-GW entity will delete or modify the associated packet domain bearer according to the bearer identity provided by the EMSC.

For an embodiment, see FIG. 15, a user equipment, including:

a transmitting unit 1501, configured to perform message interaction with the packet domain control plane entity;

The encapsulating unit 1502 is configured to send the signaling to the transmission unit after the network non-access stratum message is sent, where the network non-access stratum message carries the indication information, where the indication information is used by the packet domain control plane entity to determine whether the network is not connected. The layer message is sent to the network side call control entity;

The decapsulation unit 1503 is configured to decapsulate the corresponding signaling from the message from the transmission unit and provide a peer-to-peer protocol layer entity at the transmission level between the terminal and the network side call control entity.

For an embodiment, refer to FIG. 16, a packet domain control plane entity, including:

The receiving unit 1601 is configured to receive a message from the user equipment or the network side call control entity. The determining unit 1602 is configured to determine whether the message from the user equipment needs to transparently transmit the message from the network side call control entity to the network side call control entity. Whether it needs to be transparently transmitted to the user equipment; if necessary, generate a control instruction; The sending unit 1603 is configured to transparently transmit a message from the user equipment to the network side call control entity and transmit a message from the network side call control entity to the user equipment according to the control instruction.

For an embodiment, refer to FIG. 17, a network side call control entity, including:

The receiving unit 1701 is configured to receive the message of the circuit domain for the packet domain and the circuit domain, and the control unit 1702 is configured to generate a control instruction according to the message of the circuit domain;

The sending unit 1703 is configured to send corresponding data or signaling according to the control instruction.

Embodiments Referring to FIG. 18, a system for implementing a communication call includes:

a network side call control entity 1801, configured to generate a control message directed to the packet domain and the circuit domain;

The EMGW 1802 is configured to establish a media plane association with the terminal according to the control instruction, and the packet domain gateway 1803 is configured to establish, according to the control instruction, a bearer between the terminal and the terminal, and carry the analog circuit domain used by the transmission terminal in the packet domain. Business data.

Among them, EMGW includes:

a first gateway 18021, configured to face the packet domain, and convert the packet domain voice data format into a format of the circuit domain voice;

The second gateway 18022 is configured to face the circuit domain and perform data transmission with the first gateway. Through the description of the above embodiments, those skilled in the art can clearly understand that the present invention can be implemented by means of software plus a necessary hardware platform, and of course, all can be implemented by hardware. Based on such understanding, all or part of the technical solution of the present invention contributing to the background art may be embodied in the form of a software product, which may be stored in a storage medium such as a ROM/RAM, a magnetic disk, an optical disk, or the like. A number of instructions are included to cause a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in various embodiments of the present invention or portions of the embodiments.

The above is only a specific embodiment of the present invention, and it should be noted that those skilled in the art can also make some improvements and retouching without departing from the principles of the present invention. It is considered as the scope of protection of the present invention.

Claims

Rights request

A method for implementing a communication call, the method comprising:

Receiving a call message from the terminal;

The method according to claim 1, wherein the receiving the call message from the terminal specifically includes:

The network side call control entity receives a call setup message from the terminal, where the call setup message carries a call message, and the destination address of the call setup message is an address of the network side call control entity;

The network side call control entity obtains the call message from the call setup message.

The packet domain control plane entity receives the network layer message from the terminal, the network layer message encapsulates the call message, the network layer message carries indication information, and the indication information is used by the packet domain control plane entity to determine Whether to send the network layer message to the network side call control entity;

If it is determined that the network layer message needs to be sent to the network side call control entity, the packet domain control plane entity sends the network layer message to the network side call control entity;

The network side call control entity decapsulates the call message from the network layer message.

The method according to claim 1, wherein the controlling the establishment of the bearer between the terminal and the group domain gateway comprises:

The network side call control entity control policy charging system triggers establishment of a bearer of the packet domain, and the bearer of the packet domain is used for transmitting analog circuit domain service data;

The network side call control entity controls the EMGW to establish an interoffice media bearer.

The method according to claim 1, wherein the associated parameters of the terminal media stream include a voice codec, a terminal receiving a listening port of the media plane, and an address of the receiving media plane, where the control establishes an EMGW and the terminal The media associations between the two include: The network side call control entity sends the association parameter of the media stream of the terminal to the EMGW;

And determining, by the EMGW, a media plane association with the terminal according to an association parameter of the media stream of the terminal.

6. The method according to claim 1, wherein the method further comprises:

The network side call control entity controls to establish a security association between the EMGW and the terminal, and is used to ensure that the EMGW establishes security of media stream data transmission with the terminal.

The method according to claim 1, wherein the controlling the establishment of the loading between the terminal and the EMGW comprises:

After receiving the call message, the network side call control entity notifies the terminal to establish a bearer for transmitting the analog circuit domain service on the packet domain.

The method according to claim 1, wherein the controlling the establishment of the bearer between the terminal and the packet domain gateway comprises:

After receiving the call message, the network side call control entity notifies the packet domain control plane entity to establish a bearer for transmitting the analog circuit domain service on the packet domain.

After receiving the call message, the network side call control entity notifies the packet domain gateway entity to establish a bearer for transmitting the analog circuit domain service on the packet domain.

10. The method according to claim 1, wherein the method further comprises:

Obtaining the associated parameters of the terminal media stream.

The method according to claim 1, wherein the method further comprises:

The packet domain control plane entity learns the address of the network side call control entity.

12. The method according to claim 1, wherein the method further comprises:

Establishing a security association between the terminal and a network side call control entity;

The network side call control entity and the EMGW store security association parameters, and the security association parameters are used to protect data of the signaling plane and the data plane of the analog circuit domain call.

13. The method according to claim 1, wherein the method further comprises: The network side call control entity selects the EMGW.

14. The method according to claim 1, wherein the method further comprises:

The network side call control entity selects the multimedia media gateway module and the media gateway module in the EMGW to perform conversion between the packet domain speech codec and the voice codec of the circuit domain; the multimedia media gateway module and the media gateway module are in the same EMGW.

A method for releasing a communication call, the method comprising: after receiving a session release message from a peer, sending a message of a circuit domain release session to the terminal; ending the EMGW and the terminal according to the message of releasing the session Media plane association between the two; according to the message releasing the session, releasing the bearer between the packet domain gateway and the terminal.

The method according to claim 15, wherein the method further comprises: notifying the packet domain control plane entity to delete an address of the network side call control entity stored in the packet domain control plane entity.

17. A user equipment, comprising:

18. A packet domain control plane entity, comprising:

19. A network side call control entity, comprising:

a receiving unit, configured to face the packet domain and the circuit domain, and receive the message of the circuit domain; a control unit, configured to generate a control instruction according to the message of the circuit domain;

20. A system for implementing a communication call, comprising:

The system according to claim 20, wherein the EMGW comprises: a first gateway, configured to face a packet domain, and convert a packet domain voice data format into a format between circuit domain voices;

The second gateway is configured to face the circuit domain and perform data transmission with the first gateway.