WO2008071100A1 - Procede et systeme d'acquisition du trajet de transmission du message sip - Google Patents

Procede et systeme d'acquisition du trajet de transmission du message sip Download PDF

Info

Publication number
WO2008071100A1
WO2008071100A1 PCT/CN2007/070668 CN2007070668W WO2008071100A1 WO 2008071100 A1 WO2008071100 A1 WO 2008071100A1 CN 2007070668 W CN2007070668 W CN 2007070668W WO 2008071100 A1 WO2008071100 A1 WO 2008071100A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
unit
call request
called party
request message
Prior art date
Application number
PCT/CN2007/070668
Other languages
English (en)
French (fr)
Inventor
M. R. Prakasha
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to EP07801076A priority Critical patent/EP2068524A4/en
Publication of WO2008071100A1 publication Critical patent/WO2008071100A1/zh
Priority to US12/425,704 priority patent/US20090204715A1/en

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/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/10—Architectures or entities
    • H04L65/1045—Proxies, e.g. for session initiation protocol [SIP]
    • 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
    • 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]

Definitions

  • the present invention relates to the field of network communication technologies, and in particular, to a method and system for acquiring a session initiation protocol message transmission path.
  • SIP Session Initiation Protocol
  • IETF International Internet Standards Development Organization
  • SIP is an application layer protocol that can establish, modify, or abort multimedia sessions or calls.
  • the operator wants to actively optimize the routing policy and wants to maintain the routing policy on the network periodically, it needs to initiate a test call and request information from the called party to obtain the path of the SIP message traversing the downstream entity.
  • SIP is an application layer control protocol that establishes, modifies, or terminates multimedia sessions or calls. Calls in the SIP system are implemented through the three handshakes of the INVITE Invite Request, Successful Response, and ACK Acknowledgement Request. That is, when the calling user agent wants to initiate a call, it constructs an INVITE message and sends it to the called party. After the called party decides to accept the call after receiving the invitation, it will send back a successful response (status code is 200). After the caller receives a successful response, it sends an ACK request to the other party. After the called party receives the ACK request, the call is successfully established.
  • the Via field indicates the path that the request message has passed so far, so the calling party can provide the called party with information about the path traversed by the incoming SIP message through the field.
  • the success response message sent by the called party to the calling party no similar information is provided.
  • the field, that is, the path information cannot be provided to the calling party.
  • the embodiment of the invention provides a method and a system for acquiring a session initiation protocol message transmission path, so that the called party can provide the message transmission path information to the calling party, and provide necessary information for the operator to maintain the network.
  • the embodiment of the invention further provides a network node device for acquiring a session initiation protocol message transmission path, so as to effectively obtain a session initiation protocol message transmission path.
  • a method for obtaining a session initiation protocol message transmission path includes:
  • the calling party initiates a test call, and carries a path information request flag in the call request message, where the flag indicates that the called party is required to return the session initiation protocol message transmission path information;
  • a system for obtaining a session start protocol message transmission path includes: a calling party node and a called party node, where
  • the calling party node includes:
  • test call unit configured to initiate a test call to the called party node, and carry a path information request flag in the call request message
  • a path information obtaining unit configured to obtain a transmission path of the call request message from a success response message received by the calling party node
  • the called party node includes:
  • a detecting unit configured to detect a type of the message received by the called party node
  • a message constructing unit configured to: when the detecting unit detects that a call request message received by the called party node includes a field requesting called party information, edit the call request message to the called party node to send In the success response message to the calling party node.
  • a network node device comprising: a messaging unit, a call request message construction unit, a path information acquisition unit, and a detection unit, where
  • a messaging unit for performing message interaction with other node devices in the network, to the other
  • the node device initiates a test call, and receives a success response message from the other node device
  • a detecting unit configured to detect a message type received by the messaging unit
  • a path information obtaining unit configured to obtain a transmission path of the message from the success response message after the detecting unit detects the success response message
  • the call request message constructing unit is configured to construct a call request message required by the messaging unit to initiate a test call, and add a path information request flag to the call request message.
  • the calling party initiates a test call, and carries a path information request flag in the call request message, requesting the called party to return to the SIP. Message transmission path information.
  • the called party After receiving the call request message, the called party returns a success response message to the calling party, and includes the received call request message in the success response message, so that the calling party obtains the path that the call request message traverses in the network.
  • Figure 2 is a schematic block diagram of a preferred embodiment of the system of the present invention.
  • FIG. 3 is a schematic block diagram of a first embodiment of a network node device of the present invention.
  • FIG. 4 is a schematic block diagram of a second embodiment of a network node device of the present invention.
  • the SIP-based network initiates a test call by the calling party, and carries a path information request flag in the call request message, requesting the called party to return the SIP message transmission path information.
  • the called party After receiving the call request message, the called party returns a success response message to the calling party, and includes the received call request message in the success response message, so that the calling party obtains the path that the call request message traverses in the network. .
  • Step 101 A calling party initiates a test call, and carries a path information request flag in the call request message. This flag indicates that the called party is required to return the SIP message transmission path information.
  • a test call can be initiated using the SIP INVITE message.
  • the INVITE message is the first message sent by the calling party in the call processing period.
  • the information contained in the SIP message header identifies the calling party, the Call-ID, the called party, the call sequence number, and other contents.
  • the path information request flag needs to be carried in the INVITE message.
  • the SIP request message format consists of three parts: the start line, the message header, and the message body. Among them, in the request message, the starting line is also called the request line. In the response message, the starting line is called the status line. In the request line, the first is a method tag, followed by the requested URI (Uniform Resource Identifier), and the protocol version. In the status line, the first is the protocol version, followed by the status code and some status descriptions.
  • the SIP message header consists of multiple field names (Field), field values, and description information.
  • the message body is the part of the message content to be sent.
  • the fields in the SIP message header are: From, To, Call-ID, Cseq, Via, Contact,
  • All requests and responses must include a From field, a To field, a From field indicating the originator of the request, a To field indicating the recipient of the request, and a Call-ID to uniquely identify a particular invitation or identify all registrations for a customer.
  • Cseq is the message sequence number, and the Contact field gives the address that is then directly communicated with the user.
  • Via is used to indicate the path the request message is going through, to prevent the request message from looping, and to ensure that the response message and the request message select the same path.
  • the client making the request must insert its own hostname or network address into the request Via field.
  • each proxy server must add its own address as a new Via field before the existing Via field. Proxy client pass
  • the option tag listed in the Require field tells the proxy server which options to support when processing the request. This field is optional but cannot be ignored.
  • the path information request flag is carried in the message header of the INVITE message, to indicate that the called party is required to return the SIP message transmission path information.
  • the sipdiag field is set in the Supported header of the Require field, indicating that the call is a test call, so that the called party can immediately return the received call request message to the calling party according to the field.
  • Step 102 The called party receives the call request message.
  • Step 103 Obtain the Require field information in the message header of the call request message.
  • Step 104 Determine whether the path information request flag is included in the Require field. If yes, go to step 105; otherwise, go to step 107.
  • Step 105 Return a success response message to the calling party, and include the received call request message in the success response message.
  • the received call request message may be included in the message body of the 2XX message and sent to the calling party, so that the calling party can obtain the transmission path of the call request message according to the message.
  • Step 106 The calling party acquires a transmission path of the call request message according to the received success response message.
  • Step 107 Perform other corresponding processing procedures for the message.
  • the following is an example of the message format during a test call.
  • the Require field of the above request message is: sipdiag, which is a path information request flag.
  • the message body of the above response message whose message body type is sipfrag contains the INVITE message received by the called party.
  • the called party can accept the request of the calling party without waiting for the called party to explicitly accept, so that the calling party's domain operator can not disturb the called party.
  • the called side UA User Agent
  • the called side UA analyzes the "Via" information in the INVITE request to obtain the required path information. If the carrier finds that the path is not the best path, you can modify the routing policy in the domain and optimize the routing policy to better ensure the smooth routing of calls in the network.
  • Figure 2 is a block diagram of a preferred embodiment of the system of the present invention:
  • the system of the present invention includes a calling party node 11 and a called party node 12.
  • a calling party node 11 and a called party node 12.
  • the calling party node 11 includes: a test call unit 111, and a path information acquiring unit 112.
  • the test call unit 111 is configured to initiate a test call to the called party node 12, and carry a path information request flag in the call request message, where the flag indicates that the called party is required to return the SIP message transmission path information; Obtaining a transmission path of the call request message in a success response message received from the calling party node.
  • the called party node 12 includes: a detecting unit 121, and a message constructing unit 122.
  • the detecting unit 121 is configured to detect a type of a call request message received by the called party node; the message constructing unit 122 is configured to: when the detecting unit detects that the call request message received by the called party node includes a field requesting the called party information And editing the call request message into a success response message sent by the called party node to the calling party node.
  • the test call unit initiates a test call to the called party node, and the path request request flag is carried in the call request message of the test call.
  • the INVITE message mentioned in the foregoing description of the method embodiment of the present invention carries a path information request flag in its message header to indicate that the called party is required to return the SIP message transmission path information.
  • the sipdiag field in the Supported header of the Require field is set to the test call mode, so that the called party node can receive according to the field.
  • the call request message is included in the success response message and returned to the calling party.
  • the calling party node can initiate a test call periodically, or can initiate a test call periodically.
  • the detecting unit 121 detects the type of the call request message received by the called party node, and acquires the information in the message header of the call request message. If it is detected that the calling party sends the test call and requests the path information, the notification message constructing unit 122 edits the call request message to the success response message sent by the called party node to the calling party node, for example, the INVITE The message edits all or only the information in the Via field into the body of the success response message. The called party node then sends the success response message to the calling party node.
  • the path information obtaining unit 112 obtains the transmission path of the call request message, that is, the Via field information in the INVITE message, from the success response message. In this way, the calling party node can obtain the transmission path of the call request message, thereby providing the network operator with the necessary information for network maintenance.
  • FIG. 3 is a schematic block diagram of a first embodiment of a network node device of the present invention:
  • the device includes: a messaging unit 31, a call request message constructing unit 32, a path information acquiring unit 112, and a detecting unit 121, wherein the messaging unit 31 is configured to perform message interaction with other node devices in the network, and initiates to other node devices. Testing the call, and receiving a success response message from the other node device; the detecting unit 121 is configured to detect the type of the message received by the messaging unit; the path information acquiring unit 112 is configured to succeed after the detecting unit 121 detects the successful response message. The transmission path of the message is obtained in the response message; the call request message constructing unit 32 is configured to construct a call request message required by the messaging unit to initiate the test call, and add a field requesting the called party information to the call request message.
  • the device of the present invention further includes: a response message constructing unit 33, configured to: when the detecting unit detects the call request message, and the call request message includes a field requesting the called party information, Constructing a success response message that the messaging unit needs to respond, including all or part of the call request message in the success response message.
  • a response message constructing unit 33 configured to: when the detecting unit detects the call request message, and the call request message includes a field requesting the called party information, Constructing a success response message that the messaging unit needs to respond, including all or part of the call request message in the success response message.
  • the node device can initiate a call as another node device in the calling direction network, or can also receive the call from other nodes in the network as the called party.
  • the node device needs to initiate a test call.
  • the call request message constructing unit constructs a call request message.
  • the path information request flag needs to be added to the call request.
  • the sipdiag field in the INVITE message may be set to the test call mode. For the specific implementation, refer to the description in the foregoing method embodiment of the present invention.
  • the constructed call request message is handed over to the messaging unit. The messaging unit sends the call request message to the called node device to initiate a test call.
  • the messaging unit of the called node device After receiving the call request message, the messaging unit of the called node device detects the message by the detecting unit of the called node device. If the message is found to be a test call message and the path information request flag is included, the called node is notified. The response message construction unit in the device constructs a success response message, including all or part of the call request message into the success response message. The successful response message is then handed over to the messaging unit, which responds to the node device initiating the test call by the messaging unit.
  • the messaging unit of the node device that initiates the test call receives the message from the called device, and after the detecting unit detects the success response message of the called node device, the notification path information obtaining unit acquires the call request message in the success response message. Transmission path information. In this way, the purpose of this test call is completed.
  • FIG. 4 is a schematic block diagram of a second embodiment of a network node device of the present invention:
  • the route storage unit 41 and the route maintenance unit 42 are added.
  • the routing storage unit 41 is configured to store routing information in the network.
  • the routing maintenance unit 42 is connected to the path information acquiring unit, and is configured to update the storage path information stored in the routing storage unit according to the transmission path information of the call request message acquired by the path information acquiring unit. Routing information.
  • routing update and optimization policies may be preset, so that the routing maintenance unit 32 can automatically update the routing information stored in the routing storage unit by using the policy, thereby ensuring smooth network routing and providing better services for users.
  • the field of the requested called party information described in the above embodiment is the path information request flag.

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

获取会话起始协议消息传输路径的方法及系统
本申请要求于 2006 年 12 月 15 日提交中国专利局、 申请号为 200610168029.6、 发明名称为"获取会话起始协议消息传输路径的方法及系统" 的中国专利申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及网络通信技术领域，具体涉及一种获取会话起始协议消息传输 路径的方法及系统。
背景技术
SIP ( Session Initiation Protocol, 会话起始协议）是由 IETF (国际互联网 标准制定组织）制定的面向 Internet会议和电话的信令协议。 SIP是一个应用 层的协议， 可以建立、 修改或者中止多媒体会话或者呼叫。
在基于 SIP协议的网络中， 为了保证网络的正常运行， 运营商需要对各自 域内的路由策略设置进行定期更新和优化。在进行更新和优化时，运营商需要 进行以下处理工作：
( 1 ) 检查信令和介质路径的完备性；
( 2 ) 检测环路；
( 3 ) 优化路由策略。
如果运营商想要主动优化路由策略， 并且想要定期在网络中维护路由策 略， 则需要发起测试呼叫， 并请求来自被叫方的信息， 以获得 SIP消息穿越下 游实体的路径。
SIP是一个应用层控制协议， 它能够建立、 修改、 终止多媒体会话或者呼 叫。 SIP系统中的呼叫是通过 INVITE邀请请求、 成功响应和 ACK确认请求的三 次握手来实现的。即当主叫用户代理要发起呼叫时，它构造一个 INVITE 消息， 并发送给被叫。 被叫收到邀请后决定接受该呼叫， 就回送一个成功响应（状态 码为 200 )。 主叫方收到成功响应后， 向对方发送 ACK请求。 被叫收到 ACK请 求后， 呼叫成功建立。
当前， 在 INVITE消息的消息头中， Via字段表示请求消息迄今为止经过 的路径，因此主叫方可以通过该字段向被叫方提供有关入局 SIP消息所穿越路 径的信息。 而被叫方向主叫方回应的成功响应消息中， 则没有提供类似信息的 字段， 也就是说， 无法向主叫方提供路径信息。
发明内容
本发明实施例提供一种获取会话起始协议消息传输路径的方法及系统，使 被叫方能够向主叫方提供消息传输路径信息，为运营商对网络的维护提供必要 信息。
本发明实施例还提供一种获取会话起始协议消息传输路径的网络节点设 备， 以有效地获取会话起始协议消息传输路径。
为此， 本发明实施例提供的技术方案如下：
一种获取会话起始协议消息传输路径的方法， 包括：
主叫方发起测试呼叫， 并在呼叫请求消息中携带路径信息请求标志， 所述 标志表示要求被叫方返回会话起始协议消息传输路径信息；
被叫方收到所述呼叫请求消息后向所述主叫方返回成功响应消息，并根据 所述路径信息请求标志， 将收到的呼叫请求消息包含在该成功响应消息中； 主叫方根据收到的成功响应消息获取所述呼叫请求消息的传输路径。 一种获取会话起始协议消息传输路径的系统， 包括： 主叫方节点、 被叫方 节点， 其中，
所述主叫方节点包括：
测试呼叫单元，用于向所述被叫方节点发起测试呼叫， 并在呼叫请求消息 中携带路径信息请求标志；
路径信息获取单元，用于从主叫方节点接收的成功响应消息中获取出所述 呼叫请求消息的传输路径；
所述被叫方节点包括：
检测单元， 用于检测所述被叫方节点接收到的消息类型；
消息构造单元，用于在所述检测单元检测到所述被叫方节点接收的呼叫请 求消息中包含请求被叫方信息的字段时，将所述呼叫请求消息编辑到所述被叫 方节点发送给所述主叫方节点的成功响应消息中。
一种网络节点设备， 包括： 消息收发单元、 呼叫请求消息构造单元、 路径 信息获取单元、 检测单元， 其中，
消息收发单元，用于和网络中的其他节点设备进行消息交互， 向所述其他 节点设备发起测试呼叫， 并接收来自所述其他节点设备的成功响应消息； 检测单元， 用于检测所述消息收发单元接收到的消息类型；
路径信息获取单元，用于在所述检测单元检测到成功响应消息后，从该成 功响应消息中获得消息的传输路径；
呼叫请求消息构造单元，用于构造所述消息收发单元发起测试呼叫所需的 呼叫请求消息， 并将路径信息请求标志加入到所述呼叫请求消息中。
由以上本发明实施例提供的技术方案可以看出，本发明在基于 SIP协议的 网络中，由主叫方发起测试呼叫，并在呼叫请求消息中携带路径信息请求标志， 要求被叫方返回 SIP消息传输路径信息。被叫方收到该呼叫请求消息后向主叫 方返回成功响应消息， 并将收到的呼叫请求消息包含在该成功响应消息中，使 主叫方获得呼叫请求消息在网络中穿越的路径，从而为运营商对各自域内的路 由策略设置及主动维护提供必要的信息。
附图说明
图 1是本发明方法一个优选实施例的实现流程图；
图 2是本发明系统一个优选实施例的原理框图；
图 3是本发明网络节点设备第一实施例的原理框图；
图 4是本发明网络节点设备第二实施例的原理框图。
具体实施方式
本发明实施例是基于 SIP协议的网络中， 由主叫方发起测试呼叫， 并在呼 叫请求消息中携带路径信息请求标志，要求被叫方返回 SIP消息传输路径信息。 被叫方收到该呼叫请求消息后向主叫方返回成功响应消息，并将收到的呼叫请 求消息包含在该成功响应消息中，从而使主叫方获得呼叫请求消息在网络中穿 越的路径。
为了使本技术领域的人员更好地理解本发明方案，下面结合附图和实施方 式对本发明作进一步的详细说明。
首先， 参照图 1所示本发明一个实施例的实现流程， 包括以下步骤： 步骤 101 : 主叫方发起测试呼叫， 并在呼叫请求消息中携带路径信息请求 标志。 该标志表示要求被叫方返回 SIP消息传输路径信息。 可以使用 SIP协议的 INVITE (邀请）消息发起测试呼叫。 INVITE消息是呼 叫处理周期中主叫方发送的第一条消息， 它在 SIP消息头中包含的信息， 标识 了主叫方、 Call-ID、 被叫方、 呼叫顺序编号和其他一些内容。
除此之外 , 为了使被叫方能够得知需要向主叫方返回 INVITE消息经过的 路由信息， 还需要在 INVITE消息中携带路径信息请求标志。
SIP请求消息格式包括三部分： 起始行、 消息头、 消息体。 其中， 在请求 消息中， 起始行也称为请求行。 而在响应消息中， 起始行称为状态行。 请求行 中， 首先是一个方法标记， 然后是请求的 URI ( Uniform Resource Identifier, 统 一资源标识符）、 协议版本。 状态行中， 首先是协议版本， 然后是状态码及一 些状态说明。 SIP消息头由多个字段名称（Field )、 字段值、 描述信息组成。 消 息体则是要发送的消息内容部分。
SIP消息头中的字段主要有： From, To、 Call-ID, Cseq、 Via, Contact,
Require。 其中， 所有的请求和响应必须包含 From字段、 To字段， From字段 指示请求的发起者； To字段指明请求的接收者； Call-ID用以唯一标识一个特 定的邀请或标识某一客户的所有登记。 Cseq为消息序号， Contact字段给出其 后和用户直接通信的地址。
Via用以指示请求消息经历的路径， 以防止请求消息产生环路， 并确保响 应消息和请求消息选择同样的路径。发起请求的客户必须将其自身的主机名或 网络地址插入请求 Via字段。 在请求消息前传过程中， 每个代理服务器必须将 其自身地址作为一个新的 Via字段加在已有的 Via字段之前。 代理客户端通过
Require字段列出的选项标签， 告知代理服务器处理请求时需要支持的选项， 本字段为可选， 但不可以被忽略。
为此，本发明实施例中在 INVITE消息的消息头中携带路径信息请求标志， 以表示要求被叫方返回 SIP消息传输路径信息。
另外， 为了不使测试呼叫给被叫方的其他消息处理产生影响， 可以在
Require字段的 Supported标头中设置 sipdiag字段， 表示本次呼叫是测试呼叫， 以使被叫方可以根据该字段将收到的呼叫请求消息包含在成功响应消息中立 即返回给主叫方。
步骤 102: 被叫方接收呼叫请求消息。 步骤 103： 获取呼叫请求消息的消息头中的 Require字段信息。
步骤 104: 判断 Require字段中是否带有路径信息请求标志。 如果有， 则进 到步骤 105; 否则， 进到步骤 107。
步骤 105: 向主叫方返回成功响应消息， 并将收到的呼叫请求消息包含在 该成功响应消息中。
在本发明实施例中，可以将收到的呼叫请求消息包含在 2XX消息的消息体 中发送给主叫方， 从而使主叫方可以根据该消息获取呼叫请求消息的传输路 径。
步骤 106: 主叫方根据收到的成功响应消息获取所述呼叫请求消息的传输 路径。
步骤 107: 进行消息的其他相应处理流程。
下面举例说明进行测试呼叫过程中的消息格式。
请求消息 （INVITE ) ：
Figure imgf000007_0001
Via: SIP/2.0/TCP pc33. atlanta. com;branch=z9hG4bKnashds8
Max-Forwards: 70
Figure imgf000007_0002
v=0
o=user 2890844526 2890844526 IN IP4 client.example.com
s=Session SDP c=IN IP4 client . example . com
t=3034423619 0
m=audio 49170 RTP/AVP 0
a=rtpmap:0 PCMU/8000
上述请求消息的 Require字段为： sipdiag, 为路径信息请求标志， 被叫方收 到该请求消息后，应向主叫方返回成功响应消息， 并将收到的呼叫请求消息包 含在该成功响应消息中。
响应消息 （200 OK):
SIP/2.0 200 OK
Via: SIP/2.0/TCP serverl0.biloxi.com;branch=z9hG4bK4b43c2ff8.1
Via: SIP/2.0/TCP \
bigbox3.site3.atlanta.com;branch=z9hG4bK77ef4c2312983.1 \
； received: 192.0.2.2
Via: SIP/2.0/TCP pc33.atlanta.com;branch=z9hG4bKnashds8 \
； received=192.0.2.1
From: Alice <sip:alice@example.com>;tag=9fxced76sl
To: Bob <si ： bob @example . com>； tag=8321234356
Call-ID: 3848276298220188511@client-alice.example.com
CSeq: 1 INVITE
Contact: <sip:bob@client.biloxi. example. com>
Content-Type: multipart/mixed; boundary= "boundary 1 "
Content-Length: ...
—boundary 1
Content-Type: application/sdp
v=0
o=alice 2890844527 2890844527 IN IP4 example.com
s=Session SDP
c=IN IP4 example.com t=3034423619 0
m=audio 3456 RTP/AVP 0
a=rtpmap:0 PCMU/8000 —boundary 1
Content-Type: message/sipfrag
INVITE sip:bob@client.biloxi. example. com SIP/2.0
Via: SIP/2.0/TCP serverl0.biloxi.com;branch=z9hG4bK4b43c2ff8.1 Via: SIP/2.0/TCP \
bigbox3.site3.atlanta.com;branch=z9hG4bK77ef4c2312983.1\
； received: 192.0.2.2
Via: SIP/2.0/TCP pc33. atlanta. com;branch=z9hG4bKnashds8\
； received: 192.0.2.1
Max-Forwards: 68
From: Alice <si ： alice@atlanta. example . com>； tag=9fxced76 si To: Bob <sip:bob@example.com>
Call-ID:384827629822018851 l@client-alice.example.com
CSeq: 1 INVITE
Contact: <si ： alice@client. atlanta. example . com>
Supported: sipdiag
Require: sipdiag
Content-Type: application/sdp
Content-Length: ...
—boundary 1- 上述响应消息的消息体类型为 sipfrag的消息体中包含了被叫方接收到的 INVITE消息。 由上述实施例可见， 利用本发明， 可以在被叫方节点允许不等待被叫方明 确接受的情况下接受主叫方的请求，因此可以使主叫方的域运营商在不打扰被 叫方的情况下获得 SIP请求消息穿越的路径信息。 接收到 INVITE消息后， 被 叫侧 UA ( User Agent, 用户代理）分析 INVITE请求中的" Via"信息， 从而获 得所需的路径信息。如果运营商发现该路径不是最佳路径， 可以修改域中的路 由策略， 优化路由策略， 更好地保证网络中呼叫路由的畅通。
参照图 2, 图 2是本发明系统一个优选实施例的原理框图：
在该实施例中， 本发明系统包括主叫方节点 11和被叫方节点 12。 在实际 应用中， 主叫方节点 11和被叫方节点 12之间还可以有其他的节点设备， 主叫 方节点 11和被叫方节点 12的交互消息通过这些其他的节点设备进行转发。
主叫方节点 11包括： 测试呼叫单元 111、 路径信息获取单元 112。 其中， 测试呼叫单元 111用于向被叫方节点 12发起测试呼叫， 并在呼叫请求消息中 携带路径信息请求标志， 该标志表示要求被叫方返回 SIP消息传输路径信息； 路径信息获取单元 112 用于从主叫方节点接收的成功响应消息中获取所述呼 叫请求消息的传输路径。
被叫方节点 12包括： 检测单元 121、 消息构造单元 122。 其中， 检测单元 121用于检测被叫方节点接收的呼叫请求消息的类型； 消息构造单元 122用于 在检测单元检测到被叫方节点接收的呼叫请求消息中包含请求被叫方信息的 字段时，将所述呼叫请求消息编辑到被叫方节点发送给主叫方节点的成功响应 消息中。
该系统的工作过程如下：
当主叫方节点需要获取 SIP消息的传输路径时，由测试呼叫单元向被叫方 节点发起测试呼叫， 在该测试呼叫的呼叫请求消息中携带路径信息请求标志。 比如， 前面对本发明方法实施例的描述中提到的 INVITE消息， 在其消息头中 携带路径信息请求标志，以表示要求被叫方返回 SIP消息传输路径信息。另夕卜， 为了不使测试呼叫给被叫方的其他消息处理产生影响， 将 Require 字段的 Supported标头中的 sipdiag字段设置为测试呼叫方式， 以便被叫方节点可以根 据该字段将收到的呼叫请求消息包含在成功响应消息中返回给主叫方。根据实 际需要， 主叫方节点可以定时发起测试呼叫， 也可以周期发起测试呼叫。 被叫方节点收到呼叫请求消息后，由检测单元 121检测被叫方节点接收的 呼叫请求消息的类型， 获取该呼叫请求消息的消息头中的信息。如果检测到主 叫方发送的是测试呼叫， 并请求了路径信息， 则通知消息构造单元 122将该呼 叫请求消息编辑到被叫方节点发送给主叫方节点的成功响应消息中， 比如将 INVITE消息全部或只将 Via字段中的信息编辑到该成功响应消息的消息体中。 然后， 被叫方节点将该成功响应消息发送给主叫方节点。
主叫方节点收到被叫方节点的成功响应消息后， 由路径信息获取单元 112 从该成功响应消息中获取呼叫请求消息的传输路径， 即 INVITE消息中的 Via 字段信息。 这样， 主叫方节点就可以得到呼叫请求消息的传输路径， 从而为网 络运营商对网络的维护提供必要的信息。
图 3是本发明网络节点设备第一实施例的原理框图：
该设备包括： 消息收发单元 31、 呼叫请求消息构造单元 32、 路径信息获 取单元 112、 检测单元 121 , 其中， 消息收发单元 31用于和网络中的其他节点 设备进行消息交互， 向其他节点设备发起测试呼叫， 并接收来自其他节点设备 的成功响应消息； 检测单元 121用于检测消息收发单元接收到的消息类型； 路 径信息获取单元 112用于在检测单元 121检测到成功响应消息后，从该成功响 应消息中获取出消息的传输路径； 呼叫请求消息构造单元 32用于构造消息收 发单元发起测试呼叫所需的呼叫请求消息，并将请求被叫方信息的字段加入到 所述呼叫请求消息中。
除此之外， 在本实施例中， 本发明设备还包括： 响应消息构造单元 33 , 用于在检测单元检测到呼叫请求消息、并且该呼叫请求消息中包含请求被叫方 信息的字段时，构造消息收发单元需要回应的成功响应消息，将呼叫请求消息 全部或部分包含到该成功响应消息中。
该节点设备可以作为主叫方向网络中的其他节点设备发起呼叫，也可以作 为被叫方接收来自网络中其他节点的呼叫。
作为主叫方获取 SIP 消息传输路径或者作为被叫方向其他主叫节点设备 提供 SIP消息传输路径的详细过程如下：
本节点设备需要发起测试呼叫，首先由呼叫请求消息构造单元构造呼叫请 求消息，在构造呼叫请求消息时， 需要将路径信息请求标志加入到该呼叫请求 消息中， 为了保证不对目的节点设备产生影响， 还可以将 INVITE 消息中的 sipdiag 字段设置为测试呼叫方式， 具体实现可参照前面本发明方法实施例中 的描述。 然后， 将构造的呼叫请求消息交给消息收发单元。 消息收发单元向被 叫节点设备发送该呼叫请求消息， 发起测试呼叫。
被叫节点设备的消息收发单元接收到该呼叫请求消息后，由被叫节点设备 的检测单元检测该消息， 如果发现该消息为测试呼叫消息， 并且包含了路径信 息请求标志时， 通知被叫节点设备中的响应消息构造单元构造成功响应消息， 将呼叫请求消息全部或部分包含到该成功响应消息中。 然后，将该成功响应消 息交给消息收发单元，由消息收发单元将该消息回应给发起测试呼叫的节点设 备。
发起测试呼叫的节点设备的消息收发单元接收来自被叫设备的消息，当其 检测单元检测到被叫节点设备回应的成功响应消息后，通知路径信息获取单元 获取该成功响应消息中的呼叫请求消息传输路径信息。这样， 即完成了本次测 试呼叫的目的。
图 4是本发明网络节点设备第二实施例的原理框图：
与图 3所示实施例不同的是， 在该实施例中， 增加了路由存储单元 41和 路由维护单元 42。 其中， 路由存储单元 41用于存储网络中的路由信息； 路由 维护单元 42与路径信息获取单元相连， 用于根据路径信息获取单元获取的呼 叫请求消息的传输路径信息， 更新路由存储单元中存储的路由信息。
在实际应用中， 可以预先设定一些路由更新及优化策略， 以使路由维护单 元 32利用该策略自动更新路由存储单元中存储的路由信息， 保证网络路由的 畅通， 为用户提供更好的服务。
需要说明的是，上述实施例中所述的请求被叫方信息的字段即路径信息请 求标志。
虽然通过实施例描绘了本发明， 本领域普通技术人员知道， 本发明有许多 变形和变化而不脱离本发明的精神，希望所附的权利要求包括这些变形和变化 而不脱离本发明的精神。

Claims

权 利 要 求
1、 一种获取会话起始协议消息传输路径的方法， 其特征在于， 包括以下 步骤：
主叫方发起测试呼叫， 并在呼叫请求消息中携带路径信息请求标志， 所述 标志表示要求被叫方返回会话起始协议消息传输路径信息；
被叫方收到所述呼叫请求消息后根据所述路径信息请求标志，将收到的呼 叫请求消息全部或部分包含在成功响应消息中，并将所述成功响应消息返回给 主叫方；
主叫方根据收到的成功响应消息获取所述呼叫请求消息的传输路径。
2、 根据权利要求 1所述的方法， 其特征在于，
所述呼叫请求消息具体为会话起始协议邀请 INVITE消息 , 所述 INVITE 消息的消息头中带有所述路径信息请求标志。
3、 根据权利要求 2所述的方法， 其特征在于， 所述方法还包括： 在所述 INVITE消息的消息头中设置测试呼叫方式指示信息。
4、 根据权利要求 3所述的方法， 其特征在于， 所述路径信息请求标志使 用 Require字段， 所述测试呼叫方式指示信息使用 sipdiag字段。
5、 根据权利要求 3所述的方法， 其特征在于，
在所述被叫方收到所述呼叫请求消息后向所述主叫方返回成功响应消息 的步骤之前还包括： 所述被叫方获取所述呼叫请求消息的消息头中的 sipdiag 字段信息；
在该 sipdiag字段信息为测试呼叫方式时， 向所述被叫方返回所述成功响 应消息。
6、 根据权利要求 2所述的方法， 其特征在于， 所述被叫方收到所述呼叫 请求消息后向所述主叫方返回成功响应消息之前还包括：
所述被叫方确认所述 Require字段信息中带有所述路径信息请求标志。
7、 根据权利要求 1至 6任一项所述的方法， 其特征在于， 所述成功响应 消息为会话起始协议的 200 OK消息。
8、 根据权利要求 1所述的方法， 其特征在于，
所述被叫方将收到的呼叫请求消息全部或部分包含在所述成功响应消息 的消息体中。
9、 一种获取会话起始协议消息传输路径的系统， 包括： 主叫方节点、 被 叫方节点， 其特征在于，
所述主叫方节点包括：
测试呼叫单元，用于向所述被叫方节点发起测试呼叫， 并在呼叫请求消息 中携带路径信息请求标志；
路径信息获取单元，用于从主叫方节点接收的成功响应消息中获取出所述 呼叫请求消息的传输路径；
所述被叫方节点包括：
检测单元， 用于检测所述被叫方节点接收到的消息类型；
消息构造单元，用于在所述检测单元检测到所述被叫方节点接收的呼叫请 求消息中包含请求被叫方信息的字段时，将所述呼叫请求消息编辑到所述被叫 方节点发送给所述主叫方节点的成功响应消息中。
10、 一种网络节点设备， 其特征在于， 包括： 消息收发单元、 呼叫请求消 息构造单元、 路径信息获取单元、 检测单元， 其中，
消息收发单元，用于和网络中的其他节点设备进行消息交互， 向所述其他 节点设备发起测试呼叫， 并接收来自所述其他节点设备的成功响应消息； 检测单元， 用于检测所述消息收发单元接收到的消息类型；
路径信息获取单元，用于在所述检测单元检测到成功响应消息后，从该成 功响应消息中获取消息的传输路径；
呼叫请求消息构造单元，用于构造所述消息收发单元发起测试呼叫所需的 呼叫请求消息， 并将路径信息请求标志加入到所述呼叫请求消息中。
11、 根据权利要求 10所述的网络节点设备， 其特征在于， 还包括： 响应消息构造单元，用于在所述检测单元检测到呼叫请求消息、并且该呼 叫请求消息中包含所述路径信息请求标志时，构造所述消息收发单元需要回应 的成功响应消息， 并将所述呼叫请求消息编辑到该成功响应消息中。
12、 根据权利要求 10或 11所述的网络节点设备， 其特征在于， 还包括： 路由存储单元， 用于存储网络中的路由信息；
路由维护单元， 与所述路径信息获取单元相连， 用于根据所述路径信息获 取单元获取的呼叫请求消息的传输路径信息 ,更新所述路由存储单元中存储的 路由信息。
PCT/CN2007/070668 2006-12-15 2007-09-11 Procede et systeme d'acquisition du trajet de transmission du message sip WO2008071100A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP07801076A EP2068524A4 (en) 2006-12-15 2007-09-11 A METHOD AND SYSTEM FOR DETERMINING THE TRANSMISSION PATH OF THE SIP MESSAGE
US12/425,704 US20090204715A1 (en) 2006-12-15 2009-04-17 Method and system for acquiring a transmission path of an sip message

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610168029.6 2006-12-15
CN200610168029.6A CN1988546A (zh) 2006-12-15 2006-12-15 获取会话起始协议消息传输路径的方法及系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/425,704 Continuation US20090204715A1 (en) 2006-12-15 2009-04-17 Method and system for acquiring a transmission path of an sip message

Publications (1)

Publication Number Publication Date
WO2008071100A1 true WO2008071100A1 (fr) 2008-06-19

Family

ID=38185180

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/070668 WO2008071100A1 (fr) 2006-12-15 2007-09-11 Procede et systeme d'acquisition du trajet de transmission du message sip

Country Status (4)

Country Link
US (1) US20090204715A1 (zh)
EP (1) EP2068524A4 (zh)
CN (1) CN1988546A (zh)
WO (1) WO2008071100A1 (zh)

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP4999244B2 (ja) * 1999-06-08 2012-08-15 ザ トラスティーズ オブ コロンビア ユニヴァーシティ イン ザ シティ オブ ニューヨーク インターネット電話用のネットワーク電話器具およびシステム
CN1988546A (zh) * 2006-12-15 2007-06-27 华为技术有限公司 获取会话起始协议消息传输路径的方法及系统
CN101931630B (zh) * 2010-09-01 2014-09-10 中兴通讯股份有限公司 一种传输sip消息的方法、用户设备及网元
US8976689B2 (en) * 2011-08-23 2015-03-10 At&T Intellectual Property I, L.P. Methods, systems, and computer program products for monitoring network performance
CN103959715B (zh) * 2011-10-24 2017-03-29 泰科来股份有限公司 用于测试diameter路由节点的方法、系统和装置
KR20130085543A (ko) * 2011-12-19 2013-07-30 한국전자통신연구원 도메인 기반 패킷 포워딩 방법 및 시스템
EP3174266B1 (en) * 2015-11-27 2020-04-08 Vodafone IP Licensing limited Telecommunications system voice call routing

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005236882A (ja) * 2004-02-23 2005-09-02 Nippon Telegr & Teleph Corp <Ntt> 呼接続中継システムにおける呼接続要求中継装置および中継方法、ならびにその動作プログラム
CN1735875A (zh) * 2003-01-03 2006-02-15 诺基亚有限公司 用于在互联网协议多媒体子系统中解析协议无关的方案的方法和设备
CN1988546A (zh) * 2006-12-15 2007-06-27 华为技术有限公司 获取会话起始协议消息传输路径的方法及系统
WO2007087898A1 (en) * 2006-02-01 2007-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Routing media streams from packet switched network to circuit switched network

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
DE60024750D1 (de) * 1999-10-01 2006-01-19 Nortel Networks Ltd Aufbau von Verbindungen über ein Kommunikationsnetzwerk
KR100979073B1 (ko) * 2001-05-15 2010-08-31 아바야 인코포레이티드 자동 통지 및 응답 방법 및 장치
CA2408766A1 (en) * 2001-10-17 2003-04-17 Telecommunications Research Laboratory Content delivery network bypass system
US7283516B1 (en) * 2003-04-07 2007-10-16 At&T Corp. Session initiation protocol (SIP) messages incorporating address and/or routing information obtained from a contact header of a redirect message
US20050180435A1 (en) * 2004-02-17 2005-08-18 Hsu Hung H. Routing protocol device integrated with SIP call server
GB0519524D0 (en) * 2005-09-24 2005-11-02 Ibm Method and apparatus for verifying encryption of SIP signalling
US8472453B2 (en) * 2006-08-16 2013-06-25 Cisco Technology, Inc. Terminal capabilities set exchange between heterogeneous endpoints
US8526314B2 (en) * 2006-08-22 2013-09-03 At&T Intellectual Property I, Lp Methods and apparatus to provide service assurance for communication networks
JP2008104112A (ja) * 2006-10-20 2008-05-01 Fujitsu Ltd 送信経路設定装置、送信経路設定方法および送信経路設定プログラム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1735875A (zh) * 2003-01-03 2006-02-15 诺基亚有限公司 用于在互联网协议多媒体子系统中解析协议无关的方案的方法和设备
JP2005236882A (ja) * 2004-02-23 2005-09-02 Nippon Telegr & Teleph Corp <Ntt> 呼接続中継システムにおける呼接続要求中継装置および中継方法、ならびにその動作プログラム
WO2007087898A1 (en) * 2006-02-01 2007-08-09 Telefonaktiebolaget Lm Ericsson (Publ) Routing media streams from packet switched network to circuit switched network
CN1988546A (zh) * 2006-12-15 2007-06-27 华为技术有限公司 获取会话起始协议消息传输路径的方法及系统

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
ROSENBERG J. ET AL.: "SIP: Session Initiation Protocol", NETWORK WORKING GROUP, RFC 3261, June 2002 (2002-06-01), pages 12 - 16, XP002423186 *
See also references of EP2068524A4 *
SPARKS R.: "Internet Media Type message/sipfrag", NETWORK WORKING GROUP, RFC 3420, November 2002 (2002-11-01), XP015009164 *

Also Published As

Publication number Publication date
US20090204715A1 (en) 2009-08-13
EP2068524A4 (en) 2012-05-02
EP2068524A1 (en) 2009-06-10
CN1988546A (zh) 2007-06-27

Similar Documents

Publication Publication Date Title
JP5363461B2 (ja) グループ呼機能の問い合わせ
US8509393B2 (en) Internet protocol telephony voice/video message deposit and retrieval
JP5529129B2 (ja) 電気通信ネットワーク内の媒体属性に基づく選択的な呼転送のための方法およびシステム
JP5247709B2 (ja) 中間ノードが利用不可能な場合にｓｉｐメッセージを経路指定する方法
US8325707B2 (en) Session initiation from application servers in an IP multimedia subsystem
US20110194554A1 (en) Systems and methods for implementing call pick up using gruu an ims network
WO2008071100A1 (fr) Procede et systeme d&#39;acquisition du trajet de transmission du message sip
WO2006064347A1 (en) Method and system to the instant transfer of multimedia files between mobile radio users within the scope of combinational services
US9246955B2 (en) Capability query handling in a communication network
JP2008148313A (ja) マルチメディア情報の伝送を可能にするための通信チャネルの確立を制御する方法およびシステム
WO2007068206A1 (fr) Procede et reseau de mise en marche d&#39;informations concernant la capacite de session
US20080208993A1 (en) Method For Distributing New Services in an Internet Multimedia Subsystem (Ims), and a Node Adapted Therefore
KR100693038B1 (ko) 브이오아이피 서비스 제공 시스템의 가입자 정보 제공방법 및 장치
WO2007112640A1 (fr) Procédé et appareil de remplacement de l&#39;identification de session, serveur d&#39;application et procédé de remplacement de session
WO2008006311A1 (fr) Procédé et dispositif d&#39;utilisation d&#39;un identificateur de terminal utilisateur
US20080288643A1 (en) Session Initiation Protocol Signalling
Cisco Cisco SIP Proxy Server Call Flows
Cisco Cisco SIP Proxy Server Call Flows
Cisco Cisco SIP Proxy Server (CSPS) Call Flows
WO2008101443A1 (fr) Procédé, système et dispositif pour acquérir un flux multimédia
WO2019129359A1 (en) Method, system and entity for a media transfer session in an ims infrastructure
KR100757535B1 (ko) 어플리케이션 구분이 가능한 멀티미디어 서비스 방법 및장치
WO2009095069A1 (en) Methods, apparatuses, system, and related computer program product for session initiation
US20140143314A1 (en) Communication system
Avgeropoulos Service Policy Management for User-Centric Services in Heterogeneous Mobile Networks

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2007801076

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE