WO2007131435A1

WO2007131435A1 - A calling method, system and msce over ip supporting

Info

Publication number: WO2007131435A1
Application number: PCT/CN2007/001486
Authority: WO
Inventors: Yunfei Li; Chungeng Zhai
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-05-09
Filing date: 2007-04-30
Publication date: 2007-11-22
Also published as: CN1984054A; CN100531467C

Abstract

A calling method over IP supporting, includes: the MSCe sends a ringing message to the called BSC after it has detected that the connection for this call has been set up; and then the called BSC informs the called terminal to ring. A calling system over IP supporting, includes: a MSCe, a MGW and a called BSC. A MSCe includes: a module for requesting an IP address and a module for transmitting the ringing message. The present invention enables the called terminal not to ring until the connection for this call has been set up, avoids the situation that the calling party and the called party can not hear each other before the connection has been set up, and prevents the unusual call drop, so as to improve the users' pleasure. Also, present invention avoids to charge before the connection has been set up, thus reducing the users' cost.

Description

Call method, system and mobile softswitch center based on internet protocol bearer

The present invention relates to the field of call communication technologies, and in particular, to a call method, system and mobile softswitch center based on an Internet protocol bearer. Background of the invention

In a traditional circuit domain network architecture, the Mobile Switching Center (MSC) and the Base Station Control Center (BSC) are directly connected by Time Division Multiplexing (TDM) circuits to carry the voice path. After adopting the soft-switching structure, the control is separated from the bearer. The MSC is divided into two parts: the Mobile Softswitch Center (MSCe) and the Media Gateway (MGW). There are two basic bearer media in softswitch: TDM-based circuit link channel and Internet Protocol (IP)-based Real-Time Transport Protocol (RTP) media stream. When the IP network is used for bearer, the voice originally carried by the TDM is transmitted through the IP bearer network.

Figure 1 is a diagram of a softswitch architecture based on IP bearers. As shown in Figure 1, the functions of each part are as follows:

MSCe: mainly implements session and call signaling control functions, and simultaneously acts as an MGW controller to implement action control on the MGW;

MGW: The bearer function is implemented, and the bearer is set according to the control command of the MSCe, and the bearer related event is reported to the MSCe.

Base station (BS): refers to the BS that uses IP bearer on the A interface, and its role is the same as that of the traditional BS.

The new interface between the MSCe/GW and the BS Alp corresponds to the traditional A1 interface, and A2p corresponds to the traditional A2 interface, which is used to implement signaling and voice data transmission, respectively. The MSCe/MG can also be connected to non-IP BSs via the A1 and A2 interfaces.

Figure 2 shows the existing bureau under the softswitch architecture of the primary and the called BSC based on the IP bearer. A schematic diagram of the message flow of the internal call, as shown in FIG. 2, the specific steps are as follows: Step 201: The calling BSC sends a CM Service Request message to the MSCe, where the message carries the IP address information of the calling BSC.

Step 202: After receiving the CM service request message, the MSCe sends an Add Endpoint (ADD) message to the MGW, where the peer IP address information carried by the message is the IP address information of the calling BSC, to apply for establishing an IP bearer with the calling BSC. IP endpoint.

Step 203: After receiving the addendend message, the MGW allocates an IP endpoint for establishing an IP bearer with the calling BSC, and returns the assigned IP address information of the IP endpoint to the MSCe by adding an endpoint response message, and then the MSCe receives and saves. The IP address information of the IP endpoint allocated by the MGW to establish an IP bearer with the calling BSC.

Step 204: The MSCe sends an Assignment Request message to the calling BSC, where the message carries the IP address information of the IP endpoint allocated by the MGW to establish an IP bearer with the calling BSC.

Step 205: The MSCe sends a paging request (Paging Request) message to the called BSC. Step 206: After receiving the assignment request message, the calling BSC starts to establish an air interface channel and a calling side IP bearer, and after the establishment is completed, sends an Assignment Complete message to the MSCe.

Step 207: After receiving the paging request message, the called BSC returns a paging response (Paging Response) message to the MSCe, where the message carries the IP address information of the called BSC.

Step 208: After receiving the paging response message, the MSCe sends an addendum message to the MGW, where the peer IP address information carried by the message is the IP address information of the called BSC, to apply for establishing an IP bearer IP endpoint with the called BSC.

Step 209: After receiving the addendend message, the MGW allocates an IP endpoint for establishing an IP bearer with the called BSC, and returns the assigned IP address information of the IP endpoint to the MSCe by adding an endpoint response message, and then the MSCe receives and saves. The MGW is assigned and called BSC Establish IP address information of the IP endpoint of the IP bearer.

Step 210: The MSCe sends an assignment request message to the called BSC, where the message carries the IP address information of the IP endpoint allocated by the MGW to establish an IP bearer with the called BSC, and carries the calling number and ringing information for the called terminal. Ring yourself.

Step 211: After the established BSC establishes the air interface on the air interface and the IP address on the called side, the BSC sends an assignment completion message to the MSCe, and simultaneously informs the called terminal to ring through the called BS.

Step 212: After receiving the assignment completion message, the MSCe notifies the MGW to start playing the ring back tone to the calling side by modifying the bearer (MODIFY) message.

Step 213: The called BSC detects the called response and sends a connection (CONNECT) message to the MSCe.

Step 214: After receiving the connection message, the MSCe notifies the MGW to stop playing the ring back tone to the calling side.

FIG. 3 is a schematic diagram of a message flow of an existing inter-office call under the IP bearer softswitch architecture of the primary, the called BSC, and the interoffice. As shown in FIG. 3, the physical procedure is as follows: Step 301: The calling BSC sends a CM Service Request message to the calling MSCe, which carries the IP address information of the calling BSC.

Step 302: After receiving the CM service request message, the calling MSCe sends an addendum message to the calling MGW to apply for establishing two IP endpoints, and an IP endpoint is used to establish an IP bearer with the calling BSC. The IP address information is the IP address information of the calling BSC; the other IP endpoint is used to establish a bearer with the called MGW.

Step 303: After receiving the Add Endpoint message, the calling MGW allocates an endpoint that establishes an IP bearer with the calling BSC, and allocates an IP endpoint that establishes an IP bearer with the called MGW, and allocates IP address information of the two IP endpoints. The bearer is sent to the calling MSCe in the Add Endpoint Response message. After that, the calling MSCe saves the IP address information of the two IP endpoints established by the calling MGW to establish an IP bearer with the calling BSC and the called MGW. Step 304: The calling MSCe sends an assignment request message to the calling BSC, where the message carries the IP address information of the IP endpoint allocated by the calling MGW to establish an IP bearer with the calling BSC.

Step 305: The calling MSCe sends a call request (INVITE) message to the called MSCe, where the message carries the IP address information of the IP endpoint allocated by the calling MGW to establish an IP bearer with the called MGW.

Step 306: After receiving the call request message, the called MSCe sends a paging request message to the called BSC.

Step 307: The calling BSC receives the assignment request message, and sends an assignment completion message to the calling MSCe after the air interface channel and the IP ^^ load between the calling MG and the calling MG are established.

Step 308: Called; After receiving the paging request message, the BSC returns a paging response message to the called MSCe, where the message carries the IP address information of the called BSC.

Step 309: After receiving the paging response message, the called MSCe sends an Add Endpoint message to the called MGW to apply for establishing two IP endpoints, and an IP endpoint is used to establish an IP bearer with the calling MGW. The peer IP address information is the IP address information of the called MGW. The other IP endpoint is used to establish an IP bearer with the called BSC. The peer end address information carried by the added endpoint message is the IP address information of the called BSC.

Step 4 310: After receiving the addendend message, the called MGW allocates an IP endpoint for establishing an IP bearer with the calling MGW, and allocates an IP endpoint for establishing an IP bearer with the called BSC, and allocates the allocated IP address. The IP address information of the two IP endpoints is returned to the called MSCe. After that, the called MSCe saves the IP address information of the two IP endpoints established by the called MGW and the called MGW and the called BSC to establish an IP bearer.

Step 311: The called MSCe sends an assignment request message to the called BSC, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the called BSC, and carries the calling number and the ringing information. Ring the ring at the called terminal itself.

Step 312: After the called BSC receives the assignment request message, it starts to establish an air interface channel and After the IP bearer between the called and the called MGW is established, the assignment completion message is sent to the called MSCe, and the called terminal is notified by the called BS to ring.

Step 313: After receiving the assignment completion message, the called MSCe sends a 180 message to the calling MSCe, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the calling MGW.

Step 314: After receiving the 180 message, the calling MSCe sends a modify bearer (MODIFY) message to the calling MGW, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the calling MGW. The MGW is called to establish an interoffice IP bearer with the called MGW.

Step 315: After receiving the assignment completion message, the called MSCe notifies the called MGW to start playing the ring back tone to the calling side by modifying the bearer message.

Step 316: After the called BSC detects the called response, it sends a connection (CONNECT) message to the called MSCe.

Step 317: After receiving the connection message, the called MSCe notifies the called MGW to stop playing the ring back tone to the calling side by modifying the bearer message, and simultaneously sends a 200 response to the call request (INVITE) message to the calling MSCe to notify the main Called MSCe called has been answered.

Step 318: After receiving the 200 response message, the calling MSCe returns an acknowledgement (ACK) message to the called MSCe.

FIG. 4 is a schematic diagram of a message flow of an existing inter-office call under the IP bearer softswitch architecture of the primary, the called BSC, and the interoffice. As shown in FIG. 4, the specific steps are as follows: Steps 401-405 and Steps 301 to 305 are the same.

Step 406: After receiving the call request message, the called MSCe sends a paging request message to the called BSC, and sends a 180 message to the calling MSCe to notify the calling MSCe to start to give the calling user a ringback tone.

Step 407 is the same as step 307. Step 408: After receiving the 180 message, the calling MSCe returns a temporary response (PRACK) message for the 180 message to the called MSCe.

Step 409: After receiving the temporary response message, the called MSCe returns a 200 response message to the calling MSCe.

Step 410: The calling MSCe sends a modify bearer message to the calling MGW to request the calling MGW to play the ring back tone to the calling user.

Step 411: The calling MGW receives the modify bearer message, starts playing the ring back tone to the calling user, and returns a modify bearer response message to the calling MSCe.

Step 412 is the same as step 308.

Step 413: After receiving the paging response message, the called MSCe sends an Add Endpoint message to the called MGW to apply for establishing two IP endpoints, and an IP endpoint is used to establish an IP bearer with the calling MGW. The peer IP address information is the IP address information of the called MGW. The other IP endpoint is used to establish an IP bearer with the called BSC. The peer IP address information carried by the added endpoint message is the IP address information of the called BSC. At the same time, the called MGW is notified to play the ring back tone to the calling user through the IP endpoint for establishing an IP bearer with the calling MGW.

Step 414: After receiving the addendend message, the called MGW allocates an IP endpoint for establishing an IP bearer with the calling MGW, and plays a ringback tone to the calling user through the IP endpoint, and allocates one for calling and called. The BSC establishes an IP bearer IP endpoint, and after the establishment is completed, returns an add endpoint response message to the called MSCe, where the message carries the IP address information of the two IP endpoints that are allocated. After that, the called MSCe saves the IP address information of the two IP endpoints that are set up by the called MGW and establishes an IP bearer with the calling MGW and the called BSC.

Step 415: The called MSCe sends an assignment request message to the called BSC, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the called BSC, and carries the calling number and ringing information. Ringing at the called terminal itself; also called MSCe Sending a 183 message to the calling MSCe, the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the calling MGW.

Step 416: After receiving the assignment request message, the called BSC starts to establish an air interface channel and an IP bearer with the called MGW, and after the air interface between the air interface and the called MGW is established, the called MSCe is sent to the called MSCe. The assignment completion message is sent, and the called terminal is notified by the called BS to ring.

Step 417: After receiving the 183 message, the calling MSCe sends a modify bearer message to the calling MGW, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the calling MGW, to notify the calling MGW to start. Establish an interoffice IP bearer with the called MGW, and notify the calling MGW to stop playing the ring back tone to the calling user.

Step 418: After receiving the modify bearer message, the calling MGW starts to establish an IP bearer with the called MGW, and after completing the establishment, returns a modify bearer response message to the calling MSCe.

Step 419: After receiving the modify bearer response message, the calling MSCe sends a temporary response (PRACK) message to the called MSCe for the 183 message.

Step 420: After receiving the temporary response message, the called MSCe returns a 200 response message to the calling MSCe.

Steps 421 to 423 are the same as steps 3 16 to 318.

It can be seen from the flow shown in Figures 2, 3 and 4 above that the assignment request message received by the called BSC carries the calling number and ringing information, so that the called BSC is established on the air interface channel and the called BSC. Immediately after the establishment of the IP bearer between the called MGW and the called MGW, the called terminal will notify the called terminal to ring. If the called user immediately responds, it is likely that the IP bearer between the calling BSC and the MGW has not been established yet. After the completion, or the interoffice IP bearer between the calling MGW and the called MGW has not been established, for example: In the interoffice call flow shown in Figure 3, the calling MSCe must receive the 180 message sent by the called MSCe. After learning the IP address information of the IP endpoint assigned by the called MGW to establish an IP bearer with the calling MGW, the information can be started. The inter-office IP bearer between the MGW and the called MGW is set up, and it takes a certain time to establish an inter-office IP bearer. If the called party has responded and the IP bearer has not been established or the IP bearer has failed to be established, the master and the called party cannot hear each other's voice, and the billing has started, and the abnormal line is also broken. , reducing the quality of the call, making the user experience satisfaction P low, and causing economic losses to the user. SUMMARY OF THE INVENTION The present invention provides a call method, system, and MSCe based on an IP bearer, so as to avoid a situation in which the called party has responded and the user does not hear the voice of the other party when the IP bearer has not been established, and the call quality is improved.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A call method based on IP bearer, the method comprising:

A. The MSCe receives the call setup request, and sends an increase endpoint request to the MGW requesting to establish an IP bearer related to itself in the current call;

B. The MSCe detects that the IP bearer associated with itself in the current call is established, and sends a ringing message to the called base station control center BSC to notify the called terminal to notify the called terminal to ring.

A call system based on IP bearer, comprising: MSCe, MGW and called BSC, wherein -.

The MSCe is configured to receive an external call setup request, send an add endpoint request for requesting to establish an IP endpoint of the call IP bearer to the MGW, and send a call to the called BSC when detecting that the call bearer is established. Ringing information

The MGW is configured to establish an IP bearer related to itself in the current call according to the request for adding an endpoint sent by the MSCe.

The called BSC is used to notify the called terminal to vibrate according to the ringing information sent by the MSCe. Bell.

An MSCe includes: an IP endpoint requesting module and a ringing information sending module, where: an IP endpoint requesting module receives an externally sent call setup request, and sends an IP terminal to the MGW to apply for establishing an IP bearer of the current call. Endpoint request

The ringing information sending module sends the ringing information to the called BSC when it detects that the call bearer is established.

After the MSCe detects that the bearer of the call is established, the MSCe sends the ringing information to the called BSC, and then the called BSC notifies the called terminal to ring, so that after the bearer of the call is successfully established, The called terminal rings again, which avoids the situation that the calling party and the called party cannot hear each other's voices due to the fact that the bearer has not been established, and the call quality is improved. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a softswitch architecture based on an IP bearer;

2 is a schematic diagram of a message flow of an existing intra-office call in a softswitch architecture based on an IP bearer of both the primary and the called BSC;

FIG. 3 is a schematic diagram 1 of a message flow of an existing interoffice call under the softswitch architecture of the primary, the called BSC, and the interoffice based on the IP bearer;

4 is a schematic diagram 2 of a message flow of an existing interoffice call under a softswitch architecture based on IP bearers between the primary and the called BSC and the interoffice;

5 is a call flow diagram provided by the present invention in an IP bearer-based softswitch architecture. FIG. 6 is a schematic diagram of a message flow of an intra-office call provided by the present invention under a softswitch architecture in which both the primary and the called BSCs are based on the IP bearer. ;

7 is a schematic diagram of a message flow of a first embodiment of an inter-office call provided by the present invention in a softswitch architecture based on an IP bearer between a primary, a called BSC, and an interoffice; 8 is a schematic diagram of a message flow of a second embodiment of an inter-office call provided by the present invention in a softswitch architecture based on an IP bearer between a primary, a called BSC, and an interoffice;

9 is a schematic diagram of a message flow of a third embodiment of an inter-office call provided by the present invention in a softswitch architecture based on an IP bearer between the primary and the called BSC and the interoffice;

10 is a composition diagram of an IP bearer-based call system according to an embodiment of the present invention; FIG. 11 is a composition diagram of an intra-office call system based on an IP bearer according to an embodiment of the present invention; FIG. 12 is an intra-office call provided by an embodiment of the present invention; Schematic diagram 1 of the MSCe in the system;

FIG. 13 is a schematic structural diagram of an MSCe in an intra-office call system according to an embodiment of the present invention; FIG.

FIG. 14 is a schematic structural diagram of an MSCe in an intra-office call system according to an embodiment of the present invention; FIG.

15 is a composition diagram of an inter-office call system based on an IP bearer according to Embodiment 1 of the present invention;

FIG. 16 is a structural diagram of an inter-office call system based on an IP bearer according to Embodiment 3 of the present invention. Mode for carrying out the invention

The embodiment of the present invention implements that after detecting that the bearers of the current call are all established, the MSCe sends the ringing information to the called BSC, and then the called BSC notifies the called terminal to ring.

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

FIG. 5 is a call flow diagram provided by the present invention in an IP bearer-based softswitch architecture. As shown in FIG. 5, the specific steps are as follows: Step 501: The MSCe receives the call setup request message, and sends an add endpoint message to the IGW to apply for establishing an IP endpoint of the current call IP bearer.

The call setup request message may be an intra-office call setup request message for establishing an intra-office call, or may be an inter-office call setup request message for establishing an inter-office call.

If the endpoint message is used to apply for establishing an IP bearer IP endpoint, the adding endpoint message may further carry detection request information for requesting reporting of an IP bearer setup event related to the IP endpoint, to request the MGW to be related to the IP address associated with the IP endpoint. After the bearer is established, the MSC is notified. Of course, the addendum message may not carry the request for reporting the IP bearer setup event related to the IP endpoint. At this time, the MGW will complete the IP bearer related to the IP endpoint. Proactively notify MSCe.

Step 502: The MSCe detects that the bearer of the current call is established, and sends a ringing message to the called BSC. .

Specifically, if the current call is an intra-office call, the MSCe detects that the call is established, and is divided into the following cases:

Case 1: The primary and the called BSC are both IP bearers. After the MSCe detects that the bearer of the call is established, it includes receiving the assignment completion message sent by the primary and the called BSC, and receiving the IP endpoint sent by the MGW. The indication message that the IP bearer is established between the calling BSC, and receives the indication message that the IP bearer between the IP endpoint and the called BSC is completed, or includes: receiving the assignment sent by the calling and the called BSC. The completion message receives an increase endpoint response message sent by the MGW indicating the IP endpoint address between itself and the called BSC; or includes: receiving the primary and the called BSC to indicate the relationship between the primary and the called BSC and the MGW. The IP bearer is updated with the update response message.

Case 2: The calling BSC is an IP bearer, and the called BSC is a TDM bearer. After the MSCe detects that the bearer of the call is established, the MSCe receives the assignment completion message sent by the calling BSC, and receives the called BSC. The assignment completion message, received 4 IP endpoints on the MGW and The indication message that the IP bearer is established between the calling BSCs, or includes: receiving the assignment completion message sent by the calling BSC, receiving the assignment completion message sent by the called BSC, and receiving the added endpoint sent by the MGW And responding to the message; or comprising: receiving a bearer update response message sent by the calling BSC to indicate that the IP bearer between the calling BSC and the MGW is established.

Case 3: The calling BSC is a TDM bearer, and the called BSC is an IP bearer. After the MSCe detects that the bearer of the call is established, the MSCe receives the assignment completion message sent by the calling BSC, and receives the called BSC. The assignment completion message receives the indication message that the IP bearer between the IP endpoint reported by the MGW and the called BSC is established; or includes: receiving the assignment completion message sent by the calling BSC, and receiving the called BSC. The assignment completion message receives the addendment response message sent by the MGW, or includes: receiving the bearer update response message sent by the called BSC to indicate that the IP bearer between the called BSC and the MGW is established.

If the call is an inter-office call, the MSCe detects that the call is established, and is divided into the following cases:

Case 1: The IP address is between the called office and the previous office, and the called BSC is the IP bearer. After the MSCe detects that the bearer of the call is established, the MSCe receives the previous one sent by the previous MSCe. The indication message that the IP bearer is established is received, and the assignment completion information sent by the called BSC is received, and the indication message that the IP bearer between the IP endpoint and the called BSC sent by the called MGW is completed is received. An indication message that the IP bearer between the IP endpoint sent by the MGW and the MGW of the previous office is established; or includes: the called MSCe receives the indication sent by the previous MSCe and establishes an IP bearer related to the previous office. The completed temporary response message for the 183 message receives the assignment completion information sent by the called BSC, and receives the added endpoint response message sent by the called MGW; or includes: the called MSCe receives the previous round of the MSCe. Receiving a temporary response message for the 183 message that has been established with the IP bearer associated with the previous office, and receiving a bearer update response message that is sent by the called BSC and the IP bearer between the called MGW is received, and received The called endpoint MGW sent an increased endpoint ringing Eliminate Case 2: The IP address is between the called office and the previous office, and the called BSC is a TDM bearer. After the MSCe detects that the bearer of the call is established, the called MSCe receives the previous one sent by the previous station MSCe. Receiving the indication message that the IP bearer is set up, receiving the assignment completion information sent by the called BSC, and receiving the indication message that the IP bearer between the IP endpoint sent by the called MGW and the MGW of the previous office is established; or The called MSCe receives the temporary response message for the 18X message, such as: 180 message or 183 message, which is sent by the previous station MSCe and the IP bearer associated with the previous station. The received BSC is sent by the called BSC. The assignment completion information is received, and an indication message that the IP bearer between the IP endpoint sent by the called MGW and the MGW of the previous office is established is received.

Here, if the IP address is between the called office and the previous office, the called MSCe may forward the next IP address after receiving the IP endpoint returned by the called MGW to establish an inter-office IP bearer with the MGW of the previous office. The MSCe sends a query notification message to request the previous MSCe to notify itself after the IP bearer associated with the previous office is established. The previous MSCe receives the query notification message and after the IP bearer associated with itself is established. The called MSCe may be notified by using a query notification response message or an IP bearer setup completion indication message; or, the previous office actively notifies the called MSCe after the interoffice IP bearer is established.

Case 3: The TDM bearer between the called office and the previous office, and the called BSC is an IP bearer. After the MSCe detects that the bearer of the call is established, the called MSCe receives the assignment completion information sent by the called BSC. Receiving an indication message that the IP bearer between the IP endpoint sent by the called MGW and the called BSC is established; or: the called MSCe receives the IP bearer established between the called BSC and the called MGW. The completed bearer update response information.

Step 503: After receiving the ringing information, the called BSC notifies the called terminal to ring. The following is a specific embodiment of the intra-office call in which the calling BSC and the called BSC are both IP bearers, and the inter-office call between the calling BSC, the called BSC, the calling office, and the called office. Specific embodiments of the call will be described in further detail to the present invention.

FIG. 6 is a schematic diagram of a message flow of an intra-office call provided by the present invention in the softswitch architecture of the calling BSC and the called BSC. The specific steps are as follows: Step 601 is the same as step 201.

Step 602: After receiving the CM service request message, the MSCe sends an Add Endpoint (ADD) message to the MGW, where the peer IP address information carried by the message is the IP address information of the calling BSC, to apply for establishing an IP bearer with the calling BSC. The IP endpoint, the message carries the bearer setup event detection request information at the same time, to request the MGW to notify itself after the IP bearer between the calling BSC and the calling BSC is established.

It can be seen that the difference between the step 602 and the step 202 is that the MSCe further sends the bearer setup event detection request information to the MGW to request the MGW to notify itself after the IP bearer is established with the calling BSC.

Steps 603 to 607 are the same as steps 203 to 207.

Step 608: After receiving the assignment completion message and the paging response message, the MSCe sends an add endpoint message to the MGW, where the peer IP address information carried by the message is the IP address information of the called BSC, to apply for establishing an IP with the called BSC. The bearer IP endpoint, the message carries the bearer setup event detection request information, and requires the MGW to notify itself after the IP bearer between the called BSC and the called BSC is established.

It can be seen that the difference between the step 608 and the step 208 is that the eNBe further sends the bearer setup event detection request information to the MGW to request the MGW to notify itself after the IP bearer is established with the called BSC.

Step 609 is the same as step 209.

Step 610: The MSCe sends an assignment request message to the called BSC, where the message carries the IP address information of the IP endpoint allocated by the MGW to establish an IP bearer with the called BSC.

The difference between step 610 and step 210 is: the assignment of the MSCe to the called BSC, please The request message does not carry the calling number and does not carry the ringing information. Therefore, after the air interface channel is established, the called BSC does not notify the called terminal to ring.

Step 611: After the established BSC establishes the IP bearer between the air interface channel and the MGW, the BSC sends an assignment completion message to the MSCe.

Since the ringing information is not carried in the assignment request message received by the called BSC, the called BSC does not notify the called terminal to ring after the air interface between the air interface and the called BSC and the MGW is established. : The called user does not know that there is a call.

Step 612: After receiving the assignment completion message sent by the primary and the called BSC, and receiving the indication message that the IP bearer sent by the MGW and the called BSC is completed, the MSCe sends the carried message to the called BSC. The calling number and the ringing information of the ringing information message (Alert with Information), after which the called BSC notifies the called terminal to ring through the called BS, and the MSCe informs the MGW to start playing to the calling side by modifying the bearer message. Ringback tone.

After the IP bearer between the IP address and the calling BSC is established, the MGW reports to the MSCe that the IP bearer is established between the IP address and the called BSC. After the completion, the indication message of the establishment of the IP bearer between the called BSC and the called BSC is reported to the MSCe.

Steps 613 to 615 are the same as steps 212 to 214.

If the MSCe does not receive the indication message that the MGW sends the IP bearer between the calling BSC and/or the called BSC within the predetermined time, the MSCe removes the called side resource and sends the message to the calling side. After the road abnormality information, the calling side resources are removed.

It is to be noted that, in the steps 602 and 608, the MSCe sends the ACK message to the MGW, and the bearer setup event detection request information may not be carried in the MG, and the MGW is pre-set after the IP bearer between the master and the called BSC is established. Actively reporting to the MSCe an indication message that the IP bearer is established between the primary and the called BSC; or, in step 603, the MGW sends the IP ^^ between the self and the calling BSC to the calling BSC. Increase end The point response message is sent, and in step 609, the MGW sends an end point response message to the called BSC after the IP bearer between itself and the called BSC is established.

FIG. 7 is a schematic diagram of a message flow of a first embodiment of an inter-office call provided by the present invention in a softswitch architecture based on an IP bearer between a calling BSC, a called BSC, a calling BMC, a calling office, and a called office, as shown in FIG. As shown, the specific steps are as follows:

Step 701 is the same as step 301.

Step 702: After receiving the CM service request message, the calling MSCe sends an Add Endpoint message to the calling MGW to apply for establishing two IP endpoints, and an IP endpoint is used to establish an IP bearer with the calling BSC. The peer IP address information is the IP address information of the calling BSC; the other IP endpoint is used to establish a bearer with the called MGW. The message carries the bearer setup event detection request information to notify the MSCe after the IP bearer is established.

It can be seen that the difference between the step 702 and the step 302 is that: the MSCe further carries the bearer setup event detection request information to the calling end MGW to request the calling MGW to notify itself after the IP bearer between the called MGW and the called MGW is established. .

Steps 703 to 708 are the same as steps 303 to 308.

Step 709: After receiving the paging response message, the called MSCe sends an add endpoint message to the called MGW. The peer IP address information carried by the message is: the IP address information of the calling MGW and the IP address information of the called BSC. Applying to establish two IP endpoints, one IP endpoint is used to establish an IP bearer with the calling MGW, and the added endpoint message corresponds to the carried IP address information of the host MGW as the IP address information; The BSC is called to establish an IP bearer, and the peer IP address information corresponding to the added endpoint message is the IP address information of the called BSC. The message carries the bearer setup event detection request information to notify the called MGW to notify itself after the IP bearer between the called BSC and the called MGW is established.

It can be seen that the difference between step 709 and step 309 is: the called MSCe is called to the called MGW. The sent enhanced endpoint message further carries bearer setup event detection request information to request the called MGW to notify itself after the IP bearer between the called BSC and the called MGW is established.

Step 710 is the same as step 310.

Step 711: The called MSCe sends an assignment request message to the called BSC, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the called BSC.

Step 711 is different from step 311 in that the called MSCe does not carry the calling number in the assignment request message sent to the called BSC, and does not carry the ringing information. Thus, the called BSC is on the air interface channel and the called BSC and MGW. After the IP bearer is established, the called terminal will not be notified to ring.

Step 712: The called MSCe sends a 183 message to the calling MSCe, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the calling MGW.

Step 713: The called MSCe sends a query notification message to the calling MSCe, and the message carries the calling MSCe bearer to establish the query information, so that the calling MSCe notifies itself after the calling party IP bearer is established.

Step 714: After receiving the 183 message, the calling MSCe sends a modify bearer message to the MGW, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the calling MGW, to be established and The inter-office IP bearer is called the MGW. The message carries the bearer setup event detection request information, and the calling MGW is required to notify itself after the inter-office IP bearer between the MGW and the called MGW is established.

Step 715 is the same as step 314.

Step 716: After detecting the establishment of the IP address of the calling office, the calling MSCe receives the assignment completion message sent by the calling BSC, and receives the IP bearer sent between the calling BSC and the calling BSC. And the information that the IP bearer is established with the called MGW, and sends a 200 response message to the called MSCe for the query notification message of step 713 to notify the called party. The IP bearer of the MSCe calling office is established.

Step 717: After detecting that the bearer of the current call is established, the called MSCe receives the assignment completion message sent by the called BSC, and receives the called BSC and the called MGW from the called MGW. The IP bearer is established with the information, and receives the 200 response message sent by the calling MSCe indicating that the IP address of the calling office is established, and sends a ringing information message carrying the calling number and the ringing information to the called BSC ( Alert with Information), at the same time, by modifying the bearer message, the called MGW starts to play the ring back tone to the calling side, and sends a 180 message to the calling MSCe.

Step 718: After receiving the ringing information message, the called BSC notifies the called terminal to ring through the called BS.

Step 719 721 is the same as steps 316 to 318.

It should be noted that, in step 702, the caller establishment event detection request information may not be carried in the incremental endpoint message sent by the calling MSCe to the calling MGW. In step 709, the called MSCe sends an endpoint message to the called MGW. The bearer setup event detection request information may not be carried in the same manner; in the same way, the step 713 may not be performed; and the caller MGW is pre-set to establish the IP bearer between the calling BSC and the called MGW, and then actively initiates the call to the calling MSCe. Evaluating the information that the IP bearer between the calling BSC and the called MGW is established; or/and pre-setting the calling MSCe to receive the assignment completion information sent by the calling BSC and the calling and calling by the calling MGW After the BSC and the IP bearer with the called MGW are all set up, the indication message of the IP address of the calling office is successfully reported to the called MSCe; or/and the called MGW is in the called BSC and the calling MGW. After the establishment of the IP bearer is completed, the indication message that the IP bearer between the called BSC and the calling MGW is established is reported to the called MSCe.

FIG. 8 is a message flow diagram of a second embodiment of an inter-office call provided by the present invention in a softswitch architecture based on an IP bearer between a calling BSC, a called BSC, a calling station, and a called office. Intention, as shown in Figure 8, the specific steps are as follows:

Steps 801 to 814 are the same as steps 401 and 414.

Step 815: The called MSCe sends an assignment request message to the called BSC, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the called BSC; and the called MSCe sends a 183 message to the calling MSCe. The message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the calling MGW.

It can be seen that the difference between step 815 and step 415 is that the assignment request message sent by the called MSCe to the called BSC does not carry the calling number and does not carry the ringing information, so that the called BSC is between the air interface channel and the called MGW. After the IP bearer is established, the called terminal will not be notified to ring.

Step 816: After receiving the assignment request message, the called BSC starts to establish an air interface channel and an IP bearer with the called MGW, and after the air interface channel and the IP bearer between the called MGW and the called MGW are established, the called MSCe is sent to the called MSCe. Send assignment completion message.

It can be seen that the difference between the step 816 and the step 416 is that the called BSC does not notify the called terminal to ring after the air interface between the air interface and the called MGW is established.

Steps 717 to 719 are the same as steps 417 to 419.

Step 820: After receiving the temporary response message, the called MSCe returns a 200 response message to the calling MSCe, and simultaneously sends a ringing information message carrying the calling number and the ringing information to the called BSC, and the called BSC receives the ringing message. After the information message, the called terminal is notified by the called BS to ring.

Steps 821 to 823 are the same as steps 421 to 423.

FIG. 9 is a schematic diagram of a message flow of a third embodiment of an inter-office call provided by the present invention in a softswitch architecture based on an IP bearer between a calling BSC, a called BSC, and a calling office and a called office. As shown in 9, the specific steps are as follows:

Step 901: The calling BSC sends a CM service request message to the calling MSCe, and the message is sent. Does not carry the IP address information of the calling BSC.

Step 902: The calling MSCe sends an assignment request message to the calling BSC to request to establish an air interface channel.

Step 903: After receiving the assignment request message, the calling BSC starts to establish an air interface channel, and after the establishment is completed, returns an assignment completion message to the calling MSCe, where the message carries the IP address information of the calling BSC.

Step 904: After receiving the assignment completion message, the calling MSCe sends an addendend message to the calling MGW, requesting to establish two IP endpoints, and an IP endpoint is used to establish an IP bearer with the calling BSC, and the added endpoint message is carried. The peer IP address information is the IP address information of the calling BSC; the other IP endpoint is used to establish an IP bearer with the called MGW.

Step 905: After receiving the Add Endpoint message, the calling MGW allocates an endpoint that establishes an IP bearer with the calling BSC, and allocates an IP endpoint that establishes an IP bearer with the called MGW, and allocates IP address information of the two IP endpoints. The bearer is sent to the calling MSCe in the Add Endpoint Response message. After that, the calling MSCe saves the IP address information of the two IP endpoints established by the calling MGW and establishing the IP bearer with the calling BSC and the called MGW.

Step 906: The calling MSCe sends a call request (INVITE) message to the called MSCe, where the message carries the IP address information of the IP endpoint allocated by the calling MGW to establish an IP bearer with the called MGW.

Step 907: After receiving the call request message, the called MSCe sends a paging request message to the called BSC, and sends a 180 message to the calling MSCe to notify the calling MSCe to play the ring back tone to the calling user.

Step 908: After receiving the 180 message, the calling MSCe returns a temporary response (PRACK) message for the 180 message to the called user.

Step Silver 909: After receiving the temporary response message, the called MSCe returns a 200 response message to the calling MSCe. Step 910: The calling MSCe sends a modify bearer message to the calling MGW to request the calling MGW to start playing the ring back tone to the calling user.

Step 911: After receiving the modify bearer message, the calling MGW starts playing a ring back tone to the calling user, and returns a modify bearer response message to the calling MSCe.

Step 912: After receiving the modify bearer response message, the calling MSCe sends a bearer update request message to the calling BSC, where the message carries the IP address information of the IP endpoint that is established by the calling MGW and establishes an IP bearer with the calling BSC.

Step 913: After receiving the bearer update request message, the calling BSC establishes an IP bearer with the MGW, and then returns a bearer update response message to the calling MSCe.

Step 914: After receiving the paging request message, the called BSC returns a paging response message to the called MSCe, where the message does not carry the IP address information of the called BSC.

Step 915: After receiving the paging response message, the called MSCe sends an assignment request message to the called BSC to request to establish an air interface channel.

The assignment request message does not carry the calling number and does not carry the ringing information.

Step 916: After receiving the assignment request message, the called BSC starts to establish an air interface channel, and after the establishment is completed, returns an assignment completion message to the called MSCe, where the message carries the IP address information of the called BSC.

Step 917: After receiving the assignment completion message, the called MSCe sends an Add Endpoint message to the called MGW to apply for establishing two IP endpoints, and an IP endpoint is used to establish an IP bearer with the calling MGW, and the added endpoint message is carried. The peer IP address information is the IP address information of the calling MGW, and the called MGW is notified to play the ringback tone to the calling user through the IP endpoint; the other IP endpoint is used to establish an IP bearer with the called BSC, and the endpoint message is added. The corresponding peer IP address information is the IP address information of the called BSC.

Step 918: After receiving the add endpoint message, the called MGW allocates an IP endpoint for establishing an IP bearer with the calling MGW, and plays a ring back tone to the calling user through the IP endpoint. At the same time, an IP endpoint for establishing an IP bearer with the called BSC is allocated, and the establishment is completed, and an add endpoint response message is returned to the called MSCe, where the message carries the IP address information of the two IP endpoints that are allocated. After that, the called MSCe saves the IP address information of the two IP endpoints established by the called MGW to establish an IP bearer with the calling MGW and the called BSC.

Step 919: The called MSCe sends a bearer update request message to the called BSC, where the message carries the IP address information of the IP endpoint that establishes the IP bearer with the called MGW, and sends a 183 message to the calling MSCe, where the message carries the called MGW assignment. The IP address information of the IP endpoint that establishes the IP bearer with the calling MGW.

Step 920: After receiving the bearer update request message, the called BSC starts to establish an IP bearer with the called MGW, and after the establishment is completed, sends a bearer update response message to the called MSCe.

Step 921: After receiving the 183 message, the calling MSCe sends a modify bearer message to the calling MGW, where the message carries the IP address information of the IP endpoint allocated by the called MGW to establish an IP bearer with the calling MGW, to notify the calling MGW to establish Inter-office IP bearer with the called MGW, and informs the calling MGW to stop playing the ring back tone to the calling user.

Step 922: After receiving the modify bearer message, the calling MGW starts to establish an IP bearer with the called MGW, and after the establishment is completed, returns a modify bearer response message to the calling MSCe.

Step 923: If the codec carried in the 183 message sent by the called MSCe is different from the codec used between the original calling MGW and the calling BSC, the calling MSCe sends a bearer update to the calling BSC after receiving the modify bearer response message. A request message carrying a codec between the calling MGW and the calling BSC.

Step 924: After receiving the bearer update request message, the calling BSC returns a bearer update response message to the calling MSCe.

Step 925: After receiving the bearer update response message, the calling MSCe sends a temporary response (PRACK) message for the 183 message to the called MSCe.

Step 926: After receiving the temporary response message, the called MSCe returns 200 to the calling MSCe. In response to the message, the ringing message carrying the calling number and the ringing information is sent to the called BSC at the same time. Step 927: After the called party answers, the called BSC sends a connection message to the called MSCe. Step 928: After receiving the connection message, the called MSCe notifies the called MGW to stop playing the ring back tone to the calling user by modifying the bearer message, and simultaneously sends a 200 response to the call request (INVITE) message to the calling MSCe to notify the main Called MSCe called has been answered.

Step 929: After receiving the 200 response message, the calling MSCe returns an acknowledgement (ACK) message to the called MSCe.

A call system applying the IP bearer-based calling method provided by the embodiment of the present invention is given below:

FIG. 10 is a structural diagram of an IP bearer-based call system according to an embodiment of the present invention. As shown in FIG. 10, the method mainly includes: an MSCelO MGW 102 and a called BSC103, where:

MSCelOl: is configured to receive an external call setup request, send an add endpoint request for requesting to establish an IP endpoint of the call IP bearer to the MGW 102, and, when detecting that the call IP bearer is established, to the called BSC 103 Send a ringing message.

Further, the MSCelO1 is configured to send, to the MGW 102, information requesting to report an IP bearer setup event with the current call, while sending an addend request to the MGW 102.

MGW102: Used to establish an IP bearer related to itself in this call according to the increased endpoint request sent by MSCelO1.

Called BSC103: Used to notify the called terminal to ring according to the ringing information sent by MSCelO1.

The intra-office call system using the IP bearer-based intra-office calling method provided by the embodiment of the present invention and the inter-office call system based on the IP bearer-based inter-office call method provided by the embodiment of the present invention are respectively given below:

FIG. 11 is a structural diagram of an intra-office call system based on an IP bearer according to an embodiment of the present invention, As shown in FIG. 11, it mainly includes: a calling BSC 100, an MSCel 01, an MGW 102, and a called BSC 103, where:

The calling BSC100: is used to send a CM service request message to the MSCelO1. If the IP address information of the IP endpoint sent by the MSCelO1 is received, the IP bearer between the host and the MGW 102 is established according to the IP address information, and the establishment is completed to the MSCarel. Send an IP bearer setup completion indication message.

Here, the IP bearer setup completion indication message may be an assignment completion message or a bearer update response message.

MSCelO1: used to receive the CM service request message sent by the calling BSC 100, and send an MGW 102 an addend request for applying for establishing an IP bearer between itself and the calling BSC 100 and/or the called BSC 103, and sending the MGW 102 for the MGW 102 Establishing IP address information of the IP endpoint of the calling BSC 100 and/or the called BSC 103, correspondingly sent to the calling BSC 100 and/or the called BSC 103, according to the return of the calling BSC 100 and/or the called BSC 103, and the MGW 102 The received indication message indicating that the IP bearer is established between the MGW 102 and the calling BSC 100 and/or the called BSC 103 is sent to the called BSC 103.

The MGW 102 is configured to allocate an IP endpoint for establishing an IP bearer between the UE and the calling BSC 100 and/or the called BSC 103 according to the increased endpoint request sent by the MSCel, and return the IP address information of the IP endpoint to the MSCarol. At the same time, the indication message that the IP bearer between the calling BSC 100 and/or the called BSC 103 is established is sent to the MSCelO1.

The called BSC103: If the IP address information of the IP endpoint sent by the MSCelO1 is received, the IP bearer between itself and the MGW 102 is established according to the IP address information, and the IP bearer setup completion indication message is sent to the MSCelO1; according to the MSCarel The ringing message sent, prompts the called terminal to ring. FIG. 12 is a schematic structural diagram of an MSCel10 in an intra-office call system in which both the primary and the called BSCs are IP bearers according to an embodiment of the present invention. As shown in FIG. 12, the method mainly includes: a calling side IP endpoint requesting module 1211, a main The calling side IP endpoint information sending module 1212, the called side IP endpoint requesting module 1213, the called side IP endpoint information sending module 1214 and the ringing information sending module 1215, wherein:

The calling side IP endpoint requesting module 1211 is configured to send an add endpoint request to the MGW 102 to apply for an IP endpoint for establishing an IP bearer with the calling BSC 100 after receiving the CM service request message sent by the calling BSC 100.

The calling side IP endpoint information sending module 1212 is configured to: after receiving the IP address information of the IP endpoint sent by the MGW 102 for establishing an IP bearer between the calling BSC 100 and the MGW 102, the IP address information is carried in the assignment request message. The call is sent to the calling BSC 100, and a paging request message is sent to the called BSC 103.

The called side IP endpoint requesting module 1213 is configured to: after receiving the paging response message sent by the called BSC 103, send an add endpoint request to the MGW 102 to apply for establishing an IP endpoint for the IP bearer with the called BSC 103.

The called side IP endpoint information sending module 1214 is configured to: after receiving the IP address information of the IP endpoint used by the MGW 102 to establish an IP bearer between the MGW 102 and the called BSC 103, carry the IP address information in the assignment request The message is sent to the called BSC103.

The ringing information sending module 1215 is configured to receive the assignment completion message sent by the calling BSC 100 and the called BSC 103, and receive the indication sent by the MGW 102 and the IP bearer between the calling BSC 100 and the called BSC 103 is established. After the message is indicated, the ringing information is sent to the called BSC 103.

FIG. 13 is a schematic structural diagram of an MSCelO1 in an intra-office call system in which only a calling BSC is an IP bearer according to an embodiment of the present invention. As shown in FIG. 13, the method mainly includes: a calling side IP endpoint requesting module 1311, and a calling side. IP endpoint information sending module 1312 and ringing information A module 1313 is provided, wherein:

The calling side IP endpoint requesting module 1311 is configured to send an add endpoint request to the MGW 102 after receiving the CM service request message sent by the calling BSC 100, to apply for the calling with the calling party.

The BSC100 establishes an IP endpoint for IP 7 delivery.

The calling side IP endpoint information sending module 1312 is configured to: after receiving the IP address information of the IP endpoint sent by the MGW 102 for establishing an IP bearer between the calling BSC 100 and the MGW 102, carrying the IP address information in the assignment request message Sent to the calling BSC100, and sent to the called

The BSC 103 sends a paging request message, and after receiving the paging response message returned by the called BSC 103, sends an assignment request message to the called BSC 103.

The ringing information sending module 1313 is configured to receive the assignment completion message sent by the calling BSC100 and the called BSC103, and receive the indication sent by the MGW 102 and the calling BSC100.

After the IP bearer completes the indication message, it sends a ringing message to the called BSC103.

FIG. 14 is a schematic structural diagram of an MSCel10 in an intra-office call system in which only the called BSC is an IP bearer according to an embodiment of the present invention. As shown in FIG. 14, the method mainly includes: a called side IP endpoint requesting module 1411, and a called side. The IP endpoint information sending module 1412 and the ringing information transmitting module 1413, wherein:

The called side IP endpoint requesting module 1411 is configured to send an assignment request message to the calling BSC100 after receiving the CM service request message sent by the calling BSC100, and simultaneously call the called party

The BSC 103 sends a paging request message, and after receiving the paging response message returned by the called BSC 103, sends an add endpoint request to the MGW 102 to apply for establishment with the called BSC 103.

The IP endpoint of the IP bearer.

The called side IP endpoint information sending module 1412 is configured to: after receiving the IP address information of the IP endpoint used by the MGW 102 to establish an IP bearer between the MGW 102 and the called BSC 103, carry the IP address information in the assignment request The message is sent to the called BSC103.

Ringing information sending module 1413: used to receive the calling BSC100 and the called BSC103 After the received completion message is received, and after receiving the indication message sent by the MGW 102 and the IP bearer established between the called BSC, the ringing information is sent to the called BSC 103.

15 is a composition diagram of an inter-office call system based on an IP bearer according to Embodiment 1 of the present invention. In this embodiment, the called MGW and the MGW of the previous office of the called office are IP bearers, and the called MGW and the called The called BSC is also an IP bearer, as shown in Figure 15, which mainly includes: the called MSCel01, the called MGW102, the called BSC103 and the previous station MSCel04, where:

The called MSCarelOl: is used to receive the IP bearer setup completion indication message sent by the previous station MSCar04, and receive the indication message that the IP bearer established between the called MGW 102 and the MGW of the previous office is completed, and the received message is received. After receiving the indication message that the IP bearer between the called BSC and the called BSC is completed, and receiving the assignment completion message sent by the called BSC 103, the ringing information is sent to the called BSC 103.

The called MGW102: is configured to send an indication message that the IP bearer between the MGW and the previous MGW is established after detecting that the IP bearer between the MGW and the previous MGW is established; When the IP bearer between the BSCs is established, an indication message that the IP bearer is established with the called BSC is sent to the called MSCelO1.

The called BSC103: is used to send an assignment completion message to the called MSCelO1 after detecting that the air interface channel of itself is established, and detecting that the IP bearer between itself and the called MGW 102 is established; according to the vibration sent by the called MSCelOl The bell information prompts the called terminal to ring.

The previous MSCel04 is used to send an IP bearer setup completion indication message to the called MSCelO1 when the IP bearer associated with itself is detected.

The inter-office call system based on the IP bearer provided in the second embodiment of the present invention is shown below. In this embodiment, the called MGW and the MGW of the previous office of the called office are IP bearers, and the called MGW and the called BSC are called. It is not IP bearer, as shown in Figure 16, it mainly includes: MSCelO1, called MGW102, called BSC103 and previous station MSCar04, where: Called MSCelOl: used to receive the IP bearer setup completion indication message sent by the previous station MSCel04, and receive the indication sent by the called MGW102. After receiving the indication message that the IP bearer is established between the MGWs of the previous station, and receiving the assignment completion message sent by the called BSC 103, the ringing information is sent to the called BSC 103.

The called MGW 102: is configured to send an indication message that the IP bearer setup with the MGW of the previous station is completed to the called MSCelO1 after detecting that the IP bearer between the MGW and the MGW of the previous station is established.

The called BSC103: is configured to send an assignment completion message to the called MSCelO1 when detecting that the air interface channel of the air interface is established; and prompting the called terminal to ring according to the ringing information sent by the called MSCelO1.

16 is a composition diagram of an inter-office call system based on an IP bearer according to Embodiment 3 of the present invention. In this embodiment, the called MGW and the MGW of the previous office of the called office are not IP bearers, and the called MGW is called The IP bearer is connected to the called BSC. As shown in FIG. 16, it mainly includes: the called MSCel01, the called MGW 102, and the called BSC 103, where:

The called MSCarel1: is used to receive the indication message that the IP bearer between the called MGW 102 and the called BSC is completed, and after receiving the assignment completion message sent by the called BSC 103, send the vibration to the called BSC103. Bell information.

The called MGW 102: is configured to send an indication message that the IP bearer established between the called BSC and the called BSC is completed after detecting that the IP bearer between the self and the called BSC is established.

The called BSC103: is used to send the called MSCelO1 when it detects that the air interface channel is established and detects that the IP bearer between itself and the called MGW102 is established. The assignment completion message; prompts the called terminal to ring according to the ringing information sent by the called MSCelOl.

It can be seen from the above embodiment that after detecting that the bearer of the current call is established, the MSCe sends the ringing information to the called BSC, and then the called BSC notifies the called terminal to ring, so that the bearer in the call is made. After the successful establishment is completed, the called terminal rings again, which avoids the situation that the host and the called user cannot hear each other's voice caused by the bearer not being established, which improves the call quality and avoids abnormal disassembly. At the same time, it also avoids the situation that the billing is also performed before the bearer is established or the establishment fails, and the economic loss of the user is eliminated.

The above is only the embodiment of the process and method of the present invention, and is not intended to limit the present invention. Any modifications, equivalents, improvements, etc. made within the spirit and principles of the present invention should be included in the present invention. Within the scope of protection.

Claims

Claim

A call method based on an internet protocol bearer, characterized in that the method comprises:

A. The mobile softswitch center receives the call setup request, and sends an increase endpoint request to the media gateway MGW to establish an IP bearer related to itself in the current call;

2. The method according to claim 1, wherein the step A increases the endpoint request to add an endpoint request for establishing an IP endpoint,

And the adding endpoint request carries information that requests to report an IP bearer setup event related to the IP endpoint.

3. The method according to claim 1, wherein the call setup in step A is: an intra-office call setup request.

4. The method of claim 3, wherein both the calling BSC and the called BSC are based on an IP bearer.

And the step A and B further include: the MSCe receives the assignment completion message sent by the calling BSC and the called BSC, and receives the IP bearer sent between the calling BSC and the called BSC sent by the MGW. The completed instruction message.

5. The method of claim 3, wherein both the calling BSC and the called BSC are based on an IP bearer.

And the step Between the A and the B further comprises: the MSCe receiving the assignment completion message sent by the calling BSC and the called BSC, and receiving the IP endpoint address sent by the MGW to indicate the MGW and the primary and the called BSC. Increase the endpoint response message.

6. The method of claim 3, wherein both the calling BSC and the called BSC are based on an IP bearer.

And the step A and B further comprise: the MSCe receiving the bearer update response message sent by the calling BSC and the called BSC.

7. The method of claim 3, wherein only the calling BSC is based on an IP bearer,

And the step A and B further comprise: the MSCe receives the assignment completion message sent by the calling BSC and the called BSC, and receives an indication message that the IP bearer sent by the MGW and the calling BSC is established.

8. The method of claim 3, wherein only the calling BSC is based on an IP bearer,

And the step A and B further comprise: the MSCe receives the assignment completion message sent by the calling BSC and the called BSC, and receives the increased endpoint response message sent by the MGW.

9. The method of claim 3, wherein only the calling BSC is based on an IP bearer,

And the step A and B further comprise: the MSCe receiving the bearer update response message sent by the calling BSC.

10. The method of claim 3, wherein only the called BSC is based on an IP bearer,

And the step A and B further include: the MSCe receives the assignment completion message sent by the calling BSC and the called BSC, and receives an indication message that the IP bearer sent by the MGW and the called BSC is established.

11. The method of claim 3, wherein only the called BSC is based on an IP bearer,

And the step A and B further include: the MSCe receives the calling BSC and the called party The assignment completion message sent by the BSC receives an addend response message sent by the MGW.

12. The method of claim 3, wherein only the called BSC is based on an IP bearer,

And the step A and B further comprise: the MSCe receiving the bearer update response message sent by the called BSC.

13. The method according to claim 1, wherein the call setup request in step A is: an inter-office call setup request.

The method according to claim 13, wherein the called MGW and the MGW of the previous office of the called office are IP bearers, and the called MGW and the called BSC are IP bearers, and the step A is And the B further includes: the called MSCe receives the indication message that the IP bearer sent by the called BSC and the called MGW is completed, and receives the IP 7| and the IP address between the called and the called BSC sent by the called MGW. The IP bearer between the MGWs of the previous station has completed the indication message, and receives the indication message that the IP bearer sent by the previous station MSCe is established.

The method according to claim 13, wherein the called MGW and the MGW of the previous office of the called office are IP bearers, and the called MGW and the called BSC are IP bearers, and the step A is The method further includes: the called MSCe receives the assignment completion message sent by the called BSC, receives the added endpoint response message sent by the called MGW, and receives the temporary response message sent by the previous station MSCe for the 183 message. .

The method according to claim 13, wherein the called MGW and the MGW of the previous office of the called office are IP bearers, and the called MGW and the called BSC are IP bearers, and the step A is The method further includes: the called MSCe receives the bearer update response message sent by the called BSC, receives the added endpoint response message sent by the called MGW, and receives the temporary response message sent by the previous station MSCe for the 183 message. .

17. The method of claim 13 wherein the called MGW and the called party The MGW between the MMCs of the previous office is an IP bearer, and the called MGW and the called BSC are not IP bearers.

And the step Between the A and the B, the MSCe receives the indication message that the MSC bearer sent by the previous MSCe is established, and receives the assignment completion message sent by the called BSC. And receiving an indication message that the IP bearer sent by the called MGW and the MGW of the previous station is established.

The method according to claim 14 or 17, wherein after the step A, the called MSCe receives an indication that the IP bearer associated with the previous office sent by the previous station MSCe is established. Before the message, the method further includes: the called MSCe sends a query notification message for querying whether the IP bearer associated with the previous office is established, and the previous station MSCe receives the query notification message and is in the same state After the IP bearer related to the IP endpoint is established, the IP bearer setup completion indication message is sent to the called MSCe.

The method according to claim 13, wherein the called MGW and the MGW of the previous office of the called office are IP bearers, and the called MGW and the called BSC are IP bearers, and the step A is And the B further includes: the called MSCe sends a query notification message for querying whether the IP bearer associated with the previous office is established, and the previous station MSCe receives the query notification message and is After the IP bearer related to the IP endpoint is established, the query notification message is sent to the called MSCe.

The method according to claim 13, wherein the called MGW and the MGW of the previous office of the called office are not IP bearers, and the called MGW and the called BSC are IP bearers.

And the step A and B further comprise: the called MSCe receives the assignment completion message sent by the called BSC, and receives an indication message that the IP bearer sent by the called MGW and the BSC is established.

21. The method of claim 13 wherein the called MGW and the called party The MGW of the previous office of the bureau is not an IP bearer, and the called MGW and the called BSC are IP bearers.

And the step A and B further comprise: the called MSCe receives the called BSC to send an update response message.

22. An IP bearer-based call system, comprising: MSCe, MGW, and called BSC, wherein:

The called BSC is used to notify the called terminal to ring according to the ringing information sent by the MSCe.

The system according to claim 22, wherein the MSCe is further configured to: when sending an addend request to the MGW, send a request to the MGW to request the IP bearer setup event information.

The system according to claim 22, wherein the calling system is an intra-office call system, and both the calling BSC and the called BSC in the system are based on an IP bearer, and the MSCe includes: a calling side The IP endpoint request module, the calling side IP endpoint information sending module, the called side IP endpoint requesting module, the called side IP endpoint information sending module, and the ringing information sending module, where:

The calling side IP endpoint requesting module is configured to send an add endpoint request to the MGW to apply for an IP endpoint for establishing an IP bearer with the calling BSC according to the call setup request sent by the calling BSC;

The calling side IP endpoint information sending module is configured to receive the call originating from the MGW for establishing the calling party The IP address information of the IP bearer carried by the IP between the BSC and the MGW, and the IP address information is sent to the calling BSC;

The called side IP endpoint requesting module is configured to send an add endpoint request to the MGW to apply for an IP endpoint for establishing an IP bearer with the called BSC;

The called side IP endpoint information sending module is configured to receive the MGW for sending

The IP address information of the IP bearer of the IP bearer between the MGW and the called BSC, and the IP address information is sent to the called BSC;

The ringing information sending module is configured to receive an indication message that the IP address between the MGW and the MGW is completed after receiving the indication sent by the calling BSC and the called BSC, and receive the indication sent by the MGW and the primary and the called BSC. After the IP bearer completes the indication message, it sends the ringing information to the called BSC.

The system according to claim 22, wherein the calling system is an intra-office calling system, and only the calling BSC is based on the IP bearer in the system.

The MSCe includes: a calling side IP endpoint requesting module, a calling side IP endpoint information sending module, and a ringing information sending module, where:

The calling side IP endpoint information sending module is configured to receive the IP address information of the IP endpoint sent by the MGW to establish an IP bearer between the calling BSC and the MGW, and send the IP address information to the calling BSC;

The ringing information sending module is configured to receive an indication message that the IP bearer between the MGW and the MGW is completed after receiving the indication sent by the calling BSC, and receive an indication that the IP bearer between the MGW and the calling BSC is established. After the message, the ringing information is sent to the called BSC.

26. The system of claim 22, wherein the calling system is a bureau Internal call system, and only the called BSC is based on IP bearer in the system.

The MSCe includes: a called side IP endpoint requesting module, a called side IP endpoint information sending module, and a ringing information sending module, where:

The called side IP endpoint information sending module is configured to receive the IP address information of the IP endpoint sent by the MGW for establishing an IP bearer between the MGW and the called BSC, and send the IP address information to the called BSC;

The ringing information sending module is configured to receive an indication message that the IP bearer between the indication sent by the called BSC and the MGW is completed, and receive an indication that the indication sent by the MGW and the IP bearer between the called BSC is completed. After the message, the ringing information is sent to the called BSC.

The system according to claim 22, wherein the calling system is an inter-office call system, the MSCe is a called MSCe, the MGW is a called MGW, and the called MGW in the system The MGW between the MGW and the called BSC is the IP bearer between the MGW and the called BSC.

The system further includes: a previous MSCe of the called office, configured to send an IP bearer setup completion indication message to the called MSCe when detecting that the IP bearer associated with the call is established in the current call;

The called MGW is further configured to: send an indication message that the IP bearer between the MGW and the MGW of the previous station is established to the called MSCe, and send an indication that the IP bearer of the called BSC I can be established to the called MSCe. Message

The called BSC is further configured to send an indication message that the IP bearer between the UE and the called MGW is established to the called MSCe.

The system of claim 22, wherein the calling system is an inter-office call system, the MSCe is a called MSCe, and the MGW is a called MGW. Moreover, the called MGW in the system and the MGW of the previous office of the called office are IP bearers, and the called MGW and the called BSC are not IP bearers.

The system further includes: a previous MSCe of the called office, configured to send an IP bearer setup completion indication message to the called MSCe when detecting that the IP bearer associated with itself is established;

The called MGW is further configured to send an indication message that the IP bearer between the MGW and the MGW of the previous station is established to the called MSCe.

The system according to claim 22, wherein the calling system is an inter-office call system, the MSCe is a called MSCe, the MGW is a called MGW, and the called MGW in the system It is not an IP bearer between the MGW of the previous office of the called office, and the IP bearer between the called MGW and the called BSC.

The called MGW is further configured to: send an indication message that the IP bearer between the self and the called BSC is established to the called MSCe;

30. An MSCe, comprising: an IP endpoint requesting module and a ringing information sending module, where:

The IP endpoint requesting module receives an external call setup request, and sends an add endpoint request to the MGW for applying for establishing an IP endpoint of the call IP bearer;

The ringing information sending module, when detecting that the call bearer is established, is called to the called party

The BSC sends a ringing message.