WO2008125018A1 - Procédé, système et dispositif pour distinguer une session - Google Patents

Procédé, système et dispositif pour distinguer une session Download PDF

Info

Publication number
WO2008125018A1
WO2008125018A1 PCT/CN2008/000777 CN2008000777W WO2008125018A1 WO 2008125018 A1 WO2008125018 A1 WO 2008125018A1 CN 2008000777 W CN2008000777 W CN 2008000777W WO 2008125018 A1 WO2008125018 A1 WO 2008125018A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
identification number
message
user terminal
network element
Prior art date
Application number
PCT/CN2008/000777
Other languages
English (en)
Chinese (zh)
Inventor
Dongming Zhu
Hengliang Zhang
Songhai Ye
Chunyan Ding
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
Priority claimed from CNA2007101296883A external-priority patent/CN101291322A/zh
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2008125018A1 publication Critical patent/WO2008125018A1/fr

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/1083—In-session procedures

Definitions

  • the present invention relates to the field of communications, and in particular, to a method, system and apparatus for distinguishing a session. Background technique
  • IP Multimedia Subsystem is a subsystem in the mobile switching network superimposed on the existing Packet Switched (PS) domain. It uses the packet switched domain for its upper layer control signaling and media transmission.
  • the bearer channel introduces the Session Initiation Protocol (SIP) as a service control protocol, and provides a rich multimedia service by separating the service control from the bearer control by using SIP simple, easy to expand, and convenient media combination;
  • SIP Session Initiation Protocol
  • the main functional entities include Call Session Control Function (CSCF), which controls user registration and session control functions, Application Server (AS), which provides various business logic control functions, and centralized management of user subscription data.
  • CSCF Call Session Control Function
  • AS Application Server
  • the Proxy-Call Session Control Function (P-CSCF) accesses the IMS, and the session and service trigger control and the service control interaction with the AS are performed by the Service-Call Session Control Function (S-CSCF). .
  • CS domain Circuit Switched
  • IMS and CS domains need to be interoperable.
  • the interworking between the IMS and the CS domain is implemented by the MGCF network element to convert the ISUP (ISDN User Part) signaling and SIP signaling.
  • ISUP ISDN User Part
  • the signaling between the IMS and the CS domain can be converted depends on the ISUP signaling, whether the SIP signaling has a corresponding message, the cells in the message can be mapped to each other, and whether the MGCF can convert the mapping.
  • the operator may wish to centrally deploy services in the IMS domain, whether through the CS domain or This service can be accessed through IMS domain access.
  • an ICCF IMS CS Control Function, IP Multimedia Subsystem Circuit Domain Control Function
  • IMS CS Control Function IP Multimedia Subsystem Circuit Domain Control Function
  • IMS domain SIP signaling IP Multimedia Subsystem Circuit Domain Control Function
  • user agent implement user control and interaction in the IMS domain. According to the deployment ICCF, it can also be serialized into the access path of the packet domain.
  • ICCC IMS CS Control Channel, IP Multimedia Subsystem Circuit Domain Control
  • ICCC IMS CS Control Channel, IP Multimedia Subsystem Circuit Domain Control
  • USSD Unstructed Supplementary Service Data
  • DT F Dual Tone Multi-Frequency
  • IP-CAN IP-Connectivity Access Network
  • VoIP Voice over IP
  • the air interface of the CS domain itself can only carry one voice call.
  • only one CS domain bearer is established between the ICCF and the UE, and the service control message for the session is transmitted by using the ICCC channel. .
  • the embodiment of the invention provides a method, a system and a device for distinguishing a session.
  • a user terminal has multiple sessions, each session between the user agent network element and the user terminal can be distinguished.
  • a method for distinguishing a session includes the following steps: a service indication message sent by the device when the service of the session indicates the interaction, the service indication message carries a session control identification number associated with the session; the second device obtains the session control identification number from the service indication message, and according to the Associations distinguish sessions.
  • a system for distinguishing a session includes: a first device, configured to: when a service indication interaction of a session is performed, send a service indication message carrying a session control identification number associated with the session; Obtaining a session control identification number from the service indication message sent by the first device, and distinguishing the session according to the association relationship.
  • a user terminal includes: a recording unit, configured to record an association relationship between the session and the session control identification number when the session is established; and a carrying unit, configured to perform between the user agent and the network element
  • the session control identification number associated with the session is obtained from the recording unit, and the session control identification number is carried in the service indication message sent to the user agent network element.
  • a user agent network element of the embodiment of the present invention includes: a recording unit, configured to record an association relationship between the session and the session control identification number when the session is established; and a carrying unit, configured to perform between the user terminal and the user terminal When the service of the session indicates the interaction, the session control identification number associated with the session is obtained from the recording unit, and the session control identification number is carried in the service indication message sent to the user terminal.
  • the second device receives the service indication message sent by the first device when the service indication interaction of the session is performed, where the service indication message carries the session control identification number associated with the session;
  • the session control identification number is obtained in the message, and the session can be distinguished according to the association relationship.
  • each session can be distinguished between the user agent network element and the user terminal.
  • FIG. 2 is a schematic structural diagram of a user terminal according to an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a user agent network element according to an embodiment of the present invention. 8 000777 FIG. 4 is a flowchart of Embodiment 1 of the present invention.
  • FIG. 5 is a flowchart of Embodiment 2 of the present invention.
  • FIG. 6 is a flowchart of Embodiment 3 of the present invention.
  • FIG. 7 is a flowchart of Embodiment 4 of the present invention.
  • FIG. 8 is a flowchart of Embodiment 5 of the present invention.
  • FIG. 9 is a flowchart of Embodiment 6 of the present invention.
  • FIG. 10 is a flowchart of Embodiment 7 of the present invention.
  • FIG. 11 is a flowchart of Embodiment 8 of the present invention.
  • FIG. 12 is a flowchart of Embodiment 9 of the present invention.
  • Figure 13 is a flow chart of Embodiment 10 of the present invention.
  • FIG. 14 is a flowchart of Embodiment 11 of the present invention.
  • FIG. 15 is a flowchart of Embodiment 12 of the present invention.
  • Figure 16 is a flowchart of Embodiment 13 of the present invention.
  • FIG. 17 is a flowchart of Embodiment 14 of the present invention.
  • FIG. 18 is a flowchart of Embodiment 15 of the present invention.
  • Figure 19 is a flowchart of Embodiment 16 of the present invention.
  • FIG. 20 is a flowchart of Embodiment 17 of the present invention.
  • FIG. 21 is a flowchart of Embodiment 18 of the present invention.
  • FIG. 22 is a flowchart of Embodiment 19 of the present invention.
  • Figure 23 is a flowchart of Embodiment 20 of the present invention.
  • FIG. 24 is a flowchart of Embodiment 21 of the present invention.
  • FIG. 25 is a flowchart of Embodiment 22 of the present invention
  • FIG. 26 is a flowchart of Embodiment 23 of the present invention.
  • Figure 27 is a flow chart of Embodiment 24 of the present invention.
  • Embodiment 29 is a flowchart of Embodiment 26 of the present invention.
  • Figure 30 is a flowchart of Embodiment 27 of the present invention
  • Figure 31 is a flowchart of Embodiment 28 of the present invention
  • Figure 32 is a flowchart of Embodiment 29 of the present invention.
  • Figure 33 is a flowchart of Embodiment 30 of the present invention.
  • Figure 34 is a flow chart of Embodiment 31 of the present invention. detailed description
  • the embodiment of the present invention provides a method for distinguishing the session. See Figure 1 for the following main steps:
  • the second device receives a service indication message sent by the first device when the service indication interaction of the session, where the service indication message carries a session control identification number associated with the session.
  • the first device is a user terminal, and the second device is a user agent network element; or the first device is a user agent network element, and the second device is a user terminal.
  • the session control identification number can be carried in the SIP message in one of the following ways:
  • Method 1 Add a new SIP message header field or parameter to carry the session control identification number;
  • Method 2 Carry the session control identification number in the SDP content of the SIP message;
  • Manner 3 The existing header field or parameter of the extended SIP message carries the session control identification number.
  • the second device acquires a session control identification number from the service indication message, and distinguishes the session according to the association relationship.
  • the embodiment of the invention further provides a system for distinguishing a session, comprising: a first device and a second device.
  • the first device is a user terminal, and the second device is a user agent network element; or the first device is a user agent network element, and the second device is a user terminal.
  • a first device configured to send a service indication message carrying a session control identifier associated with the session when the service indication interaction of the session is performed;
  • the second device is configured to obtain a session control identification number from the service indication message sent by the first device, and distinguish the session according to the association relationship.
  • An embodiment of the present invention further provides a user terminal, as shown in FIG. 2, which includes: And the carrying unit, further comprising: an allocating unit; or further comprising a receiving unit and an extracting unit in addition to the recording unit and the carrying unit; or further comprising an allocating unit, a receiving unit and an extracting unit in addition to the recording unit and the carrying unit.
  • a recording unit configured to record an association relationship between the session and the session control identification number when the session is established.
  • a carrying unit configured to acquire a session control identification number associated with the session from the recording unit when the service indication interaction is performed with the user agent network element, and carry the session control identification number to the user agent
  • the service indication message sent by the NE when the user terminal and the user agent network element perform the service indication interaction of the session in the IP-CAN, the carrying unit sends the service indication carrying the session control identification number associated with the session to the user agent network element by using the SIP message. A message to indicate a business operation on the session.
  • the carrying unit sends a service indication message carrying the session control identification number associated with the session to the user agent network element by using the ICCC message.
  • the carrying unit sends the service indication message that the carried session control identification number is empty to the user agent network element, to indicate that it is the default.
  • the business indication of the session is the case where the user terminal and the user agent network element perform the service indication interaction of the session in the circuit domain.
  • an allocating unit configured to allocate a session control identification number associated with the session when the session is established, and record it to the recording unit, and send the session control identification number to the user agent network element.
  • the user terminal establishes a session in the IP-CAN, and the allocation unit assigns a session control identification number and carries the SIP message to notify the user agent network element.
  • the user terminal establishes a session in the CS domain, and the allocation unit assigns a session control identification number and carries the user agent network element in the IP Multimedia Subsystem Circuit Domain Control Channel message.
  • the user terminal and the user agent network element establish a session in the circuit domain by means of Interworking, and the allocation unit and the user agent network element respectively assign the same session control identification number to the session.
  • the receiving unit is configured to receive a message sent by the user agent network element when the session is established.
  • an extracting unit configured to extract a session control identification number from the message received by the receiving unit, and submit the record to the recording unit.
  • the user terminal establishes a session in the IP-CAN, and the user agent network element The session control identification number is assigned and carried in the SIP message to notify the user terminal; then the session control identification number is obtained by the extraction unit.
  • the user terminal establishes a session in the CS domain, and the user agent network element allocates a tongue control identification number and carries it in the IP multimedia subsystem circuit domain control channel message to notify the user terminal; and then obtains session control by using the extraction unit. Identification Number.
  • the embodiment of the present invention further provides a user agent network element, which may be an ICCF.
  • the method includes: a recording unit and a carrying unit, and further includes: an allocating unit; or further than the recording unit and the carrying unit.
  • the receiving unit and the extracting unit are included; or the allocation unit, the receiving unit, and the extracting unit are further included in addition to the recording unit and the carrying unit.
  • a recording unit configured to record an association relationship between the session and the session control identification number when the session is established.
  • a carrying unit configured to: when the service indication interaction with the user terminal is performed, obtain a session control identification number associated with the session from the recording unit, and carry the session control identification number to the user terminal In the service indication message.
  • the carrying unit sends a service indication message carrying the session control identification number associated with the session to the user terminal by using the SIP message.
  • the carrying unit sends a service indication message carrying the session control identification number associated with the session to the user terminal by using the ICCC message to indicate Perform business operations on the session.
  • the carrying unit sends the service indication message that the carried session control identification number is empty to the user terminal, to indicate that the default session is Business instructions.
  • an allocating unit configured to allocate a session control identification number associated with the session when the session is established, and record it by the recording unit, and send the session control identification number to the user terminal.
  • the user terminal establishes a session in the IP-CAN, and the allocation unit assigns a session control identification number and carries the information in the SIP message to notify the user terminal.
  • the user terminal establishes a session in the CS domain, and the allocation unit assigns a session control identification number and carries the IP multimedia subsystem circuit domain control channel message to notify the user terminal.
  • the user terminal and the user agent network element pass in the circuit domain
  • the Interworking method establishes a session, and the allocation unit and the user terminal respectively assign the same session control identification number to the session.
  • the receiving unit is configured to receive a message sent by the user terminal when the session is established.
  • an extracting unit configured to extract a session control identification number from the message received by the receiving unit, and submit the record to the recording unit.
  • the user terminal establishes a session in the IP-CAN, and the user terminal allocates the session control identifier number and carries the SIP message to notify the user agent network element; and then obtains the session control identifier number through the extracting unit.
  • the user terminal establishes a session in the CS domain, and the user terminal allocates the session control identifier number and carries the user agent network element in the IP multimedia subsystem circuit domain control channel message; and then obtains the session control identifier number by using the extracting unit. .
  • Step 1-3 When the IP-CAN is accessed, the UE initiates a call to the B session, and the Invite message is routed to the DTF (Domain Transferring Function) according to the subscription information, and the session is completed in different access domains. Switching, for example, switching from the IP access domain to the CS domain); Step 4-5, the DTF finds that it is a new call at this time, and then continues to send to the called B, and assigns a handover identification number to the session;
  • DTF Domain Transferring Function
  • Step 6 after the DTF obtains the 183 response of the called B;
  • Step 7-9 the DTF adds the handover identification number of the session to the response message returned to the UE, and returns to the UE;
  • Step 10 The UE saves the obtained handover identification number.
  • the handover procedure can use any of Embodiments 15-18.
  • the following example of establishing a switchover identification number for a session is similar to this, and will not be described again.
  • the handover identification number is returned to the UE through the 183 response message, and the actual application may also return to the UE through other response messages, such as: 180 message, 200 OK message, etc.;
  • the header field or parameter of the SIP message is carried (for example, a new one is defined)
  • the header field DT-ID, or a new parameter Transfer-ID for the header field To can also be extended using the original header field or parameters (such as User-Agent or Server header field), or in text format.
  • the content of the SDP message is carried.
  • Step 1-2 The DTF receives a session request initiated by the peer user B to the local UE.
  • Step 3 The DTF allocates a handover identification number to the session.
  • Step 4-6 The DTF adds the handover identification number of the session to the Invite message, and sends the handover identification number to the UE.
  • Step 7 The UE saves the obtained handover identification number.
  • the switch identification number can be carried by newly defining a header field or parameter of a SIP message (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original
  • the header field or parameter is extended to carry (such as User-Agent or Server header field), and can also be carried by SDP message content in text format.
  • Step 1-4 The UE notifies the ICCF through the ICCC channel that a new session is to be established, and the ICCF allocates a specific control identifier to the session, and returns it to the ICCC response message.
  • UE the UE saves the session control identification number;
  • Step 5-11 The UE initiates a session establishment process to the user B in the CS domain, and the call is forwarded to the ICCF through the Camel redirect.
  • the ICCF triggers the IDP to the SCP (Service Control Point) according to the Camel.
  • the message recovers the real called user B;
  • Step 12-13 ICCF converts the Invite message to the request to invite User B, and this message is triggered to the DTF.
  • Step 14-16 the DTF assigns a session switch identification number to the session, and continues to send the request to the called user B.
  • Step 17-19 the DTF receives the response message of the called user B, and adds a handover flag to the response message. Recognize the number and continue to return.
  • Step 20 - 21 the ICCF receives the response message that the DTF adds the handover identification number, and then returns the session control identification number and the handover identification number to the UE by using the ICCC message channel.
  • Step 22 The UE associates with the previously saved session control identification number to obtain a correct association session of the handover identification number, and saves the handover identification number.
  • steps 5 - 11 can be omitted.
  • the response message can be returned to the UE through other response messages, such as: 180 message, 200 OK message, etc.;
  • the header field or parameter of the SIP message is carried (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To). It can also be extended by using the original header field or parameters (such as User- The Agent or Server header field can also be carried by the SDP message content in text format.
  • the SCP and ICCF in Figure 6 can be deployed in the same physical entity or separately. When deployed together, information is exchanged through internal interfaces; when deployed separately, information can be exchanged through existing protocols such as CAP, MAP, SIP, and private interfaces.
  • CAP CAP
  • MAP MAP
  • SIP Session Initiation Protocol
  • the subsequent ICCF carries the session control identifier in the ICCC notification to indicate which session is associated with the switch identifier number assigned by the DTF.
  • the session control identifier number can be used to distinguish and send multiple sessions
  • the ICCC message is used to perform message notification and service control for each session. For details, refer to Step 27-31 of Embodiment 19.
  • the session control identification number assigned in the remaining embodiments also has a similar effect, which will not be described below.
  • the assignment, delivery, and subsequent use of the session control identification number described in this example can be performed independently, without being affected by the assigned handover identification number, which is similar to the subsequent embodiments.
  • Step 1-4 The UE initiates a CS domain bearer establishment process to the ICCF in the CS domain.
  • step 5-8 the UE notifies the ICCF to establish a session to the called user B through the ICCC channel.
  • the ICCF allocates a specific control identifier to the session, and returns the message to the UE in the response message of the ICCC.
  • the UE saves the session. Control identification number;
  • Step 9-11 the ICCF obtains the real called user B from the ICCC notification, and converts to an Invite message sending request to invite the user B, and the message is triggered to the DTF;
  • Step 12-14 the DTF allocates a session switch identification number to the session, and continues to send the request to the called user B;
  • Step 15-17 the DTF receives the response message of the called user B, adds a handover identification number to the response message, and continues to return;
  • Step 18 - 19 the ICCF receives the response message that the DTF adds the handover identification number, and then returns the session control identification number and the handover identification number to the UE by using the ICCC message channel;
  • Step 20 The UE associates with the previously saved session control identification number to obtain a correct association session of the handover identification number, and saves the handover identification number.
  • steps 1 - 4 can be omitted.
  • the response message may be returned to the UE through other response messages, such as: 180 message, 200 OK message, etc.;
  • the header field or parameter of the SIP message is carried (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To). It can also be extended by using the original header field or parameters (such as User- The Agent or Server header field can also be carried by the SDP message content in text format.
  • Step 1-7 The UE initiates a session establishment process to the user B in the CS domain, and the call to the CSCF is redirected to the ICCF by the Camel, and the ICCF triggers the IDP message to the SCP according to the Camel.
  • the real called user B is recovered; the UE and the ICCF identify the session established through Interworking by using a special session control identification number (for example, fixed to 1) agreed by both parties.
  • Step 8-9 the ICCF converts to an Invite message sending request to invite the user B, and the message is triggered to the DTF;
  • Step 10-12 the DTF allocates a session switching identification number to the session, and continues to send the request to the called user B;
  • Step 13-15 the DTF receives the response message of the called user B, adds a handover identification number to the response message, and continues to return;
  • Step 16-17 The JCCF receives the response message that the DTF adds the handover identification number, and then uses the ICCC message channel to carry a special fixed session control identification number (for example, fixed to 1), and the handover identification number is returned to the UE;
  • a special fixed session control identification number for example, fixed to 1
  • Step 18 After obtaining the ICCF message, the UE is always associated with the CS domain session being established according to the fixed session control identifier number, thereby obtaining the association relationship between the handover identification number and the session and saving.
  • the special session control identification number may be fixed to a value agreed by an ICCF and the UE, or may be omitted in the ICCC message; and, in order to avoid confusion, the ICCF will reject the new one during the Interworking session. Conversation.
  • the response message may be returned to the UE through other response messages, such as: 180 message, 200 OK message, etc.;
  • the header field or parameter of the SIP message is carried (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To). It can also be extended by using the original header field or parameters (such as User- The Agent or Server header field can also be carried by the SDP message content in text format.
  • the UE transmits a -DTF allocation as a handover identification number of a called party establishing a session in the CS domain. See Figure 9 for a series of steps:
  • Step 1-2 The DTF receives a session request initiated by the peer user B to the local UE.
  • Step 3 The DTF assigns a handover identification number to the session;
  • Step 4 The DTF adds the handover identification number of the session in the Invite message;
  • Step 5 the Invite message is routed to the ICCF;
  • Step 6-7 the ICCF notifies the UE to establish a new session through the ICCC channel, and carries the session control identifier number and the handover identifier number;
  • Step 8 The UE saves the session control identification number corresponding to the session.
  • Step 9 the UE saves the handover identification number corresponding to the session
  • the switch identification number can be carried by newly defining a header field or parameter of a SIP message (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original
  • the header field or parameter is extended to carry (such as User-Agent or Server header field), and can also be carried by SDP message content in text format.
  • Step 1-4 When the UE accesses the IP-CAN, the user needs to initiate a call to the session of the B. At this time, the UE allocates a handover identification number to the session, and sends the handover identifier number in the Invite message.
  • step 5-6 the session establishment request is routed to the DTF.
  • the switch identifier is saved, and the identifier information is deleted from the Invite message and sent to the user B.
  • the switch identification number can be carried by newly defining a header field or parameter of a SIP message (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original
  • the header field or parameter is extended to carry (such as User-Agent or Server header field), and can also be carried by SDP message content in text format.
  • Step 1-5 The DTF receives a session request from the peer user B to the local UE, and continues to route to the UE;
  • Step 6 the UE allocates a handover identification number to the session
  • Step 7-9 The UE adds the handover identification number of the session to the SIP response message, and sends the identifier to the session.
  • DTF the handover identification number of the session
  • Step 10-11 The DTF saves the obtained handover identification number, and deletes the handover identification number information from the response message, and continues to return to the user B.
  • the response message can be returned to the UE through other response messages, such as: 180 message, 200 OK message, etc.;
  • the header field or parameter of the SIP message is carried (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To). It can also be extended by using the original header field or parameters (such as User- The Agent or Server header field can also be carried by the SDP message content in text format.
  • Step 1-2 When the UE accesses the CS domain, the user needs to initiate a call to the B session. At this time, the UE allocates a handover identification number to the session, and sends the handover identification number in the call setup request message. Depending on how the session is established, the UE can pass the session handoff identification number to the ICCF in a number of ways, and Embodiments 11-14 list several possible ways.
  • Step 3-4 The ICCF in the routing path receives the call request, and performs a conversion as needed to ensure that the handover identifier is carried in the SIP message and sent to the DTF.
  • step 5-6 the session establishment request is routed to the DTF.
  • the switch identifier is saved, and the identifier information is deleted from the Invite message and sent to the user B.
  • the manner in which the UE carries the handover identifier number to the ICCF may be an ICCC message, or may be carried to the ICCF through a UUI (User to User Information, user-to-user information, delivered by user-to-user signaling-UUS);
  • the switch identification number can be carried by newly defining a header field or parameter of a SIP message (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original header field or
  • the parameters are extended to carry (such as User-Agent. or Server header field), and can also be carried by SDP message content in text format.
  • the UE transmits, as the called party, a handover identification number to establish a session in the CS domain. See Figure 13, which includes a series of steps:
  • Step 1-5 The DTF receives a session request initiated by the peer user B to the local UE, and continues to be routed to the UE through the ICCF.
  • Step 6 the UE allocates a handover identification number to the session
  • Step 7 the UE adds the handover identification number of the session in the response message of the ICCC, and sends it to the ICCF;
  • Step 8-11 If the session needs to establish a CS domain bearer between the ICCF and the UE at the same time, the UE closes the Alerting response in the process of establishing the bearer;
  • Step 12 After receiving the response from the UE, the ICCF adds a handover identification number to the 180 message, and continues to return to the user B;
  • Step 13-15 The response message is routed to the DTF, and the DTF saves the obtained handover identification number, and deletes the handover identification number information from the response message, and continues to return to the user B.
  • step 8-11 may be omitted, and the handover identification number is directly returned in the ICCC response message.
  • the handover identification number is returned by the 180 response message.
  • other response messages can be returned to the UE, for example: 200 OK message, etc.;
  • the handover identification number can be newly defined by a header field of a SIP message.
  • parameter carrying (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original header field or parameter for extended carrying (such as User-Agent or Server header field) ), can also be carried by SDP message content in text format.
  • Step 1 The UE notifies the ICCF by carrying the session switching identification number through the ICCC channel;
  • Step 2-4 The ICCF obtains the handover identification number through the ICCC message; if the ICCC message is associated with an existing session, the ICCF also needs to obtain the correct session from the session control identification number in the ICCC message; and then use the session.
  • the SIP message carries a handover identification number to the DTF.
  • Step 1 The UE carries the UUI cell in the SETUP message that initiates the session, and the content of the UUI is the session switching identification number.
  • Step 2 The MSC triggers the Camel intelligent service, and the ICCF is notified to the ICCF through the SCP through the IDP message.
  • Step 3-6 The ICCF notifies the MSC to redirect the PSI number to the ICCF, and then routes to the ICCF through the CS domain and the IMS call to establish an interworking manner;
  • Step 7-9 the ICCF transmits the switching identifier number in the recorded IDP message to the SIP message carrying the handover identification number to notify the DTF;
  • This embodiment can be applied to step 2 in the ninth embodiment.
  • This embodiment can be applied to the transfer of the identification number (in steps 1-7) in the embodiment 17.
  • the handover identification number is switched to the session control identification number.
  • This embodiment can also be applied to transfer the session control identification number between the UE and the ICCF.
  • the UE transmits the handover identification number to the MGCF conversion mode of the ICCF-UUI. See Figure 16 for a series of steps:
  • Step 1-2 The UE carries the UUI cell in the SETUP message that initiates the session, and the content of the UUI is the session switching identifier number; after the MSC is forwarded to the MGCF;
  • Step 3 The MGCF converts the ISUP message carrying the UUI message to the SIP message.
  • Step 4-6 The SIP message is routed to the ICCF, and the ICCF determines that the UUI content carried by the SIP message is a conversion identification number, so the SIP field is converted to use other header fields.
  • the message carries the handover identification number to the DTF, or the UUI keeps the handover identification number notified to the DTF.
  • This embodiment can be applied to step 2 in the ninth embodiment.
  • This embodiment can be applied to the transfer of the identification number (in steps 1-7) in the embodiment 17. Switching the handover identification number to the session control identification number, this embodiment can also be applied to the UE and
  • the session control identification number is passed between the ICCFs.
  • Step 1-2 The UE carries the sub-address in the SETUP message that initiates the session, and the sub-address number is the session switch identification number; after the MSC passes, it is forwarded to the MGCF;
  • Step 3 The MGCF converts the ISUP message carrying the subaddress number to the SIP message;
  • Step 4-6 The SIP message is routed to the ICCF and forwarded to the DTF.
  • This embodiment can be applied to step 2 in the ninth embodiment.
  • This embodiment can be applied to the transfer of the identification number (in steps 1-7) in the embodiment 17.
  • the handover identification number is switched to the session control identification number.
  • This embodiment can also be applied to transfer the session control identification number between the UE and the ICCF.
  • the UE initiates a handover identification number carrying a session in a multi-session handover from IP-CAN to CS domain - USSD first interaction. See Figure 18 for a series of steps:
  • Step 1-4 The UE notifies the ICCF to establish a new session through the ICCC channel, and carries the handover identification number of the session. At this time, the ICCF allocates a specific control identifier to the session, and returns it to the UE in the response message of the ICCC. The UE saves the session control identification number;
  • Step 5-11 The UE initiates a session establishment process to the VDN number of the DTF in the CS domain, and the call to the CSCF is redirected to the ICCF by the Camel, and the ICCF recovers the real called according to the IDP message triggered by the Camel to the SCP. ;
  • Step 12-13 The ICCF converts the Invite message to the DTF, and carries the handover identification number sent by the UE.
  • Step 14 The DTF uses the VDN number of the Invite message and the switching identifier number carried by the DTF to determine that it is a handover request for an existing session leg.
  • Step 15 at this time, the DTF will update the access leg information, and initiate media negotiation with the peer user; Step 16, the DTF releases the old IP-CAN access leg.
  • steps 5 - 11 may be omitted.
  • the switch identification number can be carried by newly defining a header field or parameter of a SIP message (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original header field or
  • the parameters are extended and carried (such as the Replace header field), and can also be carried by the SDP message content in text format.
  • the UE initiates a handover identification number-PSI parallel carrying the message in the multi-session handover from the IP-CAN handover to the CS domain. See Figure 19 for a series of steps:
  • Step 1-4 The UE initiates a CS domain bearer establishment process to the ICCF in the CS domain.
  • step 5-8 the UE notifies the ICCF to establish a session to the VDN number of the DTF through the ICCC channel, and the ICCF allocates a specific control identifier to the session, and returns the message to the UE in the response message of the ICCC; the UE saves the session.
  • Control identification number
  • Step 9-11 the ICCF obtains the actual called VDN number from the notification of the ICCC, and converts it into an Invite message and carries the switching identification number to the DTF;
  • Step 12 The DTF passes the Invite message for its own VDN number and the carried switching identifier number to determine that it is a handover request for an existing session leg.
  • Step 13 At this point, the DTF will update the access leg information and initiate media negotiation with the peer user. Step 14. The DTF releases the old IP-CAN access leg.
  • steps 1 - 4 can be omitted.
  • the switch identification number can be carried by newly defining a header field or parameter of a SIP message (such as newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original header field or
  • the parameters are extended and carried (such as the Replace header field), and can also be carried by the SDP message content in text format.
  • Step 1 the UE initiates a call to the VDN number of the DTF in the CS domain, and carries the handover identification number through the UUI cell of the Setup message;
  • Step 2-7 the call is triggered by the Camel on the MSC and redirected to the CS domain call is routed to the ICCF.
  • the ICCF recovers the actual called VDN number according to the trigger of the Camel to the SCPIDP message, and the handover carried in the UUI. Identification Number;
  • Step 8-9 the ICCF converts to an Invite message and carries the switch identification number to the DTF;
  • Step 10 The DTF uses the VDN number of the Invite message and the carried handover identifier number to determine that the DFS message is a handover request to an existing session leg.
  • Step 11 At this time, the DTF updates the access leg information, and initiates media negotiation with the peer user. In step 12, the DTF releases the old IP-CAN access leg.
  • the switching identifier number can be carried by newly defining a SIP message or parameter (for example, newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original header.
  • the domain or parameter is extended and carried (such as the Replace header field), and can also be carried by the SDP message content in text format.
  • Step 1-3 The UE initiates a call to the DTF VDI number in the IP-CAN domain, and carries the switching identification number, and the Invite message is routed to the DTF according to the subscription information;
  • Step 4 The DTF passes the Invite message for the purpose of determining the switching request of an existing leg by the VDI number of the Invite message and the carried change identification number.
  • Step 5 At this point, the DTF will update the access leg information and initiate media negotiation with the peer user. Step 6. The DTF releases the old CS domain access leg.
  • the switching identifier number can be carried by newly defining a SIP message or parameter (for example, newly defining a header field DT-ID, or adding a parameter Transfer-ID to the header field To), or using the original header.
  • the domain or parameter is extended and carried (such as the Replace header field), and can also be carried by the SDP message content in text format.
  • This embodiment mainly describes the processing process of the ICCF to the media, and the handover initiation process may use any one of the foregoing embodiments.
  • Step 1-4 The UE initiates the first session switching request in the CS domain, carrying the switching identifier of the session AB, since there is no CS yet.
  • the domain bearer the UE initiates the establishment of the CS domain bearer at the same time, and the handover request is first routed to the ICCF;
  • Step 5 The ICCF carries the MGW media information in the CS domain bearer setup process, and the switch identifier number is sent to the DTF through the Invite message.
  • Step 6-13 The DTF identifies that the handover request is a session leg of the session A-B according to the handover identification number, so the media negotiation process initiated by the user B is released after the CS domain access leg is established.
  • the media of the session A-B establishes a connection through the CS domain bearer and is in an active state, and the media of the session A-C is still connected through the IP-CAN, and is in a hold state;
  • Step 14 The UE initiates a second handover request in the CS domain, and carries the handover identification number of the session A-C, and indicates that the session is in the HOLD state.
  • Step 15-17 After receiving the session switching request, the ICCF cannot directly establish a media connection with the UE-C by directly using the port of the MGW because the CS domain already has a session. Therefore, the ICCF needs to reach the parties on the MRS for the session. Apply for a port;
  • Step 18 The ICCF carries the media port information allocated to the UE-C, and specifies that the media attribute is Inactive, and the switching identifier number is sent to the DTF through the Invite message.
  • Step 19-26 the DTF identifies that the handover request is a session leg of the session AC according to the handover identification number, so initiates a media negotiation process with the user C, and releases the session leg of the IP-CAN after the CS domain access leg is established;
  • the media of the session A-B establishes a connection through the CS domain bearer and is in an active state.
  • the media of the session A-C only the UE-C and the MRS are connected, and are in a hold state;
  • Steps 27-31 the subsequent UE needs to talk with the user C, and the call with the user B is temporarily held. Therefore, the ICCC initiates the session supplementary service control HOLD request to the ICCF, where the control request carries the session control identification number of the session AB and requires Call hold, and the session control identification number of the session AC and request activation; after receiving the message, the ICCF redirects the MGW media to the MRS, and The media stream of the UE-B is redirected to the MRS and modified to the inactive state, and the media of the UE-C to the MRS is activated, and the port connected to the MGW and the UE-C in the MRS is connected.
  • the control request carries the session control identification number of the session AB and requires Call hold, and the session control identification number of the session AC and request activation
  • the media of the session A-C is connected and activated by the CS domain bearer and the MRS.
  • the media of the session A-B only UE-B and the MRS are connected, and are in a hold state.
  • the UE initiates the handover request in the CS domain is not limited to the manner in the figure, and may adopt any one of the foregoing establishment manners in the foregoing embodiments; the steps 15-17 may be performed in parallel in any order;
  • the MRFP is controlled by the MRFC, or the MGW is controlled by the MGCF.
  • the MRS in the figure is the MGW
  • the connection between the MGW and the MRS in the above process is an internal connection, and the steps can be omitted; the application is applied in the MRS as shown in the figure.
  • the port can be a separate port or a port connected to the same mix resource. When connecting to the port of the same mix resource, the process of connecting the port PC and the PM can be omitted.
  • the ICCF handles the media port when multiple sessions are switched from IP-CAN to CS.
  • the UE-A establishes two sessions with the UE-B and the UE-C in the CS domain, the session A-B is in the active state, and the session A-C is in the held state; as shown in FIG. 23, the series steps are included:
  • Step 1 the UE initiates a first session handover request on the IP-CAN, and carries the handover identification number of the session A-B;
  • Step 2-6 the DTF identifies that the handover request is a session leg of the session AB according to the handover identification number, so initiates a media negotiation process with the user B, and sends a Bye message to release the CS domain after the IP-CAN access leg is established.
  • Step 7-8 After receiving the Bye message, the ICCF releases the PB of the user B to the MRS in the original session AB of the CS domain, and notifies the UE-A through the ICCC channel carrying the session control identification number AB, and the session AB is released. ;
  • the media of session AB establishes an end-to-end connection through the IP-CAN bearer and is active.
  • the media of the session AC is still connected through the CS domain and the MRS connection, and is in a hold state.
  • Step 9 the UE initiates a second session handover request on the IP-CAN, carries the handover identification number of the session AC, and provides the media provided by the UE.
  • the middle indication is in the Inactive state;
  • Step 10-14 the DTF identifies that the handover request is a session leg of the session AC according to the handover identification number, so initiates a media negotiation process with the user C, and sends a Bye message to release the CS domain after the IP-CAN access leg is established.
  • Steps 15-19 after receiving the Bye message, the ICCF releases the port PC from the user C to the MRS in the original session AC of the CS domain; and after determining that the CS domain no longer exists, releasing the port PM connected to the MGW on the MRS. And sending a Bye message to the MGCF; after receiving the Bye message, the MGCF initiates media removal, and converts to an ISUP message to initiate session demolition to the circuit domain of the UE-A;
  • the media of the session AB establishes an end-to-end connection through the IP-CAN bearer and is in an active state.
  • the media of the session AC establishes an end-to-end connection through the IP-CAN bearer and is in an inactive state, and the bearer resources of the CS domain are all released. .
  • Step 1-2 The UE initiates a SIP Invite request to the B session in the PS domain, and the request is routed to the ICCF;
  • Step 3 The ICCF assigns a corresponding session control identification number to the session and saves it;
  • Step 4-5 The ICCF continues to send the session establishment request to the called B;
  • Step 6-7 The response message of the called B (such as SIP 183) is returned to the ICCF;
  • Step 8-9 The ICCF returns the session control identification number assigned to the session to the UE that initiated the session in the add response message.
  • Step 10 The UE saves the session control identification number corresponding to the session, so as to subsequently identify and control the session by using the session control identification number.
  • the ICCF waits until the called B end returns a response message, and adds the session control identification number to the message and returns the message to the UE that initiated the session.
  • the remaining methods may also include the ICCF passing the session control identifier immediately after the session control identifier is assigned. INFO messages or other SIP messages are returned to the UE, or It is returned to the UE in the subsequent 181 and other response messages.
  • the session control identifier can be carried by the header field or parameter of a newly defined SIP message (such as newly defining a header domain SC-ID, or adding a parameter SCtrl-ID to the header domain To), or using the original header field.
  • the parameter is extended and carried (such as User-Agent or Server header field), and can also be carried by SDP message content in text format.
  • the delivery of the subsequent embodiments is similar.
  • the session control identification number assigned by the ICCF may be different from the Call-ID in the SIP session message, or may be directly derived from or derived from the Call-ID in the SIP session message.
  • Step 1-2 The remote user B initiates a session directed to the subscriber, and the request (SIP Invite) is routed to the ICCF corresponding to the subscriber.
  • Step 3 The ICCF allocates a corresponding session control identification number to the session, and saves it;
  • Step 4-5 The ICCF continues to send the SIP Invite request established by the session to the UE of the subscriber, and carries the session control identification number;
  • Step 6 The UE saves the session control identification number corresponding to the session, so as to subsequently identify and control the session by using the session control identification number.
  • Step 1 The UE prepares to initiate a session, and assigns a session control identification number to the session in advance.
  • Step 2-3 The UE initiates a SIP Invite request to the session in the PS domain, and carries the session control identification number, and the request is routed to ICCF;
  • Step 4 The ICCF saves the session control identification number corresponding to the session, so that the session is identified and controlled by using the session control identification number.
  • Step 4 The remote user B initiates a session directed to the subscriber, and the request (SIP Invite) is routed to the ICCF corresponding to the subscriber, and the ICCF continues to send to the UE of the subscriber;
  • Step 5 The UE allocates a corresponding session control identification number to the session, and saves it.
  • Step 6-7 The UE carries the session control identification number in the response message, and returns to the ICCF.
  • Step 1 The UE prepares to initiate a session, and assigns a session control identification number to the session in advance.
  • Step 2 The UE initiates a session establishment request through the ICCC channel in the CS domain, and carries the session control identification number, and the request is routed to the ICCF. ;
  • Step 3 The ICCF saves the session control identification number corresponding to the session, so that the session is identified and controlled by using the session control identification number.
  • Step 4 If no CS bearer is established between the UE and the ICCF, a CS bearer is established between the UE and the ICCF.
  • the manner of CS bearer can be referred to any of the methods disclosed in the previous embodiments. If a CS bearer has been established between the UE and the ICCF, this step can be omitted.
  • Step 5 The ICCF continues to send SIP Invite messages to the peer to establish a session.
  • Step 1 The remote user B initiates a session directed to the subscriber, and the request (SIP Invite) is routed to the ICCF corresponding to the subscriber;
  • Step 2 The ICCF sends a session establishment request to the UE of the subscriber through the ICCC channel.
  • Step 3 If the CS bearer is not established between the UE and the ICCF, the CS bearer is established between the UE and the ICCF.
  • the manner of CS bearer can be referred to any of the methods disclosed in the previous embodiments. If a CS bearer has been established between the UE and the ICCF, this step can be omitted.
  • Step 4 The UE allocates a corresponding session control identification number to the session, and saves;
  • Step 5 The UE carries the session control identification number in the response message of the ICCC channel, and returns to the ICCF;
  • Step 6 The ICCF saves the session control identification number corresponding to the session, so as to use the session control subsequently.
  • the identification number identifies and controls the session.
  • the UE obtains the configuration or other means in advance, if the ICCF does not assign the session control identification number to the session and notifies the UE, the UE uses the same null value (or other default value) as that configured on the ICCF as the default session control of the session. Identification Number.
  • Step 1 The ICCF receives a session request initiated by the peer user B to the local UE-A.
  • Step 2 The VCC AS determines that the UE-A has no session or other decision result at this time, and does not assign an explicit to the session.
  • the session controls the identification number, but uses the default null value as the session control identification number for the session.
  • the default session control identification number is not notified to the UE.
  • Step 3 The ICCF sends the call request to the UE.
  • the call request may be sent in the CS domain through the Interworking mode or the USSD interaction, or may be delivered in the PS domain through the SIP Invite message.
  • the default session control identification number of the session is not included in the call setup request (the message may not carry the parameter identifying the session control identifier, or carry the parameter but the value of the parameter is null).
  • Step 4 UE-A receives a new session establishment request, and at this time, ICCF does not assign a session control identification number to the session, so UE-A similarly uses the default null value as the session control identification number of the session.
  • Step 5 The UE-A completes the bearer and session establishment process by using the access domain, the ICCF, and the like, and the Remote-B.
  • Step 6 the ICCF receives another session request initiated by the remote user Remote-C to the local UE-A;
  • Step 7 ICCF assigns a session control identification number CID1 to the session;
  • Step 8 The ICCF notifies the UE-A to establish a new session, and the session control identification number CID1 corresponding to the session.
  • the message may be sent in the CS domain through the USSD or other ICCC message according to the domain selection result and the policy. Or the SIP domain sends the message through the SIP Invite message.
  • Step 9 After receiving the notification of the allocation session control identifier of the ICCF, the UE-A saves the session control identification number CID1 corresponding to the session (the session between the UE-A and the Remote-C).
  • Step 10 Due to the limitation of the capability on the UE-A (for example, only one microphone and the handset can only talk to one party at the same time), the UE-A decides to hold the session originally established with the Remote-B and then answer the Remote-C. Come. At this time, the UE-A sends a Hold service operation request to the ICCF, where the request does not carry the session control identification number (the message may not carry the parameter identifying the session control identification number, or carries the parameter but the value of the parameter is null). Indicates that the default session is controlled.
  • the request message may be sent by SIP message through the PS domain or by ICCC message of the CS domain.
  • Step 11 after receiving the service operation request of the UE-A, the ICCF matches the session according to the carried session control identification number.
  • the Hold service operation request does not carry the session control identification number, so the ICCF knows that the default session is operated, that is, the session between UE-A and Remote-B;
  • Step 12 The ICCF converts the SIP command and the service AS, the UE-A, and the Remote-B according to the need to complete the call hold of the session between the UE-A and the Remote-B.
  • Step 13 after the call is held for the session between the Remote-B, the UE-A decides to connect to the new session of the Remote-C, and then sends a response to the ICCF, and the response includes a session with the Remote-C.
  • the connection response is selected according to the downlink channel of step 8, which may be a response in the CS domain through USSD or other ICCC messages; or a response in the PS domain through a message such as SIP 180.
  • Step 14 The establishment process of UE-A and Remote-C new sessions.
  • the order in which two sessions are established in this embodiment may be in parallel or in any order.
  • This embodiment only describes the case where the ICCF explicitly assigns a session control identification number to a session, but the same applies to the case of UE allocation.
  • Step 1 UE-A is in a wireless access environment that can be covered by both 2G GRPS and CS.
  • UE-A The session control identification number is AB, using 2G GPRS as the ICCC channel and one of the sessions established by the peer UE-B.
  • the session establishment, the session control identification number assignment process, and the bearer establishment process may be performed using any of the methods disclosed in the foregoing embodiments, and are omitted here.
  • Step 2 Since the radio access environment of UE-A changes, 2G GPRS is not available, but CS still covers normally, so UE-A and ICCF switch to use USSD message of circuit domain as ICCC channel.
  • Step 3 The user decides to temporarily hold the session between the live and the remote UE-B.
  • the UE-A sends a HOLD service operation request through the ICCC channel of the switched USSD message, and carries the session control identification number AB corresponding to the session.
  • Step 4 After receiving the request message, the ICCF obtains the service control of the session by using the session control identifier A-B in the message, and then initiates a HOLD service interaction between the UE and the remote UE-B to complete the HOLD request.
  • Step 1 UE-A establishes a conference site. Since the conference site is also equivalent to one session for UE-A, the same session control identifier number is also assigned between ICCF and UE-A: AD; Step 2: The UE-A wants to add the session AB to the conference site, so the request for inviting the user to join the conference is sent through the ICCC channel and carries the session control identifier number AB;
  • Step 3 After the request is routed to the ICCF, the ICCF invites the UE-B of the remote user to join the conference by sending a Refer message in the corresponding session A-B according to the session control identification number in the request;
  • Step 4-5 After the participant joins the site successfully, the remote user UE-B returns a notification of the success of the joining site (SIP NOTIFY message); the ICCF carries the session control identifier number AB through the ICCC channel message, and notifies the UE-A that the other party has successfully joined the site;
  • Step 6-7 After receiving the notification that the other party has successfully joined the site, the UE-A initiates the release of the release of the original session AB.
  • the ICCF requests the session control identification number in the request, and sends a SIP Bye message to the peer in the corresponding session AB.
  • Step 8-13 In the similar way to step 2-7, invite the UE-C of the remote user to join the site.
  • the session A-B is established, and the A-C can be established in the CS domain or in the PS domain.
  • the session control identification number can be assigned only in the CS access domain and the session identification and control can be completed.
  • the session control identification number can be assigned to the session and the session can be completed in both the CS domain and the PS. Identification and control.
  • the UE-A establishes a site by establishing an existing method in the PS domain by directly sending a SIP Invite to a Conf AS.
  • the CS domain may first send a request to the ICCF through the ICCC channel, and then the ICCF passes the existing Method to establish a venue.
  • the UE-A is required to join the existing session user to the site through the ICCC channel.
  • the user can join the site by sending a SIP Refer message to the site server or the peer in the PS domain. .
  • the ICCF returns the response that the peer has successfully joined the conference to the UE-A through the ICCC channel, and can also directly return the SIP NOTIFY to the UE-A notification result in the PS domain, and other existing SIP notification method, such as sending NOTIFY/Message.
  • the conference is used as an example to describe how to control the service by using the session control identifier.
  • Other services such as call forwarding, call hold, activation, etc. can be easily implemented in a similar manner, and no longer— - Description.
  • Step 1 UE-A requests to establish a session through the ICCC channel, and the message is delivered to the ICCF.
  • Step 2 The ICCF assigns a session control identification number to the session, and assigns an IMRN number to the ICCF itself, and establishes the session control identification number. Correspondence relationship with the IMRN number;
  • Step 3 The ICCF returns the session control identification number and the IMRN to the UE-A through the ICCC channel;
  • Step 4-5 The UE-A saves the session control identification number corresponding to the session, and uses the CS domain in the CS domain.
  • the allocated IMRN initiates a SETUP call request as the called number, and establishes a CS bearer;
  • Step 6 Since the IMRN is the called number pointing to the ICCF, the establishment of this CS bearer is requested.
  • the ICCF is informed by the IMRN that the CS bearer is the bearer corresponding to the previous session establishment request. After obtaining the correspondence, the ICCF can use the bearer media information in the call setup process and subsequent service control. Negotiate with the peer.
  • the allocation session control identification number in the step can be omitted.
  • Step 1 UE-A requests to establish a session through the ICCC channel, where the message carries the calling identity of UE-A, and the message is delivered to the ICCF;
  • Step 2 The ICCF allocates a session control identifier to the session, records the identifier of the UE-A, and records the correspondence between the identifier of the UE-A and the session control identifier.
  • Step 3-4 The ICCF returns a session control identification number to the UE, and the UE saves;
  • Step 5 The UE initiates a SETUP to establish a CS bearer in the CS domain.
  • the called party may be a relatively fixed number pointing to the ICCF, or may be the current called number and redirected from the network to the ICCF, and the calling party is the identity of the UE-A itself. .
  • the specific process has been described in the foregoing embodiments.
  • Step 6 The ICCF passes the caller ID of the CS bearer and the caller ID in the ICCC session request, and the correspondence between the session and the bearer is obtained according to the same or the corresponding relationship between the two caller IDs. After the correspondence is obtained, The ICCF can use the hosted media information to perform operations such as peer negotiation in the call setup process and in subsequent service control.
  • the allocation session control identification number in the step can be omitted.
  • the calling identifiers described in this example may be IMSI, MSISDN, IMPU, and the like.
  • the user terminal and the user agent network element record the association relationship between the session and the session control identification number when the session is established; after that, the user terminal and the user agent
  • the one of the other party sends a service indication message carrying the session control identification number associated with the session; therefore, the other party can obtain the session control identification number from the service indication message.
  • distinguishing sessions according to the association relationship in the case that the user terminal has multiple sessions, each session can be distinguished between the user agent network element and the user terminal.
  • the embodiment of the invention further provides a system for distinguishing tongues, a user terminal and a user agent network element to better support the invention.
  • the embodiment of the present invention further discloses various ways of assigning a session control identification number, a delivery session control identification number, and a relationship between a recording session and a session control identification number, thereby better supporting the present invention.
  • IMS is a description of 3GPP, and a similar multimedia subsystem exists in 3GPP2 and TISPAN.
  • the description is only for IMS, but it is obvious that the described method is also applicable to 3GPP2 and TISPAN. system.
  • the spirit and scope of the invention Thus, it is intended that the present invention cover the modifications and variations of the inventions

Landscapes

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

Abstract

Cette invention concerne un procédé, un système et un dispositif permettant de distinguer une session. Selon le mode de réalisation, chaque session entre l'élément de réseau de l'agent utilisateur et le terminal utilisateur peut être distinguée à condition que le terminal utilisateur comprennent plusieurs sessions. Le procédé comprend les étapes suivantes: le second appareil reçoit le message d'indication de service transmis par le premier appareil durant l'interaction d'indication de service de la session (S1), le message d'indication de service contient un identifiant de commande de session associé à la session; le second appareil obtient l'identifiant de commande de session à partir du message d'indication de service, et il distingue la session en fonction de la relation (S2). Le système comprend: le premier appareil qui est utilisé pour transmettre un message d'indication de service contenant un identifiant de commande de session associé à la session pendant l'interaction d'indication de service de la session; et le second appareil qui est utilisé pour obtenir l'identifiant de commande session à partir du message d'indication de service transmis par le premier appareil, et pour distinguer la session en fonction de la relation.
PCT/CN2008/000777 2007-04-17 2008-04-16 Procédé, système et dispositif pour distinguer une session WO2008125018A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710100497 2007-04-17
CN200710100497.4 2007-04-17
CN200710129688.3 2007-08-17
CNA2007101296883A CN101291322A (zh) 2007-04-17 2007-08-17 一种区分会话的方法、系统及装置

Publications (1)

Publication Number Publication Date
WO2008125018A1 true WO2008125018A1 (fr) 2008-10-23

Family

ID=39863253

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/000777 WO2008125018A1 (fr) 2007-04-17 2008-04-16 Procédé, système et dispositif pour distinguer une session

Country Status (1)

Country Link
WO (1) WO2008125018A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1595937A (zh) * 2004-06-23 2005-03-16 中国电信股份有限公司研究院 一种会话初始协议电话终端中的用户注册和通话方法
JP2006087133A (ja) * 2003-11-12 2006-03-30 Hitachi Ltd セッションＱｏＳ制御装置
CN1852596A (zh) * 2005-11-30 2006-10-25 华为技术有限公司 区分业务级别发送寻呼消息的方法和系统
WO2006125474A1 (fr) * 2005-05-27 2006-11-30 Telefonaktiebolaget Lm Ericsson (Publ) Transfert d'appel dans un sous-systeme multimedia ip (ims)
WO2007039006A1 (fr) * 2005-09-29 2007-04-12 Matsushita Electric Industrial Co., Ltd. Commande de politique dans une architecture systeme evoluee

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2006087133A (ja) * 2003-11-12 2006-03-30 Hitachi Ltd セッションＱｏＳ制御装置
CN1595937A (zh) * 2004-06-23 2005-03-16 中国电信股份有限公司研究院 一种会话初始协议电话终端中的用户注册和通话方法
WO2006125474A1 (fr) * 2005-05-27 2006-11-30 Telefonaktiebolaget Lm Ericsson (Publ) Transfert d'appel dans un sous-systeme multimedia ip (ims)
WO2007039006A1 (fr) * 2005-09-29 2007-04-12 Matsushita Electric Industrial Co., Ltd. Commande de politique dans une architecture systeme evoluee
CN1852596A (zh) * 2005-11-30 2006-10-25 华为技术有限公司 区分业务级别发送寻呼消息的方法和系统

Similar Documents

Publication Publication Date Title
US8155084B2 (en) User equipment, call continuity application server, and network handover method
US8594013B2 (en) System, method and apparatus for implementing multimedia call continuity
EP2173068B1 (fr) Procédé, serveur d'application et dispositif utilisateur pour transférer le flux multimédia de la session multimédia
KR101489529B1 (ko) 착신된 음성/비디오 호를 위한 ｕｅ 접근 도메인 선택 방법
US8824410B2 (en) Method for operating a network and a network
WO2008064565A1 (fr) Système, procédé et dispositifs pour réaliser la continuité de session multimédia
EP1770949A2 (fr) Méthode et système de communication permettant aux utilisateurs d'un système de communications de circuits l'accès à un sou-système IP multimédia (IMS)
EP2247031B1 (fr) Procédé de mise en oeuvre, système et dispositif pour surveillance ims
EP1737188A2 (fr) Procédé et appareil pour joindre des sessions de communication afin de former une connexion de communication, et procédé de transfert transparent entre services cellulaires et services à paquets sans fil
WO2006063536A1 (fr) Procede et systeme pour maintenir la continuite d'une session
JP2010517411A (ja) 異種無線通信ネットワークにおけるハンドオーバー装置及び方法
WO2008028416A1 (fr) Procédé de commande de transfert intercellulaire d'appel et système de communication mettant en oeuvre ce procédé et dispositif utilisateur
WO2007009298A1 (fr) Appareil et méthode permettant à un terminal traditionnel d’accéder à un système ims
WO2008046319A1 (fr) Procédé et système pour assurer la continuité d'un appel vocal lors de la gestion d'une affaire urgente
WO2009024081A1 (fr) Procédé, dispositif et système pour traiter la continuité du flux multimédia dans une session
WO2009012665A1 (fr) Procédé pour assurer une continuité d'appel multimédia, équipement et système associés
WO2007025429A1 (fr) Procede evitant la derivation du flux media et dispositif correspondant
KR20060113284A (ko) 이종망간에 음성 서비스를 지원하는 아이엠에스 시스템 및그에 따른 호 설정 방법
US8320363B2 (en) Implementation method, system and device of IMS interception
WO2009149667A1 (fr) Procédé, dispositif et système d'accès pour appelé
WO2008116386A1 (fr) Procédé, système et dispositif pour fournir un service multi-session à des abonnés
CN101291322A (zh) 一种区分会话的方法、系统及装置
EP2094026B1 (fr) Procédé, système et dispositif pour la commutation de domaine
WO2008040171A1 (fr) Procédé, système de domaine de commutation de circuits apercevant des informations de sessions multimédia du domaine ims
WO2008125018A1 (fr) Procédé, système et dispositif pour distinguer une session

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 08733975

Country of ref document: EP

Kind code of ref document: A1