WO2011079709A1 - 会话处理方法及装置 - Google Patents
会话处理方法及装置 Download PDFInfo
- Publication number
- WO2011079709A1 WO2011079709A1 PCT/CN2010/079738 CN2010079738W WO2011079709A1 WO 2011079709 A1 WO2011079709 A1 WO 2011079709A1 CN 2010079738 W CN2010079738 W CN 2010079738W WO 2011079709 A1 WO2011079709 A1 WO 2011079709A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network
- session
- terminal
- message
- request message
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
Definitions
- the present invention claims the priority of the Chinese Patent Application entitled “Session Processing Method and Apparatus” filed on December 31, 2009, the Chinese Patent Office, Application No. 200910260762. 4, the entire contents of which are incorporated by reference. Combined in this application.
- the present invention relates to the field of communications technologies, and in particular, to a session processing method and apparatus.
- IMS IP Multimedia Subsystem, IP Multimedia Subsystem
- 3GPP Third Generation Partnership Project
- SCIM Service Capability Interaction Manager
- Service Broker does not need to modify existing services to realize the unified combination of services of different networks to form a new service package, enriching the user experience.
- the calling party and the called party are in different networks.
- the calling party is a CS (Circuit Switching) domain terminal
- the called party is an IMS domain terminal.
- the calling party wants to establish a session with the called party.
- the Broker receives the request message triggered by the CS domain core network and the request message triggered by the IMS domain core network (IMS Core), and the Service Broker associates the two request messages to establish a session between the calling party and the called party.
- IMS Core IMS domain core network
- the request messages triggered by different networks need to be associated through Service Broker, there will be more signaling interactions, which increases the network load.
- Embodiments of the present invention provide a session processing method and apparatus, which reduce signaling interactions for establishing sessions between different network terminals.
- An embodiment of the present invention provides a session processing method, which is configured to receive a request message sent by a terminal from a first network, where the request message is a session between a terminal requesting to establish a first network and a terminal of a second network, where the session is Assign a session ID;
- the embodiment of the present invention further provides a session processing apparatus, including:
- a session ID allocation unit configured to receive a request message sent by a terminal from the first network, where the request message is a session between the terminal that requests the establishment of the first network and the terminal of the second network, and allocates a session ID for the session;
- a sending unit configured to send the session ID to the first network, and deliver the session ID to a terminal of the second network by using the first network;
- a session establishing unit configured to receive a request message sent by a terminal from the second network, where the request message carries the session ID, and establish, according to the session ID, a terminal of the first network and the second network The session between the terminals.
- FIG. 1 is a schematic flowchart of a session processing method according to an embodiment of the present invention.
- FIG. 2 is a schematic structural diagram of a session processing apparatus according to an embodiment of the present invention.
- FIG. 3 is a schematic flowchart diagram of a session processing method according to an embodiment of the present invention.
- An embodiment of the present invention provides a session processing method and apparatus, by transmitting a session ID requested by a first network terminal to a terminal of a second network, so that a terminal of the second network sends a request message including the session ID, thereby implementing a session.
- the processing device no longer needs to associate request messages triggered by different networks, avoids more signaling interactions, and reduces network load.
- the session processing device may be specifically a Service Broker.
- an embodiment of the present invention provides a session processing method, including:
- the request message sent by the terminal from the first network is received, and the request message is a session between the terminal requesting the establishment of the first network and the terminal of the second network, and the session ID is assigned to the session.
- the execution subject of the method for session processing in the embodiment of the present invention may be a Service Broker.
- the terminal of the second network By transmitting the session ID requested by the first network terminal to the terminal of the second network, the terminal of the second network directly sends the request message including the session ID, so that the service broker no longer needs to associate the request message triggered by different networks, thereby avoiding More signaling interactions reduce network load.
- the first network may be a PSTN (Public Switched Telephone Network) or a GSM (Global System for Mobile Communications) network
- the second network may be an IMS network.
- the first network may be an IMS network and the second network may be a PSTN or a GSM network.
- the service broker receives a request message sent by the terminal of the first network, where the request message is a session between the terminal requesting the establishment of the first network and the second network terminal, and the service broker allocates a session ID for the session.
- the session ID can be generated according to some predetermined rule and is not restricted. Globally, each session has a unique session ID to distinguish between different sessions, and the same session corresponds to the same session ID.
- the Service Broker sends the session ID to the first network, and the session ID is transmitted to the terminal of the second network by using the first network
- the process may include The session ID is sent to the first network by using an ID delivery message, and the first network sends the session ID to the terminal of the second network by using the ID delivery message, and the session is extended in the ID delivery message.
- the service broker receives the request message sent by the terminal from the second network, where the request message carries the session ID, and the service broker obtains the corresponding session according to the session ID; and confirms that the session ID is the first network.
- the session initiated by the terminal the Service Broker establishes a session between the terminal of the first network and the terminal of the second network, so as to establish a session between terminals of different networks.
- the request message sent by the second network terminal is extended with a session ID parameter item, To carry the session ID.
- the first network is a PSTN or a GSM network
- the ID delivery message may be a CONNECT message of an INAP (Intelligent Network Application Protocol) or a CAP (CAMEL Application Part, which is an application part of CAMEL) protocol.
- the second network is an IMS network, and the request message sent by the terminal of the second network may be an INVITE message of a SIP (Session Initiation Protocol).
- the first network is an IMS network
- the first message is an INVITE message of the SIP protocol
- the second network is a PSTN network or a GSM network
- the request message sent by the terminal of the second network may be an IDP of the INAP protocol or the CAP protocol (Initial Detective) Point, initial detection point) message.
- the session ID parameter item is extended in the message of the first network and the second network to carry the session ID, and the capability of the standard INAP, CAP, and SIP protocols is extended, and no additional network is added. operating.
- the terminal of the second network sends a request message including the session ID, thereby The session processing device no longer needs to associate request messages triggered by different networks, avoiding more signaling interactions and reducing network load.
- An example provides a session processing apparatus, including:
- the session ID assigning unit 21 is configured to receive a request message sent by the terminal from the first network, where the request message is a session between the terminal that requests the establishment of the first network and the terminal of the second network, and allocates a session ID for the session;
- the sending unit 22 is configured to send the session ID to the first network, and transmit the session ID to the terminal of the second network by using the first network;
- a session establishing unit 23 configured to receive a request message sent by a terminal from the second network, where the request message carries the session ID, and establish a terminal of the first network according to the session ID A session with a terminal of the second network.
- the session processing apparatus of the embodiment of the present invention may be integrated with the Service Broker.
- the sending unit 22 is further configured to send a session ID to the first network by using an ID delivery message, where the first network sends the session ID to the second network by using the ID delivery message. Terminal.
- the session establishing unit is further configured to: according to the session ID, confirm that the session ID is a session initiated by a terminal of the first network, and establish a terminal of the first network and a terminal of the second network. Session between.
- the session processing apparatus of the embodiment of the present invention implements the extension of the standard INAP, CAP, and SIP protocol capabilities without adding additional network operations.
- the first network is a public switched telephone network PSTN or a global mobile communication system GSM network
- the ID delivery message is a CONNECT message of an intelligent network application protocol INAP or CAP protocol
- the second network is an IP multimedia sub-network.
- a system IMS network where the request message sent by the terminal of the second network is an IN VITE message of the session initiation protocol SIP;
- the first network is an IP multimedia subsystem IMS network
- the ID delivery message is an INVITE message of a session initiation protocol SIP
- the second network is a public switched telephone network PSTN or a global mobile communication system GSM network
- the request message sent by the terminal of the second network is an initial detection point IDP message of the intelligent network application protocol INAP or CAP protocol.
- the division of each functional module is merely an example. In actual applications, the foregoing function allocation may be performed according to requirements, such as configuration requirements of corresponding hardware or convenience of implementation of software.
- the internal structure of the session processing device is divided into different functional modules to complete all or part of the functions described above.
- the corresponding functional modules in this embodiment may be implemented by corresponding hardware, or may be executed by corresponding hardware.
- the sending unit 22 may be hardware having the foregoing functions, such as , a transmitter having the transmission capability, and His general-purpose transmitting device capable of performing the aforementioned functions may also be a general-purpose processor capable of executing a corresponding computer program to perform the aforementioned functions, or other hardware devices.
- FIG. 3 a schematic diagram of a scenario for applying a session processing method according to an embodiment of the present invention, where the first network is a GSM network, the applied protocol is a CAP protocol, and the calling terminal A is a GSM network terminal.
- the second network is an IMS network, the applied protocol is SIP, and the called terminal B is an IMS network terminal.
- the user of the calling terminal A subscribes to the VPN service, PPS service and PoC service.
- the user of the called terminal B subscribes to the VPN service.
- the signaling process of the calling terminal A calling the called terminal B is as follows:
- the MSC sends an IDP message to the Service Broker.
- the GSM network core network receives the request sent by the terminal A to the requesting terminal B for the PoC service call. After receiving the request, the GSM network core network triggers a request message to the Service Broker, such as the MSC (Mobile Switching Center).
- the IDP message is sent to the Service Broker, where the ID of the IDP (b, A) message is the long number of the calling terminal A, and b is the short number of the called terminal B.
- Service Broker generates a session ID.
- the Service Broker receives the IDP (b, A) message sent by the MSC. According to the long number of the calling terminal A in the IDP (b, A) message, the short number of the called terminal B, the Service Broker can know the calling terminal A and the nickname. A session is required between the terminals B, and the service broker generates a session ID that uniquely identifies the session, and identifies that the session to be established is a session between the calling terminal A and the called terminal B to distinguish the session between the other terminals.
- the Service Broker invokes the VPN service to obtain the long number of the called terminal B.
- the user of the calling terminal A subscribes to the VPN service, the Service Broker sends the IDP (b, A) message to the VPN server, and the VPN server sends the RRBE (Request Report BCSM Event, Request Report BCSM (Basic Call State Model) event.
- the message and the CON ( ⁇ , ⁇ ) message to the Service Broker the Service Broker obtains the long number of the called terminal B.
- Service Broker invokes the functions of the above messages in the VPN service, and will not be described here.
- the Service Broker invokes the PPS service to perform charging for the calling terminal A.
- the user of the calling terminal A subscribes to the PPS service, and the Service Broker sends an IDP (B, A) message to the PPS server.
- the PPS server determines the calling rate, converts the balance into the duration of the call, and sends the SCI (Subscription CAMEL Information, CAMEL subscription information). ), RRBE messages, and CON messages to Service Broker.
- SCI Subscribescription CAMEL Information, CAMEL subscription information).
- RRBE messages RRBE messages
- CON messages to Service Broker.
- the role of the above messages in the PPS service is invoked by Service Broker and will not be described here.
- the Service Broker fills in the session ID to the CONNECT message.
- the CONNECT message extension adds a session ID parameter item to carry the session ID.
- the Service Broker fills in the CONNECT message with the session ID generated by the session between the calling terminal A and the called terminal B, and identifies that the session to be established is the session between the calling terminal A and the called terminal B.
- the Service Broker needs to take an available number according to the number range of the IMS domain, such as R-IMS, and change the long number of the called terminal B to the number of the IMS domain, so that the MSC triggers.
- the request message can be connected to the IMS Core.
- the CAP protocol capability is extended by extending the session ID parameter item of the CONNECT message without adding additional signaling.
- the Service Broker sends a CONNECT message carrying the session ID to the MSC.
- the Service Broker sends a CON (R-IMS, A, Session ID) message to the MSC.
- the CON message carries the session ID and the available number R-IMS of the called terminal B in the IMS domain.
- the MSC routes the CON (R-IMS, A, Session ID) message to the IMS Core.
- the MSC routes CONK R-IMS, A, session ID according to the number of the called terminal B in the IMS domain R-IMS. Message to IMS Core.
- the IMS Core sends an INVITE message carrying the session ID to the Service Broker.
- the IMS Core receives a CON (R-IMS, A, Session ID) message, and learns that the session corresponding to the session ID is a session between the calling terminal A and the called terminal B, and sends an IN VITE message carrying the session ID to the Service. Broker.
- CON R-IMS, A, Session ID
- the protocol of the IMS network is different from the protocol of the GSM network, and the CONNECT message of the GSM network needs to be converted into the INVITE message of the IMS network.
- the INVITE message can also be extended to increase the session ID parameter item, carrying the session ID. It can be seen that the SIP ID capability is extended by expanding the session ID parameter item without adding additional signaling.
- Service Broker obtains the session ID.
- the Service Broker receives the INVITE message carrying the session ID and obtains the session ID. Based on the session I D carried in the I N VITE message, the service broker learns that the session corresponding to the session I D is the session between the calling terminal A and the called terminal B, and obtains the long number of the called terminal B.
- the Service Broker can obtain the corresponding session through the session ID, so that the Service Broker no longer needs to associate the request messages triggered by different networks, avoiding more signaling interactions and reducing the network load.
- the Service Broker invokes the PoC service.
- the Service Broker sends an INVITE message to the PoC server according to the long number of the called terminal B, requesting the intercom service.
- the PoC server sends an INVITE message to the Service Broker, and the Service Broker routes the INVITE message to the IMS Core.
- the called terminal B answers, the IMS Core sends a 200 OK to the Service Broker, and the Service Broker forwards the 200 OK to the PoC server.
- the PoC server sends 200 OK to the Service Broker, and the Service Broker forwards the 200 OK to the IMS Core.
- the Service Broker generates an Answer event, and sends an ERB (ANS) message to the PPS server, and the ERB is an Event Report BCSM, a BCSM event report, which corresponds to the foregoing step 34.
- ERB ANS
- the RRBE message informs the PPS system that billing begins.
- the PPS system sends an AC (Apply Charging) message, an RRBE message, and a CONTINUE message to the Service Broker, and the PPS system starts charging.
- the IMS Core sends an ii!ACK (Acknowledge) message to the Service Broker, and the Service Broker forwards the ACK message to the PoC server. And Service Broker forwards the ACK message from the PoC server to the IMS Core.
- ii!ACK Acknowledge
- Steps 310-314 are specific processes for the Service Broker to invoke the PoC service, and are not described here.
- the embodiment of the present invention provides a session processing method, which is also applicable to the first network being an IMS network, the application protocol is a SIP protocol, the calling terminal A is an IMS network terminal, the second network is a GSM network, and the applied protocol is a CAP protocol.
- the signaling procedure of the calling terminal A calling the called terminal B can be understood by referring to the above specific implementation manner.
- step 35 the Service Broker fills in the session ID in the INVITE message; in step 36, the Service Broker carries the session ID through the INVITE message; in step 39, the Service Broker receives the IDP message carrying the session ID.
- Service Broker can obtain the corresponding session through the session ID, so Service Broker no longer needs to associate request messages triggered by different networks, avoiding more signaling interactions and reducing network load.
- the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Telephonic Communication Services (AREA)
Description
会话处理方法及装置 本申请要求于 2009 年 12 月 31 日提交中国专利局、 申请号为 200910260762. 4 , 发明名称为 "会话处理方法及装置" 的中国专利申请的优 先权, 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及通信技术领域, 尤其涉及一种会话处理方法及装置。
背景技术
IMS ( IP Multimedia Subsystem, IP多媒体子***)作为下一代电信网 络体系架构,是一种多业务的应用架构。 为了有效控制和处理 IMS中存在的多 业务交互问题, 3GPP ( Third Generation Partnership Project, 第三代合作 伙伴计划 )在 IMS体系中引入 SCIM ( Service Capability interaction Manager, 业务能力交互管理) 的功能实体, 该功能实体也被形象的称为业务经纪人 ( Service Broker ) 。
Service Broker通过增加新的交互逻辑, 无需对现有业务修改, 实现将不 同网络的业务统一组合形成一个新的业务包, 丰富用户的体验。
如主叫方、 被叫方处于不同的网络中, 例如主叫方是 CS ( Circuit Switching , 电路交换)域终端, 被叫方是 IMS域终端, 主叫方希望与被叫方 建立会话, Service Broker接收到 CS域核心网触发的请求消息, 以及 IMS域核 心网( IMS Core )触发的请求消息, Service Broker将这两个请求消息关联起 来, 进而建立主叫方与被叫方之间的会话。 但是, 由于不同网络触发的请求 消息都需要通过 Service Broker关联起来, 则会存在较多的信令交互, 增大了 网络负荷。
发明内容 本发明的实施例提供了一种会话处理方法及装置, 实现减少建立不同网 络终端之间会话的信令交互。
本发明实施例提供了一种会话处理方法, 接收来自第一网络的终端发送 的请求消息, 所述请求消息为请求建立第一网络的终端与第二网络的终端之 间会话, 为所述会话分配会话 ID;
将所述会话 ID发送到所述第一网络, 通过所述第一网络将所述会话 ID传 递到所述第二网络的终端;
接收来自所述第二网络的终端发送的请求消息, 所述请求消息携带所述 会话 ID , 根据所述会话 ID , 建立所述第一网络的终端与所述第二网络的终端 之间的会话。
相应的, 本发明实施例还提供了一种会话处理装置, 包括:
会话 ID分配单元, 用于接收来自第一网络的终端发送的请求消息, 所述 请求消息为请求建立第一网络的终端与第二网络的终端之间会话, 为所述会 话分配会话 ID;
发送单元, 用于将所述会话 ID发送到所述第一网络, 通过所述第一网络 将所述会话 I D传递到所述第二网络的终端;
会话建立单元, 用于接收来自所述第二网络的终端发送的请求消息, 所 述请求消息携带所述会话 ID , 根据所述会话 ID , 建立所述第一网络的终端与 所述第二网络的终端之间的会话。
由上述本发明的实施例提供的技术方案可以看出, 通过将第一网络终端 请求的会话 ID传递给第二网络的终端, 使得第二网络的终端发送包含该会话 ID的请求消息, 从而使得会话处理装置不再需要关联不同网络触发的请求消 息, 避免了较多的信令交互, 减少了网络负荷。
附图说明 为了更清楚地说明本发明实施例的技术方案, 下面将对实施例描述中所 需要使用的附图作简单地介绍, 显而易见地, 下面描述中的附图仅仅是本发 明的一些实施例, 对于本领域普通技术人员来讲, 在不付出创造性劳动性的 前提下, 还可以根据这些附图获得其他的附图。
图 1为本发明实施例一种会话处理方法流程示意图;
图 2为本发明实施例一种会话处理装置结构示意图;
图 3为本发明实施例一种会话处理方法的流程示意图。
具体实施方式 下面将结合本发明实施例中的附图, 对本发明实施例中的技术方案进行 清楚、 完整地描述, 显然, 所描述的实施例仅仅是本发明一部分实施例, 而 不是全部的实施例。 基于本发明中的实施例, 本领域普通技术人员在没有做 出创造性劳动前提下所获得的所有其他实施例 , 都属于本发明保护的范围。
基于现有技术中, 由于不同网络触发的请求消息都需要通过会话处理装 置关联起来, 则会存在较多的信令交互, 增大了网络负荷的缺陷。 本发明的 实施例提供了一种会话处理方法及装置, 通过将第一网络终端请求的会话 ID 传递给第二网络的终端, 使得第二网络的终端发送包含该会话 I D的请求消息, 从而会话处理装置不再需要关联不同网络触发的请求消息, 避免了较多的信 令交互, 减少了网络负荷, 该会话处理装置可以具体为 Service Broker。
如图 1所示, 本发明实施例提供一种会话处理方法, 包括:
1 1、 接收来自第一网络的终端发送的请求消息, 所述请求消息为请求建 立第一网络的终端与第二网络的终端之间会话, 为所述会话分配会话 ID。
12、将所述会话 ID发送到所述第一网络,通过所述第一网络将所述会话 ID 传递到所述第二网络的终端。
13、 接收来自所述第二网络的终端发送的请求消息, 所述请求消息携带 所述会话 ID, 根据所述会话 ID, 建立所述第一网络的终端与所述第二网络的 终端之间的会话。
本发明实施例会话处理的方法的执行主体, 可以是 Service Broker。 通过 将第一网络终端请求的会话 ID传递给第二网络的终端, 使得第二网络的终端 直接发送包含该会话 ID的请求消息, 从而 Service Broker不再需要关联不同网 络触发的请求消息, 避免了较多的信令交互, 减少了网络负荷。
可选的, 第一网络可以为 PSTN ( Public Switched Telephone Network, 公共交换电话网络)或 GSM ( Global System for Mobile Communications, 全球移动通讯***) 网络, 第二网络可以为 IMS网络。
或者, 第一网络可以为 IMS网络, 第二网络可以为 PSTN或 GSM网络。 步骤 1 1中, 如 Service Broker接收第一网络的终端发送的请求消息, 该请 求消息为请求建立第一网络的终端与第二网络终端之间会话, Service Broker 为所述会话分配会话 ID。 会话 ID可以是按照某种预定规则生成的, 不受限制。 对于全局而言, 每个会话都有一个唯一的会话 ID以用于区分不同的会话, 而 相同的会话对应的会话 ID是相同的。
基于步骤 12中, Service Broker将所述会话 ID发送到所述第一网络, 通过 所述第一网络将所述会话 ID传递到所述第二网络的终端, 可选的: 该过程可 以包括将所述会话 ID通过 ID传递消息发送到所述第一网络, 所述第一网络通 过所述 ID传递消息将所述会话 ID发送到所述第二网络的终端, 该 ID传递消息 中扩展有会话 ID参数项, 以携带所述会话 ID。
步骤 13中, 如 Service Broker接收来自第二网络的终端发送的请求消息, 所述请求消息携带所述会话 ID, Service Broker根据所述会话 ID获得对应的会 话; 确认该会话 ID为第一网络的终端发起的会话, 则 Service Broker建立所述 第一网络的终端与第二网络的终端之间的会话, 实现将不同网络的终端之间 建立会话。 可选的, 第二网络终端发送的请求消息中扩展有会话 ID参数项,
以携带所述会话 ID。
第一网络为 PSTN或 GSM网络, 则 ID传递消息可以为 INAP ( Intelligent Network Application Protocol,智能网应用协议)或 CAP ( CAMEL Application Part, 是 CAMEL的应用部分)协议的 CONNECT消息。 第二网络为 IMS网络, 则第二网络的终端发送的请求消息可以为 SIP ( Session Initiation Protocol, 会话初始协议) 的 INVITE消息。
或者, 第一网络为 IMS网络, 第一消息为 SIP协议的 INVITE消息, 第二网 络为 PSTN网络或 GSM网络, 第二网络的终端发送的请求消息可以为 INAP协 议或 CAP协议的 IDP ( Initial Detective Point, 初始检测点) 消息。
可见, 本发明实施例会话处理方法, 第一网络和第二网络的消息中扩展 有会话 ID参数项以携带所述会话 ID, 实现对标准 INAP、 CAP, SIP协议能力 的扩展, 没有增加额外网络操作。
由上述本发明的实施例提供的技术方案可以看出, 通过将第一网络终端 请求的会话 ID传递给第二网络的终端, 使得第二网络的终端发送包含该会话 ID的请求消息, 从而使得会话处理装置不再需要关联不同网络触发的请求消 息, 避免了较多的信令交互, 减少了网络负荷。
例提供一种会话处理装置, 包括:
会话 ID分配单元 21 , 用于接收来自第一网络的终端发送的请求消息, 所 述请求消息为请求建立第一网络的终端与第二网络的终端之间会话, 为所述 会话分配会话 ID;
发送单元 22, 用于将所述会话 ID发送到所述第一网络, 通过所述第一网 络将所述会话 ID传递到所述第二网络的终端;
会话建立单元 23, 用于接收来自所述第二网络的终端发送的请求消息, 所述请求消息携带所述会话 ID, 根据所述会话 ID, 建立所述第一网络的终端
与所述第二网络的终端之间的会话。
本发明实施例会话处理装置, 可以与 Service Broker设置为一体。
一个具体的例子, 上述发送单元 22进一步用于将会话 ID通过 ID传递消息 发送到所述第一网络, 所述第一网络通过所述 ID传递消息将所述会话 ID发送 到所述第二网络的终端。
一个具体的例子, 会话建立单元, 进一步用于根据所述会话 ID, 确认所 述会话 ID为第一网络的终端发起的会话, 建立所述第一网络的终端与所述第 二网络的终端之间的会话。
可见, 本发明实施例会话处理装置实现了对标准 INAP、 CAP, SIP协议 能力的扩展, 没有增加额外网络操作。
可选的, 所述第一网络为公共交换电话网络 PSTN或全球移动通讯*** GSM网络, 所述 ID传递消息为智能网应用协议 INAP或 CAP协议的 CONNECT 消息, 所述第二网络为 IP多媒体子*** IMS网络, 所述第二网络的终端发送的 请求消息为会话初始协议 S I P的 I N VITE消息;
或者, 所述第一网络为 IP多媒体子*** IMS网络, 所述 ID传递消息为会话 初始协议 SIP的 INVITE消息, 所述第二网络为公共交换电话网络 PSTN或全球 移动通讯*** GSM网络, 所述第二网络的终端发送的请求消息为智能网应用 协议 INAP或 CAP协议的初始检测点 IDP消息。 需要说明的是, 以上会话处理装置的实施方式中, 各功能模块的划分仅 是举例说明, 实际应用中可以根据需要, 比如相应硬件的配置要求或者软件 的实现的便利考虑, 而将上述功能分配由不同的功能模块完成, 即将所述的 会话处理装置的内部结构划分成不同的功能模块, 以完成以上描述的全部或 者部分功能。 而且实际应用中, 本实施例中的相应的功能模块可以是由相应 的硬件实现, 也可以由相应的硬件执行相应的软件完成, 例如, 发送单元 22, 可以为具有执行前述功能的硬件, 比如, 具有该发送能力的发送器, 以及其
他通用的能够执行前述功能的发送装置, 也可以是能够执行相应计算机程序 从而完成前述功能的一般处理器, 或者其他硬件设备。
由上述本发明的实施例提供的技术方案可以看出, 通过将第一网络终端 请求的会话 ID传递给第二网络的终端, 使得第二网络的终端发送包含该会话 ID的请求消息, 从而使得会话处理装置不再需要关联不同网络触发的请求消 息, 避免了较多的信令交互, 减少了网络负荷。 如图 3所示, 本发明实施例会话处理方法应用场景示意图, 其中, 第一网 络为 GSM网络, 应用的协议为 CAP协议, 主叫终端 A为 GSM网络终端。 第二 网络为 IMS网络, 应用的协议为 SIP协议, 被叫终端 B为 IMS网络终端。 主叫终 端 A的用户签约有 VPN业务, PPS业务和 PoC业务。 被叫终端 B的用户签约有 VPN业务。
主叫终端 A呼叫被叫终端 B的信令流程如下:
31、 MSC发送 IDP消息到 Service Broker。
GSM网络核心网接收终端 A发送到请求与终端 B进行 PoC业务通话的请 求, GSM网络核心网接收到该请求后, 触发一个请求消息到 Service Broker, 如 MSC ( Mobile Switching Center, 移动交换中心)发送 IDP消息到 Service Broker, 其中, IDP ( b,A )消息中 A为主叫终端 A的长号, 为 b为被叫终端 B的 短号。
32、 Service Broker生成一个会话 ID。
Service Broker收到 MSC发送的 IDP ( b,A )消息, 根据 IDP ( b,A )消息 中主叫终端 A的长号, 被叫终端 B的短号, Service Broker可以获知主叫终端 A 与被叫终端 B之间需要建立会话, Service Broker生成一个唯一识别该会话的 会话 ID, 标识要建立的会话是主叫终端 A与被叫终端 B之间的会话, 以区别于 其他终端间的会话。
33、 Service Broker调用 VPN 业务来取得被叫终端 B的长号。
主叫终端 A的用户签约有 VPN业务, Service Broker发送 IDP ( b,A ) 消息 到 VPN服务器, VPN服务器发送 RRBE ( Request Report BCSM Event, 请求 报告 BCSM( Basic call state model ,基本呼叫状态模型)事件)消息以及 CON ( Β,Α )消息到 Service Broker, Service Broker获得被叫终端 B的长号。 Service Broker调用 VPN 业务中的上述各消息的作用, 在此不作赘述。
图 3中, CONNECT消息简单表示为 CON。
34、 Service Broker调用 PPS业务来进行主叫终端 A的计费。
主叫终端 A的用户签约有 PPS业务, Service Broker发送 IDP ( B,A ) 消息 到 PPS服务器, PPS服务器确定主叫费率, 将余额折算成通话时长, 发送 SCI ( Subscription CAMEL Information , CAMEL签约信息) 、 RRBE消息以及 CON消息到 Service Broker。 Service Broker调用 PPS 业务中的上述各消息 的作用, 在此不作赘述。
35、 Service Broker填写会话 ID到 CONNECT消息。
CONNECT消息扩展增加有会话 ID参数项, 以携带会话 ID。 Service Broker将为主叫终端 A与被叫终端 B之间的会话生成的会话 ID填写到 CONNECT消息中,标识要建立的会话是主叫终端 A与被叫终端 B之间的会话。
由于被叫终端 B为 IMS域终端, Service Broker需要根据 IMS域的号码范围 取一个可用的号码, 如 R-IMS, 把被叫终端 B的长号修改成 IMS域的号码, 这 样, MSC的触发请求消息可以接续到 IMS Core。
可见, 通过扩展增加 CONNECT消息的会话 ID参数项, 对 CAP协议能力 进行扩展, 没有增加额外的信令。
36、 Service Broker发送携带会话 ID的 CONNECT消息到 MSC。
Service Broker发送 CON ( R-IMS, A, 会话 ID ) 消息到 MSC, CON消息 中携带会话 ID 、 被叫终端 B在 IMS域的可用号码 R-IMS 。
37、 MSC将 CON ( R-IMS, A, 会话 ID ) 消息路由到 IMS Core。
MSC根据被叫终端 B在 IMS域的号码 R-IMS路由 CONK R-IMS, A, 会话 ID )
消息到 IMS Core 。
38、 IMS Core发送携带会话 ID的 INVITE消息到 Service Broker。
IMS Core收到 CON ( R-IMS,A, 会话 ID ) 消息, 得知该会话 ID对应的会 话为主叫终端 A与被叫终端 B之间的会话, 发送携带会话 I D的 I N VITE消息到 Service Broker 。
这里, IMS网络的协议和 GSM网络的协议不同, 需要将 GSM网络的 CONNECT消息转换成 IMS网络的 INVITE消息。
INVITE消息也可以扩展增加会话 ID参数项, 携带会话 ID。 可见, 通过扩 展增加会话 ID参数项, 对 SIP协议能力进行扩展, 没有增加额外的信令。
39、 Service Broker获得会话 ID。
Service Broker收到携带会话 ID的 INVITE消息, 获得会话 ID。 Service Broker根据 I N VITE消息携带的会话 I D ,得知该会话 I D对应的会话为主叫终端 A 与被叫终端 B之间的会话, 获得被叫终端 B的长号。
可见, Service Broker通过会话 ID可以得到对应的会话, 从而 Service Broker不再需要关联不同网络触发的请求消息, 避免了较多的信令交互, 减 少了网络负荷。
310、 Service Broker调用 PoC业务。
Service Broker根据被叫终端 B的长号向 PoC服务器发送 INVITE消息,请 求对讲业务。 PoC服务器发送 INVITE消息到 Service Broker, Service Broker 路由 INVITE消息到 IMS Core。
31 1、 被叫终端 B应答, IMS Core发送 200 OK到 Service Broker, Service Broker转发 200 OK到 PoC服务器。
312、 PoC月良务器发送 200 OK到 Service Broker, Service Broker转发 200 OK到 IMS Core。
313、 Service Broker产生 Answer事件, 发送 ERB ( ANS )消息到 PPS服 务器, ERB即 Event Report BCSM, BCSM事件报告, 其对应前述步骤 34中
的 RRBE消息, 通知 PPS***计费开始。 PPS***向 Service Broker发送 AC ( Apply Charging, 计费处理响应) 消息, RRBE消息以及 CONTINUE消息, PPS***开始计费。
图 3中, CONTINUE消息简单表示为 CONT。
314、 IMS Core发 ii!ACK ( Acknowledge, 应答)消息到 Service Broker, Service Broker把 ACK消息转发到 PoC服务器。 以及 Service Broker把 PoC服 务器来的 ACK消息转发到 IMS Core。
步骤 310-314为 Service Broker调用 PoC 业务的具体过程, 在此不作赘 述。 本发明实施例提供会话处理方法,也适用于第一网络为 IMS网络,应用的 协议为 SIP协议, 主叫终端 A为 IMS网络终端, 第二网络为 GSM网络, 应用的 协议为 CAP协议, 被叫终端 B为 GSM网络终端的情况。 主叫终端 A呼叫被叫终 端 B的信令流程, 可以依据上述具体实施方式得以参考理解。
值得注意的是, 步骤 35中, Service Broker在 INVITE消息中填写会话 ID; 步骤 36中, Service Broker通过 INVITE消息携带会话 ID; 步骤 39中, Service Broker接收携带会话 ID的 IDP消息。 Service Broker通过会话 ID可以得到对应 的会话, 从而 Service Broker不再需要关联不同网络触发的请求消息, 避免了 较多的信令交互, 减少了网络负荷。
需要说明的是, 对于前述的各方法实施例, 为了简单描述, 故将其都表 述为一系列的动作组合, 但是本领域技术人员应该知悉, 本发明并不受所描 述的动作顺序的限制, 因为依据本发明, 某些步骤可以釆用其他顺序或者同 时进行。 其次, 本领域技术人员也应该知悉, 说明书中所描述的实施例均属 于优选实施例, 所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中, 对各个实施例的描述都各有侧重, 某个实施例中没有 详述的部分, 可以参见其他实施例的相关描述。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流 程, 是可以通过计算机程序来指令相关的硬件来完成, 所述的程序可存储于 一计算机可读取存储介质中, 该程序在执行时, 可包括如上述各方法的实施 例的流程。其中,所述的存储介质可为磁碟、光盘、只读存储记忆体( Read-Only Memory, ROM )或随机存储记忆体( Random Access Memory, RAM )等。
以上所述, 仅为本发明较佳的具体实施方式, 但本发明的保护范围并不 局限于此, 任何熟悉本技术领域的技术人员在本发明揭露的技术范围内, 可 轻易想到的变化或替换, 都应涵盖在本发明的保护范围之内。 因此, 本发明 的保护范围应该以权利要求的保护范围为准。
Claims
1、 一种会话处理方法, 其特征在于, 包括:
接收来自第一网络的终端发送的请求消息, 所述请求消息为请求建立第 一网络的终端与第二网络的终端之间会话, 为所述会话分配会话 I D;
将所述会话 ID发送到所述第一网络, 通过所述第一网络将所述会话 ID传 递到所述第二网络的终端;
接收来自所述第二网络的终端发送的请求消息, 所述请求消息携带所述 会话 ID, 根据所述会话 ID, 建立所述第一网络的终端与所述第二网络的终端 之间的会话。
2、 根据权利要求 1所述的处理方法, 其特征在于, 将所述会话 ID发送到 所述第一网络, 通过所述第一网络将所述会话 ID传递到所述第二网络的终端, 包括:
将所述会话 ID通过 ID传递消息发送到所述第一网络, 所述第一网络通过 所述 ID传递消息将所述会话 ID发送到所述第二网络的终端。
3、 根据权利要求 2所述的处理方法, 其特征在于, 所述会话 ID携带在所 述 ID传递消息和第二网络的终端发送的请求消息的会话 ID参数项中。
4、 根据权利要求 2或 3所述的会话处理方法, 其特征在于, 所述第一网络 为公共交换电话网络 PSTN或全球移动通讯*** GSM网络, 所述 ID传递消息 为智能网应用协议 INAP或 CAP协议的 CONNECT消息, 所述第二网络为 IP多 媒体子*** IMS网络, 所述第二网络的终端发送的请求消息为会话初始协议 SIP的 INVITE消息;
或者, 所述第一网络为 IP多媒体子*** IMS网络, 所述 ID传递消息为会话 初始协议 SIP的 INVITE消息, 所述第二网络为公共交换电话网络 PSTN或全球 移动通讯*** GSM网络, 所述第二网络的终端发送的请求消息为智能网应用 协议 INAP或 CAP协议的初始检测点 IDP消息。
5、 根据权利要求 1所述的会话处理方法, 其特征在于, 所述根据所述会 话 ID, 建立所述第一网络的终端与所述第二网络的终端之间的会话, 包括: 根据所述会话 ID, 确认所述会话 ID为第一网络的终端发起的会话, 建立 所述第一网络的终端与所述第二网络的终端之间的会话。
6、 一种会话处理装置, 其特征在于, 包括:
会话 ID分配单元, 用于接收来自第一网络的终端发送的请求消息, 所述 请求消息为请求建立第一网络的终端与第二网络的终端之间会话, 为所述会 话分配会话 ID;
发送单元, 用于将所述会话 ID发送到所述第一网络, 通过所述第一网络 将所述会话 I D传递到所述第二网络的终端;
会话建立单元, 用于接收来自所述第二网络的终端发送的请求消息, 所 述请求消息携带所述会话 ID, 根据所述会话 ID, 建立所述第一网络的终端与 所述第二网络的终端之间的会话。
7、 根据权利要求 6所述的会话处理装置, 其特征在于, 所述发送单元, 进一步用于将会话 ID通过 ID传递消息发送到所述第一网络, 所述第一网络通 过所述 ID传递消息将所述会话 ID发送到所述第二网络的终端。
8、 根据权利要求 6或 7所述的会话处理装置, 其特征在于, 所述第一网络 为公共交换电话网络 PSTN或全球移动通讯*** GSM网络, 所述 ID传递消息 为智能网应用协议 INAP或 CAP协议的 CONNECT消息, 所述第二网络为 IP多 媒体子*** IMS网络, 所述第二网络的终端发送的请求消息为会话初始协议 SIP的 INVITE消息;
或者, 所述第一网络为 IP多媒体子*** IMS网络, 所述 ID传递消息为会话 初始协议 SIP的 INVITE消息, 所述第二网络为公共交换电话网络 PSTN或全球 移动通讯*** GSM网络, 所述第二网络的终端发送的请求消息为智能网应用 协议 INAP或 CAP协议的初始检测点 IDP消息。
9、 根据权利要求 6所述的会话处理装置, 其特征在于, 会话建立单元, 进一步用于根据所述会话 ID, 确认所述会话 ID为第一网络的终端发起的会话, 建立所述第一网络的终端与所述第二网络的终端之间的会话。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910260762.4 | 2009-12-31 | ||
CN2009102607624A CN102118369A (zh) | 2009-12-31 | 2009-12-31 | 会话处理方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2011079709A1 true WO2011079709A1 (zh) | 2011-07-07 |
Family
ID=44216963
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2010/079738 WO2011079709A1 (zh) | 2009-12-31 | 2010-12-14 | 会话处理方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN102118369A (zh) |
WO (1) | WO2011079709A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3232611B1 (en) * | 2014-12-31 | 2018-09-19 | Huawei Technologies Co., Ltd. | Method, device and system for performing bidirectional forwarding detection on an aggregated link |
CN107317786B (zh) * | 2016-04-26 | 2020-11-06 | ***通信有限公司研究院 | 一种转发会话初始协议消息的方法、装置及网元 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1889542A (zh) * | 2005-09-01 | 2007-01-03 | 华为技术有限公司 | 网络间呼叫接续方法 |
WO2008076201A1 (en) * | 2006-12-14 | 2008-06-26 | Nortel Networks Limited | Method and apparatus for exchanging routing information and the establishment of connectivity across multiple network areas |
CN101325762A (zh) * | 2007-06-12 | 2008-12-17 | 中兴通讯股份有限公司 | 一种双模终端在双待机状态时建立补充业务的实现方法 |
CN101325734A (zh) * | 2007-06-14 | 2008-12-17 | 中兴通讯股份有限公司 | 一种ims集中控制业务中终呼的实现方法 |
-
2009
- 2009-12-31 CN CN2009102607624A patent/CN102118369A/zh active Pending
-
2010
- 2010-12-14 WO PCT/CN2010/079738 patent/WO2011079709A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN1889542A (zh) * | 2005-09-01 | 2007-01-03 | 华为技术有限公司 | 网络间呼叫接续方法 |
WO2008076201A1 (en) * | 2006-12-14 | 2008-06-26 | Nortel Networks Limited | Method and apparatus for exchanging routing information and the establishment of connectivity across multiple network areas |
CN101325762A (zh) * | 2007-06-12 | 2008-12-17 | 中兴通讯股份有限公司 | 一种双模终端在双待机状态时建立补充业务的实现方法 |
CN101325734A (zh) * | 2007-06-14 | 2008-12-17 | 中兴通讯股份有限公司 | 一种ims集中控制业务中终呼的实现方法 |
Also Published As
Publication number | Publication date |
---|---|
CN102118369A (zh) | 2011-07-06 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1744569B1 (en) | Method and system of realizing communication | |
US10313847B2 (en) | Session establishment, maintenance, and termination by end device based on SMS messaging | |
US9686709B2 (en) | Method, apparatus and system for guaranteeing QoS of communication service in NAT scenario | |
US20090086719A1 (en) | Dynamic initiation of I1-ps signaling in IMS centralized services | |
WO2009152699A1 (zh) | Sip终端及其上报状态的方法、***以及sip服务器 | |
WO2008025257A1 (fr) | Procédé d'intercommunication et système de communication entre différents réseaux | |
RU2510584C2 (ru) | Способ, устройство и система для реализации сервиса оверрайда при экстренном вызове | |
JP5437435B2 (ja) | 呼制御方法、回線交換ドメインアダプタ、および端末装置 | |
CN103647764A (zh) | 长期演进***语音业务实现方法和单芯片终端 | |
US8036211B1 (en) | Legacy user proxy call session control function | |
WO2009113947A1 (en) | Using a hash value as a pointer to an application class in a communications device | |
CN111031528B (zh) | 一种专用网络的连接建立方法和装置 | |
US11418635B2 (en) | Method of dynamic selection, by a caller, from a plurality of terminals of a callee | |
WO2011079709A1 (zh) | 会话处理方法及装置 | |
WO2008110110A1 (fr) | Procédé et système de fourniture de service de sous-système multimédia ip | |
WO2012052707A1 (en) | Data communication | |
EP1953990A1 (en) | A method, system and device for realizing call waiting in packet domain | |
WO2022001972A1 (zh) | Dns请求的解析方法、通信装置及通信*** | |
KR100867447B1 (ko) | 데이터 통신 네트워크를 통해 음성 통화 서비스를 제공하는방법 및 그 장치 | |
WO2009056041A1 (fr) | Procédé, système et dispositif de transmission d'informations d'attribut de frais | |
WO2008119278A1 (fr) | Procédé, terminal et dispositif réseau pour le changement d'état de domaine à commutation de paquets | |
WO2008049371A1 (fr) | Procédé et système pour transférer un événement de service | |
KR100727067B1 (ko) | Sip 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템 | |
WO2009121281A1 (zh) | 一种ims网络中业务调用的方法、***和装置 | |
KR100706339B1 (ko) | Sip 기반의 무선 패킷 교환망 시스템에서의 타망 연동방법 및 그 시스템 |
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: 10840498 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 10840498 Country of ref document: EP Kind code of ref document: A1 |