WO2014044224A1 - 接入协商、释放中服务质量承载资源控制的方法及系统 - Google Patents

接入协商、释放中服务质量承载资源控制的方法及系统 Download PDF

Info

Publication number
WO2014044224A1
WO2014044224A1 PCT/CN2013/084023 CN2013084023W WO2014044224A1 WO 2014044224 A1 WO2014044224 A1 WO 2014044224A1 CN 2013084023 W CN2013084023 W CN 2013084023W WO 2014044224 A1 WO2014044224 A1 WO 2014044224A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
call
session
diameter
sip
Prior art date
Application number
PCT/CN2013/084023
Other languages
English (en)
French (fr)
Inventor
缪永生
张丽
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to EP13839680.9A priority Critical patent/EP2899937B1/en
Priority to US14/430,237 priority patent/US9525741B2/en
Publication of WO2014044224A1 publication Critical patent/WO2014044224A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/50—Network service management, e.g. ensuring proper service fulfilment according to agreements
    • H04L41/5003—Managing SLA; Interaction between SLA and QoS
    • H04L41/5019—Ensuring fulfilment of SLA
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1069—Session establishment or de-establishment
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1083—In-session procedures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1096—Supplementary features, e.g. call forwarding or call holding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066—Session management
    • H04L65/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management

Definitions

  • the present invention relates to a resource control technology in the field of communications, and more particularly to a scenario in which a called multimedia user (IMS, IP Multimedia Subsystem) invokes a Session Initiation Protocol (SIP), a calling agent.
  • IMS multimedia user
  • SIP Session Initiation Protocol
  • P-CSCF Proxy Call Session Control Function
  • NGN Next Generation Network
  • Figure 1 is a reference framework 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 Call Session Control Function) 104.
  • PCRF Policy and Charging Rule Function
  • S-CSCF Serving Call Session Control Function
  • IBCF Interconnection Border Control Function
  • I-CSCF Interrogating Call Session Control Function
  • MGCF Media Gateway Control
  • PCC Policy and Charging Control
  • the application function AF, Application Function
  • SDP Session Description Protocol
  • the related flow information AVP in the Diagnostic Authentication Request (Diameter AAR) message, and the corresponding information is the media stream information controlled by the PCRF.
  • the AF corresponds to the P-CSCF in the IMS.
  • the AVP refers to a property value pair specified by the Diameter protocol.
  • SIP Forking is a basic function in the IMS system.
  • the so-called SIP Forking means: a plurality of terminals share a subscriber number, and the terminal can use different bearers or have different capabilities.
  • the IMS network searches for the called subscriber terminal to have two terminals in parallel and serial. In this manner, the calling user selects a called user terminal to make a call according to a certain policy. Regardless of serial or parallel, the calling side P-CSCF needs to provide the PCRF with the media resources that the calling party negotiates with the selected called terminal.
  • the calling side process of the QoS bearer resource control function is shown in Figure 2. Taking two paths 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 receiving the call, the P-CSCF maps the SDP information to the downlink media information.
  • Step 203 The P-CSCF forwards the invitation (INVITE) request to the S-CSCF to the called party.
  • Step 204-Step 211 the calling party The P-CSCF receives the processing flow of the two-way terminal INVITE 180 message.
  • the SIP-Forking-Indication AVP is SINGLE-DIALOGUE (0) ), carrying the media information negotiated by UE1;
  • the P-CSCF can determine that the called party is forking, and the SIP-Forking-Indication AVP in the Diameter AAR request message is SEVERAL-DIALOGUES (1) ), carrying the media information negotiated by UE2;
  • Step 212 The S-CSCF forwards the INVITE 200 OK response message returned by the first path terminal to the P-CSCF, and includes SDP answer information.
  • Step 213 When receiving the INVITE 200 OK, the P-CSCF maps the SDP information to the uplink media information.
  • Step 214 The P-CSCF sends a Diameter AAR request message corresponding to the mediation of the called UE1 to the PCRF network element requesting resource authorization, where the media component number (Media-Component-Number AVP) is filled in the Diameter AAR request message.
  • media component number Media-Component-Number AVP
  • Step 215 When the PCRF receives the SIP-Forking-Indication AVP as SINGLE-DIALOGUE (0), or the AVP without the SIP-Forking-Indication AVP, according to the current Diameter
  • the PCC rule corresponding to the IP Flow carried in the current Diameter AAR request message is removed, that is, the PCC rule corresponding to the IP Flow negotiated by the calling party and the called UE2 is removed.
  • Step 217 If the calling user selects the first way to answer, the calling user needs to send a BYE request message to remove the SIP session that the calling party and the UE2 have established.
  • Step 218 The P-CSCF releases the session resource established by the calling party and the UE2.
  • Diameter STR Diameter Session End Request
  • Step 220 The P-CSCF forwards the BYE request.
  • the SIP-Forking-Indication AVP in the Diameter AAR request message is set to SINGLE-DIALOGUE (0).
  • the PCRF confirms the bearer resource of the final application by using the corresponding IP Flow in the Diameter AAA request message corresponding to the INVITE 200 OK, and then deletes the PCC rule corresponding to the IP Flow negotiated by the calling party and the called UE2, and P- Upon receiving the BYE message of the UE2 session, the CSCF sends a Diameter STR message, and the Diameter STR message releases all the bearer resources requested by the call.
  • the INVITE 200OK of multiple called terminals will be transparently transmitted to the calling user, whether in serial or parallel mode.
  • the user is requested to select the appropriate called terminal to answer according to the support request of the device and the preference of the device.
  • the selection right is at the calling user, and the selected receiving terminal is not necessarily the first terminal to return to the INVITE 200 OK.
  • the answering terminal selected by the calling user must be the first terminal to return to the INVITE 200 OK; in addition, in the SIP Forking scenario, during the release of the media resource, as long as the called terminal returns all the way Temporary response (such as INVITE 183 message), and the calling user finally answers the object other than the terminal, and needs to send a BYE message to release the SIP session established with the terminal.
  • the calling PCSCF will notify the PCRF to release all. Host resources.
  • the problems existing in the prior art are as follows: 1) For the media resource access negotiation process in the SIP Forking scenario, the media resource negotiation in the case where the multiple called terminal returns INVITE 200 OK is not supported; 2) For the SIP Forking scenario During the release of the media resource, the calling party sends a BYE message, and the SIP session is released. The bearer resources that have been applied for the entire call are released. The normal bearer resources of any one-way call are proved, so that the basic call normal interworking cannot be achieved.
  • the media resource access negotiation process in the SIP Forking scenario and the QoS bearer resource control in the media resource release process cannot meet the normal call processing in the SIP Forking scenario. Summary of the invention
  • the main purpose of the embodiments of the present invention is to provide a method and system for controlling quality of service bearer resources in an access negotiation, satisfying the requirement of a media resource access negotiation process in a SIP Forking scenario, and supporting multiple called terminals. Returns the media resource negotiation in the case of INVITE 200 OK.
  • Another object of the present invention is to provide a method and system for releasing quality of service quality bearer resources, which meets the requirements of the media resource release process in the SIP Forking scenario and avoids releasing all bearer resources.
  • a method for controlling quality of service bearer resources in an access negotiation includes: in a media resource access negotiation, the calling side network element receives an invitation INVITE 200 OK message sent by the called side terminal, and detects that the call is a session.
  • the initial protocol SIP is used to perform the update operation on the media resources negotiated by the branch session, and does not process the resource bearers negotiated by other branch sessions.
  • 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 the call is detected as a SIP Forking scenario, and the other sessions in the call are in addition to the branch session, the SIP-Forking-Indication AVP in the Diameter AAR message is set to SEVERAL. – DIALOGUES(l) and sent to the policy charging rule function PCRF;
  • the row update process does not perform any processing on the PCC rules corresponding to the IP Flow of other branch sessions obtained through the Diameter AAR message negotiation.
  • a system for controlling quality of service bearer resources in access negotiation comprising: a called side terminal, a calling side network element;
  • the called side terminal is configured to send an INVITE 200 OK message to the calling side network element
  • the calling side network element is configured to receive an invitation INVITE 200 OK message sent by the called side terminal, and detecting
  • the call is a SIP Forking scenario, and only the media resources negotiated by the branch session are updated, and the resource bearers negotiated by other branch sessions are not processed.
  • the calling side network element is specifically a P-CSCF, and the system further includes a PCRF;
  • the P-CSCF is configured to receive the SIP-Forking-Indication AVP in the Diameter AAR message when the INVITE 200 OK is received, and when the call is detected as a SIP Forking scenario, and the other session is survived in the current session.
  • SEVERAL DIALOGUES ( 1 ) and send 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 data through the Diameter AAR message negotiation.
  • the PCC rules corresponding to the IP Flow of other sessions are not processed.
  • a method for releasing quality of service quality bearer resources includes: in a media resource release, the calling side network element receives a goodbye BYE message, detecting that the call is a SIP Forking scenario, and performing only the media resources negotiated by the branch session Released, does not handle resource bearers negotiated by other branch sessions.
  • the calling side network element is specifically a P-CSCF, and the method further includes: using a Diameter AAR message in a call branch session negotiation, and setting a SIP-Forking-Indication AVP as SEVERAL_DIALOGUES(l), IP Flow
  • the AVP property is set to remove.
  • the method specifically includes: The P-CSCF receives the BYE message. If the call is detected as a SIP Forking scenario, and the other sessions in the call are in addition to the branch session, the SIP-Forking-Indication AVP in the Diameter AAR message is set to SEVERAL. DIALOGUES(1) is sent to the PCRF; wherein the Diameter AAR message further carries the bearer resource corresponding to the IP flow of the branch session, and the AVP attribute of the IP Flow is set to be removed;
  • the calling side network element is specifically a P-CSCF, and the method further includes: adding an extended Diameter STR message in a call branch session negotiation, adding a SIP-Forking-Indication AVP to the extended Diameter STR message and Set to SEVERAL—DIALOGUES(l); Add the AVP attribute of IP Flow to the extended Diameter STR message.
  • the method specifically includes:
  • the P-CSCF receives the BYE message. If the call is detected as a SIP Forking scenario, and the other sessions in the call except the branch session survive, the SIP-Forking-Indication AVP in the extended Diameter STR message is set to SE VERAL 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 AVP attribute of the IP Flow is set as the bearer corresponding to the branch session.
  • the PCRF receives the extended Diameter STR message sent by the P-CSCF, and performs, according to the AVP attribute of the IP Flow, only the bearer resource corresponding to the IP flow of the branch session carried in the Diameter AAR message. freed.
  • the calling side network element is specifically a P-CSCF, and the method further includes: not sending any Diameter message.
  • the method specifically includes: The P-CSCF receives the BYE message, and if the call is detected as a SIP Forking scenario, and the other sessions in the call are inactive except the local session, no Diameter message is sent; the PCRF does not receive any Diameter message. , does not release any hosting resources.
  • a system for releasing quality of service quality bearer resources comprising: a called side terminal, a calling side network element;
  • the called side terminal is configured to send a BYE message to the calling side network element, or receive a BYE message sent by the calling side network element;
  • the calling side network element is configured to release the media resource negotiated by the branch session only when the call is a SIP Forking scenario, and the resource bearer negotiated by other branch sessions is not processed.
  • the calling side network element is specifically a P-CSCF, and is further configured to use a Diameter AAR message when negotiating for one call branch session, an extended Diameter STR message when negotiating a call branch session, and not sending any Diameter message. Processing determines the release of media resources.
  • the P-CSCF when using the Diameter AAR message processing for the negotiation of a call branch session, detects that the call is a SIP Forking scenario, and the other sessions in the call except the branch session survive the Diameter AAR message.
  • the SIP-Forking-Indication AVP is set to SEVERAL-DIALOGUES(1) and sent to the PCRF.
  • the Diameter AAR message also carries the bearer resource corresponding to the IP Flow of the branch session, and the AVP of the IP Flow is used. Property is set 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 IP Flow, only the branch session carried in the Diameter AAR message set to be removed The bearer resource corresponding to the IP Flow is released.
  • 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 the branch session carried in the Diameter AAR message set to be removed The bearer resource corresponding to the IP Flow is released.
  • the P-CSCF when the extended Diameter STR message is used for the negotiation of a call branch session, detects that the call is a SIP Forking scenario, and the call is in the middle of the call.
  • the SIP-Forking-Indication AVP in the extended Diameter STR message is set to SEVERAL_DIALOGUES(1) and sent to the PCRF.
  • the extended Diameter STR message also carries the present version.
  • 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 further includes a PCRF configured to receive the extended Diameter STR message sent by the P-CSCF, and according to the AVP attribute of the IP Flow, only the IP Flow of the branch session carried in the Diameter AAR message The corresponding bearer resources are released.
  • a PCRF configured to receive the extended Diameter STR message sent by the P-CSCF, and according to the AVP attribute of the IP Flow, only the IP Flow of the branch session carried in the Diameter AAR message The corresponding bearer resources are released.
  • the P-CSCF further detects that the call is a SIP Forking scenario, and does not send any Diameter message to the call in the call except that the local session is still in the SIP Forking scenario.
  • PCRF PCRF
  • the system also includes a PCRF, which is further configured to not receive any Diameter messages and does not release any bearer resources.
  • the calling party network element receives the invitation INVITE 200 OK message sent by the called party terminal, detects that the call is a SIP Forking scenario, and updates only the media resources negotiated by the branch session. Operation, does not handle resource bearers negotiated by other branch sessions.
  • the resource bearer requirement of the SIP Forking scenario can be met in the media resource access negotiation.
  • the calling side network element receives the goodbye BYE message, detects that the call is a SIP Forking scenario, and only releases the media resources negotiated by the branch session, and does not process the resource bearer negotiated by other branch sessions. .
  • the resource bearer requirement of the SIP Forking scenario can be met in the media resource release.
  • FIG. 1 is a schematic diagram of a system architecture for implementing QoS control in an existing IMS
  • 2 is a flowchart of a method for carrying resource control in a SIP Forking scenario by using a prior art
  • 3 is a flowchart of a method for controlling QoS bearer resources according to Embodiment 1 of the first embodiment of the present invention
  • FIG. 4 is a flow chart of a method for controlling QoS bearer resources according to Embodiment 1 of Embodiment 2 of the present invention
  • FIG. 5 is a flow chart of a method for controlling QoS bearer resources according to Embodiment 2 of Embodiment 2 of the present invention.
  • FIG. 6 is a flowchart of a method for controlling QoS bearer resources according to Embodiment 3 of Embodiment 2 of the present invention. detailed description
  • the calling side network element receives the invitation INVITE 200 OK message sent by the called side terminal, and detects that the current call is a SIP Forking scenario, and only the media resources negotiated by the branch session are negotiated. The update operation is performed, and the resource bearers negotiated by other branch sessions are not processed.
  • the calling side network element receives the BYE message, and detects that the call is a SIP Forking scenario, and only releases the media resources negotiated by the branch session, and does not process the resource bearers negotiated by other branch sessions.
  • the bearer processing of the second INVITE 200 OK is not clear, but it can be clarified that according to the current protocol: the first INVITE 200 OK will delete the result of the second media negotiation, thereby The second INVITE 200 OK may not apply for the corresponding media resource, or the second media resource may cover the media resource that has been applied for by the first channel.
  • the current protocol does not adapt to the QoS bearer resource control of the SIP Forking scenario, whether in the media resource access negotiation process or the media resource release process. Therefore, the embodiment of the present invention includes a two-part solution, and the solution one is for media resource connection.
  • the QoS bearer resource control in the negotiation process, and the second scheme is the QoS bearer resource control in the media resource release process. The following are explained separately.
  • Solution 1 In the media resource access negotiation, the calling side network element receives the invitation sent by the called side terminal.
  • the INVITE 200 OK message is sent to detect that the call is a SIP Forking scenario, and only the media resources negotiated by the branch session are updated, and the resource bearers negotiated by other branch sessions are not processed.
  • the above problem can be solved by using the prior art.
  • the multi-way called terminal is allowed to return the media resource negotiation in the case of the INVITE 200 OK, so that the calling party can select according to his own preference.
  • a suitable called terminal makes a call.
  • a method for controlling quality of service bearer resources in access negotiation includes the following contents:
  • the calling P-CSCF When the calling P-CSCF receives the INVITE 200 OK, it detects that the call is a SIP Forking scenario. In addition to the session of the local terminal, there are other related live sessions, and the Diameter sent to the PCRF.
  • the AAR message sets the SIP-Forking-Indication AVP to SEVERAL_DIALOGUES(l).
  • the PCRF receives the Diameter AAR message sent by the P-CSCF, and updates the PCC rule corresponding to the IP flow of the local terminal carried in the Diameter AAR message, and passes any processing (including deletion, update).
  • the media resources for each application are maintained.
  • the embodiment of the present invention is different from the prior art, and the SIP-Forking-Indication AVP in the INVITE 200 OK is set to SEVERAL DIALOGUES(l), so that the PCRF does not perform any processing on the bearer resources and the PCC corresponding to the IP flows of other paths.
  • the prior art is that the SIP-Forking-Indication AVP in the INVITE 200 OK is set to SINGLE_DIALOGUE(0), so that the PCRF removes the PCC rules corresponding to the IP Flow of other road terminals.
  • a system for controlling quality of service bearer resources in an access negotiation comprising: a called side terminal and a calling side network element; wherein, the called side terminal is configured to send an INVITE 200 OK message to the calling side network
  • the calling side network element is configured to receive the invitation INVITE 200 OK message sent by the called side terminal, and detects that the call is a SIP Forking scenario, only for the branch session.
  • the negotiated media resources are updated, and the resource bearers negotiated by other branch sessions are not processed.
  • the calling side network element is specifically a P-CSCF, and the system further includes a PCRF;
  • the P-CSCF After receiving the INVITE 200 OK, the P-CSCF is configured to set the SIP-Forking-Indication AVP in the Diameter AAR message to be the SIP Forking scenario when the call is detected.
  • SEVERAL_DIALOGUES(1) is sent to the PCRF; the PCRF is configured to receive the PCC rule corresponding to the IP Flow of the branch session carried in the Diameter AAR message after receiving the Diameter AAR message sent by the P-CSCF.
  • the update process is performed, and no processing is performed on the PCC rule corresponding to the IP Flow of other sessions obtained through the Diameter AAR message negotiation.
  • Solution 2 In the media resource release, the calling side network element receives the BYE message, and detects that the call is a SIP Forking scenario, and only releases the media resources negotiated by the branch session, and does not process the resource bearer negotiated by other branch sessions. The problem caused by the prior art can be solved. 2 For the media resource release process in the SIP Forking scenario, when the calling party sends a BYE message to release one of the SIP sessions, the call media layer that meets the signaling level can also be processed normally.
  • the calling P-CSCF When the calling P-CSCF receives the BYE message, it detects that the call is a SIP Forking scenario. In addition to the session of the local terminal, there are other related live sessions, the Diameter message sent to the PCRF.
  • the SIP-Forking-Indication AVP field in the Diameter AAR message is directly set to SEVERAL-DIALOGUES(l), where The IP flow of the session negotiation corresponding to the current BYE message, and the Flow-Status AVP in the Media-Component-Description AVP corresponding to the IP Flow is set to be removed (REMOVED).
  • the P-CSCF after receiving the BYE message, the P-CSCF sends an AAR message carrying the Flow-Status AVP to the REMOVED IP Flow, which means: releasing the bearer resource specified in the call, which is different from the prior art, and receives the BYE to send the STR message. It is to release all the bearer resources of the entire call.
  • the PCRF receives the Diameter AAR message sent by the P-CSCF, and removes only the PCC rules and bearer resources corresponding to the IP Flow carried in the Diameter AAR message according to the required REMOVED, and does not perform IP Flow other than the Diameter AAR message. deal with.
  • Solution 2 includes the following:
  • the calling P-CSCF When the calling P-CSCF receives the BYE message, it detects that the call is a SIP Forking scenario.
  • the Diameter message sent to the PCRF is a Diameter STR message. Since the existing Diameter STR message does not have a SIP-Forking-Indication AVP field and a Flows AVP field, the existing Diameter STR message is extended, and the SIP-Forking-Indication AVP field is added, when SIP-Forking is -Indication
  • the AVP value is set to SEVERAL_DIALOGUES(l).
  • the scenario for identifying the SIP Forking only needs to release the session bearer resources corresponding to the Flows AVP in the STR message.
  • the Flows AVP is the bearer resource corresponding to the branch session.
  • the calling P-CSCF receives the BYE message, although it detects that the call is a SIP Forking scenario, except for the session of the local call, there is no other surviving session, that is, only one SIP.
  • the session is consistent with the existing protocol.
  • the PCSCF sends a Diameter STR message to the PCRF. If the Diameter STR message is an extended message, that is, the SIP-Forking-Indication AVP field is added, the SIP-Forking- carried by the Diameter STR message is The Indication AVP value is set to SINGLE_DIALOGUE(O); if the Diameter STR message is not an extended message, the SIP-Forking-Indication AVP is not carried.
  • the AVP may be extended in the Diameter STR message sent by the P-CSCF to identify the SIP Forking; or the AF network element may extend other Diameter messages to indicate the SIP Forking.
  • the PCRF receives the Diameter STR message sent by the P-CSCF. If the SIP-Forking-Indication AVP value is SEVERAL-DIALOGUES(l), only the bearer information corresponding to the Flows AVP is released. If there is no SIP-Forking-Indication AVP When the value is SINGLE_DIALOGUE(O), all the bearer resources associated with the Diameter session are released.
  • Solution 3 includes the following:
  • the calling P-CSCF When the calling P-CSCF receives the BYE message, it detects that the call is a SIP Forking scenario. Except for the session that calls the local terminal, there are other related live sessions, and no Diameter message is sent.
  • the foregoing solution of the embodiment of the present invention is not limited to the QoS bearer resource control of the Rx interface.
  • the QoS bearer resource control of the interface also applies the principle of the embodiment of the present invention.
  • the foregoing solution of the embodiment of the present invention is not limited to the P-CSCF, and the principles of the embodiments of the present invention are applicable to the AFCF network element of the IMS system using the Rx interface, the Gq, and the AF network element of the interface.
  • the calling P-CSCF changes the main The field value of the Diameter AAR message when the INVITE 200OK is called; for the solution 1 of the second solution, the Diameter AAR message is used when one of the BYE calls is branched; for the solution 2 of the second solution, the BYE is extended when one of the call branches is extended. STR message; For solution 3 of solution 2, when one of the BYE calls a branch, the calling P-CSCF does not send any Diameter message, and the access to the IMS network is reached.
  • the user equipment can select the QoS bearer resource control of the called terminal according to the preference of the calling party, and also satisfies the intercommunication of the normal call in the case of the called SIP Forking, improves the system QoS capability, and improves the user experience.
  • a system for releasing quality of service quality bearer resources comprising: a called side terminal, a calling side network element, wherein the called side terminal is configured to send a BYE message to the calling side network element, or receive The BYE message sent by the calling side; the calling side network element is configured to release the media resources negotiated by the branch session only when the call is received in the SIP Forking scenario, and the other branch session negotiation is not processed.
  • the resources are carried.
  • the calling side network element is specifically a P-CSCF, and is further configured to use a Diameter AAR message when negotiating for one call branch session, an extended Diameter STR message when negotiating a call branch session, and not sending any Diameter message. Processing determines the release of media resources.
  • the P-CSCF when using the Diameter AAR message processing for a call branch session negotiation, detects that the call is a SIP Forking scenario, and the other session in this call survives the other session, and the Diameter AAR message is sent.
  • the SIP-Forking-Indication AVP is set to SEVERAL-DIALOGUES(1) and sent to the PCRF.
  • the Diameter AAR message also carries the bearer resource corresponding to the IP Flow of the branch session, and the AVP of the IP Flow is used. Property is set to remove;
  • the system further includes a PCRF configured to receive the Diameter AAR message sent by the P-CSCF, and set only the carried branch session of the Diameter AAR message to be removed according to the AVP attribute of the IP Flow.
  • the bearer resource corresponding to the IP Flow is released.
  • the P-CSCF when using the extended Diameter STR message processing for a call branch session negotiation, detects that the call is a SIP Forking scenario, and the other sessions in the call except the branch session survive the session.
  • the SIP-Forking-Indication AVP in the extended Diameter STR message is set to SEVERAL_DIALOGUES(l) and sent to a PCRF; wherein the extended Diameter STR message further carries a bearer resource corresponding to the IP flow of the branch session, and the Flows AVP is configured as a bearer resource corresponding to the branch session; the system further includes a PCRF configured to receive
  • the extended Diameter STR message sent by the P-CSCF releases only the bearer resources of the branch session corresponding to the Flows AVP in the Diameter STR message.
  • the P-CSCF when processing for not transmitting any Diameter message, detects that the call is a SIP Forking scenario, and the other sessions in the call except the branch session survive, and do not send any Diameter message to the PCRF;
  • the system also includes a PCRF, which is further configured to not receive any Diameter messages and does not release any bearer resources.
  • Embodiment 1 corresponding to the first embodiment:
  • FIG. 3 is a bearer control flow of the first embodiment corresponding to the first solution, which is mainly a process in which the calling P-CSCF receives the INVITE 200 OK, and the process processing before the INVITE 200 OK is omitted, and the process before the INVITE 200 OK is processed.
  • the process before the prior art INVITE 200 OK shown in FIG. 2 is the same, and will not be described here.
  • the process of the first embodiment includes the following steps:
  • Step 301 The 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 the downlink media information.
  • Step 303 The calling P-CSCF forwards the SDP offer request message to the S-CSCF to the called side.
  • Step 304 The calling S-CSCF forwards the INVITE 200 OK message of the SDP answer sent by the called party.
  • Step 305 the calling P-CSCF receives multiple temporary responses based on the previous call (such as INVITE). 180 or 183, etc.)
  • the calling P-CSCF receives multiple temporary responses based on the previous call (such as INVITE). 180 or 183, etc.)
  • the called party has SIP Forking, combining the downlink connection information acquired by 302, constructing a Diameter AAR message, wherein the SIP-Forking-Indication AVP setting is different from the ordinary call SINGLE_DIALOGUE(O), set to SEVERAL— DIALOGUES (1);
  • Step 306 The calling P-CSCF sends the session information to the PCRF network element by using a 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-Indication AVP is SEVERAL-DIALOGUES(l), and generates an additional PCC rule to be sent to the gateway;
  • Step 308 The bearer resource control result returned by the PCRF sends a Diameter AAA response message to the P-CSCF.
  • Step 309 The P-CSCF forwards the call response message to the calling side terminal device UE.
  • the above process only describes the processing of receiving the first INVITE 200 OK on the calling side P-CSCF, and the subsequent processing of receiving multiple INVITE 200 OKs is the same.
  • Embodiment 1 corresponding to the second scheme:
  • the process of the first embodiment includes the following steps:
  • Step 401 the calling P-CSCF receives the BYE message of the terminal releasing the call;
  • Step 402 The P-CSCF detects that only one SIP session exists in the current call, and the Diameter STR message specified by the protocol is used to release the associated Diameter session; if there are multiple SIP sessions in the current call, the current BYE only releases one of the sessions.
  • the P-CSCF finds the media information negotiated by the local session, sets the Flow-Status AVP corresponding to the IP Flow to REMOVED (4), and sets the value of the SIP-Forking-Indication AVP.
  • SEVERAL—DIALOGUES(l) constructing a Diameter AAA message
  • Step 403 The P-CSCF sends a Diameter AAA message.
  • Step 404 The PCRF receives the bearer request, that is, the Diameter AAA message, finds that the value of the SIP-Forking-Indication AVP is SEVERAL-DIALOGUES(l), and deletes all related IP flows whose Flow-Status AVP is set to REMOVED;
  • Step 405 the PCRF returns a Diameter AAA message
  • Step 406 The P-CSCF releases the SIP session resource associated with the branch, and forwards the BYE message.
  • Embodiment 2 corresponding to the second scheme:
  • FIG. 5 is a bearer control process of the second embodiment corresponding to the second embodiment, which is mainly a process in which the calling P-CSCF receives the BYE, and the process of establishing a call in the SIP Forking scenario is omitted, and the example selects a path from the calling UE.
  • the call is performed to describe the sending of a BYE message to other established or unestablished SIP sessions.
  • the process of the second embodiment includes the following steps:
  • Step 501 The calling P-CSCF receives the BYE message of the release call of the terminal.
  • Step 502 The P-CSCF detects that only one SIP session exists in the current call, and the Diameter STR message specified by the protocol is used to release the associated Diameter session; if there are multiple SIP sessions in the current call, the current BYE only releases one of the sessions.
  • the P-CSCF finds the media information of the local session negotiation, constructs the Diameter STR message, fills in the Flows AVP corresponding to the local session, and carries the SIP-Forking-Indication AVP as SEVERAL-DIALOGUES(l), which is used to identify the SIP Forking scenario. Release a 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, and finds that the value of the SIP-Forking-Indication AVP is SEVERAL-DIALOGUES(1), and only the bearer resource of the Flow AVP identifier is released.
  • Step 505 the PCRF returns a Diameter STA message.
  • Step 506 The P-CSCF releases the SIP session resource associated with the session and forwards the BYE message.
  • Embodiment 6 is a bearer control procedure of Embodiment 3 corresponding to the second embodiment, which is mainly a process in which the calling P-CSCF receives the BYE, and omits the process of establishing a call in the SIP Forking scenario, and the present example selects a path from the calling UE. Calling the call to describe the sending or sending of a BYE message to other established or unestablished calls.
  • the process of the third embodiment includes the following steps:
  • Step 601 The calling P-CSCF receives the BYE message of the release call of the terminal.
  • Step 602 The P-CSCF detects that only one SIP session exists in the current call, and the Diameter STR message specified by the protocol is used to release the Diameter session associated with the protocol. If there are multiple SIP sessions in the current call, the current BYE only releases one of the sessions. , does not send any Diameter message to the PCRF;
  • Step 603 The P-CSCF releases the SIP session resource associated with the current SIP session, and forwards the BYE message.
  • the prior art is that according to the existing 3GPP 29.214 protocol, when the first INVITE 200 OK is received on the calling P-CSCF, the identifier of the SIP Forking is indicated by SEVERAL—DIALOGUES is changed to SINGLE-DIALOGUE, so that the 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 choose the object to be answered.
  • the BYE at this time is the release of the entire SIP session bearer resource, or the release of the bearer resource corresponding to only one SIP session, and the different processing modes and protocols of the two scenarios.
  • the two There is no distinction between the two, and the unified use of the existing Diameter STR message to release, resulting in Forking, even if the main and called signaling plane has been opened, but the media face is still nowhere, the call can not continue.
  • the processing flow when the INVITE 200 OK and the BYE are received by the P-CSCF is improved.
  • the INVITE 200 OK is received, only the bearer negotiated by the local path is updated, and the underlying bearer negotiated by other branches is not processed.
  • the BYE is received, only the road association is released.
  • the bearer resources of the quotient do not deal with other branches, and to the greatest extent, satisfy the user's own choice.
  • the embodiment of the present invention is applied to a scenario in which the called SIP Forking occurs in the IMS, and when multiple calls are answered at the same time, the field in the message is extended by optimizing the network processing flow to adapt to the IMS in the SIP.
  • the purpose of QoS bearer resource control in the Forking scenario is applied to a scenario in which the called SIP Forking occurs in the IMS, and when multiple calls are answered at the same time, the field in the message is extended by optimizing the network processing flow to adapt to the IMS in the SIP.
  • the calling side network element receives the goodbye BYE message, detects that the call is a SIP Forking scenario, and only releases the media resources negotiated by the branch session, and does not process the resource bearer negotiated by other branch sessions. .
  • the resource bearer requirement of the SIP Forking scenario can be met in the media resource release.

Abstract

本发明公开了一种接入协商中服务质量承载资源控制的方法及系统，其中，该方法包括：媒体资源接入协商中，主叫侧网元收到被叫侧终端发送的INVITE 200 OK消息，检测到本呼叫为SIP Forking场景，仅对本分支呼叫会话协商的媒体资源进行更新操作，不处理其他分支会话协商的资源承载。本发明还公开了一种释放中服务质量承载资源控制的方法及系统，其中，该方法包括：媒体资源释放中，主叫侧网元收到BYE消息，检测到本呼叫为SIP Forking场景，仅对本分支呼叫会话协商的媒体资源进行释放，不处理其他分支会话协商的资源承载。采用本发明，能适应于SIP Forking场景资源承载需要。

Description

接入协商、 释放中服务庸量承载资源控制的方法及系统 技术领域
本发明涉及通信领域的资源控制技术， 尤其涉及一种 IP多媒体子系统 ( IMS, IP Multimedia Subsystem )被叫用户发生会话初始协议（ SIP， Session Initiation Protocol )分流（ Forking ) 的场景下， 主叫代理呼叫会话控制功能 ( P-CSCF, Proxy Call Session Control Function )在接入协商或释放过程中 进行服务质量（QoS， Quality of Service )承载资源控制的方法及系统。 背景技术
在传统的公共交换电话网络（ PSTN， Public Switched Telephone Network) 中， 一直很重视 QoS， 由于传统传送的业务比较单一， 网络的运营区域也比 较单一， 因此只需要对传送层保证一定的 QoS就可以了。 而在下一代网络 ( NGN, Next Generation Network ) 中传送的码流可以是低速、 高时延的非 实时的数据， 可以是高速、 低时延的多媒体流， 也可以使这些实时与非实 时的数据流的并存， 这些不同媒体的数据流要求 NGN中对于端到端的 QoS 有更严格的要求。
IMS作为 NGN的重要演进，提供了网络 QoS保障。 图 1是 IMS中实现 QoS 控制的参考框架， 其中 Rx接口是代理呼叫会话控制功能和策略计费规则功 能之间的标准接口。 整个构架包括： 用户设备（UE， User Equipment ) 101、 P-CSCF 102、 策略计费规则功能（ PCRF， Policy and Charging Rule Function ) 103、服务呼叫会话控制功能（ S-CSCF, Serving Call Session Control Function ) 104， 另外在会话过程中还涉及互连边界控制功能 ( IBCF, Interconnection Border Control Function ) 105、查询呼叫会话控制功能（ I-CSCF, Interrogating Call Session Control Function ) 106、 （ MGCF， Media Gateway Control Function ) 107等功能实体。
根据 3GPP标准协议 TS29.214的描述， 在 IMS中通过 Rx参考点实现策略 和计费控制 （PCC， Policy and Charging Control )。 按照协议描述， 应用功 能（ AF， Application Function ) 向 PCRF网元提供会话信息， 而会话信息按 照协议 3GPP TS29.213描述从 SIP信令中的会话描述协议 （ SDP， Session Description Protocol )部分映射为 Diameter授权认证清求 ( Diameter AAR ) 消息中的相关流信息 AVP， 对应的信息为 PCRF控制的媒体流信息。 其中， 所述 AF在 IMS中对应为 P-CSCF。 其中， 所述 AVP指 Diameter协议规定的属 性值对。
SIP Forking是 IMS系统中的基本功能。 所谓 SIP Forking指： 多款终端共 享一个用户号码， 终端可以使用不同的承载或具有不同的能力， 当此用户 作为被叫时， IMS网络查找被叫用户终端有并行以及串行两种选终端的方 式， 主叫用户根据一定策略选择一个被叫用户终端进行通话。 无论串行或 是并行，主叫侧 P-CSCF都需要向 PCRF提供主叫与被选择的被叫终端协商的 媒体资源。
当前协议中， 多路 SIP Forking场景下， QoS承载资源控制功能主叫侧流 程如图 2所示， 以两路为例， 该流程包括以下步骤：
步骤 201， UE发起呼叫流程， 邀请（ INVITE )请求消息中包含 SDP请 求 ( offer )信息；
步骤 202， P-CSCF收到呼叫时， 将 SDP信息映射为下行媒体信息； 步骤 203， P-CSCF转发邀请 ( INVITE )请求到 S-CSCF发往被叫； 步骤 204-步骤 211，为主叫 P-CSCF收到两路终端 INVITE 180消息的处理 流程。
这里， 对于主叫 P-CSCF而言， 存在 2路 SIP会话， 一路是主叫与 UE1之 间的 SIP会话， 一路是主叫与 UE2之间的 SIP会话。 205时 P-CSCF与 PCRF之 间创建 Diameter会话用于发送 205第一路，及 209第二路对应的 Diameter AAR 请求消 息； 205 中 的 Diameter AAR请求消 息 中 SIP多 路指示 ( SIP-Forking-Indication AVP ) 为 SINGLE— DIALOGUE ( 0 )， 同时携带 UE1 协商的媒体信息； 收到第二路 INVITE 180消息时， P-CSCF可判断出被叫发 生 Forking， Diameter AAR清求消息中 SIP-Forking-Indication AVP即为 SEVERAL— DIALOGUES ( 1 )， 同时携带 UE2协商的媒体信息；
步骤 212， S-CSCF将第一路终端返回的 INVITE 200 OK响应消息转发到 P-CSCF, 包含 SDP应答（answer )信息；
步骤 213， P-CSCF收到 INVITE 200 OK时， 将 SDP信息映射为上行媒体 信息；
步骤 214， P-CSCF发送主叫与被叫 UE1媒体协商对应的 Diameter AAR请 求消息到 PCRF网元请求资源授权， 其中， 在该 Diameter AAR请求消息中填 写媒体部件编号 （ Media-Component-Number AVP ) 以 及流编号 ( Flow-Number AVP )来共同标识、 由上行以及下行媒体信息组合生成的媒 体流 IP Flow, 并且填写 SIP-Forking-Indication AVP为 SINGLE— DIALOGUE ( 0 ); 其中， 所述 IP Flow即为主叫与被选择的被叫终端协商的媒体资源； 步骤 215， PCRF收到 SIP-Forking-Indication AVP为 SINGLE— DIALOGUE ( 0 )， 或者无 SIP-Forking-Indication AVP的 AVP时， 根据当前 Diameter AAR 请求消息携带的媒体资源更新 PCC规则， 同时， 移除未匹配当前 Diameter AAR请求消息中携带的 IP Flow对应的 PCC规则， 即： 移除主叫与被叫 UE2 协商的 IP Flow对应的 PCC规则， 发送 Diameter AAA响应消息到 P-CSCF; 步骤 216， P-CSCF转发会话响应消息到主叫侧 UE;
步骤 217， 若主叫用户， 选择第一路进行接听， 则主叫用户需要发送再 见（BYE )请求消息， 以拆除掉主叫与 UE2已经建立的 SIP会话；
步骤 218， P-CSCF释放主叫与 UE2建立的会话资源； 步骤 219， P-CSCF发送 Diameter会话终止请求（ Diameter STR ) 消息请 求到 PCRF， PCRF会释放已经申请的承载资源；
步骤 220， P-CSCF转发 BYE请求。
从上述流程可以看出，针对 SIP Forking场景，采用现有技术，则 P-CSCF 收到 第 一 个 INVITE 200OK 时 ， Diameter AAR请 求 消 息 中 SIP-Forking-Indication AVP就设置为 SINGLE— DIALOGUE ( 0 )， PCRF是以 该条 INVITE 200 OK对应的 Diameter AAA请求消息中对应的 IP Flow进行最 终申请的承载资源的确认， 之后， 删除主叫与被叫 UE2协商的 IP Flow对应 的 PCC规则， 并且 P-CSCF在收到拆除 UE2会话的 BYE消息， 发送 Diameter STR消息， 此 Diameter STR消息会将本呼叫所申请的所有承载资源全部释 放。
然而， 在 SIP Forking的场景下， 根据其支持的 RFC3261的协议描述， 媒 体资源接入协商过程中， 无论串行还是并行方式， 多个被叫终端的 INVITE 200OK都会透传到主叫用户， 主叫用户会根据设备的支持请求以及自身偏 好的情况， 最终选择合适的被叫终端进行接听， 选择权在主叫用户， 所选 择的接听终端也不一定是第一个回 INVITE 200 OK的终端， 而采用现有技 术， 主叫用户所选择的接听终端一定是第一个回 INVITE 200 OK的终端； 另 夕卜， 在 SIP Forking的场景下， 媒体资源释放过程中， 只要一路被叫终端返回 过临时响应 （如 INVITE 183消息）， 而主叫用户最终接听对象非该路终端， 就需要发送 BYE消息来释放与该终端建立的 SIP会话， 而采用现有技术， 主 叫 PCSCF会通知 PCRF释放所有承载资源。
可见， 采用现有技术所存在的问题是： 1 )对于 SIP Forking场景下媒体 资源接入协商过程，不支持多路被叫终端返回 INVITE 200 OK情况下的媒体 资源协商； 2 )对于 SIP Forking场景下媒体资源释放过程， 主叫发送 BYE消 息， 释放掉一路 SIP会话， 整个呼叫已经申请的承载资源都将释放， 无法保 证任何一路呼叫的正常的承载资源， 从而无法实现基本呼叫正常的互通。 总之，采用现有技术，对于 SIP Forking场景下的媒体资源接入协商过程、 以及媒体资源释放过程的 QoS承载资源控制，都无法满足 SIP Forking场景下 正常的呼叫处理。 发明内容
有鉴于此， 本发明实施例的主要目的在于提供一种接入协商中服务质 量承载资源控制的方法及系统，满足 SIP Forking场景下的媒体资源接入协商 过程的需要， 支持多路被叫终端返回 INVITE 200 OK情况下的媒体资源协 商。
本发明实施例的另一目的在于提供一种释放中服务质量承载资源控制 的方法及系统， 满足 SIP Forking场景下的媒体资源释放过程的需要，避免释 放所有的承载资源。
为达到上述目的， 本发明实施例的技术方案是这样实现的：
一种接入协商中服务质量承载资源控制的方法， 该方法包括： 媒体资 源接入协商中， 主叫侧网元收到被叫侧终端发送的邀请 INVITE 200 OK消 息， 检测到本呼叫为会话初始协议 SIP分流 Forking场景， 仅对本分支会话协 商的媒体资源进行更新操作， 不处理其他分支会话协商的资源承载。
其中， 所述主叫侧网元具体为代理呼叫会话控制功能 P-CSCF, 该方法 具体包括：
所述 P-CSCF收到 INVITE 200 OK, 如果检测到本呼叫为 SIP Forking场 景， 且本呼叫中除了本分支会话还存活其他会话， 则将 Diameter AAR消息 中的 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l)并发送给 策略计费规则功能 PCRF;
所述 PCRF收到所述 P-CSCF发送的所述 Diameter AAR消息， 对 Diameter AAR消息中携带的本分支会话的 IP Flow对应的策略和计费控制 PCC规则进 行更新处理， 对通过 Diameter AAR消息协商获取的其他分支会话的 IP Flow 对应的 PCC规则不作任何处理。
一种接入协商中服务质量承载资源控制的系统， 该系统包括： 被叫侧 终端、 主叫侧网元； 其中，
所述被叫侧终端， 配置为发送 INVITE 200 OK消息给所述主叫侧网元； 所述主叫侧网元， 配置为收到所述被叫侧终端发送的邀请 INVITE 200 OK消息， 检测到本呼叫为 SIP Forking场景， 仅对本分支会话协商的媒体资 源进行更新操作， 不处理其他分支会话协商的资源承载。
其中， 所述主叫侧网元具体为 P-CSCF, 该系统还包括 PCRF;
所述 P-CSCF配置为收到 INVITE 200 OK后， 当检测到本呼叫为 SIP Forking场景， 且本呼叫中除了本分支会话还存活其他会话时， 将 Diameter AAR消息中的 SIP-Forking-Indication AVP设置为 SEVERAL DIALOGUES ( 1 ) 并发送给所述 PCRF;
所述 PCRF， 配置为收到所述 P-CSCF发送的所述 Diameter AAR消息后， 对 Diameter AAR消息中携带的本分支会话的 IP Flow对应的 PCC规则进行更 新处理， 对通过 Diameter AAR消息协商获取的其他会话的 IP Flow对应的 PCC规则不作任何处理。
一种释放中服务质量承载资源控制的方法， 该方法包括： 媒体资源释 放中， 主叫侧网元收到再见 BYE消息， 检测到本呼叫为 SIP Forking场景， 仅 对本分支会话协商的媒体资源进行释放， 不处理其他分支会话协商的资源 承载。
其中， 所述主叫侧网元具体为 P-CSCF, 该方法还包括： 一个呼叫分支 会话协商时使用 Diameter AAR消息， 且将 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l)， IP Flow的 AVP属性设置为移除。
其中， 该方法具体包括： 所述 P-CSCF收到 BYE消息， 如果检测到本呼叫为 SIP Forking场景， 且 本呼叫中除了本分支会话还存活其他会话， 则将 Diameter AAR消息中的 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l)并发送给 PCRF; 其中， 所述 Diameter AAR消息中还携带本分支会话 IP Flow对应的承 载资源， 且将所述 IP Flow的 AVP属性设置为移除；
所述 PCRF收到所述 P-CSCF发送的所述 Diameter AAR消息，根据所述 IP Flow的 AVP属性， 仅对设置为移除的所述 Diameter AAR消息中携带的本分 支会话 IP Flow对应的承载资源进行释放。
其中， 所述主叫侧网元具体为 P-CSCF, 该方法还包括： 一个呼叫分支 会话协商时使用扩展的 Diameter STR消息，在扩展的 Diameter STR消息中增 加 SIP-Forking-Indication AVP并将其设置为 SEVERAL— DIALOGUES(l); 在 扩展的 Diameter STR消息中增加 IP Flow的 AVP属性。
其中， 该方法具体包括：
所述 P-CSCF收到 BYE消息， 如果检测到本呼叫为 SIP Forking场景， 且 本呼叫中除了本分支会话还存活其他会话，则将扩展的 Diameter STR消息中 的 SIP-Forking-Indication AVP设置为 SE VERAL DIALOGUES ( 1 )并发送给 PCRF; 其中， 所述扩展的 Diameter STR消息中还携带本分支会话的 IP Flow 对应的承载资源， 且所述 IP Flow的 AVP属性设置为本分支会话对应的承载 资源；
所述 PCRF收到所述 P-CSCF发送的所述扩展的 Diameter STR消息，根据 所述 IP Flow的 AVP属性， 仅对所述 Diameter AAR消息中携带的本分支会话 的 IP Flow对应的承载资源进行释放。
其中， 所述主叫侧网元具体为 P-CSCF , 该方法还包括： 不发送任何 Diameter消息。
其中， 该方法具体包括： 所述 P-CSCF收到 BYE消息， 如果检测到本呼叫为 SIP Forking场景， 且 本呼叫中除了本分支会话还存活其他会话， 则不发送任何 Diameter消息； 所 述 PCRF不会收到任何 Diameter消息， 不释放任何承载资源。
一种释放中服务质量承载资源控制的系统， 该系统包括： 被叫侧终端、 主叫侧网元； 其中，
所述被叫侧终端， 配置为发送 BYE消息给所述主叫侧网元， 或者接收 主叫侧网元发送的 BYE消息；
所述主叫侧网元， 配置为收到 BYE消息后， 当检测到本呼叫为 SIP Forking场景时， 仅对本分支会话协商的媒体资源进行释放， 不处理其他分 支会话协商的资源承载。
其中， 所述主叫侧网元具体为 P-CSCF, 进一步配置为分别针对一个呼 叫分支会话协商时使用 Diameter AAR消息、 一个呼叫分支会话协商时使用 扩展的 Diameter STR消息、 以及不发送任何 Diameter消息进行处理决定媒体 资源的释放。
其中， 所述 P-CSCF , 进一步在针对一个呼叫分支会话协商时使用 Diameter AAR消息处理时，检测到本呼叫为 SIP Forking场景，且本呼叫中除 了 本分支会话还存活其他会话， 将 Diameter AAR消 息 中 的 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l)并发送给 PCRF; 其中， 所述 Diameter AAR消息中还携带本分支会话的 IP Flow对应的 承载资源， 且将所述 IP Flow的 AVP属性设置为移除；
该系统还包括 PCRF，配置为收到所述 P-CSCF发送的所述 Diameter AAR 消息， 根据所述 IP Flow的 AVP属性， 仅对设置为移除的所述 Diameter AAR 消息中携带的本分支会话的 IP Flow对应的承载资源进行释放。
其中， 所述 P-CSCF, 进一步在针对一个呼叫分支会话协商时使用扩展 的 Diameter STR消息处理时， 检测到本呼叫为 SIP Forking场景， 且本呼叫中 除了本分支会话还存活其他会话， 则将扩展的 Diameter STR消息中的 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l)并发送给 PCRF; 其中， 所述扩展的 Diameter STR消息中还携带本分支会话的 IP Flow 对应的承载资源， 且所述 IP Flow的 AVP属性设置为本分支会话对应的承载 资源；
该系统还包括 PCRF， 配置为收到所述 P-CSCF发送的所述扩展的 Diameter STR消息， 根据所述 IP Flow的 AVP属性， 仅对所述 Diameter AAR 消息中携带的本分支会话的 IP Flow对应的承载资源进行释放。
其中， 所述 P-CSCF, 进一步在针对不发送任何 Diameter消息进行处理 时，检测到本呼叫为 SIP Forking场景，且本呼叫中除了本分支会话还存活其 他会话， 不发送任何 Diameter消息给所述 PCRF;
该系统还包括 PCRF， 进一步配置为不会收到任何 Diameter消息， 不释 放任何承载资源。
本发明实施例的媒体资源接入协商中， 主叫侧网元收到被叫侧终端发 送的邀请 INVITE 200 OK消息， 检测到本呼叫为 SIP Forking场景， 仅对本分 支会话协商的媒体资源进行更新操作， 不处理其他分支会话协商的资源承 载。采用本发明实施例，在媒体资源接入协商中能满足 SIP Forking场景的资 源承载需要。
本发明实施例的媒体资源释放中， 主叫侧网元收到再见 BYE消息， 检 测到本呼叫为 SIP Forking场景， 仅对本分支会话协商的媒体资源进行释放， 不处理其他分支会话协商的资源承载。 采用本发明实施例， 在媒体资源释 放中能满足 SIP Forking场景的资源承载需要。 附图说明
图 1为现有 IMS中实现 QoS控制的系统架构示意图；
图 2为采用现有技术在 SIP Forking场景下承载资源控制的方法流程图； 图 3为本发明方案一对应的实施例一的 QoS承载资源控制的方法流程 图；
图 4为本发明方案二对应的实施例一的 QoS承载资源控制的方法流程 图；
图 5为本发明方案二对应的实施例二的 QoS承载资源控制的方法流程 图；
图 6为本发明方案二对应的实施例三的 QoS承载资源控制的方法流程 图。 具体实施方式
在本发明实施例中， 媒体资源接入协商中， 主叫侧网元收到被叫侧终 端发送的邀请 INVITE 200 OK消息， 检测到本呼叫为 SIP Forking场景， 仅 对本分支会话协商的媒体资源进行更新操作， 不处理其他分支会话协商的 资源承载。 媒体资源释放中， 主叫侧网元收到再见 BYE消息， 检测到本呼 叫为 SIP Forking场景， 仅对本分支会话协商的媒体资源进行释放， 不处理 其他分支会话协商的资源承载。
由于目前协议对于 SIP Forking场景下， 第二路 INVITE 200 OK的承载 处理未明确，但是， 可以明确的是按照目前的协议： 第一路 INVITE 200 OK 会删除掉第二路媒体协商的结果， 从而使第二路 INVITE 200 OK要么申请 不到对应的媒体资源， 要么第二路媒体资源会覆盖第一路已经申请的媒体 资源。总之，采用目前协议并不适应 SIP Forking场景的 QoS承载资源控制， 无论是在媒体资源接入协商过程还是媒体资源释放过程， 因此， 本发明实 施例包括两部分方案， 方案一是针对媒体资源接入协商过程的 QoS承载资 源控制， 方案二是针对媒体资源释放过程的 QoS承载资源控制。 以下分别 阐述。
方案一： 媒体资源接入协商中， 主叫侧网元收到被叫侧终端发送的邀 请 INVITE 200 OK消息， 检测到本呼叫为 SIP Forking场景， 仅对本分支会 话协商的媒体资源进行更新操作， 不处理其他分支会话协商的资源承载。 能解决上述采用现有技术导致的问题 1， 对于 SIP Forking场景下媒体资源 接入协商过程， 支持多路被叫终端返回 INVITE 200 OK情况下的媒体资源 协商， 满足主叫能够根据自己的偏好选择合适的被叫终端的进行呼叫。
一种接入协商中服务质量承载资源控制的方法， 包括以下内容：
( a )主叫 P-CSCF在收到 INVITE 200 OK时， 检测到本呼叫为 SIP Forking场景， 除了本次呼叫本路终端的会话， 还有其它相关的存活的会话 时， 发送给 PCRF的 Diameter AAR消息将 SIP-Forking-Indication AVP设置 为 SEVERAL— DIALOGUES(l)。
( b ) PCRF收到 P-CSCF发送的 Diameter AAR消息，对 Diameter AAR 消息中携带的本路终端 IP Flow对应的 PCC 规则进行更新处理， 对通过 任何处理（包括删除， 更新）， 这样就能够保证每路申请的媒体资源得以保 持。
这里， 本发明实施例区别于现有技术， INVITE 200 OK 中 SIP-Forking-Indication AVP设置为 SEVERAL DIALOGUES(l) , 从而使 PCRF对其他路的 IP Flow对应的承载资源和 PCC不做任何处理，而现有技 术 是 INVITE 200 OK 中 SIP-Forking-Indication AVP 设 置 为 SINGLE— DIALOGUE(0)， 从而使 PCRF移除其他路终端的 IP Flow对应的 PCC规则。
一种接入协商中服务质量承载资源控制的系统， 该系统包括： 被叫侧 终端、 主叫侧网元； 其中， 被叫侧终端， 配置为发送 INVITE 200 OK消息 给所述主叫侧网元； 主叫侧网元， 配置为收到所述被叫侧终端发送的邀请 INVITE 200 OK消息， 检测到本呼叫为 SIP Forking场景， 仅对本分支会话 协商的媒体资源进行更新操作， 不处理其他分支会话协商的资源承载。 这里， 所述主叫侧网元具体为 P-CSCF, 该系统还包括 PCRF;
P-CSCF配置为收到 INVITE 200 OK后，当检测到本呼叫为 SIP Forking 场景， 且本呼叫中除了本分支会话还存活其他会话时， 将 Diameter AAR消 息中的 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l)并发 送给所述 PCRF; PCRF,配置为收到所述 P-CSCF发送的所述 Diameter AAR 消息后， 对 Diameter AAR消息中携带的本分支会话的 IP Flow对应的 PCC 规则进行更新处理， 对通过 Diameter AAR消息协商获取的其他会话的 IP Flow对应的 PCC规则不作任何处理。
方案二： 媒体资源释放中， 主叫侧网元收到再见 BYE消息， 检测到本 呼叫为 SIP Forking场景， 仅对本分支会话协商的媒体资源进行释放， 不处 理其他分支会话协商的资源承载。 能解决上述采用现有技术导致的问题 2， 对于 SIP Forking场景下媒体资源释放过程，主叫发送 BYE消息释放其中一 路 SIP会话时， 满足信令层面接通的呼叫媒体层面也能正常处理。
一种释放中服务质量承载资源控制的方法， 有三种解决方案。
解决方案一包括以下内容：
( a )主叫 P-CSCF在收到 BYE消息时， 检测到本呼叫为 SIP Forking 场景， 除了本次呼叫本路终端的会话， 还有其它相关的存活的会话时， 发 送给 PCRF的 Diameter消息为 Diameter AAR消息，由于现有 Diameter AAR 消息中本身就存在 SIP-Forking-Indication AVP字段， 因此，直接将 Diameter AAR 消 息 中 的 SIP-Forking-Indication AVP 设 置 为 SEVERAL— DIALOGUES(l)， 其中， 携带当前 BYE消息所对应的会话协商 的 IP Flow ， 并 且 将 IP Flow 对 应 的 媒 体 部 件 描 述 ( Media-Component-Description AVP ) 中的 Flow-Status (流状态） AVP设 置为移除（ REMOVED )。 这里， 所述收到 BYE消息后， P-CSCF发送 AAR消息携带 Flow-Status AVP为 REMOVED的 IP Flow, 是指： 将呼叫中指定的承载资源释放， 区 别于现有技术收到 BYE发送 STR消息是释放整个呼叫所有的承载资源。
( b ) PCRF 收到 P-CSCF发送的 Diameter AAR 消息， 根据设置的 REMOVED的需要， 仅仅移除 Diameter AAR消息中携带的 IP Flow对应的 PCC规则以及承载资源，对于 Diameter AAR消息以外的 IP Flow不作处理。
解决方案二包括以下内容：
( a )扩展 Diameter STR消息： 增力 σ可选 SIP-Forking-Indication AVP字 段， 以及流（ Flows AVP )字段， 其中 Flows AVP表示需要删除的 IP Flow 对应的编号。
主叫 P-CSCF在收到 BYE消息时， 检测到本呼叫为 SIP Forking场景， 除了本次呼叫本路终端的会话， 还有其它存活的会话时， 发送给 PCRF 的 Diameter消息为 Diameter STR消息， 由于现有的 Diameter STR消息中并没 有 SIP-Forking-Indication AVP字段和 Flows AVP 字段， 因此， 对现有的 Diameter STR消息进行了扩展， 增加了 SIP-Forking-Indication AVP字段， 当将 SIP-Forking-Indication AVP值设置为 SEVERAL— DIALOGUES(l), 用 来标识 SIP Forking 的场景仅需要释放 STR消息中 Flows AVP对应的会话 承载资源。 其中， Flows AVP为本分支会话对应的承载资源。
这里需要指出的是： 如果主叫 P-CSCF在收到 BYE消息时， 虽然检测 到本呼叫为 SIP Forking场景， 除了本次呼叫本路终端的会话， 没有其它存 活的会话时， 即只有一路 SIP会话， 则与现有协议保持一致， PCSCF发送 Diameter STR消息给 PCRF， 如果该 Diameter STR消息是扩展的消息， 即 增加了 SIP-Forking-Indication AVP字段， 则该 Diameter STR消息携带的 SIP-Forking-Indication AVP 值设置为 SINGLE— DIALOGUE(O)； 如果该 Diameter STR消息不是扩展的消息， 则不携带 SIP-Forking-Indication AVP。 这里，上述（ a )中， P-CSCF发送的 Diameter STR消息中可以扩展 AVP, 以标识 SIP Forking; 或者 AF 网元扩展其它 Diameter 消息来指示 SIP Forking。
( b ) PCRF 收到 P-CSCF 发送的 Diameter STR 消息， 若发现 SIP-Forking-Indication AVP 值为 SEVERAL— DIALOGUES(l)时， 仅释放 Flows AVP对应的承载信息； 若无 SIP-Forking-Indication AVP 或者值为 SINGLE— DIALOGUE(O)时，释放该 Diameter会话下的所关联的所有承载资 源。
解决方案三包括以下内容：
( a )主叫 P-CSCF在收到 BYE消息时， 检测到本呼叫为 SIP Forking 场景， 除了本次呼叫本路终端的会话， 有其它相关的存活的会话时， 则不 发送任何 Diameter消息。
( b ) PCRF不会收到任何 Diameter消息， 从而也不会释放任何承载资 源。
进一步地， 本发明实施例的上述方案并不仅限于 Rx接口的 QoS承载 资源控制，对于 Gq，接口的 QoS承载资源控制也适用本发明实施例的原理。 本发明实施例的上述方案不仅限于 P-CSCF,而且对于 IMS系统中的 AGCF 网元， 使用 Rx接口、 Gq， 接口的 AF网元均适用本发明实施例的原理。
综上所述， 与现有技术相比， 由于本发明实施例在 IMS系统的 QoS承 载资源控制过程中， 对于被叫发生 SIP Forking情况下， 针对方案一而言， 主叫 P-CSCF更改主叫 INVITE 200OK时 Diameter AAR消息的字段值； 针 对方案二的解决方案一而言， BYE其中一个呼叫分支时使用 Diameter AAR 消息； 针对方案二的解决方案二而言， BYE 其中一个呼叫分支时扩展 Diameter STR消息； 针对方案二的解决方案三而言， BYE其中一个呼叫分 支时， 主叫 P-CSCF不发送任何 Diameter消息， 达到了对接入 IMS网络的 用户设备能够根据主叫的偏好来自行选择被叫终端的 QoS承载资源控制， 同时也满足了被叫 SIP Forking的情况下，正常呼叫的互通，提高了系统 QoS 能力， 提升了用户的体验。
一种释放中服务质量承载资源控制的系统， 该系统包括： 被叫侧终端、 主叫侧网元； 其中，被叫侧终端， 配置为发送 BYE消息给所述主叫侧网元， 或者接收主叫侧发送的 BYE消息； 主叫侧网元， 配置为收到 BYE消息后， 当检测到本呼叫为 SIP Forking场景时， 仅对本分支会话协商的媒体资源进 行释放， 不处理其他分支会话协商的资源承载。
这里， 所述主叫侧网元具体为 P-CSCF, 进一步配置为分别针对一个呼 叫分支会话协商时使用 Diameter AAR消息、一个呼叫分支会话协商时使用 扩展的 Diameter STR消息、 以及不发送任何 Diameter消息进行处理决定媒 体资源的释放。
这里， 所述 P-CSCF , 进一步在针对一个呼叫分支会话协商时使用 Diameter AAR消息处理时， 检测到本呼叫为 SIP Forking场景， 且本呼叫中 除了本分支会话还存活其他会话， 将 Diameter AAR 消息中的 SIP-Forking-Indication AVP 设置为 SEVERAL— DIALOGUES(l)并发送给 PCRF; 其中， 所述 Diameter AAR消息中还携带本分支会话的 IP Flow对应 的承载资源， 且将所述 IP Flow的 AVP属性设置为移除；
该系统还包括 PCRF, 配置为收到所述 P-CSCF发送的所述 Diameter AAR消息， 根据所述 IP Flow的 AVP属性， 仅对所述 Diameter AAR消息 中设置为移除的携带的本分支会话的 IP Flow对应的承载资源进行释放。
这里， 所述 P-CSCF, 进一步在针对一个呼叫分支会话协商时使用扩展 的 Diameter STR消息处理时， 检测到本呼叫为 SIP Forking场景， 且本呼叫 中除了本分支会话还存活其他会话， 则将扩展的 Diameter STR 消息中的 SIP-Forking-Indication AVP 设置为 SEVERAL— DIALOGUES(l)并发送给 PCRF;其中，所述扩展的 Diameter STR消息中还携带本分支会话的 IP Flow 对应的承载资源， 且所述 Flows AVP设置为本分支会话对应的承载资源； 该系统还包括 PCRF， 配置为收到所述 P-CSCF 发送的所述扩展的 Diameter STR消息， 仅对所述 Diameter STR消息中 Flows AVP对应的本分 支会话的承载资源进行释放。
这里， 所述 P-CSCF,进一步在针对不发送任何 Diameter消息进行处理 时， 检测到本呼叫为 SIP Forking场景， 且本呼叫中除了本分支会话还存活 其他会话， 不发送任何 Diameter消息给所述 PCRF;
该系统还包括 PCRF， 进一步配置为不会收到任何 Diameter消息， 不 释放任何承载资源。
下面结合附图对技术方案的实施作进一步的详细描述。
方案一对应的实施例一：
图 3 是上述方案一对应的实施例一的承载控制流程， 主要是主叫 P-CSCF收到 INVITE 200 OK的处理过程， 其中省略了 INVITE 200 OK之 前的流程处理， INVITE 200 OK之前的流程处理如图 2 所示的现有技术 INVITE 200 OK之前的流程一样， 此处不做赘述。 实施例一的流程包括以 下步骤：
步骤 301， UE发起呼叫；
步骤 302， 拜访地网络的 P-CSCF收到携带 SDP offer的呼叫请求后， 将 SDP信息映射为下行媒体信息；
步骤 303， 主叫 P-CSCF转发 SDP offer请求消息到 S-CSCF发往被叫 侧；
步骤 304， 主叫 S-CSCF转发被叫侧发来的 SDP answer的 INVITE 200 OK消息；
步骤 305，主叫 P-CSCF基于前期本呼叫收到多条临时响应（如 INVITE 180或者 183等）判断被叫发生 SIP Forking的情况下， 结合 302获取的下 行连接信息， 构造 Diameter AAR消息， 其中 SIP-Forking-Indication AVP设 置 不 同 于 普 通 呼 叫 的 SINGLE— DIALOGUE(O) ， 设 置 为 SEVERAL— DIALOGUES (1);
步骤 306，主叫 P-CSCF通过 Diameter AAR消息发送会话信息到 PCRF 网元；
步骤 307， PCRF 收到承载请求即 Diameter AAA 消息， 发现 SIP-Forking-Indication AVP的值为 SEVERAL— DIALOGUES(l)，则生成附加 的 PCC规则下发给网关；
步骤 308， PCRF返回的承载资源控制结果发送 Diameter AAA响应信 息到 P-CSCF;
步骤 309， P-CSCF转发呼叫响应消息到主叫侧终端设备 UE。
上述流程仅描述主叫侧 P-CSCF上收到第一个 INVITE 200 OK的处理， 后续收到多个 INVITE 200 OK的处理相同。
方案二对应的实施例一：
图 4是方案二对应的实施例一的承载控制流程， 主要是主叫 P-CSCF 收到 BYE消息的处理过程，其中省略了 SIP Forking的场景下呼叫建立的过 程， 本实例从主叫 UE选择一路呼叫进行接听对其它建立或者未建立的 SIP 会话发送 BYE消息进行描述， 实施例一的流程包括以下步骤：
步骤 401， 主叫 P-CSCF收到终端的释放呼叫的 BYE消息；
步骤 402， P-CSCF检测发现， 本次呼叫仅存在一路 SIP会话则采用协 议规定的 Diameter STR消息释放与之关联的 Diameter会话； 若本次呼叫存 在多个 SIP会话， 当前 BYE仅释放其中一路会话， P-CSCF找到本路会话 协商的媒体信息， 并将该 IP Flow 对应的 Flow-Status AVP 设置为 REMOVED (4) ， 同 时 将 SIP-Forking-Indication AVP 的 值 为 SEVERAL— DIALOGUES(l)， 构造 Diameter AAA消息；
步骤 403， P-CSCF发送 Diameter AAA消息；
步骤 404， PCRF 收到承载请求即 Diameter AAA 消息， 发现 SIP-Forking-Indication AVP 的值为 SEVERAL— DIALOGUES(l)， 并将 Flow-Status AVP设置为 REMOVED的所有相关 IP Flow删除；
步骤 405， PCRF返回 Diameter AAA消息；
步骤 406， P-CSCF释放本分支关联的 SIP会话资源， 转发 BYE消息。 方案二对应的实施例二：
图 5 是方案二对应的实施例二的承载控制流程， 主要是主叫 P-CSCF 收到 BYE的处理过程， 其中省略了 SIP Forking的场景下呼叫建立的过程， 本实例从主叫 UE选择一路呼叫进行接听对其它建立或者未建立的 SIP会 话发送 BYE消息进行描述， 实施例二的流程包括以下步骤：
步骤 501， 主叫 P-CSCF收到终端的释放呼叫的 BYE消息；
步骤 502， P-CSCF检测发现， 本次呼叫仅存在一路 SIP会话则采用协 议规定的 Diameter STR消息释放与之关联的 Diameter会话； 若本次呼叫存 在多个 SIP会话， 当前 BYE仅释放其中一路会话， P-CSCF找到本路会话 协商的媒体信息，构造 Diameter STR消息，填写本路会话对应的 Flows AVP， 同时携带 SIP-Forking-Indication AVP为 SEVERAL— DIALOGUES(l)， 用于 标识 SIP Forking场景下释放一路 SIP会话；
步骤 503， P-CSCF发送 Diameter STR消息；
步骤 504， PCRF 收到承载请求即 Diameter STR 消息， 发现 SIP-Forking-Indication AVP的值为 SEVERAL— DIALOGUES(l),仅释放 Flow AVP标识的承载资源；
步骤 505， PCRF返回 Diameter STA消息；
步骤 506， P-CSCF释放本次会话关联的 SIP会话资源，转发 BYE消息。 方案二对应的实施例三：
图 6是方案二对应的实施例三的承载控制流程， 主要是主叫 P-CSCF 收到 BYE的处理过程， 其中省略了 SIP Forking的场景下呼叫建立的过程， 本实例从主叫 UE选择一路呼叫进行接听对其它建立或者未建立的呼叫发 送 BYE消息进行描述， 实施例三的流程包括以下步骤：
步骤 601， 主叫 P-CSCF收到终端的释放呼叫的 BYE消息；
步骤 602， P-CSCF检测发现， 本次呼叫仅存在一路 SIP会话则采用协 议规定的 Diameter STR消息释放与之关联的 Diameter会话； 若本次呼叫存 在多个 SIP会话， 当前 BYE仅释放其中一路会话， 不向 PCRF发送任何 Diameter消息；
步骤 603， P-CSCF释放本次 SIP会话关联的 SIP会话资源， 转发 BYE 消息。
这里， 对比现有技术和本发明实施例可知： 现有技术是根据现有 3GPP29.214协议， 在主叫 P-CSCF上收到第一个 INVITE 200 OK时， 就将 指 示 SIP Forking 的 标 识 由 SEVERAL— DIALOGUES 变 更 为 SINGLE— DIALOGUE， 使得 PCRF仅保留第一个 INVITE 200 OK中协商的 承载资源而删除了其它分支的底层承载资源， 剥夺了用户自主选择接听对 象的权利。 同时， 对于主叫 P-CSCF在收到 BYE消息时， 此时的 BYE是整 个 SIP会话承载资源的释放， 还是仅一路 SIP会话对应的承载资源的释放， 这两种场景的不同处理方式，协议上未作区分，统一都使用现有的 Diameter STR消息来释放， 导致 Forking的情况下， 即便主被叫信令面已经打通， 但 是媒体面仍不通， 呼叫接续不了。
而本发明实施例中， 改进了 P-CSCF收到 INVITE 200 OK以及 BYE时 处理流程，在收到 INVITE 200 OK时，仅对本路协商的承载进行更新操作， 不处理其它分支协商的底层承载， 同时， 在收到 BYE 时， 仅释放本路协 商的承载资源， 不对其它分支进行处理， 最大程度上， 满足了用户的自主 选择权。
综上所述， 采用本发明实施例， 应用于 IMS中被叫发生 SIP Forking的 场景下， 多路被叫同时接听时， 通过优化网络处理流程， 扩展消息中的字 段， 达到适应于 IMS在 SIP Forking的场景下 QoS承载资源控制的目的。
以上所述， 仅为本发明的较佳实施例而已， 并非用于限定本发明的保 护范围。 工业实用性
本发明实施例的媒体资源释放中， 主叫侧网元收到再见 BYE消息， 检 测到本呼叫为 SIP Forking场景， 仅对本分支会话协商的媒体资源进行释放， 不处理其他分支会话协商的资源承载。 采用本发明实施例， 在媒体资源释 放中能满足 SIP Forking场景的资源承载需要。

Claims

权利要求书
1、 一种接入协商中服务质量承载资源控制的方法， 该方法包括： 媒体 资源接入协商中， 主叫侧网元收到被叫侧终端发送的邀请 INVITE 200 OK 消息， 检测到本呼叫为会话初始协议 SIP分流 Forking场景， 仅对本分支会话 协商的媒体资源进行更新操作， 不处理其他分支会话协商的资源承载。
2、 根据权利要求 1所述的方法， 其中， 所述主叫侧网元具体为代理呼 叫会话控制功能 P-CSCF, 该方法具体包括：
所述 P-CSCF收到 INVITE 200 OK, 如果检测到本呼叫为 SIP Forking场 景， 且本呼叫中除了本分支会话还存活其他会话， 则将 Diameter AAR消息 中的 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l)并发送给 策略计费规则功能 PCRF;
所述 PCRF收到所述 P-CSCF发送的所述 Diameter AAR消息， 对 Diameter AAR消息中携带的本分支会话的 IP Flow对应的策略和计费控制 PCC规则进 行更新处理， 对通过 Diameter AAR消息协商获取的其他分支会话的 IP Flow 对应的 PCC规则不作任何处理。
3、 一种接入协商中服务质量承载资源控制的系统， 该系统包括： 被叫 侧终端、 主叫侧网元； 其中，
所述被叫侧终端， 配置为发送 INVITE 200 OK消息给所述主叫侧网元； 所述主叫侧网元， 配置为收到所述被叫侧终端发送的邀请 INVITE 200
OK消息， 检测到本呼叫为 SIP Forking场景， 仅对本分支会话协商的媒体资 源进行更新操作， 不处理其他分支会话协商的资源承载。
4、根据权利要求 3所述的系统， 其中， 所述主叫侧网元具体为 P-CSCF, 该系统还包括 PCRF;
所述 P-CSCF, 配置为收到 INVITE 200 OK后， 当检测到本呼叫为 SIP Forking场景， 且本呼叫中除了本分支会话还存活其他会话时， 将 Diameter AAR消息中的 SIP-Forking-Indication AVP设置为 SEVERAL DIALOGUES ( 1 ) 并发送给所述 PCRF;
所述 PCRF， 配置为收到所述 P-CSCF发送的所述 Diameter AAR消息后， 对 Diameter AAR消息中携带的本分支会话的 IP Flow对应的 PCC规则进行更 新处理， 对通过 Diameter AAR消息协商获取的其他会话的 IP Flow对应的 PCC规则不作任何处理。
5、 一种释放中服务质量承载资源控制的方法， 该方法包括： 媒体资源 释放中， 主叫侧网元收到再见 BYE消息， 检测到本呼叫为 SIP Forking场景， 仅对本分支会话协商的媒体资源进行释放， 不处理其他分支会话协商的资 源承载。
6、根据权利要求 5所述的方法， 其中， 所述主叫侧网元具体为 P-CSCF, 该方法还包括： 一个呼叫分支会话协商时使用 Diameter AAR消息， 且将 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l) , IP Flow的 AVP属性设置为移除。
7、 根据权利要求 6所述的方法， 其中， 该方法具体包括：
所述 P-CSCF收到 BYE消息， 如果检测到本呼叫为 SIP Forking场景， 且 本呼叫中除了本分支会话还存活其他会话， 则将 Diameter AAR消息中的 SIP-Forking-Indication AVP设置为 SEVERAL— DIALOGUES(l)并发送给 PCRF; 其中， 所述 Diameter AAR消息中还携带本分支会话 IP Flow对应的承 载资源， 且将所述 IP Flow的 AVP属性设置为移除；
所述 PCRF收到所述 P-CSCF发送的所述 Diameter AAR消息，才艮据所述 IP Flow的 AVP属性， 仅对设置为移除的所述 Diameter AAR消息中携带的本分 支会话 IP Flow对应的承载资源进行释放。
8、根据权利要求 5所述的方法， 其中， 所述主叫侧网元具体为 P-CSCF, 该方法还包括： 一个呼叫分支会话协商时使用扩展的 Diameter STR消息，在 扩展的 Diameter STR消息中增加 SIP-Forking-Indication AVP并将其设置为 SEVERAL— DIALOGUES(l); 在扩展的 Diameter STR消息中增加 IP Flow的
AVP属性。
9、 根据权利要求 8所述的方法， 其中， 该方法具体包括：
所述 P-CSCF收到 BYE消息， 如果检测到本呼叫为 SIP Forking场景， 且 本呼叫中除了本分支会话还存活其他会话，则将扩展的 Diameter STR消息中 的 SIP-Forking-Indication AVP设置为 SE VERAL DIALOGUES ( 1 )并发送给 PCRF; 其中， 所述扩展的 Diameter STR消息中还携带本分支会话的 IP Flow 对应的承载资源， 且所述 IP Flow的 AVP属性设置为本分支会话对应的承载 资源；
所述 PCRF收到所述 P-CSCF发送的所述扩展的 Diameter STR消息，根据 所述 IP Flow的 AVP属性， 仅对所述 Diameter AAR消息中携带的本分支会话 的 IP Flow对应的承载资源进行释放。
10、根据权利要求 5所述的方法，其中，所述主叫侧网元具体为 P-CSCF, 该方法还包括： 不发送任何 Diameter消息。
11、 根据权利要求 10所述的方法， 其中， 该方法具体包括：
所述 P-CSCF收到 BYE消息， 如果检测到本呼叫为 SIP Forking场景， 且 本呼叫中除了本分支会话还存活其他会话， 则不发送任何 Diameter消息； 所 述 PCRF不会收到任何 Diameter消息， 不释放任何承载资源。
12、 一种释放中服务质量承载资源控制的系统， 该系统包括： 被叫侧 终端、 主叫侧网元； 其中，
所述被叫侧终端， 配置为发送 BYE消息给所述主叫侧网元， 或者接收 主叫侧网元发送的 BYE消息；
所述主叫侧网元， 配置为收到 BYE消息后， 当检测到本呼叫为 SIP Forking场景时， 仅对本分支会话协商的媒体资源进行释放， 不处理其他分 支会话协商的资源承载。
13、根据权利要求 12所述的系统，其中，所述主叫侧网元具体为 P-CSCF, 进一步配置为分别针对一个呼叫分支会话协商时使用 Diameter AAR消息、 一个呼叫分支会话协商时使用扩展的 Diameter STR消息、 以及不发送任何 Diameter消息进行处理决定媒体资源的释放。
14、 根据权利要求 13所述的系统， 其中， 所述 P-CSCF, 进一步在针对 一个呼叫分支会话协商时使用 Diameter AAR消息处理时， 检测到本呼叫为 SIP Forking场景， 且本呼叫中除了本分支会话还存活其他会话， 将 Diameter AAR消息中的 SIP-Forking-Indication AVP设置为 SEVERAL DIALOGUES ( 1 ) 并发送给 PCRF; 其中， 所述 Diameter AAR消息中还携带本分支会话的 IP Flow对应的承载资源， 且将所述 IP Flow的 AVP属性设置为移除；
该系统还包括 PCRF，配置为收到所述 P-CSCF发送的所述 Diameter AAR 消息， 根据所述 IP Flow的 AVP属性， 仅对设置为移除的所述 Diameter AAR 消息中携带的本分支会话的 IP Flow对应的承载资源进行释放。
15、 根据权利要求 13所述的系统， 其中， 所述 P-CSCF, 进一步在针对 一个呼叫分支会话协商时使用扩展的 Diameter STR消息处理时，检测到本呼 叫为 SIP Forking场景，且本呼叫中除了本分支会话还存活其他会话， 则将扩 展 的 Diameter STR 消 息 中 的 SIP-Forking-Indication AVP设 置 为 SEVERAL— DIALOGUES(l)并发送给 PCRF;其中，所述扩展的 Diameter STR 消息中还携带本分支会话的 IP Flow对应的承载资源， 且所述 IP Flow的 AVP 属性设置为本分支会话对应的承载资源；
该系统还包括 PCRF， 配置为收到所述 P-CSCF发送的所述扩展的 Diameter STR消息， 根据所述 IP Flow的 AVP属性， 仅对所述 Diameter AAR 消息中携带的本分支会话的 IP Flow对应的承载资源进行释放。
16、 根据权利要求 13所述的系统， 其中， 所述 P-CSCF, 进一步在针对 不发送任何 Diameter消息进行处理时， 检测到本呼叫为 SIP Forking场景， 且 本呼叫中除了本分支会话还存活其他会话，不发送任何 Diameter消息给所述 PC F;
该系统还包括 PCRF， 进一步配置为不会收到任何 Diameter消息， 不释 放任何承载资源。
PCT/CN2013/084023 2012-09-24 2013-09-23 接入协商、释放中服务质量承载资源控制的方法及系统 WO2014044224A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP13839680.9A EP2899937B1 (en) 2012-09-24 2013-09-23 Qos bearer resource control method and system during access negotiation and release
US14/430,237 US9525741B2 (en) 2012-09-24 2013-09-23 Method and system for QOS bearer resource control during access negotiation and release

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210358260.7A CN103685200B (zh) 2012-09-24 2012-09-24 接入协商、释放中服务质量承载资源控制的方法及系统
CN201210358260.7 2012-09-24

Publications (1)

Publication Number Publication Date
WO2014044224A1 true WO2014044224A1 (zh) 2014-03-27

Family

ID=50321526

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/084023 WO2014044224A1 (zh) 2012-09-24 2013-09-23 接入协商、释放中服务质量承载资源控制的方法及系统

Country Status (4)

Country Link
US (1) US9525741B2 (zh)
EP (1) EP2899937B1 (zh)
CN (1) CN103685200B (zh)
WO (1) WO2014044224A1 (zh)

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105207982B (zh) * 2014-06-30 2019-10-11 中兴通讯股份有限公司 资源共享处理方法、装置及p-cscf
US10326605B2 (en) * 2014-07-16 2019-06-18 Telefonaktiebolaget Lm Ericsson (Publ) Policy control in session initiation protocol forking
CN106506319B (zh) * 2015-09-07 2019-06-25 中国移动通信集团公司 网页实时通信中服务质量会话参数的传递方法及转换网关
FR3045999A1 (fr) * 2015-12-18 2017-06-23 Orange Procede de communication entre un appelant et une pluralite de terminaux appeles
CN106921953B (zh) * 2015-12-24 2020-04-24 中国电信股份有限公司 一种差异化计费方法、lte网络系统及pcrf
CN108234406A (zh) * 2016-12-15 2018-06-29 中兴通讯股份有限公司 一种资源管理的方法、装置和系统
WO2019005227A1 (en) * 2017-06-30 2019-01-03 Google Llc METHODS, SYSTEMS AND MEDIA FOR VOICE CALL OPERATIONS
EP3646567B1 (en) 2017-06-30 2022-05-18 Google LLC Methods, systems, and media for connecting an iot device to a call
US11005715B2 (en) 2018-12-21 2021-05-11 T-Moblle USA, Inc. Latency-sensitive network-traffic quality of service
US11044194B2 (en) 2019-02-28 2021-06-22 T-Mobile Usa, Inc. QoS for latency-sensitive network-traffic flows
CN111641602B (zh) * 2020-05-13 2022-11-04 维沃移动通信有限公司 会话创建方法、装置及电子设备
CN115037358B (zh) * 2022-06-10 2023-06-16 广州爱浦路网络技术有限公司 卫星终端多路端到端通信方法、通信系统、装置及介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1756256A (zh) * 2004-09-30 2006-04-05 华为技术有限公司 一种处理分叉业务的方法
CN101127940A (zh) * 2006-08-17 2008-02-20 华为技术有限公司 Ims域中短消息业务报告的发送方法及ims域实体
US20080240375A1 (en) * 2005-05-19 2008-10-02 Jian Chen Method Of Processing Multiple Ring Back Tone In Voice Service Application Based On Sip Fork
WO2009097032A1 (en) * 2008-01-28 2009-08-06 Motorola, Inc. Managing call delivery in an internet protocol communication system

Family Cites Families (40)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8521889B2 (en) * 2003-05-15 2013-08-27 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for modifying bandwidth and/or quality of service for a user session in a network
US20060004924A1 (en) * 2004-06-30 2006-01-05 Nokia Corporation Method and system providing support for location and service category service discovery in a SIP environment using a SIP event package, forking and AOR registration
DE602005013281D1 (de) * 2004-12-17 2009-04-23 Huawei Tech Co Ltd Verfahren und system zum halten einer sitzungskontinuität
US7680481B2 (en) * 2005-03-07 2010-03-16 Alcatel-Lucent Usa Inc. Method and apparatus for linking charging records
EP1703668A1 (en) * 2005-03-18 2006-09-20 Nederlandse Organisatie voor toegepast-natuurwetenschappelijk Onderzoek TNO System for processing quality-of-service parameters in a communication network
CN100484141C (zh) * 2005-03-28 2009-04-29 华为技术有限公司 实现ims和cs业务并发时的终端能力交互和路由控制的方法
US9401934B2 (en) * 2005-06-22 2016-07-26 Microsoft Technology Licensing, Llc Establishing sessions with defined quality of service
CN100454814C (zh) * 2006-02-18 2009-01-21 华为技术有限公司 一种Fork场景下计费话单关联和区分方法
CN101030964B (zh) * 2006-03-03 2011-07-20 华为技术有限公司 会话控制装置和方法
FR2902590B1 (fr) * 2006-06-16 2008-08-01 Alcatel Sa Detection de boucles au sein d'un element intermediaire de signalisation sip
US8289965B2 (en) * 2006-10-19 2012-10-16 Embarq Holdings Company, Llc System and method for establishing a communications session with an end-user based on the state of a network connection
CN100461778C (zh) * 2006-08-17 2009-02-11 华为技术有限公司 短消息业务在多媒体子系统中实现分叉发送的方法及系统
US8850012B2 (en) 2006-08-21 2014-09-30 Nokia Corporation Mechanism for charging and session handling supporting forking
US8194555B2 (en) * 2006-08-22 2012-06-05 Embarq Holdings Company, Llc System and method for using distributed network performance information tables to manage network communications
US9288276B2 (en) * 2006-11-03 2016-03-15 At&T Intellectual Property I, L.P. Application services infrastructure for next generation networks including a notification capability and related methods and computer program products
ATE482560T1 (de) * 2006-11-06 2010-10-15 Ericsson Telefon Ab L M Einrichtungen und verfahren zum garantieren von dienstanforderungen auf benutzergerätebasis in einen träger
US8472431B2 (en) * 2008-01-24 2013-06-25 At&T Intellectual Property I, L.P. System and method of providing IMS services to users on terminating non IMS devices
US9246950B2 (en) * 2008-01-24 2016-01-26 At&T Intellectual Property I, L.P. System and method of providing registration macros in an IMS network-based device
US8948752B2 (en) * 2008-01-24 2015-02-03 At&T Intellectual Property I, L.P. System and method of providing IMS services to users on originating non IMS devices and other devices that do not have a previous relationship with the user
US8229468B1 (en) * 2008-01-25 2012-07-24 Avaya Inc. Using intelligent agents to perform flow path discovery in telecommunications systems and networks
US8520663B2 (en) * 2008-02-26 2013-08-27 At&T Intellectual Property I, L. P. Systems and methods to select peered border elements for an IP multimedia session based on quality-of-service
US8135124B2 (en) * 2008-03-21 2012-03-13 Microsoft Corporation Communicating information pertaining to cancelling of forked call requests
US8379655B2 (en) 2008-08-26 2013-02-19 Motorola Mobility Llc Data network and method for executing forking
EP2161899B1 (en) * 2008-09-08 2016-11-09 BlackBerry Limited Apparatus and method for macro operation involving a plurality of session protocol transactions
WO2010133251A1 (en) * 2009-05-19 2010-11-25 Telefonaktiebolaget Lm Ericsson (Publ) Establishing a communication session
US8392581B2 (en) * 2009-06-09 2013-03-05 Verizon Patent And Licensing Inc. Intelligent IMS SIP session setup optimization
WO2011020493A1 (en) 2009-08-17 2011-02-24 Nokia Siemens Networks Oy Control of session parameter negotiation for communication connection
US8612609B2 (en) * 2009-08-31 2013-12-17 At&T Intellectual Property I, L.P. Methods and apparatus to reassign quality of service priorities in a communication network
US20120166659A1 (en) * 2009-09-16 2012-06-28 Telefonaktiebolaget L M Ericsson (Publ) Node and Method for Quality of Service (QoS) Control
US8737387B2 (en) * 2009-10-30 2014-05-27 Mitsubishi Electric Corporation Gateway unit, communication system and communication method
US9071684B2 (en) * 2009-11-17 2015-06-30 Cisco Technology, Inc. Media forking
US8750291B2 (en) * 2009-11-22 2014-06-10 Avaya Inc. Enhanced call preservation techniques for SIP-based communication networks
US8898317B1 (en) * 2009-12-02 2014-11-25 Adtran, Inc. Communications system and related method of distributing media
US8200754B1 (en) * 2010-04-21 2012-06-12 Adtran, Inc. Communications system and related method for automatic call distribution
EP2619964B1 (en) * 2010-09-24 2018-02-07 Nexios IT Systems and methods for peer-to-peer ims
US9178917B2 (en) * 2010-12-16 2015-11-03 Palo Alto Research Center Incorporated Custodian routing with network address translation in content-centric networks
US20120166652A1 (en) * 2010-12-23 2012-06-28 Bouthemy Jean-Luc R Advanced simultaneous and sequential sip forking
US20130097333A1 (en) * 2011-06-12 2013-04-18 Clearone Communications, Inc. Methods and apparatuses for unified streaming communication
US9253219B2 (en) * 2012-03-30 2016-02-02 Avaya Inc. System and method to influence SIP routing by sequenced applications
US9277522B2 (en) * 2013-08-21 2016-03-01 Qualcomm Incorporated Exchanging rich communication suite capability information in a communications system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1756256A (zh) * 2004-09-30 2006-04-05 华为技术有限公司 一种处理分叉业务的方法
US20080240375A1 (en) * 2005-05-19 2008-10-02 Jian Chen Method Of Processing Multiple Ring Back Tone In Voice Service Application Based On Sip Fork
CN101127940A (zh) * 2006-08-17 2008-02-20 华为技术有限公司 Ims域中短消息业务报告的发送方法及ims域实体
WO2009097032A1 (en) * 2008-01-28 2009-08-06 Motorola, Inc. Managing call delivery in an internet protocol communication system

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2899937A4 *

Also Published As

Publication number Publication date
CN103685200A (zh) 2014-03-26
EP2899937A4 (en) 2015-09-23
US9525741B2 (en) 2016-12-20
EP2899937B1 (en) 2017-11-01
US20150237144A1 (en) 2015-08-20
EP2899937A1 (en) 2015-07-29
CN103685200B (zh) 2018-01-30

Similar Documents

Publication Publication Date Title
WO2014044224A1 (zh) 接入协商、释放中服务质量承载资源控制的方法及系统
KR101185669B1 (ko) 인터넷 프로토콜 멀티미디어 서브시스템 기반 3자간 통화를 위한 방법 및 장치
EP1973283B1 (en) Interworking network element, interworking system between the csi terminal and the ims terminal and the method thereof
US8774178B2 (en) Call transfer with multiple application servers in session initiation protocol-based network
US20130080648A1 (en) Session initiation from application servers in an ip multimedia subsystem
US20150295974A1 (en) Method, User Equipment and Application Server for Adding Media Stream of Multimedia Session
WO2007025429A1 (fr) Procede evitant la derivation du flux media et dispositif correspondant
WO2010063174A1 (zh) 一种ims监听的实现方法、系统及装置
WO2010037428A1 (en) Session establishment in a communication network
WO2014180410A1 (zh) 一种实现媒体QoS承载资源控制的方法及装置
WO2009086758A1 (zh) 一种在线彩铃或彩像业务的实现方法
US10313400B2 (en) Method of selecting a network resource
WO2009046653A1 (fr) Procédé, dispositif et système d'application de lignes directrices
WO2009124512A1 (zh) 控制早媒体播放的实现方法
WO2008040171A1 (fr) Procédé, système de domaine de commutation de circuits apercevant des informations de sessions multimédia du domaine ims
WO2011023041A1 (zh) 一种指示终端媒体类型的呼叫方法及系统
WO2008110110A1 (fr) Procédé et système de fourniture de service de sous-système multimédia ip
WO2014000429A1 (zh) 一种ip多媒体子系统架构下终端移动业务的实现方法及装置
WO2009135375A1 (zh) 实现单对话彩铃业务的呼叫建立方法
WO2007085199A1 (fr) Procédé, application et appareil permettant d'identifier l'état utilisateur dans des réseaux
EP3732841B1 (en) Method, system and entity for a media transfer session in an ims infrastructure
JP6234272B2 (ja) アーリーメディアの送信タイミングを制御するセッション制御方法、ｓｉｐサーバ及びプログラム
WO2009046645A1 (fr) Procédé pour la réalisation d'une interaction entre un service de transfert aveugle de conversation et un service de session
JP6549523B2 (ja) 要求先端末のオプション機能の非使用を整合する網間制御方法、ｓｉｐサーバ及びプログラム
JP6566522B2 (ja) 要求元端末のオプション機能の非使用を整合する網間制御方法、ｓｉｐサーバ及びプログラム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13839680

Country of ref document: EP

Kind code of ref document: A1

REEP Request for entry into the european phase

Ref document number: 2013839680

Country of ref document: EP

WWE Wipo information: entry into national phase

Ref document number: 14430237

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE