WO2011018008A1 - 一种i1接口的业务控制方法、装置和系统 - Google Patents

一种i1接口的业务控制方法、装置和系统 Download PDF

Info

Publication number
WO2011018008A1
WO2011018008A1 PCT/CN2010/075724 CN2010075724W WO2011018008A1 WO 2011018008 A1 WO2011018008 A1 WO 2011018008A1 CN 2010075724 W CN2010075724 W CN 2010075724W WO 2011018008 A1 WO2011018008 A1 WO 2011018008A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
interface
message
invite message
user equipment
Prior art date
Application number
PCT/CN2010/075724
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 EP10807953.4A priority Critical patent/EP2458781B1/en
Publication of WO2011018008A1 publication Critical patent/WO2011018008A1/zh
Priority to US13/370,843 priority patent/US8886812B2/en
Priority to US14/501,678 priority patent/US20150016308A1/en

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/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/10—Architectures or entities
    • H04L65/102—Gateways
    • H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
    • 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
    • H04L65/1094—Inter-user-equipment sessions transfer or sharing
    • 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
    • H04L65/1095—Inter-network session transfer or sharing
    • 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
    • H04M—TELEPHONIC COMMUNICATION
    • H04M3/00—Automatic or semi-automatic exchanges
    • H04M3/42—Systems providing special services or facilities to subscribers
    • H04M3/42025—Calling or Called party identification service
    • H04M3/42034—Calling party identification service
    • H04M3/42059—Making use of the calling party identifier
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a service control method, apparatus, and system for an II interface. Background technique
  • IMS Centralized Services supports the use of Circuit Switched (CS) access to carry media streams for Internet Protocol Multimedia Subsystem (IMS) services, service aggregation and session continuity ( Service Centralization and Continuity (SCC) Application Server (AS) is an application server that supports ICS. It is used by the User Equipment (UE) to perform IMS session control in the IMS domain, for example, triggering at the UE. The IMS session is initiated.
  • CS Circuit Switched
  • IMS Internet Protocol Multimedia Subsystem
  • SCC Service Centralization and Continuity
  • AS Application Server
  • the ICS project has completed the standardization of the architecture, and the ongoing standardization of the protocol involves the development of a new protocol, the ICS Control Protocol (or II Protocol).
  • the II protocol is an application protocol on the II interface.
  • the II interface is a new interface introduced by the ICS project. It is located between the UE and the SCC AS and is used for IMS service control signaling.
  • the II interface is based on CS access.
  • the application protocol message of the II interface is transmitted through Unstructured Supplementary Service Data (USSD) or Short Message Service (SMS).
  • USSD Unstructured Supplementary Service Data
  • SMS Short Message Service
  • the II protocol can learn from most concepts or terms of the SIP protocol. In order to distinguish, it is generally preceded by the concept or terminology of the SIP protocol.
  • the II prefix indicates the concept or term of the II protocol.
  • the II protocol acts as an IMS session control protocol, and its traffic (ie, the overhead of II protocol messaging) is large. Due to current USSD or SMS Various applications or value-added services have been developed, and the II protocol uses USSD or SMS as the transmission protocol, which will cause a large traffic impact on USSD or SMS. Therefore, the subject requires the message overhead of the II protocol design to be as low as possible. Summary of the invention
  • the technical problem to be solved by the embodiment of the present invention is to provide a II interface service control method, device and system
  • the embodiment of the service control method of the II interface provided by the present invention can be implemented by the following technical solutions:
  • the Gm interface controls the information that is rolled back to the II interface control and the information used to associate the session initiation protocol invitation message.
  • the embodiment of the invention further provides a service control method for the II interface, including:
  • the II invite message carries a service control handover request indication of the Internet Protocol multimedia subsystem session and a session initiation protocol session identifier
  • the embodiment of the present invention further provides a service aggregation and session continuity application server, including: a session initiation protocol invitation sending unit, configured to send a session initiation protocol invitation message to a user equipment through a Gm interface;
  • a response message receiving unit configured to receive a response message returned by the user equipment, where the response message indicates that the user equipment selects to use a circuit domain bearer and uses an II interface control;
  • the II invite message sending unit is configured to: if the response message receiving unit receives the response message, send an II invite message to the user equipment by using the II interface, where the II invite message carries the indication Gm connection
  • the port controls the information that is rolled back to the II interface control and the information used to associate the session initiation protocol invite message.
  • the embodiment of the invention further provides a service concentration and session continuity application server, including
  • a requesting receiving unit configured to receive an II invite message sent by the user equipment, where the II invite message carries a service control switching request indication of the Internet Protocol multimedia subsystem session and a session initialization protocol session identifier;
  • a session search unit configured to search for an Internet Protocol multimedia subsystem session by using the session initiation protocol dialog identifier
  • a handover success message sending unit configured to send, to the user equipment, a message indicating that the service control handover is successful.
  • the embodiment of the invention further provides a user equipment, including:
  • An invitation message receiving unit configured to receive, by using a Gm interface, a session initiation protocol invite message from a service set and a session continuity application server;
  • the response message sending unit is configured to: after receiving the session initiation protocol invitation message, send a response message, where the response message indicates that the user equipment selects to use the circuit domain bearer and use the II interface control;
  • the II invite receiving unit is configured to receive the II invite message through the II interface
  • the II invite parsing unit is configured to parse the II invite message to obtain an indication that the Gm interface controls information that is rolled back to the II interface control and information used to associate the session initiation protocol invite message.
  • the embodiment of the invention further provides a user equipment, including:
  • An invitation sending unit configured to send a II invitation message to the service set and the session continuity application server, where the II invite message carries a service control switching request indication of the Internet Protocol multimedia subsystem session and a session initialization protocol session identifier;
  • the handover success message receiving unit is configured to receive a message indicating that the service control handover is successful.
  • the embodiment of the invention further provides an II interface service control system, including:
  • the service concentration and session continuity application server includes:
  • a session initiation protocol invitation sending unit configured to send a session initiation protocol invitation message to the user equipment through the Gm interface
  • a response message receiving unit configured to receive a response message returned by the user equipment, where the response message indicates that the user equipment selects to use a circuit domain bearer and uses an II interface control;
  • the II invite message sending unit is configured to: if the response message receiving unit receives the response message, send an II invite message to the user equipment by using the II interface, where the II invite message carries the indication Gm interface control to fall back to the II interface control Information and information for associating the session initiation protocol invitation message;
  • the user equipment includes:
  • An invitation message receiving unit configured to receive a session initiation protocol invitation message from the service set and the session continuity application server through the Gm interface;
  • the response message sending unit is configured to: after receiving the session initiation protocol invitation message, send a response message, where the response message indicates that the user equipment selects to use the circuit domain bearer and use the II interface control;
  • the II invite receiving unit is configured to receive the II invite message through the II interface
  • the II invite parsing unit is configured to parse the II invite message to obtain an indication that the Gm interface controls information that is rolled back to the II interface control and information used to associate the session initiation protocol invite message.
  • the embodiment of the invention further provides another II interface service control system, including:
  • the service concentration and session continuity application server includes:
  • a requesting receiving unit configured to receive an II invite message sent by the user equipment, where the II invite message carries a service control switching request indication of the Internet Protocol multimedia subsystem session and a session initialization protocol session identifier;
  • a session search unit configured to search for an Internet Protocol multimedia subsystem session by using the session initiation protocol dialog identifier
  • a handover success message sending unit configured to send, to the user equipment, a message indicating that the service control handover is successful;
  • the user equipment includes:
  • An invitation sending unit configured to send an II invite message to the service set and the session continuity application server, where the II invite message carries a service control switch request indication of the Internet Protocol multimedia subsystem session and a session initialization protocol session identifier;
  • the handover success message receiving unit is configured to receive a message indicating that the service control handover is successful.
  • FIG. 1 is a schematic flowchart of a method for calling a ICS UE according to an embodiment of the present invention
  • FIG. 2 is a schematic flowchart of a method for calling an ICS UE according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of a method for Gm fallback according to an embodiment of the present invention.
  • FIG. 4 is a schematic flowchart of a method for Gm switching according to Embodiment 2 of the present invention.
  • FIG. 5 is a schematic flowchart of a method for adding an II interface according to Embodiment 3 of the present invention.
  • FIG. 6 is a schematic structural diagram of a service aggregation and session continuity application server according to Embodiment 4 of the present invention
  • FIG. 7 is a schematic structural diagram of a service aggregation and session continuity application server according to Embodiment 4 of the present invention
  • FIG. 8 is a service aggregation and session according to Embodiment 5 of the present invention
  • FIG. 9 is a schematic structural diagram of a service aggregation and a session continuity application server according to Embodiment 6 of the present invention
  • FIG. 10 is a schematic structural diagram of a user equipment according to Embodiment 7 of the present invention
  • FIG. 11 is a schematic structural diagram of a service control system of an II interface according to Embodiment 8 of the present invention.
  • FIG. 12 is a schematic structural diagram of a service control system of an II interface according to Embodiment 9 of the present invention.
  • FIG. 13 is a schematic structural diagram of a service control system of a tenth interface according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of a service control system of an II interface of an embodiment of the present invention.
  • 15 is a schematic structural diagram of a user equipment according to an embodiment of the present invention
  • 16 is a schematic structural diagram of a user equipment according to an embodiment of the present invention
  • FIG. 17 is a schematic structural diagram of a user equipment according to Embodiment 13 of the present invention.
  • FIG. 18 is a schematic structural diagram of a user equipment according to Embodiment 13 of the present invention. detailed description
  • Embodiments of the present invention primarily relate to reducing message overhead from the perspective of "reduce information transfer.”
  • the overhead optimization design in the II protocol scheme of the calling and called scenarios mainly includes:
  • the 11 protocol does not include the Via function, the Record-route header function, the Route header function, etc. in the SIP protocol;
  • SDP Session Description Protocol
  • Invite contains the calling user ID and the called user ID of the IMS session.
  • the subsequent response or request does not need to include the calling user ID and the called user ID.
  • the subsequent response or request is by call number (Cal- ID), from the tag (From tag ) to the tag ( To tag ) combined to associate the IMS session.
  • ICS UE A initiates an IMS session through the II interface, and the SCC AS assigns a Public Service Identity Directory Numbe (PSI DN) for the UE to initiate a CS domain call to establish a CS bearer.
  • PSI DN Public Service Identity Directory Numbe
  • the CS bearer is used to transmit the IMS session media stream
  • the SCC AS receives the CS domain Mobile Switching Centre (MSC) server or the Media Gateway Control Function (MGCF).
  • MSC Mobile Switching Centre
  • MGCF Media Gateway Control Function
  • Step 101 The ICS UE A sends an II Invite message through the II interface to initiate an IMS session, and the information includes:
  • call-ID used to identify the current IMS session or call on the II interface, for example, set to: 2037701k s;
  • II 1" 011 header (From header), the value of the header field is used to indicate the calling user ID of this session, t ⁇ , set to user-a@example.com, From header also includes ⁇ "label ( tag, tag is used in combination with the II call identity to identify the current IMS session or call identity on the II interface. In order to reduce the message overhead, the tag may not be set/passed, for example, set to a2ci;
  • the value of the header field indicates the called user ID of the session, for example, set to user_b@example.com;
  • the II command sequence number (Cseq, Command Sequence), used to indicate the order of the II command (or II request, II method).
  • UE A When UE A generates the II Inivte request, randomly select a value as the CSeq value, such as 1688. When the subsequent UE A sends another II request, the CSeq will continue to increment by 1.
  • the CSeq also includes a method information indicating the II invitation. The response sent by the SCC AS to the II invitation will copy the CSeq for UE A to perform II. The match between the request and the II response.
  • the II command may be II Inivte, or may be another command (or request, method) message sent through the II interface, which is not limited in this embodiment of the present invention.
  • Step 102 After receiving the II Inivte, the SCC AS saves the Call-ID, the From header, the To header, and the command sequence number (the SCC AS also generates and maintains its own command sequence number when the II sends the II request), and sends the response II session progress through the II interface.
  • the message, the information contained are:
  • SDP session description protocol
  • the PSI DN is associated with the SCC AS, for example, the PSI DN is set to +12125556666;
  • the CS call can be sent to the SCC AS using the PSI DN.
  • step 103 to step 104 the ICS UE A initiates a CS domain call with the PSI DN as the called number, and the CS domain MSC server or the MGCF (Media Gateway Control Function) performs CS signaling and SIP conversion to generate a SIP Invite. (including the PSI DN), the SIP Invite finally reaches the SCC AS, and the SCC AS uses the PSI DN to associate the saved II Invite information.
  • the PSI DN the PSI DN
  • the SIP Invite finally reaches the SCC AS, and the SCC AS uses the PSI DN to associate the saved II Invite information.
  • UE A may send other II requests. For example, when the II Update request is made, CSeq: 1689 Update should be set.
  • Steps 105 to 106 The SCC AS generates SIP Invite (including the called subscriber identity and the CS bearer information, and the CS bearer information is used for the UE B to perform the media stream transmission), the SIP Invite finally reaches the UE B, and the UE B user picks up the phone and accepts the IMS. In the session invitation, UE B sends a success message (200 OK) indicating that the user has picked up the phone.
  • SIP Invite including the called subscriber identity and the CS bearer information, and the CS bearer information is used for the UE B to perform the media stream transmission
  • the SIP Invite finally reaches the UE B, and the UE B user picks up the phone and accepts the IMS.
  • UE B sends a success message (200 OK) indicating that the user has picked up the phone.
  • Steps 107 to 108 The SCC AS sends a 200 OK to the MSC server or the MGCF to indicate that the CS call is successfully established, and the MSC Server sends a connect message to the UE A to indicate that the CS call is successfully established.
  • Step 109 The SCC AS sends an II 200 OK response through the II interface, indicating that the IMS session is successfully established.
  • the header field portion of the II 200 OK is the same as the II session progress message, and the SDP portion no longer contains the PSI DN.
  • Step 110 The SCC AS sends a SIP ACK request to the UE B, for performing (receiving) confirmation on the 200 OK.
  • the SCC AS does not have to wait for UE A to acknowledge the reception of the II 200 OK, it can use the reliable transmission capability of the underlying transport layer protocol (such as USSD or SMS).
  • the SCC AS sends an IMS session invitation through the II interface, including the PSI DN, for the UE to initiate a CS domain call to establish a CS bearer (for transmitting the IMS session media stream).
  • the specific process is shown in Figure 2:
  • Step 201 The SCC AS receives the SIP Invite message, including the calling user identifier (for example, set to user-b@example.com) and the called user label "i only" (t ⁇ , set to user-a@example .com ).
  • Step 202 The SCC AS sends the II Invite message to the ICS UE A through the II interface, and the included information Yes (SCC AS also saves this information):
  • Call ID used to identify the current IMS session or call on the II interface, for example, set to 9t3j 9xsdfw9tg374js7usj v;
  • header the value of the header field is used to indicate the calling user ID of this session, t ⁇ , set to user-b@example.com, From header also contains ⁇ "labels ( Tag ), t ⁇ , set to kg48;
  • the value of the header field indicates the called user ID of the session, for example, set to user_a@example.com;
  • CSeq Command Sequence
  • SDP session description protocol
  • CS bearer or CS connection
  • Step 203 After receiving the II Inivte, the ICS UE saves the II Call-ID, II From header, II To header, and II command sequence number, and sends a response II session progress through the II interface, and the information included is:
  • Step 204 ⁇ Step 207 establish a CS bearer.
  • the ICS UE A initiates a CS domain call with the PSI DN as the called number, and the CS domain MSC server or the MGCF performs CS signaling and SIP conversion to generate a SIP Invite (including the PSI DN), and the SIP Invite finally reaches the SCC AS, and the SCC AS uses The PSI DN is associated with the saved II Invite related information.
  • the SCC AS sends a final response 200 OK to the MSC server or MGCF (indicating that the call is successfully established), and the MSC server or MGCF performs the 200 OK reception confirmation with the ACK.
  • the MSC server sends a connect indication to UE A that the CS call is successfully established.
  • Step 208 to step 210 UE A sends an II 200 OK response through the II interface, indicating that the IMS session is successfully established.
  • the header field of the II 200 OK is the same as the session of the II session.
  • the SCC AS sends a SIP 200 OK to the UE B, indicating that the user of the UE A has gone off-hook and the IMS session is successfully established.
  • UE B sends a SIPACK request to the SCC AS for a (receive) acknowledgement of the 200 OK.
  • the II interface includes three scenarios: Gm interface fallback to II interface, Gm switch to II interface, and II interface. The optimization design mentioned above can be used in these three scenarios. .
  • the following describes the optimization design of the II interface service control in the scenario where the Gm interface is fallback to the II interface, Gm is switched to the II interface, and the II interface is added.
  • the first embodiment of the present invention provides an II interface service control method in a Gm fallback scenario.
  • the SCC AS-end process may include: sending a SIP session initiation protocol invite message to the ICS UE through the Gm interface. If the response message returned by the user equipment is received, the response message indicates that the user equipment selects to use the circuit domain bearer and uses the II interface control, and then sends an II invite message to the user equipment through the II interface, where the II invitation message is included. Instructing the Gm interface (service) to control the information that is rolled back to the II interface (service) control and the information used to associate the SIP invite. Preferably, the above two information are included in the replacement header field, optionally, the II invite message uses SIP.
  • the call identity and tag of the conversation are used as the II interface call identifier and the II interface tag, and the SIP dialog is triggered by the previous SIP Invite. Note: For simplicity, the II interface tag can be omitted;
  • the SCC AS can omit the calling and called user IDs when the call request (ie, II Invite) is sent again on the II interface. Privacy can be omitted, and for the UE to be able to associate the II call request with the previous SIP Invite, the SCC AS should contain associated information, such as using a replace header containing the SIP dialog call identifier and tag (the tag is optional) Including), further, the default SIP dialog call identifier and tag are respectively used as II call identifier and II tag, then the SCC AS does not have to include a new II call identifier and II tag in II Invite (II tag includes II From tag and II To Tag ). This has two aspects of optimization: omission of the calling and called user IDs (the UE uses the SIP dialog call identifier and tag associated with the saved calling and called user IDs), omitting the generation of the new II call identifier and II tag operating.
  • the SCC AS may first send the SIP Invite to the UE A through the Gm interface, and the SDP information in the Invite includes the packet switching media (PS media ) information and the CS media information of the circuit switched medium, and the CS media information indication.
  • PS media packet switching media
  • UE A can select CS bearer, and CS media information can also contain PSI DN.
  • UE A decides to use the CS bearer to transmit the session media stream and use the II interface for service control, returning the SIP session progress (SIP 183) response (indicating the use of CS bearer)
  • II interface control ⁇ SCC AS, SCC AS sends a call request to UE A through the II interface, establishes an IMS session, and releases the SIP dialog (dialog X).
  • Step 301 The SCC AS receives a SIP Invite message, including a calling user identifier (for example, set to user-b@example.com) And the called user is only marked (t ⁇ , set to user-a@example.com).
  • a calling user identifier for example, set to user-b@example.com
  • t ⁇ set to user-a@example.com
  • Step 302 The SCC AS sends a SIP Invite message to the ICS UE A through the Gm interface to initiate an IMS session, and the information included (the SCC AS also saves the information):
  • Call ID used to identify this IMS session or call, for example, set to I93j9xsKKIg374js7u8JY;
  • the value of the header field is used to indicate the caller ID of the session, t ⁇ , set to user-b@example.com, and the header is also included ⁇ tag(tag) , t ⁇ port, set to 094P;
  • the value of the header field indicates the called user ID of the session, for example, set to user_a@example.com;
  • Command sequence number (CSeq, Command Sequence), for example, set to CSeq: 891 Invite;
  • SDP session description protocol
  • PS media information indicates that UE A can select CS bearer
  • CS media information can also include PSI DN, for example, set to +12125556886.
  • Step 303 After receiving the SIP Inivte, the ICS UE A saves the Call-ID, the From header, the To header, and the command sequence number. UE A decides to use CS bearer to transmit the session media stream, and returns the response to the SCC AS through the Gm interface (returning the response will generate a SIP dialog, SIP dialog is an attribute of the SIP protocol for subsequent SIP message communication), such as 183 (session progress sessin) Progress ), contains information:
  • Step 304 The SCC AS sends the II Invite (excluding the II Call-ID header, the II From header, and the II To header) to the UE A through the II interface, and the information included is:
  • the header field indicates that the II Invite replaces the previous SIP Invite, and the header field contains SIP Dialog call identification information and tag information;
  • the command sequence number (CSeq, Command Sequence), for example, is set to CSeq: 891 Invite.
  • Steps 305, 108 11 £ Receive 11 11 ⁇ identify the Gm interface back to the II interface through the II Replace header, and find the saved SIP dialog information (calling, called user identifier, etc.) according to the II Replace header information.
  • the UE uses the SIP dialog call identifier and the tag as the II call identifier and the II tag to perform a normal II interface called session establishment process (this process can refer to the procedure of the ICS UE called).
  • 13 ⁇ 4 or 8 ( ⁇ : eight 8 can be initiated (3 ⁇ 4 interface 81? ⁇ 1 (3 ⁇ 4 release.
  • Embodiment 2 of the present invention provides a service control method for an II interface in a Gm interface control handover scenario.
  • the execution process may include: receiving a service of a service centralized in the Internet Protocol multimedia subsystem.
  • the II invite message sent by the device, the replacement header field of the II invite message includes a service control handover request indication and a session initiation protocol session ID; the IMS session is searched by the session initiation protocol session ID; and the II success message indication is sent to the user equipment to the II The interface control was successfully switched.
  • the II interface call identifier of the above II invite message is the session identifier of the session initiation protocol session.
  • the service control instead of the Gm interface is indicated by using the II Invite request to include a replace header (the replace header carries the Gm interface SIP dialog ID).
  • the II call identifier and the II tag can reuse the call identifier and tag of the SIP dialog ID, so that II Invite can omit the delivery of the II Call-ID header, the II From header, and the II To header.
  • the SCC AS After receiving the service control switch request, the SCC AS returns to the II 200 OK, indicating that the service control switch is successful. Subsequent UEs can perform service control through the II interface. This has two aspects of optimization: omitting the calling and called user identities (the SCC AS associates the IMS session with the IMS session, the calling and called user identities), omitting the operation of generating the new II call id and the II tag.
  • Step 401 UE A sends an II Invite message (excluding II Call-ID header, II From header, and II To header, default and SIP) Consistent in the dialog) to the SCC AS, the information contained is:
  • the header field indicates a service control switch request
  • the header field contains a dialog of a SIP dialog
  • Step 402 The SCC AS finds a SIP dialog by using the replace header information (the SIP dialog is used to control the IMS session), and identifies that the IMS session has used the CS bearer to transmit the media stream, and the SCC AS responds to the UE A with the II 200 OK, indicating that the service control is successfully switched. If the IMS session currently uses the PS domain to transport media streams, you need to create a new CS bearer.
  • the SIP conversation call identifier and tag are used as the II call identifier and II tag, respectively. Subsequent UEs can perform service control through the II interface.
  • the UE or SCC AS can initiate a SIP dialog release.
  • Embodiment 3 of the present invention provides a service control method for an II interface in an II interface service control scenario.
  • the execution process may include: receiving a service centralized in the multimedia protocol of the Internet Protocol
  • the II invitation sent by the user equipment includes a session transfer identifier (STI) indicating to increase the II interface service control (which may be referred to as an add-on II interface), and the STI may serve as a request for a Uniform Resource Identifier (Request URI) or The value of the To header;
  • the SCC AS obtains the CS domain number of the above-mentioned user equipment through the underlying transport layer (such as Mobile Station Integrated Service Digital Network Number (MSISDN, Mobile Station ISDN), MDN (Mobile Directory Number, Mobile Directory Number) And then searching for the Internet Protocol Multimedia Subsystem session through the CS domain number, or searching for the Internet Protocol Multimedia Subsystem session through the STI; sending the II invitation Success message to the user equipment to indicate that the II interface is successfully added.
  • MSISDN Mobile Station Integrated Service Digital
  • the execution scenario of the foregoing process may be: UE A determines to add the II interface to maintain the current IMS session, and establishes a second session.
  • the II invitation further includes: maintaining the indication information of the current Internet Protocol multimedia subsystem session.
  • the SCC AS sends a new IMS session through the II interface (in the normal called flow) and UE A needs to keep the first session and connect to the second session (new IMS session), then the above received Internet protocol Before the II invitation sent by the user equipment of the service in the multimedia subsystem, the SCC AS sends an II invitation to the user equipment to initiate a new Internet Protocol multimedia subsystem session.
  • the SCC AS initiates the increase of the II interface service control, and the SCC AS increases the II interface service control by using the II invite (without the calling party and the called user identifier).
  • the specific scenario may be that the peer adds or deletes the video, or has other The information to the UE needs to be sent; from the perspective of the ICS UE, the execution process may include:
  • Receiving the II invitation sent by the service concentration and the session continuity application server, and the above II invitation includes a session transfer identifier (STI) indication to increase the II interface service control (
  • the cartridge is called the Add II interface.
  • the STI can be used as the value of the Request Uniform Resource Provider (Request URI) or To Header.
  • the SCC AS may send the II Invite (excluding the calling and called user identifiers) to the STI, which includes the STI to indicate to the UE that the II interface service control is increased, the II call identifier and
  • the creation of the II tag can take the form of the normal II interface called process.
  • the current UE has only one IMS session, so the UE can naturally associate with the IMS session.
  • the above technical solution solves three technical problems in the case that the UE A adds the II interface service control, one is the representation of the II interface service control increase request, the other is the II call identity and the II tag establishment, and the other is the SCC AS. How to associate an IMS session.
  • the II Invite request can be used to include the STI (session transfer identifier, the prior art is used to perform access transfer access, such as transferring the media stream from the CS domain to the PS domain) to indicate the II interface service control addition request.
  • the creation of the II call identity and the II tag can capture the way in the normal II interface call process.
  • the SCC AS association IMS session may use STI (if it can uniquely identify UE A), or the CS domain UE number (such as MSISDN, MDN (Moblie Directory Number)) reported by the SCC AS through the underlying transport layer.
  • STI if it can uniquely identify UE A
  • CS domain UE number such as MSISDN, MDN (Moblie Directory Number)
  • MSISDN MSISDN
  • MDN Moblie Directory Number
  • the process of adding the II interface service control by the UE may include the following steps: Step 501: UE A sends an II Invite message to the SCC AS, and the information included is:
  • STI as the value of the Uniform Resource Identifier (URI) header or the To header, indicating that the II interface service control is added;
  • URI Uniform Resource Identifier
  • CSeq Command Sequence Number
  • Step 502 The SCC AS obtains the CS domain number (such as MSISDN, MDN) of the UE A through the underlying transport layer, and then finds the IMS session through the CS domain number, or searches for the IMS session through the STI, 8 ( ⁇ : 8 8 to 11 200 01 1 corresponds to (including 1&8) 1; £8, indicating that the II interface is added successfully.
  • the CS domain number such as MSISDN, MDN
  • Embodiment 4 As shown in FIG. 6, the embodiment of the present invention further provides a service concentration and session continuity application server, including: a session initiation protocol invitation sending unit 601, configured to send a session initiation protocol invite message to the user equipment through the Gm interface;
  • a session initiation protocol invitation sending unit 601 configured to send a session initiation protocol invite message to the user equipment through the Gm interface;
  • the response message receiving unit 602 is configured to receive a response message returned by the user equipment, where the response message indicates that the user equipment selects to use the circuit domain bearer and use the II interface control;
  • the II invite message sending unit 603 is configured to send the II invite message to the user equipment by using the II interface, where the II invite message carries the Gm interface control to fall back to the II interface control. Information and information used to associate the above Session Initiation Protocol Invite message.
  • the service concentration and session continuity application server further includes: an identifier setting unit 701, configured to set a call of the II interface call identifier of the II invite message to the session initiation protocol invitation message. logo.
  • the replacement header field that uses the II invite message carries the information indicating that the Gm interface controls the fallback to the II interface control and the information used to associate the session initiation protocol invite message, omitting the calling and called user identifiers, and
  • the call ID of the dialog using the session initiation protocol invite message described above can be omitted as the II interface call identifier.
  • Embodiment 5 As shown in FIG. 8, the embodiment of the present invention further provides a service concentration and session continuity application server, including
  • the II invite receiving unit 801 is configured to receive an II invite message sent by the user equipment, where the II invite message carries a service control handover request indication and a session identifier of the session initiation protocol session;
  • a session search unit 802 configured to search for a session initialization protocol session by using the session identifier of the session initiation protocol session;
  • the handover success message sending unit 803 is configured to send a message indicating that the service control handover is successful to the user equipment.
  • the II interface call identifier of the II invite message received by the II receiving unit 801 is the call identifier of the session initiation protocol session.
  • the II invite message carries the service control handover request indication and the session identifier of the session initiation protocol session, and the calling and called user identifiers may be omitted, and the call identifier of the conversation by using the session initiation protocol invitation message is used as the II interface.
  • the call identifier can omit the II dialog ID. Reduce the overhead of II protocol messages.
  • Embodiment 6 As shown in FIG. 9, an embodiment of the present invention further provides a service concentration and session continuity application server, including:
  • the II invite receiving unit 901 is configured to receive an II invite message sent by the user equipment, where the II invite message carries an IMS session add II interface indication; the foregoing Internet Protocol multimedia subsystem session adds an II interface indication, by unifying the request of the II invite message
  • the value of the resource identifier or the value of the header is set to be carried by the session transfer identifier; or, carried by the public service identity directory number included in the II invite message, the public service identity directory number being the Internet Protocol multimedia sub- The number of the other party to the system session;
  • the session search unit 902 is configured to search for an Internet Protocol multimedia subsystem session by using the session transfer identifier or the public service identity directory number; or, the session search unit 902 is configured to obtain the circuit domain number of the user equipment by using the underlying transport layer, and then Finding an Internet Protocol Multimedia Subsystem session through the above circuit domain number;
  • the request success message sending unit 903 is configured to send a message indicating that the II interface is successfully added to the user equipment.
  • the II interface indication is added by using the II invite message to carry the IMS session, and the calling and called user identifiers are omitted. Reduce the overhead of II protocol messages.
  • an embodiment of the present invention further provides a user equipment, including:
  • the II invite receiving unit 1001 is configured to receive the II invite message sent by the service set and the session continuity application server, where the II invite message carries information indicating that the IMS session increases the II interface service control;
  • the II interface service control establishing unit 1002 is configured to establish II interface service control, and associate the foregoing II interface service control with the foregoing IMS session.
  • the II interface indication is added by using the II invite message to carry the IMS session, and the calling and called user identifiers are omitted. Reduce the overhead of II protocol messages.
  • an embodiment of the present invention further provides an II interface service control system, including:
  • the service concentrating and session continuity application server 1101 is configured to send a session initiation protocol invitation message to the user equipment 1102 through the Gm interface. If the response message returned by the user equipment 1102 is received, the response message indicates that the user equipment selects to use the circuit domain. Carrying and using the II interface control, the II invitation message is sent to the user equipment 1102 through the II interface, and the above II invitation message is carried. Instructing the Gm interface to control information that is rolled back to the II interface control and information used to associate the session initiation protocol invite message;
  • the user equipment 1102 is configured to send a response message to the service aggregation and session continuity application server 1101 after receiving the session initiation protocol invitation message, where the response message indicates that the user equipment 1102 selects to use the circuit domain bearer and uses the II interface control;
  • the invite message parses the above II invite message to obtain information indicating that the Gm interface controls fallback to the II interface control and information for associating the above session initiation protocol invite message.
  • the 11 interface call identifier of the foregoing II invitation message sent by the service aggregation and session continuity application server 1101 is a call identifier of the session of the session initiation protocol invitation message;
  • the user equipment 1102 is further configured to perform the II interface called session establishment process by using the call identifier of the session initiation protocol invitation message generating session as the II interface call identifier.
  • the calling and called user identifiers may be omitted, and the above session is used.
  • the call identity of the dialog that initializes the protocol invite message can be omitted as the II interface call identifier. Reduce the overhead of II protocol messages.
  • an embodiment of the present invention further provides a service control system for an II interface, which is characterized in that:
  • the service concentrating and session continuity application server 1201 is configured to receive an II invitation message sent by the user equipment 1202, where the II invitation message carries a service control handover request indication and a call identifier of a session initiation protocol session; Searching for an Internet Protocol Multimedia Subsystem session; transmitting a message indicating that the service control handover is successful to the user equipment 1202; the user equipment 1202, configured to send an II invite message to the service aggregation and session continuity application server 1201; The service control is successfully switched.
  • the II interface call identifier of the foregoing II invite message sent by the user equipment 1202 is a call identifier of the session initiation protocol session.
  • the service aggregation and session continuity application server 1201 configured to receive the II invitation message sent by the user equipment, includes: receiving the II invitation message sent by the user equipment, where the II interface call identifier is the session identifier of the session initiation protocol session, and performing the II interface.
  • the calling session establishment process includes: receiving the II invitation message sent by the user equipment, where the II interface call identifier is the session identifier of the session initiation protocol session, and performing the II interface.
  • the above embodiment by using the II invite message to carry the indication of the service control request and the initial session
  • the session identifier of the protocol session may be initialized, and the calling and called user identifiers may be omitted.
  • the II dialog ID may be omitted by using the call identifier of the session of the session initiation protocol invitation message as the II interface call identifier. Reduce the overhead of II protocol messages.
  • an embodiment of the present invention provides a service control system for an II interface, including:
  • the service concentrating and session continuity application server 1301 is configured to receive the II invite message sent by the user equipment 1302, where the II invite message carries an IMS session add II interface indication; the foregoing Internet Protocol multimedia subsystem session adds an II interface indication, by using the foregoing II
  • the value of the requesting uniform resource identifier of the invitation message or the value of the header is set to be carried by the session transfer identifier, or carried by the public service identity directory number included in the II invite message, where the public service identity directory number is The number of the other party of the Internet Protocol Multimedia Subsystem session; searching for an Internet Protocol Multimedia Subsystem session by the Session Transfer Identifier or the Public Service Identity Directory Number, or obtaining the circuit domain number of the above user equipment 1302 through the underlying transport layer and passing the circuit domain number Finding an Internet Protocol Multimedia Subsystem session; sending a message to the user equipment 130 indicating that the II interface is successfully added;
  • the user equipment 1302 is configured to send an II invitation to the service concentration and session continuity application server 1301; and receive the II success message to learn that the II interface is successfully added.
  • the calling and called user identifiers may be omitted by using the II invite message to carry the IMS session to add the II interface indication. Reduce the overhead of II protocol messages.
  • Embodiment 11 As shown in FIG. 14, an embodiment of the present invention provides a service control system for an II interface, including:
  • the user equipment 1402 is configured to receive the II invite message sent by the service concentration and the session continuity application server 1401, where the II invite message indicates that the IMS session adds the information of the II interface service control; the II interface service control is established, and the II interface service control is associated with the The above IMS session;
  • the service centralization and session continuity application server 1401 is configured to send an II invite message to the user equipment 1402, where the II invite message indicates that the IMS session adds information of the II interface service control.
  • the calling and called user identifiers may be omitted by using the II invite message to carry the IMS session to add the II interface indication. Reduce the overhead of II protocol messages.
  • an embodiment of the present invention provides a user equipment, including: an invitation message receiving unit 1501, configured to receive, by a Gm interface, a service aggregation and a session continuity. a session initiation protocol invitation message of the application server; the session initiation protocol invitation message carries a response message using the circuit domain bearer and the indication controlled by the II interface;
  • the response message sending unit 1502 is configured to: after receiving the session initiation protocol invite message, send a response message carrying an indication that uses the circuit domain bearer and uses the II interface control;
  • the II invite receiving unit 1503 is configured to receive the II invite message through the II interface
  • the II invitation parsing unit 1504 is configured to parse the foregoing II invite message to obtain information indicating that the Gm interface controls to fall back to the II interface control and information for associating the session initiation protocol invite message;
  • the II interface call identifier of the above II invite message is the call identifier of the session initiation protocol invitation message generation dialog
  • the session establishing unit 1601 is configured to perform the interface called session establishment process by using the call identifier of the session of the session initiation protocol invitation message as the 11 interface call identifier.
  • Embodiment 13 As shown in FIG. 17, the embodiment of the present invention further provides a user equipment, including: an II invitation sending unit 1701, configured to send an II invite message to a service set and a session continuity application server, where the II invite The message carries a service control handover request indication of the Internet Protocol Multimedia Subsystem session and a session initialization protocol session identifier;
  • an II invitation sending unit 1701 configured to send an II invite message to a service set and a session continuity application server, where the II invite The message carries a service control handover request indication of the Internet Protocol Multimedia Subsystem session and a session initialization protocol session identifier;
  • the handover success message receiving unit 1702 is configured to receive a message indicating that the service control handover is successful. Further, as shown in FIG. 18, the above-mentioned II request sending unit 1601 includes:
  • the identifier setting unit 1801 is configured to set the II interface call identifier of the above II invite message to the call identifier of the above-mentioned session initializing ten-conference dialog.
  • the above user equipment and service concentration and session continuity application servers can be used for service control of the II interface.
  • the related hardware can be instructed by a program, and the program can be stored in a computer readable storage medium.
  • the above mentioned storage medium can be a read only memory, a magnetic disk or an optical disk.

Landscapes

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

Description

一种 II接口的业务控制方法、 装置和系统
本申请要求于 2009 年 8 月 12 日提交中国专利局、 申请号为 200910165624.8、 发明名称为"一种 II接口的业务控制方法、 装置和系统"的 中国专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及通信技术领域， 特别涉及一种 II接口的业务控制方法、装置 和系统。 背景技术
IMS 集中的服务（IMS Centralized Services, ICS ) 支持使用电路交换 ( Circuit Switched, CS )接入来承载媒体流以实现因特网协议多媒体子系统 ( Internet Multimedia Subsystem, IMS )业务，业务集中和会话连续性（ Service Centralization and Continuity, SCC )应用月良务器 ( Application Server, AS ) 是支持 ICS的应用服务器，用于代理用户设备 ( User Equipment, UE )在 IMS 域进行 IMS会话控制， 比如， 在 UE的触发下发起 IMS会话。
ICS课题已经完成了架构的标准化， 正在进行的协议实现标准化涉及制 定一个新的协议 ( protocol ), 即 ICS控制协议 (或称 II协议）。 II协议是 II 接口上的一个应用协议， II接口是 ICS课题引人的一个新接口 , 位于 UE和 SCC AS之间， 用于 IMS业务控制信令传递。 II接口基于 CS接入， 比如 II 接口的应用协议消息通过非结构化补充业务数据 （ Unstructured Supplementary Service Data, USSD )或者短消息( Short Message Service, SMS ) 进行传递。
考虑到 ICS中 SCC AS要进行 II协议和会话初始化协议（ Session Initiation Protocol, SIP ) 的互通操作， II协议可以借鉴 SIP协议的多数概念或术语， 为了区分， 一般在 SIP协议的概念或术语前带 II前缀表示 II协议的概念或 术语。
因为 IMS会话的数量很大， II协议作为一个 IMS会话控制协议， 其业 务量（即 II协议消息传递的开销）是很大的。 由于当前基于 USSD或 SMS 已经开展了各种应用或增值业务， 而 II协议釆用 USSD或 SMS作为传输协 议， 将会对 USSD或 SMS造成很大的业务量冲击。 因此课题要求 II协议设 计时消息开销要尽量低。 发明内容
本发明实施例要解决的技术问题是提供一种 II接口业务控制方法、装置和 系统
为解决上述技术问题，本发明所提供的 II接口的业务控制方法实施例可以 通过以下技术方案实现：
通过 Gm接口向用户设备发送会话初始化协议邀请消息；
若接收到所述用户设备返回的响应消息 , 所述响应消息指示了所述用户 设备选择使用电路域承载和使用 II接口控制；
则通过 II接口向所述用户设备发送 II邀请消息， 所述 II邀请消息携带指示
Gm接口控制回退到 II接口控制的信息和用于关联所述会话初始化协议邀请消 息的信息。 本发明实施例还提供了一种 II接口的业务控制方法， 包括：
接收用户设备发送的 II邀请消息，所述 II邀请消息携带因特网协议多媒体 子系统会话的业务控制切换请求指示以及会话初始化协议对话标识；
通过所述会话初始化协议对话标识查找因特网协议多媒体子系统会话； 向所述用户设备发送指示业务控制切换成功的消息。 本发明实施例还提供了一种业务集中和会话连续性应用服务器 , 包括： 会话初始协议邀请发送单元， 用于通过 Gm接口向用户设备发送会话初始 化协议邀请消息；
响应消息接收单元， 用于接收所述用户设备返回的响应消息， 所述响应 消息指示了所述用户设备选择使用电路域承载和使用 II接口控制；
II邀请消息发送单元，用于若响应消息接收单元接收到所述响应消息， 则 通过 II接口向所述用户设备发送 II邀请消息， 所述 II邀请消息携带指示 Gm接 口控制回退到 II接口控制的信息和用于关联所述会话初始化协议邀请消息的 信息。 本发明实施例还提供了一种业务集中和会话连续性应用服务器， 包括
II邀请接收单元， 用于接收用户设备发送的 II邀请消息， 所述 II邀请消息 携带因特网协议多媒体子系统会话的业务控制切换请求指示以及会话初始化 协议对话标识；
会话查找单元 , 用于通过所述会话初始化协议对话标识查找因特网协议 多媒体子系统会话；
切换成功消息发送单元， 用于向所述用户设备发送指示业务控制切换成 功的消息。
本发明实施例还提供了一种用户设备， 包括：
邀请消息接收单元， 用于通过 Gm接口接收来自业务集中和会话连续性应 用月良务器的会话初始化协议邀请消息；
响应消息发送单元， 用于接收到所述会话初始化协议邀请消息后， 发送 响应消息， 所述响应消息指示了所述用户设备选择使用电路域承载和使用 II 接口控制；
II邀请接收单元， 用于通过 II接口接收 II邀请消息；
II邀请解析单元， 用于解析所述 II邀请消息得到指示 Gm接口控制回退到 II接口控制的信息和用于关联所述会话初始化协议邀请消息的信息。 本发明实施例还提供了一种用户设备， 包括：
II邀请发送单元，用于向业务集中和会话连续性应用服务器发送 II邀请消 息，所述 II邀请消息携带因特网协议多媒体子系统会话的业务控制切换请求指 示以及会话初始化协议对话标识；
切换成功消息接收单元， 用于接收指示业务控制切换成功的消息。 本发明实施例还提供了一种 II接口的业务控制系统 , 包括:
业务集中和会话连续性应用服务器和用户设备， 其中， 所述业务集中和会话连续性应用服务器包括：
会话初始协议邀请发送单元， 用于通过 Gm接口向用户设备发送会话初始 化协议邀请消息；
响应消息接收单元， 用于接收所述用户设备返回的响应消息， 所述响应 消息指示了所述用户设备选择使用电路域承载和使用 II接口控制；
II邀请消息发送单元，用于若响应消息接收单元接收到所述响应消息， 则 通过 II接口向所述用户设备发送 II邀请消息 , 所述 II邀请消息携带指示 Gm接 口控制回退到 II接口控制的信息和用于关联所述会话初始化协议邀请消息的 信息；
所述用户设备包括：
邀请消息接收单元， 用于通过 Gm接口接收来自业务集中和会话连续性应 用服务器的会话初始化协议邀请消息；
响应消息发送单元， 用于接收到所述会话初始化协议邀请消息后， 发送 响应消息， 所述响应消息指示了所述用户设备选择使用电路域承载和使用 II 接口控制；
II邀请接收单元， 用于通过 II接口接收 II邀请消息；
II邀请解析单元， 用于解析所述 II邀请消息得到指示 Gm接口控制回退到 II接口控制的信息和用于关联所述会话初始化协议邀请消息的信息。 本发明实施例还提供了另一种 II接口的业务控制系统， 包括：
业务集中和会话连续性应用服务器和用户设备， 其中，
所述业务集中和会话连续性应用服务器包括：
II邀请接收单元， 用于接收用户设备发送的 II邀请消息， 所述 II邀请消息 携带因特网协议多媒体子系统会话的业务控制切换请求指示以及会话初始化 协议对话标识；
会话查找单元 , 用于通过所述会话初始化协议对话标识查找因特网协议 多媒体子系统会话；
切换成功消息发送单元， 用于向所述用户设备发送指示业务控制切换成 功的消息； 所述用户设备包括：
II邀请发送单元，用于向业务集中和会话连续性应用服务器发送 II邀请消 息 ,所述 II邀请消息携带因特网协议多媒体子系统会话的业务控制切换请求指 示以及会话初始化协议对话标识；
切换成功消息接收单元， 用于接收指示业务控制切换成功的消息。
上述技术方案具有如下有益效果：通过使用 II邀请消息的置换头域携带指 示 Gm接口控制回退到 II接口控制的信息和用于关联上述会话初始化协议邀请 消息的信息， 可以省略主叫和被叫用户标识， 降低了 II协议消息的开销。 附图说明 施例或现有技术描述中所需要使用的附图作简单地介绍， 显而易见地， 下面 描述中的附图仅仅是本发明的一些实施例， 对于本领域普通技术人员来讲， 在不付出创造性劳动性的前提下 , 还可以根据这些附图获得其他的附图。
图 1为本发明实施例 ICS UE主叫的方法流程示意图；
图 2为本发明实施例 ICS UE被叫的方法流程示意图；
图 3为本发明实施例一 Gm fallback的方法流程示意图；
图 4为本发明实施例二 Gm切换的方法流程示意图；
图 5为本发明实施例三增加 II接口的方法流程示意图；
图 6为本发明实施例四业务集中和会话连续性应用服务器结构示意图； 图 7为本发明实施例四业务集中和会话连续性应用服务器结构示意图； 图 8为本发明实施例五业务集中和会话连续性应用服务器结构示意图； 图 9为本发明实施例六业务集中和会话连续性应用服务器结构示意图； 图 10为本发明实施例七用户设备结构示意图；
图 11为本发明实施例八 II接口的业务控制系统结构示意图；
图 12为本发明实施例九 II接口的业务控制系统结构示意图；
图 13为本发明实施例十 II接口的业务控制系统结构示意图；
图 14为本发明实施例十一 II接口的业务控制系统结构示意图；
图 15为本发明实施例十二用户设备结构示意图； 图 16为本发明实施例十二用户设备结构示意图；
图 17为本发明实施例十三用户设备结构示意图；
图 18为本发明实施例十三用户设备结构示意图。 具体实施方式
下面将结合本发明实施例中的附图 , 对本发明实施例中的技术方案进行 清楚、 完整地描述， 显然， 所描述的实施例仅仅是本发明一部分实施例， 而 不是全部的实施例。 基于本发明中的实施例， 本领域普通技术人员在没有做 出创造性劳动前提下所获得的所有其他实施例， 都属于本发明保护的范围。
II协议设计时降低消息开销有两个角度： 减少信息传递，对要传递的信息 进行高效的编码。 本发明实施例主要涉及从 "减少信息传递" 角度降低消息 开销。
主叫和被叫场景的 II协议方案中的开销优化设计主要有：
1 )11协议不包含 SIP协议中的经由（ Via )头功能、记录路由（ Record-route ) 头功能、 路线（Route )头功能等；
2 )对于会话描述协议（ Session Description Protocol, SDP )功能， II协议 仅包含 SIP协议中的部分 SDP功能；
3 ) II 邀请（ Invite ) 包含 IMS会话的主叫用户标识和被叫用户标识， 后 续的响应或请求都不必包含主叫用户标识和被叫用户标识， 后续的响应或请 求通过呼叫编号（ Call-ID )、 从标签（ From tag )和往标签（ To tag )组合起来 关联 IMS会话。
首先介绍主叫和被叫场景下的优化方案：
场景一、 ICS UE主叫
这个流程中 , ICS UE A通过 II接口发起 IMS会话， SCC AS分配一个公共 月良务身份目录号码（ Public Service Identity Directory Numbe, PSI DN )用于 UE 发起一个 CS域呼叫以建立 CS承载（bearer ) (该 CS bearer用于传输 IMS会话媒 体流）， SCC AS接收到 CS域移动交换中心（ Mobile Switching Centre , MSC ) 月良务器（ server )或媒体网关控制功能（ Media Gateway Control Function, MGCF ) 发送的 SIP Invite (邀请） 消息后， 代替 UE A生成 SIP Invite消息以发起 IMS会 话。 具体流程如图 1所示：
步驟 101、 ICS UE A通过 II接口发送 II Invite消息以发起一个 IMS会话 , 包 含的信息有：
II呼叫标识（ Call-ID ), 用于在 II接口上标识本次 IMS会话或呼叫， 比如， 设置为： 2037701k s;
II 1"011头（ From header ),该头域的值用于指明本次会话的主叫用户标识， t匕^口, 设置为 user— a@example.com, From头还包^ "个标签 ( tag, tag用于和 II呼叫标识组合起来在 II接口上标识本次 IMS会话或呼叫标识， 为了减小消息 开销， 可能不设置 /传递 tag ), 比如， 设置为 a2ci;
II To头 （To Header ), 该头域的值指明本次会话的被叫用户标识， 比如， 设置为 user_b@example . com；
II命令序号 （Cseq, Command Sequence ), 用于指明该条 II命令（或称 II 请求、 II方法）的顺序， UE A生成该 II Inivte请求时， 随机的选择一个数值作 为 CSeq值， 比如 1688, 后续 UE A发送其它 II请求时， CSeq将不断加 1 , CSeq 还包括一个方法（method )信息， 指明 II邀请， SCC AS发出的对该条 II邀请 的响应都会复制该 CSeq， 以便 UE A进行 II请求和 II响应的匹配。 II命令可以 为 II Inivte, 也可以为其他通过 II接口发送的命令（或称请求、 方法） 消息， 在此本发明实施例不予限定。
步驟 102、 SCC AS接收到 II Inivte后保存 Call-ID、 From头、 To头、 命令序 号（ SCC AS后续发送 II请求时也生成并维护自己的命令序号）， 并通过 II接口 发出响应 II会话进度消息， 包含的信息有：
11呼叫标识， 从 11 Invite复制过来；
II From头， 从 II Invite复制过来， 并删除主叫用户标识；
II To头， 从 II Invite复制过来， 删除被叫用户标识， 并生成一个 tag ( tag 用于和 II呼叫标识组合来在 II接口上标识本次 IMS会话或呼叫标识， 为了减小 消息开销， 可能不设置 /传递 tag ) 包含在 To头中， 比如 tag=u7c3, II Call-ID、 II From tag和 II To tag组合起来在 II接口上唯一的标识一个 IMS会话或呼叫； II命令序号 （Cseq ), 从 II Invite复制过来；
SDP ( session description protocol,会话描述协议 M言息，其中包含 PSI DN, 用于 ICS UE A发起一个 CS呼叫以建立 CS bearer (或称 CS connection ), CS bearer用于 IMS会话的媒体流的传输， PSI DN和 SCC AS关联， 比如， PSI DN 设置为 +12125556666; 后续 UE可以用 PSI DN将 CS呼叫发送到 SCC AS。 在其 它 II请求或响应 中 SDP信息还可以 包含其它信息 , 比如 II Update(SDP(a=inactive)) , 用于指示将 IMS会话保持（hold )。
步驟 103 ~步驟 104、 ICS UE A以 PSI DN为被叫号码发起一个 CS域呼叫 , CS域 MSC server或者 MGCF ( Media Gateway Control Function, 媒体网关控制 功能）进行 CS信令和 SIP转换， 生成 SIP Invite (包含 PSI DN ), 该 SIP Invite最 后达到 SCC AS , SCC AS使用 PSI DN关联保存的 II Invite信息。
注： 步驟 102之后， UE A可能发送其它 II请求， 比如 II Update请求时， 应 设置 CSeq: 1689 Update。
步驟 105 ~步驟 106、 SCC AS生成 SIP Invite(包含被叫用户标识和 CS bearer 信息 , CS bearer信息用于 UE B进行媒体流传输）， 该 SIP Invite最后达到 UE B , UE B用户摘机接受 IMS会话邀请， UE B发送成功消息（ 200 OK )指示用户已 摘机。
步驟 107 ~步驟 108、 SCC AS向 MSC server或者 MGCF发送 200 OK, 指示 CS呼叫建立成功， MSC Server向 UE A发送 connect消息，指示 CS呼叫建立成功。
步驟 109、 SCC AS通过 II接口发送 II 200 OK响应，指示 IMS会话建立成功。 II 200 OK的头域部分和 II会话进度消息相同， 而 SDP部分不再包含 PSI DN。
步驟 110、 SCC AS向 UE B发送 SIP ACK请求 , 用于对 200 OK进行 (接收） 确认。 SCC AS不必等待 UE A对 II 200 OK的接收确认，它可以使用底层的传输 层协议（比如 USSD或 SMS ) 的可靠传输能力。
场景二、 ICS UE被叫
这个流程中， SCC AS通过 II接口下发 IMS会话邀请， 包含 PSI DN, 用于 UE发起一个 CS域呼叫以建立 CS bearer (用于传输 IMS会话媒体流）。具体流程 如图 2所示：
步驟 201、 SCC AS接收到 SIP Invite消息， 包含主叫用户标识（比如， 设置 为 user— b@example.com )和被叫用户标" i只 ( t匕^口,设置为 user— a@example.com )。
步驟 202、 SCC AS通过 II接口发送 II Invite消息到 ICS UE A, 包含的信息 有 （SCC AS也保存这些信息）：
II 呼叫标识（Call-ID ), 用于在 II接口上标识本次 IMS会话或呼叫， 比如， 设置为 9t3j 9xsdfw9tg374js7usj v；
II ? 011头（ From header ),该头域的值用于指明本次会话的主叫用户标识， t匕^口, 设置为 user— b@example.com, From头还包^ "个标签 ( tag ), t匕^口, 设 置为 kg48;
II To头 （To Header ), 该头域的值指明本次会话的被叫用户标识， 比如， 设置为 user— a@example.com;
II命令序号（CSeq, Command Sequence ), 比如， 设置为 CSeq: 98 Invite;
SDP ( session description protocol,会话描述协议 M言息，其中包含 PSI DN, 用于 ICS UE A发起一个 CS呼叫以建立 CS bearer (或称 CS connection ), 比如 , 设置为 +12125558888。
步驟 203、 ICS UE Α接收到 II Inivte后保存 II Call-ID, II From头、 II To头、 II命令序号， 并通过 II接口发出响应 II会话进度， 包含的信息有：
11呼叫标识 , 从 11 Invite复制过来；
11 From头 , 从 11 Invite复制过来 , 并删除主叫用户标识；
II To头， 从 II Invite复制过来， 删除被叫用户标识， 并生成一个 tag包含在 II To头中 , 比如 tag=i89r;
II命令序号 （Cseq )， 从 II Invite复制过来；
步驟 204 ~步驟 207、 建立 CS bearer。 ICS UE A以 PSI DN为被叫号码发起 一个 CS域呼叫， CS域 MSC server或者 MGCF进行 CS信令和 SIP转换， 生成 SIP Invite (包含 PSI DN )， 该 SIP Invite最后达到 SCC AS， SCC AS使用 PSI DN关联 到保存的 II Invite相关信息。 SCC AS发送最终响应 200 OK到 MSC server或者 MGCF (指示呼叫建立成功）， MSC server或者 MGCF以 ACK进行 200 OK接收 确认。 MSC server向 UE A发送 connect指示 CS呼叫建立成功。
步驟 208 ~步驟 210、 UE A通过 II接口发送 II 200 OK响应， 指示 IMS会话 建立成功。 II 200 OK的头域部分和 II会话进度相同。 SCC AS向 UE B发送 SIP 200 OK, 该指示 UE A的用户已摘机， IMS会话建立成功。 UE B向 SCC AS发送 SIPACK请求， 用于对 200 OK进行（接收）确认。 II接口除了主叫和被叫场景， 还包括 Gm接口回退（ fallback )到 II接口、 Gm切换到 II接口和增加 II接口三种场景， 前面提到的优化设计在这三种场景 都可以借鉴。
以下将分别就 Gm接口回退（ fallback )到 II接口、 Gm切换到 II接口和增加 II接口场景下 II接口业务控制优化设计进行说明。
实施例一，本发明实施例提供了 Gm fallback场景下的一种 II接口的业务控 制方法， 从 SCC AS—端来看， 执行流程可以包括： 通过 Gm接口向 ICS UE发 送 SIP会话初始化协议邀请消息； 若接收到上述用户设备返回的响应消息， 上 述响应消息指示了上述用户设备选择使用电路域承载和使用 II接口控制，则通 过 II接口向上述用户设备发送 II邀请消息， 上述 II邀请消息的包含指示 Gm接 口 (业务）控制回退到 II接口 (业务）控制的信息和用于关联 SIP邀请的信息， 优选的， 上述两个信息包含在置换头域中， 可选的， II邀请消息使用 SIP对话 的呼叫标识和 tag作为 II接口呼叫标识和 II接口 tag， SIP对话由前面的 SIP Invite 触发生成。 说明： 为了简化， II接口 tag可以省略；
分析： 由于 UE可以通过 SIP Invite消息获取主叫、 被叫用户标识、 保密 ( privacy ), SCC AS在 II接口再次下发呼叫请求（即 II Invite ) 时， 可以省略 主叫和被叫用户标识， 可以省略保密（privacy ), 且为了 UE能够关联 II呼叫请 求和之前的 SIP Invite , SCC AS应该包含关联信息 , 比如使用置换（ replace ) 头包含 SIP对话（dialog )呼叫标识和 tag ( tag是可选包含的）， 进一步， 默认 SIP对话呼叫标识和 tag分别作为 II呼叫标识和 II tag, 则 SCC AS不必在 II Invite 中另外包含新的 II呼叫标识和 II tag ( II tag包括 II From tag和 II To tag )。 这样 就有两个方面的优化： 省略主叫和被叫用户标识（UE使用 SIP dialog呼叫标识 和 tag关联已保存的主叫和被叫用户标识）、 省略生成新的 II呼叫标识和 II tag 的操作。
上述实施例中， SCC AS可以先通过 Gm接口下发 SIP Invite到 UE A, Invite 中的 SDP信息包含分组交换媒体 ( acket switching media, PS media )信息和 电路交换媒体 CS media信息， CS media信息指示 UE A可以选择 CS bearer, CS media信息也可以包含 PSI DN。 UE A决定使用 CS bearer传输会话媒体流并且使 用 II接口进行业务控制，返回 SIP会话进度 ( SIP 183 )响应（指示使用 CS bearer 和 II接口控制 ^ SCC AS, SCC AS通过 II接口下发呼叫请求到 UE A,建立 IMS 会话， 释放 SIP对话 ( dialog X
更具体地， 如图 3所示， Gm fallback场景下的流程可以包括以下步驟： 步驟 301、 SCC AS接收到 SIP Invite消息， 包含主叫用户标识（比如， 设置 为 user— b@example.com )和被叫用户标只 ( t匕^口,设置为 user— a@example.com )。
步驟 302、 SCC AS通过 Gm接口发送 SIP Invite消息到 ICS UE A以发起一个 IMS会话， 包含的信息有 （SCC AS也保存这些信息）：
呼叫标识 （ Call-ID ), 用于标识本次 IMS会话或呼叫， 比如， 设置为 I93j9xsKKIg374js7u8JY;
From头 ( From header ), 该头域的值用于指明本次会话的主叫用户标识， t匕^口, 设置为 user— b@example.com, From头还包^ "个标签 ( tag ), t匕^口, 设 置为 094P;
To头（To Header ), 该头域的值指明本次会话的被叫用户标识， 比如， 设 置为 user— a@example.com;
命令序号 （CSeq, Command Sequence ), 比如， 设置为 CSeq: 891 Invite;
SDP ( session description protocol, 会话描述协议)信息， 包含 PS media 信息和 CS media信息， CS media信息指示 UE A可以选择 CS bearer, CS media 信息也可以包含 PSI DN, 比如， 设置为 +12125556886。
步驟 303、 ICS UE A接收到 SIP Inivte后保存 Call-ID、 From头、 To头、 命令 序号。 UE A决定使用 CS bearer传输会话媒体流， 通过 Gm接口返回响应给 SCC AS (返回响应会生成 SIP dialog, SIP dialog是 SIP协议的一个属性， 用于后续 SIP消息通信）， 比如 183 (会话进度 sessin progress )， 包含的信息有：
呼叫标识 , 从 SIP Invite复制过来；
From头， 从 SIP Invite复制过来；
To头，从 SIP Invite复制过来，并生成一个 tag包含在 To头中，比如 tag=io7p; 命令序号 （Cseq ), 从 SIP Invite复制过来。
步驟 304、 SCC AS通过 II接口下发 II Invite (不包含 II Call-ID头、 II From 头和 II To头）到 UE A, 包含的信息有：
II Replace头，该头域指明该 II Invite代替前面的 SIP Invite,该头域包含 SIP dialog呼叫标识信息和 tag信息；
命令序号 （CSeq, Command Sequence ), 比如， 设置为 CSeq: 891 Invite。 步驟 305、 108 11£ 接收到11 11 ^^,通过 II Replace头识别到 Gm接口回退 到 II接口， 并根据 II Replace头信息查找到保存的 SIP dialog信息（主叫、 被叫 用户标识等）， UE使用 SIP dialog呼叫标识和 tag作为 II呼叫标识和 II tag进行正 常的 II接口被叫会话 ( session )建立过程 (这个过程可以参考 ICS UE被叫的流 程）。 另夕卜， 1¾或8(^：八8可以发起(¾接口81? ^1(¾释放。
实施例二， 本发明实施例提供了 Gm接口控制切换场景下的一种 II接口的 业务控制方法， 从 SCC AS—端来看， 执行流程可以包括： 接收因特网协议多 媒体子系统集中的服务的用户设备发送的 II邀请消息，上述 II邀请消息的置换 头域包含业务控制切换请求指示以及会话初始化协议对话 ID; 通过上述会话 初始化协议对话 ID查找 IMS会话； 向上述用户设备发送 II成功消息指示向 II接 口控制切换成功。
具体地，上述 II邀请消息的 II接口呼叫标识为上述会话初始化协议会话的 对话标识。
上述实施例中， 解决了目前要进行业务控制的切换， 需要解决的两个技 术问题， 一个是业务控制切换请求的表示， 另一个是 II呼叫标识和 II tag的建 立。 通过使用 II Invite请求包含置换（replace )头 （ replace头携带 Gm接口 SIP dialog ID )来指示代替 Gm接口的业务控制。 另外 II呼叫标识和 II tag可以重用 SIP dialog ID的呼叫标识和 tag, 这样 II Invite可以省略 II Call-ID头、 II From 头和 II To头的传递。 SCC AS收到业务控制切换请求后返回 II 200 OK, 指示业 务控制切换成功。 后续 UE可以通过 II接口进行业务控制。 这样就有两个方面 的优化： 省略主叫和被叫用户标识（ SCC AS通过 Replace头关联 IMS会话、 主 叫和被叫用户标识）、 省略生成新的 II呼叫标识和 II tag的操作。
更具体地， 如图 4所示， Gm切换场景下的流程可以包括以下步骤： 步驟 401、 UE A发送 II Invite消息（不包含 II Call-ID头、 II From头和 II To 头， 默认和 SIP dialog中的一致）到 SCC AS, 包含的信息有：
Replace头，该头域指示业务控制切换请求，该头域包含 SIP dialog的 dialog
ID; II命令序号（CSeq, Command Sequence ), 比如， 设置为 CSeq: 263 Invite。 步驟 402、 SCC AS通过 replace头信息查找到 SIP dialog ( SIP dialog用来控 制 IMS会话），并识别 IMS会话已经使用 CS bearer传输媒体流， SCC AS以 II 200 OK响应 UE A,指示业务控制切换成功；若 IMS会话目前使用 PS域传输媒体流， 则需要新建 CS bearer。 SIP对话呼叫标识和 tag分别作为 II呼叫标识和 II tag。后 续 UE可以通过 II接口进行业务控制。 UE或 SCC AS可以发起 SIP dialog释放。
实施例三，本发明实施例提供了增加 II接口业务控制场景下的一种 II接口 的业务控制方法， 从 SCC AS—端来看， 执行流程可以包括： 接收因特网协议 多媒体子系统集中的服务的用户设备发送的 II邀请，上述 II邀请包含会话转移 标识符（ session transfer identifier, STI )指示增加 II接口业务控制 (可筒称为 增加 II接口）， STI可作为请求统一资源标识（Request URI )或往头（To header ) 的值； SCC AS通过底层的传输层获得上述用户设备的 CS域号码（比如移动台 综合业务数字网号码（ MSISDN, Mobile station ISDN )、 MDN( Mobile Directory Number, 移动目录号码））， 然后通过上述 CS域号码查找因特网协议多媒体子 系统会话， 或， 通过上述 STI查找因特网协议多媒体子系统会话； 向上述用户 设备发送 II邀请成功消息指示 II接口增加成功。
上述流程的执行场景下可以是： UE A决定增加 II接口是为了保持当前 IMS 会话， 并建立第二个会话， 则上述 II邀请还包括： 保持当前因特网协议多媒体 子系统会话的指示信息。
也可能是 SCC AS通过 II接口下发了新的 IMS会话（按正常被叫流程） 而 UE A需要保持第一个会话而接通第二个会话（新的 IMS会话）， 则上述接收因 特网协议多媒体子系统集中的服务的用户设备发送的 II邀请之前还包括： SCC AS向上述用户设备发送 II邀请 , 发起新的因特网协议多媒体子系统会话。
也可能， SCC AS发起 II接口业务控制的增加， SCC AS通过 II invite (不 携带主叫、被叫用户标识）增加 II接口业务控制， 具体的场景可能是对端增加 或者删除 video、 或者有其它到 UE的信息需要发送； 则从 ICS UE—端来看， 执 行流程可以包括：
接收业务集中和会话连续性应用服务器发送的 II邀请，上述 II邀请包含会 话转移标识符（ session transfer identifier, STI )指示增加 II接口业务控制 （可 筒称为增加 II接口）， STI可作为请求统一资源标识（ Request URI )或往头（ To header ) 的值。
上述由 SCC AS发起 II接口业务控制的增加， 则 SCC AS可以发送 II Invite (不包含主叫和被叫用户标识）到1¾, 其中包含 STI以向 UE指示 II接口业务 控制增加 , II呼叫标识和 II tag的创建可以采取正常的 II接口被叫过程中的方 式。 默认当前 UE只有 1个 IMS会话 , 因此 UE自然可以关联 IMS会话。
上述技术方案， 在 UE A增加 II接口业务控制的情况下解决了三个技术问 题， 一个是 II接口业务控制增加请求的表示， 另一个是 II呼叫标识和 II tag的 建立，再一个是 SCC AS如何关联 IMS会话。可以使用 II Invite请求包含 STI (会 话转移标识符 session transfer identifier , 现有技术用来进行接入转移 access transfer, 比如将媒体流从 CS域转移到 PS域）来指示 II接口业务控制增加请求。 II呼叫标识和 II tag的创建可以釆取正常的 II接口主叫过程中的方式。 SCC AS 关联 IMS会话可以使用 STI (如果能够唯一标识 UE A )， 或者 SCC AS通过底层 的传输层上报的 CS域 UE号码 （比如 MSISDN、 MDN ( Moblie Directory Number ) )。 这样就有两个方面的优化： 省略主叫和被叫用户标识（ SCC AS通 过 STI或者 CS域 UE号码查找 IMS会话、 主叫和被叫用户标识）。
更具体地，如图 5所示， UE增加 II接口业务控制的流程可以包括以下步驟： 步驟 501、 UE A发送 II Invite消息到 SCC AS, 包含的信息有：
STI (作为请求（Request ) 统一资源标识 ( Uniform Resource Identifier, URI )头或者 To头的值）， 指示增加 II接口业务控制；
II Call-ID头和 From tag;
II 命令序号（CSeq， Command Sequence ),比如，设置为 CSeq: 163 Invite。 UE A可以包含将当前 IMS会话保持的请求， 比如， 设置 a=inactive (未激 活）。
步骤 502、 SCC AS通过底层的传输层获得 UE A的 CS域号码 （比如 MSISDN, MDN ), 再通过 CS域号码查找到 IMS会话， 或者通过 STI查找 IMS 会话， 8(^：八8以11 200 01 1向应 （包含 1&8 ) 1；£八， 指示 II接口增加成功。
实施例四， 如图 6所示， 本发明实施例还提供了一种业务集中和会话连续 性应用服务器， 包括： 会话初始协议邀请发送单元 601 , 用于通过 Gm接口向用户设备发送会话 初始化协议邀请消息；
响应消息接收单元 602, 用于接收上述用户设备返回的响应消息， 上述响 应消息指示了上述用户设备选择使用电路域承载和使用 II接口控制；
II邀请消息发送单元 603 , 用于响应消息接收单元 602接收到所述响应消 息， 则通过 II接口向上述用户设备发送 II邀请消息， 上述 II邀请消息携带指示 Gm接口控制回退到 II接口控制的信息和用于关联上述会话初始化协议邀请消 息的信息。
进一步地，如图 7所示， 上述业务集中和会话连续性应用服务器，还包括： 标识设置单元 701， 用于设置上述 II邀请消息的 II接口呼叫标识为上述会 话初始化协议邀请消息的对话的呼叫标识。
上述实施方式， 通过使用 II邀请消息的置换头域携带指示 Gm接口控制回 退到 II接口控制的信息和用于关联上述会话初始化协议邀请消息的信息，省略 主叫和被叫用户标识， 另外通过使用上述会话初始化协议邀请消息的对话的 呼叫标识作为 II接口呼叫标识可省略 II dialog ID。 降低了 II协议消息的开销。
实施例五， 如图 8所示， 本发明实施例还提供了一种业务集中和会话连续 性应用服务器， 包括
II邀请接收单元 801 , 用于接收用户设备发送的 II邀请消息， 上述 II邀请 消息携带业务控制切换请求指示以及会话初始化协议会话的对话标识；
会话查找单元 802, 用于通过上述会话初始化协议会话的对话标识查找会 话初始化协议会话；
切换成功消息发送单元 803， 用于向上述用户设备发送指示业务控制切换 成功的消息。
可选的 , II邀请接收单元 801接收到的上述 II邀请消息的 II接口呼叫标识 为上述会话初始化协议对话的呼叫标识。
上述实施方式 ,通过 II邀请消息携带业务控制切换请求指示以及会话初始 化协议会话的会话标识， 可以省略主叫和被叫用户标识， 另外通过使用上述 会话初始化协议邀请消息的对话的呼叫标识作为 II接口呼叫标识可省略 II dialog ID。 降低了 II协议消息的开销。 实施例六， 如图 9所示， 本发明实施例还提供了一种业务集中和会话连续 性应用服务器， 包括：
II邀请接收单元 901 , 用于接收用户设备发送的 II邀请消息， 上述 II邀请 消息携带 IMS会话增加 II接口指示； 上述因特网协议多媒体子系统会话增加 II 接口指示，通过将上述 II邀请消息的请求统一资源标识的值或往头的值设置为 会话转移标识符来携带； 或， 由所述 II邀请消息包含的公共服务身份目录号码 来携带， 所述公共服务身份目录号码为所述因特网协议多媒体子系统会话另 一方的号码；
会话查找单元 902, 用于通过上述会话转移标识符或公共服务身份目录号 码查找因特网协议多媒体子系统会话； 或， 会话查找单元 902， 用于通过底层 传输层获得上述用户设备的电路域号码， 然后通过上述电路域号码查找因特 网协议多媒体子系统会话；
请求成功消息发送单元 903， 用于向上述用户设备发送指示 II接口增加成 功的消息。
上述实施方式， 通过使用 II邀请消息携带 IMS会话增加 II接口指示， 省略 主叫和被叫用户标识。 降低了 II协议消息的开销。
实施例七， 如图 10所示， 本发明实施例还提供了一种用户设备， 包括：
II邀请接收单元 1001 ,用于接收业务集中和会话连续性应用服务器发送的 II邀请消息， 上述 II邀请消息携带指示 IMS会话增加 II接口业务控制的信息；
II接口业务控制建立单元 1002, 用于建立 II接口业务控制， 关联上述 II接 口业务控制和上述 IMS会话。
上述实施方式， 通过使用 II邀请消息携带 IMS会话增加 II接口指示， 省略 主叫和被叫用户标识。 降低了 II协议消息的开销。
实施例八，如图 11所示， 本发明实施例还提供了一种 II接口的业务控制系 统， 包括：
业务集中和会话连续性应用服务器 1101 , 用于通过 Gm接口向用户设备 1102发送会话初始化协议邀请消息； 若接收到上述用户设备 1102返回的响应 消息，上述响应消息指示了上述用户设备选择使用电路域承载和使用 II接口控 制， 则通过 II接口向上述用户设备 1102发送 II邀请消息， 上述 II邀请消息携带 指示 Gm接口控制回退到 II接口控制的信息和用于关联上述会话初始化协议邀 请消息的信息；
用户设备 1102 , 用于接收到会话初始化协议邀请消息后向上述业务集中 和会话连续性应用服务器 1101发送响应消息， 上述响应消息指示了用户设备 1102选择使用电路域承载和使用 II接口控制； 接收 II邀请消息， 解析上述 II邀 请消息得到指示 Gm接口控制回退到 II接口控制的信息和用于关联上述会话初 始化协议邀请消息的信息。
可选的，上述业务集中和会话连续性应用服务器 1101发送的上述 II邀请消 息的 11接口呼叫标识为上述会话初始化协议邀请消息的对话的呼叫标识；
上述用户设备 1102， 还用于使用上述会话初始化协议邀请消息生成对话 的呼叫标识作为 II接口呼叫标识进行 II接口被叫会话建立流程。
上述实施方式， 通过使用 II邀请消息携带指示 Gm接口控制回退到 II接口 控制的信息和用于关联上述会话初始化协议邀请消息的信息， 可以省略主叫 和被叫用户标识， 另外通过使用上述会话初始化协议邀请消息的对话的呼叫 标识作为 II接口呼叫标识可省略 II dialog ID。 降低了 II协议消息的开销。
实施例九，如图 12所示，本发明实施例还提供了一种 II接口的业务控制系 统， 其特征在于， 包括：
业务集中和会话连续性应用服务器 1201 ,用于接收用户设备 1202发送的 II 邀请消息，上述 II邀请消息携带业务控制切换请求指示以及会话初始化协议对 话的呼叫标识； 通过上述会话初始化协议对话的呼叫标识查找因特网协议多 媒体子系统会话； 向上述用户设备 1202发送指示业务控制切换成功的消息； 用户设备 1202，用于向上述业务集中和会话连续性应用服务器 1201发送 II 邀请消息； 接收上述 II成功消息获知业务控制切换成功。
可选的，上述用户设备 1202发送的上述 II邀请消息的 II接口呼叫标识为上 述会话初始化协议对话的呼叫标识；
上述业务集中和会话连续性应用服务器 1201 ,用于接收用户设备发送的 II 邀请消息包括：接收用户设备发送的上述 II接口呼叫标识为上述会话初始化协 议会话的会话标识的 II邀请消息， 进行 II接口主叫会话建立流程。
上述实施方式，通过使用 II邀请消息携带业务控制请求的指示以及会话初 始化协议会话的会话标识， 可以省略主叫和被叫用户标识， 另外通过使用上 述会话初始化协议邀请消息的对话的呼叫标识作为 II接口呼叫标识可省略 II dialog ID。 降低了 II协议消息的开销。
实施例十，如图 13所示，本发明实施例提供了一种 II接口的业务控制系统， 包括：
业务集中和会话连续性应用服务器 1301 ,用于接收用户设备 1302发送的 II 邀请消息， 上述 II邀请消息携带 IMS会话增加 II接口指示； 上述因特网协议多 媒体子系统会话增加 II接口指示，通过将上述 II邀请消息的请求统一资源标识 的值或往头的值设置为会话转移标识符来携带，或由所述 II邀请消息包含的公 共服务身份目录号码来携带， 所述公共服务身份目录号码为所述因特网协议 多媒体子系统会话另一方的号码； 通过会话转移标识符或公共服务身份目录 号码查找因特网协议多媒体子系统会话， 或， 通过底层传输层获得上述用户 设备 1302的电路域号码并通过电路域号码查找因特网协议多媒体子系统会 话； 向上述用户设备 130发送指示 II接口增加成功的消息；
用户设备 1302,用于向上述业务集中和会话连续性应用服务器 1301发送 II 邀请； 接收 II成功消息获知 II接口增加成功。
上述实施方式， 通过使用 II邀请消息携带 IMS会话增加 II接口指示， 可以 省略主叫和被叫用户标识。 降低了 II协议消息的开销。
实施例十一，如图 14所示，本发明实施例提供了一种 II接口的业务控制系 统， 包括：
用户设备 1402,用于接收业务集中和会话连续性应用服务器 1401发送的 II 邀请消息， 上述 II邀请消息指示 IMS会话增加 II接口业务控制的信息； 建立 II 接口业务控制 , 关联上述 II接口业务控制和上述 IMS会话；
业务集中和会话连续性应用服务器 1401 ,用于向上述用户设备 1402发送 II 邀请消息， 上述 II邀请消息指示 IMS会话增加 II接口业务控制的信息。
上述实施方式， 通过使用 II邀请消息携带 IMS会话增加 II接口指示， 可以 省略主叫和被叫用户标识。 降低了 II协议消息的开销。
实施例十二， 如图 15所示， 本发明实施例提供了一种用户设备， 包括： 邀请消息接收单元 1501 , 用于通过 Gm接口接收来自业务集中和会话连续 性应用服务器的会话初始化协议邀请消息； 上述会话初始化协议邀请消息携 带有使用电路域承载和使用 II接口控制的指示的响应消息；
响应消息发送单元 1502, 用于接收到上述会话初始化协议邀请消息后， 发送携带有使用电路域承载和使用 II接口控制的指示的响应消息；
II邀请接收单元 1503 , 用于通过 II接口接收 II邀请消息；
II邀请解析单元 1504 , 用于解析上述 II邀请消息得到指示 Gm接口控制回 退到 II接口控制的信息和用于关联上述会话初始化协议邀请消息的信息；
进一步地， 如图 16所示， 上述 II邀请消息的 II接口呼叫标识为上述会话初 始化协议邀请消息生成对话的呼叫标识； 还包括：
会话建立单元 1601 , 用于使用上述会话初始化协议邀请消息的对话的呼 叫标识作为 11接口呼叫标识进行 11接口被叫会话建立流程。
实施例十三， 如图 17所示， 本发明实施例还提供了一种用户设备， 包括： II邀请发送单元 1701， 用于向业务集中和会话连续性应用服务器发送 II 邀请消息 ,上述 II邀请消息携带因特网协议多媒体子系统会话的业务控制切换 请求指示以及会话初始化协议对话标识；
切换成功消息接收单元 1702， 用于接收指示业务控制切换成功的消息。 进一步地， 如图 18所示， 上述 II请求发送单元 1601包括：
标识设置单元 1801 ,用于设置上述 II邀请消息的 II接口呼叫标识为上述会 话初始化十办议对话的呼叫标识。
以上的用户设备和业务集中和会话连续性应用服务器均可以用于 II接口 的业务控制。 是可以通过程序来指令相关的硬件完成， 所述的程序可以存储于一种计算机 可读存储介质中， 上述提到的存储介质可以是只读存储器， 磁盘或光盘等。
以上对本发明实施例所提供的一种 II接口的业务控制方法、装置和系统进 述， 以上实施例的说明只是用于帮助理解本发明的方法及其核心思想； 同时， 对于本领域的一般技术人员， 依据本发明的思想， 在具体实施方式及应用范 围上均会有改变之处， 综上所述， 本说明书内容不应理解为对本发明的限制。

Claims

权 利 要 求
1、 一种 II接口的业务控制方法， 其特征在于， 包括：
通过 Gm接口向用户设备发送会话初始化协议邀请消息；
若接收到所述用户设备返回的响应消息， 所述响应消息指示了所述用户 设备选择使用电路域承载和使用 II接口控制；则通过 II接口向所述用户设备发 送 II邀请消息 , 所述 II邀请消息携带指示 Gm接口控制回退到 II接口控制的信 息和用于关联所述会话初始化协议邀请消息的信息。
2、 根据权利要求 1所述方法， 其特征在于， 所述指示 Gm接口控制回退到 II接口控制的信息和用于关联所述会话初始化协议邀请消息的信息通过所述 II邀请消息的置换头域携带。
3、 根据权利要求 1或 2所述方法， 其特征在于，
所述 II邀请消息的 II接口呼叫标识为所述会话初始化协议邀请消息生成 对话的呼叫标识。
4、 一种 II接口的业务控制方法， 其特征在于， 包括：
接收用户设备发送的 II邀请消息，所述 II邀请消息携带因特网协议多媒体 子系统会话的业务控制切换请求指示以及会话初始化协议对话标识；
通过所述会话初始化协议对话标识查找因特网协议多媒体子系统会话； 向所述用户设备发送指示业务控制切换成功的消息。
5、 根据权利要求 4所述方法， 其特征在于， 所述因特网协议多媒体子系 统会话的业务控制切换请求指示以及会话初始化协议对话标识通过所述 II邀 请消息的置换头域携带。
6、 根据权利要求 4或 5所述方法， 其特征在于，
所述 II邀请消息的 II接口呼叫标识为所述会话初始化协议对话的呼叫标 识。
7、 一种业务集中和会话连续性应用服务器， 其特征在于， 包括： 会话初始协议邀请发送单元 , 用于通过 Gm接口向用户设备发送会话初始 化协议邀请消息；
响应消息接收单元 , 用于接收所述用户设备返回的响应消息 , 所述响应 消息指示了所述用户设备选择使用电路域承载和使用 II接口控制； II邀请消息发送单元，用于若响应消息接收单元接收到所述响应消息， 则 通过 II接口向所述用户设备发送 II邀请消息， 所述 II邀请消息携带指示 Gm接 口控制回退到 II接口控制的信息和用于关联所述会话初始化协议邀请消息的 信息。
8、 根据权利要求 7所述业务集中和会话连续性应用服务器， 其特征在于， 还包括：
标识设置单元，用于设置所述 II邀请消息的 II接口呼叫标识为所述会话初 始化协议邀请消息生成对话的呼叫标识。
9、 一种业务集中和会话连续性应用服务器， 其特征在于， 包括：
II邀请接收单元， 用于接收用户设备发送的 II邀请消息， 所述 II邀请消息 携带因特网协议多媒体子系统会话的业务控制切换请求指示以及会话初始化 协议对话标识；
会话查找单元， 用于通过所述会话初始化协议对话标识查找因特网协议 多媒体子系统会话；
切换成功消息发送单元， 用于向所述用户设备发送指示业务控制切换成 功的消息。
10、 一种用户设备， 其特征在于， 包括：
邀请消息接收单元， 用于通过 Gm接口接收来自业务集中和会话连续性应 用月良务器的会话初始化协议邀请消息；
响应消息发送单元， 用于接收到所述会话初始化协议邀请消息后， 发送 响应消息， 所述响应消息指示了所述用户设备选择使用电路域承载和使用 II 接口控制；
II邀请接收单元， 用于通过 II接口接收 II邀请消息；
II邀请解析单元， 用于解析所述 II邀请消息得到指示 Gm接口控制回退到 II接口控制的信息和用于关联所述会话初始化协议邀请消息的信息。
11、 根据权利要求 10所述用户设备， 其特征在于， 所述 II邀请消息的 II接 口呼叫标识为所述会话初始化协议邀请消息生成对话的呼叫标识； 还包括： 会话建立单元， 用于使用所述会话初始化协议邀请消息的对话的呼叫标 识作为 II接口呼叫标识进行 II接口被叫会话建立流程。
12、 一种用户设备， 其特征在于， 包括：
II邀请发送单元，用于向业务集中和会话连续性应用服务器发送 II邀请消 息 ,所述 II邀请消息携带因特网协议多媒体子系统会话的业务控制切换请求指 示以及会话初始化协议对话标识；
切换成功消息接收单元， 用于接收指示业务控制切换成功的消息。
13、根据权利要求 12所述用户设备， 其特征在于， 所述 II请求发送单元包 括：
标识设置单元，用于设置所述 II邀请消息的 II接口呼叫标识为所述会话初 始化十办议对话的呼叫标识。
14、 一种 II接口的业务控制系统， 其特征在于， 包括如权利要求 7或 8任一 项所述的业务集中和会话连续性应用服务器以及如权利要求 10或 11任一项所 述的用户设备。
15、 一种 II接口的业务控制系统， 其特征在于， 包括如权利要求 9所述的 业务集中和会话连续性应用服务器以及如权利要求 12或 13任一项所述的用户 设备。
PCT/CN2010/075724 2009-08-12 2010-08-05 一种i1接口的业务控制方法、装置和系统 WO2011018008A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP10807953.4A EP2458781B1 (en) 2009-08-12 2010-08-05 Method, device and system for service control of i1 interface
US13/370,843 US8886812B2 (en) 2009-08-12 2012-02-10 Method, apparatus, and system for service control via I1 interface
US14/501,678 US20150016308A1 (en) 2009-08-12 2014-09-30 Method and apparatus for service control

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200910165624.8 2009-08-12
CN200910165624.8A CN101997697B (zh) 2009-08-12 2009-08-12 一种i1接口的业务控制方法和装置

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/370,843 Continuation US8886812B2 (en) 2009-08-12 2012-02-10 Method, apparatus, and system for service control via I1 interface

Publications (1)

Publication Number Publication Date
WO2011018008A1 true WO2011018008A1 (zh) 2011-02-17

Family

ID=43585944

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075724 WO2011018008A1 (zh) 2009-08-12 2010-08-05 一种i1接口的业务控制方法、装置和系统

Country Status (4)

Country Link
US (2) US8886812B2 (zh)
EP (1) EP2458781B1 (zh)
CN (1) CN101997697B (zh)
WO (1) WO2011018008A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101997697B (zh) 2009-08-12 2012-06-20 华为终端有限公司 一种i1接口的业务控制方法和装置
US20130219070A1 (en) * 2012-02-16 2013-08-22 Research In Motion Limited Resolving device specific identifiers to a user identifier to initiate a dialog establishment with devices of a user
KR101538285B1 (ko) * 2012-04-27 2015-07-21 가부시키가이샤 코나미 데지타루 엔타테인멘토 단말 장치, 그 제어 방법 및 컴퓨터 판독 가능한 기록 매체 및 애플리케이션 시스템
US20160241560A1 (en) * 2015-02-13 2016-08-18 Instart Logic, Inc. Client-site dom api access control
CN111130616B (zh) * 2018-11-01 2022-09-09 中兴通讯股份有限公司 会话控制方法及卫星地面站

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009693A (zh) * 2006-01-24 2007-08-01 华为技术有限公司 在分组网络中实现综合业务数字网业务的系统和方法
CN101114985A (zh) * 2006-07-27 2008-01-30 华为技术有限公司 编解码转换系统及方法
EP2071839A1 (en) * 2006-09-25 2009-06-17 Huawei Technologies Co., Ltd. A method, a system and a device for channel authorization of television living broadcast by network

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN100531194C (zh) * 2004-09-07 2009-08-19 华为技术有限公司 分组域业务信号处理系统及其方法
US7920551B2 (en) * 2005-03-08 2011-04-05 Genband Us Llc Multiple access service convergence
US7983240B2 (en) * 2006-10-16 2011-07-19 Telefonaktiebolaget Lm Ericsson (Publ) System and method for communication session correlation
CN101573996B (zh) 2006-11-06 2012-11-14 艾利森电话股份有限公司 允许通过ussd消息经由cs接入进行ims服务的会话控制的方法和设备
CN101453453B (zh) * 2007-12-04 2011-08-03 华为技术有限公司 实现呼叫保持的方法及设备
CN101459970B (zh) * 2007-12-14 2011-02-09 华为技术有限公司 一种媒体类型变更的方法、系统和装置
EP2342909B1 (en) * 2008-09-29 2015-11-11 Telefonaktiebolaget LM Ericsson (publ) Correlation of sessions in case of session transfer in ims domain
PL2351309T3 (pl) * 2008-10-03 2017-08-31 Telefonaktiebolaget Lm Ericsson (Publ) Ustanawianie sesji w sieci komunikacyjnej
CN101494648B (zh) * 2009-02-03 2012-01-25 华为终端有限公司 一种终端设备间媒体转移方法和网络设备
EP2461627B1 (en) * 2009-07-31 2018-10-17 Alcatel Lucent Terminal handover method, network element, device and system in non-stable voice over ip (voip) calling,
CN101997697B (zh) 2009-08-12 2012-06-20 华为终端有限公司 一种i1接口的业务控制方法和装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101009693A (zh) * 2006-01-24 2007-08-01 华为技术有限公司 在分组网络中实现综合业务数字网业务的系统和方法
CN101114985A (zh) * 2006-07-27 2008-01-30 华为技术有限公司 编解码转换系统及方法
EP2071839A1 (en) * 2006-09-25 2009-06-17 Huawei Technologies Co., Ltd. A method, a system and a device for channel authorization of television living broadcast by network

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN101997697B (zh) 2012-06-20
CN101997697A (zh) 2011-03-30
US20150016308A1 (en) 2015-01-15
EP2458781A1 (en) 2012-05-30
US20120144046A1 (en) 2012-06-07
EP2458781B1 (en) 2015-10-07
EP2458781A4 (en) 2013-03-13
US8886812B2 (en) 2014-11-11

Similar Documents

Publication Publication Date Title
TWI358930B (en) System and method for originating a sip call via a
EP2107714B1 (en) Method and apparatus for implementing a multimedia ring back tone service and multimedia caller identification service
US11431774B2 (en) Method, user equipment and application server for adding media stream of multimedia session
EP2458816B1 (en) Method and apparatuses for changing status of packet switched domain
WO2006099815A1 (fr) Procede d'enregistrement d'un utilisateur dans le sous-systeme multimedia ip et systeme associe
WO2023071915A1 (zh) 业务设置方法和装置、存储介质及电子设备
WO2009015525A1 (en) A method for switching the session control path of ip multimedia core network subsystem centralized service
US20150016308A1 (en) Method and apparatus for service control
US8411597B2 (en) Method, system and apparatus for setting up multimedia call
EP1914973B1 (en) System and method to provide combinational services to anonymous callers
US8817778B2 (en) Session processing method, device, and communication system
EP2472952B1 (en) Method for inter-ue media transfer and application server thereof
WO2009149635A1 (zh) 一种实现显式呼叫转移的方法、设备及移动通信系统
CN101227728B (zh) 一种多媒体会话连续性业务的会话合并方法
US20120081505A1 (en) Session transfer method and user equipment
WO2008052458A1 (fr) Procédé, système et terminal d'acquisition d'informations de caractères médiatiques.
CN110581853B (zh) 信令发送、接收方法及装置、存储介质、网络设备、终端
WO2009121310A1 (zh) 一种网关选择的方法、系统及设备
CN109120578B (zh) 一种实现链路连接处理的方法及装置
EP1998517B1 (en) METHOD AND aPPARATUS FOR CHANGING STATUS OF PACKET SWITCHED DOMAIN
KR102352982B1 (ko) 수신 단말의 통신 방법 및 수신 단말
US20090228596A1 (en) Method, server and terminal for implementing call directions
WO2010075719A1 (zh) 一种多媒体会话在接入网间转移的方法、装置及系统

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: 10807953

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2010807953

Country of ref document: EP