WO2008080342A1 - Procédé et système pour mettre en application un service de simulation, procédé pour mettre en application l'interfonctionnement, et unité pour commander l'interfonctionnement - Google Patents
Procédé et système pour mettre en application un service de simulation, procédé pour mettre en application l'interfonctionnement, et unité pour commander l'interfonctionnement Download PDFInfo
- Publication number
- WO2008080342A1 WO2008080342A1 PCT/CN2007/071305 CN2007071305W WO2008080342A1 WO 2008080342 A1 WO2008080342 A1 WO 2008080342A1 CN 2007071305 W CN2007071305 W CN 2007071305W WO 2008080342 A1 WO2008080342 A1 WO 2008080342A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- user identifier
- control unit
- circuit domain
- domain network
- network
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Ceased
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/102—Gateways
- H04L65/1043—Gateway controllers, e.g. media gateway control protocol [MGCP] controllers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1069—Session establishment or de-establishment
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1083—In-session procedures
- H04L65/1095—Inter-network session transfer or sharing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M7/00—Arrangements for interconnection between switching centres
- H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
- H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
- H04M7/1225—Details of core network interconnection arrangements
- H04M7/123—Details of core network interconnection arrangements where the packet-switched network is an Internet Protocol Multimedia System-type network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/10—Architectures or entities
- H04L65/1016—IP multimedia subsystem [IMS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/22—Arrangements for supervision, monitoring or testing
- H04M3/2281—Call monitoring, e.g. for law enforcement purposes; Call tracing; Detection or prevention of malicious calls
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42034—Calling party identification service
- H04M3/42042—Notifying the called party of information on the calling party
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/42025—Calling or Called party identification service
- H04M3/42085—Called party identification service
- H04M3/42093—Notifying the calling party of information on the called or connected party
Definitions
- the present invention relates to the field of service processing technologies, and specifically relates to a public switched telephone network/integrated service digital network (PSTN/ISDN) analog service implementation method, system, and an IP multimedia subsystem network and circuit domain network interworking implementation method, and an interworking control unit.
- PSTN/ISDN public switched telephone network/integrated service digital network
- Session Initiation Protocol As the packet telecommunication core network call control signaling is the current technological development.
- IP IP Multimedia Subsystem
- NTN The core network of the network (NGN).
- TISPAN ETSI's Telecom and Internet Convergence Service and Advanced Network Protocol
- PSTN/ISDN public switched telephone network/integrated service digital network
- WI Work Item
- OIP Originating Identity Presentation
- TIP Terminal Identity Presentation
- MCID Malicious Call Identification
- the business logic of the OIP, TIP, and MCID services is implemented on the application server (AS).
- the MCID service and the OIP service need to identify the calling party identity of a session, and the TIP service needs to identify the called user identity of a session.
- the user ID is carried in the P-Asserted-Identity header field of the SIP message.
- the P-CSCF inserts the P-Asserted-Identity header field for carrying the user identifier in the SIP message.
- the user identity is passed in the Calling Party Number and Connected Number parameters of the Signaling System 7 (SS7) message.
- the Media Gateway Control Unit In order to obtain the circuit domain network user identity in the IMS network, the Media Gateway Control Unit (MGCF) needs to map the Calling Party Number and Connected Number parameters to the P-Asserted-Identity header field of the SIP message.
- the circuit domain network does not require the user ID to be provided. Therefore, when the SS7 message does not contain the Calling Party Number and Connected Number parameters, the MGCF cannot obtain the user ID of the circuit domain network user, which may result in subsequent services being unachievable.
- FIG. 1 shows the existing implementation MCID.
- Step 101 The AS of the IMS network detects that the signaling message from the circuit domain network does not carry the calling party identifier when processing the MCID service, and requests the calling user identifier from the MGCF by using the extended SIP message.
- Step 102 After receiving the requesting subscriber identity message, the MGCF sends an identification request (IDR) message to the circuit domain network.
- IDR identification request
- Step 103 After receiving the IDR message, the circuit domain network returns the calling subscriber identity to the MGCF through an identification response (IRS) message.
- IDS identification response
- Step 104 The MGCF receives the IRS message, and sends the caller ID carried in the message to the AS, and the AS performs the MCID service processing according to the caller ID.
- the method has the following disadvantages: First, the existing SIP protocol is required to be extended, which increases the difficulty of implementation; secondly, the AS needs to perform signaling interaction with the MGCF, and adds a network interface and The complexity of AS business processing. SUMMARY OF THE INVENTION
- the present invention provides a method and system for implementing a simulated service to reduce the complexity of implementing a PSTN/ISDN analog service.
- the present invention provides an IMS network and circuit domain network interworking implementation method and an interworking control unit, so as to reduce the implementation complexity of the interworking between the IMS network and the circuit domain network.
- An analog business implementation method including:
- the interworking control unit detects that the circuit domain network user identifier is not carried in the call signaling message from the circuit domain network, obtains the circuit domain network user identifier, and sends the obtained user identifier to the IMS network, and the IMS network according to the user identifier Perform PSTN/ISDN analog service processing.
- An analog service implementation system includes: a circuit domain network, an interworking control unit, and an IMS network, wherein:
- circuit domain network configured to send a call signaling message to the interworking control unit
- the interworking control unit is configured to: after detecting that the call signaling message sent by the circuit domain network does not carry the circuit domain network user identifier, send the obtained circuit domain network user identifier to the IMS network;
- the IMS network is configured to perform PSTN/ISDN analog service processing according to the circuit domain network user identity sent by the interworking control unit.
- An interworking control unit includes: a default user identity storage module and a user identity acquisition module, where:
- a default user identifier storage module configured to store a default circuit domain network user identifier
- a user identifier obtaining module configured to detect a call signaling message sent by the circuit domain network
- the user identifier read from the default user identity storage module is carried in the SIP message and sent to the IMS network.
- An interworking control unit includes: a user identity detection module and a user identity acquisition module, where:
- a user identity detection module configured to receive a call signaling message sent by the circuit domain network, and when detecting that the circuit domain network user identifier is not carried in the message, send an acquisition indication to the user identifier;
- the user identifier obtaining module is configured to send a request user identifier message to the circuit domain network according to the obtaining indication sent by the user identifier detecting module, and carry the user identifier sent by the circuit domain network to the IMS network in the SIP message.
- An implementation method for interworking between an IMS network and a circuit domain network including:
- the interworking control unit detects that the circuit signaling user message from the circuit domain network does not carry the circuit domain network user identifier, obtains the circuit domain network user identifier, and sends the obtained user identifier to the IP multimedia subsystem IMS network.
- the present invention actively acquires the circuit domain network in the current call when the interworking control unit detects that the circuit domain network user identity of the call is not carried in the call signaling message sent by the circuit domain network.
- the user identifier is sent to the IMS network, and the existing SIP protocol is not required to be extended, and the IMS network and the interworking control unit are not required to obtain the signaling interaction of the user identifier, thereby reducing the interworking between the IMS network and the circuit domain network.
- the complexity also reduces the complexity of implementing PSTN/ISDN analog services.
- FIG. 1 is a timing diagram of a message flow of an existing MCID service
- 2 is a system composition diagram of implementing a PSTN/ISDN analog service according to an embodiment of the present invention
- 3 is a schematic structural diagram of an interworking control unit according to an embodiment of the present invention
- FIG. 4 is a flowchart of implementing a PSTN/ISDN analog service according to an embodiment of the present invention
- FIG. 5 is a sequence diagram of a message flow for implementing an MCID service according to an embodiment of the present invention
- FIG. 6 is a schematic diagram of implementing an OIP service according to an embodiment of the present invention
- FIG. 7 is a sequence diagram of a message flow for implementing a TIP service according to an embodiment of the present invention.
- FIG. 2 is a schematic structural diagram of a system for implementing a PSTN/ISDN analog service according to an embodiment of the present invention.
- the method mainly includes: a circuit domain network 21, an interworking control unit 22, a session control unit 23, and a service control unit 24,
- the session control unit 23 and the service control unit 24 are located in the IMS network domain, and the functions of each unit are as follows:
- the circuit domain network 21 is configured to send a call signaling message in an ISDN User Part (ISUP) or Bearer Independent Call Control (BICC) protocol to the interworking control unit 22, and receive a requesting user identification message sent by the interworking control unit 22, The interworking control unit 22 returns the user identification.
- ISUP ISDN User Part
- BICC Bearer Independent Call Control
- the interworking control unit 22 is configured to: after receiving the call signaling message sent by the circuit domain network 21, if it is detected that the message does not carry the circuit domain network user identifier of the current call, send the request user identifier to the circuit domain network 21 The message, and the user identifier returned by the circuit domain network 21 is carried in the SIP message and sent to the session control unit 23.
- the interworking control unit 22 may be an MGCF, an Interworking Border Control Unit (IBCF), or the like. Alternatively, the interworking control unit 22 is configured to save the default circuit domain network user identifier, and if it detects that the call signaling message sent by the circuit domain network 21 does not carry the circuit domain network user identifier of the current call, the default is saved by itself. The circuit domain network user identity is carried in the SIP message and sent to the session control unit 23.
- IBCF Interworking Border Control Unit
- the interworking control unit 22 is configured to save the default circuit domain network user identifier, After the circuit domain network 21 sends the request user identification message, if the user identifier returned by the circuit domain network 21 is not received, the default circuit domain network user identifier saved by itself is carried in the SIP message and sent to the session control unit 23.
- the session control unit 23 is configured to receive a SIP message sent by the interworking control unit 22 and carry the circuit domain user identifier, and forward the message to the service control unit 24.
- the session control unit 23 may be a CSCF or the like in an IMS network.
- the service control unit 24 is configured to perform PSTN/ISDN analog service processing according to the SIP message carrying the circuit domain network user identifier sent by the session control unit 23.
- the service control unit 24 may be an AS or the like in the IMS network.
- FIG. 3 is a schematic structural diagram of a session control unit 22 according to an embodiment of the present invention. As shown in FIG. 3, the method mainly includes: a default user identifier storage module 221, a user identifier detection module 222, and a user identifier acquisition module 223, where:
- the user identity detection module 222 is configured to receive a call signaling message sent by the circuit domain network. If the message does not carry the circuit domain network user identifier, the user identity acquisition module 223 sends an acquisition indication.
- the user identifier obtaining module 223 is configured to send a request user identification message to the circuit domain network 21 according to the acquisition indication sent by the user identifier detection module 222, and carry the circuit domain network user identifier returned by the circuit domain network 21 in the SIP message and send the IMS network.
- the user identifier obtaining module 223 is configured to send a request user identification message to the circuit domain network 21 according to the acquisition indication sent by the user identifier detection module 222, and if the circuit domain network user identifier returned by the circuit domain network 21 is not received,
- the default user identifier is read from the default user identifier storage module 221, and the default user identifier is carried in a SIP message and sent to the IMS network.
- the user identifier obtaining module 223 is configured to send according to the user identifier detecting module 222.
- the obtaining instruction indicates that the default circuit domain network user identifier is read from the default user identity storage module 221, and the default circuit domain network user identifier is carried in the SIP message and sent to the IMS network.
- FIG. 4 is a flowchart of implementing PSTN/ISDN analog service according to an embodiment of the present invention. As shown in FIG. 4, the specific steps are as follows:
- Step 401 The circuit domain network sends a call signaling message to the interworking control unit.
- Step 402 The interworking control unit receives the call signaling message, and detects that the message does not carry the circuit domain network user identifier in the current call, obtains the circuit domain network user identifier, and carries the user identifier in the SIP message. Send to the IMS network.
- the circuit domain network user identifier may be a calling subscriber identity or a called subscriber identity.
- the interworking control unit can obtain the circuit domain network user identifier in the following two ways: Method 1: The interworking control unit pre-configures a default circuit domain network user identifier, and detects that the call signaling message sent by the circuit domain network does not carry the current call. When the circuit domain network user identifier is in the middle, the default circuit domain network user identifier is carried in the SIP message and sent to
- the default circuit domain network user ID can be set arbitrarily, or can be determined according to the relevant information of each call, such as: According to the network of the circuit domain network user in the current call, the information of the current call occupation circuit, and the current call circuit The relay group information or the signaling point coding information of the office point of the circuit domain network user in the current call is set.
- the interworking control unit can carry the default circuit domain network user identity in the SIP message by:
- the first step is to add a parameter in the header field for carrying the user identification attribute information in the SIP message, where the parameter is used to indicate that the user identifier carried in the message is a default circuit domain network user identifier, such as: Private (Privacy) ) Add an enumeration value "default" to the header field.
- the second step is to add a parameter in the header field for carrying the user identifier in the SIP message, where the parameter is used to indicate that the user identifier carried in the message is the default circuit domain network user identifier.
- the parameter is used to indicate that the user identifier carried in the message is the default circuit domain network user identifier.
- the keyword is added to the user identifier (P_Asserted_Identity) header field.
- the defaults path is three.
- a new header field is added to the SIP message to indicate that the user identifier carried in the message is the default circuit domain network user identifier.
- the interworking control unit sends a request user identification message to the circuit domain network when detecting that the call signaling message sent by the circuit domain network does not carry the circuit domain network user identifier in the current call, and the circuit domain network receives the message. After that, the circuit domain network user identifier of the current call is returned to the interworking control unit.
- the interworking control unit does not receive the user identifier sent by the circuit domain network
- the default circuit domain network user identifier may be obtained by using the method 1.
- Step 403 The IMS network receives the message, and performs PSTN/ISDN analog service processing according to the circuit domain network user identifier carried in the message.
- the present invention will be further described in detail below by taking the MCID service, the OIP service, and the TIP service as examples.
- FIG. 5 is a timing diagram of a message flow for implementing an MCID service according to an embodiment of the present invention. As shown in FIG. 5, the specific steps are as follows:
- Step 501 A user in the circuit domain network initiates a call request to call a user in the IMS network, and the circuit domain network sends a call request to the MGCF that communicates with the IMS network through an initial address (IMM) message in the ISUP protocol, where the IAM message is not Carry the identity of the calling user.
- IMM initial address
- Step 502 The MGCF receives the IAM message, and detects that the message does not carry the calling user identity.
- Step 503 The MGCF sends an IDR message to the circuit domain network to request to provide the calling user identity.
- Step 504 The circuit domain network receives the IDR message and returns an IRS message to the MGCF.
- Step 505 After receiving the IRS message, the MGCF determines whether the message carries the calling party. User identification, if yes, go to step 506; otherwise, go to step 507.
- the circuit domain network may not be able to obtain the calling party identity, thereby returning an IRS message that does not carry the calling party identity to the MGCF.
- the A office knows the calling user identity from the call request initiated by the calling terminal, but it is between the A office and the B office.
- the protocol message does not support the presence of the calling user ID, and the A office cannot send the calling user ID to the B office.
- the B office After receiving the IDR message, the B office cannot obtain the calling user ID from the A office.
- An IRS message that does not carry the calling party identity is returned to the MGCF.
- Step 506 The MGCF sends the calling party identifier in the IRS message to the AS in the IMS network through the S-CSCF in the call request (INVITE) message, and proceeds to step 408.
- Step 507 The MGCF carries the default caller ID that is saved by itself to the AS in the IMS network through the S-CSCF in the call request (INVITE) message.
- the MGCF can set the same default caller ID for all calls, or it can be determined according to the information about each call, such as: According to the network where the calling user is located, the information of the circuit occupied by the call, and the location of the call circuit.
- the relay circuit information or the signaling point coding information of the MGCF is set to a default identifier.
- the MGCF can use the default telephone uniform resource identifier (TEL URI): tel: +0000-23 as this time.
- Caller ID of the call where 0000 represents the default identity provided by the calling subscriber identity for the MGCF, 23 the trunk circuit number used for the call; or, the MGCF uses a default SIP URI: DefaultIdCircuit23 @ MGCF .com is used as the calling party ID of the current call, where Circuit 23 indicates that the circuit number occupied by this call is 23.
- Step 508 The AS in the IMS network receives the call request message, and performs MCID service processing according to the calling party identifier in the message.
- the MGCF when the MGCF detects that the IAM message does not carry the calling party identifier, the MGCF may directly carry the default calling user identifier in the call request message.
- FIG. 6 is a timing diagram of a message flow for implementing an OIP service according to an embodiment of the present invention. As shown in FIG. 6, the specific steps are as follows:
- Step 601 A user in the circuit domain network initiates a call request to call a user in the IMS network, and the circuit domain network sends a call request to the MGCF that communicates with the IMS network through the IAM message in the ISUP protocol, where the IAM message does not carry the calling user.
- the circuit domain network sends a call request to the MGCF that communicates with the IMS network through the IAM message in the ISUP protocol, where the IAM message does not carry the calling user.
- Step 602 The MGCF receives the IAM message, and detects that the message does not carry the calling user identity.
- Step 603 The MGCF sends an information request (INR) message to the circuit domain network to request the calling party identifier.
- ISR information request
- Step 604 The circuit domain network receives the INR message and returns an information (INF) message to the MGCF.
- INF information
- Step 605 After receiving the INF message, the MGCF determines whether the message carries the calling user identifier. If yes, go to step 606; otherwise, go to step 607.
- Step 606 The MGCF carries the calling party identifier in the INF message in the call request (INVITE) message to the AS in the IMS network through the S-CSCF, and proceeds to step 608.
- Step 607 The MGCF carries the default caller ID that is saved by itself to the AS in the IMS network through the S-CSCF in the call request (INVITE) message.
- Step 608 The AS in the IMS network receives the call request message, and performs OIP service processing according to the calling party identifier in the message.
- FIG. 7 is a sequence diagram of a message flow for implementing a TIP service according to an embodiment of the present invention. As shown in FIG. 7, the specific steps are as follows:
- Step 701 A user in the IMS network initiates a call request, and calls a user in the circuit domain network, and the IMS network sends a call request (INVITE) message to the MGCF that communicates with the circuit domain network.
- INVITE call request
- Step 702 The MGCF receives the call request message, and sends an IAM to the circuit domain network.
- the IAM message may carry an indication that the called user identifier is requested.
- Step 703 The circuit domain network receives the IAM message and returns an acknowledgement (ANM) message to the MGCF.
- NAM acknowledgement
- Step 704 The MGCF receives the ANM message, and detects that the message does not carry the called user identifier.
- Step 705 The MGCF carries the default called user identifier saved by itself to the AS in the 200 response (OK) message sent to the IMS network through the S-CSCF.
- Step 706 The AS of the IMS network receives the 200 response message, and performs TIP service processing according to the called user identifier in the message.
Landscapes
- Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Telephonic Communication Services (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Description
模拟业务实现方法、 系统及互通实现方法、 互通控制单元 技术领域
本发明涉及业务处理技术领域, 具体涉及公共交换电话网络 /综合业 务数字网络( PSTN/ISDN )模拟业务实现方法、 系统及 IP多媒体子系统 网络和电路域网络互通实现方法、 互通控制单元。 发明背景
随着分组技术的不断成熟, 基于电路交换的传统电信网络正在向着 基于分组交换的宽带电信网发展, 而使用会话发起协议( SIP )作为分组 电信核心网的呼叫控制信令则是当前的技术发展趋势之一, 如国际电信 联盟电信标准部分(ITU-T )和欧洲电信标准协会(ETSI ) 当前都采用 第三代合作伙伴组织 (3GPP )定义的 IP 多媒体子系统(IMS ) 网络架 构作为下一代网络(NGN ) 的核心网。
在新的分组电信网络中,新的分组终端 SIP终端将逐步取代传统的 终端话机。 其中, ETSI 下属的电信和互联网融合业务及高级网络协议 ( TISPAN )将在 NGN中向 SIP终端用户提供的具有传统业务特征的业 务统称为公共交换电话网络 /综合业务数字网络( PSTN/ISDN )模拟业务。 TISPAN成立了多个工作项目 (WI, Work Item ) 来研究这些模拟业务, 如: 发端标识呈现(OIP )、终端标识呈现(TIP )、恶意呼叫识别(MCID ) 业务等。
在 TISPAN的规范标准中, OIP、 TIP, MCID业务的业务逻辑在应 用服务器( AS )上实现。 MCID业务和 OIP业务需要识别出一个会话的 主叫用户标识, TIP业务需要识别出一个会话的被叫用户标识。 当用户
位于 IMS 网络内部时, 用户标识携带在 SIP消息的 P- Asserted-Identity 头域中, P-CSCF 会在 SIP 消息中插入用于携带用户标识的 P- Asserted-Identity头域。
当用户位于电路域网络时, 用户标识在信令系统 7 ( SS7 ) 消息的 Calling Party Number和 Connected Number参数中传递。 为了在 IMS网 络中获得电路域网络用户标识, 媒体网关控制单元 (MGCF ) 需要将 Calling Party Number 和 Connected Number 参数映射到 SIP 消息的 P-Asserted-Identity头域。 但是, 电路域网络不要求必须提供用户标识, 因此, 当 SS7消息不包含 Calling Party Number和 Connected Number参 数时, MGCF无法获得电路域网络用户的用户标识, 从而导致后续业务 无法实现。 为了确保 IMS网络能够获得电路域网络用户的用户标识, 在 TISPAN#llter会议上, DT在文稿 lltTD273中提出了在 MCID业务中获 得主叫用户标识的方法, 图 1给出了现有的实现 MCID业务的流程图, 如图 1所示, 其具体步骤如下:
步骤 101 : IMS网络的 AS在处理 MCID业务时检测到来自电路域 网络的信令消息中未携带主叫用户标识, 则通过扩展的 SIP 消息向 MGCF请求主叫用户标识。
步骤 102: MGCF收到该请求主叫用户标识消息后, 向电路域网络 发送识别请求(IDR ) 消息。
步骤 103: 电路域网络收到该 IDR消息后, 将主叫用户标识通过识 别应答(IRS ) 消息返回给 MGCF。
步骤 104: MGCF收到 IRS消息, 将该消息中携带的主叫用户标识 发送给 AS, AS根据该主叫用户标识进行 MCID业务处理。
该方法有以下缺点: 首先, 要求对现有 SIP协议进行扩展, 增加了 实现难度; 其次, AS需要同 MGCF进行信令交互, 增加了网络接口和
AS业务处理的复杂性。 发明内容 本发明提供一种模拟业务实现方法及系统,以降低实现 PSTN/ISDN 模拟业务的复杂度;
同时,本发明提供一种 IMS网络和电路域网络互通实现方法及互通 控制单元, 以降低 IMS网络与电路域网络互通的实现复杂度。
本发明的技术方案是这样实现的:
一种模拟业务实现方法, 包括:
互通控制单元检测到来自电路域网络的呼叫信令消息中未携带电路 域网络用户标识, 获取该电路域网络用户标识, 并将获取到的用户标识 发送给 IMS网络, IMS网络根据所述用户标识进行 PSTN/ ISDN模拟业 务处理。
一种模拟业务实现系统, 包括: 电路域网络、 互通控制单元和 IMS 网络, 其中:
电路域网络, 用于向互通控制单元发送呼叫信令消息;
互通控制单元, 用于在检测到电路域网络发来的呼叫信令消息未携 带电路域网络用户标识后, 将获取到的电路域网络用户标识发送给 IMS 网络;
IMS网络, 用于根据互通控制单元发来的电路域网络用户标识, 进 行 PSTN/ISDN模拟业务处理。
一种互通控制单元, 包括: 默认用户标识存储模块和用户标识获取 模块, 其中:
默认用户标识存储模块, 用于存储默认的电路域网络用户标识; 用户标识获取模块, 用于在检测到电路域网络发来的呼叫信令消息
未携电路域网络用户标识时, 将从默认用户标识存储模块读取的用户标 识携带在 SIP消息中发送给 IMS网络。
一种互通控制单元, 包括:用户标识检测模块和用户标识获取模块, 其中:
用户标识检测模块, 用于接收电路域网络发来的呼叫信令消息, 在 检测到该消息中未携带电路域网络用户标识时, 向用户标识获耳 ^莫块发 送获取指示;
用户标识获取模块, 用于根据用户标识检测模块发来的获取指示, 向电路域网络发送请求用户标识消息, 将电路域网络发来的用户标识携 带在 SIP消息中发送给 IMS网络。
一种 IMS网络和电路域网络互通实现方法, 包括:
互通控制单元检测到来自电路域网络的呼叫信令消息中未携带电路 域网络用户标识, 获取该电路域网络用户标识, 并将获取到的用户标识 发送给 IP多媒体子系统 IMS网络。
与现有技术相比, 本发明通过在互通控制单元在检测到电路域网络 发来呼叫信令消息中未携带本次呼叫的电路域网络用户标识时, 主动获 取本次呼叫中的电路域网络用户标识,然后将该用户标识发送给 IMS网 络, 无需对现有 SIP协议进行扩展, 也无需 IMS网络与互通控制单元进 行获取用户标识的信令交互,降低了 IMS网络与电路域网络互通的实现 复杂度, 也降低了实现 PSTN/ISDN模拟业务的复杂度。 附图简要说明
图 1为现有的实现 MCID业务的消息流程时序图;
图 2为本发明实施例提供的实现 PSTN/ISDN模拟业务的系统组成 图;
图 3为本发明实施例提供的互通控制单元的结构示意图;
图 4为本发明实施例提供的实现 PSTN/ISDN模拟业务的流程图; 图 5为本发明实施例提供的实现 MCID业务的消息流程时序图; 图 6为本发明实施例提供的实现 OIP业务的消息流程时序图; 图 7为本发明实施例提供的实现 TIP业务的消息流程时序图。 实施本发明的方式
下面结合附图及具体实施例对本发明再作进一步详细的说明。
图 2为本发明实施例提供的实现 PSTN/ISDN模拟业务的系统组成 图, 如图 2所示, 其主要包括: 电路域网络 21、 互通控制单元 22、 会 话控制单元 23和业务控制单元 24, 其中, 会话控制单元 23和业务控制 单元 24位于 IMS网络域, 各单元的功能如下:
电路域网络 21:用于向互通控制单元 22发送 ISDN用户部分( ISUP ) 或承载无关呼叫控制(BICC )协议中的呼叫信令消息, 收到互通控制单 元 22发来的请求用户标识消息, 向互通控制单元 22返回用户标识。
互通控制单元 22: 用于在收到电路域网络 21发来的呼叫信令消息 后, 若检测到该消息未携带本次呼叫的电路域网络用户标识, 则向电路 域网络 21发送请求用户标识消息, 并将电路域网络 21返回的用户标识 携带在 SIP消息中发送给会话控制单元 23。
互通控制单元 22可以是 MGCF、 互通边界控制单元(IBCF )等。 或者, 互通控制单元 22用于, 保存默认电路域网络用户标识, 若检 测到电路域网络 21 发来的呼叫信令消息中未携带本次呼叫的电路域网 络用户标识, 则将自身保存的默认电路域网络用户标识携带在 SIP消息 中发送给会话控制单元 23。
或者, 互通控制单元 22用于, 保存默认电路域网络用户标识, 在向
电路域网络 21发送请求用户标识消息后, 若未收到电路域网络 21返回 的用户标识, 则将自身保存的默认电路域网络用户标识携带在 SIP消息 中发送给会话控制单元 23。
会话控制单元 23: 用于接收互通控制单元 22发来的携带电路域网 络用户标识的 SIP消息, 并将该消息转发给业务控制单元 24。
会话控制单元 23可以是 IMS网络中的 CSCF等。
业务控制单元 24: 用于根据会话控制单元 23发来的携带电路域网 络用户标识的 SIP消息, 进行 PSTN/ISDN模拟业务处理。
业务控制单元 24可以是 IMS网络中的 AS等。
图 3是本发明实施例提供的会话控制单元 22的结构示意图,如图 3 所示, 其主要包括: 默认用户标识存储模块 221、用户标识检测模块 222 和用户标识获取模块 223 , 其中:
默认用户标识存储模块 221: 用于保存默认电路域网络用户标识。 用户标识检测模块 222: 用于接收电路域网络 21发来的呼叫信令消 息, 若检测到该消息未携带电路域网络用户标识, 则向用户标识获取模 块 223发送获取指示。
用户标识获取模块 223: 用于根据用户标识检测模块 222发来的获 取指示, 向电路域网络 21发送请求用户标识消息, 将电路域网络 21返 回的电路域网络用户标识携带在 SIP消息中发送给 IMS网络。
或者, 用户标识获取模块 223用于, 根据用户标识检测模块 222发 来的获取指示, 向电路域网络 21 发送请求用户标识消息, 若未收到电 路域网络 21 返回的电路域网络用户标识, 则从默认用户标识存储模块 221读取默认用户标识,将该默认用户标识携带在 SIP消息中发送给 IMS 网络。
或者, 用户标识获取模块 223用于, 根据用户标识检测模块 222发
来的获取指示, 从默认用户标识存储模块 221读取默认电路域网络用户 标识,将该默认电路域网络用户标识携带在 SIP消息中发送给 IMS网络。
图 4为本发明实施例提供的实现 PSTN/ISDN模拟业务的流程图, 如图 4所示, 其具体步骤如下:
步骤 401: 电路域网络向互通控制单元发送呼叫信令消息。
步骤 402: 互通控制单元收到该呼叫信令消息, 检测到该消息未携 带本次呼叫中的电路域网络用户标识, 则获取该电路域网络用户标识, 并将该用户标识携带在 SIP消息中发送给 IMS网络。
电路域网络用户标识可以是主叫用户标识,也可以是被叫用户标识。 互通控制单元可通过如下两种方式获取电路域网络用户标识: 方式一、 互通控制单元预先配置一个默认电路域网络用户标识, 当 检测到电路域网络发来的呼叫信令消息未携带本次呼叫中的电路域网 络用户标识时, 将该默认电路域网络用户标识携带在 SIP消息中发送给
IMS网络。
默认电路域网络用户标识可以任意设置, 也可以根据每次呼叫的相 关信息确定, 如: 根据本次呼叫中的电路域网络用户所在的网络、 本次 呼叫占用电路的信息、 本次呼叫电路所在的中继群信息或本次呼叫中的 电路域网络用户所在局点的信令点编码信息等设置。
互通控制单元可通过以下途径将默认电路域网络用户标识携带在 SIP消息中:
途径一、 在 SIP消息中的用于携带用户标识属性信息的头域中新增 加一个参数, 该参数用于表示该消息中携带的用户标识为默认电路域网 络用户标识, 如: 在私有 (Privacy ) 头域中增加一个枚举值" default"。
途径二、在 SIP消息中的用于携带用户标识的头域中增加一个参数, 该参数用于表示该消息中携带的用户标识为默认电路域网络用户标识,
如: 在用户标识( P_Asserted_Identity ) 头域中增加关键字" defaults 途径三、 在 SIP消息中新增一个专门用于表示该消息中携带的用户 标识为默认电路域网络用户标识的头域。
方式二、 互通控制单元在检测到电路域网络发来的呼叫信令消息未 携带本次呼叫中的电路域网络用户标识时, 向电路域网络发送请求用户 标识消息, 电路域网络收到该消息后, 将本次呼叫的电路域网络用户标 识返回给互通控制单元。
若互通控制单元未收到电路域网络发来的用户标识, 则可采用方式 一获取默认电路域网络用户标识。
步骤 403: IMS 网络收到该消息, 根据该消息携带的电路域网络用 户标识进行 PSTN/ISDN模拟业务处理。
以下分别以 MCID业务、 OIP业务、 TIP业务为例, 对本发明进行 进一步详细说明。
图 5为本发明实施例提供的实现 MCID业务的消息流程时序图, 如 图 5所示, 其具体步骤如下:
步骤 501: 电路域网络中的用户发起呼叫请求, 呼叫 IMS网络中的 用户, 电路域网络通过 ISUP协议中的初始地址( IAM ) 消息发送呼叫 请求到和 IMS网络互通的 MGCF , 该 IAM消息中未携带主叫用户的标 识。
步骤 502: MGCF收到 IAM消息, 检测到该消息未携带主叫用户标 识。
步骤 503: MGCF向电路域网络发送 IDR消息, 以请求提供主叫用 户标识。
步骤 504: 电路域网络收到 IDR消息, 向 MGCF返回 IRS消息。 步骤 505: MGCF收到该 IRS消息后, 判断该消息是否携带主叫用
户标识, 若是, 执行步骤 506; 否则, 执行步骤 507。
由于某些原因, 电路域网络可能无法获得主叫用户标识, 从而向 MGCF返回不携带主叫用户标识的 IRS消息。 例如: 若呼叫请求为电路 域网络中的 A局经 B局发送到 MGCF的, A局从主叫终端发起的呼叫 请求中得知了主叫用户标识,但却由于 A局与 B局之间的协议消息不支 持携带主叫用户标识, 而使得 A局无法将主叫用户标识发送给 B局, 则 B局收到 IDR消息后, 由于无法从 A局获取到主叫用户标识, 而只能向 MGCF返回不携带主叫用户标识的 IRS消息。
步骤 506: MGCF将 IRS 消息中的主叫用户标识携带在呼叫请求 ( INVITE )消息中通过 S-CSCF发送给 IMS网络中的 AS ,转至步骤 408。
步骤 507: MGCF将自身保存的默认主叫用户标识携带在呼叫请求 ( INVITE ) 消息中通过 S-CSCF发送给 IMS网络的 AS。
MGCF可以为所有的呼叫设置相同的默认主叫用户标识, 也可以根 据每次呼叫的相关信息确定, 如: 根据主叫用户所在的网络、 本次呼叫 占用电路的信息、本次呼叫电路所在的中继电路信息或 MGCF的信令点 编码信息等设置默认标识, 例如: 本实施例中, MGCF可以使用缺省的 电话统一资源标识符(TEL URI ): tel: +0000-23作为本次呼叫的主叫用 户标识, 其中, 0000代表该主叫用户标识为 MGCF提供的缺省标识, 23为本次呼叫采用的中继电路号码; 或者, MGCF使用一个默认的 SIP URI: DefaultIdCircuit23 @ MGCF.com作为本次呼叫的主叫用户标识, 其中, Circuit23表示本次呼叫占用的电路号为 23。
步骤 508: IMS 网络中的 AS收到该呼叫请求消息, 根据该消息中 的主叫用户标识进行 MCID业务处理。
在实际应用中, 在步骤 502中 MGCF检测到 IAM消息未携带主叫 用户标识时, 也可直接将默认的主叫用户标识携带在呼叫请求消息中发
送给 S-CSCF, 而不进行向电路域网络发送 IDR消息以获取主叫用户标 识的步骤。
图 6为本发明实施例提供的实现 OIP业务的消息流程时序图, 如图 6所示, 其具体步骤如下:
步骤 601: 电路域网络中的用户发起呼叫请求, 呼叫 IMS网络中的 用户, 电路域网络通过 ISUP协议中的 IAM消息发送呼叫请求到和 IMS 网络互通的 MGCF, 该 IAM消息中未携带主叫用户标识。
步骤 602: MGCF收到 IAM消息, 检测到该消息未携带主叫用户标 识。
步骤 603: MGCF 向电路域网络发送信息请求(INR ) 消息, 以请 求提供主叫用户标识。
步骤 604: 电路域网络收到 INR消息, 向 MGCF返回信息( INF ) 消息。
步骤 605: MGCF收到该 INF消息后, 判断该消息是否携带主叫用 户标识, 若是, 执行步骤 606; 否则, 执行步骤 607。
步骤 606: MGCF将 INF 消息中的主叫用户标识携带在呼叫请求 ( INVITE )消息中通过 S-CSCF发送给 IMS网络中的 AS,转至步骤 608。
步骤 607: MGCF将自身保存的默认主叫用户标识携带在呼叫请求 ( INVITE ) 消息中通过 S-CSCF发送给 IMS网络的 AS。
步骤 608: IMS 网络中的 AS收到该呼叫请求消息, 根据该消息中 的主叫用户标识进行 OIP业务处理。
在实际应用中, 在步骤 602中 MGCF检测到 IAM消息未携带主叫 用户标识时, 也可直接将默认的主叫用户标识携带在呼叫请求消息中发 送给 S-CSCF, 而不进行向电路域网络发送 INR消息以获取主叫用户标 识的步骤。
图 7为本发明实施例提供的实现 TIP业务的消息流程时序图, 如图 7所示, 其具体步骤如下:
步骤 701: IMS 网络中的用户发起呼叫请求, 呼叫电路域网络中的 用户, IMS 网络发送呼叫请求 ( INVITE ) 消息到和电路域网络互通的 MGCF。
步骤 702: MGCF收到该呼叫请求消息, 向电路域网络发送 IAM消 该 IAM消息可能携带请求提供被叫用户标识的指示。
步骤 703: 电路域网络收到 IAM消息, 向 MGCF返回应答( ANM ) 消息。
步骤 704: MGCF收到该 ANM消息, 检测到该消息未携带被叫用 户标识。
步骤 705: MGCF将自身保存的默认被叫用户标识携带在 200响应 ( OK ) 消息中通过 S-CSCF发送给 IMS网络的 AS。
步骤 706: IMS网络的 AS收到 200响应消息, 根据该消息中的被 叫用户标识进行 TIP业务处理。
以上所述仅为本发明的过程及方法实施例, 并不用以限制本发明, 凡在本发明的精神和原则之内所做的任何修改、 等同替换、 改进等, 均 应包含在本发明的保护范围之内。
Claims
1、 一种模拟业务实现方法, 其特征在于, 包括:
互通控制单元检测到来自电路域网络的呼叫信令消息中未携带电 路域网络用户标识, 获取该电路域网络用户标识, 并将获取到的用户标 识发送给 IP多媒体子系统 IMS网络, IMS网络根据所述用户标识进行 公共交换电话网 PSTN/综合业务数字网 ISDN模拟业务处理。
2、 如权利要求 1 所述的方法, 其特征在于, 所述互通控制单元获 取电路域网络用户标识包括: 互通控制单元从电路域网络获取电路域网 络用户标识。
3、 如权利要求 1 所述的方法, 其特征在于, 互通控制单元预先配 置一个默认用户标识,
则所述互通控制单元获取电路域网络用户标识包括: 互通控制单元 将所述默认用户标识作为获取到的电路域网络用户标识。
4、 如权利要求 3所述的方法, 其特征在于, 所述默认用户标识为: 本次呼叫中电路域网络用户所在的网络信息、 本次呼叫所占用的电路信 息、 本次呼叫所在的中继群信息、 本次呼叫中电路域网络用户所在局点 的信令点编码信息、 互通控制单元任意设置的标识信息中的一种或任意 组合。
5、 如权利要求 3 所述的方法, 其特征在于, 所述互通控制单元将 获取到的用户标识发送给 IMS网络包括: 时在该消息中携带指示该用户标识为默认用户标识的指示信息, 将该 SIP消息发送给 IMS网络。
6、 如权利要求 5 所述的方法, 其特征在于, 所述互通控制单元在
SIP消息中携带指示该用户标识为默认用户标识的指示信息为: 互通控制单元在 SIP消息的私有头域中增加 "默认" 指示; 或者, 互通控制单元在 SIP消息的用户标识头域中增加 "默认" 指 示;
或者, 互通控制单元在 SIP消息中新增一个专门用于指示该用户标 识为默认用户标识的头域。
7、 如权利要求 1所述的方法, 其特征在于, 所述 PSTN/ISDN模拟 业务为: 恶意呼叫识别 MCID业务或发端标识呈现 OIP业务,
所述获取用户标识包括: 互通控制单元向电路域网络发送请求主叫 用户标识消息, 电路域网络收到该消息后, 向互通控制单元返回主叫用 户标识。
8、 如权利要求 7 所述的方法, 其特征在于, 所述互通控制单元向 电路域网络发送请求主叫用户标识消息之后进一步包括: 互通控制单元 未收到电路域网络返回的主叫用户标识, 则将默认用户标识作为当前主 叫用户标识。
9、 如权利要求 7 所述的方法, 其特征在于, 所述互通控制单元将 获取到的用户标识发送给 IMS网络为: 互通控制单元通过 SIP请求消息 将主叫用户标识发送给 IMS网络。
10、 如权利要求 1所述的方法, 其特征在于, 所述 PSTN/ISDN模 拟业务为终端标识呈现 TIP业务,
所述互通控制单元将获取到的用户标识发送给 IMS网络为:互通控 制单元通过 SIP响应消息将被叫用户标识发送给 IMS网络。
11、 一种模拟业务实现系统, 其特征在于, 包括: 电路域网络、 互 通控制单元和 IMS网络, 其中:
电路域网络, 用于向互通控制单元发送呼叫信令消息;
互通控制单元, 用于在检测到电路域网络发来的呼叫信令消息未携 带电路域网络用户标识后, 将获取到的电路域网络用户标识发送给 IMS 网络;
IMS网络, 用于根据互通控制单元发来的电路域网络用户标识, 进 行 PSTN/ISDN模拟业务处理。
12、 如权利要求 11 所述的系统, 其特征在于, 所述电路域网络进 一步用于, 收到互通控制单元发来的请求用户标识消息, 将用户标识发 送给互通控制单元。
13、 如权利要求 11 所述的系统, 其特征在于, 所述互通控制单元 包括: 默认用户标识存储模块和用户标识获取模块, 其中:
默认用户标识存储模块, 用于存储默认的电路域网络用户标识; 用户标识获取模块, 用于在检测到电路域网络发来的呼叫信令消息 未携电路域网络用户标识时, 将从默认用户标识存储模块读取的用户标 识携带在 SIP消息中发送给 IMS网络。
14、 如权利要求 11 所述的系统, 其特征在于, 所述互通控制单元 包括: 用户标识检测模块和用户标识获取模块, 其中:
用户标识检测模块, 用于在检测到电路域网络发来的呼叫信令消息 未携带电路域网络用户标识时, 向用户标识获取模块发送获取指示; 用户标识获取模块, 用于根据用户标识检测模块发来的获取指示, 向电路域网络发送请求用户标识消息, 将电路域网络发来的用户标识携 带在 SIP消息中发送给 IMS网络。
15、 如权利要求 11 所述的系统, 其特征在于, 所述互通控制单元 为媒体网关控制单元 MGCF或互通边界控制单元 IBCF。
16、 一种互通控制单元, 其特征在于, 包括: 默认用户标识存储模 块和用户标识获取模块, 其中:
默认用户标识存储模块, 用于存储默认的电路域网络用户标识; 用户标识获取模块, 用于在检测到电路域网络发来的呼叫信令消息 未携电路域网络用户标识时, 将从默认用户标识存储模块读取的用户标 识携带在 SIP消息中发送给 IMS网络。
17、 一种互通控制单元, 其特征在于, 包括: 用户标识检测模块和 用户标识获取模块, 其中:
用户标识检测模块, 用于接收电路域网络发来的呼叫信令消息, 在 检测到该消息中未携带电路域网络用户标识时, 向用户标识获耳 ^莫块发 送获取指示;
用户标识获取模块, 用于根据用户标识检测模块发来的获取指示, 向电路域网络发送请求用户标识消息, 将电路域网络发来的用户标识携 带在 SIP消息中发送给 IMS网络。
18、 如权利要求 17 所述的互通控制单元, 其特征在于, 进一步包 括: 默认用户标识存储模块, 用于存储默认电路域网络用户标识;
且所述用户标识获取模块在未收到电路域网络发来的用户标识后, 将从默认用户标识存储模块获取的电路域网络用户标识携带 SIP消息中 发送给 IMS网络。
19、 如权利要求 17 所述的互通控制单元, 其特征在于, 所述互通 控制单元为媒体网关控制单元 MGCF或互通边界控制单元 IBCF。
20、一种 IMS网络和电路域网络互通实现方法,其特征在于, 包括: 互通控制单元检测到来自电路域网络的呼叫信令消息中未携带电 路域网络用户标识, 获取该电路域网络用户标识, 并将获取到的用户标 识发送给 IP多媒体子系统 IMS网络。
21、如权利要求 20所述的方法, 其特征在于, 所述互通控制单元为 媒体网关控制单元 MGCF或互通边界控制单元 IBCF。
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| EP07846131.6A EP2068517B1 (en) | 2006-12-30 | 2007-12-21 | Method and system for implementing simulative service, method for implementing interworking, and unit for controlling interworking |
| US12/398,644 US9055083B2 (en) | 2006-12-30 | 2009-03-05 | Interworking method and interworking control unit, method and system for implementing simulation services |
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN200610172793.0 | 2006-12-30 | ||
| CN200610172793.0A CN100550949C (zh) | 2006-12-30 | 2006-12-30 | 模拟业务实现方法、系统及互通控制单元 |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| US12/398,644 Continuation US9055083B2 (en) | 2006-12-30 | 2009-03-05 | Interworking method and interworking control unit, method and system for implementing simulation services |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| WO2008080342A1 true WO2008080342A1 (fr) | 2008-07-10 |
| WO2008080342A8 WO2008080342A8 (fr) | 2008-12-04 |
Family
ID=39160787
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2007/071305 Ceased WO2008080342A1 (fr) | 2006-12-30 | 2007-12-21 | Procédé et système pour mettre en application un service de simulation, procédé pour mettre en application l'interfonctionnement, et unité pour commander l'interfonctionnement |
Country Status (4)
| Country | Link |
|---|---|
| US (1) | US9055083B2 (zh) |
| EP (1) | EP2068517B1 (zh) |
| CN (1) | CN100550949C (zh) |
| WO (1) | WO2008080342A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119136269A (zh) * | 2024-11-11 | 2024-12-13 | 北京首信科技股份有限公司 | 一卡双号呼叫建立专载时ims域和ps域交互的方法及装置 |
Families Citing this family (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| EP2448351B1 (en) * | 2009-06-19 | 2019-04-10 | BlackBerry Limited | Type II Relay Node Initializataion Procedures. |
| JP5477056B2 (ja) * | 2010-03-04 | 2014-04-23 | ヤマハ株式会社 | 電子機器、および電子機器の動作設定方法 |
| EP2629475B1 (en) | 2012-02-16 | 2019-08-28 | BlackBerry Limited | Method and system for obtaining availability status for multiple sip users |
| CN103731898A (zh) * | 2012-10-12 | 2014-04-16 | 北京信威通信技术股份有限公司 | 一种路由sip呼叫请求的方法 |
| RU2753302C1 (ru) * | 2017-12-29 | 2021-08-12 | Телефонактиеболагет Лм Эрикссон (Пабл) | Способ, система и объект для сеанса передачи мультимедиа в инфраструктуре ims |
| CN111866772B (zh) * | 2019-04-25 | 2022-06-14 | 中国移动通信集团安徽有限公司 | 防止盗打电话的方法、装置、计算机设备及计算机存储介质 |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005039132A1 (en) * | 2003-10-17 | 2005-04-28 | Nokia Corporation | System, apparatus, and method for establishing circuit-switched communications via packet switched network signaling |
| CN1741633A (zh) * | 2004-08-27 | 2006-03-01 | 华为技术有限公司 | 实现电路域移动流媒体点播的系统及其方法 |
| CN1747470A (zh) * | 2004-09-07 | 2006-03-15 | 华为技术有限公司 | 分组域业务信号处理系统及其方法 |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20020110104A1 (en) * | 2001-02-13 | 2002-08-15 | Telefonaktiebolaget Lm Ericsson (Publ). | Hybrid media gateway control function providing circuit-switched access to a packet-switched radio telecommunications network |
| SE0202059D0 (sv) * | 2002-07-02 | 2002-07-02 | Ericsson Telefon Ab L M | Method and apparatus for routing a service request in a telecommunication system |
| GB0422275D0 (en) * | 2004-10-07 | 2004-11-10 | Nokia Corp | Callback services in a communication system |
| US20060092925A1 (en) * | 2004-10-29 | 2006-05-04 | Telefonaktiebolaget Lm Ericsson (Publ) | Roaming between circuit-switched and all-IP networks |
| CN100379316C (zh) | 2005-07-05 | 2008-04-02 | 华为技术有限公司 | 传统终端用户接入ims域的实现方法及系统 |
| CN100596124C (zh) | 2006-03-03 | 2010-03-24 | 华为技术有限公司 | 实现业务互通的方法及系统 |
| US7760712B2 (en) * | 2006-08-11 | 2010-07-20 | Research In Motion Limited | System and method for managing call continuity in IMS network environment |
-
2006
- 2006-12-30 CN CN200610172793.0A patent/CN100550949C/zh active Active
-
2007
- 2007-12-21 WO PCT/CN2007/071305 patent/WO2008080342A1/zh not_active Ceased
- 2007-12-21 EP EP07846131.6A patent/EP2068517B1/en active Active
-
2009
- 2009-03-05 US US12/398,644 patent/US9055083B2/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2005039132A1 (en) * | 2003-10-17 | 2005-04-28 | Nokia Corporation | System, apparatus, and method for establishing circuit-switched communications via packet switched network signaling |
| CN1741633A (zh) * | 2004-08-27 | 2006-03-01 | 华为技术有限公司 | 实现电路域移动流媒体点播的系统及其方法 |
| CN1747470A (zh) * | 2004-09-07 | 2006-03-15 | 华为技术有限公司 | 分组域业务信号处理系统及其方法 |
| WO2006026901A1 (en) | 2004-09-07 | 2006-03-16 | Huawei Technologies Co., Ltd. | The process system for the packet domain service signal and the method using the same |
Non-Patent Citations (2)
| Title |
|---|
| MARSIC B., BOROSA T., POCUCA S.: "IMS to PSTN/CS Interworking", IEEE TELECOMMUNICATION 2003 CONTEL 2003, vol. 2, 11 June 2003 (2003-06-11) - 13 June 2003 (2003-06-13), pages 701 - 704, XP010646977 * |
| See also references of EP2068517A4 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN119136269A (zh) * | 2024-11-11 | 2024-12-13 | 北京首信科技股份有限公司 | 一卡双号呼叫建立专载时ims域和ps域交互的方法及装置 |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2008080342A8 (fr) | 2008-12-04 |
| CN101136970A (zh) | 2008-03-05 |
| US9055083B2 (en) | 2015-06-09 |
| EP2068517A4 (en) | 2010-01-13 |
| EP2068517A1 (en) | 2009-06-10 |
| CN100550949C (zh) | 2009-10-14 |
| EP2068517B1 (en) | 2016-10-26 |
| US20100002682A1 (en) | 2010-01-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103763446B (zh) | 使用既有设备的ims网络接入 | |
| CN101569154B (zh) | 用于为非登记订户的gsm与ims之间的重叠 | |
| KR101548140B1 (ko) | 원격통신 네트워크에서 매체 속성들에 기초한 선택적 호 포워딩을 위한 방법 및 시스템 | |
| CN103975566B (zh) | 服务域选择服务指示符 | |
| EP2104305A1 (en) | Call service handling in an IMS-based system | |
| US20080270611A1 (en) | Method and Device for Providing Correlation Means in Hybrid Telecommunication Networks | |
| WO2008080342A1 (fr) | Procédé et système pour mettre en application un service de simulation, procédé pour mettre en application l'interfonctionnement, et unité pour commander l'interfonctionnement | |
| WO2007098706A1 (en) | A method for transmitting the service data and a packet terminal used in the method | |
| CN101212323B (zh) | Ims网络为群用户提供服务的方法和系统 | |
| CN102884858B (zh) | 用于使能来自ims中未登记ue的连接的设置的方法和装置 | |
| CN101009693B (zh) | 在分组网络中实现综合业务数字网业务的系统和方法 | |
| WO2007115455A1 (en) | A method device and system for the circuit switched domain terminals accessing packet network realizing packet service | |
| US20120195235A1 (en) | Method and apparatus for specifying a user's preferred spoken language for network communication services | |
| CN101437176B (zh) | 提供网际协议多媒体子系统业务的方法、系统及装置 | |
| CN102612827B (zh) | 用于路由选择具有第一和第二网络提供的服务的呼叫的方法和节点 | |
| CN101365240A (zh) | Ip多媒体子系统中的呼叫接续方法、装置和系统 | |
| US20150296078A1 (en) | Call identifying method and apparatus | |
| CN102143478B (zh) | 业务参数的处理方法及装置 | |
| CN101179458B (zh) | 一种实现多媒体信息的主叫呈现业务的方法 | |
| CN101448044B (zh) | 一种基于sip协议无串音播放彩铃音的方法 | |
| CN101222478A (zh) | 实现呼叫建立的方法、系统及装置 | |
| WO2008151538A1 (fr) | Procédé, dispositif et système pour réaliser un service d'interdiction d'appels | |
| CN101212522A (zh) | 关联会话的方法、装置及系统 | |
| CN101800948B (zh) | 实现呼叫转向业务的方法、装置和系统 | |
| CN101902437B (zh) | 在请求建立会话的过程中处理错误响应消息的方法及装置 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 07846131 Country of ref document: EP Kind code of ref document: A1 |
|
| REEP | Request for entry into the european phase |
Ref document number: 2007846131 Country of ref document: EP |
|
| WWE | Wipo information: entry into national phase |
Ref document number: 2007846131 Country of ref document: EP |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |