WO2007082454A1 - Procédé, système et terminal de communication pour la mise en oeuvre de communication à composants de multi-applications basée sur le protocole d'ouverture de session - Google Patents
Procédé, système et terminal de communication pour la mise en oeuvre de communication à composants de multi-applications basée sur le protocole d'ouverture de session Download PDFInfo
- Publication number
- WO2007082454A1 WO2007082454A1 PCT/CN2006/003555 CN2006003555W WO2007082454A1 WO 2007082454 A1 WO2007082454 A1 WO 2007082454A1 CN 2006003555 W CN2006003555 W CN 2006003555W WO 2007082454 A1 WO2007082454 A1 WO 2007082454A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application component
- communication
- application
- identifier
- sip
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
Definitions
- the Session Initiation Protocol is an application layer control protocol proposed and supported by the IETF for multimedia communication over an IP network for creating, modifying, and terminating sessions attended by one or more participants.
- the SIP protocol draws on protocols such as HTTP and SMTP, supports functions such as proxying, redirection, and registration of users, and supports user movement.
- SIP Voice over IP
- RFC3265, RFC3903, RFC3428, etc. define different SIP request message types such as SUBSCRIBE, NOTIFY, PUBLISH, MESSAGE, etc., such as SIMPLE (SIP Instant Messaging and Presence Leveraging Extensions) protocol defined by IETF, including IM and Presence applications; Push, XCAP, etc. are used.
- SIMPLE SIP Instant Messaging and Presence Leveraging Extensions
- IETF including IM and Presence applications
- Push, XCAP, etc. are used.
- SIP protocol and extended messages This raises the need for interaction between different types of application components.
- FIG. 1 An architecture for implementing a SIP protocol stack in the prior art is shown in FIG. 1.
- This architecture defines four types: user agent, session, transmission, and service, where the service is an abstract class, corresponding to different services to define corresponding Service class; an application corresponds to a user agent, can establish and manage multiple SIP sessions, and each session can also establish and manage multiple transactions, and each session and transaction corresponds to different services. (Service). From this It is known that for different applications, you must implement your own user agent. Each user agent manages its own sessions and transactions, as well as its own resources, including system resources and network resources.
- This architecture mainly utilizes the concept of polymorphism in object-oriented programming, which limits the implementation of this implementation to object-oriented languages such as C++ and JAVA.
- the technical problem to be solved by the present invention is to provide a method, a system and a communication terminal for implementing communication of multiple application components based on the SIP protocol, which realize that different types of application components share the same SIP protocol stack, and are easy to implement.
- An embodiment of the present invention provides a method for implementing communication of multiple application components based on a SIP protocol, including:
- the first communication end assigns the header field of the request message to the application component identifier, and sends the clear request to the second communication end;
- the second communication end responds to the request, obtains an application component identifier therein, and invokes a corresponding application component according to the application component identifier to perform processing of a corresponding SIP message.
- the embodiment of the invention provides a communication terminal, including:
- SIP protocol stack used to establish communication for sharing by different types of application components
- a storage module configured to be connected to the protocol stack, configured to store the plurality of application component identifiers; the sending module, carrying the application component identifier in the request message, and sending the identifier to the peer end;
- the processing module calls the application component according to the received application component identifier to process the corresponding SIP message.
- An embodiment of the present invention further provides a system for implementing multi-application component communication based on a SIP protocol, including a first communication terminal, a second communication terminal, and the first communication terminal and the second communication.
- the terminal is connected through a communication link, and the communication terminal includes:
- a SIP protocol stack for establishing communication between communication terminals for sharing by different types of application components; a plurality of application components, each application component being respectively connected to the protocol stack, and being called as needed;
- a storage module which is connected to the protocol stack, and configured to store the plurality of application component identifiers; the sending module, the identifier of the application component is carried in the request message and sent to the peer end; and the processing module invokes the application component according to the received application component identifier. Processing of the corresponding SIP message.
- an application component identifier correspondence table is established in advance at the first and second end communication ends, and the application component identifier correspondence table includes a plurality of pieces of the application component information and the application component identifier, and the header in the SIP request message is used.
- the domain User-Agent transmits the application component identifier, and the communication terminal that receives the request message searches the application component identifier correspondence table to obtain the application component information, and then invokes the corresponding application component to process the request message.
- the application component identifier correspondence table is managed by the SIP protocol stack to ensure that the application component identifiers do not conflict.
- the application component identifier distinguishes different types of application components, multiple application components of different types can share one SIP protocol stack, and multiple application components only need to occupy system resources and network resources of one SIP protocol stack, thereby effectively saving device resources. It is especially effective for systems with tight resources.
- FIG. 1 is a schematic diagram of an architecture of a SIP protocol stack in the prior art
- FIG. 2 is a flowchart of a method for SIP message communication in an embodiment of the present invention
- FIG. 3 is a flowchart of processing of a second communication end in the embodiment of the present invention.
- FIG. 5 is a structural diagram of response message self-supplied information in a SIP message communication method according to an embodiment of the present invention
- Figure 8 is a structural diagram of a communication terminal in a specific embodiment of the present invention.
- FIG. 9 is a structural diagram of a communication system in a specific embodiment of the present invention. detailed description In order to make the objects, features and advantages of the present invention more comprehensible, the invention will be described in detail below in conjunction with the specific embodiments.
- the method for implementing SIP message communication in the embodiment of the present invention includes the following steps:
- the first communication end assigns a header field of the request message to the application component identifier, and sends the request message to the second communication end.
- the second communication end acquires a header field of the request message, obtains an application component identifier, and then invokes a corresponding application component according to the application component identifier.
- the application component processes the request message.
- the User-Agent header field obtains the application component identifier, and the second communication end protocol stack searches the application component correspondence table (the table in FIG. 4) according to the application component identifier, and then calls the processing program in the corresponding application component for processing. As shown in Figure 3, the following steps are specifically included:
- the second communication end receives the SIP request message.
- the second communication end acquires a request message header field, and searches for an application component identifier correspondence table to obtain a control block of the corresponding application component.
- the second communication end invokes a processing program in the corresponding application component to process the SIP request message.
- the types of application components in this method are IM group, Presence component and other SIP-supported application components.
- a method for SIP message communication in the embodiment of the present invention is applied to the first and second communication ends, and a plurality of application components of different types at the communication end share a SIP protocol stack.
- the first and second communication ends respectively include a plurality of application components and a protocol stack.
- an application component correspondence table needs to be preset in the first and second communication ends, and the storage structure of the table is as shown in FIG. , including multiple application component identifiers.
- the first communication end sends a SIP request message to the second communication end, and the second communication end responds to the request message to respond to the first communication end with a SIP response message.
- FIG. 6 is a flowchart of a method according to a first embodiment of the present invention, which specifically includes the following steps:
- the first communication end assigns an application component identifier to the header field of the request message, and The second communication end sends the request message;
- the user component identifier field of the SIP request message is first assigned a corresponding application component identifier, and then sent to the second communication end.
- the second communication end receives the SIP request message.
- the second communication end acquires a request message header field, searches an application component identifier correspondence table, and obtains a control block of the application component;
- S604 The second communication end invokes the corresponding application component to process the SIP request message.
- the second communication end assigns an application component identifier to the header field of the SIP response message, and sends the response message to the first communication end;
- the first communication end receives the SIP response message.
- the first communication end obtains a response message header field, searches an application component identifier correspondence table, and obtains a control block of the application component.
- the first communication end invokes a corresponding application component to process the SIP response message.
- the SIP protocol stack can distinguish different types of application components and call the corresponding application component to process the request message; for the SIP response message, the corresponding application can be invoked by using the message itself.
- the component processes the response message.
- Multiple different types of application components can share a single SIP protocol stack, saving device resources.
- FIG. 7 is a flowchart of a method according to a second embodiment of the present invention, which is different from the first embodiment in that after the second protocol stack processes the request message of the first protocol stack, the response message may be directly sent to the first protocol stack.
- Cseq directly locates the corresponding application component.
- the steps of the response message processing flow are as follows:
- Steps S701 to 704 are the same as steps S601 to 604 of the first embodiment, and are not repeated here;
- S705 The second communication end directly sends a SIP response message to the first communication end.
- the first communication end receives the SIP response message.
- the first communication end obtains an application component name according to the information that is included in the header field of the SIP response message.
- the information in the response message header field includes: a Call-ID message identifier and a Cseq message sequence number, and the corresponding relationship with the application component is as shown in FIG. 5, including: an application component, a Call-ID message identifier, and a Cseq message sequence number.
- the first communication end obtains the application component name corresponding to the response message according to the Call-ID message identifier and the Cseq message sequence number in the header field.
- the first communication end invokes the corresponding application component to process the SIP response message, and the first communication end invokes the application component to process the SIP response message according to the obtained application component name.
- multiple different types of application components share a SIP protocol stack.
- the header field of the SIP response message is also used to pass the application component identifier, and the corresponding application component is called to process the response message. Save equipment resources and improve system efficiency.
- the communication terminal for SIP message communication in the embodiment of the present invention includes:
- the SIP protocol stack 801 is configured to establish communication for sharing by different types of application components; and multiple application components 802, each application component is respectively connected to the protocol stack, and is required to be called;
- a storage module 803 configured to be connected to the protocol stack, configured to store the plurality of application component identifiers; the sending module 804, the identifier of the application component is carried in the request message and sent to the peer end; the processing module 805, according to the received application component identifier The application component processes the corresponding SIP message.
- the application component identifier includes: application component information, application component identifier; and the application component information includes: an application component name, and an application component control block.
- the communication terminal of the present invention can distinguish different application components, and realize sharing of multiple application components.
- the system for SIP message communication of the present month includes:
- the first communication terminal and the second communication terminal are connected by a communication network, and the communication terminal includes:
- a SIP protocol stack 801 configured to establish communication for sharing by different types of application components; a plurality of application components 802, each application component being respectively connected to the protocol stack, and being called as needed;
- a storage module 803 which is connected to the protocol stack and configured to store multiple application component identifiers;
- the sending module 804, the identifier of the application component is carried in the request message and sent to the peer end; the processing module 805, the received application component identifier invokes the application component to process the corresponding SIP message.
- the application component identifier includes: application component information, application component identifier; and the application component information includes: an application component name, and an application component control block.
- the communication terminal in the communication system of the present invention can distinguish different application components, and realize that multiple application components share a SIP protocol stack, thereby saving system resources.
- the types of application components in the present invention are IM components, Presence components, and other SIP-supported application components. After the invention is applied, since the application component identification list is established, different application components are distinguished by the SIP request message header domain User-Agent and the response message header domain Server, so that different application components of different types can be shared.
- a SIP protocol stack For different application components of different types, only one system resource and network resources of the SIP protocol stack are occupied, which effectively saves device resources, and is particularly effective for a system with relatively tight resources. Since the present invention is implemented without relying on a specific programming language, it is easy to implement.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Multimedia (AREA)
- Telephonic Communication Services (AREA)
- Telephone Function (AREA)
Description
一种基于 SIP协议实现多应用组件通信的方法、
系统和通信终端 本申请要求于 2006 年 01 月 17 日提交中国专利局、 申请号为 200610033141.9、 发明名称为 "一种 SIP 消息通信的方法、 通信终端和 系统,,的中国专利申请的优先权, 其全部内容通过引用结合在本申请中。 技术领域 本发明涉及通信技术领域, 尤其涉及基于 SIP协议的通信方法、 系 统和通信终端。 背景技术
会话初始化协议 ( SIP, session initiation protocol )是 IETF提出并支 持研究的一个在 IP 网络上进行多媒体通信的应用层控制协议, 用于创 建、 修改和终结一个或多个参与者参加的会话。 SIP协议借鉴了 HTTP、 SMTP等协议, 支持代理、 重定向及登记定位用户等功能, 支持用户移 动。
目前, SIP因其简单、灵活和易于扩展的特性得到了广泛的关注, SIP 不仅做为 IP电话( VoIP, Voice over IP ) 系统中的核心协议,越来越多的 SIP扩展协议也层出不穷,比如 RFC3265,RFC3903,RFC3428等分别定义 了 SUBSCRIBE,NOTIFY,PUBLISH,MESSAGE等不同的 SIP请求消息类 多,比如 IETF 定义的 SIMPLE(SIP Instant Messaging and Presence Leveraging Extensions)协议,包括 IM和 Presence两种应用; 以及 Push, XCAP等都用到. SIP协议及扩展消息。 由此便提出不同类型应用组件间 互相交互的需求。
现有技术中一种实现 SIP协议栈的体系架构,如图 1所示:此架构定 义了四种类: 用户代理、 会话、 传输、 服务, 其中服务为抽象类,对应不 同的服务以定义对应的服务类; 一个应用对应一个用户代理,可以建立、 管理多个 SIP会话 (Session),同时每个会话也可以建立、 管理多个事务 (Transaction), 而每个会话和事务都对应于不同的服务 (Service)。 由此可
知对于不同的应用,必须实现自己的一个用户代理,每个用户代理都管理 属于自己的会话和事务, 同时也要管理属于自己的资源,包括系统资源和 网络资源。
现有的这种技术方案虽然也能够实现多个应用组件互相交互 ,但是, 多个应用要使用 SIP协议栈通信,必须要实现多个用户代理类,同时要占 用同样多的系统资源和网络资源,造成资源的浪费,不适合于资源比较紧 张的系统。
此架构主要利用了面向对象编程中的多态的概念,也就限制了此实 现必须要用 C++, JAVA等面向对象语言来实现。
发明内容
本发明要解决的技术问题是提供一种基于 SIP协议实现多应用组件 通信的方法、 系统和通信终端, 实现不同类型应用组件共享同一个 SIP 协议栈, 且易于实现。
本发明实施例提供一种基于 SIP协议实现多应用組件通信的方法, 包括:
第一通信端将请求消息的头域赋值为应用组件标识, 并向第二通信 端发送该清求;
第二通信端响应所述请求, 得到其中的应用组件标识, 并根据所述 的应用组件标识调用对应的应用组件进行相应 SIP消息的处理。
本发明实施例提供一种通信终端, 包括:
SIP协议栈, 用于建立通信,供不同类型应用组件共享;
多个应用组件, 每个应用组件分别与所述协议栈连接, 根据需要被 调用;
存储模块, 其与协议栈连接, 用于存储多条应用组件标识; 发送模块, 将所述应用组件标识携带在请求消息中发送给对端;
.处理模块, 根据接收的应用组件标识调用应用组件进行相应 SIP消 息的处理。
本发明实施例还提供一种基于 SIP 协议实现多应用组件通信的系 统, 包括第一通信终端、 第二通信终端, 所述第一通信终端与第二通信
终端通过通信链路连接, 其特征在于, 所述通信终端包括:
SIP协议栈, 用于通信终端间建立通信, 供不同类型应用组件共享; 多个应用组件, 每个应用组件分别与所述协议栈连接, 根据需要被 调用;
存储模块, 其与协议栈连接, 用于存储多条应用组件标识; 发送模块 , 将所述应用组件标识携带在请求消息中发送给对端; 处理模块, 根据接收的应用組件标识调用应用组件进行相应 SIP消 息的处理。
本发明的具体实施方案中, 预先在第一、 第二端通信端建立应用組 件标识对应表, 应用组件标识对应表中含有多条包含应用组件信息和应 用组件标识, 通过 SIP请求消息中的头域 User- Agent来传递应用组件标 识,收到请求消息的通信端搜索应用组件标识对应表获取应用组件信息 , 再调用相应的应用组件处理请求消息。 由 SIP协议栈管理应用组件标识 对应表, 保证应用组件标识不冲突。 由于采用应用组件标识区分不同类 型应用组件, 不同类型的多个应用組件能够共享一个 SIP协议栈, 多个 应用组件, 只需占用一个 SIP协议栈的系统资源和网络资源, 有效地节 省了设备资源, 对于资源比较紧张的系统尤其有效。 附图说明
图 1是现有技术中一种实现 SIP协议栈的体系架构示意图; 图 2是本发明实施例中 SIP消息通信的方法流程图;
图 3是本发明实施例中第二通信端的处理流程图;
图 4是本发明实施例的应用组件标识对应表的结构;
图 5是本发明实施例的 SIP消息通信的方法中响应消息自带信息的 结构;
图 6是本发明的第一实施例中 SIP消息通信流程图;
图 7是本发明第二实施例中 SIP消息通信流程图;
图 8是本发明具体实施例中通信终端的结构图;
图 9是本发明具体实施例中的通信系统结构图。 具体实施方式
为使本发明的目的、 特性和优点更加清楚, 下面结合具体实施例对 ■本发明予以详细描述。
如图 2所示, 本发明实施例中的实现 SIP消息通信的方法, 包括如 下步骤:
S201 , 第一通信端将请求消息的头域赋值为应用组件标识, 并向第 二通信端发送该请求消息;
S202,第二通信端获取请求消息的头域,得到其中的应用组件标识, 然后才艮据所述的应用组件标识调用对应的应用组件; 所述的应用组件处 理所述的请求消息。
当第二通信端收到 SIP 请求消息时,通过解析请求消息中的
User-Agent头域,获得应用组件标识, 第二通信端协议栈再根据此应用组 件标识搜索应用组件对应表(图 4中的表),然后调用对应的应用组件中 的处理程序进行处理。 如图 3所示, 具体包括以下步骤:
S301 , 第二通信端接收 SIP请求消息;
S302,第二通信端获取请求消息头域,并搜索应用组件标识对应表, 获得对应的应用组件的控制块;
S303 , 第二通信端调用对应的应用组件中的处理程序处理 SIP请求 消息。
该方法中应用组件的类型为 IM組 、 Presence组件及其他 SIP 支持的应用组件。
本发明实施例的一种 SIP消息通信的方法, 应用于第一、 第二通信 端, 实现在通信端不同类型的多个应用组件共享一个 SIP协议栈。 所述 第一、 第二通信端分别包括多个应用组件和一个协议栈, 在本发明中需 要在第一、 第二通信端预先设置应用组件对应表, 该表的存储结构如图 5所示, 包括多条应用组件标识。 对于 SIP通信来讲, 第一通信端向第 二通信端发送一个 SIP请求消息, 第二通信端处理完该请求消息相应的 就要向第一通信端回复一个 SIP响应消息。 图 6为本发明的第一实施例 的方法流程图, 具体包括如下步骤:
S601 , 第一通信端在请求消息的头域赋值为应用组件标识, 并向第
二通信端发送该请求消息;
当第一通信端的某个应用組件发送 SIP请求消息时, 先在 SIP请求 消息的 User-Agent头域赋值为对应的应用组件标识,然后发送给第二通 信端。
S602, 第二通信端接收该 SIP请求消息;
5603 , 第二通信端获取请求消息头域,搜索应用组件标识对应表, 获得应用组件的控制块;
5604, 第二通信端调用对应的应用组件处理 SIP请求消息;
5605, 第二通信端在 SIP响应消息的头域赋值为应用组件标识, 并 向第一通信端发送该响应消息;
5606, 第一通信端接收 SIP响应消息;
5607, 第一通信端获取响应消息头域,搜索应用组件标识对应表, 获得应用組件的控制块;
5608, 第一通信端调用对应的应用组件处理 SIP响应消息。
由于采用 SIP请求消息的头域传递应用组件标识, SIP协议栈能区 分不同类型的应用组件并调用相应的应用组件处理该请求消息;对于 SIP 响应消息,可以利用其自带的消息调用相应的应用组件处理该响应消息。 多个不同类型应用組件能够共享一个 SIP协议栈, 节省设备资源。
图 7为本发明的第二实施例的方法流程图, 其与第一实施例的不同 在于第二协议栈处理完第一协议栈的请求消息后, 可以直接向第一协议 栈发送响应消息, 通过图 5所示列表内的 Call-ID,Cseq直接定位到对应 的应用组件。 具体来讲, 在第二通信端调用对应的应用组件处理 SIP请 求消息之后对响应消息处理流程的步骤如下:
步骤 S701至 704与第一实施例的步骤 S601至 604相同, 在此不再 重复;
5705, 第二通信端直接向第一通信端发送 SIP响应消息;
5706, 第一通信端接收 SIP响应消息;
5707, 第一通信端根据 SIP响应消息头域中自带的信息, 获得应用 組件名称;
所述响应消息头域中自带的信息包括: Call-ID消息标识和 Cseq消 息序号,其与应用组件的对应关系如图 5所示, 包括:应用组件、 Call-ID 消息标识和 Cseq消息序号。 第一通信端 据头域中的 Call-ID消息标识 和 Cseq消息序号获取该响应消息所对应的应用组件名称。
S708, 第一通信端调用对应的应用组件处理 SIP响应消息, 第一通 信端才艮据所获得的应用组件名称调用该应用组件处理 SIP响应消息。
本实施例中,多个不同类型应用组件共享一个 SIP协议栈,对于 SIP 响应消息, 也采用 SIP响应消息的头域传递应用组件标识, 并调用相应 的应用组件处理该响应消息。 节省设备资源, 提高系统效率。
如图 8所示, 本发明实施例的 SIP消息通信的通信终端包括:
SIP协议栈 801 , 用于建立通信, 供不同类型应用组件共享; 多个应用组件 802, 每个应用组件分别与所述协议栈连接, 居需 要被调用;
存储模块 803 , 其与协议栈连接, 用于存储多条应用组件标识; 发送模块 804, 将所述应用组件标识携带在请求消息中发送给对端; 处理模块 805,根据接收的应用组件标识调用应用组件进行相应 SIP 消息的处理。
所述的应用组件标识包括: 应用组件信息、 应用组件标识; 所述的 应用组件信息包括: 应用組件名称、 应用组件控制块。
通过建立应用组件标识存储模块, 存储应用组件标识的对应信息, 本发明的通信终端, 能区分不同应用组件, 实现多个应用组件共享一个
SIP协议栈, 节约系统资源。
如图 9所示, 本发 H月的 SIP消息通信的系统包括:
包括第一通信终端、 第二通信终端, 所述第一通信终端与第二通信 终端通过一通信网连接, 所述通信终端都包括有:
SIP协议栈 801, 用于建立通信, 供不同类型应用组件共享; 多个应用組件 802, 每个应用组件分别与所述协议栈连接, 根据需 要被调用;
存储模块 803, 其与协议栈连接, 用于存储多条应用组件标识;
发送模块 804, 将所述应用组件标识携带在请求消息中发送给对端; 处理模块 805 , 居接收的应用组件标识调用应用组件进行相应 SIP 消息的处理。
所述的应用组件标识包括: 应用组件信息、 应用组件标识; 所述的 应用组件信息包括: 应用组件名称、 应用组件控制块。
通过建立应用组件标识存储模块, 存储应用组件标识的对应信息, 本发明的通信系统中的通信终端, 能区分不同应用组件, 实现多个应用 組件共享一个 SIP协议栈, 节约系统资源。
本发明中应用组件的类型为 IM组件、 Presence组件及其他 SIP 支持的应用組件。 采用本发明后, 由于建立了应用组件标识列表, 对不 同类型的应用組件, 通过 SIP请求消息头域 User-Agent和响应消息头域 Server来进行区分,从而实现不同类型的多个应用组件能够共享一个 SIP 协议栈。 对于不同类型的多个应用组件, 只需占用一个 SIP协议栈的系 统资源和网络资源, 有效地节省了设备资源, 对于资源比较紧张的系统 尤其有效。 由于本发明不依赖特定的编程语言来实现, 易于实现。
以上所述, 仅为本发明较佳的具体实施方式, 但本发明的保护范围 并不局限于此, 凡在本发明的精神和原则之内所做的任何修改、 等同替 换和改进等, 均应包含在本发明的保护范围之内, 因此, 本发明的保护 范围应该以权利要求的保护范围为准。
Claims
1、一种基于 SIP协议实现多应用组件通信的方法, 其特征在于, 包 括:
第一通信端将请求消息的头域赋值为应用组件标识, 并向第二通信端 发送该请求;
第二通信端响应所述请求, 得到其中的应用组件标识, 并根据所述的 应用组件标识调用对应的应用组件进行相应 SIP消息的处理。
2、 如权利要求 1所述的 SIP消息通信的方法, 其特征在于, 所述第 二通信端响应所述请求, 得到其中的应用组件标识, 并才艮据所述的应用 組件标识调用对应的应用组件具体包括:
第二通信端接收请求消息;
获取请求消息头域, 并查询应用组件标识对应表, 获得对应的应用 组件的控制块;
调用所述应用组件的控制块处理所述请求。
3、 如权利要求 2所述的 SIP消息通信的方法, 其特征在于, 所述的 应用組件标识对应表包括: 应用組件信息、 应用组件标识;
所述的应用组件信息包括: 应用組件名称、 应用组件控制块。
4、 如权利要求 1或 2所述的方法, 其特征在于, 进一步包括: 第二通信端向第一通信端发送响应消息, 并将响应消息的头域赋值 为对应的应用组件标识;
第一通信端获取响应消息头域, 并查询应用组件标识对应表, 获得 对应的应用组件的控制块;
第一通信端调用所述应用组件的控制块处理所述处理响应消息。
5、 如权利要求 1或 2所述的方法, 其特征在于, 还包括: 第二通信端向第一通信端发送响应消息;
第一通信端获取响应消息头域, 根据响应消息头域中自带的信息, 获得对应的应用组件名称;
第一通信端调用所述应用组件处理所述处理响应消息。
6、 如权利要求 5所述的方法, 其特征在于, 所述响应消息头域中自
带的信息包括: 应用組件名称、 响应消息标识 Call-ID和消息序号 Cseq。
7、 一种通信终端, 其特征在于, 包括:
SIP协议栈, 用于建立通信, 供不同类型应用组件共享;
多个应用组件, 每个应用组件分别与所述协议栈连接, 根据需要被 调用;
存储模块, 其与协议栈连接, 用于存储多条应用组件标识; 发送模块, 将所述应用組件标识携带在请求消息中发送给对端; 处理模块, 根据接收的应用组件标识调用对应的应用组件进行相应 SIP消息的处理。
8、如权利要求 7所述的通信终端, 其特征在于, 所述的应用組件标 识包括: 应用组件信息和应用组件标识。
9、 如权利要求 8所述的通信终端, 其特征在于, 所述的应用组件信 息包括: 应用组件名称和应用组件控制块。
10、 一种基于 SIP协议实现多应用组件通信的系统, 包括第一通信 终端、 第二通信终端, 所述第一通信终端与第二通信终端通过通信链路 连接, 其特征在于, 所述通信终端包括:
SIP协议栈, 用于通信终端间建立通信, 供不同类型应用组件共享; 多个应用组件, 每个应用组件分别与所述协议栈连接, 根据需要被 调用;
存储模块, 其与协议栈连接, 用于存储多条应用组件标识; 发送模块 , 将所述应用组件标识携带在请求消息中发送给对端; 处理模块, 根据接收的应用组件标识调用对应的应用组件进行相应 SIP消息的处理。
11、 如权利要求 10所述的通信系统, 其特征在于, 所述的应用組件 标识包括: 应用组件信息、 应用组件标识。
12、 如权利要求 11所述的通信系统, 其特征在于, 所述的应用组件 信息包括: 应用组件名称、 应用组件控制块。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200610033141.9A CN101005492A (zh) | 2006-01-17 | 2006-01-17 | 一种sip消息通信的方法、通信终端和系统 |
CN200610033141.9 | 2006-01-17 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2007082454A1 true WO2007082454A1 (fr) | 2007-07-26 |
Family
ID=38287253
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2006/003555 WO2007082454A1 (fr) | 2006-01-17 | 2006-12-22 | Procédé, système et terminal de communication pour la mise en oeuvre de communication à composants de multi-applications basée sur le protocole d'ouverture de session |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN101005492A (zh) |
WO (1) | WO2007082454A1 (zh) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101764828B (zh) * | 2008-12-23 | 2013-08-07 | 华为终端有限公司 | 推送会话的建立方法、推送系统和相关设备 |
CN114844963B (zh) * | 2022-03-31 | 2023-02-17 | 慧之安信息技术股份有限公司 | 基于开源协议栈eXosip的扩展头部信息提取方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003085911A1 (en) * | 2002-04-08 | 2003-10-16 | Nokia Corporation | Message header for messaging service |
CN1499804A (zh) * | 2002-11-12 | 2004-05-26 | ���ǵ�����ʽ���� | 处理会话发起协议系统的会话信息的方法及其记录介质 |
CN1662004A (zh) * | 2004-02-27 | 2005-08-31 | 华为技术有限公司 | 一种实现会话发起协议应用服务器多业务处理的方法 |
-
2006
- 2006-01-17 CN CN200610033141.9A patent/CN101005492A/zh active Pending
- 2006-12-22 WO PCT/CN2006/003555 patent/WO2007082454A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2003085911A1 (en) * | 2002-04-08 | 2003-10-16 | Nokia Corporation | Message header for messaging service |
CN1499804A (zh) * | 2002-11-12 | 2004-05-26 | ���ǵ�����ʽ���� | 处理会话发起协议系统的会话信息的方法及其记录介质 |
CN1662004A (zh) * | 2004-02-27 | 2005-08-31 | 华为技术有限公司 | 一种实现会话发起协议应用服务器多业务处理的方法 |
Also Published As
Publication number | Publication date |
---|---|
CN101005492A (zh) | 2007-07-25 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2150013B1 (en) | System, equipment and method for implementing special calling services | |
KR101441434B1 (ko) | 로컬 영역 네트워크에서 통신 세션 제어를 제공하는 방법 및 시스템 | |
US20090092109A1 (en) | Method and Apparatus for Enabling Discovery Within a Home Network | |
US8601139B2 (en) | Multiple core session initiation protocol (SIP) | |
EP1516263A1 (en) | Integration of service registration and discovery in networks | |
US20160330163A1 (en) | Method and server enabling a first user to automatically discover the social network identifiers of a second user and the respective statuses of this second user in these social networks | |
CN100574474C (zh) | 一种通讯系统中建立通讯业务连接的方法 | |
CN101834730A (zh) | 一种多媒体会议控制方法和系统 | |
CN101854703A (zh) | 获取状态信息的方法、服务器及系统 | |
JP5172850B2 (ja) | セッションベースの通信 | |
EP1889416A1 (en) | Shared ip multimedia resource reservation | |
WO2006008297A2 (en) | Push to watch network element and software architecture | |
US20090232141A1 (en) | Using a Hash Value as a Pointer to an Application Class in a Communications Device | |
EP2863603A1 (en) | A method for optimizing the capability discovery of terminals in an IMS network | |
KR100976050B1 (ko) | 이동통신 단말기의 임시 아이디를 이용한 익명성 메시지제공 시스템 및 그 방법 | |
WO2007082454A1 (fr) | Procédé, système et terminal de communication pour la mise en oeuvre de communication à composants de multi-applications basée sur le protocole d'ouverture de session | |
EP2730084A1 (en) | A method and a system to discover and establish an enriched communication channel in a voice call | |
CN101635672A (zh) | 一种群组方式下实现融合业务会话的装置和方法 | |
JP4919347B2 (ja) | プレゼンス情報にセッション情報を対応付けた通信リソース状態管理方法、システム及びプログラム | |
WO2010075688A1 (zh) | Ims集群会议的创建和加入方法、装置及系统 | |
Chou et al. | WIP: Web service initiation protocol for multimedia and voice communication over IP | |
Chou et al. | Web services for service-oriented communication | |
JP2005033528A (ja) | 通信セッションの確立方法 | |
KR20180074341A (ko) | 통화 중 단말 변경 서비스를 제공하기 위한 장치 및 방법 | |
CN101815070A (zh) | 消息处理方法及系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 06840611 Country of ref document: EP Kind code of ref document: A1 |