WO2012019546A1

WO2012019546A1 - Method and system for establishing voice over ip call

Info

Publication number: WO2012019546A1
Application number: PCT/CN2011/078254
Authority: WO
Inventors: 骆文; 涂杨巍
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-08-12
Filing date: 2011-08-11
Publication date: 2012-02-16
Also published as: CN102377887A; CN102377887B

Abstract

Disclosed is a method for establishing a Voice over IP call. The method comprises: when receiving a Session Initial Protocol (SIP) INVITE message sent to a called terminal, a called Voice over IP (VoIP) server judging that the called terminal is currently in an IDLE state according to acquired state information of the called terminal, or judging that a terminal type of the called terminal is a mobile terminal according to acquired terminal type information of the called terminal, and performing corresponding call establishing operations. Also disclosed is a system for establishing a Voice over IP call. A call establishing unit is used for performing corresponding call establishing operations according to a judgment result of a judging unit. The method and system of the present invention can prevent the problems generated because the called VoIP server must wait for a long time to confirm that the SIP INVITE message is received by the called terminal.

Description

Method and system for realizing network telephone call establishment

The present invention relates to the field of communications, and in particular, to a method and system for establishing a voice over IP (VoIP) call. Background technique

VoIP is a technology that uses the Internet Protocol (IP) to transmit voice over the network. It is a hot spot for operators. FIG. 1 is a schematic diagram of a network structure for supporting a VoIP service. As shown in FIG. 1 , whether the called terminal or the calling terminal is connected to the access gateway through the base station, the access channel can reside on the data channel. (DPF, Data Path Function), Paging Controller (PC, Paging Controller) and Anchor AAuthenticator (AA), these entities can be combined on the same access gateway, or can be divided into On different access gateways. The role of the access gateway (DPF) includes as a sink node for communication between the terminal and the outside world to support data exchange between the terminal and the outside world; the role of the access gateway (PC) includes maintaining the terminal in idle (IDLE) mode. The status of the paging, the terminal in the idle mode, etc.; the role of the access gateway (AA) is to assist the authentication and authorization (AAA, Authentication, Authorization and Accounting) to implement authentication and authentication of the terminal. Among them, the IDLE mode is also called the IDLE state, and the two are equivalent.

The AAA server is an important facility in the communication network, which is used to implement network operators' control and management of data and users, and provides authentication, authorization and account services.

The VoIP server is a node used by the network to carry out VoIP services, including a SIP (Session Initial Protocol) registration for maintaining the terminal, a VoIP session between the calling terminal and the called terminal using the SIP protocol, and a session process. Responsible for the media stream, that is, the transmission of voice packets, media format conversion, and so on. VoIP server and access gateway and AAA server There are interfaces between them. The main function of the interface between the VoIP server and the AAA server is to obtain the end user account information from the AAA server to support the authorization of the user to use the VoIP service; the main function of the interface between the VoIP server and the access gateway is to support the VoIP server and the DPF. The interaction between the DPF and the terminal exchanges signaling and media streams related to the VoIP service. It should be noted that in the Worldwide Interoperability for Microwave Access (WiMAX) network, the VoIP server is also called WVS Server (WVS Server, WiMAX VoIP Service Server), and will not be described.

The left and right sides of the dotted line shown in Figure 1 represent the calling side and the called side, respectively. In addition to the calling terminal and the called terminal, the calling side and the called side also include network devices such as a base station, an access gateway, a VoIP server, and an AAA server, and serve the calling terminal and the called terminal respectively. The calling terminal and the called terminal are respectively registered to their respective VoIP servers. The two VoIP servers are connected through an IP network, such as the Internet, and the signaling and media streams between the calling terminal and the called terminal pass the IP. The network exchanges, as shown in Figure 1, there are two independent VoIP servers serving the calling terminal and the called terminal respectively. The calling terminal and the called terminal can also be registered to the same VoIP server. In this case, the two VoIP servers on both sides of the dotted line in Figure 1 can be the same physical entity.

The following describes the existing SIP registration technology to illustrate the SIP registration process of the terminal. The figure shows the process of registering a terminal with a VoIP server in the prior art. Since the SIP protocol is used between the terminal and the VoIP server, the registration process is also called the SIP registration process, and mainly includes the following steps:

Step 201: The terminal sends a SIP registration request to the VoIP server.

Step 202: The VoIP server processes the registration request according to the SIP protocol. After the terminal authentication succeeds, the VoIP server sends an access request message to the AAA server of the terminal.

Step 203: After receiving the access request message, the AAA server saves information such as the SIP registration validity period of the terminal, and returns the access acceptance to the VoIP server.

Step 204: The VoIP server returns a SIP registration response to the terminal, and completes the SIP registration process. The following describes the prior art related to IDLE, mainly explaining the process in which the IDLE state currently in the terminal is delivered to the AAA server of the terminal.

The terminal can achieve the purpose of power saving by entering the IDLE state. A mobile terminal in the IDLE state cannot be called (if a VoIP call cannot be accepted). Therefore, when a mobile terminal in the IDLE state needs to be called, the network (paging controller) must first page the mobile terminal and trigger the mobile terminal to exit the IDLE state. In the prior art, if the terminal needs to enter the IDLE state, the request is initiated by the terminal itself or by the network side entity, and the request for the terminal to enter the IDLE state is sent to the AA of the terminal, and the AA is allowed. After that, the terminal can enter the IDLE state. Take the process initiated by the terminal as an example. Figure 3 contains the following steps:

Step 301: The terminal sends a request message requesting to enter the IDLE state to the AA of the terminal through the access network.

Step 302: The AA checks whether the terminal meets the condition of entering the IDLE state. When the condition is met, the AA sends a charging update request message to the AAA server of the terminal, and carries an indication to notify the AAA server that the terminal is currently in the IDLE state. The charging update request message is an intermediate update request.

Step 303: The AAA server saves the status information that the terminal is currently in the IDLE state locally, and returns a charging update response message to the AA. The charging update response message is an intermediate update response.

Step 304: The AA returns an IDLE status entry response message to the terminal, and agrees that the terminal enters the IDLE state.

Each terminal in the IDLE state is assigned a paging cycle. In the prior art, the duration of the paging cycle should not be set too short, otherwise the power saving purpose cannot be achieved, especially for a terminal having a MIMO (Multiple Input Multiple Output) function. A typical minimum suitable length is 5.12 seconds. Taking the period value of 5.12 seconds as an example, the terminal in the IDLE state wakes up every 5.12 seconds and listens to whether there is a paging message for paging itself. The terminal does not accept any messages during the time. Therefore, if the PC wants to page the terminal, it must send a paging message at the point in time when the terminal wakes up, that is, the opportunity to wake up the terminal at most once every 5.12 seconds. If the terminal receives a paging message at the point in time when the terminal wakes up, the terminal triggers the process of exiting the IDLE state, and returns to the active state (mode;). In the ACTIVE state, the terminal can Accept the call.

In the prior art, when the calling terminal calls the called terminal, the calling party first needs to send a SIP INVITE signaling message to the called terminal. The process mainly includes the following contents: 1. The calling terminal will SIP. The INVITE signaling message is sent to the VoIP server of the calling terminal (the calling VoIP server, the left side of the dotted line in Figure 1). Specifically, the calling terminal first sends the signaling message to the access gateway (an anchor DPF) in the form of an IP data packet, and then the access gateway sends the IP packet to the calling VoIP server.

2. The calling VoIP server parses the signaling message, finds the VoIP server of the called terminal (called the VoIP server, the right side of the dotted line in Figure 1), and sends the signaling message to the called VoIP server.

3. The called VoIP server sends the signaling message to the called terminal. Specifically, the called VoIP server sends the signaling to the access gateway (an anchor DPF) in the form of an IP data packet, and then the access gateway sends the IP packet to the called terminal through the base station.

In the above process, if the currently called terminal is in the IDLE state, after the called VoIP server sends the SIP INVITE signaling message to the anchor DPF in the form of an IP packet, the anchor DPF cannot continue to send the IP packet. To the called terminal, this IP packet can only be cached locally. At the same time, the anchor DPF notifies the PC of the terminal that the data sent to the called terminal arrives; after the PC performs the paging process to prompt the terminal to exit the IDLE state, the anchor DPF then passes the cached signaling message in the form of an IP packet. The base station sends to the called terminal.

In summary, since the PC must page the terminal at the point in time when the terminal wakes up, in the worst case, when the anchor DPF notifies the PC to page the terminal, the terminal has just woken up once. At this time, the PC must wait for the paging cycle of an entire terminal to page the terminal. In fact, In order to achieve the purpose of power saving of the terminal, the setting of the paging cycle of the terminal is generally not too short, and generally is greater than the typical minimum suitable duration (5.12 seconds). Therefore, it takes time for the PC to page the terminal and trigger the terminal to exit the IDLE state. For a long time, the called VoIP server wants to confirm that the SIP INVITE message is received by the called terminal and has to wait for a long time, and waiting for a long time will lead to the following problems:

a. The called VoIP server does not get the response of the called terminal for a long time, which will cause the called VoIP server timer to time out, and resend the SIP INVITE signaling message, or even resend it more than once. These messages will be treated as IP. The package is stacked in the anchor DPF. When the called terminal exits the IDLE state and returns to the ACTIVE state, the access gateway sends all the accumulated IP packets to the called terminal at one time, so that the called terminal receives multiple SIP INVITE messages at the same time, causing the called terminal to process. Failure, resulting in call setup failure;

b. The called VoIP server does not get the response of the called terminal for a long time, and it will judge that the terminal is currently offline or unreachable, which in turn triggers the execution of unnecessary call forwarding services (for example, offline transfer). In this way, one is to waste network resources; the second is to charge the user's service usage fee; the third is to cause the called user to question the network capability, because the called user is in the boot state. But can't receive the call. Both the second and third will cause the called user to be greatly dissatisfied with the operator, which will reduce the reputation of the operator, which is not conducive to business development. Fourth, after the call forwarding service is executed, the called terminal exits the IDLE state and receives the anchor DPF. After the cached SIP INVITE message, the called terminal will process the message normally and send a SIP response to the calling party. At this point, the caller will receive a response from the called party and a SIP response from another terminal after the call transfer, which will cause the caller to confuse the call, causing the call setup to fail;

c. The calling user does not hear the ring back tone (RBT, Ring Back Tone) for a long time, and will think that the network is faulty, and choose to abandon the call, and complain to the operator that the network quality is poor, resulting in lower satisfaction of the calling user. It is also not conducive to operators to conduct business. Summary of the invention

In view of this, the main object of the present invention is to provide a method and system for implementing VoIP call setup, which can avoid the situation that the called VoIP server wants to confirm that the SIP INVITE message has to wait for a long time after being received by the called terminal. The above series of questions.

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

A method for implementing network telephone call setup, the method comprising: when a called network telephone (VoIP) server receives a Session Initiation Protocol (SIP) Invite (INVITE) message addressed to a called terminal, according to the obtained called terminal The status information determines that the called terminal is currently in an idle (IDLE) state, or determines that the terminal type of the called terminal is a mobile terminal according to the obtained terminal type information of the called terminal, and performs corresponding Call setup operation.

The obtaining the status information of the called terminal includes: an authentication authorization charging (AAA) server sends (push) the status information of the called terminal to the VoIP server.

The obtaining the status information of the called terminal or acquiring the terminal type information of the called terminal includes: the VoIP server actively requests (requests) from the AAA server, and acquires (pulls) the called terminal from the AAA server. The status information, or the terminal type of the called terminal, wherein the status information of the called terminal includes: the called terminal is currently in the IDLE state, or the called terminal is currently in an ACTIVE state.

The terminal type information of the called terminal includes: the terminal type of the called terminal is a mobile terminal, or the terminal type of the called terminal is a fixed terminal.

When it is determined that the called terminal is currently in the IDLE state, or the terminal type of the called terminal is determined to be a mobile terminal, the performed call setup operation includes: the called VoIP server adjusts the SIP message. The timer, the extended timeout period is long enough to complete the paging of the called terminal, and/or the called VoIP server returns a ringback tone message to the calling party.

A system for implementing network telephone call setup, the system comprising: a judging unit and a call setup Unit; among them,

The determining unit is configured to: when receiving the SIP INVITE message sent to the called terminal, determine, according to the obtained state information of the called terminal, that the current state of the called terminal is in an IDLE state, or according to the acquired state The terminal type information of the called terminal determines that the terminal type of the called terminal is a mobile terminal;

The call establishing unit is configured to perform a corresponding call setup operation according to the determination result of the determining unit.

The system further includes an obtaining unit, configured to obtain status information of the called terminal, and the acquiring includes: the AAA server directly sends (push) the status information of the called terminal to the VoIP server.

The system further includes an obtaining unit, configured to acquire status information of the called terminal, or obtain terminal type information of the called terminal; the obtaining includes the VoIP server actively requesting (requesting) from the AAA server, from the AAA The server acquires (pushes) the status information of the called terminal or the terminal type information of the called terminal.

The status information of the called terminal includes: the called terminal is currently in the IDLE state, or the called terminal is currently in the ACTIVE state.

The call establishing unit is further configured to: when it is determined that the current state of the called terminal is an IDLE state, or when determining that the terminal type of the called terminal is a mobile terminal, the called VoIP server adjusts the SIP. The timer of the message, the extension timeout is long enough to complete the paging of the called terminal, and/or the called VoIP server returns a ringback tone message to the calling party.

When the called VoIP server receives the SIP INVITE message addressed to the called terminal, it determines whether the current state of the called terminal is in the IDLE state according to the obtained state information of the called terminal, or according to the obtained called terminal. Terminal type information to determine the terminal class of the called terminal Whether the type is a mobile terminal, performs a corresponding call setup operation.

According to the present invention, the status information of the called terminal or the terminal type information of the called terminal can be obtained, thereby determining whether the current state of the called terminal is in the IDLE state according to the acquired status information of the called terminal, or according to the obtained The terminal type information of the called terminal determines whether the terminal type of the called terminal is a mobile terminal to perform a corresponding call setup operation, and can avoid waiting for the called VoIP server to confirm that the SIP INVITE message is received by the called terminal. The above series of problems caused by long time. DRAWINGS

FIG. 1 is a schematic diagram of a network structure supporting a VoIP service in the prior art;

2 is a flow chart of registering a terminal with a VoIP server in the prior art;

3 is a flow chart of the AAA server in which the IDLE status of the terminal is transmitted to the terminal in the prior art;

4 is a flowchart of acquiring status information of a called terminal according to Embodiment 1 of the present invention;

5 is a flowchart of implementing VoIP call establishment when a called terminal is in an IDLE state according to Embodiment 1 of the present invention;

6 is a flowchart of acquiring status information of a called terminal according to Embodiment 2 of the present invention;

FIG. 7 is a flowchart of implementing VoIP call establishment when the called terminal is in the IDLE state according to the second embodiment of the present invention. detailed description

The basic idea of the present invention is: Receive a SIP addressed to the called terminal at the called VoIP server.

In the INVITE message, it is determined whether the current state of the called terminal is the IDLE state according to the acquired state information of the called terminal, or whether the terminal type of the called terminal is a mobile terminal according to the acquired terminal type information of the called terminal. Perform the corresponding call setup operation.

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings. The prior art can only call the called terminal when the called terminal exits the IDLE state, so as to implement VoIP call setup, that is, it is necessary to wait until the called terminal wakes up at the time point to page the terminal. It takes a long time from waiting for the point in time to paging the called terminal and triggering the called terminal to exit the IDLE state. According to the solution of the present invention, before the called VoIP server sends the SIP INVITE message to the called terminal, the judgment is performed according to the obtained state information of the called terminal, or the judgment according to the obtained terminal type of the called terminal is added ( Fixed terminal\mobile terminal), which determines the process of performing the operation, realizes the VoIP call establishment when the called terminal is in the IDLE state, and can avoid waiting for the called VoIP server to confirm that the SIP INVITE message is received by the called terminal. The above series of problems caused by a long time.

A method for implementing VoIP call establishment mainly includes the following contents:

When the called VoIP server receives the SIP INVITE message addressed to the called terminal, it determines whether the current state of the called terminal is in the IDLE state according to the obtained status information of the called terminal, or according to the acquired terminal of the called terminal. The type information determines whether the terminal type of the called terminal is a mobile terminal, thereby determining which corresponding operation is performed.

Here, the corresponding operation performed by the called terminal in the IDLE state is different from the corresponding operation performed by the called terminal in the IDLE state; the terminal type of the called terminal is The corresponding operation performed by the mobile terminal and the terminal type of the called terminal are different from the corresponding operations performed by the fixed terminal.

Further, obtaining the status information of the called terminal specifically includes: the AAA server notifying the VoIP server of the status information of the called terminal.

Further, obtaining the status information of the called terminal, or acquiring the terminal type information of the called terminal, specifically includes: in the process of establishing the call, the VoIP server actively requests the AAA server for the status information of the called terminal, or the terminal of the called terminal. Type information.

Further, obtaining the status information of the called terminal specifically includes: in the process of registering the called terminal to the VoIP server, the VoIP server requests the AAA server for the terminal type of the called terminal. Information.

Further, the status information of the called terminal specifically includes: the called terminal is currently in the IDLE state, or the called terminal is currently in the ACTIVE state.

Further, the terminal type information of the called terminal specifically includes: the current terminal type of the called terminal is a mobile terminal, or the called terminal is currently a fixed terminal.

Further, the called VoIP server sends the SIP INVITE message sent to the called terminal to the called terminal.

Further, after the current state information of the called terminal or the terminal type information of the called terminal is obtained, the corresponding operations performed by the VoIP server specifically include:

When it is determined that the called terminal is currently in the IDLE state, or it is determined that the terminal type of the called terminal is a mobile terminal, the called VoIP server adjusts (resets) the timer of the SIP message (such as a SIP INVITE message) ( The timer may be a timeout timer), the timeout period is extended to allow the network to complete paging to the called terminal; and/or the called VoIP server returns a ringback tone message to the calling party;

Further, the calling party includes one of the following: a calling terminal, or a calling VoIP server. The invention is illustrated by way of example below.

Embodiment 1: After the VoIP server requests the AAA server, the AAA server obtains the status information of the terminal.

When the terminal is called as the called terminal, the called VoIP server receives the SIP INVITE message sent from the calling terminal to the called terminal, firstly to the AAA server of the called terminal, and queries whether the called terminal status information is The calling terminal is currently in the IDLE state. If the called terminal is currently in the IDLE state, the timeout timer of the SIP message is adjusted (reset), the timeout period is extended, and the ringback tone is returned to the calling party.

As shown in FIG. 4, the VoIP server obtains the terminal status information from the AAA server, and the general process can be executed whether it is called or not. The process includes the following steps: Step 401: The VoIP server sends a terminal status information request message to the AAA server, where the terminal status information request message carries the identifier of the terminal.

Here, preferably, the identifier of the terminal may be a network access identifier (NAI) of the terminal, or an identifier used by the terminal to use the VoIP service.

Here, preferably, the terminal status information request message further carries an indication (Indication) for instructing the AAA server to return the current status of the designated terminal, or an indication that the AAA server returns whether the designated terminal is in the IDLE state.

Here, preferably, the terminal status information request message may be an AAA message, for example, a message defined by a Remote Authentication Dial In User Service (RADIUS) protocol, or a message defined by a Diameter protocol. When the RADIUS protocol is used, the terminal status information request message corresponds to an access request (Access-Request) message.

Step 402: The AAA server returns a terminal status information response message to the VoIP server, where the current status of the specified terminal is carried.

Here, preferably, the state is used to indicate that the terminal is currently in the IDLE state, or is in the ACTIVE state; or the state is a 1/0 value (true/false value), 1 indicates that the terminal is in the IDLE state, and 0 indicates that the terminal is not in the IDLE state. status.

Here, preferentially, when the terminal is in the IDLE state, the terminal status information response message may also be used to send the paging cycle value of the terminal to the VoIP server.

Here, preferably, the terminal status information response message may be an AAA message as described in step 401. When the RADIUS protocol is used, the terminal status information response message corresponds to an Access-Accept message.

Using the process described in FIG. 4, after the called VoIP server receives the SIP INVITE message, it can obtain information about whether the called terminal is currently in the IDLE state from the AAA server of the called terminal; and, preferably, when determined to be When the terminal is in the IDLE state, the VoIP server can also know the paging cycle of the called terminal. As shown in FIG. 5, when the called terminal is in the IDLE state, the process of supporting the VoIP call establishment includes the following steps:

Step 501: The SIP INVITE message sent by the calling terminal to the called terminal is first sent to the calling VoIP server.

Step 502: The calling VoIP server returns to the calling terminal SIP is trying (SIP 100

(Trying) ) Message.

Step 503~Step 504: The calling VoIP server queries the AAA server of the calling terminal to query whether the called terminal is allowed to call. This embodiment assumes that the AAA server returns a positive response to the calling VoIP server.

Step 505: The calling VoIP server finds the called VoIP server and sends the above SIP INVITE message to the called VoIP server.

Step 506: The called VoIP server returns a SIP 100 (Trying) message to the calling VoIP server.

Step 507: The called VoIP server sends a terminal status information request message to the AAA server of the called terminal to request the current status of the called terminal (as described in step 401).

Here, the called VoIP server can find the AAA server of the called terminal according to the identifier of the called terminal carried in the SIP INVITE message from the calling VoIP server, in particular, the domain name information carried in the identifier.

Step 508: The AAA server of the called terminal acquires current status information of the called terminal, and returns the status information to the called VoIP server according to step 402.

In addition, if the AAA server of the called terminal does not have the status information of the called terminal, the AAA server may send a message to the AA of the called terminal to query the current status of the called terminal; or, the called terminal After receiving the query request from the called VoIP server, the AAA server always goes to the AA query of the called terminal, that is, the AAA server requests the AA to exchange the status information of the terminal, and finally the AAA server of the called terminal obtains the status information. . Here, the message sent by the AAA server to the AA is an AAA message (RADIUS, or Diameter). When the RADIUS protocol is used, the AAA message may be a RADIUS CoA message, and the AA responds to the AAA server by using a RADIUS CoA ACK message, where the current terminal is carried. Status information.

Step 509: When the information obtained from the AAA server indicates that the called terminal is currently in the IDLE state, the VoIP server extends the waiting timeout timer duration for the SIP INVITE message.

Here, the extended timeout period of the timer can be customized by the operator. For example, according to the network deployment of the operator, the maximum paging period of the called terminal is 20 seconds, and the timeout period may be determined by referring to 20 seconds (for example, 25 seconds) to accommodate the worst case; or The duration is determined by referring to the paging cycle of the called terminal (as described in step 402, the VoIP server can obtain the paging period value of the called terminal from the AAA server). In this way, depending on the called terminal, the VoIP server can set different timeout durations. Before the timer expires, the VoIP server does not resend the SIP INVITE message, and does not trigger services such as call forwarding.

Step 510~Step 511: The called VoIP server sends a ringback response (SIP 180) to the calling VoIP server; the calling VoIP server further sends SIP 180 to the calling terminal, and plays the RBT to the calling user, prompting the user to wait.

Step 512: The called VoIP server sends a SIP INVITE message to the called terminal, and the message is first sent in the form of a data packet to the access network of the called terminal (the called anchor DPF). And start the above timeout timer.

It should be noted here that step 512 and step 510 can be performed simultaneously.

Step 513: At this time, the access network finds that the called terminal is in the IDLE state, so the triggering PC initiates paging to the called terminal, prompting the called terminal to exit the IDLE state.

Step 514: After the called terminal exits the IDLE state, the access network of the terminal sends the above data packet (containing the SIP INVITE message) to the called terminal.

Step 515: After processing the SIP message, the terminal returns a SIP to the called VoIP server. 100 ( Trying ) message. At this point, the called VoIP server receives the message before the timer expires.

Step 516: Since the current terminal has exited the IDLE state and enters the ACVITE state, the subsequent steps are the same as the prior art, and are not described again.

In fact, while querying the status of the called terminal, the VoIP server of the called terminal can send the SIP INVITE message to the called terminal, which is beneficial to reduce the delay of the entire call setup, that is, steps 507 and 512 can be simultaneously carried out.

Embodiment 2: The AAA server directly notifies the terminal status information to the VoIP server registered by the terminal, so that the VoIP server acquires the terminal status information.

When the AAA server of the terminal receives the indication that the terminal enters the IDLE state, it actively informs the VoIP server registered by the terminal. In this way, when the terminal is called as the called terminal, the called VoIP server can directly obtain the state of the called terminal locally.

As shown in FIG. 6, the AAA server notifies the VoIP server of the terminal status information to the terminal to register the VoIP server, so that the VoIP server can obtain the terminal status information, whether it is called or not, can perform the general process. The process includes the following steps:

Step 601: The AAA server sends a terminal status information update message to the VoIP server, where the terminal status information update message carries the identifier of the terminal.

Here, preferably, the identifier of the terminal may be the NAI of the terminal, or the identifier used by the terminal to use the VoIP service.

Here, preferably, the step is triggered by the AAA server receiving the charging update request message as described in step 302. The charging update request message can be represented by "Billing - Intermediate Update Request".

It should be noted here that, as shown in FIG. 2, when the terminal registers with the VoIP server, the VoIP server sends a message (access request message) to the AAA server of the terminal. Here, the VoIP server is also required to carry its own identifier in the message, and send its own identifier (preferably, also including an IP address) to the AAA server, and the AAA server saves it locally. In this way, In this step, the AAA can find the VoIP server registered by the terminal, and send the terminal status information update message to the terminal.

Here, preferably, according to the description of the current terminal status carried in the foregoing “Bill-Intermediate Update Request”, the terminal status information update message further carries an indication for indicating the current status of the terminal, or carries whether the terminal is in IDLE. An indication of the status.

For example, if the "Bill-Intermediate Update Request" carries a description that the terminal is currently in (or not in) the IDLE state, then the above indication will be used to inform the VoIP server that the terminal is in (or not in) the IDLE state.

Here, preferably, when the terminal is in the IDLE state, the terminal status information update message may further carry the paging period value of the terminal.

Here, preferably, the terminal status information update message may be an AAA message, for example, a message defined by using a RADIUS protocol, or a message defined by a Diameter protocol. When the RADIUS protocol is used, the called terminal status information update message is a CoA Request (Change of Authorization Request) message.

Step 602: The VoIP server sends a terminal status information update response message to the AAA server. Here, the VoIP server receives the indication of the terminal status information update message for indicating the current status of the terminal, or the indication of whether the terminal is in the IDLE state, and saves the status of the terminal (eg, in the IDLE state). local. For example, the state of the terminal is saved by using the identifier of the terminal as an index.

Here, preferably, the terminal status information update response message may be an AAA message, for example, a message defined by using a RADIUS protocol, or a message defined by a Diameter protocol. When the RADIUS protocol is used, the terminal status information update response message is a CoA ACK (Change of Authorization ACK) message.

Using the flow described in FIG. 6, the VoIP server registered by the terminal can know the current state of the terminal in real time or in near real time, or know that the current terminal is in/out of the IDLE state. at this time, When the terminal is called (ie, as the called terminal), the VoIP server of the terminal (in this case, the called VoIP server) can locally query whether the called terminal is currently in the IDLE state.

As shown in FIG. 7, when the called terminal is in the IDLE state, the process of supporting the VoIP call establishment includes the following steps:

Step 701 - Step 706: Same as step 501 to step 506.

Step 707: The called VoIP server locally queries the current state of the called terminal.

As shown in FIG. 6, the AAA server of the called terminal will send the called terminal's paging period value to the called terminal to register the current state of the called terminal, and preferably, when the called terminal is in the IDLE state. VoIP server. Therefore, after receiving the SIP INVITE message, the VoIP server can obtain the current state information of the called terminal locally, and determine whether the called terminal is currently in the IDLE state.

Step 708: When it is determined that the called terminal is currently in the IDLE state, as described in step 509, the VoIP server extends the waiting timeout timer duration for the SIP INVITE message.

Step 709~Step 715: Same as step 510~Step 516.

Through the process described in this embodiment, the called VoIP server acquires that the called terminal is currently in the

After the information of the IDLE state, the timer itself is extended to solve the problem of the prior art. At the same time, the called VoIP server also plays a ringback tone to the calling terminal in advance to prompt the calling party to wait, which also solves the defect that the prior art will cause the satisfaction of the calling user to decrease.

Embodiment 3: The VoIP server acquires the terminal type information of the terminal from the AAA server, and learns whether the current terminal type is a mobile terminal or a fixed terminal. In general, the fixed terminal does not consider the power saving problem, that is, the fixed terminal does not enter the IDLE state. When the terminal is called as the called terminal, the called VoIP server knows the type of the called terminal: If the called terminal is a mobile terminal, adjust (reset) the timeout timer of the SIP message, and extend the timeout period. , returning a ringback tone to the calling party.

As shown in Figure 2, when the terminal registers with the VoIP server, the VoIP server will go to the terminal. The AAA server sends a message (access request message), and after the AAA server of the terminal performs the corresponding processing, it returns a response message (access acceptance) to the VoIP server. Here, the AAA of the terminal is also required to return the type information of the terminal to the terminal. For example, the type information indicates that the terminal is a mobile terminal or a fixed terminal; or the type information indicates whether the terminal is a mobile terminal. After obtaining the type information of the terminal, the VoIP server saves the information locally.

In the prior art, the subscription information of the user stored on the AAA may indicate that the user is a fixed terminal user, or a nomadic terminal user, or a mobile terminal user. According to this, in the present invention, the AAA can determine the type of the terminal according to the subscription information of the user: determining the terminal of the contracted fixed terminal user as the fixed terminal; determining the terminal of the subscription mobile terminal user as the mobile terminal; signing the nomadic terminal The user can be determined as a fixed terminal or a mobile terminal according to the operator policy.

When the terminal is called as the called terminal, referring to the flow shown in Figure 7, the process of supporting the establishment of the VoIP call includes the following steps:

Step 801 to step 806: Same as step 701 to step 706.

Step 807: The called VoIP server locally queries the terminal type of the called terminal.

As mentioned above, in the SIP registration process, the called VoIP server can obtain the type of the called terminal from the called AAA server and save it locally. In this step, the VoIP server can obtain the type of the called terminal locally. When it is determined that the called terminal is a mobile terminal (the terminal may be in the IDLE state or may not be in the IDLE state), the following steps 808-810 are performed; otherwise, the SIP call flow in the prior art is executed, and the SIP INVITE message is sent to the called party. Terminal (the terminal must not be in the IDLE state). The following assumes that the type of the terminal is a mobile terminal.

Step 808: When it is determined that the terminal is a mobile terminal, as described in step 509, the VoIP server extends the waiting timeout timer duration for the SIP INVITE message.

Step 809~Step 810: Same as step 510~Step 511.

Step 811: The called VoIP server sends a SIP INVITE message to the called terminal, and the message is first sent to the access network of the called terminal in the form of a data packet. Step 812: If the called terminal is currently in the IDLE state, the access network triggers the execution of the paging terminal process, so that the called terminal exits the IDLE state. If the called terminal is not in the IDLE state, this step is not performed, and step 813 is directly executed.

Step 813: The access network of the terminal sends the foregoing data packet (containing the SIP INVITE message) to the called terminal.

Step 814~Step 815: Same as step 515 (714) ~ step 516 (715).

With this method, when it is determined that the terminal is a mobile terminal, whether the terminal is in the IDLE state or not, the method is processed according to the method in which the terminal is in the IDLE state, and the problem existing in the prior art can be solved.

The terminal type does not change after the terminal enters the network. Therefore, the VoIP server obtains the terminal type from the AAA server during the SIP registration process of the terminal. Of course, the possibility that the VoIP server does not acquire the terminal type in the SIP registration process is not excluded. For example, after the called VoIP server receives the SIP INVITE message sent to the called terminal (refer to the example shown in FIG. 5), it finds that the terminal type information of the called terminal is not saved locally, and the AAA server can be sent to the called terminal. Request the type of the terminal. Preferably, after the response of the AAA server is obtained, the type information is saved locally. Similarly, in this case, the interaction between the VoIP server and the AAA can also use the RADIUS protocol, or the Diameter protocol, and will not be described again.

It should be noted here that in the WiMAX network, the above VoIP server is also called WVS Server. In the above two embodiments, the VoIP server equivalent can be replaced with the WVS server, and the principle is the same.

A system for establishing a VoIP call, the system comprising: a judging unit and a call establishing unit, wherein the judging unit is configured to judge, according to the acquired state information of the called terminal, when receiving the SIP INVITE message addressed to the called terminal The terminal is currently in the IDLE state, or determines the terminal type of the called terminal as the mobile terminal according to the obtained terminal type information of the called terminal. The call establishing unit is configured to perform a corresponding call establishing operation according to the judgment result of the determining unit. Here, the system further includes an obtaining unit, configured to obtain status information of the called terminal, and the acquiring includes the AAA server directly transmitting (pushing) the status information of the called terminal to the VoIP server.

Here, the system further includes an obtaining unit, configured to acquire state information of the called terminal, or obtain terminal type information of the called terminal; the obtaining includes: the VoIP server actively requests (requests) from the AAA server, and obtains from the AAA server. (pull) the status information of the called terminal, or the terminal type information of the called terminal.

Here, the status information of the called terminal specifically includes: the called terminal is currently in the IDLE state, or the called terminal is currently in the ACTIVE state.

Here, the terminal type information of the called terminal specifically includes: the terminal type of the called terminal is a mobile terminal, or the terminal type of the called terminal is a fixed terminal.

Here, the call setup unit is further configured to: when determining that the called terminal is currently in the IDLE state, or determining that the terminal type of the called terminal is a mobile terminal, the called VoIP server adjusts (resets) the timing of the SIP message. The extension timeout is long enough to complete the paging of the called terminal, and/or the called VoIP server returns a ringback tone message to the calling party.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for implementing VoIP call setup, the method comprising: when a called VoIP server receives a Session Initiation Protocol (SIP) invite (INVITE) message addressed to a called terminal, Determining, according to the obtained status information of the called terminal, that the called terminal is in an idle (IDLE) state, or determining, according to the obtained terminal type information of the called terminal, that the terminal type of the called terminal is The mobile terminal performs a corresponding call setup operation.

The method according to claim 1, wherein the obtaining the status information of the called terminal comprises: an authentication authorization charging (AAA) server sending the status information of the called terminal to a VoIP server.

The method according to claim 1, wherein the obtaining the status information of the called terminal or obtaining the terminal type information of the called terminal comprises: the VoIP server actively requests from the AAA server, and obtains from the AAA server. Status information of the called terminal or terminal type information of the called terminal.

The method according to any one of claims 1 to 3, wherein the status information of the called terminal comprises: the called terminal is currently in an IDLE state, or the called terminal is currently in an active (ACTIVE) state. .

The method according to any one of claims 1 to 3, wherein the terminal type information of the called terminal comprises: the terminal type of the called terminal is a mobile terminal, or the terminal type of the called terminal is Fixed terminal.

The method according to any one of claims 1 to 3, wherein when it is determined that the called terminal is currently in the IDLE state, or the terminal type of the called terminal is determined to be In the case of the mobile terminal, the call setup operation performed includes: a timer for the called VoIP server to adjust the SIP message, extending the timeout period to be sufficient to complete paging to the called terminal, and/or the called VoIP server returning to the calling party Ringback tone message.

The method according to claim 1, further comprising: the called VoIP server transmitting a SIP INVITE message to the called terminal.

8. A system for establishing a network telephone call, the system comprising: a judging unit and a call establishing unit;

The system according to claim 8, wherein the system further comprises an obtaining unit, configured to acquire state information of the called terminal; and the obtaining comprises: directly, by the AAA server, status information of the called terminal. Send to the VoIP server.

The system according to claim 8, wherein the system further comprises an obtaining unit, configured to acquire state information of the called terminal, or obtain terminal type information of the called terminal; The VoIP server actively requests the AAA server to obtain the status information of the called terminal or the terminal type information of the called terminal from the AAA server.

The system according to any one of claims 8 to 10, wherein the status information of the called terminal comprises: the called terminal is currently in an IDLE state, or the called terminal is currently in an ACTIVE state.

The system according to any one of claims 8 to 10, wherein the terminal type information of the called terminal comprises: the terminal type of the called terminal is a mobile terminal, or the terminal type of the called terminal is Fixed terminal.

The system according to any one of claims 8 to 10, wherein the call establishing unit is further configured to: when it is determined that the called terminal is currently in an IDLE state Or, when it is determined that the terminal type of the called terminal is a mobile terminal, the called VoIP server adjusts the timer of the SIP message, and extends the timeout period to be sufficient to complete paging to the called terminal, and/or called The VoIP server returns a ringback tone message to the calling party.