[go: up one dir, main page]

WO2007068206A1 - Procede et reseau de mise en marche d'informations concernant la capacite de session - Google Patents

Procede et reseau de mise en marche d'informations concernant la capacite de session Download PDF

Info

Publication number
WO2007068206A1
WO2007068206A1 PCT/CN2006/003395 CN2006003395W WO2007068206A1 WO 2007068206 A1 WO2007068206 A1 WO 2007068206A1 CN 2006003395 W CN2006003395 W CN 2006003395W WO 2007068206 A1 WO2007068206 A1 WO 2007068206A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
message
network
capability information
information
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2006/003395
Other languages
English (en)
Chinese (zh)
Inventor
Long Luo
Lei Zhu
Yajuan Wu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2007068206A1 publication Critical patent/WO2007068206A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • 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/1101—Session protocols
    • H04L65/1104—Session initiation protocol [SIP]

Definitions

  • the present invention relates to session establishment techniques in a Session Initiation Protocol (SIP) network, and more particularly to a method and network entity for performing session capability information operations during session establishment.
  • SIP Session Initiation Protocol
  • mobile communications are not limited to traditional voice communications, but can also combine multiple media services such as audio, video, pictures and text.
  • a variety of media services can meet the diverse needs of user equipment (UE) by combining data services such as presence, short message, web browsing, location information, push service (PUSH) and file sharing.
  • UE user equipment
  • data services such as presence, short message, web browsing, location information, push service (PUSH) and file sharing.
  • PUSH push service
  • 3GPP and 3GPP2 have successively launched IMS architectures.
  • the purpose is to implement a variety of multimedia service applications using a standardized open architecture in mobile networks, providing more to the UE. Choice and richer feelings.
  • IMS In the 3GPP Release 5 (R5, Release) phase, IMS is introduced, which is superimposed on the packet domain network, by Call Control Function (CSCF), Media Gateway Control Function (MGCF), Media Resource Function (MRF) and Home Subscriber A functional entity such as a server (HSS).
  • the CSCF can be divided into three logical entities: service CSCF (S-CSCF), proxy CSCF (P-CSCF) and query CSCF (I-CSCF).
  • S-CSCF service switching center of the IMS, performs session control, maintains session state, is responsible for managing UE information, and generates charging information.
  • the P-CSCF is an access point for the UE to access the IMS, completes UE registration, and is responsible for quality of service (QoS) Control and security management;
  • the I-CSCF is responsible for interworking between IMS domains, managing the allocation and selection of S-CSCFs, hiding network topology and configuration, and generating billing data.
  • the MGCF controls the gateway to implement interworking between the IMS and other networks.
  • MRF provides media resources.
  • the HSS stores subscription data, configuration information, and the like of the UE.
  • the IMS network defined by 3GPP can also be applied to the packet network defined in 3GPP2, providing interworking with multiple types of networks, and achieving independence from the use of terminal types. Therefore, there is no restriction on IMS being applied only to 3GPP related networks and applications. Other types of access networks and bearer network services and applications can also be implemented by the IMS architecture.
  • SIP is an IP telephony signaling protocol proposed by the Internet Engineering Task Force (IETF). SIP is used to initiate a session. It can control the establishment and termination of multimedia sessions attended by multiple participants, and can dynamically adjust and modify session attributes such as session bandwidth requirements, media types (voice, video, text, etc.), media. Codec format, support for multicast and unicast, etc. In IMS, the SIP protocol is used as the signaling control protocol for IP multimedia sessions.
  • IETF Internet Engineering Task Force
  • the service platform of the IMS network is a service platform based on SIP established Internet Protocol (IP) telephony sessions.
  • IP Internet Protocol
  • a session needs to be established between the terminal and the terminal or the AS.
  • the calling and called terminals need to negotiate the service capability, and the IMS in the process of the service capability negotiation.
  • Network entities on the network may participate in the process of business capability negotiation.
  • the service capability of a session refers to the ability to implement the required business needs after the negotiation of the session is completed.
  • the information of the business capability can be carried by the message body of the SIP message, and can be through Content/sdp, Content/application or Content/mime.
  • the calling terminal when the calling and called terminals negotiate the session through the IMS network, the calling terminal sends a session establishment request message to the called terminal through the IMS network, and the request uses the SIP message and carries the session capability information, and the request passes the Processing of network entities in an IMS network.
  • the network entity in the IMS network forwards the request to the called terminal.
  • the called terminal determines that it does not support the service capability of the calling terminal according to the session capability information carried in the request, it returns to the network entity or the master in the IMS network. Calling the terminal error response message, the network entity or the calling terminal in the IMS network receives the error response message and then re-executes the main called terminal.
  • negotiation and conversion of end business capabilities when the calling and called terminals negotiate the session through the IMS network, the calling terminal sends a session establishment request message to the called terminal through the IMS network, and the request uses the SIP message and carries the session capability information, and the request passes the Processing of network entities in an IMS network.
  • the service capability described herein refers to various capabilities required by the network entity of the IMS network or the calling and called terminal to implement the service, such as codec capability, multimedia processing capability, media parameter capability, and application, etc.
  • Information refers to the description of service capabilities, such as the method specified by the Session Description Protocol (SDP), and can also be described in the message body using XML voice and SCRIPT methods.
  • SDP Session Description Protocol
  • the network entity included in the process includes: a calling terminal UE1, a P-CSCF#1 to which the UE1 belongs, an S-CSCF#1 to which the UE1 belongs, and a called terminal.
  • UE2 P-CSCF #2 to which the called terminal UE2 belongs, and S-CSCF#1 to which UE1 belongs, the specific process is as follows:
  • Step 101 The UE1 adds an encoding parameter to the load of the SDP, where the encoding parameter reflects the service capability of the UE1 and the encoding parameters expected in the session.
  • Step 102 Carry an SDP in the session establishment request (INVITE) sent by UE1, and send it to P-CSCF#1.
  • Step 103 The P-CSCF#1 checks the media parameter information in the SDP. If the P-CSCF#1 cannot allow the media parameter information to be used in the session due to local policy reasons or QoS authorization reasons, the service capability negotiation is denied. . The rejection message will contain enough information to inform UE1 so that UE1 initiates the next session negotiation based on this information.
  • Step 104 P-CSCF#1 allows media parameter information to be used in the session, and CSCF #1 forwards the INVITE to S-CSCF #1.
  • Step 105 The S-CSCF#1 checks the media parameter information described in the SDP. If the S-CSCF#1 cannot allow the media parameter information to be used in the session due to the local policy reason or the UE1 subscription, the service capability negotiation is rejected. The rejection message will contain enough information to inform UE1 so that UE1 initiates the next session negotiation based on this information.
  • Step 106 S-CSCF#1 allows media parameter information to be used in the session, S-CSCF# 1 Forward the INVITE to S-CSCF # 2.
  • Step 107 The S-CSCF #2 checks the media parameter information described in the SDP. If the S-CSCF #2 cannot allow the media parameter information to be used in the session due to the local policy reason or the UE2 subscription, the service capability negotiation is rejected. In the rejection message, sufficient information is sent to UE1 so that 'UE1 initiates the next session negotiation based on this information.
  • Step 108 S-CSCF#2 allows the media parameter information to be used in the session, and S-CSCF#2 forwards the INVITE to P-CSCF #2.
  • Step 109 The P-CSCF#2 checks the media parameter information described in the SDP. If the P-CSCF #2 cannot allow the media parameter information to be used in the session due to local policy reasons or QoS authorization reasons, the service capability negotiation is rejected. . The rejection message will contain enough information to inform UE1 so that UE1 initiates the next session negotiation based on this information.
  • P-CSCF # 2 generates an authorization token (Authentication-Token).
  • Step 110 P-CSCF#2 allows media parameter information to be used in the session, P-CSCF#2 forwards the INVITE to UE #2, and the authorization token is included in the INVITE.
  • Step 111 UE#2 determines a complete set of encodings for completing the session, and compares the intersection of the encoded information in the SDP in the message. If any media is not supported, the port number of the media description is set to 0, for the supporting media. The port number of the media description is inserted to assign a port number.
  • Step 112 UE2 returns an SDP response to P-CSCF #2, that is, a description of a group of media streams and codes.
  • Step 113 P-CSCF#2 authorizes retaining these media streams and encoded QoS resources.
  • Step 115 S-CSCF#2 forwards the SDP response to S-CSCF#1.
  • Step 116 S-CSCF#1 forwards the SDP response to P-CSCF#1.
  • Step 117 P-CSCF#1 authorizes retaining these media streams and encoded QoS resources.
  • Step 119 UE1 determines which media streams are used in the session, and UE1 determines which encoding parameters are used in the media stream. If more than one media stream can be selected in a session, or if more than one encoding parameter can be selected in a media stream, then UE1 needs to negotiate with UE2 again to reduce the number of encoding parameters to one.
  • Steps 120-124 UE1 sends a proposed SDP (sold SDP) to UE2.
  • the coding parameters used in the session can be negotiated during the session negotiation process, and the coding parameters are the service capabilities negotiated by the called terminal.
  • the network entity decides whether to accept the negotiation request according to the local policy, the quality of service (QoS) authorization, or the subscription of the user. If the network entity rejects the session negotiation, it returns a rejection response, and in the response of the rejection. Provide sufficient information to the calling terminal so that the calling terminal decides how to proceed to the next session negotiation.
  • QoS quality of service
  • the IMS network entity involved in this process includes: an S-CSCF, an AS in the IMS network, and an MRF that provides IMS network media resources. The specific steps are as follows:
  • Step 200 The calling terminal UE1 sends an INVITE request carrying the session capability information of the UE1 to the S-CSCF, where the request carries a service identifier, which is used to identify the service type of the current service request.
  • Step 201 The S-CSCF returns, to the UE1, a response that receives the INVITE request, that is, a 100 Trying message.
  • Step 202 The S-CSCF determines, according to the service identifier carried in the INVITE request, the AS that processes the current service request, and forwards the INVITE request that carries the session capability information of the UE1 to the determined AS.
  • Step 203 The AS returns a response of the INVITE request to the S-CSCF.
  • Step 206 The S-CSCF sends an acknowledgement message, that is, an ACK message, to the UE2 that receives the error message.
  • Step 207 The S-CSCF forwards an error message, that is, a 606-2 message, to the AS.
  • Step 209 The AS returns an acknowledgement message, that is, an ACK-2 message, to the S-CSCF that receives the error message.
  • the INVITE request, the SDP of the UE2 is obtained by the AS from an error message carrying the session capability information supported by the UE2.
  • Steps 213 to 214 The S-CSCF sends a 200 OK response to the AS, and the AS returns an acknowledgement message, that is, an ACK-3 message, to the S-CSCF to receive the 200 OK message.
  • Step 215 The S-CSCF returns an acknowledgement message, that is, an ACK-3 message, to the MRP that receives the 200 OK message.
  • Step 216 Determine that the data transmitted between the UE1 and the UE2 is to be converted according to the SDP supported by the UE1 and the service capability supported by the UE2, and then continue to perform the subsequent establishment session according to the 3GPP IMS specification until the UE1 and the UE2 Establish a session between.
  • a method for performing session capability information operations comprising:
  • the session message may be a session establishment request message, a session establishment response message, a session establishment negotiation message, a session establishment negotiation confirmation message, a session update message, or a session update confirmation message.
  • the session establishment request message is an INVITE message or a REFER message; the session establishment response message is a 200 OK message; the session establishment negotiation message is a 183 message; and the session establishment negotiation confirmation message is a PRACK message.
  • the session update message is an UPDATE message or a REINVITE message; the session update confirmation message is a 200 OK message.
  • the network entity in the SIP network may add, delete, or/and modify the content in the session capability information in the session message sent by the calling party, and set the attribute information in the session capability information.
  • the modification of the message by the network entity further includes adding, deleting, or/and modifying the attribute information of the session capability information, and the session message is a session establishment request message or a session establishment response message.
  • the session capability information in the session message can be used.
  • the method description specified by the SDP protocol can also be described by describing a media information language (XML), or a scripting language (SCRIPT).
  • the modification of the session capability information specified by the SDP protocol may be extended to the description method specified by the SDP protocol.
  • Capability Server can also be replaced by Capability Provide Function.
  • the UE is mainly used as a calling party that initiates session negotiation as an example.
  • the calling party that initiates the session and the called party that terminates the session may be the UE, or may be the border gateway of the AS or SIP network that performs the client agent (UA).
  • the calling and called UEs in the SIP network can use the service capability negotiation method of the embodiment of the present invention as the calling party and the called party to perform session negotiation; a calling UE and an AS in the SIP network can serve as the calling party and the calling party.
  • the called party uses the service capability negotiation method of the embodiment of the present invention to perform session negotiation.
  • the two ASs in the SIP network can also use the service capability negotiation method of the embodiment of the present invention to perform session negotiation.
  • Step 300 The calling party sends a session establishment request message to the calling party side network entity, where the request message carries the session capability information of the calling party.
  • Step 303 The session negotiation processing entity may send a service capability query request supported by the SIP network to the Capability Server.
  • Step 304 The Capability Server returns a service capability query request response supported by the SIP network to the session negotiation processing entity, where the response carries the session capability information supported by the SIP network, for example, the description of the session capability information supported by the SIP network, SDP1, SDP2, and SDP3. And SDP4.
  • Steps 308-309 The called party that receives the session establishment request message carries the session capability information, such as the service capabilities described by SDP1, SDP2, SDP3, and SDP4, according to the service capability, and selects the service capability supported by itself, such as the service described by SDP4.
  • the capability by the called party side network entity, returns a response to the SDP4 carrying the session capability information of the calling party side network entity.
  • Step 310 The calling party side network entity forwards the received response of the SDP4 carrying the session capability information to the session negotiation processing entity.
  • Step 311 The session negotiation processing entity compares the description SDP4 of the session capability information carried in response with the description SDP1 of the session capability information supported by the calling party to determine whether the two are the same. If yes, determine the transmission between the calling party and the called party. The data is directly sent to the party through the session negotiation processing entity, and step 312 is performed; if not, the data transmitted between the calling party and the called party is converted into a service capability and then sent to the other party, and step 312 is performed.
  • the embodiment of the present invention may omit steps 303-304.
  • the session negotiation processing entity directly carries the stored service capability in the session establishment request. Sent in the message.
  • the service capability interaction process of the session negotiation in the embodiment of the present invention may be applied to multiple scenarios, such as the calling party network and the called party network, and the session service capability negotiation method of the embodiment of the present invention is supported; the calling party network supports the present invention.
  • the session service capability negotiation method of the embodiment, the called party network does not support the session service capability negotiation method of the embodiment of the present invention; the calling party network does not support the session service capability negotiation method of the embodiment of the present invention, and the called party network supports the present invention.
  • the session service capability negotiation method of the embodiment does not distinguish the primary called party network.
  • the calling party here may be a UE or a network entity in an IMS network.
  • the CSCF, the AS, the MRF, and the like in the different IMS networks may use the method in the embodiment of the present invention to modify the session capability information in the message body of the session message. And joining the session capability message supported by the IMS network.
  • the IMS network where the calling party is located and the network entity in the IMS network where the called party is located can use the method described in this embodiment of the present invention to modify the session in the session negotiation. Capability information and provided to the called party.
  • the descriptions SDP1, SDP2, SDP3, and SDP4 of the session capability information added to the session establishment request message by the IMS network where the calling party is located and the network entity on the IMS network where the called party is located are provided to the called party for selection. .
  • the network entity on the IMS network where the calling party is located and the IMS network where the called party is located can also query the Capability Server on the IMS network where it supports the session capability information supported by the IMS network.
  • the Capability Server returns the supported IMS network. Description of session capability information SDP.
  • the network entity on the IMS network where the primary and called parties are located joins the session capability information supported by the IMS network, it needs to follow the carrier's local policy and under the control of the operator.
  • the local policy is derived from the carrier's local settings and can be saved. On the Capability Server, it can also be saved on other network entities.
  • the embodiment of the present invention is described by performing a session establishment process in the IMS network.
  • a P-CSCF in the IMS network where the calling party is located.
  • #1, S-CSCF#1 and AS#1, P-CSCF#2, S-CSCF#2 and AS#2 in the IMS network where the called party is located participate.
  • the S-CSCF #1 in the IMS network where the calling party is located can modify the session capability information in the session establishment request message sent by the calling party according to the local policy, and add the description SDP2 of the session capability information supported by the calling party's IMS network.
  • the P-CSCF # 2 and S-CSCF # 2 on the IMS network where the called party is located are responsible for checking the session capability information and attribute information of the session negotiation, and deleting the session capability prohibited on the IMS network where the called party is located according to the operator's local policy.
  • the information, the description SDP5 of the session capability information supported by the IMS network of the called party is added to the session establishment request message according to the operator local policy, and the attribute information is set for the session capability information SDP5, and the session establishment request is set according to the content of the session negotiation.
  • the message is forwarded to AS#2 of the IMS network where the called party is located.
  • the AS #2 on the IMS network can change the session establishment request message, and add the SDP6 and SDP7 descriptions of the session capability information supported by the IMS network where the calling party can obtain the AS #2 to the session message.
  • the session capability information SDP6 and SDP7 set attribute information.
  • the network entity on the IMS network where the called party is located (including P-CSCF # 2, S-CSCF # 2 and AS # 2) must comply with the carrier's local policy and the carrier when joining the service capabilities supported by the IMS network. Under the control, the local policy is derived from the carrier's settings, and can be saved on the Capability Server or on other network entities.
  • These session capability information are divided into a plurality of session capability information blocks in the message using the method specified by the SDP protocol, and the plurality of session capability information blocks are distinguished using the session capability information attribute.
  • P-CSCF #1, S-CSCF #1 and AS #1 of the IMS network where the calling party is located and P-CSCF # 2, S-CSCF # 2 and AS # 2 of the IMS network where the called party is located are in the message body
  • SDP2, SDP3, SDP4, SDP5, SDP6, and SDP7 is provided to the called party for selection.
  • the IMS network where the called party is located sends a session establishment request message to the called party, and the called party selects the description SDP1 of the desired session capability information according to the session capability information of the session establishment request message and its service capability, and returns a response message.
  • a description of the SCP1 carrying the selected session capability information Therefore, in the session negotiation process in which both the calling party IMS network and the called party IMS network support the service capability of the embodiment of the present invention, the AS participates in the session protocol.
  • the process of business has completed the process of negotiating business capabilities.
  • the network entity on the SIP network can save the service capability for supporting the service on the Capability Server, and the service capability is saved according to different network entities.
  • the Capability Server query the Capability Server for the session capability required to provide the service.
  • the Capability Server retrieves the service capabilities that can be supported on the saved SIP network, and returns the description of the session capability information to the querying network entity in the query response message using the description format specified by the SDP protocol in accordance with the operator's local policy.
  • Different network entities in the IMS network may be querying network entities supporting the service capabilities in the IMS network.
  • the specific process of using the Capability Server by network entities such as CSCF, AS, and MRF is as follows.
  • P-CSCF #1 in the IMS network where the calling party is located.
  • P-CSCF in the IMS network where the calling party is located #1, S-CSCF#1 can modify the description of the session capability information in the session establishment request message sent by the calling party, SDP1, and add the description SDP2 of the session capability information supported by the IMS network where the calling party is located according to the local policy of the operator.
  • SDP3 and SDP4 can be pre-stored on AS #1, can be obtained from other ASs participating in the session, or can send service capability query requests to Capability Server#1. Query the session capability information supported by the IMS network saved on Capability Server#1. The message returned by Capability Server #1 is the description of the session capability information supported by the IMS network.
  • SDP3 and SDP4o CSCF in the IMS network where the calling party is located. responsible for forwarding the session negotiation processed by AS #1 to the IMS network where the called party is located, and describing the session capability information of the session negotiation SDP1, SDP2, SDP3, and SDP4.
  • the S-CSCF #2 on the IMS network where the called party is located is responsible for checking the session capability information of the session negotiation, and adding the description SDP5 of the session capability information supported by the IMS network of the called party to the session establishment request message according to the carrier local policy. And the attribute information is set for the session capability information SDP5, and the message is forwarded to the AS#2 of the IMS network where the called party is located according to the content of the session negotiation.
  • the local policy of the operator may be pre-set, may be determined according to the service capability of the network entity, or may be determined by combining pre-setting and service capabilities of the network entity.
  • the descriptions of the session capability information of the CSCF # 1 and AS # 1 of the IMS network where the calling party is located and the CSCF # 2 and AS # 2 of the IMS network where the called party is located in the message body are SDP2, SDP3, SDP4, SDP5, SDP6 and SDP7, provided to the called party to make a selection.
  • the S-CSCF #2 on the IMS network where the called party is located sends a session establishment request message to the called party, and the called party can select a description of the desired session capability information according to the session capability information of the session establishment request message and its service capability. SDP1, and carries a description SDP1 of its selected session capability information in the returned response message.
  • the network entity on the IMS network uses the session service capability negotiation method in the embodiment of the present invention to query the Capability Server for the session capability information on the IMS network, thereby completing the session negotiation process.
  • the MRF can be called by other network entities.
  • the MRF can also directly communicate with the calling and called parties as a SIP Proxy and SIP B2BUA.
  • the network entity may further determine whether to perform service media data routing according to the operation of the session capability information carried in the session message.
  • the process of determining whether to perform the service media data routing is as follows: The network entity determines whether the session capability information of the terminal carried by the session message cannot be operated, and if yes, sets the service media data route, and routes to the media resource function MRF. The session capability information carried by the session message is operated by the MRF; otherwise, the session capability information carried by the session message is directly operated by the network entity.
  • the method provided by the embodiment of the present invention can also be applied to the PoC service.
  • the following specific embodiments illustrate the application of the service capability negotiation in the PoC service.
  • PoC server provides the PoC service for the UE as the AS in the IMS platform.
  • the PoC server when the PoC server (Controlling) and the PoC Server (the Participating) receive the service negotiation request message, is called the INVITE request, and is in the INVITE request. Adding the business capabilities supported by the PoC server is provided to the called party to select.
  • PoC Server (Controlling) and PoC Server (Parting) may belong to the same IMS network or belong to different IMS networks.
  • PoC Server (Controlling) and PoC Server (Parting) may change the call request information of the session request by a PoC server.
  • the operation describing the content of the SDP can also be performed to change the call request.
  • the description of the speech capability information describes the operation of the content of the SDP.
  • Step 400 The UE1 sends a PoC session request to the S-CSCF1, that is, an INVITE request, where the request carries the session capability information SDP1 of the UE1, and may include attribute information.
  • Step 401 The S-CSCF1 determines, according to the INVITE request, that the current service is configured by the PoC Server.
  • Controlling Processes and forwards the INVITE request to the PoC Server (Controlling).
  • Step 402 The PoC Server (Controlling) sends an INVITE request describing the attributes of the SDP1, SDP2, SDP3, and SDP4 and the session capability information of the session capability information supported by the PoC Server (Controlling) to the S-CSCF1 according to the PoC service, where the service
  • the capability support information includes information about the network to which the PoC Server (Controlling) belongs, information indicating the PoC server, priority information, and other information used to identify the session capability information.
  • Step 406 The S-CSCF2 sends an INVITE request to the UE2.
  • Step 407 The UE2 that receives the INVITE request selects the SDP, which is supported by the SDP1, SDP2, SDP3, and SDP4, according to the description of the session capability information carried by the request, such as SDP4, and returns to the S-CSCF2 a 200 OK description SDP4 carrying the session capability information. response.
  • Steps 408 to 409 the S-CSCF2 sends the 200 OK response of the SDP4 to the PoC Server (Parting), and the PoC Server (Parting) returns a response to receive the 200 OK response to the S-CSCF2.
  • Step 410 The S-CSCF2 sends a description of the session capability information, and the 200 OK response of the SDP4 is sent to the S-CSCF1.
  • Step 412 The PoC Server (Controlling) compares the SDP4 description of the session capability information carried by the 200 OK response with the description SDP1 of the session capability information supported by the UE1, and determines whether the two are the same. If yes, the PoC Server determines the UE1 and The data transmitted between the UE2 is directly sent to the other terminal through the PoC Server (Controlling), and step 413 is performed; otherwise, the PoC Server (Controlling) determines that the data transmitted between the UE1 and the UE2 is converted into a service capability and then sent to the other terminal. 413.
  • Steps 413 to 414 the PoC Server (Controlling) sends a 200 OK response to the UE1 through the S-CSCF1 according to the procedure specified by the PoC service specification, and the service capability negotiation between the UE1 and the UE2 is completed.
  • the PoC Server (Controlling) implements the IMS-based PoC service capability negotiation process by using the interaction optimization process of the service capability negotiation in the embodiment of the present invention.
  • FIG. 5 is a diagram showing a service capability association of a terminal when an IMS network adopts a PoC service according to the present invention
  • the signaling flow chart of the second embodiment includes: the calling terminal UE1, the called terminal UE2, the S-CSCF1 to which the UE1 in the IMS network belongs, and the S-CSCF2 to which the UE2 in the IMS network belongs.
  • the PoC Server Controlling of the group in which the UE1 and the UE2 are located, the PoC Server (the Participating) that governs the UE2, and the PoC Server (the Participating) are supported by the SDP.
  • the session capability information has attribute information.
  • the PoC server processes the session capability information according to the attribute information. The specific steps are:
  • Step 500 The UE1 sends a PoC session request to the S-CSCF1, that is, an INVITE request, where the request carries the description SDP1 of the session capability information of the UE1.
  • the SDP1 may include attribute information, and the attribute information describes that the SDP1 is from the initiator terminal, and the priority is the highest level. Since UE1 sends the initiator terminal, it can also be specified that SDP1 does not add attribute information.
  • Step 501 The S-CSCF1 determines, according to the INVITE request, that the current service is processed by the PoC Server (Controlling), and forwards the INVITE request to the PoC Server (Controlling). In this process, the P-CSCF and the S-CSCF may perform a session. Ability information is checked.
  • Step 502 PoC Serve Controlling) sends a response to the S-CSCF 1 to receive the INVITE request.
  • Step 503 According to the PoC service specification, the S-CSCF1 sends the INVITE request to the S-CSCF2 according to the PoC service specification.
  • Step 505 The PoC ServerC Participating sends an INVITE request describing the SDP1, SDP2, SDP3, and SDP4 of the service capability supported by the PoC Server (Parting) to the S-CSCF2.
  • Step 506 The S-CSCF2 sends an INVITE request to the UE2.
  • Step 507 The UE2 that receives the INVITE request according to the description of the session capability information carried by the request SDP1, SDP2, SDP3, and SDP4 selects the SDP supported by itself, such as SDP4, and returns the S-CSCF2 with the description of the SDP4 carrying the session capability information. Response to S-CSCF2.
  • Step 508 The S-CSCF2 sends a 200 OK response carrying the SDP4 to the PoC Server (Parting).
  • Step 509 The PoC Server (Parting) compares the SDP4 description of the session capability information carried by the 200 OK response with the description SDP1 of the session capability information supported by the UE1, and determines whether the two are the same. If yes, the PoC Server (Parting) determines the UE1 and The data transmitted between the UE2 is directly sent to the opposite terminal through the PoC Server (Controlling), and step 510 is performed; otherwise, the PoC Server (Parting) determines that the data transmitted between the UE1 and the UE2 is converted into a service capability and then sent to the other terminal, and the steps are performed. 510.
  • Step 510 The PoC Server (Parting) returns a response to the 200 OK response to the S-CSCF2.
  • Step 511 The S-CSCF2 sends a 200 OK response to the S-CSCFL.
  • Step 512 The S-CSCF1 forwards the 200 OK response to the PoC ServerC Controlling.
  • Steps 513-514, PoC Server (Controlling) sends a 200 OK response to UE1 through S-CSCF1 according to the procedure specified by the PoC service specification, and the service capability negotiation between UE1 and UE2 is completed.
  • the PoC Server (Parting) implements the IMS-based PoC service capability negotiation process by using the interaction optimization process of the service capability negotiation in the embodiment of the present invention.
  • PoC Server ( Controlling ) and PoC Server ( Participating ) are respectively controlled The AS of the network where the PoC service is located and the AS of the network where the calling and called terminals are located. It should be noted that after receiving the INVITE message, the PoC Server (Controlling) and the PoC Server (Parting) can add the description SDP of the session capability information supported by the network to the INVITE request to provide the called terminal for selection. When PoC Server (Controlling) and PoC Server (Parting) add session capability information, you can describe the attribute information of session capability information. PoC Server (Controlling) can add the attributes of session capability information to belong to the initiator network and control session network. Lower than the session capability information of the terminal.
  • the PoC Server (Parting) can add the session capability information attribute to the called party network.
  • the priority of setting the session capability information can be higher or lower than the priority of the session capability information added by the PoC Server (Controlling).
  • the PoC server may first check attribute information of multiple session capability information, and according to priority information, home network information, and other information, multiple One or more of the session capability information is selected in the session capability information. Selecting a corresponding parameter describing the session capability information among the selected one or more session capability information.
  • FIG. 6 is a schematic diagram of the service capability conversion supported by the called terminal in the IMS network according to the present invention, as shown in the following figure:
  • the session between the UE1 and the UE2 is established through the AS of the IMS network, and the AS can be based on the type of service provided and
  • the service capability provided by itself determines whether the server needs to provide service capability support. If yes, the data transmission between UE1 and UE2 is respectively transmitted by the AS and the server after the service capability is converted.
  • the data transmission between the UE1 and the UE2 is performed by the AS, and the service capability conversion in the process of sending the data to the other party may be performed independently by the AS, or the AS may authorize other services in the IMS network.
  • the entity of the capability conversion function is completed, and can also be completed by other entities in the AS and IMS networks that have the capability conversion function. to make.
  • the other server provides the service capability conversion of the data transmitted by the calling party and the called party; when the description of the session capability information selected by the called party is different from the description SDP of the session capability information supported by the calling party, and the called party In the selected SDP, there is a description of the session capability information supported by the AS, and the description of the session capability information supported by the other server.
  • the AS and the other server jointly provide the service capability conversion of the data transmitted by the calling party and the called party.
  • Figure ⁇ is a flowchart of a signaling embodiment of a terminal for performing service capability negotiation in an IMS network, where the network entity includes: a calling terminal UE1, a called terminal UE2, and an S-CSCF1 to which the UE1 in the IMS network belongs.
  • the specific steps are as follows:
  • Step 701 The S-CSCF1 returns, to the UE1, a response that receives the INVITE request, that is, a 100 Trying message.
  • Step 702 The S-CSCF1 determines, according to the INVITE request, an AS that provides a service capability negotiation function, and forwards the INVITE request to the AS.
  • Step 703 The AS sends a service capability query request to the Capability Server.
  • Step 704 The Capability Server returns a service capability query request response to the AS, where the response carries a description SDP of the session capability information supported by the IMS network, for example, SDP1, SDP2, SDP3, and SDP4.
  • SDP1 and SDP2 are descriptions of service capabilities supported by the AS, and SDP1, SDP2, SDP3, and SDP4 are descriptions of service capabilities supported by other servers.
  • Step 705 The AS sends an INVITE request carrying the service capability descriptions SDP1, SDP2, SDP3, and SDP4 to the S-CSCF1.
  • Steps 706 ⁇ 707 S-CSCF1 sends the received INVITE request to UE2 through S-CSCF2.
  • Steps 708 to 709 the UE2 that receives the INVITE request, according to the description of the session capability information carried by the request, SDP1, SDP2, SDP3, and SDP4 selects the service capabilities supported by the UE, such as SDP4 and SDP2, and returns to the S-CSCF1 through the S-CSCF2. 200 OK response for SDP4 and SDP2.
  • the service capability described by the selected SDP4 is the service capability supported by the application server, and the service capability described by the selected SDP2 is the service capability supported by the AS.
  • Step 710 The S-CSCF1 forwards the received 200 OK response of the SDP4 and SDP2 carrying the service capability to the AS.
  • Step 711 The AS compares the description of the session capability information carried by the 200 OK response with the SDP4 and the SDP1 supported by the UE1 to determine whether the two are the same. If yes, the AS determines that the data transmitted between the UE1 and the UE2 directly passes through the AS and the application. The server sends the signal to the other party, and performs step 712. If not, the data transmitted between the UE1 and the UE2 is determined to be converted to a service capability, and then sent to the other party through the AS and other servers. Step 712.
  • Steps 712-713 the AS sends a 200 OK response to the UE1 through the S-CSCF1, and the service capability negotiation between the UE1 and the UE2 is completed.
  • a specific embodiment is used to describe the operations of the network entity of the SIP network to add, delete, or/and modify the session establishment request message and the session establishment response message for session establishment, so as to implement the session capability of the embodiment of the present invention. Information operation.
  • FIG. 8 is a flow chart of Embodiment 2 of signaling for performing service capability negotiation in an IMS network according to the present invention.
  • the network entity involved includes: a calling terminal UE1, a called terminal UE2, a network entity in a SIP network to which UE1 belongs, a network entity to which UE2 belongs, a processing entity in a SIP network to which UE1 belongs, and a SIP network to which UE2 belongs.
  • Processing entity 2 in .
  • the processing entity 1 and the processing entity 2 respectively add, delete, and modify the session capability information in the message body of the session establishment request message and the session establishment response message, and implement the session negotiation process.
  • the processing entity may be an independent network entity, or may be a logical function integrated on the network entity, and the network entity may be an AS, a CSCF, an MRF, a SIP-ALG, or the like.
  • the specific steps are:
  • Step 800 The UE1 sends an INVITE request message to the network entity 1, where the request message carries the session capability information of the UE1.
  • Step 801 The network entity 1 forwards the INVITE request message to the processing entity 1.
  • Step 802 803 The processing entity 1 checks the session capability information in the message body of the INVITE request message, and adds the session capability information supported by the SIP network where the ⁇ 1 is located, and then sends the INVITE request message to the network entity 1.
  • Step 804 The network entity 1 transmits an INVITE request message to the processing entity 2.
  • Step 805 806 Processing the entity 2, checking the session capability information in the message body of the INVITE request message, deleting the session capability information that is not supported by the SIP network to which the UE2 belongs, adding the session capability information supported by the SIP network to which the UE2 belongs, and modifying the INVITE After requesting the session capability information in the message body of the message, the INVITE request message is sent to the network entity 2. ,
  • Step 810 The network entity 2 sends a session establishment response message response carrying the session capability information supported by the UE2 to the processing entity 2.
  • Step 815 The network entity 1 transmits a response message to the UE1, and the process of the service capability negotiation is completed.
  • the method for negotiating the service capability provided by the embodiment of the present invention may be not limited to the network used by the network, that is, the functional entity used in the network where the calling party is located, and may be CSCF, AS, MRP, and SIP-ALG, and may be the above.
  • the network entity is not limited to these network entities; it can also be used for the SIP network where the called party is located.
  • the method for negotiating the service capability in the embodiment of the present invention may be used at the same time as the service network where the calling party and the called party are located, or may be separately used. In addition, in some applications, the calling party network may not be distinguished, and may also be used. This method of business capability negotiation.
  • the network entity in the SIP network can directly change the session establishment request message when the calling party sends a session establishment request message carrying the service capability of the calling party to the SIP network.
  • the information of the service capability supported by the SIP network is carried in the request message and sent to the called party, and the called party selects the service capability supported by the called party and sends the response to the SIP network through the session establishment response message.
  • the network entity, the network entity in the SIP network performs subsequent processing according to the accepted service capability supported by the called party, and the network entity in the SIP network can also add, delete, and modify the service capability of the session establishment response message.
  • the calling terminal does not wait until the called terminal returns the reject message, and then re-negotiates the service capability between the calling and called terminals, and directly provides the session capability information of the SIP network for the called party.
  • the terminal selects, thereby the process of negotiating the service capability negotiation between the calling and called terminals, and reducing the delay of session establishment.
  • the session capability information can be described by using the SDP protocol, that is, the session message adopts SDP.
  • the session capability information carried in the session message may be divided into multiple session capability information blocks, and the SDP adds a number and an attribute definition to the session capability information block, so that multiple session capability information blocks carried by the session message can be Identifying, and determining which session capability information block to select for processing based on the number and attributes of the session capability information block.
  • the session capability information block is identified by a number, for example, the number is defined as Series, or is defined as SDP ID, etc., and series is used as the number of the session capability information block.
  • the numbering enables multiple session capability information blocks in the message body of the same session message to be distinguished from each other.
  • the method of the identification may be:
  • the specific usage method is: if the current session capability information block is the third session capability information block in the current session message, the session capability information block is identified.
  • the sequence number is defined from 0 - n, and the message body that does not support a session message in the embodiment of the present invention contains more than n different session capability information blocks.
  • the range of the number can also be determined according to the processing capability of the SIP network.
  • the embodiment of the present invention may set the end flag information to the session capability information block: Since the message body of the session message may include multiple session capability information blocks, it is necessary to increase the end flag of the session capability information block at the end of each session capability information block.
  • the information enables the network entity of the SIP network to identify the end flag information of the session capability information block.
  • the end flag information is defined as the end flag of a complete session capability information block. Once the network entity of the SIP network finds the end flag, it can be determined that a session capability information block has ended.
  • the embodiment of the present invention can define the end flag of the session capability information block in the ⁇ finished manner.
  • Embodiment 1 The embodiment of the present invention defines a message body content in a session message as follows.
  • a definition of a message body content attribute is newly added in a message header of a session message, and a message body content attribute describes a content attribute of a message body content of the session message, and the message body content attribute is provided to the network entity and the session initiator. , or / and message recipients.
  • Which session capability information blocks, attributes of these session capability information blocks, and priority levels are carried in the message body.
  • the content attribute of the message body of the session message is defined as follows.
  • the message header of the session message is defined as Content
  • the definition of the Content field is as follows:
  • the message header Content indicates that the session capability information block carried in the message body of the session message is described in this field.
  • Series[x] represents the number of the session capability information block. After each series[x], it is necessary to include the attribution attribute of the session capability information block, the priority level, and the description attribute attribute of the media information of the session capability information block.
  • the attribution attribute identifies which network entity the session capability information block belongs to.
  • the home attribute of the session capability information block is the terminal, the session initiator, the network where the calling terminal is located, the network where the session controller is located, or/and the called terminal is located.
  • the internet The following defined method is used in the embodiment of the present invention: Define the attribution attribute of the session capability information block, that is, Belong is endpoint, origination network:, focus network:, or / and termination network.
  • the description of the media information of the session capability information block that is, the Entity specifies which network entity the description of the media information belongs to, and may belong to an AS, a Session Controller, such as a PoC CF, Conference Server, etc., or/and a resource controller, such as MRF, media gateway, etc.
  • a Session Controller such as a PoC CF, Conference Server, etc.
  • a resource controller such as MRF, media gateway, etc.
  • Entity As Application Server ⁇ Session Controller or / and Resource Controller.
  • the priority determination process of the session capability information block is as follows.
  • the priority may be included in the message body content attribute set in the message header of the session message. Since the called party determines which network the session capability information block belongs to and which network entity belongs to, by analyzing the session capability information block, the priority order of the plurality of session capability information blocks in the session message body can be determined, and each session capability information is The priority of the block is set in the message body content attribute in the message header of the session message.
  • the embodiment of the present invention also defines the content length in the message body of the session message. After the description of the attribute of the session capability information block in the message body in the session message ends, the session capability information block should be identified by the method of counting the number of bytes in decimal. The specific definition is that if a session capability information block is 518 bytes long, the length is defined as: Content-length: 518.
  • the specific method for extending the message header of the session message in the embodiment of the present invention is as follows.
  • the message header of the session message in the embodiment of the present invention performs content attribute setting on the content part in the message body of the session message, thereby expanding the message header.
  • the extended method is to add a description Content field of the message body content attribute in the message header of the session message for each session capability information block or other message body content in the message body of the session message, and to view this in the Content field.
  • the type, format, content length, etc. of some message body contents are described.
  • all session capability information blocks or message body contents in the message body of the session message are set with a content attribute in the message header of the session message, and the content attribute defines the session capability information block or the number of the message body content, the network to which it belongs, or the network to which it belongs or The terminal, which network entity it belongs to, the priority of the option, the type of content, such as SDP, picture or audio, etc., encoding format or/and message body content length.
  • the first message body content carried by the session message is a session capability information block desired by the calling party, and the second message body content is that the calling party adds a personal photo to the session message, and the third message body
  • the content is a session capability information block provided by the SIP network where the calling party is located;
  • the fourth message body content is the session capability information block provided by the network where the session controller is located.
  • Embodiment 2 The definition of the message body type is added to the message body of the session message, and the message body content attribute of the session message is expanded, and the rest is the same as that of Embodiment 1.
  • the message body content attribute including the message body type is used in the session message as described below.
  • the message body of the session message can contain multiple session capability information blocks, then the type of the Content-type identifier in the message header of the session message should be, Content-type: Application/MIME.
  • each session capability information block in the message body of the session message should be described.
  • the session capability information block in the message body of the session message needs to be used in the message header.
  • the field describes the message body type.
  • the called party's use of the message body type in the message header of the session message is: The calling party is received in the message header of the session message.
  • the message body representing the session message received by the called party carries multiple complete session capability information blocks.
  • the called party needs to view the content of the Content field in the message header of the session message, and based on the content attribute of each session capability information block in the Content field, determines which session capability information block selects the media parameter desired by the called party.
  • the content in the message body of the session message includes:
  • a plurality of media parameters may be present in a session capability information block. Therefore, a description of the media parameter attribute and the priority information is added to a session capability information block carried in the session message, according to the description of the media parameter attribute. It can be obtained which type of network entity or terminal the media parameter belongs to, and the priority level of the media parameter is determined according to the priority information of the media parameter. In this way, the called party of the session message can obtain the service attribute information of the media by viewing the media parameter attribute, and can effectively select the media parameter.
  • the media parameters of the session capability information block include three types:
  • the first category belongs to the session information, including the session identifier and other session-level parameters, such as the IP address of the session initiator, the topic, the contact information of the session or the creator, etc.; Timing description information, including start and stop time, number of repetitions, and one or more media level descriptions;
  • third category belongs to media type and format description information, including transport protocol and transport address, such as IP address and port number, type of media, Encoding type and other media parameters.
  • the definition of the media parameter attribution attribute and the priority is added, and a method for how the called party selects the media parameter according to the attribution attribute and priority of the media parameter is provided.
  • multiple media parameters from different networks and network entities are added in the session capability information block.
  • the description of the media parameters needs to be distinguished in different media parameters.
  • the description of the media parameter may be a description of the network parameter belonging to which network in the session negotiation process, the type of network entity to which the media parameter belongs, the priority parameter to which the network entity or the called party joins, or/and other attributes.
  • the description of the media parameter in the message body of the session message received by the called party including the network parameter belonging to the network in the session negotiation process, the network entity to which the media parameter belongs, the priority of the network entity or the receiver.
  • a description of the parameters, or/and other attributes, the called party uses the description of these media parameters to select the media parameters for this session negotiation.
  • the format of the message body of the session message is as follows.
  • o (owner/creator and session identifier).
  • timing level The parameters defined by the timing level are:
  • the parameters defined at the media level are:
  • the specific meaning of the media parameters of the session capability information block can be referred to the RFC 2327 standard.
  • the actual travel example of the present invention uses the a parameter to increase the media parameter attribution attribute, the media parameter type, and the media parameter priority definition.
  • the media parameter attribution attribute is defined as the network entity or terminal where the media parameter is located.
  • the format of the definition is:
  • the belonging may be the end point of the session, the network where the session initiator is located, the network where the message receiver is located, or/and the network where the controller is located, and the specific definition may be endpoint origination networks termination network:, or / and focus network :.
  • the endpoint indicates the media parameter provided by the calling party;
  • the origination network indicates the media parameter provided by the calling party's network;
  • the termination network indicates the media parameter provided by the called party's network;
  • the focus network identifies the media provided by the session controller's network. parameter.
  • the media parameter priority attribute is defined as the priority order of the media parameters provided by the network. For example, it is specified that the smaller the number between 0 and n, the higher the priority.
  • the parameter 0 indicates that the media parameter belongs to a type of media parameter that is preferentially supported by the service, and belongs to the most commonly used media parameter.
  • the media parameter of parameter 0 may be one or more, and is a media parameter recommended by the network entity.
  • Parameter 1 represents, in addition to the recommended media parameters, other media parameters provided by the network.
  • multiple media parameters of the session capability information block can be considered as multiple media parameters within a group. Since the default group is unique in the session capability information block in RFC 3388 describing the definition of the media parameter grouping, it is extended on the basis of which a plurality of media parameter groups are included in one session capability information block.
  • the method of using the media attribution attribute and priority of the calling party in the message body of the session message is as follows.
  • the calling party is the initiator of the session, and the session capability information block that sends the session establishment request message to the network in which it is located carries the expected media parameters of the session initiator, and the media parameters are in addition to the normal media parameter attributes.
  • the method of using the media parameter attribution attribute and priority in the message body of the session message by the network side is as follows.
  • Adding media parameter attribution attribute and priority attribute on the network side can be divided into three parts, namely, the network where the calling party is located, the network where the controlling party is located, and the network where the called party is located.
  • the three parts of the network may separately add media parameters supported by the network, or may provide media parameters supported by the network by a certain network.
  • the schematic diagram of the network is shown in FIG. 6.
  • the network where the calling party is located After receiving the session establishment request message, the network where the calling party is located processes the content in the session establishment request message according to the normal process of the IMS specification, and can also add the service capability supported by the network where the calling party is located to the session establishment request message. in.
  • the session capability information block of the session establishment request message is added with multiple or more sets of media parameters, and the network where the session initiator is located needs to set the media parameter attribution attribute and the priority attribute for the plurality or groups of media parameters.
  • the network where the calling party is located processes the session establishment request message according to the normal flow of the IMS specification.
  • the network where the service controller is located processes the content in the session establishment request message according to the normal process of the IMS specification, and can also add the service capability supported by the network where the service controller is located to the session establishment request.
  • the session capability information block of the session establishment request message is added with multiple or more sets of media parameters, and the network where the controller is located needs to set the media parameter attribution attribute and the priority attribute for the added plurality or groups of media parameters.
  • the network where the calling party is located and the network where the controlling party is located may be the same network, that is, the network where the PoC server (Controlling) is located is both the network where the calling party is located and the network where the calling party is located. The network where the controlling party is located.
  • the network where the controller is located processes the session establishment request message according to the normal flow of the IMS specification.
  • the network where the called party is located processes the content in the session establishment request according to the normal process of the IMS specification, and can also add the service capability supported by the network of the called party to the session establishment request.
  • the SDP description of the session establishment request is added with multiple or multiple sets of media parameters, and the network where the message receiver is located needs to set the media parameter attribution attribute and the priority attribute for the multiple or multiple sets of media parameters. Since the judgment of the priority is made on the AS, and the other network entities cannot determine the priority of the current media parameter, the criterion for the priority of the AS judgment can be considered to be uniform and no conflict occurs.
  • the network where the called party is located processes the session establishment request message according to the normal flow of the IMS specification.
  • the process of adding the media parameters supported by the network side in the call setup request message may be optional.
  • the network where the calling party is located, the network where the controlling party is located, and the network where the called party is located may select whether to join the network supported by the network.
  • the condition for judging whether to join the media parameters supported by the network may be the service f or the like.
  • the processing procedure of the session capability information block in the session establishment request message by the AS is as follows.
  • the AS acts as a service processing network entity in the IMS network and can be responsible for the IMS network. Query the media parameters supported by the IMS network, and add the media parameters of the query to the session establishment request. In this case, the media parameter attribution attribute and the priority parameter need to be added to the media parameters in the added media parameters.
  • the media parameters are stored on the network entity on the IMS platform.
  • the media parameters do not need to carry the parameter attribution attribute and the priority parameter before being sent to the AS.
  • the priority attributes of the media parameters are added to the obtained media parameters according to the services to be provided by the AS.
  • the method of determining the media parameter priority attribute by the AS may be determined according to the description of the media parameter attribute in the message body of the session negotiation message.
  • the entity in the SIP network may also edit or add or delete the application information carried in the request message, and the application information includes ringtones, pictures, messages, videos, and executable programs. And so on.
  • the called party can execute or delete the application information according to the settings of the called party.
  • FIG. 9 is a signaling flowchart of a method for a network entity to add a ringtone and modify a ringtone to a message body in a session establishment request message according to the present invention.
  • the entities involved include: a calling terminal UE1, a called terminal UE2, and a SIP network.
  • S-CSCF #1 in the SIP network to which UE1 belongs S-CSCF in the SIP network to which UE2 belongs, 2, AS #1 in the SIP network to which UE1 belongs, and AS #2 in the SIP network to which UE2 belongs, assuming AS #1
  • Step 900 The UE1 sends a session establishment request message, that is, an INVITE request, to the S-CSCF #1, where the request carries the session capability information of the UE1, and the UE1 may also add the ringtone playback program Sound to the message body of the request message.
  • a session establishment request message that is, an INVITE request
  • Step 901 The S-CSCF #1 determines, according to the INVITE request, that the current service is by AS #1. Processing, forwarding the INVITE request to AS #1.
  • Step 902 AS #1 determines, according to the policy of the operator, whether to add, modify, or delete the ringtone player Sound saved on the AS #1 supported by the SIP network in the message body of the session message. If the operator's policy requires AS #1 to join the ringtone player Sound # l and delete the original ringtone player Sound, AS #1 sends an INVITE request carrying Sound #1 to S-CSCF #1.
  • Step 903 The S-CSCF #1 sends the received INVITE request to the S-CSCF #2.
  • Steps 904 ⁇ 905 S-CSCF # 2 sends the received INVITE request to AS # 2 , and AS # 2 can select whether to add, change, or delete the content in the message body of the session request message according to the policy of the operator, and return to receive.
  • the response to the INVITE request is given to S-CSCF #2, and the message body of the session request message may include Sound #1 and/or Sound #2.
  • Step 906 S-CSCF # 2 sends an INVITE request to the UE.
  • Steps 907-908 The ringtone playing program carried by the UE2 that receives the INVITE request according to the request, in addition to the session negotiation, plays a ringtone to the user who uses the UE2. At this time, UE2 returns a 200 OK response to S-CSCF #2 and performs other operational steps of the session negotiation process.
  • AS #1 and AS #2 modify the content of the message body of the session establishment request message according to the policy of the operator, and may add, modify, or delete the ringtone player Sound in the message body of the request message.
  • other application information is provided.
  • the network entity that edits or adds or deletes the application information in the message body of the session establishment request message may be one or more of the S-CSCF, the P-CSCF, the AS, and the MRF, and is not limited to the above network entity.
  • the application information of the network entity to edit or add or delete application information may include, but is not limited to, ringtones, pictures, messages, videos, and program content.
  • the process of editing or adding or deleting application information by a network entity can be performed simultaneously with the process of session negotiation. Conducting does not affect the process of business capability negotiation.
  • FIG. 10 is a signaling flowchart of a description of a media entity in a SIP network in a SIP network that adds a video type to a message body in a session establishment request message, and the network entity involved is: a session initiator terminal UE1, a session access The party terminal UE2, the AS #1 in the SIP network to which the UE1 belongs, and the AS#2 in the SIP network to which the UE2 belongs, the specific steps are as follows:
  • Step 1000 UE1 sends a session establishment request message to AS#1. Since UE1 only supports audio, only the description of the media information of the audio media type supported by UE1 is carried in the session request setup message.
  • Steps 1001 to 1003 after receiving the session establishment request message, AS#1 adds a description of the media information of the video media type supported by AS#1 to the message, and then sends a session establishment request message to UE2 through AS#2.
  • AS# 1 may also add priority level and attribute information to the description of each media information in the session establishment request message, and provide it to UE2 for reference.
  • Step 1004 After receiving the session establishment request message, the UE2 selects the audio and video media type in the description of the media information carried in the session establishment request message as the result of the session establishment.
  • UE2 can first determine that UE1 only supports audio, UE2 must select an audio media type; then UE2 can determine that AS#2 supports video, UE2 selects the video media type, and video communication can be established between AS#2 and AS#1.
  • audio and video communication can be performed through AS#2 and AS#1 and UE2.
  • Steps 1005 ⁇ 1006 UE2 returns a 200 OK message through AS#2, which carries a description of the media information of the audio and video media type selected by UE2.
  • Step 1007 After receiving the 200 OK message, AS#1 determines that UE2 selects audio and The video media type is used as the media type of the session. AS#1 establishes an audio media type connection between AS#1 and UE1, and establishes an audio and video media type connection between AS#1 and UE2 via AS#1. A 200 OK message is returned to UE1, which carries a description of the media information of the audio media type supported by UE1.
  • the description of the media information of the audio and video media type selected by the UE2 may or may not be carried in the 200 OK message returned by the AS1 to the UE1.
  • the UE1 may determine the present.
  • the media type of the secondary session, if not carried, does not affect UE1's use of audio as a media type in this session.
  • the embodiment of the present invention further adds a system for session capability information operation.
  • the terminals in the SIP network are connected by one or more network entities set by the present invention.
  • a terminal in a SIP network can be a receiver or a sender.
  • the network entity includes: a receiving module 120, a policy obtaining module 121, and a processing module 122, which are sequentially connected, and a response module 123 and a forwarding module 124 respectively connected to the processing module 122;
  • the receiving module 120, the response module 123, and the forwarding module 124 are also connected to respective terminals in the SIP network.
  • the terminal that is, the sender of the session message, sends the session message to the receiving module 120.
  • the policy obtaining module 121 transparently transmits the session message received by the receiving module 120 to the processing module 122 and processes the session message.
  • the policy is sent to the processing module 122.
  • the processing module 122 processes the session message by using the policy of processing the session message
  • the generated session establishment request message is sent to the forwarding module 124, or the session establishment response message is sent to the response module 123, and the forwarding module 124
  • the session establishment request message is sent to the terminal, and the response module 123 sends a session establishment response message to the corresponding terminal, that is, the receiver of the session message.
  • the network entity in the embodiment of the present invention further includes a Capability Provide Function and a policy.
  • the obtaining module is connected, configured to store a policy for processing the session message, and send the stored policy for processing the session message to the policy acquiring module.
  • the Capability Provide Function can also exist independently of the network entity.

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Procédé et réseau utilisés pour la mise en marche d'informations concernant la capacité de session. Selon le procédé, un message de capacité de session contenu dans l'information concernant la session est mis en oeuvre après que le réseau de protocole de lancement de session SIP ne reçoive l'information contenant le message. Le procédé et le réseau sont en mesure de négocier la capacité de service entre la partie appelante et la partie appelée afin de réduire la configuration de la session.
PCT/CN2006/003395 2005-12-13 2006-12-13 Procede et reseau de mise en marche d'informations concernant la capacite de session Ceased WO2007068206A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200510134644.0 2005-12-13
CN200510134644.0A CN100550908C (zh) 2005-12-13 2005-12-13 一种进行会话能力信息操作的方法及网络实体

Publications (1)

Publication Number Publication Date
WO2007068206A1 true WO2007068206A1 (fr) 2007-06-21

Family

ID=38162567

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/003395 Ceased WO2007068206A1 (fr) 2005-12-13 2006-12-13 Procede et reseau de mise en marche d'informations concernant la capacite de session

Country Status (2)

Country Link
CN (1) CN100550908C (fr)
WO (1) WO2007068206A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102970751A (zh) * 2012-11-21 2013-03-13 华为技术有限公司 一种lte网络下完成业务协商的方法、装置及系统

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101340613B (zh) * 2007-07-05 2012-12-12 华为技术有限公司 一种实现用户终端通信的方法、装置和系统
US8549615B2 (en) * 2007-11-29 2013-10-01 Telefonaktiebolaget L M Ericsson Method and apparatuses for end-to-edge media protection in an IMS system
US8838805B2 (en) * 2008-01-11 2014-09-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for establishing a streamed media session
CN102843336A (zh) * 2011-06-20 2012-12-26 中兴通讯股份有限公司 一种ims多媒体会议接入的方法及系统
CN104093028B (zh) * 2014-06-25 2019-02-01 中兴通讯股份有限公司 一种设备能力协商的方法和装置
CN104580166B (zh) * 2014-12-19 2018-08-31 大唐移动通信设备有限公司 一种基于cscf媒体编码格式转换的方法和装置
CN108076452A (zh) * 2016-11-18 2018-05-25 大唐移动通信设备有限公司 一种通知业务能力的方法、装置和系统
CN113766435B (zh) * 2020-06-05 2023-04-07 成都鼎桥通信技术有限公司 通信群组的建立方法、设备以及存储介质
CN117729187B (zh) * 2024-02-06 2024-05-28 中兴通讯股份有限公司 通信方法、设备和计算机可读存储介质
CN119865937A (zh) * 2024-03-22 2025-04-22 中国电信股份有限公司技术创新中心 接入网关改选方法、装置、通信设备和存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1421008A (zh) * 1999-11-08 2003-05-28 Mci全球通讯公司 基于会话启动协议的特征控制
CN1627746A (zh) * 2003-12-11 2005-06-15 华为技术有限公司 一种实现多媒体优先业务的方法
CN1645812A (zh) * 2004-07-30 2005-07-27 华为技术有限公司 将终端能力变化通知给网络的方法
KR20050087938A (ko) * 2004-02-27 2005-09-01 엘지전자 주식회사 Ｓｉｐ 기반의 네트워크 접속 시스템 및 방법

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1421008A (zh) * 1999-11-08 2003-05-28 Mci全球通讯公司 基于会话启动协议的特征控制
CN1627746A (zh) * 2003-12-11 2005-06-15 华为技术有限公司 一种实现多媒体优先业务的方法
KR20050087938A (ko) * 2004-02-27 2005-09-01 엘지전자 주식회사 Ｓｉｐ 기반의 네트워크 접속 시스템 및 방법
CN1645812A (zh) * 2004-07-30 2005-07-27 华为技术有限公司 将终端能力变化通知给网络的方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102970751A (zh) * 2012-11-21 2013-03-13 华为技术有限公司 一种lte网络下完成业务协商的方法、装置及系统

Also Published As

Publication number Publication date
CN100550908C (zh) 2009-10-14
CN1984135A (zh) 2007-06-20

Similar Documents

Publication Publication Date Title
US8401005B2 (en) Session initiation protocol message content processing method and network
KR101245915B1 (ko) Ｉｍｓ 서비스를 식별하는 방법 및 장치
CN101313543B (zh) 互通功能网元、网际协议多媒体子系统结合业务csi终端与网际协议多媒体子系统ims终端互通系统及方法
EP1619854A1 (fr) Message SIP étendue pour un service utilisant des poussoirs de régarder
CN100362807C (zh) 一种实现网际协议多媒体子系统中用户注册的方法
WO2009024081A1 (fr) Procédé, dispositif et système pour traiter la continuité du flux multimédia dans une session
CN101030964B (zh) 会话控制装置和方法
CN1327680C (zh) 一种电路交换网络到ims网络呼叫路由的建立方法
CN100550908C (zh) 一种进行会话能力信息操作的方法及网络实体
WO2008000134A1 (fr) Méthode et dispositif de transmission d'un message de demande dans un système multimédia
WO2007095855A1 (fr) Procédé et entité réseau de négociation d'un paramètre de type média
CN101563903B (zh) 用于向用户提供ip多媒体子系统通信服务的方法和设备
CN101217698B (zh) 一种实现彩铃和/或彩像业务的方法
CN102484641B (zh) 用于选择网络资源的方法
WO2008080297A1 (fr) Procédé, équipement et système pour mettre en rapport une session
CN1984132B (zh) 一种对会话能力信息进行处理的方法和终端
CN100583837C (zh) 一种基于ims的业务实现方法
CN101110790A (zh) 建立会话的方法
AU2005263756A1 (en) Push to watch network element and software architecture
CN1968262B (zh) 一种ims网络中的会话控制方法和装置
RU2389148C2 (ru) Способ и устройство идентификации ims-услуги
CN101009664B (zh) 一种处理会话初始化协议消息中内容的方法及网络实体
EP1672867A1 (fr) Méthode pour le transfert rapide et fiable d'une grande quantité de données entre utilisateurs radio mobiles impliqués dans une session SIP
Husain et al. 3gpp Ims-Based Inter-Device Collaboration
WO2009079847A1 (fr) Procédé d'utilisation de doubles appels pour réaliser un service de sonnerie personnalisée

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 06828313

Country of ref document: EP

Kind code of ref document: A1