WO2006034658A1 - Procede et systeme de realisation de communication - Google Patents

Procede et systeme de realisation de communication Download PDF

Info

Publication number
WO2006034658A1
WO2006034658A1 PCT/CN2005/001635 CN2005001635W WO2006034658A1 WO 2006034658 A1 WO2006034658 A1 WO 2006034658A1 CN 2005001635 W CN2005001635 W CN 2005001635W WO 2006034658 A1 WO2006034658 A1 WO 2006034658A1
Authority
WO
WIPO (PCT)
Prior art keywords
ims
domain
call
bearer
session
Prior art date
Application number
PCT/CN2005/001635
Other languages
English (en)
French (fr)
Inventor
Jiongjiong Gu
Dongming Zhu
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 CNB2004100848248A external-priority patent/CN1297124C/zh
Priority claimed from CNB2005100026182A external-priority patent/CN100352295C/zh
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP05802141A priority Critical patent/EP1744569B1/en
Priority to DE602005012817T priority patent/DE602005012817D1/de
Publication of WO2006034658A1 publication Critical patent/WO2006034658A1/zh
Priority to US11/562,237 priority patent/US8089956B2/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/10Architectures or entities
    • H04L65/1016IP multimedia subsystem [IMS]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/64Hybrid switching systems
    • H04L12/6418Hybrid transport
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1069Session establishment or de-establishment
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/1066Session management
    • H04L65/1083In-session procedures
    • H04L65/1095Inter-network session transfer or sharing

Definitions

  • the present invention relates to a comprehensive circuit switched bearer (CSI) technology for integrated circuit switched bearers and IP multimedia subsystem services in a third generation mobile communication network, and more particularly to a method and system for ensuring communication between CSI terminals.
  • CSI circuit switched bearer
  • IMS IP Multimedia Subsystem
  • the traditional communication network is divided into a circuit switched domain (CS) and a packet switched domain (PS), which respectively perform circuit switching services (including voice services, circuit type data services, faxes, etc.) and packet data services. Both the signaling and media streams in the IMS are carried over the PS. Because CS and PS handle different network resources, CS is an exclusive resource type, and PS is a shared resource type. Therefore, for services with higher real-time requirements, such as voice services, IMS implementation adopts PS bearer transmission compared with CS. The amount of service shields carrying the transmissions will be significantly reduced, thus failing to meet the business needs of operators and users.
  • the International Organization for Standardization proposes an integrated service CSI that combines a CS bearer with an IMS service, that is, a multimedia service is implemented by combining a PS bearer and a CS bearer, and a voice service with high real-time requirements is still Through the CS bearer, other services with low real-time requirements, such as pictures and message services, are uniformly controlled by the PS bearer and the IMS.
  • FIG. 1 is a schematic diagram of a CSI service that implements a CS bearer and an IMS service.
  • CSI services and multimedia provided by IMS in user operations The service is basically the same, but in terms of delivery delay, etc., the media stream part with higher real-time requirements in the integrated service adopts the CS bearer and has been greatly improved.
  • FIG. 2 is a schematic diagram of the logical functional framework for implementing CSI services.
  • three logical functional entities including a circuit bearer control function (CBCF), a circuit bearer origination function (CBOF), and a circuit bearer termination function (CBTF) are included in the logical function framework of the alternative proposed by 3GPP TS 23.899.
  • the CBCF judges and controls the establishment of the CS bearer between the CBOF and the CBTF in the IMS service.
  • the three functional entities can be implemented in the original IMS entity, such as the terminal (UE) and the application server (AS).
  • the specific distribution is negotiated during the session establishment process, and the CBOF or CBTF can also be a SIP user agent.
  • the CBOF or CBTF can also be a SIP user agent.
  • the meaning of establishing a CS bearer between them is to establish a CS bearer between the peer end and a CS domain and an IMS domain interworking gateway on behalf of it.
  • the terminal proposed in the 3GPP TS 23.899 standard proposes two different modes: terminal-to-terminal and terminal-to-gateway for implementing CSI services.
  • the direction in which CS bearers are established may be terminal-to-network or vice versa. It has nothing to do with the actual established IMS session direction.
  • the 3GPP TS 23.899 standard also proposes the principles that the CSI implementation should follow and the problems that need to be solved. For example, the implementation of the requirements should be limited to terminals that affect IMS and CSI, other network elements, terminals, and IMS and other networks. Intercommunication orders should be unaffected, CS/PS/IMS charging associations should be provided, and billing consistency for end users should be ensured, and so on.
  • the implementation of the CSI service requires both the terminal and the network to support the ability to maintain the CS and PS air interface connections at the same time, and the network capability varies depending on the current access network of the terminal, therefore, for the CSI service, if the CSI terminal receives When a CSI call is made, the radio access network connected to the CSI terminal cannot be connected to the air interface of the CS and the PS at the same time. That is, when the CSI terminal cannot continue the subsequent CSI service, the communication of the CSI terminal should be performed. What kind of business processing, there is no specific solution at present. It can be seen that how to ensure communication between CSI terminals has become an urgent problem to be solved. Summary of the invention
  • a primary object of the present invention is to provide a method of implementing communication, and another object of the present invention is to provide a system for implementing communication, thereby ensuring that a CSI terminal can implement communication.
  • a method of implementing communication comprising:
  • the IMS terminal module in the integrated service CSI terminal IMS TM indicates that the CS terminal module CS TM in the CSI terminal initiates the CS bearer establishment;
  • CS TM sends the call setup request to the CS domain call control entity as the called IMS TM;
  • the C. CS domain call control entity routes the call setup request to the CS domain and the IMS domain interworking gateway according to the called number information in the received call setup request;
  • the CS domain and the IMS domain interworking gateway convert the received call setup request into an IMS session establishment request and send it to the IMS TM;
  • the method further includes: determining, by the IMS, whether the media stream required to be exchanged by the IMS service includes a media stream that needs to be transmitted by using the CS bearer, and if yes, performing step A.
  • the method further comprises: IMSTM determining whether the condition for implementing the CSI service is currently met, and if so, performing step A.
  • the step of determining whether the IMS TM currently meets the CSI service condition includes: The IMS TM determines whether the cell that the UE is connected has the capability of maintaining the CS and PS air interface connection at the same time, and if yes, determines that the condition for implementing the CSI service is currently met.
  • the IMS TM After the IMS TM determines that the cell to which the cell is connected has the capability of maintaining the connection between the CS and the PS air interface, and before determining that the condition for implementing the CSI service is satisfied, the IMS TM further includes: determining, by the IMS TM, whether the confirmed user intention is The CSI service is performed, and if so, it is judged that the condition for implementing the CSI service is currently satisfied.
  • the manner in which the IMS(TM) confirms the user's will includes: The IMS(TM) determines the user's willingness by providing a specific user interface and receiving the user-entered service implementation, or the IMS(TM) is determined based on the service implementation set by the user in advance.
  • the step A further includes: the IMS TM providing the bearer capability indication information required by the session to the CS TM;
  • the call setup request carries the bearer capability indication information provided by the IMS TM.
  • the step D further includes: the CS domain and the IMS domain interworking gateway according to the bearer capability indication carried in the call setup request Information reservation includes IP port resources of IP address and UDP port;
  • step D the CS domain and the IMS domain interworking gateway send an IMS session establishment request.
  • the step of sending to the IMS TM includes: the CS domain and the IMS domain interworking gateway carrying the IP address and UDP port information of the reserved IP port resource in the IMS session establishment request and sent to the IMS TM;
  • the step E includes: the IMS TM processes the two sessions between the peer and the CS domain and the IMS domain interworking gateway in a back-to-back SIP user agent B2BUA mode, and the B2BUA mode association process includes:
  • the IMS TM obtains the session description protocol indication from the received IMS session establishment request, and uses the obtained session description protocol indication as the local description of the media stream that is applied by the CS in the corresponding IMS session, and the processing and the peer end
  • the IMS domain session establishment process ; and the IMS terminal module uses the session description protocol indication of the peer end of the media stream applied for the CS bearer obtained during the IMS session establishment process with the peer end, as the local session description protocol indication, processing Establishing an IMS domain session between the CS domain and the IMS domain interworking gateway, establishing an IMS session connection between the UE and the peer, and establishing an IMS and CS interworking call connection between the CS domain and the IMS domain interworking gateway to the CS TM, and thereby
  • the CS domain and the IMS domain interworking gateway and the peer end use the reserved IP port resource to exchange the media stream carried by the CS in the CSI terminal and the inter-terminal IMS session, and the CS-bearing media stream passes through the CS
  • the method further includes: pre-assigning CS TM to the mobile station International ISDN ( MSISDN ) number that the CS TM is contracted in the CS domain;
  • the method further includes: the IMS (TM) acquiring the MSISDN number of the CSTM; the step D further comprising: the CS domain and the IMS domain interworking gateway acquiring the MSISDN number of the CSTM according to the calling number in the call setup request, and
  • the IMS session setup request from the IMS TM carries the MSISDN number of the acquired CS TM from the header field;
  • the method further comprises: the IMS TM from the received IMS session establishment request From Obtaining CS TM MSISDN in the header field The number is judged whether the currently acquired MSISDN number of the CS TM is the same as the MSISDN number of the CS TM acquired in step A, and if yes, the step of performing the association process is continued.
  • step A the IMS TM acquires the MSISDN of the CS TM through a real-time interaction or a pre-interaction process with the CS TM, where
  • the obtaining by real-time interaction includes: the IMS TM first initiates a request to the CS TM through an interface between itself and the CS TM, and after receiving the request, the CS TM sends its own MSISDN to the IMS TM, and the IMS TM acquires the CS TM MSISDN;
  • the obtaining by pre-interaction includes: when the IMSTM and the CSTM are started, the IMSTM initiates a request to the CSTM, and after receiving the request, the CSTM sends its own MSISDN to the IMSTM, and the IMSTM saves the received MSISDN. In its own cache, and currently obtain the saved MSISDN of the CS TM from its own cache;
  • the obtaining comprises: the IMS TM acquiring the MSISDN of the CS TM from the shared data area.
  • the method further includes: pre-assigning an E.164 number to the IMSTM, and configuring the called analysis data for the E.164 number of the IMS(TM) in the CS domain call control entity;
  • step A the IMSTM provides an E.164 number assigned to the IMSTM upon instructing the CSTM to initiate the CS bearer setup;
  • the step A further includes: A0, CSTM acquiring the E.164 number of the IMSTM; the step B includes: the CSTM transmitting the acquired E.164 number of the IMSTM as the called number in the call setup request to the CS domain call control entity;
  • step C the CS domain call control entity routes the call setup request to the CS domain based on the E.164 number of the IMSTM as the called number and the configured called analysis data. Interwork with the IMS domain gateway.
  • the IMS TM and the CS TM are disposed in different terminals;
  • the step A includes: the IMS TM sends a CS bearer setup request carrying its own E.164 number to the CS TM;
  • the step AO includes: the CSTM acquires the E.164 number of the IMSTM from the CS bearer setup request.
  • the IMS TM and the CS TM terminal are integrated in the same terminal;
  • the step A includes: the IMS TM instructs the CS TM to initiate a CS bearer setup by an internal instruction;
  • the step AO comprises: CS TM obtaining the E.164 number of the IMS TM from an internal command or from a shared data area of the IMS TM .
  • the E.164 number of the IMS TM includes an area identification prefix or a service type prefix; in step C, the CS domain call control entity further identifies a prefix or a service type prefix according to an area in an E.164 number of the IMS TM
  • the analysis sends a call setup request to the CS domain of the IMS TM home zone and the IMS domain interworking gateway or the closer CS domain and IMS domain interworking gateway.
  • the method further includes: pre-setting conversion data of the E.164 number of the IMS TM and its initial session protocol uniform resource locator SIP URI;
  • the step D further includes: the CS domain and the IMS domain interworking gateway make a call according to the E.164 number of the IMS TM as the called number carried in the call setup request.
  • An address mapping (ENUM) server query obtaining an initial session protocol uniform resource locator SIP URI of the IMS TM through the set conversion data;
  • step D the CS domain and the IMS domain interworking gateway convert the call setup request into an IMS according to the obtained initial session protocol Uniform Resource Locator SIP URI of the IMSTM.
  • the request is sent to the IMS TM after the request is established.
  • step D the step of performing the ENUM server query by the CS domain and the IMS domain interworking gateway further includes: determining, by the CS domain and the IMS domain interworking gateway, whether the E.164 number of the IMS TM in the call setup request exists correspondingly according to the query result Converting the data, if yes, determining that the current CSI service is legal, and continuing to perform the step of acquiring the initial session protocol uniform resource locator SIP URI of the IMSTM by corresponding conversion data, otherwise, ending the current process.
  • the step A further includes: the IMS TM providing its initial session protocol uniform resource locator SIP URI address to the CS TM;
  • the step B further includes: the CSTM transmitting the user-to-user information cell carrying the SIP URI address to the CS domain call control entity;
  • the step C further includes: the CS domain call control entity sends the user-to-user information cell carrying the SIP U I address to the CS domain and the IMS domain interworking gateway;
  • the step D includes: the CS domain and the IMS domain interworking gateway obtain the SIP URI address by using the user to the user information cell, and convert the session establishment request into an IMS session establishment request according to the acquired SIP URI, and then send the request to the IMS TM.
  • step D the CS domain and the IMS domain interworking gateway further carry the dedicated indication information in the session description protocol indication of the sent IMS session establishment request, where the dedicated indication information is configured by the session description of the IMS session establishment request.
  • the protocol is extended to define the implementation;
  • the step D further includes: the IMS domain proxy call and session control function entity, when transmitting the IMS session establishment request to the IMSTM, identifying the media stream carried by the CS according to the dedicated indication information and performing special resource reservation processing .
  • the method further comprises: at the end of the session, the IMSTM instructs the CSTM to release the established CS bearer, and the CSTM initiates a call release request according to a standard CS procedure, and the CS call control entity and the interworking gateway receive After the CS bearer release request, The release process of the established CS bearer is completed, and the interworking gateway completes the release of the IMS domain callback with the IMSTM after receiving the CS bearer release request.
  • the IMS TM does not support initial session protocol extension
  • the step D further includes: the D1, the CS domain, and the IMS domain interworking gateway complete the establishment of the IMS domain callback interworking with the terminal that does not support the initial session protocol extension by performing an end-to-end negotiation process with the IMSTM.
  • step D1 the CS domain and the IMS domain interworking gateway complete the establishment of the IMS domain callback by not querying the IMS TM capability in advance, or by requiring the support of the initial session protocol extension; or the CS domain and the IMS domain interworking gateway receive the IMS TM return.
  • the IMS session establishment request that does not require support for the initial session protocol extension is re-initiated, and the establishment of the IMS domain callback is completed.
  • the method further includes: setting, in advance, a correspondence between the E.164 numbers corresponding to the CSTM and the IMSTM in each processing node of the CS domain;
  • the step C further includes: when sending the call setup request, each processing node in the CS domain determines the E.164 number of the CS TM corresponding to the calling and called number in the call setup request and the E.164 number corresponding to the IMS TM Whether there is a pre-set correspondence between the two, if any, then the associated charging process with the IMS session is performed.
  • the method further includes: pre-assigning a special prefix to the E.164 number corresponding to the IMSTM, and configuring the analysis data for the special prefix in the CS domain call control entity, and avoiding the CS calling side supplementary service by analyzing the special prefix and
  • the intelligent service affects the CS bearer establishment process of the CSI service;
  • the E.164 number of the IMS TM further includes the allocated special prefix; the step C further includes: after the CS domain call control entity receives the E.164 number of the IMS TM carrying the special prefix, according to the special The configuration data of the prefix, in the current call, the CS calling side supplementary service that affects the CS bearer establishment process of the CSI service is prohibited. Calling and triggering of intelligent services.
  • the IMS TM receives the IMS session establishment request sent by the peer as the called party. After determining that the condition for implementing the CSI service is not met, the method further includes:
  • IMS TM sends an IMS session redirection indication to the opposite end, and carries the CS TM addressing number in the CS domain in the IMS session redirection indication;
  • the peer end after receiving the IMS session redirection indication, releases the IMS session that is requested to be established, and redirects the IMS session to the addressing number carried in the indication as the called number to initiate a session request to the CS IMS domain;
  • the IMS network involved in the peer end sends the session establishment to the CS domain and the IMS domain interworking gateway according to the called number in the session request sent by the peer end;
  • the G14, the CS domain and the IMS domain interworking gateway map the received IMS session request to a CS call, and send the CS call to the CSTM through the CS network;
  • CS TM establishes a CS call connection through the CS network and the CS domain and the IMS domain interworking gateway, and the CS domain and the IMS domain interworking gateway establish an IMS session connection with the peer end.
  • the addressing number is the MSISDN signed by the CS TM at the CS.
  • the addressing number is formed by adding a specific prefix or a special identifier to the CS-signed MSISDN of the CS;
  • the step G14 further includes: the CS domain and the IMS domain interworking gateway deducting a specific prefix or special identifier added in the addressing number;
  • step G14 the addressing number transmitted in the CS network is the MSISDN signed by the CS TM at the CS.
  • the step G14 further includes: the CS domain and the IMS domain interworking gateway add a fallback indication in the sent CS call, and the CS network and/or the CSTM perform the CSI service fallback call processing according to the fallback indication added in the received CS call. .
  • Call processing includes: special billing processing and/or business conflict handling;
  • the CSI service fallback call processing includes: prompting the user that the current call is a CSI service related fallback call, or prompting the user that the current call is a CSI service related fallback call, and further controlling the user Enable call deflection processing.
  • the IMS TM receives the IMS session establishment request sent by the peer as the called party. After determining that the condition for implementing the CSI service is not met, the method further includes:
  • IMS TM sends an IMS session release indication to the peer end, and after receiving the IMS session release indication, the peer end releases the IMS session requested to be established;
  • CS TM initiates a call setup request in the CS, and the called number in the call setup request is the peer E.164 number;
  • the G23, CS network receives the call setup. After the request, the call is routed to the IMS and CS interworking gateway according to the analysis result of the called number of the call setup request.
  • the IMS domain and the CS domain interworking gateway map the received call setup request to the IMS session request, and send the IMS session request to the peer end through the IMS network involved in the peer end;
  • the peer end and the IMS domain establish an IMS session connection with the CS domain interworking gateway, and the IMS domain and the CS domain interworking gateway perform IMS/CS interworking processing and establish a CS call connection with the CSTM.
  • step G21 the IMSTM sends an addressing number carrying the CSTM in the CS domain in the IMS session release indication of the opposite end;
  • the method further includes: after receiving the IMS session establishment request, the peer end acquires the CS TM number from the IMS session establishment request, and determines the acquired number and the received IMS session release indication. Whether the numbers of the CS TM carried in the same are the same, and if so, the CSI service fallback call processing is performed.
  • the step of performing CSI service fallback processing on the peer end includes: prompting the peer user that the current call is a CSI service related fallback call, and further avoiding ringing during the session establishment process.
  • the step E further includes: releasing the established CS bearer between the CS TM and the CS domain call control entity and between the CS domain call control entity and the CS domain and the IMS domain interworking gateway; Interworking with the IMS domain gateway # puts an IMS session connection with the IMS TM; the IMS TM establishes a packet-switched PS bearer by using the renegotiation process, and uses the corresponding PS to transmit the corresponding media of the original bearer CS bearer transmission with the established PS bearer. Streams interact.
  • a method for implementing communication which is applied to an abnormal release of a CS bearer during implementation of a CSI service, the method comprising:
  • a CS bearer established between the CS TM and the CS domain call control entity and between the CS domain call control entity and the CS domain and the IMS domain interworking gateway;
  • the CS domain and the IMS domain interworking gateway release the IMS session connection with the IMS TM; c.
  • the IMS TM establishes the packet switched PS bearer by using the renegotiation process, and uses the established PS bearer to perform the original use of the CS bearer. The corresponding media stream carrying the transmission interacts.
  • the method further includes: the IMS TM notifying the peer to suspend the delivery of the media stream through the CS bearer;
  • step c after the PS bearer is established, and before the transmission is performed by using the established PS bearer, the method further includes: the IMSTM notifying the peer end to resume the transmission of the media stream originally carried by the CS bearer.
  • the step of the IMS TM establishing the PS bearer and the media interaction with the peer by using the renegotiation process includes: the IMS TM initiating a request to change the interactive media stream to the peer end, and completing the application and establishment of the PS bearer resource on the local side, And notifying the peer end that the media stream that originally interacted with the CS domain and the IMS domain interworking gateway and then transmitted to the CSI terminal by using the CS bearer is redirected and interacted to the CSI terminal PS bearer port.
  • a system for implementing communication comprising:
  • CS domain call control entity used to interact with the CS TM and establish a CS bearer, and will be The IMS TM control, the CS TM initiates the establishment of the established CS bearer call route to the CS domain and the IMS domain interworking gateway;
  • the CS domain and the IMS domain interworking gateway are configured to convert the CS call that is controlled by the CS domain call control entity to the local end into an IMS session establishment request, and connect the IMS session establishment request to the control to initiate the CS bearer process.
  • IMS TM thereby establishing a CS to IMS interworking call between the CS TM and the IMS TM ; and the CS domain and the IMS domain interworking gateway pass the IP address and port information of the IP port resource reserved for the IMS domain interactive media stream to the IMS TM, and using the CS bearer established between itself and the CS TM to interact with the media stream interacting with the peer through the IP bearer;
  • the IMS TM is configured to implement the CS bearer control function, determine and control the establishment process of the CS TM initiated CS bearer in the IMS service, and adopt the back-to-back user proxy mode after receiving the callback forwarded by the CS domain and the IMS domain interworking gateway.
  • the IP port reserved by the domain interworking gateway is transmitted to the CS domain and the IMS domain interworking gateway, and then transmitted to the local terminal through the CS bearer established between the CS domain and the IMS domain interworking gateway and the CS TM; CS TM, for receiving After the IMS TM command, the IMS TM is used as the setup request of the called CS bearer, and interacts with the CS domain call control entity to complete the establishment process of the CS bearer.
  • the IMSTM is integrated with the CSTM in the same terminal.
  • the IMS TM and the CS TM are disposed in different terminals and are connected by using a wireless short-distance communication method; the CS domain call control entity is further configured to send the peer end through the CS domain and the IMS domain interworking gateway.
  • the incoming CSI is sent back to the CS call setup request to send the call setup request to the CSTM, or the CSI sent by the CSTM is dropped back to the CS call setup request.
  • the CS domain and the IMS domain interworking gateway are further configured to convert the CSI back to the CS IMS session establishment request and convert the CSI back to the CS call setup after receiving the IMS session setup request sent by the peer to the CS.
  • After the request is sent to the CS domain call control entity; or, after receiving the call setup request sent by the CSI terminal CSTM via the CS domain call control entity to the CS, it is converted into an IMS session where the CSI falls back to the CS.
  • the request is established, it is sent to the peer;
  • the IMS TM is further configured to: when determining that the CSI service condition is not met, return an IMS session redirect indication or an IMS session release indication to the peer end, so that the peer end and the self complete the IMS session release.
  • the CS TM is further configured to: after receiving the call setup request initiated by the peer user in the IMS and through the CS domain and the IMS domain interworking gateway and the CS domain call control entity, through the CS domain call control entity, the CS domain and the IMS domain
  • the interworking gateway establishes a CSI fallback to the IMS to the CS intercommunication call connection with the peer end; or, the peer end acts as the called party, and the CS domain call control entity and the CS domain and the IMS domain interworking gateway actively establish a CSI fallback to the CS.
  • CS to IMS intercom call connection is further configured to: after receiving the call setup request initiated by the peer user in the IMS and through the CS domain and the IMS domain interworking gateway and the CS domain call control entity, through the CS domain call control entity, the CS domain and the IMS domain
  • the interworking gateway establishes a CSI fallback to the IMS to the CS intercommunication call connection with the peer end; or, the peer end acts as
  • the present invention provides a specific implementation scheme of a CSI service in a terminal-to-gateway/terminal control mode, including a specific implementation form of a CBCF in a user terminal, and a call in a terminal and an associated CS/IMS domain network element, such as a CS domain.
  • the control entity or the IMS domain call control entity cooperates with the specific implementation process of the CSI service; further, the CS route detour problem that may occur in the case of CSI terminal roaming, the CS/IMS associated charging problem, the non-standard terminal access, and
  • the present invention provides a specific solution to the problem that the CS bears corresponding processing in the case of abnormal release. Therefore, the present invention provides a practical technical solution for realizing the CSI service on the CSI terminal, thereby ensuring the CSI terminal.
  • the current CSI business communication process including a specific implementation form of a CBCF in a user terminal, and a call in a terminal and an associated CS/IMS domain network element, such as
  • the CSI terminal when the CSI terminal as the called party cannot implement the CSI service due to the current network capability reason or the user selects, the CSI terminal can drop the received CSI call into a CS call, further ensuring the communication of the CSI terminal. process. BRIEF DESCRIPTION OF THE DRAWINGS
  • FIG. 1 is a schematic diagram of a CSI service that implements a CS bearer and an IMS service.
  • Figure 2 is a schematic diagram of the logical functional framework for implementing CSI services.
  • Figure 3 is a schematic illustration of the system of the present invention.
  • Figure 4 is a flow chart showing the implementation of CSI services by a CSI terminal in the present invention.
  • Figure 5 is a process flow diagram for the abnormal release of CS bearers in the present invention.
  • Fig. 6 is a flow chart showing the processing when the IMS terminal module does not support the SIP protocol extension in the CSI terminal in the present invention. ⁇
  • Figure 7 is a flow diagram of a first mode of implementing a CSI session back to a CS call in the present invention.
  • Figure 8 is a flow diagram showing the second way in which the CSI session is dropped back to the CS call in the present invention. Mode for carrying out the invention
  • the present invention proposes a method for implementing communication for a CSI terminal, the core idea of which is: IMS terminal module (IMS TM ) root in a CSI terminal 5 001635 indicates that the CS terminal module (CS TM ) in the CSI terminal initiates a CS bearer setup procedure according to the needs of the current IMS service; the CS TM sends the IMS TM as a called party to the CS domain call control entity to send a CS call setup request for establishing the CS bearer; The CS domain call control entity routes the call setup request to the CS domain and the IMS domain interworking gateway according to the called number information in the received call setup request; the CS domain and the IMS domain interworking gateway convert the received call
  • the IMS TM After the request is sent to the IMS TM; the IMS TM performs association control with the CS domain and the IMS domain interworking gateway and the two sessions between the peer end, establishes an IMS session connection between the IMS TM itself and the peer end, and the IMS TM itself passes through the CS domain Interworking with the IMS-CS between the IMS domain interworking gateway and the corresponding CS TM, establishing CS TM and CS in the IMS-CS interworking connection between the CS domain itself and the IMS domain interworking gateway and the corresponding CS TM
  • the CS bearer between the domain and the IMS domain interworking gateway controls the association between the two sessions through the IMS TM, so that the peer uses its IP bearer between the CS domain and the IMS domain interworking gateway and the CS domain and the IMS domain interworking gateway and CS.
  • TM The CS carries two segments of the bearer, and interacts with the CSI terminal to require a media stream with higher real-time requirements supported
  • the present invention may further reduce the CSI call to a CS call, so that The CSI terminal can continue to communicate with the peer.
  • the present invention proposes a system for terminal-to-gateway/terminal control mode.
  • Figure 3 is a schematic illustration of the system of the present invention.
  • the system of the present invention includes a CSI terminal, a CS call control entity, and a CS domain and an IMS domain interworking gateway.
  • the CSI terminal specifically includes: an IMS terminal module (IMSTM) that implements a CBCF function and a CBTF function, and implements a CBOF function.
  • IMSTM IMS terminal module
  • CS TM CS terminal module
  • CS domain call control entity such as a Mobile Switching Center (MSC)
  • MSC Mobile Switching Center
  • IMS TM and CS TM Interacting and establishing a CS bearer, and routing CS calls initiated by the IMS TM and CS TM to establish a CS bearer to the CS domain and the IMS domain interworking gateway, that is, from the CS TM to the CS domain and the IMS domain in the network Establishing a CS bearer path between the interworking gateways; and transmitting the call setup request to the CS TM after receiving the call setup request sent by the peer end through the CS domain and the IMS domain interworking gateway to the CS, or the CS TM
  • the call setup request sent back to the CS by the CSI is sent to the CS domain and the IMS domain interworking gateway.
  • the CS domain and the IMS domain interworking gateway are configured to interact with the CS TM and establish a CS bearer, convert the CS call that is controlled by the CS domain call control entity to the local end into an IMS session establishment request, and control the IMS session establishment request through the IMS session.
  • the entity continues to control the IMS TM that initiates the establishment of the CS bearer process; and, after receiving the IMS session establishment request that the CSI sent back from the peer falls back to the CS, the IMS session establishment request that the CSI falls back to the CS is converted into the CSI fallback to After the CS call setup request of the CS is sent to the CS domain call control entity, or after the CSI terminal receives the CS call setup request sent by the CS domain call control entity to the CS, it is converted into a CSI fallback to the CS. The IMS session establishment request is sent to the peer.
  • the process of connecting the CS domain to the IMS domain interworking gateway to connect the session to the IMS TM may be completed by a thin solid line and a dotted line path labeled 2 in FIG. 3; and the CS domain and the IMS domain interworking gateway will interact with the IMS domain.
  • the IP address and port information of the IP port resource reserved by the media stream is transmitted to the IMS TM, and the media stream that the peer interacts with the reserved IP port is further performed with the CS TM by using the CS bearer established between the UE and the CS TM. Interaction.
  • the IMS TM is used to implement the CS bearer control function, and determines and controls the establishment process of the CS TM initiated CS bearer in the IMS service, and adopts the back-to-back user agent (B2BUA) after receiving the callback forwarded by the CS domain and the IMS domain interworking gateway.
  • B2BUA back-to-back user agent
  • the method is to complete the association control between the CS domain and the IMS domain interworking gateway and the two IMS sessions between the peer and the peer, so that the peer needs to interact with the local user in the IMS session.
  • the IP port reserved by the CS domain and the IMS domain interworking gateway is transmitted to the CS domain and the IMS domain interworking gateway, and then transmitted to the local terminal through the CS bearer established between the CS domain and the IMS domain interworking gateway and the CS TM;
  • the IMS session redirection indication or the IMS session release indication is returned to the peer end, so that the peer end and the self complete the IMS session release.
  • the CS TM is configured to, after receiving the IMS TM command, use the IMS TM as the setup request of the called CS bearer, and perform corresponding interaction with the CS domain call control entity to complete the establishment process of the CS bearer; or, after receiving the pair
  • the IMS initiates and establishes a call setup request sent by the CS domain and the IMS domain interworking gateway and the CS domain call control entity
  • the end user establishes an IMS to CS interworking call connection with the peer end to the CS, or the peer end
  • the called party actively establishes a CSI back-to-CS CS-to-IMS interworking call connection with the CS through the CS domain call control entity and the CS domain and the IMS domain interworking gateway.
  • the thick solid line indicates the CS bearer and the signal path
  • the thin solid line indicates the PS bearer path
  • the dotted line indicates the SIP message path.
  • IMS TM and CS TM can be integrated in the same terminal or in different terminals.
  • the short distance wireless connection may be performed between the IMS TM and the CS TM by using, but not limited to, Bluetooth, etc.
  • the IMS TM may be implemented by using, but not limited to, the following: a personal computer (PC) or Personal Digital Assistant (PDA), that is, implementing the IMSTM using software built into a PC or PDA.
  • PC personal computer
  • PDA Personal Digital Assistant
  • the respective E.164 numbers are also stored in CS TM and IMS TM, which can be stored in respective corresponding storage modules; when IMS TM and CS TM are integrated in the same terminal
  • the respective E.164 numbers of CS TM and IMS TM may also be stored in the data area shared by CS TM and IMS TM .
  • Figure 4 is a flow chart showing the implementation of CSI services by a CSI terminal in the present invention.
  • the process of the present invention for implementing a CSI service by a CSI terminal includes the following steps:
  • Step 401 Assign an E.164 number to the CSTM and the IMSTM, respectively, and configure the called analysis data on the CS domain call processing node for the E.164 number assigned to the IMSTM.
  • the E.164 numbers assigned for CS TM and IMS TM respectively are E.164 numbers that can effectively identify CS TM and IMS TM in the CS and IMS networks.
  • the E.164 number assigned to the CS TM is the mobile station international ISDN ( MSISDN ) number that the CS TM subscriber belongs to in the CS domain
  • the E.164 number assigned to the IMS TM is the IMS TM subscriber in the IMS network. The number of the contract.
  • each node in the CS domain call processing node that is, each node in the CS that needs to transmit a call, such as a CS domain call control entity in the system of the present invention, configures the called analysis data for the subsequent calls in the CS domain.
  • the processing node is able to route the call to the interworking gateway of the CS and IMS.
  • the CS domain call processing node configures the called analysis data, and in the subsequent process, each call processing node in the CS domain can identify the current service as a CSI service, thereby performing special charging and service processing.
  • the area identification prefix and/or the service type prefix may be included in the E.164 number allocated for the IMS TM, so that the call can be determined by the area identification prefix and/or the service type prefix in the subsequent process. Routing, and/or in subsequent processes, each call processing node in the CS domain can identify that the current service is a CSI service, thereby performing special charging and service processing.
  • Step 402 The IMS TM as the CS bearer control function entity determines whether the CSI service needs to be triggered currently. If yes, step 403 is performed. Otherwise, the current CSI industry is terminated. Process.
  • the IMS TM may be configured to initiate an IMS session establishment request, receive an IMS session establishment request sent by the peer, prepare to initiate a renegotiation request during the IMS session, or receive a renegotiation request sent by the peer. , the process of performing the judgment described in this step.
  • the IMS TM may be configured according to whether the media stream that is prepared for interaction or the media stream that the other party requests to interact with needs to be transmitted through the CS bearer, that is, whether the media stream according to the required interaction has a real-time multimedia service stream component, such as whether Contains voice information, etc., to determine whether the CSI service needs to be triggered.
  • a real-time multimedia service stream component such as whether Contains voice information, etc.
  • Step 403 The IMS(TM) determines whether the condition for implementing the CSI service is currently met. If yes, step 404 is performed. Otherwise, the process of establishing the CSI service is ended.
  • the IMS TM can determine whether the current CZ service condition is met according to the determined user intention according to whether the cell that the UE is connected has the capability of maintaining the connection with the CS and the PS air interface. That is to say, if the cell that the user accesses has the capability of maintaining the connection with the CS and the PS air interface at the same time, and further, the determined user intention is to perform the CSI service, the IMS TM considers that the condition for implementing the CSI service is currently satisfied.
  • the user's willingness can be determined by:
  • Step 404 The IMSTM acquires the MSISDN of the CSTM.
  • the IMSTM can acquire the MSISDN of the CSTM through a real-time interaction with the CSTM or a process of pre-interaction. If the process of real-time interaction is passed, the implementation process of this step is: IMS TM first initiates a request to CS TM through an interface between itself and CS TM, and CS TM receives After the request, the MSISDN of its own is sent to the IMS TM, and the IMS TM acquires the MSISDN of the CS TM; if the process of the pre-interaction is initiated, the IMS TM initiates to the CS TM when the CSI terminal (including the IMS TM and CS TM ) is started After the CS TM receives the request, it sends its own MSISDN to the IMS TM, and the IMS TM saves the received MSISDN in its own MSISDN cache.
  • the implementation process of this step is: IMS TM first initiates a request to CS TM through an interface between itself and
  • the process of this step described above belongs to the internal interaction process between the internal modules of the terminal. At this time, if the IMS TM and CS TM further adopt the shared data area to store the IMS TM and CS TM When the respective E.164 number is used, the implementation process of this step is: IMS TM acquires the MSISDN of the CS TM from the shared data area.
  • Step 405 The IMS TM instructs the CS TM to initiate CS bearer setup.
  • the process described in this step belongs to an internal interaction process between the internal modules of the terminal, that is, the IMS TM instructs the CS TM to initiate the CS bearer establishment by an internal command, and
  • the indication includes the corresponding bearer capability indication information
  • the process described in this step is: the IMS TM sends a CS bearer setup request to the CS TM through a short-range wireless communication method such as Bluetooth, and carries the corresponding in the CS bearer setup request. Carrying capacity indication information.
  • the IMS(TM) further carries the E.164 number of the IMS(TM) itself in the indication.
  • the IMS TM may further carry an Initial Session Protocol Uniform Resource Locator (SIP URI ) address of the IMS TM in the indication, so as to facilitate the CS domain and the IMS domain interworking gateway to obtain the IMS TM in a subsequent process.
  • the CSTM sends a call setup request to the CS domain call control entity according to a standard CS domain procedure.
  • the CSTM in its own call setup request, uses its own MSISDN as the calling number, which will be obtained from the IMSTM number storage module or from the CS bearer setup indication/request from the IMSTM.
  • the E.164 number of the IMS TM is taken as the called number, and the bearer capability indication in the call setup request sent by itself is filled according to the bearer capability indication provided by the IMS TM .
  • the CS TM can carry the SIP URI address of the IMS ⁇ by user-to-user signaling (UUS ) and send it to the CS domain call control. entity.
  • UUS user-to-user signaling
  • Step 407 After receiving the call setup request, the CS domain call control entity routes the call setup request to the CS domain and the IMS domain interworking gateway according to the called number information.
  • the CS domain call control entity may be an MSC, according to the called number in the call setup request, that is, the E.164 number allocated for the IMS TM that initiates the CS bearer setup process, and the called party profile configured in advance in itself. Data, determining to route the call to the interworking gateway of the CS and the IMS, so that the CS bearer is in communication with the CS domain and the IMS domain interworking gateway.
  • the CS domain call control entity analyzes the prefix according to the service type.
  • the call setup request is forwarded to the closer CS domain and the IMS domain interworking gateway, that is, the corresponding service type prefix is configured to be routed to the nearest CS domain and the IMS domain interworking gateway in the called analysis data, thereby avoiding CS The bearer route is bypassed.
  • the CS domain call control entity analyzes the call identification of the area to transfer the call setup request to the CS domain and the IMS domain interworking gateway of the user area to which the IMS TM belongs, that is, configure the corresponding area identification prefix as the route in the called analysis data.
  • the CS domain and the IMS domain interworking gateway to the IMS TM home zone ensure that the IMS TM can reliably implement the CSI service even in the roaming situation.
  • the CS domain call control entity carries the SIP URI address of the IMS TM through the UUS and sends it to the CS domain and the IMS domain interworking gateway.
  • the step may be deleted in the process, that is, after performing the foregoing step 406, directly perform the following steps. 408.
  • Step 408 The CS domain and the IMS domain interworking gateway acquire the IMS domain public identity corresponding to the IMS TM, and then send the IMS domain public identity as the called address to the IMS TM to send an IMS session establishment request.
  • the present invention can pre-configure the conversion data of the E.164 number assigned by the IMS TM and the IMS domain public identifier in the telephone number mapping (E UM ) server, so that in this step, the CS domain communicates with the IMS domain.
  • the gateway MGCF/IM-MGW obtains the E.164 number assigned by the IMS TM according to the called number carried in the call setup request, and performs an ENUM server query to obtain the IMS domain public identifier of the IMS TM through the set conversion data.
  • this step also implements a process of authenticating the current CSI service, that is, when the conversion data of the E.164 number allocated for the IMS TM is queried in the ENUM service, It is determined that the IMS TM application CSI service is allowed.
  • the IMS domain public identifier is in the form of a SIP URI, and the IMS domain uses SIP URI addressing; therefore, if the CS domain and the IMS domain interworking gateway receive the SIP URI of the IMS TM carried by the UUS Address, in this step, CS domain and IMS The domain interworking gateway can also obtain the SIP URI address, that is, the IMS domain public identifier of the IMS TM, directly from the UUS.
  • the CS domain and the IMS domain interworking gateway acquire the MSISDN number of the CSTM from the calling number in the received call setup request, and the session establishment request message From the IMS TM is sent.
  • the MSISDN number carrying the CS TM in the header field is sent.
  • the CS domain and the IMS domain interworking gateway MGCF/IM-MGW instruct the IM-MGW to reserve port resources for the media stream that the IMS side interacts according to the IMS domain standard interworking process, and connect the IMS session to the IMS network through the IMS network.
  • the IMS TM that initiates the establishment of the CS bearer is controlled, that is, the interworking gateway sends an IMS session establishment request to the IMS TM that initiates the CS bearer setup procedure.
  • the CS domain and the IMS domain interworking gateway indicate, in the sent session establishment request, the IP address and the user datagram protocol of the port reserved for the IMS side on the IM-MGW through the Session Description Protocol (SDP) part ( UDP) Port information, so that the CSI terminal can use the port resource to interact with the peer media stream in the subsequent process.
  • SDP Session Description Protocol
  • UDP User Datagram Protocol
  • Step 409 After receiving the session establishment request sent by the interworking gateway, the IMS TM performs association processing with the interworking gateway and the two sessions with the peer end. .
  • the specific implementation process of this step includes:
  • the IMS TM acquires the MSISDN number in the From field of the session establishment request message, and determines whether the currently acquired MSISDN number is the same as the MSISDN of the CS TM acquired in step 404, and if yes, determines
  • the current IMS session establishment request is an IMS callback corresponding to the CS bearer setup procedure requested by the local end, and is not a new session setup request initiated by another user;
  • the IMS TM obtains the SDP from the received session establishment request, that is, the IP address and UDP port information of the port reserved by the interworking gateway for the interactive media stream, and the obtained information is obtained.
  • the SDP obtained by the N2005/001635 is sent to the peer end as the local session description protocol corresponding to the media stream that is applied by the CS bearer.
  • the SDP corresponding to the CS bearer part is used as the local session description on the IMS session between the CS domain and the IMS domain interworking gateway.
  • the protocol indication is provided to the interworking gateway, and the IMS callback process established with the CS bearer between the CS domain and the IMS interworking gateway and the IMS session establishment process with the peer end are respectively performed as a back-to-back user agent (B2BUA).
  • B2BUA back-to-back user agent
  • the IMS TM that controls the initiation of the CS bearer establishment as the B2BUA completes the IMS-CS interworking session establishment of the CS domain and the IMS domain interworking gateway MGCF/IM-MGW to the CS TM and the IMS between the peer and the peer respectively.
  • the establishment of the CS bearer between the CS TM and the interworking gateway MGCF/IM-MGW is completed in the IMS TM CS-CS interworking session establishment between the IMS TM and the IMS domain interworking gateway to the CS TM, and in the process Passing the session description protocol indication on the part of the media stream that the local end decides to adopt the CS bearer is transparently transmitted between the gateway and the peer end (that is, the corresponding session description protocol indication sent by the gateway and the peer end is respectively transmitted as the local session description protocol indication to The peer end and the gateway) enable the peer end and the interworking gateway to transfer the media stream, which is determined by the CS bearer, to the local end by using the IP bearer, and then established between the interworking gateway MGCF/IM-MGW and the CSTM.
  • the CS bearer connection continues to pass the part of the media stream between the gateway and the local CSI terminal.
  • the IMS TM adds a related indication to the sent SDP.
  • the proxy call and session control function entity (P-CSCF) of the IMS domain receives the SDP sent by the IMSTM, it is identified according to the relevant indication added in the SDP.
  • P-CSCF proxy call and session control function entity
  • the process in which the IMSTM adds a related indication in the sent SDP may be, but is not limited to, adopting an SDP.
  • the method of extending the definition is implemented, for example, by using one description or multiple description combinations defined in the SDP to indicate the media stream information carried by the CS.
  • the process of establishing a CSI service connection between the IMS TM and the CS TM in the CSI terminal and the opposite end is completed. Thereafter, the CSI terminal and the opposite end pass the CSI terminal CS TM to the CS between the CS domain and the IMS domain interworking gateway.
  • the bearer, the CS domain and the IMS domain interworking gateway and the IP bearer between the peers carry the two bearers, and the transmitting local end decides to adopt the media stream carried by the CS to implement the CSI service.
  • the present invention further includes releasing the established CS connection, and the specific processing procedure is: controlling the IMS TM that initiates the CS bearer establishment to indicate the establishment of the CS TM release at the end of the session.
  • the CS bearer, the CS TM initiates a CS call release request according to the standard CS process, and after the CS call control entity and the interworking gateway receive the CS call release request, complete the # put process for the established CS bearer, and the interworking gateway receives the CS.
  • the MGCF completes the dry release of the IMS domain callback with the IMSTM, thus completing the release process of the entire CS bearer and establishing the CS to IMS intercommunication call involved in the bearer.
  • the above process of releasing the connection is a process of releasing the connection under normal circumstances, that is, at the end of the session.
  • the CS bearer is abnormally released.
  • the present invention completes the call release between the CS TM and the CS domain network element according to the CS domain standard procedure, the interworking gateway MGCF releases the IMS domain callback to the IMS TM, and the IMS TM completes the IMS callback session release, and is at the peer end During the session, the renegotiation process is used to negotiate with the peer to reverse the traffic or redirect the media stream. Referring to FIG.
  • Step 501 The CS domain call release process is completed according to the CS domain standard process between the CSTM and the CS call control entity, and the CS call control entity and the CS call control entity CS domain and IMS domain interworking gateway
  • the CS domain transfer call release process is completed between the MGCF/IM-MGW according to the CS domain standard process.
  • Step 502 The process of releasing the IMS domain callback between the CS domain and the IMS domain interworking gateway MGCF and the IMS TM is completed.
  • Step 503 The IMS TM notifies the peer to suspend the transmission of the media stream originally transmitted by the CS bearer at the local end.
  • Step 504 The IMSTM and the peer establish a corresponding PS bearer through the renegotiation process to transmit the media stream originally transmitted through the CS bearer, and notify the peer end to redirect the media stream to the PS bearer port established in this step.
  • Step 505 The IMS TM notifies the peer end to resume the transmission of the media stream.
  • Step 506 The IMS TM and the peer use the established PS bearer to perform transmission interaction on the media stream originally transmitted by using the CS.
  • the processing for the abnormal release of the CS bearer is completed.
  • the present invention can ensure that the CSI terminal continues to communicate even if the CS bearer is abnormally released.
  • the process of releasing the abnormality of the CS bearer in the process of implementing the CSI service shown in FIG. 5 may be applied to the CSI service implemented in any mode, such as the terminal to gateway/network control mode, where step 503 is performed.
  • ⁇ 506 is also applicable to the terminal-to-terminal mode, that is, the process shown in FIG. 5 may be a process of releasing the abnormality of the CS bearer in the process of implementing the CSI service in the terminal-to-gateway/terminal control mode shown in FIG. It may be a process of implementing abnormal release of the CS bearer in the CSI service process in other modes, such as the terminal-to-gateway/network control mode.
  • the CS domain and the IMS domain interworking gateway may further carry the dedicated indication information in the session description protocol indication of the sent CSI callback IMS session establishment request, where The dedicated indication information is implemented by extending the definition of the session description protocol of the IMS session establishment request;
  • the IMS domain proxy call and session control function entity may further determine, according to the dedicated indication information, that the part of the media stream will be sent via the CS bearer, so as to perform special resource pre-preparation. Leave the processing, that is, not to carry out the part of the capital
  • IMS TM does not support 3GPP requirements ⁇ Precondition preset conditions as defined by IETF RFC 3312, integrated resource management and SIP), the UPDATE (update) method defined by IETF RFC 3311 and the 100 Rel (Reliable Delivery of SIP Temporary Transfer) ⁇ defined by IETF RFC 3262, correspondingly there is IMS TM access that does not support the relevant SIP extension.
  • the CS domain and the IMS domain interworking gateway MGCF use the end-to-end (E2E) manner to complete the process negotiation of the 3GPP SIP and the non-3GPP SIP.
  • the CS domain and the IMS domain interworking gateway MGCF may also perform capability query negotiation with the IMS TM through SIP related operations before the IMS session is initiated, and decide whether to adopt the SIP extension when initiating the session establishment process to the IMS TM according to the negotiation result.
  • Figure 6 is a flow chart showing the processing when the IMS terminal module does not support the SIP protocol extension in the CSI terminal in the present invention. Referring to FIG. 4 and FIG.
  • step 408 in order to avoid the impact of the IMS TM not supporting the SIP protocol extension on the subsequent session, in the process from step 408 to step 409 shown in FIG. 4, the following steps are further included:
  • the CS domain and the IMS domain interworking gateway MGCF request the IMS TM to support SIP protocol extension (such as Precondition, etc.) through the IMS session establishment request.
  • SIP protocol extension such as Precondition, etc.
  • Step 602 After receiving the IMS session establishment request, the IMS TM returns a session establishment failure message to the CS domain and the IMS domain interworking gateway MGCF, and the failure cause value in the session establishment failure message does not support the SIP protocol extension.
  • the process of the foregoing steps 601 to 602 may also be: Interworking between the CS domain and the IMS domain
  • the MGCF initiates an IMS capability query request to the IMSTM to learn whether the IMSTM supports the SIP protocol extension; the IMSTM returns information that does not support SIP. protocol extensions (such as Precondition) to the CS domain and the IMS domain interworking gateway MGCF.
  • Step 603 The CS domain and the IMS domain interworking gateway
  • the MGCF initiates an IMS session establishment request to the IMSTM, and the IMSTM support request does not require the SIP protocol extension that the IMSTM cannot support.
  • Step 604 After receiving the IMS session establishment request sent by the CS domain and the IMS domain interworking gateway MGCF that does not require support for the SIP protocol extension that cannot be supported by the IMS, the IMS TM returns the session establishment to the CS domain and the IMS domain interworking gateway MGCF. Success message.
  • the CS domain and the IMS domain interworking gateway MGCF learn that the IMS TM does not support the SIP protocol extension Precondition, that is, the CS domain cannot be correctly notified during the IMS session establishment process with the CS domain and the IMS domain interworking gateway MGCF.
  • the associated IMS domain has good associated bearer resources, so the session established in steps 603 and 604 above describes the interacting media stream as an inactive state to prevent either party from transmitting the invalid media stream in advance.
  • Step 605 The peer end notifies the IMS TM after completing the preparation of the required bearer resource, and the IMS TM directly initiates or forwards the notification of the peer end to the CS domain and the IMS domain interworking gateway MGCF.
  • Step 606 The CS domain and the IMS domain interworking gateway
  • the MGCF initiates a renegotiation process to the IMS TM to modify the media stream description to be activated, and the CSI terminal includes the media stream transmission of the CSI service between the IMS TM and the CS TM and the peer.
  • the correspondence between the E.164 numbers corresponding to the CSTM and the IMSTM respectively may be set in advance in each processing node of the CS domain.
  • the processing of the CS domain is performed.
  • the node After receiving the call setup request sent by the CS TM, the node may be based on the E.164 number corresponding to the CS TM and the called number is the E.164 number corresponding to the IMS TM.
  • the caller establishes the request in the main and called There is a preset correspondence between the numbers to determine whether the call is a CS bearer used by the IMS session.
  • the calling number is the MSISDN number of a subscriber, the called party, etc., so that each processing node in the CS domain can perform associated charging processing for the current CSI service, for example, the call can be applied to the current call.
  • the charging of the CS bearer is exempted or attached to the IMS service for charging.
  • step 406 shown in FIG. 4 since the CS TM initiates a call setup request for the CS bearer by using the MSISDN subscribed in the CS domain, it is also necessary to consider the impact of the CS TM side supplementary service, where the CSI service is affected.
  • Mobile Intelligent Service (CAMEL) will likely limit the The establishment of the CS bearer call or the triggering of the intelligent service during the CS bearer call to introduce the control and influence of the intelligent service (such as changing the number, etc.).
  • the processing method of the present invention is: pre-specifying a special prefix for the E.164 number corresponding to the IMSTM, such as a prefix representing the service type, and passing the CS domain.
  • the method of configuring the analysis data for the special prefix in the call control entity prevents the CS calling side supplementary service and the intelligent service from affecting the CSI service CS bearer establishment process, so that in the process shown in FIG.
  • the CS TM acquires And further including the allocated special prefix in the E.164 number of the IMS TM sent by the CS domain, after the CS domain call control entity receives the E.164 number of the IMS TM carrying the special prefix, according to the configured for the special
  • the analytic data analysis of the prefix prohibits the supplementary service call and the intelligent service triggering in the current call of the CS TM, thereby preventing the CS calling side supplementary service and the intelligent service from affecting the CSI service CS bearer establishing process.
  • the CS domain call control entity may also perform associated charging processing for the current CSI service according to the configured analysis data analysis for the special prefix, for example, the charging of the CS bearer applied to the current call may be exempted. Or attached Billing is performed in the IMS service.
  • the present invention proposes a CSI that meets the requirements of the 3GPP TS 23.899 standard.
  • the specific implementation of the service ensures that the CSI terminal can implement the CSI service.
  • the present invention further provides a solution for avoiding route bypass in the case of CSI terminal roaming, a solution in the case of CS bearer abnormal dry release, and an IMS terminal module in the CSI terminal.
  • the solution to the SIP protocol extension required by the 3GPP standard, the solution to the associated charging of the CS domain and the IMS domain, and the solution to avoid the impact of the CS domain calling side supplementary service and the intelligent service are provided, thereby providing an extremely complete solution. And a rich CSI business implementation solution.
  • the process of implementing the CSI service must be based on the capability of the CSI terminal to maintain the connection with the CS and PS air interfaces, and further based on the user's will. Therefore, when the CSI service condition is not met, the CSI terminal If the accessing cell cannot be connected to the air interface of the CS and the PS at the same time or the user wishes to not perform the CSI service, if the communication between the CSI terminal and the peer user is still to be guaranteed, the CSI session must be considered as a CS call. Therefore, in the step 402 of implementing the CSI service process shown in FIG. 4, if the called CSI terminal receives the IMS domain session establishment request sent by the peer, it is determined that the CSI service should be triggered, but it is determined in step 403.
  • the present invention further provides a method for reverting a CSI service to a CS call, which includes two implementation manners: Method 1: The CSI terminal sends a call redirect indication to the opposite end and is re-directed by the peer end. The IMS session is initiated and the CS domain and the IMS domain interworking gateway are switched to the CS call connection to the CSI terminal. The second method is: the CSI terminal uses the IMS session established by the request for the specific reason, and then actively initiates the CS to the opposite end in the CS domain. It is implemented by means of IMS intercommunication.
  • FIG. 7 is a flow of a method 1 for implementing a CSI session back to a CS call in the present invention.
  • Figure. Referring to FIG. 7, in the foregoing manner 1, when the CSI terminal that is called is configured to receive the IMS domain session establishment request sent by the peer end, it is determined that the CSI service should be triggered, but if it is further determined that the current CSI service condition is not met, The process of implementing the CSI service back to the CS call specifically includes the following steps:
  • Step 701 The IMSTM in the CSI terminal returns an IMS session redirection indication to the peer end, and carries the E.164 number used by the CSTM in the CSI terminal in the CSI terminal in the IMS session redirection indication.
  • the E.164 number used by the CSTM in the CSI terminal in the CS call addressing has the capability of indicating that the IMS network involved in the opposite end transfers the call to the CS connection, and the E.164 number may be the CSI terminal signing on the CS.
  • the MSISDN can also be composed of a specific prefix or special identifier added by the MSISDN.
  • Step 702 After receiving the IMS session redirection indication, the peer returns a call redirection confirmation, and the IMS TM and the peer release the IMS session established by the current request.
  • Step 703 The peer initiates a new IMS session establishment request, and redirects the IMS session to the E.164 number carried in the indication, that is, the E.164 number used by the CSI terminal to address the CS call, as the new IMS session is established.
  • the requested called number The E.164 number carried in the indication, that is, the E.164 number used by the CSI terminal to address the CS call.
  • Step 704 The IMS network involved in the peer end determines the new session according to the analysis result of the called number of the new IMS session establishment request, that is, the E.164 number used by the CSI terminal in the CS call addressing.
  • the setup request is forwarded to the CS connection and the CS domain and the IMS domain interworking gateway are selected, and then the new session establishment request message is forwarded to the selected CS domain and the IMS domain interworking gateway.
  • Step 705 After receiving the new session establishment request, the CS domain and the IMS domain interworking gateway perform IMS/CS interworking processing, complete CS route analysis according to the CS standard processing procedure, and send a CS call setup request to the CS through the CS network.
  • TM and the CS domain and the IMS domain interworking gateway and the peer end complete the IMS session part through the IMS network involved in the peer end SDP negotiation.
  • step 601 if the E.164 number returned by the CSI terminal to the peer end is formed by adding a specific prefix or a special identifier to the MSISDN number of the CSI terminal, that is, in steps 703 and 704 above.
  • the called number of the new session establishment request transmitted in the session is formed by adding a specific prefix or a special identifier to the MSISDN number of the CSTM.
  • the CS domain and the IMS domain interworking gateway firstly from the called number.
  • the specific prefix or special identifier added is deducted, and the MSISDN remaining after the deduction is used as the called number to complete the interaction processing with the CS network.
  • the CS domain and the IMS domain interworking gateway when deducting the added specific prefix or special identifier, may further determine, according to the added specific prefix or special identifier, that the current call is a CSI service related fallback call, thereby being in the CS
  • a special indication is added to the call control signaling so that the CS network and/or the CSTM can perform special processing of the CSI service related fallback call according to the special indication. For example,
  • the CS network may, according to the special indication added by the CS domain and the IMS domain interworking gateway, may perform the following special processing:
  • Special billing processing For example, the CS network deducts part of the CS credit according to the special instruction;
  • Service conflict handling For example, the CS network circumvents part of the CS domain supplementary services according to the special indication, such as forward rotation, call blocking, and intelligent triggering.
  • the CSTM may, depending on the special indication added by the CS domain and the IMS domain interworking gateway, may perform the following special treatments:
  • Step 706 After receiving the CS call setup request, the CSTM interacts with the corresponding CS network to complete the CS call setup process, and returns the CS to the CS domain and the IMS domain interworking gateway.
  • the user ringing and CS user response message establishes a CS call between the CSTM and the CS domain and the IMS domain interworking gateway.
  • Step 707 The CS domain and the IMS domain interworking gateway perform the IMS/CS interworking process, and the process is mapped to the IMS session establishment process. After the IMS network involved in the peer end returns the IMS user ringing and the IMS user response to the peer end. After the peer returns an IMS response confirmation, an IMS session is established between the CS domain and the IMS domain interworking gateway.
  • FIG. 8 is a flow diagram showing the second way in which the CSI session is dropped back to the CS call in the present invention.
  • the process of implementing the CSI service back to the CS call specifically includes the following steps:
  • Step 801 The IMSTM in the CSI terminal responds to the IMS session release indication to the peer end.
  • the IMS TM may carry the CSI service indication and the number used by the CS TM in the CS in the CSI terminal, that is, its MSISDN, in the IMS session release indication that is responded to.
  • the call can be identified.
  • Step 802 After receiving the IMS session release indication, the peer end responds to the IMS TM with a call release confirmation, and the IMS TM releases the IMS session established by the peer with the current request.
  • the peer acquires the MSISDN number of the CS TM from the IMS session release indication.
  • Step 803 The CS TM initiates a call setup request to the opposite end of the CS, and the called number in the call setup request is the peer E.164 number.
  • the called number that is, the R164 number of the opposite end
  • the called number has the capability of indicating that the CS network involved in the CSI terminal transfers the call to the IMS connection, and specifically may be the MSISDN signed by the opposite end in the CS, or may be added by the MSISDN with a specific prefix.
  • the called number in the call setup request that is, the E.164 number of the peer end is obtained by the CSI terminal according to the IMS session establishment request sent by the peer end, that is, in step 402 shown in FIG. 4 above.
  • the CSI terminal When the CSI terminal receives the IMS session establishment request sent by the peer, the CSI terminal obtains the IMS identity of the peer from the From header field in the IMS session establishment request, and then derives (depends on) the acquired IMS identifier.
  • the E.164 number of the peer end is obtained by the peer.
  • the E.164 number of the peer end is obtained according to the acquired IMS identifier and the directory information, or is carried by the peer directly in the IMS session establishment request.
  • the CSI terminal may further carry a fallback indication in its subsequent call setup request initiated by the CS, so that in the subsequent process, the CS network or the CS domain and the IMS domain interworking gateway may be in accordance with the fallback indication. Special handling of CSI service related fallback calls.
  • Step 804 After receiving the call setup request, the CS network involved in the CSI terminal routes the call to the CS domain and the IMS domain interworking gateway according to the analysis result of the called number of the call setup request.
  • the CSI terminal picks up a specific prefix to form a called number before the MSISDN number of the opposite end, or a method of carrying the fallback indication directly in the CS call setup request
  • the CSI terminal may perform, but is not limited to, the following special processing according to the specific prefix or the fallback indication carried in the call setup request message added before the MSISDN number of the peer end in the call setup request:
  • Step 805 The CS domain and the IMS domain interworking gateway perform IMS and CS interworking, and the IMS is The session establishment request is sent to the peer.
  • step 803 if the CSI terminal adopts a method of adding a prefix to the MSISDN number of the opposite end to form a called number or directly carrying a fallback indication in the call setup request, the CSI terminal performs the method in step 805.
  • the CS domain and the IMS domain interworking gateway may perform, but is not limited to, a process of adding a fallback indication in the IMS session establishment request that is mapped and sent to the peer end.
  • Step 806 After the terminal is connected to the IMS session establishment request, the IMS session is established through the interaction between the IMS network and the CS domain and the IMS domain interworking gateway, and the IMS user ringing and IMS are returned to the CS domain and the IMS domain interworking gateway. User response message.
  • the peer acquires the MSISDN of the CSI terminal, in this step, the peer determines that the received When the MSISDN in the From header field in the IMS Session Establishment Request message is the same as the MSISDN number acquired in step 802, special processing is performed; or, in the above step 805, if the IMS/CS gateway performs the IMS session establishment request The process of carrying the fallback indication is performed in this step.
  • the special treatments described include, but are not limited to, the following processing:
  • Step 807 The CS domain and the IMS domain interworking gateway return an IMS response confirmation to the opposite end, and then establish an IMS session between the peer end and the CS domain and the IMS domain interworking gateway, and the CS domain and the IMS domain interworking gateway perform IMS and CS interworking processing.
  • the process mapping establishes a corresponding process for the CS session, and the CS network involved in the CSI terminal returns the CS user ringing and the CS user response to the CSTM in the CSI terminal, and establishes a CS call connection with the CSTM in the CSI terminal.
  • the process of reverting the IMS session that needs to be applied to the CSI service to the CS call is completed, and the CSI terminal can still communicate with the peer when the CSI service cannot be implemented.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • General Business, Economics & Management (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Reduction Or Emphasis Of Bandwidth Of Signals (AREA)
  • Communication Control (AREA)

Description

一种实现通信的方法和***
技术领域
本发明涉及第三代移动通信网络中的综合电路交换承载与 IP 多媒 体子***业务的综合业务(CSI )技术, 特别是涉及一种保证 CSI终端 实现通信的方法和***。 发明背景
目前, 基于 Internet和电信网络融合的趋势, 3GPP在分组承载网基 础上引入了全 IP业务网络架构的 IP多媒体子***(IMS )。 IMS的目标 是按照个性化用户数据、 屏蔽用户接入方式以及控制业务能力的开放程 度来提供多媒体的通信体验。
传统的通信网络分为电路交换域(CS )和分组交换域(PS ), 分别 完成电路交换业务(包括语音业务、 电路型数据业务、 传真等)和分組 数据业务。 IMS中的信令和媒体流都通过 PS承载。 由于 CS和 PS对于 网络资源的处理不同, CS是独占资源型, PS则是共享资源型, 所以对 于实时性要求较高的业务, 如语音业务, 用 IMS实现即采用 PS承载传 输相比采用 CS承载传输的业务盾量将会显著下降, 从而无法满足运营 商和用户的业务需求。 为此, 国际标准化组织 3GPP提出了将 CS承载 与 IMS业务相结合的综合业务 CSI, 也就是将多媒体业务通过 PS承载 和 CS承载相结合的方式来实现, 将实时性要求高的语音业务, 仍通过 CS 承载, 其它实时性要求不高的业务, 如图片、 消息业务等, 则通过 PS承载, IMS完成统一控制。
图 1是实现 CS承载与 IMS业务结合的 CSI业务的示意图。 参见图 1 , 就用户业务体验而言, 在用户操作上 CSI业务和 IMS提供的多媒体 业务是基本一致的, 但在传递时延等方面则因为综合业务中实时性要求 较高的媒体流部分采用了 CS承载而有了较大的提高。
目前, 3GPP TS 23.899标准提出了实现 CSI业务的一种备选方案的 逻辑功能框架。 图 2是实现 CSI业务的逻辑功能框架示意图。 参见图 2, 在 3GPP TS 23.899所提出的备选方案的逻辑功能框架中包括电路承载控 制功能 (CBCF )、 电路承载始发功能 (CBOF ) 和电路承载终结功能 ( CBTF )三个逻辑功能实体,由 CBCF在 IMS业务中判断并控制 CBOF 和 CBTF间 CS承载的建立。 三个功能实体可在原有 IMS实体中实现, 如终端(UE )、 应用服务器(AS ), 具体分布则在会话建立过程中协商, CBOF或 CBTF也可以是一个 SIP用户代理, 这样, 在对端与其间建立 CS承载的含义就是在对端与代表其的一个 CS域与 IMS域互通网关间 建立 CS承载。
3GPP TS 23.899标准所提出的备选方案中提出了实现 CSI业务的终 端到终端以及终端到网关两种不同的模式, 在终端到网关模式下, CS 承载建立的方向可以是终端到网络或相反,与实际建立的 IMS会话方向 无关。 另外, 3GPP TS 23.899标准同时提出了 CSI实现方案应该遵循的 原则以及需要解决的问题, 比如,要求方案的实现应仅限于影响 IMS及 支持 CSI的终端, 其他网元、终端以及 IMS与他网的互通信令都应该不 受影响, 应提供 CS/PS/IMS的计费关联, 并确保对终端用户的计费一致 性, 等等。
然而, 在目前, 也仅仅存在上'述基于 3GPP TS 23.899标准的实现 CSI业务的逻辑功能框架、 实现 CSI业务的模式、 所遵循的原则以及所 需解决的问题, 而并不存在具体的实现 CSI业务的技术方案, 比如, 目 前还没有针对具备 CSI控制功能的终端 (以下筒称为 CSI终端) 实现 CSI业务的具体方案, 同时, 在实现 CSI业务的过程中, 也并不存在当 CS承载异常释放时使 CSI终端能够继续进行通信的解决方法, 因此极 大地限制了 CSI业务的适用性和可扩展性。 另外, 由于 CSI业务的实现 需要终端和网络都能支持同时保持 CS和 PS空口连接的能力,而网络能 力因终端当前接入网络的不同而不同, 因此, 对于 CSI业务, 如果 CSI 终端在接收到 CSI呼叫时, 该 CSI终端所接入的无线接入网络无法同时 保持与 CS和 PS的空口连接, 也就是说, CSI终端无法继续进行后续的 CSI业务时, 为保证该 CSI终端的通信应该进行何种业务处理, 在目前 也不存在具体的解决方案。 由此可见, 如何保证 CSI终端实现通信已经 成为了一个亟待解决的问题。 发明内容
本发明的主要目的在于提供一种实现通信的方法, 本发明的另一目 的在于提供一种实现通信的***, 从而保证 CSI终端能够实现通信。
为了达到上述目的, 本发明的技术方案是这样实现的:
一种实现通信的方法, 该方法包括:
A、 综合业务 CSI终端中的 IMS终端模块 IMS TM指示 CSI终端中 的 CS终端模块 CS TM发起 CS承载建立;
B、 CS TM将 IMS TM作为被叫向 CS域呼叫控制实体发送呼叫建 立请求;
C、 CS域呼叫控制实体根据接收到的呼叫建立请求中被叫号码信息 将呼叫建立请求路由到 CS域与 IMS域互通网关;
D、 CS域与 IMS域互通网关将接收到的呼叫建立请求转化为 IMS 会话建立请求后发送至 IMS TM;
E、
间的关联控制, 实现 CSI业务 5 001635 在步骤 A之前, 该方法进一步包括: IMS TM判断 IMS业务所需交 互的媒体流中是否包含有需要通过 CS承载传输的媒体流, 如果是, 则 执行步骤 A。
所述 IMS TM在准备发起 IMS会话建立请求、 接收到对端发来的 IMS会话建立请求、在 IMS会话过程中准备发起重协商请求或者接收到 对端发来的重协商请求时, 执行所述判断的步骤。
在步骤 A之前, 该方法进一步包括: IMS TM判断当前是否满足实 现 CSI业务的条件, 如果是, 则执行步骤 A。
所述 IMS TM判断当前是否满足实现 CSI业务条件的步骤包括: IMS TM判断自身所接入的小区是否具备同时保持 CS和 PS空口连接的能力, 如果是, 则判断当前满足实现 CSI业务的条件。
所述 IMS TM在判断出自身所接入的小区具备同时保持 CS和 PS空 口连接的能力之后, 并在判断当前满足实现 CSI业务的条件之前, 进一 步包括: IMS TM判断所确认的用户意愿是否为进行 CSI业务, 如果是, 则判断当前满足实现 CSI业务的条件。
所述 IMS TM确认用户意愿的方式包括: IMS TM通过提供特定用 户界面并接收用户输入的业务实现方式确定用户意愿, 或, IMS TM根 据用户预先所设置的业务实现方式确定。
所述步骤 A进一步包括: IMS TM将本次会话所要求的承载能力指 示信息提供给 CS TM;
所述呼叫建立请求中携带 IMS TM所提供的承载能力指示信息; 在发送 IMS会话建立请求之前, 所述步骤 D进一步包括: CS域与 IMS域互通网关才 据呼叫建立请求中携带的承载能力指示信息预留包括 IP地址和 UDP端口的 IP端口资源;
在步骤 D中,所述 CS域与 IMS域互通网关将 IMS会话建立请求发 送至 IMS TM的步骤包括: 所述 CS域与 IMS域互通网关将所预留的 IP 端口资源的 IP地址和 UDP端口信息携带在 IMS会话建立请求中发送至 IMS TM;
所述步驟 E包括: IMS TM以背靠背 SIP用户代理 B2BUA模式关 联处理与对端及与 CS域与 IMS域互通网关间的两段会话建立过程, 所 述以 B2BUA模式关联处理包括:
IMS TM从接收到的 IMS会话建立请求中获取会话描述协议指示 , 将所获取的会话描述协议指示作为自身对应的 IMS会话中申请采用 CS 承载的媒体流的本端描述指示, 处理与对端间的 IMS域会话建立过程; 并且, IMS终端模块利用与对端之间 IMS会话建立过程中得到的关于申 请采用 CS承载的媒体流的对端的会话描述协议指示, 作为本侧会话描 述协议指示,处理与 CS域与 IMS域互通网关间的 IMS域会话建立过程, 建立自身与对端间的 IMS会话连接以及自身经过 CS域与 IMS域互通网 关至 CS TM的 IMS与 CS互通呼叫连接,并由此使得 CS域与 IMS域互 通网关与对端间利用所预留的 IP端口资源交互 CSI终端与对端间 IMS 会话中申请釆用 CS承载的媒体流, 该采用 CS承载的媒体流进而通过 CS域与 IMS域互通网关与 CS TM间建立的 CS承载传输到 CSI终端。
该方法进一步包括: 预先为 CS TM分配该 CS TM在 CS域签约的 移动台国际 ISDN ( MSISDN )号码;
在步骤 A中, 进一步包括: IMS TM获取 CS TM的 MSISDN号码; 所述步驟 D进一步包括: CS域与 IMS域互通网关根据呼叫建立请 求中的主叫号码获取 CS TM的 MSISDN号码, 并在向 IMS TM发送的 IMS会话建立请求 From头域中携带所获取的 CS TM的 MSISDN号码; 在步骤 E中, 在 IMS TM执行所述关联处理之前进一步包括: IMS TM从接收到的 IMS会话建立请求 From头域中获取 CS TM的 MSISDN 号码, 判断当前所获取的 CS TM的 MSISDN号码与在步驟 A中获取的 CS TM的 MSISDN号码是否相同, 如果是, 则继续执行所述的关联处 理的步驟。 '
当所述 IMS TM与 CS TM设置在不同终端内时, 在步骤 A中, 所 述 IMS TM通过与 CS TM所进行的实时交互或预先交互的过程获取所 述 CS TM的 MSISDN, 其中,
所述通过实时交互获取包括: IMS TM首先通过自身与 CS TM之间 的接口向 CS TM发起请求, CS TM接收到该请求之后, 将自身的 MSISDN发送至 IMS TM, IMS TM获取该 CS TM的 MSISDN;
所述通过预先交互获取包括:在 IMS TM和 CS TM启动时, IMS TM 向 CS TM发起请求, CS TM接收到该请求之后, 将自身的 MSISDN发 送至 IMS TM, IMS TM将接收到的 MSISDN保存在自身的緩存中, 并 在当前从自身緩存中获取所保存的 CS TM的 MSISDN;
当 IMS TM与 CS TM集成在同一终端中,且釆用共享数据区域存储 CS TM的 MSISDN号码时, 在步骤 A中, 所述获取包括: IMS TM从 共享数据区域中获取 CS TM的 MSISDN。
该方法进一步包括: 预先为 IMS TM分配 E.164号码, 并在 CS域 呼叫控制实体为该 IMS TM的 E.164号码配置被叫分析数据;
在步骤 A中, IMS TM在指示 CS TM发起所述 CS承载建立时提供 为 IMS TM分配的 E.164号码;
所述步骤 A进一步包括: A0、 CS TM获取 IMS TM的 E.164号码; 所述步骤 B包括: CS TM将获取的 IMS TM的 E.164号码作为被叫 号码携带在呼叫建立请求中发送至 CS域呼叫控制实体;
在步骤 C中, CS域呼叫控制实体根据作为被叫号码的 IMS TM的 E.164号码及所配置的被叫分析数据将所述的呼叫建立请求路由到 CS域 与 IMS域互通网关。
所述 IMS TM与 CS TM设置在不同终端内;
所述步骤 A包括: IMS TM将携带自身 E.164号码的 CS承载建立请 求发送至 CS TM;
所述步驟 AO包括: CS TM从 CS承载建立请求中获取 IMS TM的 E.164号码。
所述 IMS TM与 CS TM终端集成在同一终端内;
所述步驟 A包括: IMS TM通过内部指令指示 CS TM发起 CS承载 建立;
所述步骤 AO包括: CS TM从内部指令或与 IMS TM的共享数据区 域中获取 IMS TM的 E.164号码。
所述 IMS TM的 E.164号码中包括区域识别前缀或业务类型前缀; 在步骤 C 中, 所述 CS域呼叫控制实体进一步根据对 IMS TM的 E.164 号码中的区域识别前缀或业务类型前缀的分析将呼叫建立请求发 送至 IMS TM归属区域的 CS域与 IMS域互通网关处或较近的 CS域与 IMS域互通网关处。
该方法进一步包括: 预先设置 IMS TM的 E.164号码与其初始会话 协议统一资源定位符 SIP URI对应关系的转换数据;
在将 IMS会话建立请求发送至 IMS TM之前,所述步驟 D进一步包 括; 所述 CS域与 IMS域互通网关根据呼叫建立请求中携带的作为被叫 号码的 IMS TM的 E.164号码, 进行电话号码映射(ENUM )服务器查 询, 通过所设置的转换数据获取 IMS TM的初始会话协议统一资源定位 符 SIP URI;
在步骤 D中, 所述 CS域与 IMS域互通网关根据所获取的 IMS TM 的初始会话协议统一资源定位符 SIP URI将呼叫建立请求转化为 IMS会 话建立请求后发送至 IMS TM。
在步驟 D中, 所述 CS域与 IMS域互通网关进行 ENUM服务器查 询的步骤进一步包括: CS域与 IMS域互通网关根据查询结果判断呼叫 建立请求中的 IMS TM的 E.164号码是否存在对应的转换数据,如果是, 则确定当前 CSI业务合法, 继续执行通过对应转换数据获取 IMS TM的 初始会话协议统一资源定位符 SIP URI的步骤, 否则, 结束当前流程。
所述步骤 A进一步包括: 所述 IMS TM将自身的初始会话协议统一 资源定位符 SIP URI地址提供给 CS TM;
所述步骤 B进一步包括: CS TM将携带 SIP URI地址的用户到用户 信息信元发送至 CS域呼叫控制实体;
所述步骤 C进一步包括: CS域呼叫控制实体将携带 SIP U I地址的 用户到用户信息信元发送至所述 CS域与 IMS域互通网关;
所述步骤 D包括: 所述 CS域与 IMS域互通网关通过用户到用户信 息信元获取 SIP URI地址, 并根据所获取的 SIP URI将会话建立请求转 化为 IMS会话建立请求后发送至 IMS TM。
在步骤 D中, CS域与 IMS域互通网关在发送的 IMS会话建立请求 的会话描述协议指示中进一步携带专用指示信息, 其中, 所述的专用指 示信息通过对所述 IMS会话建立请求的会话描述协议进行扩展定义实 现;
所述步骤 D进一步包括: IMS域代理呼叫与会话控制功能实体在将 IMS会话建立请求发送至 IMS TM时, 根据所述的专用指示信息识别经 由 CS承载的媒体流并进行特殊的资源预留处理。
在步骤 E之后, 该方法进一步包括: 在会话结束时, 所述 IMS TM 指示 CS TM释放所建立的 CS承载, CS TM按照标准的 CS流程发起呼 叫释放请求, CS呼叫控制实体与互通网关接收到 CS承载释放请求后, 完成对所建立的 CS承载的释放过程,并且,互通网关接收到 CS承载释 放请求后完成与 IMS TM之间的 IMS域回呼的释放。
所述 IMS TM不支持初始会话协议扩展;
所述步骤 D进一步包括: Dl、 CS域与 IMS域互通网关通过与 IMS TM 间端到端协商过程完成与不支持初始会话协议扩展的终端间互通的 IMS域回呼的建立。
在步骤 D1中, CS域与 IMS域互通网关通过预先查询 IMS TM能力, 采用不要求支持初始会话协议扩展的方式完成 IMS 域回呼的建立; 或 CS域与 IMS域互通网关接收到 IMS TM返回的不支持初始会话协议扩 展的指示后重新发起不要求支持初始会话协议扩展的 IMS会话建立请 求, 并进而完成 IMS域回呼的建立。
该方法进一步包括: 预先在 CS域的各个处理节点中设置 CS TM和 IMS TM分别对应的 E.164号码之间的对应关系;
所述步骤 C进一步包括: CS域各个处理节点在发送所述呼叫建立 请求时,判断该呼叫建立请求中主被叫号码所对应的 CS TM的 E.164号 码与 IMS TM对应的 E.164号码之间是否存在预先设置的对应关系, 如 果存在, '则进行与所述 IMS会话的关联计费处理。
该方法进一步包括: 预先为 IMS TM对应的 E.164号码分配特殊前 缀, 并在 CS域呼叫控制实体配置针对该特殊前缀的分析数据, 通过对 该特殊前缀的分析避免 CS主叫侧补充业务及智能业务对 CSI业务 CS 承载建立过程产生影响;
所述 IMS TM的 E.164号码中进一步包括所分配的特殊前缀; 所述步骤 C进一步包括: CS域呼叫控制实体接收到携带该特殊前 缀的 IMS TM的 E.164号码后, 根据针对该特殊前缀的配置数据, 在本 次呼叫中禁止影响 CSI业务 CS承载建立过程的 CS主叫侧补充业务的 调用及智能业务的触发。
所述 IMS TM作为被叫接收到对端发来的 IMS会话建立请求; 在判断出当前不满足实现 CSI业务的条件之后,该方法进一步包括:
Gl l、 IMS TM向对端发送 IMS会话改向指示, 并在该 IMS会话改 向指示中携带 CS TM在 CS域的寻址号码;
G12、对端接收到 IMS会话改向指示后,释放请求建立的 IMS会话, 并将 IMS会话改向指示中携带的寻址号码作为被叫号码向 CS TM发起 IMS域的会话请求;
G13、 对端所涉及的 IMS网络根据对端所发送的会话请求中的被叫 号码, 将该会话建立发送至 CS域与 IMS域互通网关;
G14、 CS域与 IMS域互通网关将接收到的 IMS会话请求映射为 CS 呼叫, 通过 CS网络将 CS呼叫发送至 CS TM;
G15、 CS TM通过 CS网絡与 CS域与 IMS域互通网关建立 CS呼叫 连接, CS域与 IMS域互通网关与对端建立 IMS会话连接。
所述寻址号码为 CS TM在 CS签约的 MSISDN。
所述寻址号码为 CS TM在 CS签约的 MSISDN添加特定前缀或特殊 标识构成;
所述步驟 G14进一步包括: 所述 CS域与 IMS域互通网关扣除寻址 号码中所添加的特定前缀或特殊标识;
在步骤 G14中, 在 CS网络中所传送的寻址号码为 CS TM在 CS签 约的 MSISDN。
所述步骤 G14进一步包括: CS域与 IMS域互通网关在所发送的 CS 呼叫中添加回落指示, CS网络和 /或 CS TM根据接收到的 CS呼叫中所 添加的回落指示进行 CSI业务回落呼叫处理。
当 CS网络进行所述 CSI业务回落呼叫处理时, 该 CSI业务回落呼 叫处理包括: 特殊的计费处理和 /或业务冲突处理;
当 CS TM进行所述 CSI业务回落呼叫处理时,该 CSI业务回落呼叫 处理包括: 提示用户当前呼叫为 CSI业务相关回落呼叫, 或, 提示用户 当前呼叫为 CSI业务相关回落呼叫, 并进一步在用户控制下启用呼叫偏 转处理。
所述 IMS TM作为被叫接收到对端发来的 IMS会话建立请求; 在判断出当前不满足实现 CSI业务的条件之后,该方法进一步包括:
G21、 IMS TM向对端发送 IMS会话释放指示, 对端接收到 IMS会 话释放指示后, 释放请求建立的 IMS会话;
G22、 CS TM在 CS发起呼叫建立请求, 该呼叫建立请求中的被叫 号码为对端的 E.164号码;
G23、 CS网络接收到呼叫建立.请求后, 根据对该呼叫建立请求的被 叫号码分析结果将呼叫路由到 IMS与 CS互通网关。
G24、 IMS域与 CS域互通网关将接收到的呼叫建立请求映射为 IMS 会话请求, 通过对端所涉及的 IMS网络将该 IMS会话请求发送至对端;
G25、 对端与 IMS域与 CS域互通网关建立 IMS会话连接, IMS域 与 CS域互通网关执行 IMS/CS互通处理与 CS TM建立 CS呼叫连接。
在步骤 G21中,所述 IMS TM发送至对端的 IMS会话释放指示中携 带 CS TM在 CS域的寻址号码;
在步骤 G24与步骤 G25之间, 进一步包括: 对端接收到 IMS会话 建立请求后, 从该 IMS会话建立请求中获取 CS TM的号码, 并判断所 获取的号码与所接收到的 IMS会话释放指示中携带的 CS TM的号码是 否相同, 如果是, 则进行 CSI业务回落呼叫处理。
所述对端进行 CSI业务回落处理的步骤包括: 提示对端用户当前呼 叫为 CSI业务相关回落呼叫, 并进一步在会话建立过程中免于振铃。 当 CS承载异常释放时, 所述步骤 E进一步包括: CS TM和 CS域 呼叫控制实体之间以及 CS域呼叫控制实体和 CS域与 IMS域互通网关 之间互通释放所建立的 CS承载; CS域与 IMS域互通网关 #放与 IMS TM间的 IMS会话连接; IMS TM利用重协商过程建立分组交换 PS承载, 并与对端利用所建立的 PS承载对原利用所鋒放 CS承载传输的对应媒体 流进行交互。
一种实现通信的方法, 应用于在 CSI业务的实现过程中 CS承载异 常释放的情况, 该方法包括:
a、 CS TM和 CS域呼叫控制实体之间以及 CS域呼叫控制实体和 CS 域与 IMS域互通网关之间互通释放所建立的 CS承载;
b、 CS域与 IMS域互通网关释放与 IMS TM间的 IMS会话连接; c、 IMS TM利用重协商过程建立分组交换 PS承载, 并与对端利用 所建立的 PS承载对原利用所幹放 CS承载传输的对应媒体流进行交互。
在步骤 c之前进一步包括: IMS TM通知对端暂停通过 CS承载传递 媒体流;
在步骤 c中, 在建立所述 PS承载之后, 并在利用所建立的 PS承载 进行传输之前, 进一步包括: IMS TM通知对端恢复对原通过 CS承载 的媒体流的发送。
在步骤 c中,所述 IMS TM利用重协商过程建立 PS承载与对端进行 媒体交互的步骤包括: IMS TM向对端发起更改交互媒体流的请求, 完 成本侧 PS承载资源的申请和建立, 并通知对端将原来交互到 CS域与 IMS域互通网关进而利用 CS承载传递到 CSI终端的媒体流改向交互至 CSI终端 PS承载端口。
一种实现通信的***, 该***包括:
CS域呼叫控制实体, 用于与 CS TM交互并建立 CS承载, 并将由 IMS TM控制、 CS TM发起建立的建立 CS承载的呼叫路由到 CS域与 IMS域互通网关上;
CS域与 IMS域互通网关,用于将 CS域呼叫控制实体控制路由到本 端的 CS呼叫转换为 IMS会话建立请求,并将该 IMS会话建立请求经 IMS 会话控制实体接续到控制发起建立 CS承载过程的 IMS TM, 从而在 CS TM和 IMS TM间建立 CS到 IMS互通呼叫; 并且, CS域与 IMS域互 通网关将为 IMS域交互媒体流预留的 IP端口资源的 IP地址和端口信息 传递到 IMS TM, 并利用自身与 CS TM间建立的 CS承载将与对端通过 IP承载交互的媒体流与 CS TM间进行交互;
IMS TM, 用于实现 CS承载控制功能, 在 IMS业务中判断并控制 CS TM发起 CS承载的建立过程, 并在后续收到 .CS域与 IMS域互通网 关转发的回呼后采用背靠背用户代理方式完成自身与 CS域与 IMS域互 通网关及与对端间两段 IMS会话的关联控制,令对端将其与本端用户间 IMS会话中交互的对应 CS承载的媒体流首先通过 CS域与 IMS域互通 网关预留的 IP端口传递到 CS域与 IMS域互通网关上, 进而经过 CS域 与 IMS域互通网关与 CS TM间建立的 CS承载传递到本侧终端; CS TM, 用于在接收到 IMS TM的指令后将 IMS TM作为被叫发起 CS承载的建 立请求, 并与 CS域呼叫控制实体进行交互完成 CS承载的建立过程。
所述 IMS TM与所述 CS TM集成在同一终端内。
所述 IMS TM与所述 CS TM设置在不同终端内,通过无线短距离通 信方式进行连接; ' 所述 CS域呼叫控制实体, 进一步用于在接收到对端通过 CS域与 IMS域互通网关发来的 CSI回落到 CS的呼叫建立请求后将该呼叫建立 请求发送至 CS TM,或将 CS TM发来的 CSI回落到 CS的呼叫建立请求 发送至 CS域与 IMS域互通网关;
CS域与 IMS域互通网关, 进一步用于在接收到对端发来的 CSI回 落到 CS的 IMS会话建立请求后, 将该 CSI回落到 CS的 IMS会话建立 请求转换为 CSI回落到 CS的呼叫建立请求后发送至 CS域呼叫控制实 体; 或者, 用于在接收到 CSI终端 CS TM经 CS域呼叫控制实体发来的 CSI回落到 CS的呼叫建立请求后将其转换为 CSI回落到 CS的 IMS会 话建立请求后发送至对端;
IMS TM,进一步用于在确定无法满足实现 CSI业务条件时, 向对端 返回 IMS会话改向指示或 IMS会话释放指示, 使对端与自身完成 IMS 会话释放 ^
CS TM, 进一步用于在接收到对端用户在 IMS发起并通过 CS域与 IMS域互通网关及 CS域呼叫控制实体发来的呼叫建立请求后 ,通过 CS 域呼叫控制实体及 CS域与 IMS域互通网关与对端建立 CSI回落到 CS 的 IMS到 CS互通呼叫连接; 或, 将对端作为被叫, 通过 CS域呼叫控 制实体及 CS域与 IMS域互通网关主动与对端建立 CSI回落到 CS的 CS 到 IMS互通呼叫连接。
可见, 本发明具有以下优点:
1、 本发明提供了一个终端到网关 /终端控制模式下 CSI业务的具体 的实现方案, 包括 CBCF在用户终端中的具体实现形式, 以及在终端和 相关 CS/IMS域网元,比如 CS域呼叫控制实体或 IMS域呼叫控制实体, 配合下 CSI业务的具体实现过程; 进一步地, 对于 CSI终端漫游情况下 可能出现的 CS路由迂回问题、 实现 CS/IMS关联计费问题、 非标准终 端接入以及 CS承载异常释放情况下相应处理等问题, 本发明均提供了 具体的解决方法。 因此, 本发明为在 CSI终端上实现 CSI业务提供了一 种实际应用处理过程中的切实可行的技术方案, 从而确保了 CSI终端实 现 CSI业务通信过程。
2、在本发明中, 当作为被叫的 CSI终端由于当前网络能力原因或用 户选择无法实现 CSI业务时, CSI终端能够将接收到的 CSI呼叫回落为 CS呼叫, 进一步确保.了 CSI终端的通信过程。 附图简要说明
图 1是实现 CS承载与 IMS业务结合的 CSI业务的示意图。
图 2是实现 CSI业务的逻辑功能框架示意图。
图 3是本发明***的示意图。
图 4是在本发明中使 CSI终端实现 CSI业务的流程图。
图 5是在本发明中针对 CS承载异常释放的处理流程图。
图 6是在本发明中 CSI终端中 IMS终端模块不支持 SIP协议扩展时 的处理流程图。 ·
图 7是在本发明中实现将 CSI会话回落到 CS呼叫的方式一的流程 图。
图 8是在本发明中实现将 CSI会话回落到 CS呼叫的方式二的流程 图。 实施本发明的方式
为使本发明的目的、 技术方案和优点更加清楚, 下面结合附图及具 体实施例对本发明作进一步地详细描述。
在现有技术中, 针对具备 CSI控制功能的终端, 即 CSI终端, 并未 提供实现 CSI业务的具体实现过程, 因此极大地限制了 CSI业务的适用 性和可扩展性。 针对这一缺点, 本发明提出了一种针对 CSI终端实现通 信的方法, 其核心思想是: CSI终端中的 IMS终端模块(IMS TM )根 5 001635 据当前 IMS业务的需要指示 CSI终端中的 CS终端模块(CS TM )发起 CS承载建立过程; CS TM将 IMS TM作为被叫向 CS域呼叫控制实体发 送建立 CS承载的 CS呼叫建立请求; CS域呼叫控制实体根据接收到的 呼叫建立请求中被叫号码信息将呼叫建立请求路由到 CS域与 IMS域互 通网关; CS域与 IMS域互通网关将接收到的呼叫建立请求转化为 IMS 会话建立请求后发送至 IMS TM; IMS TM进行与 CS域与 IMS域互通 网关以及与对端间两段会话间的关联控制, 建立 IMS TM自身与对端间 的 IMS会话连接以及 IMS TM自身经 CS域与 IMS域互通网关与对应的 CS TM间的 IMS-CS互通连接, 在所述 IMS TM自身经 CS域与 IMS域 互通网关与对应的 CS TM间的 IMS-CS互通连接中建立 CS TM与 CS 域与 IMS域互通网关间的 CS承载 , 通过 IMS TM对两段会话间的关联 控制, 使得对端利用其到 CS域与 IMS域互通网关间的 IP承载和 CS域 与 IMS域互通网关与 CS TM闳的 CS承载两段承载, 与该 CSI终端交 互该次 CSI业务中需要由 CS承载的实时性要求较高的媒体流。
另外, 在本发明方法中, 当 CSI终端作为被叫接收到需要应用 CSI 业务的 IMS会话时,如果当前不满足实现 CSI业务的条件, 则本发明还 可进一步将 CSI呼叫回落为 CS呼叫, 使得 CSI终端能够继续与对端进 行通信。
根据 3GPP TS 23.899标准所定义的图 2所示的实现 CSI业务的逻辑 功能框架, 本发明提出了一种针对终端到网关 /终端控制模式下的***。 图 3是本发明***的示意图。 参见图 3 , 本发明***包括 CSI终端、 CS 呼叫控制实体以及 CS域与 IMS域互通网关, 其中, CSI终端又具体包 括: 实现 CBCF功能和 CBTF功能的 IMS终端模块( IMS TM )和实现 CBOF功能的 CS终端模块( CS TM ), 其中,
CS域呼叫控制实体, 比如为移动交换中心(MSC ), 用于与 CS TM 交互并建立 CS承载, 并将由 IMS TM控制、 CS TM发起建立 CS承载 的 CS呼叫路由到 CS域与 IMS域互通网关上, 即在网络中从 CS TM经 CS呼叫控制实体到 CS域与 IMS域互通网关间建立一条 CS承载路径; 并且, 在接收到对端通过 CS域与 IMS域互通网关发来的 CSI回落到 CS的呼叫建立请求后将该呼叫建立请求发送至 CS TM, 或将 CS TM发 来的 CSI回落到 CS的呼叫建立请求发送至 CS域与 IMS域互通网关。
CS域与 IMS域互通网关, 用于与 CS TM交互并建立 CS承载, 将 CS域呼叫控制实体控制路由到本端的 CS呼叫转换为 IMS会话建立请 求, 并将该 IMS会话建立请求经 IMS会话控制实体接续到控制发起建 立 CS承载过程的 IMS TM; 并且, 在接收到对端发来的 CSI回落到 CS 的 IMS会话建立请求后,将该 CSI回落到 CS的 IMS会话建立请求转换 为 CSI回落到 CS的 CS呼叫建立请求后发送至 CS域呼叫控制实体,或 者, 在接收到 CSI终端经 CS域呼叫控制实体发来的 CSI回落到 CS的 CS呼叫建立请求后将其转换为 CSI回落到 CS的 IMS会话建立请求后 发送至对端。
所述 CS域与 IMS域互通网关将会话接续到所述 IMS TM的过程可 以通过图 3中标示为 2的细实线和虚线路径完成; 并且, CS域与 IMS 域互通网关将为 IMS域交互媒体流所预留的 IP端口资源的 IP地址和端 口信息传递到 IMS TM, 并利用自身与 CS TM间建立的 CS承载将对端 与该预留 IP端***互的媒体流进而与 CS TM间进行交互。
IMS TM, 用于实现 CS承载控制功能, 在 IMS业务中判断并控制 CS TM发起 CS承载的建立过程, 并在后续收到 CS域与 IMS域互通网 关转发的回呼后采用背靠背用户代理(B2BUA )方式完成自身与 CS域 与 IMS域互通网关及自身与对端间两段 IMS会话的关联控制, 令对端 将其与本端用户间 IMS会话中交互的需要经 CS承载的对应媒体流首先 通过 CS域与 IMS域互通网关预留的 IP端口传递到 CS域与 IMS域互通 网关上,进而经过 CS域与 IMS域互通网关与 CS TM间建立的 CS承载 传递到本侧终端; 在确定无法实现 CSI业务时, 向对端返回 IMS会话改 向指示或 IMS会话释放指示, 使对端与自身完成 IMS会话释放。
CS TM, 用于在接收到 IMS TM的指令后将 IMS TM作为被叫发起 CS承载的建立请求, 并与 CS域呼叫控制实体进行相应的交互完成 CS 承载的建立过程;或,在接收到对端用户在 IMS发起并通过 CS域与 IMS 域互通网关及 CS域呼叫控制实体发来的呼叫建立请求后, 与对端建立 CSI回落到 CS的 IMS到 CS互通呼叫连接; 或, 将对端作为被叫通过 CS域呼叫控制实体及 CS域与 IMS域互通网关主动与对端建立 CSI回 落到 CS的 CS到 IMS互通呼叫连接。
参见图 3 , 粗实线表示 CS承载和信号路径, 细实线表示 PS承载路 径, 虚线表示 SIP消息路径, 当 IMS业务中在两端用户间交互的媒体流 中出现需要通过 CS承载的媒体流时, 则可以通过由对端首先经过 IP承 载交互到 CS域与 IMS域互通网关, 进而通过图 3中粗实线表示的 CS 域与 IMS域互通网关到 CS TM间的 CS承载传输到 CSI终端, 从而利 用本发明***实现了 CSI业务。
在本发明***中, IMS TM和 CS TM既可以集成在同一终端中, 也 可设置在不同终端中。 当 IMS TM和 CS TM设置在不同终端中时, 所 述 IMS TM与 CS TM间可以采用但不限于蓝牙等方式进行短距离无线 连接,并且, IMS TM可以采用但不限于以下方式实现:个人计算机( PC ) 或个人数字助理( PDA ), 即采用内置于 PC或 PDA中的软件实现所述 的 IMS TM。
另外, CS TM和 IMS TM中还保存各自 E.164号码, 可以分别存储 在各自对应存储模块中; 在 IMS TM和 CS TM集成在同一终端的情况 下, 也可以将 CS TM和 IMS TM各自的 E.164号码均存储在 CS TM和 IMS TM共享的数据区域中。
图 4是在本发明中使 CSI终端实现 CSI业务的流程图。 参见图 3和 图 4, 利用本发明***, 本发明方法使 CSI终端实现 CSI业务的过程具 体包括以下步骤:
步骤 401 :预先为 CS TM和 IMS TM分别分配 E.164号码,并在 CS 域呼叫处理节点上对于为 IMS TM分配的 E.164号码配置被叫分析数据。
这里, 为 CS TM和 IMS TM分别分配的 E.164号码是在 CS和 IMS 网络中能够有效标识 CS TM和 IMS TM 的 E.164号码。 比如说, 为 CS TM所分配的 E.164号码为 CS TM所属用户在 CS域签约的移动台国际 ISDN ( MSISDN )号码, 为 IMS TM所分配的 E.164号码为 IMS TM所 属用户在 IMS网络签约的号码。
这里, 在 CS域呼叫处理节点, 即 CS中需传送呼叫的各个节点, 比 如本发明***中的 CS域呼叫控制实体, 配置被叫分析数据, 是为了在 后续过程中, CS域中的各个呼叫处理节点能够将呼叫路由到 CS与 IMS 的互通网关。 进一步地, 在 CS域呼叫处理节点配置被叫分析数据, 还 可在后续过程中使 CS 域中的各个呼叫处理节点能够识别本次业务为 CSI业务, 从而进行特殊的计费及业务处理。
另外, 在本步骤中, 为 IMS TM所分配的 E.164号码中可以包括区 域识别前缀和 /或业务类型前缀,以便在后续过程中能够通过该区域识别 前缀和 /或业务类型前缀确定呼叫的路由, 和 /或在后续过程中, CS域中 的各个呼叫处理节点能够识别本次业务为 CSI业务, 从而进行特殊的计 费及业务处理。
步骤 402:作为 CS承载控制功能实体的 IMS TM判断当前是否需要 触发 CSI业务, 如果是, 则执行步骤 403 , 否则, 结束当前建立 CSI业 务的流程。
这里, 所述的 IMS TM可以在准备发起 IMS会话建立请求、 接收到 对端发来的 IMS会话建立请求、 在 IMS会话过程中准备发起重协商请 求或者接收到对端发来的重协商请求时, 执行本步驟中所述的判断的过 程。
另外, 所述的 IMS TM可以根据自身准备交互的媒体流或对方要求 交互的媒体流是否需要通过 CS承载传输, 也就是根据所需交互的媒体 流中是否带有实时多媒体业务流成分, 比如是否包含有语音信息等, 来 判断是否需要触发 CSI业务。
步骤 403: IMS TM判断当前是否满足实现 CSI业务的条件,如果是, 则执行步骤 404, 否则, 结束当前建立 CSI业务的流程。
这里, IMS TM可以根据自身所接入的小区是否具备同时保持与 CS 和 PS 空口连接的能力, 并可进一步根据所确定的用户意愿来判断当前 是否满足实现 CSI业务的条件。 也就是说, 如果自身所接入的小区具备 同时保持与 CS和 PS空口连接的能力,进一步地, 所确定的用户意愿为 进行 CSI业务, 则 IMS TM认为当前满足实现 CSI业务的条件。
在本步骤中, 所述的用户意愿可以通过以下方式来确定:
( 1 )通过在 IMS TM上显示的特定用户界面(如弹出菜单)与用户 进行即时交互而确定; .
( 2 )通过用户预先在 IMS TM上的设置来确定。
步骤 404: IMS TM获取 CS TM的 MSISDN。
这里,如果 IMS TM与 CS TM设置在不同终端内 , 则 IMS TM可以 通过与 CS TM所进行的实时交互或预先交互的过程来获取 CS TM的 MSISDN。 如果通过实时交互的过程, 则本步骤的实现过程为: IMS TM 首先通过自身与 CS TM之间的接口向 CS TM发起请求, CS TM接收到 该请求之后,将自身的 MSISDN发送至 IMS TM, IMS TM获取该 CS TM 的 MSISDN; 如果通过预先交互的过程, 则在 CSI终端 (包括 IMS TM 和 CS TM ) 启动时, IMS TM向 CS TM发起请求, CS TM接收到该请 求之后, 将自身的 MSISDN发送至 IMS TM, IMS TM将接收到的 MSISDN保存在自身的 MSISDN緩存中, 这样, 本步骤的实现过程为: IMS TM从自身緩存中获取所保存的 CS TM的 MSISDN。
如果 IMS TM与 CS TM集成在同一终端中,则以上所述本步骤的过 程属于终端内部模块间的内部交互过程, 此时, 如果 IMS TM与 CS TM 进一步采用共享数据区域存储 IMS TM和 CS TM各自的 E.164号码时, 则本步骤的实现过程为: IMS TM 从共享数据区域中获取 CS TM 的 MSISDN。
步骤 405: IMS TM指示 CS TM发起 CS承载建立。
这里,如果 IMS TM和 CS TM集成在同一终端中, 则本步骤所述的 过程属于终端内部模块间的内部交互过程, 也就是说, IMS TM通过内 部指令指示 CS TM发起 CS承载建立, 并且, 所述指示中包括了相应的 承载能力指示信息;
如果 IMS TM和 CS TM设置在不同终端中,则本步骤所述的过程为: IMS TM通过蓝牙等短距离无线通信方式向 CS TM发送 CS承载建立请 求, 并在该 CS承载建立请求中携带相应的承载能力指示信息。
在本步骤中, 如果 CS TM不能通过直接访问 IMS TM的号码存储 模块来获取 IMS TM的 E.164号码时, 则 IMS TM在所述指示中进一步 携带 IMS TM自身的 E.164号码。
在本步驟中, IMS TM在所述指示中还可以进一步携带 IMS TM的 初始会话协议统一资源定位符(SIP URI )地址, 以在后续过程中方便 CS域与 IMS域互通网关获取该 IMS TM的 IMS域公有标识。 步驟 406: CS TM按照标准的 CS域流程向 CS域呼叫控制实体发送 呼叫建立请求。
这里, CS TM在自身所发送的呼叫建立请求中, 将自身的 MSISDN 作为主叫号码,将从 IMS TM的号码存储模块所获取的或从发自 IMS TM 的 CS承载建立指示 /请求中所菽取的 IMS TM的 E.164号码作为被叫号 码, 并根据 IMS TM提供的承载能力指示填写自身所发送的呼叫建立请 求中的承载能力指示。
这里, 如果 CSI TM向 CS TM提供了 IMS TM的 SIP URI地址, 则 在本步驟中, CS TM可以通过用户到用户信令(UUS )携带该 IMS ΤΜ 的 SIP URI地址并发送至 CS域呼叫控制实体。
步骤 407: CS域呼叫控制实体接收到呼叫建立请求后, 根据其中的 被叫号码信息将该呼叫建立请求路由到 CS域与 IMS域互通网关处。
这里, CS域呼叫控制实体, 比如可以是 MSC, 根据呼叫建立请求 中的被叫号码, 即为发起 CS承载建立过程的 IMS TM分配的 E.164号 码, 以及预先在自身中配置的被叫分析数据, 确定将呼叫路由到 CS与 IMS的互通网关, 从而使得 CS承载与所述 CS域与 IMS域互通网关连 通。
另外, 如果 CS域呼叫控制实体所接收到的被叫号码即为 IMS TM 分配的 E.164号码中包括业务类型前缀, 则在本步骤中, CS域呼叫控制 实体根据对该业务类型前缀的分析将呼叫建立请求转接到较近的 CS域 与 IMS域互通网关处,即在被叫分析数据中将相应的业务类型前缀配置 为路由到最近的 CS域与 IMS域互通网关处, 从而避免 CS承载的路由 迂回。
另外, 如果 CS域呼叫控制实体所接收到的被叫号码即为 IMS TM 分配的 E.164号码中包括区域识别前缀, 则在本步骤中, CS域呼叫控制 实体^据对该区域识别前缀的分析将呼叫建立请求转接到 IMS TM所属 用户归属区域的 CS域与 IMS域互通网关处, 即在被叫分析数据中将相 应的区域识別前缀配置为路由到 IMS TM归属区域的 CS域与 IMS域互 通网关处, 从而保证了 IMS TM在漫游情况下也能够可靠地实现 CSI业 务。
在本步骤中, 如果接收到了通过 uus携带的 IMS TM的 SIP υτ 地址, 则 CS域呼叫控制实体通过 UUS携带该 IMS TM的 SIP URI地址 并发送至 CS域与 IMS域互通网关。
需要说明的是, 如果 CS域呼叫控制实体与 CS域与 IMS域互通网 关为同一网络实体, 则在本流程中可删除本步骤, 即在执行完上述的步 骤 406之后, 直接执行下述的步骤 408。
步驟 408: CS域与 IMS域互通网关获取 IMS TM对应的 IMS域公 有标识,然后将 IMS TM的 IMS域公有标识作为被叫地址向 IMS TM发 送 IMS会话建立请求。
这里, 本发明可以预先在电话号码映射(E UM )服务器中设置为 IMS TM分配的 E.164号码与其 IMS域公有标识对应关系的转换数据, 这样, 在本步骤中, CS域与 IMS域互通网关 MGCF/IM-MGW根据呼 叫建立请求中携带的被叫号码, 即为 IMS TM分配的 E.164号码, 进行 ENUM服务器查询从而通过所设置的转换数据获取 IMS TM的 IMS域 公有标识。 并且, 通过查询 ENUM服务器, 本步骤还实现了对本次 CSI 业务进行鉴权的过程,也就是,当在 ENUM服务中查询到所述为 IMS TM 分配的 E.164号码的转换数据时,则确定允许该 IMS TM应用 CSI业务。
在本步骤中, 所述的 IMS域公有标识是 SIP URI形式, 在 IMS域中 采用的是 SIP URI寻址; 因此, 如果 CS域与 IMS域互通网关接收到了 通过 UUS携带的 IMS TM的 SIP URI地址,则在本步骤中, CS域与 IMS 域互通网关也可直接从 UUS中获取 SIP URI地址即 IMS TM的 IMS域 公有标识。
需要说明的是, 在本步驟中, CS域与 IMS域互通网关从接收到的 呼叫建立请求中的主叫号码获取 CS TM的 MSISDN号码, 并在向 IMS TM发送的会话建立请求消息 From(源)头域中携带 CS TM的 MSISDN 号码。
另外,在本步骤中, CS域与 IMS域互通网关 MGCF/IM-MGW按 IMS 域标准互通流程指示 IM-MGW为 IMS侧交互的媒体流预留端口资源, 并经过 IMS网絡将 IMS会话接续到控制发起 CS承载建立的 IMS TM, 即所述的互通网关向发起 CS承载建立过程的 IMS TM发送 IMS会话建 立请求。
在本步骤中, CS域与 IMS域互通网关在所发送会话建立请求中通 过会话描述协议(SDP )部分指示出在 IM-MGW上为 IMS侧所预留端 口的 IP地址和用户数据报协议( UDP )端口信息, 以便于在后续过程中 CSI终端可以利用该端口资源与对端交互媒体流。
步驟 409: 所述 IMS TM接收到互通网关发来的会话建立请求后, 进行与互通网关以及与对端间两段会话的关联处理。 .
本步骤的具体实现过程包括:
一、 所述 IMS TM获取会话建立请求消息 From (源) 头域中的 MSISDN号码,并判断当前所获取的 MSISDN号码与在步骤 404中所获 取的 CS TM的 MSISDN是否相同, 如果是, 则确定当前的 IMS会话建 立请求为本端请求的 CS承载建立过程对应的 IMS回呼, 而并非其它用 户发起的新的会话建立请求;
二、 所述 IMS TM从接收到的会话建立请求中获取 SDP, 也就是互 通网关为交互媒体流所预留端口的 IP地址和 UDP端口信息, 并将所获 N2005/001635 取的 SDP作为申请采用 CS承载的媒体流所对应的本端会话描述协议指 示发送至对端;
三、 所述 IMS TM接收到对端发来的会话描述协议指示后, 将其中 对应于釆用 CS承载部分的 SDP作为与所述 CS域与 IMS域互通网关间 IMS会话上的本端会话描述协议指示提供给互通网关, 并作为背靠背用 户代理( B2BUA )分别完成与所述 CS域与 IMS互通网关间 CS承载建 立的 IMS回呼过程以及与对端间的 IMS会话建立过程。
通过本步骤 409, 控制发起 CS承载建立的 IMS TM作为 B2BUA分 别完成了自身经 CS域与 IMS域互通网关 MGCF/IM-MGW到 CS TM的 IMS-CS互通会话建立以及自身和对端间的 IMS域会话建立,在 IMS TM 经 CS域与 IMS域互通网关到 CS TM的 IMS-CS互通会话建立中完成了 CS TM和互通网关 MGCF/IM-MGW之间的 CS承载的建立, 并在此过 程中通过在网关和对端间透明传递关于本端决定采用 CS承载的媒体流 部分的会话描述协议指示(即将网关和对端发来的相应会话描述协议指 示分别作为本端会话描述协议指示传递给对端和网关), 使得对端与互 通网关间互为目的地地以 IP承载传递本端决定采用 CS承载的媒体流, 继而通过在互通网关 MGCF/IM-MGW与 CS TM之间所建立的 CS承载 连接, 继续在网关和本端 CSI终端间传递该部分媒体流。
需要说明的是, 由于采用 CS承载的媒体流实际上不再需要进行所 述 CSI终端接入侧的资源预留, 因此, 在本步骤 409中, IMS TM在所 发送的 SDP中添加相关指示, 以表明由 CS承载的媒体流信息, 这样, 当 IMS域的代理呼叫与会话控制功能实体(P-CSCF )接收到 IMS TM 所发来的 SDP时, 根据该 SDP中所添加的相关指示识别该部分媒体流 将经由 CS承载, 从而在资源预留上做特殊处理。 其中, 所述 IMS TM 在所发送的 SDP中添加相关指示的过程可以但不限于采用对 SDP进行 扩展定义的方式来实现, 比如, 利用 SDP中已定义的一个描述或多个描 述组合来指示由 CS承载的媒体流信息。
至此, 则完成了所述 CSI终端中的 IMS TM与 CS TM与对端建立 CSI业务连接的过程, 此后, CSI终端与对端间通过 CSI终端 CS TM到 CS域与 IMS域互通网关间的 CS承载、 CS域与 IMS域互通网关到对端 间的 IP承载两段承载, 传递交互本端决定采用 CS承载的媒体流, 实现 了 CSI业务。
当会话结束需要释放本次 CSI业务连接时, 本发明还包括释放所建 立的 CS连接,其具体处理过程为:控制发起 CS承载建立的所述 IMS TM 在会话结束时指示 CS TM释放所建立的 CS承载, CS TM按照标准的 CS流程发起 CS呼叫释放请求, CS呼叫控制实体与互通网关接收到 CS 呼叫释放请求后, 完成对所建立的 CS承载的 #放过程, 并且, 互通网 关接收到 CS呼叫释放请求后由 MGCF完成与 IMS TM之间的 IMS域回 呼的幹放,这样便完成了整个 CS承载及建立该承载所涉及的 CS到 IMS 互通呼叫的释放处理。
上述释放连接的处理过程是在正常情况下, 即会话结束时, 释放连 接的过程。 在具体的业务实现中, 在 CS承载以及 IMS域的连接均建立 后并实现 CSI业务的过程中, 由于网络环境的***, 经常会出现所 建立的 CS承载异常释放的情况, 在此种情况下, 本发明在 CS TM和 CS域网元间按 CS域标准流程完成呼叫释放, 互通网关 MGCF释放到 IMS TM的 IMS域回呼, IMS TM完成该 IMS回呼的会话释放, 并在与 对端的会话中通过重协商过程与对端协商业务回落或媒体流改向。 参见 图 5, 当 CS承载异常释放时, 本发明的处理过程具体包括以下步骤: 步驟 501: CS TM与 CS呼叫控制实体间按 CS域标准流程完成 CS 域呼叫释放过程, 并且 CS呼叫控制实体与 CS域与 IMS域互通网关 MGCF/IM-MGW间按 CS域标准流程完成 CS域转接呼叫释放过程。 步骤 502: CS域与 IMS域互通网关 MGCF与 IMS TM之间完成释 放 IMS域回呼的处理。
步驟 503: IMS TM通知对端暂停在本端原来通过 CS承载传递的媒 体流的发送。
步驟 504: IMS TM与对端通过重协商过程建立相应的 PS承载用于 传输原来通过 CS承载传递的媒体流, 并通知对端将媒体流改向传递到 本步驟中所建立的 PS承载端口。
步驟 505: IMS TM通知对端恢复媒体流的发送。
步骤 506: IMS TM与对端利用所建立的 PS承载对原来利用 CS承 载传输的媒体流进行传输交互。
至此, 则完成了针对 CS承载异常释放情况的处理。 通过上述图 5 所示的过程, 在实现 CSI业务的过程中, 即使 CS承载异常释放, 本发 明仍然能够保证 CSI终端继续进行通信。
需要说明的是, 上述图 5所示的在实现 CSI业务过程中针对 CS承 载异常释放的处理过程, 可以适用于任何模式下实现的 CSI业务, 比如 终端到网关 /网络控制模式, 其中的步骤 503 ~ 506还适用于终端到终端 模式, 也就是说, 图 5所示过程可以是在图 4所示的终端到网关 /终端控 制模式下实现 CSI业务过程中对于 CS承载异常释放的处理过程, 也可 以是在其它模式, 比如终端到网关 /网络控制模式下, 实现 CSI业务过程 中对于 CS承载异常释放的处理过程。
需要说明的是, 在上述实现 CSI业务的过程中 , CS域与 IMS域互 通网关在发送的 CSI回呼的 IMS会话建立请求的会话描述协议指示中还 可进一步携带专用指示信息, 其中, 所述的专用指示信息是通过对所述 IMS会话建立请求的会话描述协议进行扩展定义来实现的; 这样, 在后 续过程中, IMS域代理呼叫与会话控制功能实体在将 IMS会话建立请求 发送至 IMS TM时, 还可以根据所述的专用指示信息确定该部分媒体流 将经由 CS承载, 从而进行特殊的资源预留处理, 即不进行该部分的资
Figure imgf000030_0001
但是,在实际应用中, 特别是在 IMS TM和 CS TM设置在不同终端 中时,存在 IMS TM不支持 3GPP要求的 SIP协议扩展{如 IETF RFC 3312 所定义的 Precondition预置条件,综合资源管理和 SIP ), IETF RFC 3311 所定义的 UPDATE (更新 )方法以及 IETF RFC 3262所定义的 100 Rel ( SIP临时响应的可靠传递) } 的情况, 相应地也就存在不支持相关 SIP 扩展的 IMS TM接入的情况,即非标准终端接入的情况,针对此种情况, 在本发明中, CS域与 IMS域互通网关 MGCF釆用端到端 ( E2E )方式 完成 3GPP SIP和 non-3GPP SIP的流程协商; CS域与 IMS域互通网关 MGCF也可在 IMS会话发起前通过 SIP相关操作与 IMS TM进行能力查 询协商, 并根据协商结果在发起到 IMS TM的会话建立过程时决定是否 采用所述的 SIP扩展。图 6是在本发明中 CSI终端中 IMS终端模块不支 持 SIP协议扩展时的处理流程图。 参见图 4和图 6 , 为了避免 IMS TM 不支持 SIP协议扩展而对后续会话所造成的影响, 在上述图 4所示的步 骤 408至步驟 409的过程中, 进一步包括如下步骤的处理过程: 会话建立请求时, CS域与 IMS域互通网关 MGCF通过该 IMS会话建立 请求要求所述 IMS TM支持 SIP协议扩展(如 Precondition等)。
步骤 602: 所述的 IMS TM接收到 IMS会话建立请求后, 向 CS域 与 IMS域互通网关 MGCF返回会话建立失败消息, 并在该会话建立失 败消息中携带失败原因值为不支持 SIP协议扩展。
上述步驟 601至步骤 602的过程也可以为: CS域与 IMS域互通网 关 MGCF向 IMS TM发起 IMS能力查询请求, 以获知 IMS TM是否支 持 SIP协议扩展; IMS TM向 CS域与 IMS域互通网关 MGCF返回不支 持 SIP.协议扩展 (如 Precondition ) 的信息。
步骤 603: CS域与 IMS域互通网关 MGCF向所述的 IMS TM发起 IMS会话建立请求, 在本次发送的 IMS会话建立请求中不再要求 IMS TM支持其所不能支持的 SIP协议扩展。
步骤 604: 所述 IMS TM接收到 CS域与 IMS域互通网关 MGCF发 来的不要求其支持所不能支持的 SIP协议扩展的 IMS会话建立请求后, 向 CS域与 IMS域互通网关 MGCF返回会话建立成功消息。
通过上述图 6所示过程, CS域与 IMS域互通网关 MGCF获知 IMS TM不支持 SIP协议扩展 Precondition, 也就是说无法在与 CS域与 IMS 域互通网关 MGCF的 IMS会话建立过程中正确通知 CS域与 IMS域互 好了相关的承载资源, 因此在步骤上述 603和 604中建立的会话将交互 的媒体流描述为未激活状态, 以避免任何一方提前发送无效媒体流。
步骤 605:对端在完成所需承载资源的准备后通知 IMS TM, IMS TM 直接发起或将对端的通知转发给 CS域与 IMS域互通网关 MGCF。
步骤 606: CS域与 IMS域互通网关 MGCF向 IMS TM发起重协商 过程, 将媒体流描述修改为激活, CSI终端包括 IMS TM和 CS TM与对 端进行 CSI业务的媒体流传输。
在本发明中, 还可以预先在 CS域的各个处理节点中设置 CS TM和 IMS TM分别对应的 E.164号码之间的对应关系, 在上述图 4所示的过 程中, CS域的各个处理节点在接收到 CS TM发来的呼叫建立请求后, 由于该呼叫建立请求的主叫号码为 CS TM对应的 E.164号码,且被叫号 码为 IMS TM对应的 E.164号码, 则可根据该呼叫建立请求中主、 被叫 号码之间存在预先设置的对应关系,来判断该次呼叫为 IMS会话使用的 CS承载。 比如, 其中主叫号码为一个签约用户的 MSISDN号码, 被叫 等, 这样, CS域的各个处理节点则可以进行针对本次 CSI业务的关联 计费处理, 比如, 可以将对本次呼叫应用的 CS承载的计费免除或附加 在 IMS业务中进行计费。
另外, 在上述图 4所示步驟 406中, 由于 CS TM采用在 CS域签约 的 MSISDN发起 CS承载的呼叫建立请求, 因此,还需要考虑 CS TM侧 补充业务的影响, 其中对 CSI业务有影响的主要有呼出闭锁 {包括呼出 闭锁补充业务(BO )和运营商决定的呼出闭锁 (ODB ) }、 闭合用户群 ( CUG )和 GSM.的移动智能业务( CAMEL ), 因为这些业务将可能限 制所述 CS承载呼叫的建立或者在所述 CS承载呼叫过程中触发智能业务 从而引入智能业务的控制和影响(如改号等)。 因此, 为避免 CS域主叫 侧补充业务和智能业务的影响, 本发明的处理方法为: 预先为 IMS TM 对应的 E.164号码分配特殊前缀, 如代表业务类型的前缀, 并通过在 CS 域呼叫控制实体中配置针对该特殊前缀的分析数据的方式, 避免 CS主 叫侧补充业务及智能业务对 CSI业务 CS承载建立过程产生影响,这样, 在上述图 4所示过程中, CS TM所获取并在 CS域发送的 IMS TM的 E.164号码中进一步包括所分配的特殊前缀, CS域呼叫控制实体接收到 携带该特殊前缀的 IMS TM的 E.164号码后, 根据所配置的针对该特殊 前缀的分析数据分析,则在该 CS TM的本次呼叫过程中禁止补充业务调 用及智能业务触发, 从而避免 CS主叫侧补充业务及智能业务对 CSI业 务 CS承载建立过程产生影响。 当然, CS域呼叫控制实体也可以根据所 配置的针对该特殊前缀的分析数据分析, 进行针对本次 CSI业务的关联 计费处理, 比如, 可以将对本次呼叫应用的 CS承载的计费免除或附加 在 IMS业务中进行计费。
在上述过程中, 在满足实现 CSI业务条件的情况下, 即 CSI终端所 接入的小区具备同时保持与 CS和 PS空口连接的能力时,本发明提出了 一种符合 3GPP TS 23.899标准要求的 CSI业务的具体实现方案,从而保 证了 CSI终端能够实现 CSI业务。 另外, 在上述保证 CSI终端实现 CSI 业务的过程中, 本发明进一步提出了在 CSI终端漫游情况下避免路由迂 回的解决方法、在 CS承载异常幹放情况下的解决方法、 CSI终端中 IMS 终端模块不能支持 3GPP标准要求的 SIP协议扩展时的解决方法、 CS域 和 IMS域关联计费的解决方法、以及避免 CS 域主叫侧补充业务及智能 业务影响的解决方法, 从而提供了一种极为完整和丰富的 CSI业务实现 方案。
由于上述实现 CSI业务的过程必须是基于 CSI终端所接入的小区具 备同时保持与 CS和 PS空口连接的能力, 并进一步基于用户意愿的, 因 此, 当不满足实现 CSI业务条件, 即 CSI终端所接入的小区无法同时保 持与 CS和 PS的空口连接或用户意愿为不进行 CSI业务时,如果仍需保 证 CSI终端与对端用户的通信,则必须考虑将 CSI会话回落为 CS呼叫。 因此, 在上述图 4所示实现 CSI业务过程的步驟 402中, 如果作为被叫 的 CSI终端接收到对端发来的 IMS域会话建立请求后判断出应触发 CSI 业务, 但在步骤 403中判断出当前不满足实现 CSI业务条件时, 本发明 进一步提出了将 CSI业务回落到 CS呼叫的方法, 包括两种实现方式: 方式一、由 CSI终端向对端发送呼叫改向指示并由对端重新发起 IMS会 话并经过 CS域与 IMS域互通网关转换为 CS呼叫接续到 CSI终端来实 现; 方式二、 CSI终端采用以特定原因幹放请求建立的 IMS会话, 进而 主动在 CS域发起向对端的 CS到 IMS互通呼叫的方式来实现。
图 7是在本发明中实现将 CSI会话回落到 CS呼叫的方式一的流程 图。 参见图 7, 针对上述方式一, 当作为被叫的 CSI终端接收到对端发 来的 IMS域会话建立请求后判断出应触发 CSI业务,但进一步判断出当 前不满足实现 CSI业务条件时, 本发明实现将 CSI业务回落到 CS呼叫 的过程具体包括以下步驟:
步驟 701 : CSI终端中的 IMS TM向对端返回 IMS会话改向指示, 并在该 IMS会话改向指示中携带 CSI终端中的 CS TM在 CS呼叫寻址 使用的 E.164号码
这里, 所述 CSI终端中的 CS TM在 CS呼叫寻址使用的 E.164号码 具有指示对端所涉及 IMS网络将呼叫转到 CS接续的能力, 该 E.164号 码可以是 CSI终端在 CS签约的 MSISDN, 也可以由该 MSISDN添加特 定前缀或特殊标识构成。
步骤 702: 对端接收到 IMS会话改向指示后, 返回呼叫改向确认, IMS TM与对端释放本次请求建立的 IMS会话。
步骤 703: 对端发起新的 IMS会话建立请求, 并将 IMS会话改向指 示中携带的 E.164号码, 即 CSI终端在 CS呼叫寻址使用的 E.164号码, 作为该新的 IMS会话建立请求的被叫号码。
步骤 704:对端所涉及的 IMS网络根据对该新的 IMS会话建立请求 的被叫号码, 即 CSI终端在 CS呼叫寻址使用的 E.164号码, 进行的分 析结果, 决定将该新的会话建立请求转往 CS接续并选择 CS域与 IMS 域互通网关, 然后将该新的会话建立请求消息转发到所选择的 CS域与 IMS域互通网关。
步骤 705: 所述 CS域与 IMS域互通网关接收到该新的会话建立请 求后, 执行 IMS/CS互通处理, 按 CS标准处理流程完成 CS路由分析, 经过 CS网络将 CS呼叫建立请求发送至 CS TM,并且,该 CS域与 IMS 域互通网关与对端通过该对端所涉及的 IMS网络完成 IMS会话部分的 SDP协商。
需要说明的是,在上述步驟 601中,如果 CSI终端返回给对端的 E.164 号码是由该 CSI终端的 MSISDN号码添加特定前缀或特殊标识构成的 , 也就是说, 在上述步骤 703和步驟 704中所传送的新的会话建立请求的 被叫号码是由 CS TM的. MSISDN号码添加特定前缀或特殊标识构成的, 则在本步骤中, 所述 CS域与 IMS域互通网关首先从被叫号码中扣除所 添加的特定前缀或特殊标识,并釆用扣除后所剩余的 MSISDN作为被叫 号码完成与 CS网络的所述交互处理。 并且, 所述 CS域与 IMS域互通 网关在扣除所添加的特定前缀或特殊标识时, 还可根据该所添加的特定 前缀或特殊标识确定出本次呼叫为 CSI业务相关回落呼叫, 从而在 CS 呼叫控制信令中添加特殊指示,使得 CS网络和 /或 CS TM可以根据该特 殊指示进行 CSI业务相关回落呼叫的特殊处理。 比如,
CS网络根据所述 CS域与 IMS域互通网关添加的特殊指示,可以但 不限于进行如下的特殊处理:
1、特殊的计费处理: 如 CS网络根据该特殊指示减免部分 CS话费;
2、 业务冲突处理: 如 CS网络根据该特殊指示规避部分 CS域补充 业务, 如前转、 呼叫闭锁以及智能触发等。
CS TM根据所述 CS域与 IMS域互通网关添加的特殊指示, 可以但 不限于进行如下特殊处理:
1、识别本次呼叫为 CSI业务相关回落呼叫, 从而通过弹出菜单、 特 殊铃音等方式提示用户当前呼叫为 CSI业务相关回落呼叫;
2、识别本次呼叫为 CSI业务相关回落呼叫并提示给用户,继而在用 户控制下进行启用呼叫偏转等处理。
步骤 706: CS TM接到 CS呼叫建立请求后, 与对应 CS网络交互完 成 CS呼叫建立处理, 并向所述 CS域与 IMS域互通网关依次返回 CS 用户振铃和 CS用户应答消息,建立 CS TM与 CS域与 IMS域互通网关 间的 CS呼叫。
步骤 707: 所述 CS域与 IMS域互通网关执行 IMS/CS互通处理,将 上述过程映射为 IMS会话建立相应过程, 经过对端所涉及 IMS网络向 对端先后返回 IMS用户振铃和 IMS用户应答, 对端返回 IMS应答确认 后与 CS域与 IMS域互通网关间建立 IMS会话。
图 8是在本发明中实现将 CSI会话回落到 CS呼叫的方式二的流程 图。 参见图 8, 针对上述方式二, 当作为被叫的 CSI终端接收到对端发 来的 IMS域会话建立请求后判断出应触发 CSI业务,但进一步判断出当 前不满足实现 CSI业务条件时, 本发明实现将 CSI业务回落到 CS呼叫 的过程具体包括以下步骤:
步骤 801 : CSI终端中的 IMS TM向对端回应 IMS会话释放指示。 这里, IMS TM可以在所回应的 IMS会话释放指示中携带 CSI业务 指示及 CSI终端中的 CS TM在 CS使用的号码, 即其 MSISDN。使得对 端终端后续接到 CSI终端发起的回落呼叫时, 能够识别出该呼叫。
步骤 802: 对端接收到该 IMS会话释放指示后向 IMS TM回应呼叫 释放确认, IMS TM与对端释放本次请求建立的 IMS会话。
这里,如果在步驟 801中 IMS TM在所回应的 IMS会话幹放指示中 携带了 CS TM的 MSISDN号码, 则在本步骤中, 对端从 IMS会话释放 指示中获取 CS TM的 MSISDN号码。
步骤 803: CS TM在 CS向对端发起呼叫建立请求, 该呼叫建立请 求中的被叫号码为对端的 E.164号码。
这里, 被叫号码即对端的 R164号码具有指示 CSI终端所涉及 CS 网络将呼叫转到 IMS 接续的能力, 具体可以是对端在 CS 签约的 MSISDN, 也可以由该 MSISDN添加特定前缀构成。 需要说明的是, 呼叫建立请求中的被叫号码即对端的 E.164号码是 由 CSI终端根据对端发来的 IMS会话建立请求而获得的, 也就是, 在上 述图 4所示步骤 402中,当 CSI终端作为被叫接收到对端发来的 IMS会 话建立请求时, CSI终端从该 IMS会话建立请求中 From头域中获取对 端的 IMS标识, 然后根据所获取的 IMS标识推导出 (依赖于特定的网 络编号方案)对端的 E.164号码, 或根据所获取的 IMS标识及号码簿信 息获得对端的 E.164号码, 或者由对端直接在 IMS会话建立请求中携带 过来。
另夕卜,在本步骤中, CSI终端还可在自己随后在 CS发起的呼叫建立 请求中进一步携带回落指示,以便在后续过程中, CS网络或 CS域与 IMS 域互通网关可以根据该回落指示进行 CSI 业务相关回落呼叫的特殊处 理。
步骤 804: CSI终端所涉及 CS网络接收到呼叫建立请求后, 根据对 该呼叫建立请求的被叫号码分析结果将呼叫路由到 CS域与 IMS域互通 网关。
这里,如果在步驟 803中, CSI终端在 CS发起的呼叫建立请求釆取 了在对端的 MSISDN号码前添加特定前缀构成被叫号码或直接在 CS呼 叫建立请求中携带回落指示的方法, 则 CSI终端相关 CS网絡根据呼叫 建立请求中对端的 MSISDN号码前所添加的特定前缀或呼叫建立请求 消息中携带的回落指示, 可以进行但不限于如下特殊处理:
( 1 )特殊的计费处理: 如根据该指示减免部分 CS话费;
( 2 )业务冲突处理:如根据该指示规避部分 CS域主叫侧补充业务, 如呼叫闭锁、 闭合用户群以及智能触发等, 可以依据 CS现有紧急呼叫 或特服呼叫规避上述业务处理的机制处理。
步骤 805: CS域与 IMS域互通网关进行 IMS与 CS互通处理,将 IMS 会话建立请求发送至对端。
这里, 在步骤 803中, 如果 CSI终端在 CS发起的呼叫建立请求中 采取了在对端的 MSISDN号码前添加前缀构成被叫号码或直接在呼叫 建立请求中携带回落指示的方法, 则在本步骤 805中, CS域与 IMS域 互通网关可以进行但不限于在所映射并发送至对端的 IMS会话建立请 求中添加回落指示的处理。
步骤 806: 对端接到 IMS会话建立请求后, 通过其所涉及 IMS网络 与 CS域与 IMS域互通网关交互完成 IMS会话建立处理,向 CS域与 IMS 域互通网关先后返回 IMS用户振铃、 IMS用户应答消息。
这里,如果在上述步骤 801中 CSI终端在 IMS会话释放指示中携带 了自身的 MSISDN, 而且, 在步驟 802 中, 对端获取了 CSI 终端的 MSISDN, 则在本步骤中, 对端判断出所接收到的 IMS会话建立请求消 息中 From头域内的 MSISDN与在步驟 802中所获取的 MSISDN号码相 同时, 进行特殊处理; 或, 在上述步骤 805中, 如果 IMS/CS网关进行 了在 IMS会话建立请求中携带回落指示的处理,则在本步骤中对端进行 特殊处理。 所述的特殊处理包括但不限于以下的处理:
( 1 )识别该次呼叫为 CSI业务回落回呼, 从而通过弹出莱单、 特殊 铃音等方式提示给用户;
( 2 )识别该次呼叫为 CSI业务回落回呼,从而在会话建立过程中免 除振铃过程。
步骤 807: CS域与 IMS域互通网关向对端返回 IMS应答确认后建 立对端与 CS域与 IMS域互通网关间的 IMS会话, CS域与 IMS域互通 网关执行 IMS与 CS互通处理, 将上述过程映射为 CS会话建立相应过 程, 经过 CSI终端所涉及 CS网络向 CSI终端中的 CS TM先后返回 CS 用户振铃和 CS用户应答, 与 CSI终端中的 CS TM建立 CS呼叫连接。 至此,则完成了将 CSI终端接收到的需要应用 CSI业务的 IMS会话 回落为 CS呼叫的过程, CSI终端则可在无法实现 CSI业务时, 仍然能 够与对端进行通信。
总之, 以上所述仅为本发明的较佳实施例而已, 并非用于限定本发 明的保护范围。 凡在本发明的精神和原则之内, 所作的任何修改、 等同 替换、 改进等, 均应包含在本发明的保护范围之内。

Claims

权利要求书
1、 一种实现通信的方法, 其特征在于, 该方法包括:
A、 综合业务 CSI终端中的 IMS终端模块 IMS TM指示 CSI终端中 的 CS终端模块 CS TM发起 CS承载建立;
B、 CS TM将 IMS TM作为被叫向 CS域呼叫控制实体发送呼叫建 立请求;
C、 CS域呼叫控制实体根据接收到的呼叫建立请求中被叫号码信息 将呼叫建立请求路由到 CS域与 IMS域互通网关;
D、 CS域与 IMS域互通网关将接收到的呼叫建立请求转化为 IMS 会话建立请求后发送至 IMS TM;
E、 IMS TM进行与 CS域与 IMS域互通网关以及与对端间两段会话 间的关联控制, 实现 CSI业务。
2、 根据权利要求 1所述的方法, 其特征在于, 在步驟 A之前, 该 方法进一步包括: IMS TM判断 IMS业务所需交互的媒体流中是否包含 有需要通过 CS承载传输的媒体流, 如果是, 则执行步骤 A。
3、根据权利要求 2所述的方法, 其特征在于, 所述 IMS TM在准备 发起 IMS会话建立请求、接收到对端发来的 IMS会话建立请求、在 IMS 会话过程中准备发起重协商请求或者接收到对端发来的重协商请求时, 执行所述判断的步骤。
4、 根据权利要求 1、 2或 3所述的方法, 其特征在于, 在步骤 A之 前, 该方法进一步包括: IMS TM判断当前是否满足实现 CSI业务的条 件, 如果是, 则执行步骤 A。
5、根据权利要求 4所述的方法, 其特征在于, 所述 IMS TM判断当 前是否满足实现 CSI业务条件的步骤包括: IMS TM判断自身所接入的 小区是否具备同时保持 CS和 PS空口连接的能力, 如果是, 则判断当前 满足实现 CSI业务的条件。
6、根据权利要求 5所述的方法, 其特征在于, 所述 IMS TM在判断 出自身所接入的小区具备同时保持 CS和 PS空口连接的能力之后,并在 判断当前满足实现 CSI业务的条件之前, 进一步包括: IMS TM判断所 确认的用户意愿是否为进行 CSI业务, 如果是, 则判断当前满足实现 CSI业务的条件。
7、根据权利要求 6所述的方法, 其特征在于, 所述 IMS TM确认用 户意愿的方式包括: IMS TM通过提供特定用户界面并接收用户输入的 业务实现方式确定用户意愿, 或, IMS TM 4 据用户预先所设置的业务 实现方式确定。
8、 ^居权利要求 1所述的方法, 其特征在于, 所述步驟 A进一步 包括: IMS TM将本次会话所要求的承载能力指示信息提供给 CS TM; 所述呼叫建立请求中携带 IMS TM所提供的承载能力指示信息; 在发送 IMS会话建立请求之前, 所述步骤 D进一步包括: CS域与
IMS域互通网关根据呼叫建立请求中携带的承载能力指示信息预留包括
IP地址和 UDP端口的 IP端口资源;
在步骤 D中,所述 CS域与 IMS域互通网关将 IMS会话建立请求发 . 送至 IMS TM的步骤包括: 所述 CS域与 IMS域互通网关将所预留的 IP 端口资源的 IP地址和 UDP端口信息携带在 IMS会话建立请求中发送至
IMS TM;
所述步骤 E包括: IMS TM以背靠背 SIP用户代理 B2BUA模式关 述以 B2BUA模式关联处理包括:
IMS TM从接收到的 IMS会话建立请求中获取会话描述协议指示, 将所获取的会话描述协议指示作为自身对应的 IMS会话中申请采用 CS 承载的媒体流的本端描述指示, 处理与对端间的 IMS域会话建立过程; 并且, IMS终端模块利用与对端之间 IMS会话建立过程中得到的关于申 请采用 CS承载的媒体流的对端的会话描述协议指示, 作为本侧会话描 述协议指示,处理与 CS域与 IMS域互通网关间的 IMS域会话建立过程, 建立自身与对端间的 IMS会话连接以及自身经过 CS域与 IMS域互通网 关至 CS TM的 IMS与 CS互通呼叫连接,并由此使得 CS域与 IMS域互 通网关与对端间利用所预留的 IP端口资源交互 CSI终端与对端间 IMS 会话中申请采用 CS承载的媒体流, 该采用 CS承载的媒体流进而通过 CS域与 IMS域互通网关与 CS TM间建立的 CS承载传输到 CSI终端。
9、根据权利要求 1或 8所述的方法, 其特征在于, 该方法进一步包 括: 预先为 CS TM分配该 CS TM在 CS域签约的移动台国际 ISDN
( MSISDN )号码;
在步骤 A中, 进一步包括: IMS TM获取 CS TM的 MSISDN号码; 所述步驟 D进一步包括: CS域与 IMS域互通网关根据呼叫建立请 求中的主叫号码获取 CS TM的 MSISDN号码, 并在向 IMS TM发送的 IMS会话建立请求 From头域中携带所获取的 CS TM的 MSISDN号码; 在步骤 E中, 在 IMS TM执行所述关联处理之前进一步包括: IMS TM从接收到的 IMS会话建立请求 From头域中获取 CS TM的 MSISDN 号码 , 判断当前所获取的 CS TM的 MSISDN号码与在步驟 A中获取的 CS TM的 MSISDN号码是否相同, 如果是, 则继续执行所述的关联处 理的步骤。
10、 根据权利要求 9所述的方法, 其特征在于, 当所述 IMS TM与 CS TM设置在不同终端内时,在步骤 A中,所述 IMS TM通过与 CS TM 所进行的实时交互或预先交互的过程获取所述 CS TM的 MSISDN, 其 中,
所述通过实时交互获取包括: IMS TM首先通过自身与 CS TM之间 的接口向 CS TM发起请求, CS TM接收到该请求之后, 将自身的 MSISDN发送至 IMS TM, IMS TM获取该 CS TM的 MSISDN;
所述通过预先交互获取包括:在 IMS TM和 CS TM启动时, IMS TM 向 CS TM发起请求, CS TM接收到该请求之后, 将自身的 MSISDN发 送至 IMS TM, IMS TM将接收到的 MSISDN保存在自身的緩存中, 并 在当前从自身緩存中获取所保存的 CS TM的 MSISDN;
当 IMS TM与 CS TM集成在同一终端中,且采用共享数据区域存储 CS TM的 MSISDN号码时, 在步骤 A中, 所述获取包括: IMS TM从 共享数据区域中获取 CS TM的 MSISDN。
11、根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: 预先为 IMS TM分配 E.164号码,并在 CS域呼叫控制实体为该 IMS TM 的 E.164号码配置被叫分析数据;
在步驟 A中, IMS TM在指示 CS TM发起所述 CS承载建立时提供 为 IMS TM分配的 E.164号码;
所述步骤 A进一步包括: A0、 CS TM获取 IMS TM的 E.164号码; 所述步骤 B包括: CS TM将获取的 IMS TM的 E.164号码作为被叫 号码携带在呼叫建立请求中发送至 CS域呼叫控制实体;
在步骤 C中, CS域呼叫控制实体根据作为被叫号码的 IMS TM的 E.164号码及所配置的被叫分析数据将所述的呼叫建立请求路由到 CS域 与 IMS域互通网关。
12、 根据权利要求 11所述的方法, 其特征在于, 所述 IMS TM与 CS TM设置在不同终端内;
所述步驟 A包括: IMS TM将携带自身 E.164号码的 CS承载建立 请求发送至 CS TM;
所述步骤 AO包括: CS TM从 CS承载建立请求中获取 IMS TM的 E.164号码。
13、 根据权利要求 11所述的方法, 其特征在于, 所述 IMS TM与 CS TM终端集成在同一终端内;
所述步骤 A包括: IMS TM通过内部指令指示 CS TM发起 CS承载 建立;
所述步骤 AO包括: CS TM从内部指令或与 IMS TM的共享数据区 域中获取 IMS TM的 E.164号码。
14、 根据权利要求 11所述的方法, 其特征在于, 所述 IMS TM的 E.164号码中包括区域识别前缀或业务类型前缀;
在步骤 C中, 所述 CS域呼叫控制实体进一步根据对 IMS TM的 E.164 号码中的区域识别前缀或业务类型前缀的分析将呼叫建立请求发 送至 IMS TM归属区域的 CS域与 IMS域互通网关处或较近的 CS域与 IMS域互通网关处。
15、根据权利要求 11所述的方法,其特征在于,该方法进一步包括: 预先设置 IMS TM的 E.164号码与其初始会话协议统一资源定位符 SIP URI对应关系的转换数据;
在将 IMS会话建立请求发送至 IMS TM之前,所述步骤 D进一步包 括; 所述 CS域与 IMS域互通网关根据呼叫建立请求中携带的作为被叫 号码的 IMS TM的 E.164号码, 进行电话号码映射 ( ENUM )服务器查 询, 通过所设置的转换数据获取 IMS TM的初始会话协议统一资源定位 符 SIP URI;
在步骤 D中, 所述 CS域与 IMS域互通网关根据所获取的 IMS TM 的初始会话协议统一资源定位符 SIP URI将呼叫建立请求转化为 IMS会 话建立请求后发送至 IMS TM。
16、 根据权利要求 15所述的方法, 其特征在于, 在步驟 D中, 所 述 CS域与 IMS域互通网关进行 ENUM服务器查询的步骤进一步包括: CS域与 IMS域互通网关根据查询结果判断呼叫建立请求中的 IMS TM 的 E.164号码是否存在对应的转换数据, 如果是, 则确定当前 CSI业务 合法, 继续执行通过对应转换数据获取 IMS TM的初始会话协议统一资 源定位符 SIP URI的步骤, 否则, 结束当前流程。
17、 根据权利要求 1所述的方法, 其特征在于, 所述步骤 A进一步 包括: 所述 IMS TM将自身的初始会话协议统一资源定位符 SIP URI地 址提供给 CS TM;
所述步骤 B进一步包括: CS TM将携带 SIP URI地址的用户到用户 信息信元发送至 CS域呼叫控制实体;
所述步骤 C进一步包括: CS域呼叫控制实体将携带 SIP URI地址的 用户到用户信息信元发送至所述 CS域与 IMS域互通网关;
所述步骤 D包括: 所述 CS域与 IMS域互通网关通过用户到用户信 息信元获取 SIP URI地址, 并根据所获取的 SIP URI将会话建立请求转 化为 IMS会话建立请求后发送至 IMS TM。
18、 根据权利要求 1 所述的方法, 其特征在于, 在步驟 D 中, CS 域与 IMS域互通网关在发送的 IMS会话建立请求的会话描述协议指示 中进一步携带专用指示信息,其中,所述的专用指示信息通过对所述 IMS 会话建立请求的会话描述协议进行扩展定义实现;
所述步骤 D进一步包括: IMS域代理呼叫与会话控制功能实体在将 IMS会话建立请求发送至 IMS TM时, 根据所述的专用指示信息识别经 由 CS承载的媒体流并进行特殊的资源预留处理。
19、 根据权利要求 1所述的方法, 其特征在于, 在步骤 E之后, 该 方法进一步包括: 在会话结束时, 所述 IMS TM指示 CS TM释放所建 立的 CS承载, CS TM按照标准的 CS流程发起呼叫释放请求, CS呼叫 控制实体与互通网关接收到 CS承载释放请求后, 完成对所建立的 CS 承载的释放过程,并且,互通网关接收到 CS承载释放请求后完成与 IMS TM之间的 IMS域回呼的释放。 .
20、 根据权利要求 1所述的方法, 其特征在于, 所述 IMS TM不支 持初始会话协议扩展;
所述步骤 D进一步包括: Dl、 CS域与 IMS域互通网关通过与 IMS TM 间端到端协商过程完成与不支持初始会话协议扩展的终端间互通的 IMS域回呼的建立。
21、 根据权利要求 20所述的方法, 其特征在于, 在步骤 D1中, CS 域与 IMS域互通网关通过预先查询 IMS TM能力,采用不要求支持初始 会话协议扩展的方式完成 IMS域回呼的建立;或 CS域与 IMS域互通网 关接收到 IMS TM返回的不支持初始会话协议扩展的指示后重新发起不 要求支持初始会话协议扩展的 IMS会话建立请求, 并进而完成 IMS域 回呼的建立。
22、根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: 预先在 CS域的各个处理节点中设置 CS TM和 IMS TM分别对应的 E.164 号码之间的对应关系;
所述步骤 C进一步包括: CS域各个处理节点在发送所述呼叫建立 请求时,判断该呼叫建立请求中主被叫号码所对应的 CS TM的 E.164号 码与 IMS TM对应的 E.164号码之间是否存在预先设置的对应关系, 如 果存在, 则进行与所述 IMS会话的关联计费处理。
23、根据权利要求 1所述的方法, 其特征在于, 该方法进一步包括: 预先为 IMS TM对应的 E.164号码分配特殊前缀, 并在 CS域呼叫控制 实体配置针对该特殊前綴的分析数据 ,通过对该特殊前缀的分析避免 CS 主叫侧补充业务及智能业务对 CSI业务 CS承载建立过程产生影响; 所述 IMS TM的 E.164号码中进一步包括所分配的特殊前缀; 所述步骤 C进一步包括: CS域呼叫控制实体接收到携带该特殊前 缀的 IMS TM的 E.164号码后, 根据针对该特殊前缀的配置数据, 在本 次呼叫中禁止影响 CSI业务 CS承载建立过程的 CS主叫侧补充业务的 调用及智能业务的触发。
24、 根据权利要求 5或 6所述的方法, 其特征在于, 所述 IMS TM 作为被叫接收到对端发来的 IMS会话建立请求;
在判断出当前不满足实现 CSI业务的条件之后,该方法进一步包括:
Gll、 IMS TM向对端发送 IMS会话改向指示, 并在该 IMS会话改 向指示中携带 CS TM在 CS域的寻址号码;
G12、对端接收到 IMS会话改向指示后,释放请求建立的 IMS会话, 并将 IMS会话改向指示中携带的寻址号码作为被叫号码向 CS TM发起 IMS域的会话请求;
G13、 对端所涉及的 IMS网络根据对端所发送的会话请求中的被叫 号码, 将该会话建立发送至 CS域与 IMS域互通网关;
G14、 CS域与 IMS域互通网关将接收到的 IMS会话请求映射为 CS 呼叫, 通过 CS网絡将 CS呼叫发送至 CS TM;
G15、 CS TM通过 CS网络与 CS域与 IMS域互通网关建立 CS呼叫 连接, CS域与 IMS域互通网关与对端建立 IMS会话连接。
25、 根据权利要求 24 所述的方法, 其特征在于, 所述寻址号码为 CS TM在 CS签约的 MSISDN。
26、 根据权利要求 24 所述的方法, 其特征在于, 所述寻址号码为 CS TM在 CS签约的 MSISDN添加特定前缀或特殊标识构成; 所述步骤 G14进一步包括:所述 CS域与 IMS域互通网关扣除寻址 号码中所添加的特定前缀或特殊标识;
在步骤 G14中, 在 CS网络中所传送的寻址号码为 CS TM在 CS签 约的 MSISDN。
27、 根据权利要求 26所述的方法, 其特征在于, 所述步骤 G14进 一步包括: CS域与 IMS域互通网关在所发送的 CS呼叫中添加回落指 示, CS网络和 /或 CS TM根据接收到的 CS呼叫中所添加的回落指示进 行 CSI业务回落呼叫处理。
28、 根据权利要求 27所述的方法, 其特征在于, 当 CS网络进行所 述 CSI业务回落呼叫处理时, 该 CSI业务回落呼叫处理包括: 特殊的计 费处理和 /或业务冲突处理;
当 CS TM进行所述 CSI业务回落呼叫处理时, 该 CSI业务回落呼 叫处理包括: 提示用户当前呼叫为 CSI业务相关回落呼叫, 或, 提示用 户当前呼叫为 CSI业务相关回落呼叫, 并进一步在用户控制下启用呼叫 偏转处理。
29、 根据权利要求 5或 6所述的方法, 其特征在于, 所述 IMS TM 作为被叫接收到对端发来的 IMS会话建立请求;
在判断出当前不满足实现 CSI业务的条件之后,该方法进一步包括:
G21、 IMS TM向对端发送 IMS会话释放指示, 对端接收到 IMS会 话释放指示后, 释放请求建立的 IMS会话;
G22、 CS TM在 CS发起呼叫建立请求, 该呼叫建立请求中的被叫 号码为对端的 E.164号码;
G23、 CS网络接收到呼叫建立请求后, 根据对该呼叫建立请求的被 叫号码分析结果将呼叫路由到 IMS与 CS互通网关。
G24、IMS域与 CS域互通网关将接收到的呼叫建立请求映射为 IMS 会话请求, 通过对端所涉及的 IMS网络将该 IMS会话请求发送至对端; G25、 对端与 IMS域与 CS域互通网关建立 IMS会话连接, IMS域 与 CS域互通网关执行 IMS/CS互通处理与 CS TM建立 CS呼叫连接。
30、 根据权利要求 29所述的方法, 其特征在于,
在步驟 G21中, 所述 IMS TM发送至对端的 IMS会话释放指示中 携带 CS TM在 CS域的寻址号码; .
在步骤 G24与步骤 G25之间, 进一步包^: 对端接收到 IMS会话 建立请求后, 从该 IMS会话建立请求中获取 CS TM的号码, 并判断所 获取的号码与所接收到的 IMS会话 #放指示中携带的 CS TM的号码是 否相同, 如果是, 则进行 CSI业务回落呼叫处理。
31、 根据权利要求 30所述的方法, 其特征在于, 所述对端进行 CSI 业务回落处理的步骤包括: 提示对端用户当前呼叫为 CSI业务相关回落 呼叫, 并进一步在会话建立过程中免于振铃。
32、 根据权利要求 1所述的方法, 其特征在于, 当 CS承载异常释 放时, 所述步骤 E进一步包括: CS TM和 CS域呼叫控制实体之间以及 CS域呼叫控制实体和 CS域与 IMS域互通网关之间互通释放所建立的 CS承载; CS域与 IMS域互通网关释放与 IMS TM间的 IMS会话连接; IMS TM利用重协商过程建立分组交换 PS承载,并与对端利用所建立的 PS承载对原利用所释放 CS承载传输的对应媒体流进行交互。
33、 一种实现通信的方法, 应用于在 CSI业务的实现过程中 CS承 载异常释放的情况, 其特征在于, 该方法包括:
a、 CS TM和 CS域呼叫控制实体之间以及 CS域呼叫控制实体和 CS 域与 IMS域互通网关之间互通释放所建立的 CS承载;
b、 CS域与 IMS域互通网关释放与 IMS TM间的 IMS会话连接; c、 IMS TM利用重协商过程建立分组交换 PS承载, 并与对端利用 所建立的 PS承载对原利用所释放 CS承载传输的对应媒体流进行交互。
34、根据权利要求 33所述的方法, 其特征在于, 在步骤 c之前进一 步包括: IMS TM通知对端暂停通过 CS承载传递媒体流;
' 在步骤 c中, 在建立所述 PS承载之后, 并在利用所建立的 PS承载 进行传输之前, 进一步包括: IMS TM通知对端恢复对原通过 CS承载 的媒体流的发送。
35、根据权利要求 33或 34所述的方法, 其特征在于, 在步骤 c中, 所述 IMS TM利用重协商过程建立 PS承载与对端进行媒体交互的步骤 包括: IMS TM向对端发起更改交互媒体流的请求, 完成本侧 PS承载资 源的申请和建立, 并通知对端将原来交互到 CS域与 IMS域互通网关进 而利用 CS 7 载传递到 CSI终端的媒体流改向交互至 CSI终端 PS承载端 π。
36、 一种实现通信的***,.其特征在于, 该***包括:
CS域呼叫控制实体, 用于与 CS TM交互并建立 CS承载, 并将由 IMS TM控制、 CS TM发起建立的建立 CS承载的呼叫路由到 CS域与 IMS域互通网关上;
CS域与 IMS域互通网关, 用于将 CS域呼叫控制实体控制路由到 本端的 CS呼叫转换为 IMS会话建立请求,并将该 IMS会话建立请求经 IMS会话控制实体接续到控制发起建立 CS承载过程的 IMS TM, 从而 在 CS TM和 IMS TM间建立 CS到 IMS互通呼叫; 并且, CS域与 IMS 域互通网关将为 IMS域交互媒体流预留的 IP端口资源的 IP地址和端口 信息传递到 IMS TM, 并利用自身与 CS TM间建立的 CS承载将与对 通过 IP承载交互的媒体流与 CS TM间进行交互;
IMS TM, 用于实现 CS承载控制功能, 在 IMS业务中判断并控制 CS TM发起 CS承载的建立过程, 并在后续收到 CS域与 IMS域互通网 关转发的回呼后采用背靠背用户代理方式完成自身与 CS域与 IMS域互 通网关及与对端间两段 IMS会话的关联控制,令对端将其与本端用户间 IMS会话中交互的对应 CS承载的媒体流首先通过 CS域与 IMS域互通 网关预留的 IP端口传递到 CS域与 IMS域互通网关上, 进而经过 CS域 与 IMS域互通网关与 CS TM间建立的 CS承载传递到本侧终端; CS TM, 用于在接收到 IMS TM的指令后将 IMS TM作为被叫发起 CS承载的建 立请求, 并与 CS域呼叫控制实体进行交互完成 CS承载的建立过程。
37、 根据权利要求 36所述的***, 其特征在于, 所述 IMS TM与 所述 CS TM集成在同一终端内。
38、 根据权利要求 36所述的***, 其特征在于, 所述 IMS TM与 所述 CS TM设置在不同终端内 , 通过无线短距离通信方式进行连接;
39、根据权利要求 36、 37或 38所述的***, 其特征在于, 所述 CS 域呼叫控制实体, 进一步用于在接收到对端通过 CS域与 IMS域互通网 关发来的 CSI回落到 CS的呼叫建立请求后将该呼叫建立请求发送至 CS TM,或将 CS TM发来的 CSI回落到 CS的呼叫建立请求发送至 CS域与 IMS域互通网关;
CS域与 IMS域互通网关, 进一步用于在接收到对端发来的 CSI回 落到 CS的 IMS会话建立请求后, 将该 CSI回落到 CS的 IMS会话建立 请求转换为 CSI回落到 CS的呼叫建立请求后发送至 CS域呼叫控制实 体; 或者, 用于在接收到 CSI终端 CS TM经 CS域呼叫控制实体发来的 CSI回落到 CS的呼叫建立请求后将其转换为 CSI回落到 CS的 IMS会 话建立请求后发送至对端;
IMS TM, 进一步用于在确定无法满足实现 CSI业务条件时, 向对 端返回 IMS会话改向指示或 IMS会话释放指示,使对端与自身完成 IMS 会话释放;
CS TM, 进一步用于在接收到对端用户在 IMS发起并通过 CS域与 IMS域互通网关及 CS域呼叫控制实体发来的呼叫建立请求后,通过 CS 域呼叫控制实体及 CS域与 IMS域互通网关与对端建立 CSI回落到 CS 的 IMS到 CS互通呼叫连接; 或, 将对端作为被叫 , 通过 CS域呼叫控 制实体及 CS域与 IMS域互通网关主动与对端建立 CSI回落到 CS的 CS 到 IMS互通呼叫连接。
PCT/CN2005/001635 2004-09-30 2005-09-30 Procede et systeme de realisation de communication WO2006034658A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP05802141A EP1744569B1 (en) 2004-09-30 2005-09-30 Method and system of realizing communication
DE602005012817T DE602005012817D1 (de) 2004-09-30 2005-09-30 Verfahren system zur realisierung von kommunikation
US11/562,237 US8089956B2 (en) 2004-09-30 2006-11-21 Method and system for implementing communications

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CNB2004100848248A CN1297124C (zh) 2004-09-30 2004-09-30 Ip多媒体子***中利用电路交换承载业务的***及方法
CN200410084824.8 2004-09-30
CN200510002618.2 2005-01-24
CNB2005100026182A CN100352295C (zh) 2005-01-24 2005-01-24 Ip多媒体子***会话回落到电路交换呼叫的实现方法

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US11/562,237 Continuation US8089956B2 (en) 2004-09-30 2006-11-21 Method and system for implementing communications

Publications (1)

Publication Number Publication Date
WO2006034658A1 true WO2006034658A1 (fr) 2006-04-06

Family

ID=36118597

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2005/001635 WO2006034658A1 (fr) 2004-09-30 2005-09-30 Procede et systeme de realisation de communication

Country Status (5)

Country Link
US (1) US8089956B2 (zh)
EP (1) EP1744569B1 (zh)
AT (1) ATE423436T1 (zh)
DE (1) DE602005012817D1 (zh)
WO (1) WO2006034658A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070259651A1 (en) * 2006-04-26 2007-11-08 Samsung Electronics Co., Ltd. Method and system of forwarding capability information of user equipment in Internet Protocol Multimedia Subsystem network
DE102006028324A1 (de) * 2006-06-20 2007-12-27 Infineon Technologies Ag Nachrichtenerzeugungsanordnung und Verfahren zum Erzeugen einer Nachricht
EP1858222A3 (en) * 2006-04-26 2008-04-23 Huawei Technologies Co., Ltd. Method, apparatus and system for session adding
WO2008071213A1 (en) * 2006-12-14 2008-06-19 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatuses and computer program products for routing a call from a circuit switched domain to a unified service domain
WO2008095440A1 (fr) * 2007-02-08 2008-08-14 Huawei Technologies Co., Ltd. Procédé, système de communication et dispositif pour acquérir et fournir un numéro msisdn
EP2090069A1 (en) * 2006-11-03 2009-08-19 Telefonaktiebolaget LM Ericsson (PUBL) Accessing a communications network
CN101064683B (zh) * 2006-04-26 2011-04-20 华为技术有限公司 处理补充业务的方法、***及装置
CN101325732B (zh) * 2007-06-15 2011-07-20 华为技术有限公司 呼叫控制的方法和ims的电路交换控制装置及终端设备
US8406228B2 (en) 2006-06-20 2013-03-26 Intel Mobile Communications GmbH Message generating arrangement

Families Citing this family (34)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101379791B (zh) * 2005-12-19 2011-11-09 艾利森电话股份有限公司 用于在不同的协议域之间提供互操作性的技术
EP1964351A1 (en) * 2005-12-19 2008-09-03 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for enabling discovery within a home network
CN100583822C (zh) * 2006-04-25 2010-01-20 华为技术有限公司 具有会话更改功能的分组网络***及其实现方法和装置
ES2346563T3 (es) * 2006-06-09 2010-10-18 Telefonaktiebolaget Lm Ericsson (Publ) Gestion de interfases de multiples usuarios en un subsistema de multimedios ip.
US8391873B2 (en) * 2006-07-21 2013-03-05 Qualcomm Incorporated Systems and methods for coordinating supplementary services for voice telephone calls in a centralized fashion
CA2672922C (en) * 2006-12-21 2015-02-10 Rogier August Caspar Joseph Noldus Scp-controlled overlay between gsm and ims
WO2008084316A1 (en) * 2007-01-08 2008-07-17 Nokia Corporation Method for fast circuit switched service enabling handover from packet-switched only networks
FR2912024A1 (fr) * 2007-01-31 2008-08-01 France Telecom Reseau de communication comprenant des moyens de gestion de conflits lors de l'execution de plusieurs services de communication
US9049209B2 (en) * 2007-05-08 2015-06-02 At&T Intellectual Property I, L.P. Methods and apparatus to route a communication session in an internet protocol (IP) multimedia subsystem (IMS) network
US8144859B1 (en) * 2007-05-14 2012-03-27 Sprint Communications Company L.P. Integrated ENUM and number portability translation in a communication system
CN101335991B (zh) * 2007-06-29 2014-03-12 朗迅科技公司 使非sip用户呼叫sip用户容易的方法
US8681960B2 (en) * 2007-08-30 2014-03-25 8631654 Canada Inc. Extending originating capabilities of a subscriber to devices in any telephony network
US8774174B2 (en) * 2007-10-11 2014-07-08 At&T Intellectual Property I, Lp System and method for conveying end-to-end call status
KR101453971B1 (ko) * 2008-01-03 2014-10-21 삼성전자주식회사 무선 네트워크와 유선 네트워크의 연동을 위한 장치 및방법
CN101489288B (zh) 2008-01-16 2011-04-20 华为技术有限公司 演进分组网络中电路域业务的处理方法、***及相关设备
CN101978767B (zh) * 2008-01-31 2013-11-20 爱立信电话股份有限公司 移动端接的呼叫的电路交换回退
DK2250782T3 (en) * 2008-02-21 2018-11-26 Ericsson Telefon Ab L M Method of providing at least one value-added service in the packet switched telecommunications network
EP2637441A3 (en) * 2008-03-21 2014-05-14 Interdigital Patent Holdings, Inc. Method and apparatus to enable fallback to circuit switched domain from packet switched domain
WO2009132122A2 (en) * 2008-04-22 2009-10-29 Nortel Networks Limited Session transfer between different access network types
US8711846B2 (en) 2008-09-18 2014-04-29 Futurewei Technologies, Inc. Network attachment for IMS systems for legacy CS UE with home node B access
US8520682B2 (en) * 2008-09-18 2013-08-27 Futurewei Technologies, Inc. System and method for provision of IMS based services for legacy CS UE with home node B access
US8358647B2 (en) * 2008-09-18 2013-01-22 Futurewei Technologies, Inc. System and method for provision of IMS based services for legacy CS UE with home node B access
US8488596B2 (en) 2008-11-03 2013-07-16 At&T Intellectual Property I, L.P. Method and apparatus for sharing a single data channel for multiple signaling flows destined to multiple core networks
WO2010057538A2 (en) * 2008-11-24 2010-05-27 Telefonaktiebolaget Lm Ericsson (Publ) Providing circuit switched calls and services over a broadband network
US20100150144A1 (en) * 2008-12-12 2010-06-17 Bernard Ku Method and apparatus for completing a circuit switched service call in an internet protocol network
US9397862B2 (en) * 2008-12-12 2016-07-19 At&T Intellectual Property I, L.P. Method and apparatus for completing a circuit switched service call in an internet protocol network
CN102714818B (zh) 2009-10-30 2016-06-15 交互数字专利控股公司 用于无线通信的信令
EP2408258A1 (en) 2010-07-12 2012-01-18 NEC CASIO Mobile Communications, Ltd. Method for establishing an IP session while negotiating an audio channel over CS communication
FR2964281A1 (fr) * 2010-09-01 2012-03-02 France Telecom Procede de traitement de messages sip
US8953501B2 (en) * 2011-03-28 2015-02-10 Avaya Inc. IMS application sequencing optimizer
IN2013MN00752A (zh) * 2011-08-12 2015-06-12 Spreadtrum Comm Shanghai Co
WO2013087114A1 (en) * 2011-12-15 2013-06-20 Telefonaktiebolaget L M Ericsson (Publ) Service domain selection service indicator
US9160515B2 (en) * 2013-04-04 2015-10-13 Intel IP Corporation User equipment and methods for handover enhancement using scaled time-to-trigger and time-of-stay
CN103747430B (zh) * 2013-12-31 2018-10-19 华为技术有限公司 呼叫控制设备和处理用户业务的方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1161104A1 (en) * 2000-06-02 2001-12-05 TELEFONAKTIEBOLAGET L M ERICSSON (publ) Call control network, access control server and call control method
US20030026245A1 (en) * 2001-07-31 2003-02-06 Ejzak Richard Paul Communication system including an interworking mobile switching center for call termination
US20040190498A1 (en) * 2003-03-25 2004-09-30 Juha Kallio Method, system and gateway device for enabling interworking between IP and CS networks

Family Cites Families (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR950007572B1 (ko) * 1992-03-31 1995-07-12 삼성전자주식회사 Esd 보호장치
JPH09162713A (ja) * 1995-12-11 1997-06-20 Mitsubishi Electric Corp 半導体集積回路
CN1058196C (zh) 1996-09-24 2000-11-08 黄信璁 用于超高楼层爬升并左右横移的消防灭火装置
DE19814161B4 (de) 1998-03-30 2005-08-04 Siemens Ag Verfahren zum Verbindungsaufbau für ankommende, an einen Teilnehmer eines Kommunikationsnetzes gerichtete Anrufe sowie Dienstesteuerungseinheit zum Unterstützen des Verbindungsaufbaus
KR20010085327A (ko) 1998-08-03 2001-09-07 추후제출 패킷 데이터 및 ip 음성/멀티미디어 서비스를 지원하는플러그 및 플레이 무선 시스템
FI109444B (fi) 1999-01-11 2002-07-31 Nokia Corp Menetelmä ja järjestelmä datansiirtokanavien rinnakkaiskäyttöä varten
US6512761B1 (en) * 1999-02-02 2003-01-28 3Com Corporation System for adjusting billing for real-time media transmissions based on delay
FI991092A (fi) 1999-05-12 2000-11-13 Nokia Networks Oy Menetelmä tietoliikenneyhteyden laadun parantamiseksi ja verkkoelement ti
US6879581B1 (en) 2000-08-22 2005-04-12 Qualcomm Incorporated Method and apparatus for providing real-time packetized voice and data services over a wireless communication network
FR2822320B1 (fr) * 2001-03-16 2003-07-04 Evolium Sas Procede pour le controle de session d'appel multimedia dans un systeme cellulaire de radiocommunications mobiles
US7187666B1 (en) * 2001-03-30 2007-03-06 Ipr Licensing, Inc. Employing simulated acknowledgment signals for efficient handoffs in cellular packet networks
GB0115996D0 (en) 2001-06-29 2001-08-22 Nokia Corp Circuit-switched and packet-switched communications
CN1177508C (zh) 2001-08-07 2004-11-24 华为技术有限公司 一种实现异地智能用户漫游呼叫的方法
US6811575B2 (en) * 2001-12-20 2004-11-02 Rohm And Haas Company Method for marking hydrocarbons with anthraquinones
EP1376926B1 (en) 2002-06-25 2007-03-21 Alcatel Method and device for data broadcasting in third generation networks
SE0302004D0 (sv) * 2003-07-04 2003-07-04 Ericsson Telefon Ab L M Method and arrangement in a telecommunication system
US7885208B2 (en) * 2003-09-11 2011-02-08 Nokia Corporation IP-based services for circuit-switched networks
US7295853B2 (en) * 2004-06-30 2007-11-13 Research In Motion Limited Methods and apparatus for the immediate acceptance and queuing of voice data for PTT communications
CN100352295C (zh) 2005-01-24 2007-11-28 华为技术有限公司 Ip多媒体子***会话回落到电路交换呼叫的实现方法
CN1297124C (zh) 2004-09-30 2007-01-24 华为技术有限公司 Ip多媒体子***中利用电路交换承载业务的***及方法
KR100909542B1 (ko) * 2005-08-01 2009-07-27 삼성전자주식회사 Csi 단말과 ims 단말 사이의 음성 및 멀티미디어 서비스 연동을 위한 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1161104A1 (en) * 2000-06-02 2001-12-05 TELEFONAKTIEBOLAGET L M ERICSSON (publ) Call control network, access control server and call control method
US20030026245A1 (en) * 2001-07-31 2003-02-06 Ejzak Richard Paul Communication system including an interworking mobile switching center for call termination
US20040190498A1 (en) * 2003-03-25 2004-09-30 Juha Kallio Method, system and gateway device for enabling interworking between IP and CS networks

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101064683B (zh) * 2006-04-26 2011-04-20 华为技术有限公司 处理补充业务的方法、***及装置
US8582566B2 (en) * 2006-04-26 2013-11-12 Samsung Electronics Co., Ltd Method and system of forwarding capability information of user equipment in internet protocol multimedia subsystem network
EP1858222A3 (en) * 2006-04-26 2008-04-23 Huawei Technologies Co., Ltd. Method, apparatus and system for session adding
US20070259651A1 (en) * 2006-04-26 2007-11-08 Samsung Electronics Co., Ltd. Method and system of forwarding capability information of user equipment in Internet Protocol Multimedia Subsystem network
US8406228B2 (en) 2006-06-20 2013-03-26 Intel Mobile Communications GmbH Message generating arrangement
DE102006028324A1 (de) * 2006-06-20 2007-12-27 Infineon Technologies Ag Nachrichtenerzeugungsanordnung und Verfahren zum Erzeugen einer Nachricht
US9001738B2 (en) 2006-06-20 2015-04-07 Intel Mobile Communications GmbH Message generating arrangement
US9380629B2 (en) 2006-06-20 2016-06-28 Intel Deutschland Gmbh Message generating arrangement
DE102006028324B4 (de) * 2006-06-20 2020-02-13 Intel Deutschland Gmbh Nachrichtenerzeugungsanordnung und Verfahren zum Erzeugen einer Nachricht
EP2090069A1 (en) * 2006-11-03 2009-08-19 Telefonaktiebolaget LM Ericsson (PUBL) Accessing a communications network
WO2008071213A1 (en) * 2006-12-14 2008-06-19 Telefonaktiebolaget Lm Ericsson (Publ) Methods, apparatuses and computer program products for routing a call from a circuit switched domain to a unified service domain
WO2008095440A1 (fr) * 2007-02-08 2008-08-14 Huawei Technologies Co., Ltd. Procédé, système de communication et dispositif pour acquérir et fournir un numéro msisdn
CN101325732B (zh) * 2007-06-15 2011-07-20 华为技术有限公司 呼叫控制的方法和ims的电路交换控制装置及终端设备
US8369314B2 (en) 2007-06-15 2013-02-05 Huawei Technologies Co., Ltd. Call control method and IMS CS control apparatus

Also Published As

Publication number Publication date
EP1744569B1 (en) 2009-02-18
US20070121608A1 (en) 2007-05-31
US8089956B2 (en) 2012-01-03
EP1744569A4 (en) 2007-06-27
EP1744569A1 (en) 2007-01-17
DE602005012817D1 (de) 2009-04-02
ATE423436T1 (de) 2009-03-15

Similar Documents

Publication Publication Date Title
WO2006034658A1 (fr) Procede et systeme de realisation de communication
KR100701637B1 (ko) 회선 교환 및 패킷 교환 통신들
US7746849B2 (en) Providing packet-based multimedia services via a circuit bearer
US8213418B2 (en) Providing packet-based multimedia services via a circuit breaker
JP3830898B2 (ja) 無線通信ネットワークにおけるパケット音声呼サービスを提供するための方法及びネットワークシステム
JP4212230B2 (ja) メディア通信システム及び該システムにおける端末装置
WO2008064565A1 (fr) Système, procédé et dispositifs pour réaliser la continuité de session multimédia
WO2008061443A1 (fr) Système, procédé et appareil assurant la continuité d'un appel multimédia
WO2006063536A1 (fr) Procede et systeme pour maintenir la continuite d'une session
JP2009517933A (ja) Imsに登録されたユーザのための呼処理
WO2007079679A1 (fr) Élément réseau d'interfonctionnement, système d'interfonctionnement entre le terminal csi et le terminal ims et procédé associé
WO2009012665A1 (fr) Procédé pour assurer une continuité d'appel multimédia, équipement et système associés
WO2009015525A1 (en) A method for switching the session control path of ip multimedia core network subsystem centralized service
WO2009149667A1 (zh) 被叫接入的方法、装置和***
US8879539B2 (en) Method of and a system for establishing a call over an IP multi media communications system and a circuit switched communications system
CN100488313C (zh) 一种ims网络sip终端互通***及其方法
WO2008116386A1 (fr) Procédé, système et dispositif pour fournir un service multi-session à des abonnés
EP2575320A1 (en) Telecommunications system and method for inter access network handover
WO2010048845A1 (zh) 高速分组数据网络中紧急呼叫业务的实现方法和***
FI108185B (fi) Yhteyksien hallintamenetelmä
WO2008110110A1 (fr) Procédé et système de fourniture de service de sous-système multimédia ip
WO2009092437A1 (en) Completion of fax and analog data call
KR20080051993A (ko) 데이터 통신 네트워크를 통해 음성 통화 서비스를 제공하는방법 및 그 장치
KR101384160B1 (ko) 음성메시지 서비스 제공을 위한 패킷 서비스 시스템 및 부가서비스 제어기, 그리고 그의 음성메시지 서비스 제공 방법
KR100921557B1 (ko) Svd 서비스를 이용하여 실시간으로 데이터를 전송하는방법 및 시스템

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV LY MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWE Wipo information: entry into national phase

Ref document number: 11562237

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2005802141

Country of ref document: EP

WWP Wipo information: published in national office

Ref document number: 2005802141

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

WWP Wipo information: published in national office

Ref document number: 11562237

Country of ref document: US