CN103685200B - The method and system of service quality bearer resources control in access negotiation, release - Google Patents

Abstract

The invention discloses a method and system for controlling quality of service bearer resources in access negotiation, wherein the method includes: during media resource access negotiation, the network element on the calling side receives the INVITE200OK message sent by the terminal on the called side, and detects When the current call is a SIP Forking scenario, only the media resources negotiated in the call session of this branch are updated, and the resources carried by the sessions negotiated in other branches are not processed. The present invention also discloses a method and system for controlling quality of service bearer resources during release, wherein the method includes: during release of media resources, the network element on the calling side receives a BYE message, detects that the call is a SIP Forking scenario, and only Release the media resources negotiated by the call session of this branch, and do not process the resources bearer negotiated by other branch sessions. By adopting the present invention, it can adapt to the resource bearing requirement of the SIP Forking scene.

Description

Method and system for controlling quality of service bearer resources during access negotiation and release

technical field

The present invention relates to resource control technology in the communication field, and in particular to an IP Multimedia Subsystem (IMS, IPMultimedia Subsystem) where a called user generates a Session Initiation Protocol (SIP, Session Initiation Protocol) forking. A control function (P-CSCF, Proxy CallSession Control Function) method and system for controlling quality of service (QoS, Quality of Service) bearer resources during access negotiation or release.

Background technique

In the traditional Public Switched Telephone Network (PSTN, Public Switched Telephone Network), QoS has always been attached great importance to. Because the traditional transmission services are relatively simple, and the network operation area is also relatively simple, it is only necessary to guarantee a certain QoS for the transmission layer. up. The code stream transmitted in the next generation network (NGN, Next Generation Network) can be low-speed, high-delay non-real-time data, high-speed, low-delay multimedia stream, and these real-time and non-real-time data streams can also be combined. Coexistence of data streams, these data streams of different media require stricter requirements for end-to-end QoS in NGN.

As an important evolution of NGN, IMS provides network QoS guarantee. Figure 1 is a reference frame for implementing QoS control in IMS, where the Rx interface is a standard interface between the proxy call session control function and the policy charging rule function. The entire framework includes: User Equipment (UE, User Equipment) 101, P-CSCF 102, Policy and Charging Rule Function (PCRF, Policy and Charging Rule Function) 103, Serving Call Session Control Function (S-CSCF, Serving CallSession Control Function) 104, In addition, functions such as Interconnection Border Control Function (IBCF, Interconnection Border Control Function) 105, Inquiry Call Session Control Function (I-CSCF, Interrogating Call Session Control Function) 106, (MGCF, Media Gateway Control Function) 107 are also involved in the session process entity.

According to the description of the 3GPP standard protocol TS29.214, policy and charging control (PCC, Policy and Charging Control) is implemented through the Rx reference point in the IMS. According to the protocol description, the application function (AF, ApplicationFunction) provides session information to the PCRF network element, and the session information is mapped from the Session Description Protocol (SDP, Session Description Protocol) part of the SIP signaling to Diameter authorization authentication according to the protocol 3GPPTS29.213 The related flow information AVP in the request (Diameter AAR) message corresponds to the media flow information controlled by the PCRF. Wherein, the AF corresponds to the P-CSCF in the IMS. Wherein, the AVP refers to an attribute-value pair specified in the Diameter protocol.

SIP Forking is a basic function in the IMS system. The so-called SIP Forking refers to: multiple types of terminals share a user number, and the terminals can use different bearers or have different capabilities. When the user is called, the IMS network searches for the called user terminal. There are two types of terminals: parallel and serial. mode, the calling user selects a called user terminal to make a call according to a certain policy. Regardless of serial or parallel, the P-CSCF at the calling side needs to provide the PCRF with media resources negotiated between the calling terminal and the selected called terminal.

In the current protocol, in the multi-channel SIP Forking scenario, the calling side process of the QoS bearer resource control function is shown in Figure 2. Taking two channels as an example, the process includes the following steps:

Step 201, the UE initiates a call process, and the INVITE request message includes SDP request (offer) information;

Step 202, when the P-CSCF receives the call, it maps the SDP information to downlink media information;

Step 203, the P-CSCF forwards the INVITE request to the S-CSCF and sends it to the called party;

Steps 204 to 211 are the processing flow for the calling P-CSCF to receive two INVITE 180 messages from terminals.

Here, for the calling P-CSCF, there are two SIP sessions, one is the SIP session between the calling party and UE1, and the other is the SIP session between the calling party and UE2. At 205, a Diameter session is established between the P-CSCF and the PCRF for sending the Diameter AAR request message corresponding to the first path in 205 and the second path in 209; the SIP multipath indication (SIP-Forking-Indication AVP) is SINGLE_DIALOGUE(0), and carries the media information negotiated by UE 1; when receiving the second INVITE 180 message, the P-CSCF can determine that the called party has forking, and the SIP-Forking-Indication AVP in the Diameter AAR request message is It is SEVERAL_DIALOGUES(1), and carries the media information negotiated by UE2 at the same time;

Step 212, the S-CSCF forwards the INVITE 200 OK response message returned by the first terminal to the P-CSCF, including SDP answer information;

Step 213, when the P-CSCF receives the INVITE 200 OK, it maps the SDP information to uplink media information;

Step 214, the P-CSCF sends the Diameter AAR request message corresponding to the media negotiation between the calling party and the called UE1 to the PCRF network element to request resource authorization, wherein the Media-Component-Number AVP is filled in the Diameter AAR request message and the flow number (Flow-Number AVP) to jointly identify the media flow IP Flow generated by the combination of uplink and downlink media information, and fill in the SIP-Forking-Indication AVP as SINGLE_DIALOGUE (0); wherein, the IP Flow is the main The media resource negotiated between the caller and the selected called terminal;

Step 215, when the PCRF receives the SIP-Forking-Indication AVP as SINGLE_DIALOGUE (0), or an AVP without the SIP-Forking-Indication AVP, it updates the PCC rule according to the media resources carried in the current Diameter AAR request message, and removes the unmatched The PCC rule corresponding to the IP Flow carried in the current Diameter AAR request message, that is, remove the PCC rule corresponding to the IP Flow negotiated between the calling party and the called UE2, and send a Diameter AAA response message to the P-CSCF;

Step 216, the P-CSCF forwards the session response message to the UE on the calling side;

Step 217, if the calling user selects the first channel to answer, the calling user needs to send a BYE request message to tear down the established SIP session between the calling user and UE2;

Step 218, the P-CSCF releases the session resource established between the calling party and UE2;

Step 219, the P-CSCF sends a Diameter session termination request (Diameter STR) message request to the PCRF, and the PCRF will release the applied bearer resources;

In step 220, the P-CSCF forwards the BYE request.

It can be seen from the above process that for the SIP Forking scenario, using the existing technology, when the P-CSCF receives the first INVITE 200OK, the SIP-Forking-IndicationAVP in the Diameter AAR request message is set to SINGLE_DIALOGUE (0), and the PCRF is Use the corresponding IP Flow in the DiameterAAA request message corresponding to the INVITE 200OK to confirm the finally applied bearer resource, and then delete the PCC rule corresponding to the IP Flow negotiated between the calling and called UE2, and the P-CSCF receives the removal The BYE message of the UE2 session sends a Diameter STR message, and the Diameter STR message will release all the bearer resources applied for by this call.

However, in the SIP Forking scenario, according to the RFC3261 protocol description supported by it, during the media resource access negotiation process, regardless of serial or parallel mode, the INVITE200OK of multiple called terminals will be transparently transmitted to the calling user. The user will finally select the appropriate called terminal to answer according to the support request of the device and his own preference. The right to choose lies with the calling user, and the selected answering terminal may not necessarily be the first terminal to reply INVITE 200 OK, but Using the existing technology, the answering terminal selected by the calling user must be the first terminal that returns INVITE 200 OK; in addition, in the SIP Forking scenario, during the release of media resources, as long as all the called terminals return a temporary response (such as INVITE183 message), and the calling user finally answers the terminal that is not the terminal, it needs to send a BYE message to release the SIP session established with the terminal, and using the existing technology, the calling PCSCF will notify the PCRF to release all bearer resources.

It can be seen that the problems existing in the prior art are: 1) For the media resource access negotiation process under the SIP Forking scenario, the media resource negotiation under the condition that multiple called terminals return INVITE 200 OK is not supported; 2) For the SIP Forking scenario In the media resource release process, the calling party sends a BYE message to release a SIP session, and the bearer resources applied for by the entire call will be released. The normal bearer resources of any call cannot be guaranteed, so that the normal intercommunication of basic calls cannot be realized.

In a word, using the existing technology, the normal call processing in the SIP Forking scenario cannot be satisfied for the media resource access negotiation process and the QoS bearer resource control in the media resource release process in the SIP Forking scenario.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method and system for quality of service bearer resource control in access negotiation, to meet the needs of the media resource access negotiation process in the SIP Forking scenario, and to support multiple called terminals returning INVITE Media resource negotiation in case of 200 OK.

Another object of the present invention is to provide a method and system for controlling quality of service bearer resources during release, which can meet the requirements of the media resource release process in the SIP Forking scenario and avoid releasing all bearer resources.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A method for controlling quality of service bearer resources during access negotiation, the method comprising: during media resource access negotiation, the network element on the calling side receives an invitation INVITE 200 OK message sent by the terminal on the called side, and detects that the call is a session In the initial protocol SIP offloading forking scenario, only the media resources negotiated in the session of this branch are updated, and the resources carried by sessions negotiated in other branches are not processed.

Wherein, the calling side network element is specifically a proxy call session control function P-CSCF, and the method specifically includes:

The P-CSCF receives the INVITE 200 OK, if it detects that the call is a SIP Forking scenario, and there are other sessions alive in this call besides this branch session, then set the SIP-Forking-Indication AVP in the Diameter AAR message to SEVERAL_DIALOGUES (1) and sent to the policy charging rule function PCRF;

The PCRF receives the Diameter AAR message sent by the P-CSCF, updates the policy and charging control PCC rule corresponding to the IP Flow of the branch session carried in the DiameterAAR message, and performs negotiation on the The PCC rules corresponding to the IP Flow of other branch sessions do not perform any processing.

A system for controlling quality of service bearer resources in access negotiation, the system includes: a called side terminal and a calling side network element; wherein,

The called terminal is configured to send an INVITE 200 OK message to the calling network element;

The calling side network element is used to receive the invitation INVITE 200 OK message sent by the called side terminal, detect that the call is a SIP Forking scenario, and only update the media resources negotiated in the branch session, and do not process other Resource bearer for branch session negotiation.

Wherein, the network element on the calling side is specifically a P-CSCF, and the system also includes a PCRF;

The P-CSCF is used to send the SIP-Forking-Indication AVP in the Diameter AAR message when it detects that the call is a SIP Forking scenario and there are other sessions alive in the call except the fork session after receiving the INVITE 200 OK. set to SEVERAL_DIALOGUES(1) and sent to the PCRF;

The PCRF is configured to, after receiving the Diameter AAR message sent by the P-CSCF, update the PCC rule corresponding to the IP Flow of the branch session carried in the DiameterAAR message, and update the other The PCC rule corresponding to the IP Flow of the session does not perform any processing.

A method for controlling quality of service bearer resources during release, the method comprising: during release of media resources, the network element on the calling side receives a BYE message, detects that the call is a SIP Forking scenario, and performs only the media resources negotiated by the branch session Release, and do not process resource bearers negotiated by other branch sessions.

Wherein, the calling side network element is specifically a P-CSCF, and the method further includes: using a Diameter AAR message when negotiating a call branch session, and setting the SIP-Forking-Indication AVP to SEVERAL_DIALOGUES(1), the AVP of IP Flow property is set to remove.

Among them, the method specifically includes:

The P-CSCF receives the BYE message, if it detects that the call is a SIP Forking scenario, and other sessions survive in addition to the branch session in the call, the SIP-Forking-Indication AVP in the Diameter AAR message is set to SEVERAL_DIALOGUES( 1) and send it to PCRF; wherein, the Diameter AAR message also carries the bearer resource corresponding to the IP Flow of the branch session, and sets the AVP attribute of the IP Flow to remove;

The PCRF receives the Diameter AAR message sent by the P-CSCF, and according to the AVP attribute of the IPFlow, performs only the bearer resources corresponding to the IP Flow of the branch session carried in the Diameter AAR message that is set to be removed. freed.

Wherein, the calling side network element is specifically a P-CSCF, and the method further includes: using an extended Diameter STR message during negotiation of a call branch session, adding a SIP-Forking-IndicationAVP to the extended Diameter STR message and setting it to For SEVERAL_DIALOGUES(1); add the AVP attribute of IP Flow in the extended Diameter STR message.

Among them, the method specifically includes:

The P-CSCF receives the BYE message, if it detects that the call is a SIP Forking scenario, and there are other sessions alive in this call besides the branch session, the SIP-Forking-Indication AVP in the extended Diameter STR message is set to SEVERAL_DIALOGUES (1) and sent to PCRF; wherein, the extended DiameterSTR message also carries the bearer resource corresponding to the IP Flow of the branch session, and the AVP attribute of the IP Flow is set as the bearer resource corresponding to the branch session;

The PCRF receives the extended Diameter STR message sent by the P-CSCF, and according to the AVP attribute of the IPFlow, only releases the bearer resource corresponding to the IP Flow of the branch session carried in the DiameterAAR message.

Wherein, the calling side network element is specifically a P-CSCF, and the method further includes: not sending any Diameter message.

Among them, the method specifically includes:

The P-CSCF receives the BYE message, if it detects that the call is a SIP Forking scenario, and there are other sessions alive in this call besides the branch session, it will not send any Diameter message; the PCRF will not receive any Diameter message , without releasing any bearer resources.

A system for controlling quality of service bearer resources during release, the system includes: a called side terminal and a calling side network element; wherein,

The called terminal is configured to send a BYE message to the calling network element, or receive a BYE message sent by the calling network element;

The calling side network element is configured to release the media resources negotiated by the session of this branch when detecting that the call is a SIP Forking scenario after receiving the BYE message, and not process resource bearers negotiated by sessions of other branches.

Wherein, the calling side network element is specifically the P-CSCF, which is further used for using Diameter AAR messages during session negotiation of a call leg, using extended Diameter STR messages during session negotiation of a call leg, and not sending any Diameter messages, respectively. Perform processing to determine the release of media resources.

Wherein, the P-CSCF further detects that the call is a SIP Forking scenario when negotiating a call branch session using the DiameterAAR message, and there are other sessions alive in the call except the branch session, and inserts the Diameter AAR message The SIP-Forking-Indication AVP of the SIP-Forking-Indication AVP is set to SEVERAL_DIALOGUES (1) and sent to the PCRF; wherein, the Diameter AAR message also carries the bearer resource corresponding to the IP Flow of the forked session, and the AVP attribute of the IP Flow is set to remove;

The system also includes a PCRF, configured to receive the Diameter AAR message sent by the P-CSCF, and according to the AVP attribute of the IP Flow, only for the branch session carried in the Diameter AAR message set to be removed Release the bearer resources corresponding to the IPFlow.

Wherein, the P-CSCF further detects that the call is a SIP Forking scenario when using the extended DiameterSTR message during negotiation of a call branch session, and that other sessions survive the call except the branch session, then the extended DiameterSTR message will be extended. The SIP-Forking-Indication AVP in the Diameter STR message is set to SEVERAL_DIALOGUES (1) and sent to the PCRF; wherein, the extended Diameter STR message also carries the bearer resource corresponding to the IP Flow of the branch session, and the IP The AVP attribute of Flow is set to the bearer resource corresponding to the session of this branch;

The system also includes a PCRF, configured to receive the extended Diameter STR message sent by the P-CSCF, and only perform the IP Flow for the session of this branch carried in the Diameter AAR message according to the AVP attribute of the IP Flow The corresponding bearer resources are released.

Wherein, when the P-CSCF further processes not sending any Diameter message, it detects that the call is a SIP Forking scenario, and there are other sessions alive in this call except the forked session, and does not send any Diameter message to the PCRF;

The system also includes a PCRF, which is further configured not to receive any Diameter message, and not to release any bearer resources.

In the media resource access negotiation of the present invention, the network element on the calling side receives the invitation INVITE200OK message sent by the terminal on the called side, detects that the call is a SIP Forking scenario, and only updates the media resources negotiated in the session of the branch, and does not process Resource bearer negotiated by other branch sessions. By adopting the present invention, the resource bearer requirement of the SIP Forking scene can be met in media resource access negotiation.

In the media resource release of the present invention, the network element on the calling side receives the BYE message and detects that the call is a SIPForking scenario, and only releases the media resources negotiated by the session of this branch, and does not process resource bearers negotiated by sessions of other branches. By adopting the present invention, the resource bearer requirement of the SIP Forking scene can be met in the media resource release.

Description of drawings

FIG. 1 is a schematic diagram of a system architecture for realizing QoS control in an existing IMS;

FIG. 2 is a flow chart of a method for carrying resource control in a SIP Forking scenario using the prior art;

FIG. 3 is a flowchart of a method for controlling QoS bearer resources in Embodiment 1 corresponding to Solution 1 of the present invention;

FIG. 4 is a flowchart of a method for controlling QoS bearer resources in Embodiment 1 corresponding to Solution 2 of the present invention;

FIG. 5 is a flowchart of a method for controlling QoS bearer resources in Embodiment 2 corresponding to Solution 2 of the present invention;

FIG. 6 is a flowchart of a method for controlling QoS bearer resources in Embodiment 3 corresponding to Solution 2 of the present invention.

detailed description

The basic idea of the present invention is: during media resource access negotiation, the network element on the calling side receives the invitation INVITE 200 OK message sent by the terminal on the called side, detects that the call is a SIP Forking scenario, and only media resources negotiated for this branch session The update operation is performed, and resource bearers negotiated by other branch sessions are not processed. During the release of media resources, the NE on the calling side receives a BYE message and detects that the call is a SIP Forking scenario, and only releases the media resources negotiated in the session of this branch, and does not handle resource bearers negotiated in sessions of other branches.

Since the current protocol is not clear about the bearer processing of the second INVITE 200 OK in the SIP Forking scenario, it is clear that according to the current protocol: the first INVITE 200 OK will delete the result of the second media negotiation, so that Either the second INVITE 200 OK cannot apply for the corresponding media resource, or the second media resource will overwrite the first applied media resource. In short, the current protocol is not suitable for the QoS bearer resource control in the SIP Forking scenario, whether it is in the media resource access negotiation process or the media resource release process. Therefore, the present invention includes two solutions. The first solution is for media resource access negotiation The QoS bearer resource control of the process, the second scheme is for the QoS bearer resource control of the media resource release process. The following are described separately.

Solution 1: During the media resource access negotiation, the NE on the calling side receives the INVITE200 OK message sent by the terminal on the called side, detects that the call is a SIP Forking scenario, and only updates the media resources negotiated in the session of the branch. Handle resource bearers negotiated by other branch sessions. It can solve the above-mentioned problems caused by using the existing technology 1. For the media resource access negotiation process in the SIP Forking scenario, it supports media resource negotiation when multiple called terminals return INVITE 200 OK, so that the calling party can choose according to their own preferences. The appropriate called terminal makes the call.

A method for controlling quality of service bearer resources in access negotiation, comprising the following content:

(a) When the calling P-CSCF receives the INVITE 200 OK, it detects that the call is a SIP Forking scenario, and when there are other related surviving sessions in addition to the session of this call to the terminal, it sends the Diameter to the PCRF The AAR message sets the SIP-Forking-Indication AVP to SEVERAL_DIALOGUES(1).

(b) The PCRF receives the Diameter AAR message sent by the P-CSCF, updates the PCC rules corresponding to the IP Flow of the terminal carried in the Diameter AAR message, and updates the PCC rules corresponding to the IP Flow of other terminals obtained through negotiation of the Diameter AAR message. The PCC rules do not perform any processing (including deletion and update), so as to ensure that the media resources applied for by each channel can be maintained.

Here, the present invention is different from the prior art. In the INVITE 200 OK, the SIP-Forking-Indication AVP is set to SEVERAL_DIALOGUES (1), so that the PCRF does not perform any processing on the bearer resources and PCC corresponding to the IP Flow of other paths, while the existing The technique is to set SIP-Forking-Indication AVP to SINGLE_DIALOGUE (0) in INVITE 200 OK, so that PCRF removes the PCC rules corresponding to the IP Flow of other road terminals.

A system for controlling quality of service bearer resources in access negotiation, the system comprising: a called side terminal and a calling side network element; wherein, the called side terminal is used to send an INVITE 200 OK message to the calling side network The calling side network element is used to receive the invitation INVITE 200 OK message sent by the called terminal, detect that the call is a SIP Forking scenario, and only update the media resources negotiated by the branch session, and do not process other Resource bearer for branch session negotiation.

Here, the calling side network element is specifically a P-CSCF, and the system also includes a PCRF;

The P-CSCF is used to set the SIP-Forking-Indication AVP in the Diameter AAR message to SEVERAL_DIALOGUES (1) and sent to the PCRF; PCRF, after receiving the Diameter AAR message sent by the P-CSCF, update the PCC rule corresponding to the IPFlow of the branch session carried in the Diameter AAR message , do not perform any processing on the PCC rules corresponding to the IPFlow of other sessions acquired through Diameter AAR message negotiation.

Solution 2: During the release of media resources, the NE on the calling side receives a BYE message and detects that the call is a SIPForking scenario, and only releases the media resources negotiated in the session of this branch, and does not process the resource bearer negotiated in the sessions of other branches. It can solve the above-mentioned problem 2 caused by using the existing technology. For the media resource release process in the SIPForking scenario, when the caller sends a BYE message to release one of the SIP sessions, the media layer of the call that meets the requirements of the signaling layer connection can also be processed normally.

A method for releasing medium quality of service bearer resource control has three solutions.

Solution one includes the following:

(a) When the calling P-CSCF receives the BYE message and detects that the call is a SIP Forking scenario, and there are other related surviving sessions besides the session of the current call terminal, the Diameter message sent to the PCRF It is a Diameter AAR message. Since the SIP-Forking-IndicationAVP field exists in the existing Diameter AAR message, the SIP-Forking-Indication AVP in the Diameter AAR message is directly set to SEVERAL_DIALOGUES(1), which carries the current BYE message The corresponding session negotiated IP Flow, and set the Flow-Status (flow status) AVP in the Media-Component-Description AVP corresponding to the IPFlow to REMOVED.

Here, after receiving the BYE message, the P-CSCF sends an AAR message carrying an IP Flow whose Flow-Status AVP is REMOVED. It is to release all bearer resources of the entire call.

(b) PCRF receives the Diameter AAR message sent by the P-CSCF, and only removes the PCC rules and bearer resources corresponding to the IP Flow carried in the Diameter AAR message according to the set REMOVED requirements, and does not make any changes to the IP Flow other than the Diameter AAR message deal with.

Solution two consists of the following:

(a) Extend the Diameter STR message: add an optional SIP-Forking-Indication AVP field and a Flow (Flows AVP) field, where the Flows AVP indicates the number corresponding to the IP Flow that needs to be deleted.

When the calling P-CSCF receives the BYE message and detects that the call is a SIP Forking scenario, and there are other surviving sessions besides the call to the local terminal, the Diameter message sent to the PCRF is a Diameter STR message. Since there is no SIP-Forking-Indication AVP field and FlowsAVP field in the existing Diameter STR message, the existing Diameter STR message is extended to add the SIP-Forking-IndicationAVP field. When the SIP-Forking-Indication The AVP value is set to SEVERAL_DIALOGUES(1), which is used to identify the SIPForking scenario and only needs to release the session bearer resource corresponding to the Flows AVP in the STR message. Among them, the Flows AVP is the bearer resource corresponding to the session of this branch.

What needs to be pointed out here is: if the calling P-CSCF detects that the call is a SIPForking scenario when receiving the BYE message, and there are no other surviving sessions except the session of this call to the terminal, that is, there is only one SIP session , it is consistent with the existing protocol. PCSCF sends a Diameter STR message to PCRF. If the Diameter STR message is an extended message, that is, the SIP-Forking-Indication AVP field is added, the SIP-Forking-Indication carried in the Diameter STR message The AVP value is set to SINGLE_DIALOGUE(0); if the Diameter STR message is not an extended message, it does not carry the SIP-Forking-Indication AVP.

Here, in the above (a), the Diameter STR message sent by the P-CSCF may extend the AVP to identify SIP Forking; or the AF network element may extend other Diameter messages to indicate SIP Forking.

(b) PCRF receives the Diameter STR message sent by the P-CSCF, and if it finds that the SIP-Forking-Indication AVP value is SEVERAL_DIALOGUES (1), it only releases the bearer information corresponding to the FlowsAVP; if there is no SIP-Forking-Indication AVP or the value is SINGLE_DIALOGUE (0), release all associated bearer resources under the Diameter session.

Solution three includes the following:

(a) When receiving the BYE message, the calling P-CSCF detects that the call is a SIP Forking scenario, and does not send any Diameter message if there are other related surviving sessions except the session of this call to the local terminal.

(b) The PCRF will not receive any Diameter message, and thus will not release any bearer resources.

Furthermore, the above solution of the present invention is not limited to the QoS bearer resource control of the Rx interface, and the principle of the present invention is also applicable to the QoS bearer resource control of the Gq' interface. The above solution of the present invention is not limited to the P-CSCF, but also applies the principle of the present invention to the AGCF network element in the IMS system, and the AF network element using the Rx interface and the Gq' interface.

To sum up, compared with the prior art, since the present invention controls the QoS bearer resources of the IMS system, in the case of SIP Forking for the called party, for scheme 1, the calling P-CSCF changes the calling INVITE 200 OK, the field value of the Diameter AAR message; for Solution 1 of Scheme 2, use the Diameter AAR message when one of the BYE calls the branch; for Solution 2 of Scheme 2, extend the DiameterSTR message when one of the BYE calls the branch; For Solution 3 of Solution 2, when one of the call branches is BYE, the calling P-CSCF does not send any Diameter message, so that the user equipment accessing the IMS network can select the called terminal by itself according to the caller's preference The QoS bearer resource control also satisfies the intercommunication of normal calls in the case of called SIP Forking, which improves the QoS capability of the system and improves the user experience.

A system for controlling quality of service bearer resources during release, the system comprising: a called side terminal and a calling side network element; wherein, the called side terminal is used to send a BYE message to the calling side network element, or receive The BYE message sent by the calling side; after receiving the BYE message, the network element on the calling side is used to release only the media resources negotiated by the session of this branch when it detects that the call is a SIP Forking scenario, and does not process the session negotiation of other branches resource bearer.

Here, the calling side network element is specifically the P-CSCF, which is further used for using Diameter AAR messages during session negotiation of a call leg, using extended Diameter STR messages during session negotiation of a call leg, and not sending any Diameter messages Perform processing to determine the release of media resources.

Here, the P-CSCF further detects that the call is a SIP Forking scenario when negotiating a call branch session using the DiameterAAR message, and there are other sessions alive in the call except the branch session, and inserts the Diameter AAR message into the Diameter AAR message. The SIP-Forking-Indication AVP of the SIP-Forking-Indication AVP is set to SEVERAL_DIALOGUES (1) and sent to the PCRF; wherein, the Diameter AAR message also carries the bearer resource corresponding to the IP Flow of the forked session, and the AVP attribute of the IP Flow is set to remove;

The system further includes PCRF, configured to receive the Diameter AAR message sent by the P-CSCF, and according to the AVP attribute of the IP Flow, only carry out the session of the branch that is set to be removed in the Diameter AAR message Release the bearer resources corresponding to the IPFlow.

Here, the P-CSCF further detects that the call is a SIP Forking scenario when the extended DiameterSTR message is used for negotiation of a call branch session, and there are other sessions alive in this call besides the branch session, then the extended DiameterSTR message will be extended. The SIP-Forking-Indication AVP in the Diameter STR message is set to SEVERAL_DIALOGUES (1) and sent to the PCRF; wherein, the extended Diameter STR message also carries the bearer resource corresponding to the IP Flow of the branch session, and the Flows The AVP is set as the bearer resource corresponding to the session of this branch;

The system further includes a PCRF, configured to receive the extended Diameter STR message sent by the P-CSCF, and only release the bearer resource of the current branch session corresponding to the Flows AVP in the Diameter STR message.

Here, when the P-CSCF further processes not sending any Diameter message, it detects that the call is a SIP Forking scenario, and there are other sessions alive in this call except the fork session, and does not send any Diameter message to the PCRF;

The system also includes a PCRF, which is further configured not to receive any Diameter message, and not to release any bearer resource.

The implementation of the technical solution will be further described in detail below in conjunction with the accompanying drawings.

Embodiment 1 corresponding to Scheme 1:

Figure 3 is the bearer control flow of Embodiment 1 corresponding to the above solution 1, mainly the processing process of the calling P-CSCF receiving the INVITE 200 OK, which omits the flow processing before the INVITE 200 OK, and the flow processing before the INVITE 200 OK The process before the INVITE 200 OK in the prior art shown in FIG. 2 is the same, and will not be repeated here. The process of Embodiment 1 includes the following steps:

Step 301, UE initiates a call;

Step 302, after receiving the call request carrying the SDP offer, the P-CSCF of the visited network maps the SDP information to downlink media information;

Step 303, the calling P-CSCF forwards the SDP offer request message to the S-CSCF and sends it to the called side;

Step 304, the calling S-CSCF forwards the INVITE 200OK message of the SDP answer sent by the called side;

Step 305, the calling P-CSCF judges that the called party has SIP Forking based on receiving multiple temporary responses (such as INVITE 180 or 183, etc.) based on the previous call, and constructs a Diameter AAR message in combination with the downlink connection information obtained in 302, wherein The SIP-Forking-Indication AVP setting is different from SINGLE_DIALOGUE(0) for ordinary calls, and is set to SEVERAL_DIALOGUES(1);

Step 306, the calling P-CSCF sends the session information to the PCRF network element through the Diameter AAR message;

Step 307, the PCRF receives the bearer request, that is, the Diameter AAA message, and finds that the value of the SIP-Forking-IndicationAVP is SEVERAL_DIALOGUES (1), then generates an additional PCaC rule and sends it to the gateway;

Step 308, send the Diameter AAA response message to the P-CSCF according to the bearer resource control result returned by the PCRF;

Step 309, the P-CSCF forwards the call response message to the UE on the calling side.

The above process only describes the processing of receiving the first INVITE 200 OK on the calling side P-CSCF, and the processing of receiving multiple INVITE 200 OKs subsequently is the same.

Embodiment 1 corresponding to Scheme 2:

Figure 4 is the bearer control flow of Embodiment 1 corresponding to Solution 2. It is mainly the processing process of the calling P-CSCF receiving the BYE message. The call establishment process in the SIP Forking scenario is omitted. This example selects the All the way calls are answered and send BYE message described to other establishment or unestablished SIP session, the flow process of embodiment one comprises the following steps:

Step 401, the calling P-CSCF receives the BYE message of releasing the call from the terminal;

Step 402, P-CSCF detects that there is only one SIP session in this call, and then uses the Diameter STR message specified in the protocol to release the associated Diameter session; if there are multiple SIP sessions in this call, the current BYE only releases one of the sessions , the P-CSCF finds the media information negotiated in this session, sets the Flow-Status AVP corresponding to the IP Flow to REMOVED (4), and sets the value of the SIP-Forking-Indication AVP to SEVERAL_DIALOGUES (1), and constructs a DiameterAAA message ;

Step 403, the P-CSCF sends a DiameterAAA message;

Step 404, the PCRF receives the bearer request, that is, the Diameter AAA message, finds that the value of the SIP-Forking-IndicationAVP is SEVERAL_DIALOGUES (1), and sets the Flow-StatusAVP to REMOVED for all relevant IPFlow deletions;

Step 405, PCRF returns Diameter AAA message;

In step 406, the P-CSCF releases the SIP session resource associated with the branch, and forwards the BYE message.

Embodiment 2 corresponding to Scheme 2:

Figure 5 is the bearer control process of Embodiment 2 corresponding to Scheme 2. It is mainly the processing process of the calling P-CSCF receiving BYE. The call establishment process in the SIP Forking scenario is omitted. In this example, the calling UE selects a route The call is answered and the BYE message sent by other established or unestablished SIP sessions is described. The flow process of embodiment two includes the following steps:

Step 501, the calling P-CSCF receives the BYE message of releasing the call from the terminal;

Step 502, P-CSCF detects that there is only one SIP session in this call, and then uses the Diameter STR message specified in the protocol to release the Diameter session associated with it; if there are multiple SIP sessions in this call, the current BYE only releases one of the sessions , the P-CSCF finds the media information negotiated in this session, constructs a Diameter STR message, fills in the Flows AVP corresponding to this session, and carries the SIP-Forking-Indication AVP as SEVERAL_DIALOGUES(1), which is used to identify the release of a channel in the SIP Forking scenario. SIP session;

Step 503, the P-CSCF sends a Diameter STR message;

Step 504, the PCRF receives the bearer request, that is, the Diameter STR message, finds that the value of the SIP-Forking-IndicationAVP is SEVERAL_DIALOGUES (1), and only releases the bearer resources identified by the Flow AVP;

Step 505, PCRF returns Diameter STA message;

In step 506, the P-CSCF releases the SIP session resource associated with this session, and forwards the BYE message.

Embodiment 3 corresponding to Scheme 2:

Figure 6 is the bearer control flow of Embodiment 3 corresponding to Solution 2, mainly the processing process of the calling P-CSCF receiving BYE, which omits the call establishment process in the SIP Forking scenario. In this example, the calling UE selects a route The call is answered and the BYE message sent by other established or unestablished calls is described. The flow process of the third embodiment includes the following steps:

Step 601, the calling P-CSCF receives the BYE message of releasing the call from the terminal;

Step 602, P-CSCF detects that there is only one SIP session in this call, and then releases the Diameter session associated with it using the Diameter STR message specified in the protocol; if there are multiple SIP sessions in this call, the current BYE only releases one of the sessions , do not send any Diameter message to PCRF;

In step 603, the P-CSCF releases the SIP session resource associated with the current SIP session, and forwards the BYE message.

Here, comparing the prior art with the present invention, it can be known that the prior art is based on the existing 3GPP29.214 protocol, when the calling P-CSCF receives the first INVITE 200 OK, it changes the identification indicating SIP Forking from SEVERAL_DIALOGUES It is SINGLE_DIALOGUE, so that PCRF only retains the bearer resources negotiated in the first INVITE 200 OK and deletes the underlying bearer resources of other branches, depriving the user of the right to independently choose the listener. At the same time, when the calling P-CSCF receives the BYE message, whether the BYE at this time is the release of the bearer resources of the entire SIP session, or the release of the bearer resources corresponding to only one SIP session, the different processing methods of these two scenarios, the protocol No distinction is made above, and the existing Diameter STR message is used uniformly for release. In the case of forking, even though the signaling plane of the calling party and the called party have been connected, the media plane is still disconnected, and the call cannot be connected.

However, in the present invention, the P-CSCF improves the processing flow when receiving INVITE 200 OK and BYE. When receiving INVITE 200 OK, it only updates the bearer negotiated by this path, and does not process the bottom bearer negotiated by other branches. At the same time, When a BYE is received, only the bearer resources negotiated by this channel are released, and other branches are not processed, which satisfies the user's right to choose independently to the greatest extent.

To sum up, the present invention is applied to the scenario of SIP Forking of the called party in the IMS. When multiple called parties are answered at the same time, by optimizing the network processing flow and expanding the fields in the message, it is suitable for the SIP Forking of the IMS. The purpose of QoS bearer resource control in the scenario.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (15)

1. A method for controlling quality of service bearer resources in access negotiation, characterized in that the method comprises: during media resource access negotiation, the network element on the calling side receives the invitation INVITE 200OK message sent by the terminal on the called side, and detects When this call is a SIP offload Forking scenario, only the media resources negotiated in the session of this branch are updated, and the resources carried by sessions negotiated in other branches are not processed. 2. The method according to claim 1, wherein the calling side network element is specifically a proxy call session control function P-CSCF, and the method specifically comprises: The P-CSCF receives the INVITE 200OK, if it detects that the call is a SIP Forking scenario, and other sessions survive in addition to the branch session in the call, the SIP-Forking-Indication AVP in the Diameter AAR message is set to SEVERAL_DIALOGUES( 1) and sent to the policy charging rule function PCRF; The PCRF receives the Diameter AAR message sent by the P-CSCF, updates the policies and charging control PCC rules corresponding to the IP Flow of the branch session carried in the Diameter AAR message, and performs negotiation on the The PCC rules corresponding to the IP Flow of other branch sessions do not perform any processing. 3. A system for controlling quality of service bearer resources in access negotiation, characterized in that the system includes: a called side terminal and a calling side network element; wherein, The called terminal is configured to send an INVITE 200OK message to the calling network element; The calling side network element is used to receive the invitation INVITE 200OK message sent by the called side terminal, detect that the call is a SIP Forking scenario, and only update the media resources negotiated in the session of this branch, and do not process other branches Resource bearer for session negotiation. 4. The system according to claim 3, wherein the calling side network element is specifically a P-CSCF, and the system also includes a PCRF; The P-CSCF is used to set the SIP-Forking-IndicationAVP in the Diameter AAR message to SEVERAL_DIALOGUES (1) and sent to the PCRF; The PCRF is configured to, after receiving the Diameter AAR message sent by the P-CSCF, update the PCC rule corresponding to the IP Flow of the branch session carried in the Diameter AAR message, and obtain the The PCC rules corresponding to the IP Flow of other sessions do not perform any processing. 5. A method for controlling quality of service bearer resources during release, characterized in that the method comprises: during release of media resources, the network element on the calling side receives a BYE message, detects that the call is a SIP Forking scenario, and only for this branch The media resources negotiated by the session are released, and the resource bearers negotiated by other branches are not processed; The method also includes: The calling side network element is specifically the P-CSCF, and does not send any Diameter message. 6. The method according to claim 5, wherein the calling side network element is specifically a P-CSCF, and the method further comprises: using a Diameter AAR message when negotiating a call branch session, and converting the SIP-Forking- IndicationAVP is set to SEVERAL_DIALOGUES (1), and the AVP attribute of IP Flow is set to remove. 7. The method according to claim 6, characterized in that the method specifically comprises: The P-CSCF receives the BYE message, if it detects that the call is a SIP Forking scenario, and other sessions survive in addition to the branch session in the call, the SIP-Forking-Indication AVP in the Diameter AAR message is set to SEVERAL_DIALOGUES( 1) and send it to PCRF; wherein, the Diameter AAR message also carries the bearer resource corresponding to the IP Flow of the branch session, and sets the AVP attribute of the IP Flow to remove; The PCRF receives the Diameter AAR message sent by the P-CSCF, and according to the AVP attribute of the IPFlow, only the bearer resource corresponding to the IP Flow of the branch session carried in the Diameter AAR message that is set to be removed to release. 8. The method according to claim 5, wherein the calling side network element is specifically a P-CSCF, and the method further comprises: using an extended Diameter STR message when negotiating a call branch session, and using the extended Diameter STR message in the extended Diameter Add SIP-Forking-Indication AVP to the STR message and set it to SEVERAL_DIALOGUES(1); add the AVP attribute of IP Flow to the extended Diameter STR message. 9. The method according to claim 8, characterized in that the method specifically comprises: The P-CSCF receives the BYE message, if it detects that the call is a SIP Forking scenario, and there are other sessions alive in this call besides this branch session, then set the SIP-Forking-IndicationAVP in the extended Diameter STR message to SEVERAL_DIALOGUES (1) and sent to PCRF; wherein, the extended Diameter STR message also carries the bearer resource corresponding to the IP Flow of the branch session, and the AVP attribute of the IP Flow is set as the bearer resource corresponding to the branch session; The PCRF receives the extended Diameter STR message sent by the P-CSCF, and according to the AVP attribute of the IP Flow, performs only the bearer resources corresponding to the IP Flow of the branch session carried in the Diameter AAR message freed. 10. The method according to claim 5, characterized in that the method specifically comprises: The P-CSCF receives the BYE message, if it detects that the call is a SIP Forking scenario, and there are other sessions alive in the call except the forked session, it will not send any Diameter message; the PCRF will not receive any Diameter message, and will not Release any bearer resources. 11. A system for controlling quality of service bearer resources during release, characterized in that the system includes: a called side terminal and a calling side network element; wherein, The called terminal is configured to send a BYE message to the calling network element, or receive a BYE message sent by the calling network element; The calling side network element is used to release the media resources negotiated in the session of this branch when it detects that the call is a SIP Forking scenario after receiving the BYE message, and does not process the resources carried in the session negotiation of other branches; The calling side network element is specifically a P-CSCF, and is specifically configured not to send a Diameter message. 12. The system according to claim 11, wherein the calling side network element is specifically a P-CSCF, and is further used to use Diameter AAR messages for a call branch session negotiation, and a call branch session negotiation for a call branch session. The extended Diameter STR message is used, and no Diameter message is sent for processing to determine the release of the media resource. 13. The system according to claim 12, wherein the P-CSCF further detects that the call is a SIP Forking scenario when the Diameter AAR message is used for the negotiation of a call branch session, and the call In addition to this fork session, other sessions are still alive, set the SIP-Forking-IndicationAVP in the DiameterAAR message to SEVERAL_DIALOGUES (1) and send it to PCRF; wherein, the Diameter AAR message also carries the bearer resources corresponding to the IP Flow of this fork session , and set the AVP attribute of the IP Flow to remove; The system further includes a PCRF, configured to receive the Diameter AAR message sent by the P-CSCF, and according to the AVP attribute of the IPFlow, only perform The bearer resources corresponding to the IP Flow are released. 14. The system according to claim 12, wherein the P-CSCF further detects that the call is a SIP Forking scenario when the extended Diameter STR message is used for processing a call branch session negotiation, and this If there are other sessions alive in addition to this branch session during the call, set the SIP-Forking-Indication AVP in the extended Diameter STR message to SEVERAL_DIALOGUES (1) and send it to PCRF; wherein, the extended Diameter STR message also carries this The bearer resource corresponding to the IP Flow of the branch session, and the AVP attribute of the IP Flow is set as the bearer resource corresponding to the branch session; The system also includes a PCRF, configured to receive the extended Diameter STR message sent by the P-CSCF, and only perform the IP Flow for the session of this branch carried in the Diameter AAR message according to the AVP attribute of the IP Flow The corresponding bearer resources are released. 15. The system according to claim 12, characterized in that the P-CSCF further detects that the call is a SIP Forking scenario when not sending any Diameter message, and the call except the branch session Other sessions are still alive, and no Diameter message is sent to PCRF; The system also includes a PCRF, which is further configured not to receive any Diameter message, and not to release any bearer resources.