WO2013097250A1

WO2013097250A1 - Call establishment method, device and system for voice over internet protocol

Info

Publication number: WO2013097250A1
Application number: PCT/CN2011/085205
Authority: WO
Inventors: 汪红星
Original assignee: 华为技术有限公司
Priority date: 2011-12-31
Filing date: 2011-12-31
Publication date: 2013-07-04
Also published as: CN103548330A; CN103548330B

Abstract

A VoIP call establishment method, including: receiving a first call request sent by a calling device; when it is determined that the calling device is located under an NAT device, allocating a media address of an initiation side SBC for connecting a called device; sending to a receiving side SBC a second call request which carries the media address of the initiation side SBC for connecting the called device, so that when it is determined that the access media domains of the calling device and the called device are the same, the receiving side SBC transfers the media address of the initiation side SBC for connecting the called device to the called device; receiving a second call response sent by the receiving side SBC and carrying the media address of the called device, so as to establish a VoIP call connected between the initiation side SBC and the called device; and sending a third call response to the calling device, so as to establish a VoIP call connected between the initiation side SBC and the calling device. In addition, also provided are another three VoIP call establishment methods and a corresponding device and system.

Description

Network telephone establishing call method, device and system

Technical field

The present invention relates to the field of communications technologies, and in particular, to a VoIP (VoIP over Internet Protocol) call setup method, apparatus, and system.

Background technique

In the case of VoIP (VoIP over Internet Protocol), the analog voice signal (Voice) is digitized and made in the form of a data packet on the Internet Protocol Network (IP Network). Pass in real time. The biggest advantage of VoIP is that it can widely use the Internet (Internet) and the Internet (Internet Protocol) interconnection environment to provide more and better services than traditional telephone services.

The Session Border Controller (SBC) is a device used in a VoIP network. It is usually used to manage signaling such as session establishment, transmission, and teardown in VoIP calls, and to manage media data streams in VoIP calls. The calling user equipments can be located under the same session border controller or under different session border controllers. In the prior art, many users, especially enterprise users, generally access the access bearer network through a Network Address Translation (NAT) device when accessing the network, at this time, under different SBCs. For the user equipment (including the fixed terminal and the mobile terminal), the current technical solution requires that the media data stream must be carried by the core network, that is, the media data stream must pass through the SBC; for example, the user equipment 1 sends the media data stream to the user equipment. 2, for example, where the NAT device of the user equipment 1 is "NAT device 1", the SBC of the user equipment 1 is "SBC1", the NAT device of the user equipment 2 is "NAT device 2", and the SBC of the user equipment 2 is "SBC2". " , then the direction of the media data stream is: "User Equipment 1 -> NAT Equipment 1 -> Access Bearer Network - a > SBC1 - -> Core Bearer Network - a > SBC2 - - > Access Bearer Network - >NAT device 2 -> > User device 2".

In the research and practice of the prior art, the inventors of the present invention have found that for such a call party, at least one user equipment that needs to pass through a NAT device and is located under a different SBC needs to be VoIP called. Occupying core network bandwidth, it wastes network resources.

Summary of the invention

The embodiment of the invention provides a method, a device and a system for establishing a VoIP call, which can save network resources without occupying the bandwidth of the core network. A method for establishing a VoIP call, including:

Receiving a first call request sent by the calling device;

And determining, according to the first call request, that the calling device is located under the NAT device, and allocating a media address for connecting the originating side SBC of the called device;

Sending a second call request to the receiving side SBC, where the second call request carries a media address for connecting the originating side SBC of the called device, so that the receiving side SBC determines that the access media domain to which the calling device belongs is associated with the called device. When the media domain is the same, the media address of the originating side SBC for connecting to the called device is delivered to the called device;

Receiving a second call response sent by the receiving side SBC, where the second call response carries a media address of the called device, to establish a VoIP call connection between the originating side SBC and the called device;

A third call response is sent to the calling device to establish a VoIP call connection between the originating side SBC and the calling device.

A method for establishing a VoIP call, including:

Receiving a second call request sent by the sending side SBC, where the second call request carries a media address for connecting the originating side SBC of the called device;

When the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address used to connect the originating side SBC of the called device is used as the medium for connecting the receiving side SBC of the called device. Address, sending a third call request to the called device;

Receiving a first call response returned by the called device;

Sending a second call response to the originating side SBC according to the first call response, the second call response carrying the media address of the called device to establish a VoIP call connection between the originating side SBC and the called device, and establishing an originating side SBC A VoIP call connection to the calling device.

A method for establishing a VoIP call, including:

Receiving a first call request sent by the calling device;

Sending a fourth call request to the receiving side SBC according to the first call request, where the fourth call request carries the media address of the calling device, so that the receiving side SBC determines that the called device is located under the NAT device, and the fourth call request carries When the media address of the calling device is the same as the access media domain to which the called device belongs, the media address of the receiving side SBC for connecting the calling device is allocated; Receiving a fourth call response returned by the receiving side SBC, where the fourth call response carries a media address for connecting the receiving side SBC of the calling device;

Determining that the fourth call response carries a media address for connecting the receiving side SBC of the calling device, and the accessing media domain to which the calling device belongs is the same as the accessing media domain to which the called device belongs. The media address of the receiving side SBC serves as a media address for connecting the originating side SBC of the calling device, and sends a fifth call response to the calling device to establish a VoIP call connection between the receiving side SBC and the calling device.

A method for establishing a VoIP call, including:

Receiving a fourth call request sent by the sending side SBC, where the fourth call request carries a media address of the calling device;

Determining that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs. Calling the media address of the receiving side SBC of the device;

Sending a fifth call request to the called device according to the fourth call request;

Receiving a first call response returned by the called device to establish a VoIP call connection between the receiving side SBC and the called device;

Sending a fourth call response to the originating side SBC according to the first call response, where the fourth call response carries a media address for connecting the receiving side SBC of the calling device, so that the originating side SBC determines that the fourth call response is carried for connecting the main When the media address of the receiving side SBC of the device is called, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address of the receiving side SBC for connecting the calling device is used as The media address of the originating side SBC of the calling device is connected, and the fifth call response is sent to the calling device to establish a VoIP call connection between the receiving side SBC and the calling device.

A VoIP call setup device, including:

a first receiving unit, configured to receive a first call request sent by the calling device;

An allocating unit, configured to allocate, according to the first call request, a media address used to connect the originating side SBC of the called device when the calling device is located under the NAT device;

a first sending unit, configured to send a second call request to the receiving side SBC, where the second call request carries a media address used to connect the originating side SBC of the called device, so that the receiving side SBC determines the main When the access media domain to which the device belongs is the same as the access media domain to which the called device belongs, the media address for connecting the originating side SBC of the called device is transmitted to the called device;

a second receiving unit, configured to receive a second call response sent by the receiving side SBC, where the second call response carries a media address of the called device, to establish a VoIP call connection between the originating side SBC and the called device;

The second sending unit is configured to send a third call response to the calling device to establish a VoIP call connection between the originating side SBC and the calling device.

A VoIP call setup device, including:

a first receiving unit, configured to receive a second call request sent by the initiating side SBC, where the second call request carries a media address used to connect the originating side SBC of the called device;

The first sending unit is configured to determine, when the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address used to connect the originating side SBC of the called device as a connection for the called party The media address of the receiving side SBC of the device, sending a third call request to the called device

a second receiving unit, configured to receive a first call response returned by the called device;

a second sending unit, configured to send a second call response to the originating side SBC according to the first call response, where the second call response carries the media address of the called device to establish a VoIP call between the originating side SBC and the called device Connect, and establish a VoIP call connection between the originating side SBC and the calling device.

A VoIP call setup device, including:

a first sending unit, configured to send a fourth call request to the receiving side SBC according to the first call request, where the fourth call request carries the media address of the calling device, so that the receiving side SBC determines that the called device is located under the NAT device, and When the fourth call request carries the media address of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address for connecting the receiving side SBC of the calling device is allocated;

a second receiving unit, configured to receive a fourth call response returned by the receiving side SBC, where the fourth call response carries a media address used to connect the receiving side SBC of the calling device;

a second sending unit, configured to determine that the fourth call response carries a media address used to connect the receiving side SBC of the calling device, and the access media domain to which the calling device belongs and the access media domain to which the called device belongs At the same time, the media address of the receiving side SBC for connecting the calling device is used as the media address for connecting the originating side SBC of the calling device, and the fifth call response is sent to the calling device to establish the receiving side SBC and the main Call a VoIP call connection between devices.

A VoIP call setup device, including:

a first receiving unit, configured to receive a fourth call request sent by the sending side SBC, where the fourth call request carries a media address of the calling device;

The allocating unit determines that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the accessing media domain to which the calling device belongs is the same as the accessing media domain to which the called device belongs. a media address connected to the receiving side SBC of the calling device;

a first sending unit, configured to send a fifth call request to the called device according to the fourth call request, and a second receiving unit, configured to receive the first call response returned by the called device, to establish a receiving side

a VoIP call connection between the SBC and the called device;

a second sending unit, configured to send a fourth call response to the originating side SBC according to the first call response, where the fourth call response carries a media address for connecting the receiving side SBC of the calling device, so that the initiating side SBC determines the fourth When the call response carries the media address of the receiving side SBC of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the receiving side for connecting the calling device is used. The media address of the SBC is used as a media address for connecting the originating side SBC of the calling device, and sends a fifth call response to the calling device to establish a VoIP call connection between the receiving side SBC and the calling device.

A communication system includes any of the VoIP call setup devices provided by the embodiments of the present invention.

In the embodiment of the present invention, when determining that the calling device is located under the NAT device, the media address of the originating side SBC for connecting to the called device is allocated, and is transmitted to the called device, and is subsequently received and returned to carry the called device. The media address is used to establish a VoIP call connection between the calling device, the originating side SBC, and the called device, so that the receiving side SBC can be bypassed when the media data stream is transmitted, so that the media data stream does not pass through the core network ( That is, bypassing the core network), to achieve the purpose of saving transmission bandwidth.

Similarly, another solution provided by the embodiment of the present invention is to determine that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the access device belongs to the access media domain and is When the access media domain to which the device belongs is the same, the media address of the receiving side SBC for connecting to the calling device is allocated, and when the first call response returned by the called device is subsequently received, the connection is used for the connection. The media address of the receiving side SBC of the calling device is transmitted to the calling device to establish a VoIP call connection between the calling device, the receiving side SBC and the called device, thereby bypassing the transmission of the media data stream. The side SBC enables the media data stream to pass through the core network (ie, bypass the core network), thereby achieving the purpose of saving transmission bandwidth.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings used in the description of the embodiments will be briefly described below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those skilled in the art, other drawings may be obtained according to these drawings without any creative work.

1 is a flowchart of a method for establishing a VoIP call according to an embodiment of the present invention;

2 is another flowchart of a method for establishing a VoIP call according to an embodiment of the present invention;

Figure 3a is a schematic diagram of a scenario of bypassing the receiving side SBC;

FIG. 3b is another schematic diagram of bypassing the receiving side SBC;

FIG. 3 is a flowchart of an application example of a method for establishing a VoIP call according to an embodiment of the present invention; FIG. 4 is still another flowchart of a method for establishing a VoIP call according to an embodiment of the present invention;

FIG. 5 is still another flowchart of a method for establishing a VoIP call according to an embodiment of the present invention;

FIG. 6a is a schematic diagram of a scenario of bypassing the originating side SBC;

FIG. 6 is a flowchart of another application example of a VoIP call setup method according to an embodiment of the present invention; FIG. 7 is a schematic structural diagram of a network telephone call setup apparatus according to an embodiment of the present invention; FIG. 7b is a network according to an embodiment of the present invention; FIG. 8 is another schematic structural diagram of a network telephone call establishing apparatus according to an embodiment of the present invention; FIG. 9 is another schematic structural diagram of a network telephone call establishing apparatus according to an embodiment of the present invention; FIG. 10 is still another schematic structural diagram of a network telephone call establishing apparatus according to an embodiment of the present invention.

detailed description

BRIEF DESCRIPTION OF THE DRAWINGS The technical solutions in the embodiments of the present invention will be described in detail below with reference to the accompanying drawings. All other embodiments obtained by a person skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.

Embodiments of the present invention provide a method, an apparatus, and a system for establishing a VoIP call. The following are detailed Detailed description.

Embodiment 1

This embodiment will be described from the perspective of the SBC on the calling device side. For the convenience of description, in the embodiment of the present invention, the SBC on the calling device side is referred to as the initiating side SBC, and the SBC in the called device side is referred to as receiving. Side SBC.

A method for establishing a VoIP call, comprising: receiving a first call request sent by a calling device; and determining, when determining that the calling device is located under the NAT device according to the first call request, allocating a media address for connecting the originating side SBC of the called device; Sending a second call request to the receiving side SBC, where the second call request carries a media address for connecting the originating side SBC of the called device, so that the receiving side SBC determines that the access media domain to which the calling device belongs and the access of the called device belong to When the media domain is the same, the media address of the originating SBC of the called device is transmitted to the called device; the second call response sent by the receiving side SBC is received, and the second call response carries the media address of the called device. To establish a VoIP call connection between the originating side SBC and the called device; send a third call response to the calling device to establish a VoIP call connection between the originating side SBC and the calling device.

As shown in Figure 1, the specific process can be as follows:

The call request for establishing a VoIP connection sent by the calling device is received. For the convenience of description, in the embodiment of the present invention, the call request for establishing a VoIP connection is referred to as a first call request.

The first call request includes a media address of the calling device, indicating that the first call request is from the calling device, so that the receiving end can subsequently return a corresponding response to the calling device.

It should be noted that the media address in the embodiment of the present invention may include information such as an Internet Protocol (IP) address and a port.

102. When determining that the calling device is located under the NAT device according to the first call request, allocate a media address for connecting the originating side SBC of the called device.

Specifically, the session initiating protocol (SIP) of the calling device can be used to learn whether the calling device is located under the NAT device. For example, after receiving the first call request, the initiating side SB C determines the first If a call request is from the terminal A, the previous SIP registration process of the terminal A can be used to determine whether the calling device is located under the NAT device.

103. Send a second call request to the receiving side SBC.

The second call request carries a media address for connecting the originating side SBC of the called device. In this way, after receiving the second call request, the receiving side SBC determines that the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, and the second call request carries the connection device for connecting to the called device. Initiating the media address of the side SBC, determining that the receiving side SBC can be bypassed, and then transmitting the media address for connecting the originating side SBC of the called device to the called device as the media address of the receiving side SBC, so that the called device The VoIP call connection is established directly with the originating side SBC without passing through the receiving side SBC.

For example, the second call request may specifically carry a media address for connecting the originating side SBC of the called device by using an extension of the media level a line in the Session Description Protocol (SDP).

In addition, the second call request may further include the access media domain information (ie, IP domain information) of the calling device, where the access media domain information of the calling device indicates the access media domain to which the calling device belongs, so that the receiving side The SBC can learn the access media domain to which the calling device belongs. Of course, the access media domain information of the calling device can also be obtained through other means, for example, the SIP access registration process is used to learn the access media of the calling device according to the second call request. Domain information, and so on. In addition, the access media domain to which the called device belongs can also be learned through the SIP registration process, and details are not described herein.

104. Receive a second call response sent by the receiving side SBC, where the second call response carries a media address of the called device to establish a VoIP call connection between the originating side SBC and the called device.

After the originating side SBC receives the second call response, the VoIP call connection between the originating side SBC and the called device is completed.

The second call response may specifically carry the media address of the called device by using an extension of the media level a line in the SDP.

In addition, the second call response may further include the access media domain information of the called device, where the access media domain information of the called device indicates the access media domain to which the called device belongs, so that the originating SBC can learn the called device. Accessing the media domain, of course, the access media domain information of the called device can also be obtained by other means, for example, after receiving the second call response, the called device is learned by the SIP registration process according to the second call response. Access media domain information, and more.

105. Send a third call response to the calling device to establish a VoIP call connection between the originating side SBC and the calling device.

After the calling device receives the third call response from the originating side SBC, the originating side SBC and the master A VoIP call connection between devices is called to build.

For example, before sending the third call response to the calling device, specifically, a media address for the originating side SBC of the calling device may be allocated, and then determining that the second call response carries the media address of the called device, and When the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address of the originating side SBC to the calling device and the media address of the originating side SBC for connecting the called device are internally established. The media session connection between the two, so that the "VoIP call connection between the originating side SBC and the calling device" and the "VoIP call connection between the originating side SBC and the called device" can be connected to form a calling party. A VoIP call connection between the device, the originating side SBC, and the called device (bypassing the receiving side SBC).

As can be seen from the above, in this embodiment, when determining that the calling device is located under the NAT device, the media address for connecting the originating side SBC of the called device is allocated, and is transmitted to the called device, and is carried back in the subsequent receiving. Calling the media address of the device to establish a VoIP call connection between the calling device, the originating side SBC, and the called device, thereby bypassing the receiving side SBC when transmitting the media data stream, so that the media data stream does not pass through the core The network (that is, bypassing the core network bearer) achieves the purpose of saving transmission bandwidth. Embodiment 2

This embodiment is a VoIP call setup method corresponding to the first embodiment.

This embodiment will be described from the perspective of the SBC on the called device side, that is, the reception side SBC.

A method for establishing a VoIP call, comprising: receiving a second call request sent by an initiating side SBC, where the second call request carries a media address used to connect the originating side SBC of the called device; determining that the calling device belongs to the access When the media domain is the same as the access media domain to which the called device belongs, the media address used to connect the originating side SBC of the called device is used as the media address of the receiving side SBC for connecting the called device, and the third call request is sent to The called device receives the first call response returned by the called device; sends a second call response to the originating side SBC according to the first call response, where the second call response carries the media address of the called device to establish the originating side SBC A VoIP call connection with the called device, and a VoIP call connection between the originating side SBC and the calling device.

As shown in Figure 2, the specific process can be as follows:

201. Receive a second call request sent by the sending side SBC, where the second call request carries a media address used to connect the originating side SBC of the called device, indicating that the second call request is from the main Calling the device, the receiving end can then return a corresponding response to the calling device.

The second call request may specifically carry a media address for connecting the originating side SBC of the called device by using an extension of the media level a line in the SDP.

In addition, the second call request may also carry the access media domain information of the calling device (ie, the IP domain information), and the access media domain information of the calling device indicates the access media domain to which the calling device belongs, so that the receiving side SBC The access media domain to which the calling device belongs can be obtained. Of course, the access media domain information of the calling device can also be obtained through other means, for example, after receiving the second call request, according to the second call request, the SIP registration process is used. Know the access media domain information of the calling device, and so on.

It should be noted that the media address in the embodiment of the present invention may include information such as an IP address and a port.

202. When it is determined that the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address used to connect the originating side SBC of the called device is used as the receiving side SBC for connecting the called device. Media address, sending a third call request to the called device. For example, the following may be as follows: After receiving the second call request, the receiving side SBC determines that the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, and the second call request carries the connection The media address of the initiating side SBC of the called device indicates that the receiving side SBC can be bypassed, and then the media address used to connect the originating side SBC of the called device is transmitted to the called device as the media address of the receiving side SBC. That is, the media address of the originating side SBC for connecting the called device is replaced with the media address of the receiving side SBC of the called device, and the third call request is sent to the called device, so that the called device directly and the originating side The SBC establishes a VoIP call connection without going through the receiving side SBC.

203. Receive a first call response returned by the called device.

The first call response carries the media address of the called device.

204. Send a second call response to the originating side SBC according to the first call response.

The second call response carries the media address of the called device to establish a VoIP call connection between the originating side SBC and the called device, and establish a VoIP call connection between the originating side SBC and the calling device. For example, the second call response may specifically carry the media address of the called device through the extension of the media level a line in the SDP.

It should be noted that, after receiving the first call response returned by the called device, the receiving side SBC will allocate a media address to the receiving side SBC of the originating side SBC, and then the receiving side SBC And replacing the media address of the allocated side SBC of the originating side SBC with the media address of the called device in the original first call response, so as to indicate that the second call response is from the receiving side SBC, and the called device is The media address is carried to the originating side SBC by an extension of the media level a line in the SDP (here, the second call response).

For the operation of the SBC after receiving the second call response, refer to the first embodiment, and details are not described herein again.

As can be seen from the above, in the embodiment, when determining that the calling device is located under the NAT device, the originating side SBC allocates a media address for connecting the originating side SBC of the called device, and then determines the access of the calling device at the receiving side SBC. When the media domain is the same as the access media domain to which the called device belongs, the media address of the originating side SBC for connecting the called device is transmitted by the receiving side SBC to the media address of the receiving side SBC for connecting the called device to the media address. Calling the device, and subsequently transmitting the media address of the called device to the originating side SBC to establish a VoIP call connection between the calling device, the originating side SBC and the called device, thereby transmitting the media data stream The SBC is removed from the receiving side, so that the media data stream does not pass through the core network (ie, bypasses the core network bearer), thereby achieving the purpose of saving transmission bandwidth. Embodiment 3

Embodiments 1 and 2 mainly describe a scenario in which the receiving side SBC is bypassed, and the scenario will be described in detail below by way of example.

Referring to Figures 3a and 3b, the two figures are schematic illustrations of two scenes bypassing the receiving side SBC, respectively. Figure 3a shows a scenario in which a VoIP call is established when both the calling device and the called device are located under the NAT, and Figure 3b shows a scenario in which the VoIP call is established when the called device is located under the NAT and the called device is not located under the NAT. The dashed line indicates the path of the signaling, and the path representing the media data stream is implemented. The VoIP call setup method provided by the embodiment of the present invention will be described in detail below by taking the two scenarios as an example.

For the convenience of description, in this embodiment, the calling device is the terminal A, the called device is the terminal B, the NAT of the terminal A is NAT1, the NAT of the terminal B is the NAT2, and the originating side SBC is the SBC1, and the receiving is performed. The side SBC is SBC2 as an example.

As shown in Figure 3c, the specific process can be as follows:

301. Terminal A sends a first call request through NAT1 through SIP signaling.

The first call request carries a SDP offer (Session Description Protocol offer) message body, and the SDP offer message body includes the media address of the terminal A: IP0 and port 0.

For example, if IP0 is IP4 192.0.2.1 and port 0 is 49170, the format of the SDP offer message body can be as follows:

SDP offer (UEl to SBC1)

INVITE SIP: user_B@operator_Y.net; SIP/2.0

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 192.0.2.1

m=audio 49170 RTP/AVP 96 97

a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:96 telephone-event

a=maxptime: 20

302. The SBC1 allocates the media address of the SBC1 to the core side: IP2 and port 2. Since the terminal A is known to be located under the NAT device through the SIP registration process of the terminal A, the SBC1 allocates a media address of the SBC1 at this time. : IP1 and port 1, used to connect to terminal B.

303. The SBC1 sends a second call request to the core network according to the first call request.

The second call request carries an SDP offer message body, where the SDP offer message body includes the media address of the SBC1: IP2 and port 2 (ie, replaces the IP0 and port 0 in the original first call request), and simultaneously passes the SDP The media level a line is extended to carry the multi-allocated media address of the SBC1 for connecting to the terminal B: IP1 and port 1. In addition, the access media domain information to which the terminal A belongs may also be carried: R1 information. For example, if IP2 is 13.24.1.1, port 2 is 62111, IP1 is 192.0.2.2, and port 1 is 49180, the format of the SDP offer message body can be as follows:

SDP offer (SBCl to Core to SBC2)

INVITE SIP: user_B@operator_Y.net; SIP/2.0

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 13.24.1.1

m=audio 62111 RTP/AVP 96 97

a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:96 telephone-event

a=maxptime: 20

a=nat-visited-realm: l Rl IN IP4 192.0.2.2 49180

The underlined part is an extended a-line information.

After receiving the second call request, the core network routes the second call request to the SBC2, and the SBC2 determines that the SDP offer carried by the second call request includes the extended media level a line, and then obtains the R1 information. And obtaining the access media domain information of the terminal B, determining whether the R1 information and the access media domain information to which the terminal B belongs are the same. If yes, it is considered that the core network bearer can be bypassed, so that it is determined that the SBC2 can be bypassed; if not, it is considered It is not possible to bypass the core network bearer, and then operate according to the existing process.

305. SBC2 sends IP3 and port 1 in the extended media level a line as the media address of SBC2 to terminal B, and sends a third call request to terminal B.

The third call request carries an SDP offer message body, where the SDP offer message body includes IP1 and port 1.

It should be noted that the SBC2 originally needs to allocate the media address of the SBC2 to the terminal B, and then carries it to the terminal B in the third call request to indicate that the third call request is from the SBC2, and in this embodiment, The IP1 address and port 1 in the extended media level a line will be replaced by the original allocation. The media address of the SBC2 to the terminal B, that is, the IP1 address and port 1 in the extended media level a line are used as the media address of the SBC2 destined for the terminal B, and the third call request is sent to the terminal B, In this way, the terminal B can know the media address of the SBC1, thereby achieving the purpose of bypassing the SBC2. There is no need to extend the media level a line in the third call request.

For example, the format of the SDP offer message body after the IP1 address and port 1 in the extended media level a line is used as the media address of the SBC2 to the terminal B may be as follows:

SDP offer(SBC2 to Called)

INVITE SIP: sip:UE-B ©operatorX.net; SIP/2.0

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 192.0.2.2

m=audio 49180 RTP/AVP 96 97

a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:96 telephone-event

a=maxptime: 20

306, terminal B returns the first call response to SBC2;

The first call response carries a session description protocol answer (SDP answer, Session Description Protocol answer), and the SDP answer includes the media address of the terminal B: IP3 and port 3; and may also include the media domain information of the terminal B: R1 information .

For example, if IP3 is 192.0.2.4 and port 3 is 16511, the format of the SDP answer message body can be as follows:

SDP answer(Called to SBC2)

SIP/2.0 183 Session Progress

SIP headers

Content- Type: application/sdp

Content-Length: (...) V=0

c=IN IP4 192.0.2.4

m=audio 16511 RTP/AVP 97 98

a=rtpmap:98 AMR

a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime: 20

307. After receiving the first call response, the SBC2 allocates the media address of the SBC2 to the core network: IP4 and port 4, and sends a second call response to the core network.

The second call response carries the SDP answer message body, and the SDP answer message body carries the assigned media address of the SBC2 to the core network: IP4 and port 4 (ie, IP4 and port 4 are replaced by the original first call response) The media address of the terminal B: IP3 and port 3), and the media address of the terminal B is carried by the extension of the media level a: IP3 and port 3. In addition, the access media domain information of the terminal B can also be carried: R1 information.

For example, if IP4 is IP4 13.24.1.2 and port 4 is 16000, the format of the SDP answer message body can be as follows:

SDP answer(SBC2 to Core to SBC1)

SIP/2.0 183 Session Progress

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 13.24.1.2

m=audio 16000 RTP/AVP 97 98

a=rtpmap:98 AMR

a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime: 20

a=nat-visited-realm: l Rl IN IP4 192.0.2.4 16511 Among them, the underlined part is the extended media level a line.

308. After receiving the second call response, the core network routes the second call response to SBC1. After receiving the second call response routed by the core network, the SBC1 allocates the media address to the terminal A: IP5 and port 5; since the SDP answer is found to contain the extended media level a line, and the terminal A and the terminal B belong to The access media domain is the same, so SBC1 determines that the core network bearer can be bypassed, that is, SBC2 can be bypassed, and SBC1 establishes a media session connection internally: IP5+port<-->IP1+ port.

309. SBC1 sends a third call response to terminal A.

The third call response carries an SDP answer message body, and the SDP answer message body includes a media address to the terminal A: IP5 and port 5, that is, IP5 and port 5 are replaced with the IP4 and port in the original second call response. 4.

For example, if IP5 is 192.0.2.5 and port 5 is 16611, the format of the SDP answer message body can be as follows:

SDP answer (SBCl to Caller)

SIP/2.0 183 Session Progress

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 192.0.2.5

m=audio 16611 RTP/AVP 97 98

a=rtpmap:98 AMR

a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime: 20

At this point, the VoIP call is established, and thereafter, the terminal A and the terminal B can perform the media session without being carried by the core network.

As can be seen from the above, in this embodiment, when determining that the terminal A is located under the NAT device, the media address of the SBC1 for connecting to the terminal B is allocated, and is carried to the SBC2 through the extended media level a line, so that the SBC2 will be used for the connection. The media address of SBC1 of terminal B is transmitted as the media address of SBC2. To the terminal B, and then carry the media address of the terminal B to the SBC1 through the extended media level a line by the SBC2 to establish a VoIP call connection between the terminal A, the SBC1 and the terminal B, thereby transmitting the media data stream. Bypassing SBC2, the media data stream does not pass through the core network (ie bypassing the core network bearer), thereby achieving the purpose of saving transmission bandwidth. Embodiment 4

Another embodiment of the present invention provides a VoIP call setup method. The VoIP call setup method will be described in detail in Embodiments 4, 5 and 6.

In this embodiment, the description will be made from the perspective of the SBC on the calling device side, that is, the originating side SBC. A method for establishing a VoIP call, comprising: receiving a first call request sent by a calling device; sending a fourth call request to a receiving side SBC according to the first call request, where the fourth call request carries a media address of the calling device, so that The receiving side SBC determines that the called device is located under the NAT device, and the first call request carries the media address of the calling device, and the accessing media domain to which the calling device belongs is the same as the access media domain to which the called device belongs. a media address of the receiving side SBC connected to the calling device; receiving a fourth call response returned by the receiving side SBC, the fourth call response carrying a media address for connecting the receiving side SBC of the calling device; determining the fourth call response When the media address of the receiving side SBC is used to connect to the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the receiving side SBC for connecting the calling device is used. The media address is used as a media address for connecting the originating side SBC of the calling device, and sends a fifth call response to the calling device to establish reception. A VoIP call connection between the side SBC and the calling device.

Referring to Figure 4, the specific process can be as follows:

401. Receive a first call request sent by a calling device.

402. Send a fourth call request to the receiving side SBC according to the first call request, where the fourth call request carries the media address of the calling device, so that the receiving side SBC determines that the called device is located under the NAT device, and the fourth call request When the media address of the calling device is carried in, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the receiving side for connecting the calling device is allocated. SBC's media address.

The fourth call request carries the media address of the calling device through the extension of the media level a line in the SDP.

In addition, the fourth call request may further carry the access media domain information (ie, the IP domain information) of the calling device, and is used to indicate the access media domain to which the calling device belongs, and of course, the access media domain information of the calling device. It can also be obtained through other means, such as obtaining the access media domain information of the calling device through the SIP registration process, and the like. In addition, the access media domain to which the called device belongs can also be learned through the SIP registration process, and details are not described herein.

403. Receive a fourth call response returned by the receiving side SBC, where the fourth call response carries a media address used to connect the receiving side SBC of the calling device.

For example, the fourth call response may specifically carry the media address of the receiving side SBC for connecting to the calling device through the extension of the media level a line in the SDP.

In addition, the fourth call response may further carry the access media domain information of the called device, and the access media domain information of the called device indicates the access media domain to which the called device belongs. Of course, the access media domain to which the called device belongs can also be learned through the SIP registration process, and details are not described herein.

404. Determine that the fourth call response carries a media address used to connect the receiving side SBC of the calling device, and if the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, it is determined that the receiving may be bypassed. The side SBC, and then the media address for connecting the receiving side SBC of the calling device is used as the media address for connecting the originating side SBC of the calling device (that is, replacing the media address of the receiving side SBC for connecting the calling device) The assigned media address of the originating side SBC of the calling device is sent, and the fifth call response is sent to the calling device. When the calling device receives the fifth call response, the VoIP between the receiving side SBC and the calling device The call connection is built to form a VoIP call connection between the calling device, the receiving side SBC and the called device (bypassing the originating side SBC).

As can be seen from the above, the embodiment is used to determine that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the access media domain to which the calling device belongs and the access media to which the called device belongs. When the domains are the same, the media address of the receiving side SBC for connecting to the calling device is allocated, and when the first call response returned by the called device is subsequently received, the media address of the receiving side SBC for connecting the calling device is allocated. Passed to the calling device to establish a VoIP call connection between the calling device, the receiving side SBC and the called device, thereby bypassing the originating side SBC when transmitting the media data stream, The media data stream is not passed through the core network (ie, bypassing the core network bearer), thereby achieving the purpose of saving transmission bandwidth. Embodiment 5

This embodiment is a VoIP call establishment method corresponding to the fourth embodiment.

A method for establishing a VoIP call, comprising: receiving a fourth call request sent by an initiating side SBC, where the fourth call request carries a media address of the calling device; determining that the called device is located under the NAT device, and the first call request is carried The media address of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, and the media address of the receiving side SBC for connecting the calling device is allocated; Receiving a call request to the called device; receiving a first call response returned by the called device to establish a VoIP call connection between the receiving side SBC and the called device; and transmitting a fourth call response to the originating side SBC according to the first call response, The fourth call response carries a media address for connecting the receiving side SBC of the calling device, so that the originating side SBC determines that the fourth call response carries a media address for connecting the receiving side SBC of the calling device, and the calling device belongs to When the incoming media domain is the same as the access media domain to which the called device belongs, the media area for connecting the receiving side SBC of the calling device is used. As the media address for initiating the calling side connection of the SBC device, the call sends a fifth response to the calling device to establish a VoIP call connection between the calling device and the reception side SBC.

As shown in Figure 5, the specific process can be as follows:

501. Receive a fourth call request sent by the sending side SBC, where the fourth call request is sent by the sending side SBC according to the received first call request (ie, the first call request sent by the calling device).

The fourth call request carries the media address of the calling device. For example, the media address of the calling device may be carried by the extension of the media level a line in the SDP.

It should be noted that the media address in the embodiment of the present invention may include information such as an IP address and a port. 502. Determine that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs. The media address of the receiving side SBC of the calling device is connected. For example, the receiving side SBC, after receiving the fourth call request, determines that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the calling device belongs to If the inbound media domain is the same as the access media domain to which the called device belongs, it indicates that the originating side SBC can be bypassed, and then the media address of the receiving side SBC for connecting to the calling device is allocated, so that the media address can be subsequently transmitted to the calling device. Establish a VoIP call connection between the calling device and the receiving side SBC.

503. Send a fifth call request to the called device according to the fourth call request.

504. Receive a first call response returned by the called device to establish a VoIP call connection between the receiving side SBC and the called device.

505. Send a fourth call response to the originating side SBC according to the first call response, where the fourth call response carries the “media address for connecting the receiving side SBC of the calling device” allocated in step 502.

The fourth call response may specifically carry a media address for connecting the receiving side SBC of the calling device by using an extension of the media level a line in the SDP.

After receiving the fourth call response, the initiating side SBC determines that the fourth call response carries the media address of the receiving side SBC for connecting to the calling device, and the accessing media domain to which the calling device belongs is associated with the called device. When the media domain is the same, it is considered that the originating side SBC can be bypassed, and then the media address used to connect the receiving side SBC of the calling device is used as the media address for connecting the originating side SBC of the calling device, and the fifth is sent. The call response is sent to the calling device, that is, the media address of the receiving side SBC for connecting the calling device is replaced by the media address of the transmitting side SBC of the calling device, and the fifth call request is sent to the calling device, so that The calling device establishes a VoIP call connection directly with the receiving side SBC without passing through the originating side SBC.

As can be seen from the above, this embodiment is used to determine that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the access device belongs to the accessed media domain and the called device. When the access media domain is the same, the media address of the receiving side SBC for connecting to the calling device is allocated, and when the first call response returned by the called device is subsequently received, the receiving side for connecting the calling device is used. The media address of the SBC is delivered to the calling device to establish a VoIP call connection between the calling device, the receiving side SBC and the called device, thereby bypassing the originating side SBC when transmitting the media data stream, so that the media data The flow does not pass through the core network (that is, bypasses the core network bearer), achieving the purpose of saving transmission bandwidth. Embodiment 6

The methods described in the fourth and fifth embodiments will be exemplified in detail below.

Referring to FIG. 6a, the figure is a schematic diagram of bypassing the SBC of the originating side when the media data stream is transmitted. In FIG. 6a, the calling device is not located under the NAT, and the called device is located under the NAT, where the dotted line indicates signaling. Path, the path that represents the flow of media data. The VoIP call setup method provided by the embodiment of the present invention will be described in detail below by taking the scenario as an example.

For the convenience of description, in this embodiment, the calling device will be the terminal A, and the called device will be the terminal.

B. The NAT of the terminal B is NAT2, the SBC of the initiating side is SBC1, and the SBC of the receiving side is SBC2.

As shown in Figure 6b, the specific process can be as follows:

601. Terminal A sends a first call request by using SIP signaling.

The first call request carries the SDP offer message body, and the SDP offer message body includes the media address of the terminal A: IP0 and port 0.

SDP offer (UEl to SBCl)

INVITE SIP: user_B@operator_Y.net; SIP/2.0

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 192.0.2.1

m=audio 49170 RTP/AVP 96 97 a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:96 telephone-event

a=maxptime: 20

602. SBC1 allocates the media address of SBC1 to the core side: IP2 and port 2.

603. The SBC1 sends a fourth call request to the core network according to the first call request.

The fourth call request carries an SDP offer message body, where the SDP offer message body includes the media address of the SBC1: IP2 and the port (ie, replaces the IP0 and port 0 in the original first call request), and simultaneously passes the SDP media level. The extension of the a line carries the media address of the terminal A: IP0 and port 0, and may also carry the access media domain information of the terminal A: R1 information.

For example, if IP2 is 13.24.1.1 and port 2 is 62111; the format of the SDP offer message body can be as follows:

SDP offer (SBCl to Core to SBC2)

INVITE SIP: user_B@operator_Y.net; SIP/2.0

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 13.24.1.1

m=audio 62111 RTP/AVP 96 97

a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:96 telephone-event

a=maxptime: 20

a=visited-realm: l Rl IN IP4 192.0.2.1 49170

The line portion is an extended media level a line.

604. After receiving the fourth call request, the core network routes the fourth call request to the SBC2. On the one hand, the SBC2 allocates the media address of the SBC2 to the terminal B under the NAT2: IP6 and port 6. On the other hand, SBC2 determines that terminal B is located under NAT2, and the SDP offer carried by the fourth call request is The extended media level a line is included, and the R1 information is obtained, and the access media domain information of the terminal B is obtained, and it is determined whether the R1 information and the access media domain information of the terminal B belong to the same. If yes, the core network is considered to be bypassed. Bearer, then allocates the media address of SBC2 for connecting terminal A: IP1 and port 1 to bypass SBC1; if not, it is considered that the core network bearer cannot be bypassed, and then operates according to the existing flow.

605. The SBC2 sends a fifth call request to the terminal B.

The fifth call request carries an SDP offer message body, where the SDP offer message body includes the media address of the SBC2 assigned to the terminal B under the NAT2: IP6 and port 6.

For example, if IP6 is 192.0.2.5 and port 6 is 16611, the format of the SDP offer message body can be as follows:

SDP offer(SBC2 to Called)

INVITE SIP: sip:UE-B ©operatorX.net; SIP/2.0

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 192.0.2.5

m=audio 16611 RTP/AVP 96 97

a=rtpmap:97 AMR

a=fmtp:97 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:96 telephone-event

a=maxptime: 20

606. Terminal B returns a first call response to SBC2.

The first call response carries the SDP answer, and the SDP answer includes the media address of the terminal B: IP3 and port 3. The media domain information of the terminal B may also be included: R1 information.

SDP answer(Called to SBC2)

SIP/2.0 183 Session Progress SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 192.0.2.4

m=audio 16511 RTP/AVP 97 98

a=rtpmap:98 AMR

a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime: 20

607. After receiving the first call response, the SBC2 allocates the media addresses of the SBC2 to the core network: IP4 and port 4, and sends a fourth call response to the core network.

The fourth call response carries the SDP answer message body, and the SDP answer message body carries the assigned media address of the SBC2 to the core network: IP4 and port 4 (ie, IP4 and port 4 are replaced by the original first call response) The media address of the terminal B: IP3 and port 3), and the media address of the SBC2 for connecting to the terminal A is carried by the extension of the media level a: IP1 and port 1, and the access of the terminal B can also be carried. Media domain information: R1 information.

For example, if IP4 is IP4 13.24.1.2, port 4 is 16000, IP1 is 192.0.2.2, and port 1 is 49180, the format of the SDP answer message body can be as follows:

SDP answer(SBC2 to Core to SBC1)

SIP/2.0 183 Session Progress

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0

c=IN IP4 13.24.1.2

m=audio 16000 RTP/AVP 97 98

a=rtpmap:98 AMR

a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2 a=rtpmap:97 telephone-event

a=maxptime: 20

a= visited-realm: 1 Rl IN IP4 192.0.2.2 49180

Among them, the underlined part is the extended media level a line.

608. After receiving the fourth call response, the core network routes the fourth call response to SBC1. After receiving the fourth call response routed by the core network, the SBC1 determines that the SDP answer includes the extended media level a line, and then obtains the R1 information, and obtains the access media domain information of the terminal A, and determines the access of the terminal A. The media domain information is the same as the fixed R1 information, so it is determined that the core network bearer can be bypassed, that is, SBC1 can be bypassed.

609. The SBC1 sends a fifth call response to the terminal A by using the media address "IP1" and the port of the SBC2 for connecting the terminal A in the fourth call response as the media address of the SBC1 for connecting to the terminal A.

The fifth call response carries an SDP answer message body, where the SDP answer message body includes a media address of the SBC2 for connecting to the terminal A: IP1 and port 1.

It should be noted that the SBC1 originally needs to allocate the media address of the SBC1 to the terminal A, and then carries it to the terminal A in the fifth call response to indicate that the fifth call response is from SBC1, and in this embodiment, The IP1 address and port 1 in the extended media level a row will be replaced with the originally assigned media address of SBC1 destined for terminal A, that is, the IP1 address and port in the extended media level a row. 1 As the media address of the SBC1 to the terminal A, the fifth call response is sent to the terminal A, so that the terminal A can know the media address of the SBC2, thereby achieving the purpose of bypassing the SBC1. There is no need to extend the media level a line in the fifth call response.

For example, if IP1 is 192.0.2.2 and port 1 is 49180, the specific format of the SDP answer message body can be as follows:

SDP answer (SBCl to Caller)

SIP/2.0 183 Session Progress

SIP headers

Content- Type: application/sdp

Content-Length: (...)

V=0 c=IN IP4 192.0.2.2

m=audio 49180 RTP/AVP 97 98

a=rtpmap:98 AMR

a=fmtp:98 mode-set=0,2,5,7; mode-change-period=2

a=rtpmap:97 telephone-event

a=maxptime: 20

It can be seen that, in this embodiment, when it is determined that the terminal B is located under the NAT device, and the fourth call request carries the media address of the terminal A, and the access media domain to which the terminal A belongs is the same as the access media domain to which the terminal B belongs, The SBC2 allocates a media address for connecting to the SBC2 of the terminal A, and when subsequently receiving the first call response returned by the terminal B, it is carried to the SBC1 through the extended media level a, and is used by the SBC1 for the connection. The media address of the SBC2 of the terminal A is transmitted to the terminal A as the media address of the SBC1 for connecting the terminal A, so as to establish a VoIP call connection between the terminal A, the SBC2 and the terminal B, thereby transmitting the media data stream. The SBC1 is off the originating side, so that the media data stream does not pass through the core network (ie, bypasses the core network bearer), thereby achieving the purpose of saving transmission bandwidth. Example VII.

In order to better implement the methods of Embodiments 1 to 3, the embodiment of the present invention further provides a network telephone call setup device, that is, a VoIP call setup device, which can serve as an originating side SBC, as shown in FIG. 7a, the network telephone call. The establishing device includes a first receiving unit 701, an allocating unit 702, a first sending unit 703, a second receiving unit 704, and a second sending unit 705;

The first receiving unit 701 is configured to receive a first call request sent by the calling device.

The allocating unit 702 is configured to allocate, according to the first call request received by the first receiving unit 701, that the calling device is located under the NAT, and allocate a media address for connecting the originating side SBC of the called device; The SIP process of the device is used to know whether the calling device is located under the NAT device. For example, after receiving the first call request, the originating SBC may pass the previous SIP of the terminal A if it is determined that the first call request is from the terminal A. Registration process to determine the calling setup Whether the device is under the NAT device.

The first sending unit 703 is configured to send a second call request to the receiving side SBC, where the second call request carries a media address allocated by the allocating unit 702 for connecting the originating side SBC of the called device, so that the receiving side SBC determines the main When the access media domain to which the device belongs is the same as the access media domain to which the called device belongs, the media address for connecting the originating side SBC of the called device is transmitted to the called device; and the second receiving unit 704 is configured to receive and receive. a second call response sent by the side SBC, where the second call response carries the media address of the called device to establish a network telephone call connection between the originating side SBC and the called device;

The second sending unit 705 is configured to send a third call response to the calling device to establish a network telephone call connection between the originating side SBC and the calling device.

The second call request may specifically carry a media address for connecting the originating side SBC of the called device by using an extension of the media level a line in the SDP. which is:

The first sending unit 701 is specifically configured to send a second call request to the receiving side SBC, where the second call request carries an media address for connecting the originating side SBC of the called device by using an extension of the media level a line in the SDP. .

Optionally, the second call request may further include the access media domain information (ie, the IP domain information) of the calling device, where the access media domain information of the calling device indicates the access media domain to which the calling device belongs, so that The receiving side SBC can learn the access media domain to which the calling device belongs. Of course, the accessing media domain information of the calling device can also be obtained by other means, for example, the SIP calling process is used to learn the connection of the calling device according to the second call request. Enter media domain information, and more. In addition, the access media domain to which the called device belongs can also be learned through the SIP registration process, and details are not described herein.

Similarly, the second call response may also carry the media address of the called device through the extension of the media level a line in the SDP. which is:

The second receiving unit 704 is specifically configured to receive a second call response sent by the receiving side SBC, where the second call response carries the media address of the called device by using an extension of the media level a line in the SDP.

Optionally, the second call response may further include the access media domain information of the called device, where the access media domain information of the called device indicates the access media domain to which the called device belongs, so that the originating side SBC can be informed The access media domain to which the device belongs is used. Of course, the access media domain information of the called device can also be obtained through other means, for example, after receiving the second call response, according to the second call response. The SIP registration process learns the access media domain information of the called device, and so on.

In addition, referring to FIG. 7b, the network telephone call setup device may further include a processing unit 706. The processing unit 706 is configured to allocate a media address to the originating side SBC of the calling device, and determine that the second call response carries the called device. When the media address is the same, and the access media domain to which the called device belongs is the same as the access media domain to which the called device belongs, the media address of the originating side SBC to the calling device and the initiation of the connected device are established internally. Media session connection between media addresses of side SBCs.

At this time, the second sending unit 705 is specifically configured to send a third call response to the calling device to establish a network telephone call connection between the originating side SBC and the calling device, where the third call response carrying processing unit 706 The assigned media address to the originating side SBC of the calling device.

For the specific implementation of the above various units, refer to the foregoing method embodiments, and details are not described herein again. It should be noted that, in the specific implementation, the foregoing units may be implemented as independent entities, or may be any combination, as the same or several. The entity is implemented, and will not be described here.

As can be seen from the above, the VoIP call setup device of the embodiment uses the media address for connecting the originating side SBC of the called device by the allocating unit 702 when determining that the calling device is located under the NAT device, and is configured by the first sending unit. 703 is transmitted to the called device via the receiving side SBC, and is subsequently received by the second receiving unit 704, and the media address carrying the called device is received to establish a relationship between the calling device, the originating side SBC and the called device. The VoIP call is connected, so that the receiving side SBC is bypassed when the media data stream is transmitted, so that the media data stream does not pass through the core network (ie, bypasses the core network bearer), thereby achieving the purpose of saving transmission bandwidth. Example VIII.

Corresponding to the seventh embodiment, the embodiment of the present invention further provides another VoIP call setup device, that is, a VoIP call setup device, which can serve as a receiving side SBC. As shown in FIG. 8, the VoIP call setup device includes a first receiving. The unit 801, the first sending unit 802, the second receiving unit 803, and the second sending unit 804;

The first receiving unit 801 is configured to receive a second call request sent by the initiating side SBC, where the second call request carries a media address used to connect the originating side SBC of the called device.

It should be noted that the media address in the embodiment of the present invention may include information such as an IP address and a port. The first sending unit 802 is configured to determine that the access media domain to which the calling device belongs is associated with the called device. When the media domain is the same, the media address of the originating side SBC for connecting to the called device is used as the media address of the receiving side SBC for connecting the called device, and the third call request is sent to the called device; The unit 803 is configured to receive a first call response returned by the called device, where the first call response carries a media address of the called device.

The second sending unit 804 is configured to send a second call response to the originating side SBC according to the first call response, where the second call response carries the media address of the called device to establish an between the originating side SBC and the called device. A VoIP call connection, and a VoIP call connection between the originating side SBC and the calling device.

The first receiving unit 801 is specifically configured to receive a second call request sent by the originating side SBC, where the second call request carries an extension of the media level a in the session description protocol to carry the originating side SBC for connecting the called device. Media address.

Optionally, the second call response may specifically carry the media address of the called device by using an extension of the media level a line in the SDP, that is,

The second receiving unit 803 is specifically configured to send a second call response to the originating side SBC according to the first call response, where the second call response carries the media address of the called device by using an extension of the media level a line in the SDP.

For the specific implementation of the above various units, refer to the foregoing method embodiments, and details are not described herein again. It should be noted that, in the specific implementation, each of the foregoing units may be implemented as an independent entity, or may be implemented in any combination, and implemented as the same entity or several entities, and details are not described herein again.

It can be seen that the first receiving unit 801 of the network telephone call setup device of this embodiment can receive the second call request that is sent by the originating side SBC and carries the media address of the originating side SBC for connecting the called device, and then determines the main When the access media domain to which the device belongs is the same as the access media domain to which the called device belongs, the first sending unit 802 uses the media address of the originating side SBC for connecting the called device as the receiving side for connecting the called device. The media address of the SBC is delivered to the called device, and the media address of the called device is subsequently transmitted by the second sending unit 804 to the originating side SBC to establish a relationship between the calling device, the originating side SBC and the called device. The VoIP call is connected, so that the receiving side SBC is bypassed when the media data stream is transmitted, so that the media data stream does not pass through the core network (ie, bypasses the core network bearer), thereby achieving the purpose of saving transmission bandwidth. Example IX.

In order to better implement the methods of the fourth to sixth embodiments, the embodiment of the present invention further provides a network telephone call setup device, that is, a VoIP call setup device, which can serve as an originating side SBC, as shown in FIG. 9, the network telephone call. The establishing device includes a first receiving unit 901, a first transmitting unit 902, a second receiving unit 903, and a second sending unit 904;

The first receiving unit 901 is configured to receive a first call request sent by the calling device, where the first call request includes a media address of the calling device, indicating that the first call request is from the calling device, and is convenient for the receiving end. Subsequent returns can be returned to the calling device.

The first sending unit 902 is configured to send a fourth call request to the receiving side SBC according to the first call request, where the fourth calling request carries the media address of the calling device, so that the receiving side SBC determines that the called device is located under the NAT, and When the fourth call request carries the media address of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address for connecting the receiving side SBC of the calling device is allocated;

a second receiving unit 903, configured to receive a fourth call response returned by the receiving side SBC, where the fourth call response carries a media address used to connect the receiving side SBC of the calling device;

The second sending unit 904 is configured to determine that the fourth call response carries the connection for connecting the calling device. When the media address of the side SBC is the same as the access media domain to which the called device belongs, the media address of the receiving side SBC for connecting the calling device is used as the connection destination device. The media address of the originating side SBC sends a fifth call response to the calling device to establish a network telephone call connection between the receiving side SBC and the calling device.

The fourth call request carries the media address of the calling device through the extension of the media level a line in the SDP. which is:

The first sending unit 902 is specifically configured to send a fourth call request to the receiving side SBC according to the first call request, where the fourth call request carries the media address of the calling device by using the extension of the media level a line in the SDP.

Optionally, the fourth call request may further include the access media domain information of the calling device, that is, the IP domain information, used to indicate the access media domain to which the calling device belongs, and of course, the access media of the calling device. The domain information can also be obtained through other means, such as obtaining the access media domain information of the calling device through the SIP registration process, and the like. In addition, the access media domain to which the called device belongs can also be learned through the SIP registration process, and details are not described herein.

Similarly, the fourth call response may also carry the media address of the receiving side SBC for connecting to the calling device through the extension of the media level a line in the SDP. which is:

The second receiving unit 903 is specifically configured to receive a fourth call response returned by the receiving side SBC, where the fourth call response carries the media address used to connect the receiving side SBC of the calling device by using the extension of the media level a line in the SDP. .

Optionally, the fourth call response may further include the access media domain information of the called device, where the access media domain information of the called device indicates the access media domain to which the called device belongs. Of course, the access media domain to which the called device belongs can also be learned through the SIP registration process, and details are not described herein.

As can be seen from the above, the first receiving unit 901 of the VoIP call setup device of the present embodiment, after receiving the first call request that is sent by the calling device and carrying the media address of the calling device, is called by the first sending unit 902. The media address of the device is transmitted to the receiving side SBC, and the receiving side SBC determines that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the main When the access media domain to which the device belongs is the same as the access media domain to which the called device belongs, the media address of the receiving side SBC for connecting the calling device is allocated, so that the receiving side SBC subsequently receives the first call returned by the called device. In response, the media address for connecting the receiving side SBC of the calling device is transmitted to the calling device to establish a VoIP call connection between the calling device, the receiving side SBC and the called device, thereby transmitting When the media data stream is bypassed, the originating side SBC is bypassed, so that the media data stream does not pass through the core network (ie, bypasses the core network), thereby achieving the purpose of saving transmission bandwidth. Embodiment 10

Corresponding to the ninth embodiment, the embodiment of the present invention further provides another VoIP call setup device, that is, a VoIP call setup device, which can be used as a receiving side SBC. As shown in FIG. 10, the VoIP call setup device includes a first receiving. a unit 1001, an allocating unit 1002, a first transmitting unit 1003, a second receiving unit 1004, and a second transmitting unit 1005;

The first receiving unit 1001 is configured to receive a fourth call request sent by the initiating side SBC, where the fourth call request carries a media address of the calling device;

The allocating unit 1002 determines that the called device is located under the NAT, and the fourth call request carries the media address of the calling device, and the accessing media domain to which the calling device belongs is the same as the accessing media domain to which the called device belongs. a media address connected to the receiving side SBC of the calling device;

The first sending unit 1003 is configured to send a fifth call request to the called device according to the fourth call request.

a second receiving unit 1004, configured to receive a first call response returned by the called device, to establish a network telephone call connection between the receiving side SBC and the called device;

The second sending unit 1005 is configured to send a fourth call response to the originating side SBC according to the first call response, where the fourth call response carries a media address for connecting the receiving side SBC of the calling device, so that the initiating side SBC determines The four-call response carries the media address of the receiving side SBC for connecting the calling device, and the accessing media domain to which the calling device belongs is the same as the accessing media domain to which the called device belongs. The media address of the SBC serves as a media address for connecting the originating side SBC of the calling device, and sends a fifth call response to the calling device to establish a network telephone call connection between the receiving side SBC and the calling device. The fourth call request may specifically carry the media address of the calling device by using an extension of the media level a line in the SDP. which is:

The first receiving unit 1001 is specifically configured to receive a fourth call request sent by the initiating side SBC, where the fourth call request carries the media address of the calling device by using an extension of the media level a line in the SDP.

Similarly, the fourth call response may also carry the media address of the receiving side SBC for connecting to the calling device through the extension of the media level a line in the SDP.

The second sending unit 1005 is specifically configured to send a fourth call response to the originating side SBC according to the first call response, where the fourth call response carries the receiving side for connecting the calling device by using the extension of the media level a line in the SDP. SBC's media address.

It can be seen that the allocating unit 1002 of the VoIP call setup device in this embodiment determines that the called device is located under the NAT device, and the fourth call request carries the media address of the calling device, and the access device belongs to the access device. When the domain is the same as the access media domain to which the called device belongs, the media address of the receiving side SBC for connecting to the calling device is allocated, and when the first call response returned by the called device is subsequently received, the second sending unit 1005 Transmitting, by the originating side SBC, the media address of the receiving side SBC of the calling device to the calling device, to establish a VoIP call connection between the calling device, the receiving side SBC and the called device, thereby When the media data stream is transmitted, the originating side SBC is bypassed, so that the media data stream does not pass through the core network (ie, bypasses the core network bearer), thereby achieving the purpose of saving transmission bandwidth. Embodiment 11

Correspondingly, the embodiment of the present invention further provides a communication system, which includes any network telephone call setup device provided by the embodiment of the present invention.

For example, the communication system may specifically include an initiating side SBC and a receiving side SBC, where the initiating side SBC may be any one of the network telephone call establishing devices provided in the seventh embodiment, and the receiving side SBC may be provided in the eighth embodiment. Any type of VoIP call setup device; or,

For example, the communication system may specifically include an initiating side SBC and a receiving side SBC, where the initiating side SBC may be any one of the network telephone call establishing devices provided in the ninth embodiment, and the receiving side SBC may be the tenth embodiment. Any of the provided VoIP call setup devices.

For a detailed description of each VoIP call setup device, refer to the previous embodiment, and details are not described herein again.

It can be seen that, when the communication system of the present embodiment determines that the calling device is located under the NAT device, the media address of the originating side SBC for connecting the called device is allocated in advance by the originating side SBC, and is transmitted to the called device. Establishing a VoIP call connection between the calling device, the originating side SBC, and the called device, thereby bypassing the receiving side SBC when transmitting the media data stream, so that the media data stream does not pass through the core network, thereby realizing saving transmission bandwidth. purpose.

Similarly, the communication system may further determine that the called device is located under the NAT device, and the receiving side SBC allocates a media address for connecting the receiving side SBC of the calling device, and subsequently receives the first call returned by the called device. In response, the media address for connecting the receiving side SBC of the calling device is transmitted to the calling device to establish a VoIP call connection between the calling device, the receiving side SBC and the called device, thereby transmitting When the media data stream is bypassed, the originating side SBC is bypassed, so that the media data stream does not pass through the core network, thereby achieving the purpose of saving transmission bandwidth. A person skilled in the art may understand that all or part of the various steps of the foregoing embodiments may be completed by a program instructing related hardware. The program may be stored in a computer readable storage medium, and the storage medium may include: Read Only Memory (ROM), Random Access Memory (RAM), disk or optical disk.

The foregoing description of the method, apparatus, and system for establishing a VoIP call provided by an embodiment of the present invention is only for helping to understand the method and core idea of the present invention; A person skilled in the art will have a change in the specific embodiments and the scope of the application according to the idea of the present invention. In the above, the contents of the present specification should not be construed as limiting the present invention.

Claims

Rights request

A method for establishing a network telephone call, comprising:

Receiving a first call request sent by the calling device;

Determining, according to the first call request, that the calling device is located under the network address switching device, and assigning a media address of the first border session controller for connecting to the called device;

Sending a second call request to the second border session controller, where the second call request carries a media address of the first border session controller for connecting to the called device, so that the second border session controller determines that the calling device belongs to When the media domain is the same as the access media domain to which the called device belongs, the media address of the first border session controller for connecting to the called device is delivered to the called device;

Receiving a second call response sent by the second border session controller, where the second call response carries a media address of the called device to establish a network between the first border session controller and the called device Telephone call connection;

And transmitting a third call response to the calling device to establish a network telephone call connection between the first border session controller and the calling device.

2. The method of claim 1 wherein

The second call request carries a media address of a first border session controller for connecting to the called device through an extension of the media level a line in the session description protocol.

3. The method of claim 2, wherein

The second call response carries the media address of the called device through an extension of the media level a line in the session description protocol.

The method according to any one of claims 1 to 3, wherein before the sending the third call response to the calling device, the method further includes:

Allocating a media address to the first border session controller of the calling device;

After determining that the second call response carries the media address of the called device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the first to the calling device is internally established. A media session connection between the media address of the border session controller and the media address of the first border session controller used to connect to the called device.

The method according to any one of claims 1 to 3, characterized in that

The second call request further includes access media domain information of the calling device, where the calling device The access media domain information indicates an access media domain to which the calling device belongs;

The second call response further includes the access media domain information of the called device, and the access media domain information of the called device indicates the access media domain to which the called device belongs.

6. A method for establishing a network telephone call, comprising:

Receiving a second call request sent by the first border session controller, where the second call request carries a media address of a first border session controller for connecting to the called device;

When the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address of the first border session controller for connecting to the called device is used as the second device for connecting the called device. a media address of the border session controller, sending a third call request to the called device;

Receiving a first call response returned by the called device;

Transmitting, according to the first call response, a second call response to the first border session controller, where the second call response carries a media address of the called device to establish the first border session controller and the A network telephone call connection between the devices is called, and a network telephone call connection between the first border session controller and the calling device is established.

7. The method of claim 6 wherein:

8. The method of claim 7 wherein:

9. A method according to any one of claims 6 to 8, characterized in that

The second call request further includes the access media domain information of the calling device, and the access media domain information of the calling device indicates the access media domain to which the calling device belongs;

A method for establishing a network telephone call, comprising:

Receiving a first call request sent by the calling device;

Sending a fourth call request to the second border session controller according to the first call request, where the fourth call request carries a media address of the calling device, so that the second border session controller determines the called party The device is located under the network address switching device, and the fourth call request carries the media address of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs. The media address of the second border session controller of the calling device;

Receiving a fourth call response returned by the second border session controller, the fourth call response carrying a media address of a second border session controller for connecting to the calling device;

Determining that the fourth call response carries a media address of a second border session controller for connecting to the calling device, and the access device belongs to the access media domain to which the called device belongs. Transmitting, by the media address of the second border session controller of the calling device, as a media address of the first border session controller for connecting the calling device, sending a fifth call response to the calling device, to establish the A network telephone call connection between the two border session controller and the calling device.

11. The method of claim 10, wherein

The fourth call request carries the media address of the calling device through an extension of the media level a line in the session description protocol.

12. The method of claim 11 wherein:

The fourth call response carries a media address of a second border session controller for connecting to the calling device through an extension of the media level a line in the session description protocol.

The method according to any one of claims 10 to 12, further comprising: the fourth call request further carrying access media domain information of the calling device, and the access of the calling device The media domain information indicates an access media domain to which the calling device belongs;

The fourth call response further includes the access media domain information of the called device, and the access media domain information of the called device indicates the access media domain to which the called device belongs.

14. A method for establishing a VoIP call, comprising:

Receiving a fourth call request sent by the first border session controller, where the fourth call request carries a media address of the calling device;

Determining that the called device is located under the network address switching device, and the fourth call request carries the media address of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs. Allocating a media address of a second border session controller for connecting to the calling device; sending a fifth call request to the called device according to the fourth call request;

Receiving a first call response returned by the called device to establish the second border session controller a network telephone call connection with the called device;

Transmitting, according to the first call response, a fourth call response to the first border session controller, where the fourth call response carries a media address of a second border session controller for connecting to the calling device, so that the A border session controller determines that the fourth call response carries a media address of a second border session controller for connecting to the calling device, and the access device belongs to the same access media domain as the called device belongs to Transmitting, by using a media address of the second border session controller for connecting the calling device as a media address of the first border session controller for connecting the calling device, sending a fifth call response to the calling device, Establishing a network telephone call connection between the second border session controller and the calling device.

15. The method of claim 14 wherein:

16. The method of claim 15 wherein:

The method according to any one of claims 14 to 16, further comprising: the fourth call request further carrying access media domain information of the calling device, and the access of the calling device The media domain information indicates an access media domain to which the calling device belongs;

18. A network telephone call setup device, comprising:

An allocating unit, configured to allocate, according to the first call request, a media address of the first border session controller for connecting to the called device when the calling device is located under the network address switching device;

a first sending unit, configured to send a second call request to the second border session controller, where the second call request carries a media address used to connect the first border session controller of the called device, so that the second border session control When the device determines that the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address of the first border session controller for connecting the called device is transmitted to the called device; a second receiving unit, configured to receive a second call response sent by the second border session controller, where the second call response carries a media address of the called device to establish a relationship between the first border session controller and the called device The network gives a telephone call connection;

And a second sending unit, configured to send a third call response to the calling device, to establish a network telephone call connection between the first border session controller and the calling device.

The VoIP call setup device according to claim 18, wherein the first sending unit is configured to send a second call request to the second border session controller, where the second call request passes the session. An extension of the media level a line in the protocol is described to carry the media address of the first border session controller used to connect to the called device.

The VoIP call setup device according to claim 19, wherein the second receiving unit is configured to receive a second call response sent by the second border session controller, where the second call response is passed The extension of the media level a line in the session description protocol carries the media address of the called device.

The VoIP call setup device according to any one of claims 18 to 20, further comprising a processing unit;

a processing unit, configured to allocate a media address of the first border session controller to the calling device, determine that the second call response carries the media address of the called device, and the access device belongs to the access media domain and the called party When the access media domain to which the device belongs is the same, the medium between the media address of the first border session controller destined for the calling device and the media address of the first border session controller for connecting the called device is internally established. Session connection.

22. A network telephone call setup device, comprising:

a first receiving unit, configured to receive a second call request sent by the first border session controller, where the second call request carries a media address of a first border session controller for connecting to the called device; When the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, the media address of the first border session controller for connecting the called device is used as a connection for the called device. a media address of the second border session controller, sending a third call request to the called device;

a second sending unit, configured to send a second call response to the first border session according to the first call response The controller, the second call response carries a media address of the called device, to establish a network telephone call connection between the first border session controller and the called device, and establish a first border session controller and a calling device. Inter-network phone call connection.

The VoIP call setup device according to claim 22, wherein the first receiving unit is configured to receive a second call request sent by the first border session controller, where the second call request is passed The extension of the media level a line in the session description protocol carries the media address of the first border session controller for connecting to the called device.

The VoIP call setup device according to claim 23, wherein the second receiving unit is configured to send a second call response to the first border session controller according to the first call response, the second call The media address of the called device is carried in response to an extension of the media level a line in the session description protocol.

25. A network telephone call setup device, comprising:

a first sending unit, configured to send a fourth call request to the second border session controller according to the first call request, where the fourth call request carries a media address of the calling device, so that the second border session controller determines the called device The device is located in the network address switching device, and the fourth call request carries the media address of the calling device, and the access device belongs to the same as the access media domain to which the called device belongs. The media address of the second border session controller;

a second receiving unit, configured to receive a fourth call response returned by the second border session controller, where the fourth call response carries a media address of a second border session controller for connecting to the calling device; And determining, when the fourth call response carries a media address of the second border session controller for connecting to the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs, Transmitting a fifth call response to the calling device to establish a second border session control by using a media address of the second border session controller connected to the calling device as a media address of the first border session controller for connecting to the calling device A VoIP call connection between the device and the calling device.

The VoIP call setup device according to claim 25, wherein the first sending unit is configured to send a fourth call request to the second border session controller according to the first call request, where the The four call request carries the media address of the calling device through the extension of the media level a line in the session description protocol.

The VoIP call setup device according to claim 26, wherein the second receiving unit is configured to receive a fourth call response returned by the second border session controller, where the fourth call response is passed The extension of the media level a line in the session description protocol carries the media address of the second border session controller for connecting to the calling device.

28. A network telephone call setup device, comprising:

a first receiving unit, configured to receive a fourth call request sent by the first border session controller, where the fourth call request carries a media address of the calling device;

The allocating unit determines that the called device is located under the network address switching device, and the fourth call request carries the media address of the calling device, and the access media domain to which the calling device belongs is the same as the access media domain to which the called device belongs. And a second sending unit, configured to send a fifth call request to the called device according to the fourth call request, and a second receiving unit, configured to receive the called party The first call response returned by the device to establish a network telephone call connection between the second border session controller and the called device;

a second sending unit, configured to send a fourth call response to the first border session controller according to the first call response, where the fourth call response carries a media address of the second border session controller for connecting the calling device, so that The first border session controller determines that the fourth call response carries a media address of the second border session controller for connecting to the calling device, and the access device belongs to the access media domain to which the called device belongs. Transmitting, by using a media address of the second border session controller for connecting the calling device as a media address of the first border session controller for connecting the calling device, sending a fifth call response to the calling device, to establish a A VoIP call connection between the two border session controller and the calling device.

The VoIP call setup device according to claim 28, wherein the first receiving unit is configured to receive a fourth call request sent by the first border session controller, where the fourth call request is passed The extension of the media level a line in the session description protocol carries the media address of the calling device.

The VoIP call setup device according to claim 29, wherein the second sending unit is configured to send a fourth call response to the first border session controller according to the first call response, where the The four call response carries the media address of the second border session controller for connecting to the calling device through an extension of the media level a line in the session description protocol.

A communication system, comprising the network telephone call establishing apparatus of any one of claims 18 to 30.