WO2012075934A1 - 消息循环的检测方法、路由代理设备及组网系统 - Google Patents

消息循环的检测方法、路由代理设备及组网系统 Download PDF

Info

Publication number
WO2012075934A1
WO2012075934A1 PCT/CN2011/083564 CN2011083564W WO2012075934A1 WO 2012075934 A1 WO2012075934 A1 WO 2012075934A1 CN 2011083564 W CN2011083564 W CN 2011083564W WO 2012075934 A1 WO2012075934 A1 WO 2012075934A1
Authority
WO
WIPO (PCT)
Prior art keywords
request message
link
message
routing information
sends
Prior art date
Application number
PCT/CN2011/083564
Other languages
English (en)
French (fr)
Inventor
李春生
张丙才
徐斌
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP11846804.0A priority Critical patent/EP2582093B1/en
Publication of WO2012075934A1 publication Critical patent/WO2012075934A1/zh
Priority to US13/787,075 priority patent/US9231856B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/18—Loop-free operations

Definitions

  • the embodiments of the present invention relate to the field of communications technologies, and in particular, to a message loop detection method, a routing proxy device, and a networking system. Background technique
  • the third layer of mobile communication technology (3rd-generation; referred to as the SCTP) or the Transmission Control Protocol (TCP) Diameter protocol is the third generation mobile communication technology (3rd-generation; 3G)
  • PCC Policy and Charging Control
  • LTE Long Term Evolution
  • IMS IP Multimedia Subsystem
  • DRA Diameter Routing Agent
  • DRA Diameter Routing Agent
  • the message loop in the DRA is an important defect affecting the normal service of the network.
  • it is usually necessary to add the peer identifier of the received message when the DRA forwards the message.
  • AVP Route-Record attribute value pair
  • the DRA when the DRA receives a Diameter request message, it first checks whether the Route-Record AVP of the request message has its own identifier. If yes, it indicates that a message loop occurs, and the DRA sends a response message of DIAMETER_LOOP_DETECTED, and the response message is returned to the client (Client) along the original path to inform the client that there is a problem with the path.
  • the above existing message loop detection method can well detect a message loop between three or more DRA devices.
  • DRA1 receives a Diameter request message sent by the client, and sends a Diameter request message to DRA2, and boosts the Route-Record AVP of the Diameter request message.
  • Client ID. DRA2 then sends the Diameter request message to DRA1, and adds the ID of DRAl in the Route-Record AVP of the Diameter request message.
  • the DRA1 detects that the Route-Record AVP has its own identifier.
  • the DRA1 can determine that a message loop occurs.
  • the DRA1 needs to return the DIAMETER_LOOP-DETECTED to the DRA2 along the original path.
  • the response message of the DIAMETER_LOOP_DETECTED is returned to the DRA1 by the DRA2
  • the response message of the DIAMETER_LOOP_DETECTED is returned to the Client by the DRA1.
  • the detection method of the message loop between the two DRAs is less efficient. Summary of the invention
  • the embodiment of the present invention provides a message loop detection method, a routing proxy device, and a networking system, which are used to solve the defect that the processing method of the message loop detection method between the network element device and the routing proxy device in the prior art is low.
  • the embodiment of the invention provides a method for detecting a message loop, which includes:
  • An embodiment of the present invention provides a routing proxy device, including:
  • a receiving module configured to receive a request message sent by the network element device;
  • An acquiring module configured to acquire routing information that sends the request message to the server device, and a detecting module, configured to detect a link of the next hop that sends the request message in the routing information, and receive the request message Whether the link belongs to the same link set;
  • a sending module configured to: when detecting that the link that sends the request message in the routing information and the link that receives the request message belong to the same link set, send a response that detects a message loop to the network element device .
  • the embodiment of the invention further provides a networking system, including: a network element device and a routing proxy device;
  • the network element device is configured to send a request message to the routing proxy device
  • the routing proxy device is configured to receive the request message sent by the network element device, and obtain routing information that sends the request message to a server device, and detect that the routing information is sent by using the request message. Whether the link of one hop belongs to the same link set as the link that receives the request message; when detecting that the link that sends the request message in the routing information belongs to the same link as the link that receives the request message At the time of collection, a response to the detected message loop is sent to the network element device.
  • the method for detecting a message loop, the routing proxy device, and the networking system of the embodiment of the present invention by receiving a request message sent by the network element device, and acquiring routing information for sending the request message to the server device; detecting the sending of the routing information Whether the link of the next hop of the request message and the link receiving the request message belong to the same link set; when detecting the link that sends the request message in the routing information and receives the request message When the link belongs to the same link set, the response to the detected message loop is sent to the network element device.
  • the technical solution of the embodiment of the present invention can improve the detection efficiency of the message loop; thereby reducing the additional signaling load in the networking, reducing signaling congestion, and providing guarantee for the normal service processing of subsequent messages, which is reluctant and practical. Sex. DRAWINGS
  • FIG. 1 is a flowchart of a method for detecting a message loop according to Embodiment 1 of the present invention.
  • FIG. 2 is a flowchart of a method for detecting a message loop according to Embodiment 2 of the present invention.
  • FIG. 3 is a flowchart of a method for detecting a message loop according to Embodiment 3 of the present invention.
  • FIG. 4 is a structural diagram of a network including two DRAs according to Embodiment 4 of the present invention.
  • FIG. 6 is a schematic structural diagram of a routing proxy device according to Embodiment 6 of the present invention.
  • FIG. 7 is a schematic structural diagram of a networking system according to Embodiment 7 of the present invention. detailed description
  • FIG. 1 is a flowchart of a method for detecting a message loop according to Embodiment 1 of the present invention.
  • the execution subject of the message loop detection method of this embodiment is DRA.
  • the method for detecting a message loop in this embodiment may specifically include the following steps:
  • Step 100 Receive a request message sent by the network element device.
  • Step 101 Acquire routing information that sends the request message to the server device.
  • Step 102 Detect whether the link that sends the next hop of the request message in the routing information and the link that receives the request message belong to the same link set.
  • Step 103 When detecting that the next hop link that sends the request message in the routing information belongs to the same link set as the link that receives the request message, send a response that detects the message loop to the network element device.
  • the request message of this embodiment may be a Diameter request message.
  • the Diameter request message may specifically be a request authentication message, or an uplink location message or a request charging message.
  • the DRA receives a Diameter request message sent by a network element device.
  • the DRA obtains routing information from the DRA to send the Diameter request message to the server device (such as Server). And detecting, in the routing information, whether the link that sends the next hop of the Diameter request message and the link that receives the Diameter request message belong to the same link set.
  • the next hop link that sends the request message in the routing information belongs to the same link set as the link that receives the request message, and specifically includes two situations. One is to send the next hop link of the request message and receive the The link of the request message belongs to the same link. In another case, the next hop link that sends the request message and the link that receives the request message belong to different links in the same link set, for example, the next hop link that sends the request message passes the network element.
  • the link between the device and the DRA is sent by the link 1; and the link receiving the Diameter request message sent by the network element device is the link 3 between the network element device and the DRA; Road 3 belongs to different links in the same link set.
  • the link that the DRA receives the Diameter request message is the link between the network element device and the DRA. And determining, by the DRA, the link of the next hop of the Diameter request message sent by the DRA to be the link between the DRA and the network element device, and determining that the acquired routing information is sent in the routing information.
  • the one-hop link belongs to the same link set as the link that receives the Diameter request message.
  • the DRA sends a response to the network element device detecting the message loop. After the network element device receives the response to the detected message loop, the routing information may be re-selected for the Diameter request message, and the alarm signal may be resent or directly sent by the staff to speed up the corresponding Diameter request message.
  • the business is running normally.
  • the method for detecting a message loop in this embodiment can be applied to the detection of a message loop between two network elements.
  • it can be applied to the detection of a message loop between two DRAs in a networking system including two DRAs, and the detection of a message loop between a DRA and a client.
  • the network element device in this embodiment may be a client (Client) or a DRA.
  • the method for detecting a message loop in this embodiment by receiving a Diameter request message sent by the network element device, and acquiring routing information for sending a Diameter request message to the server; detecting a link for transmitting a Diameter request message and receiving a Diameter request message in the routing information Whether the links belong to the same link set, and when they belong to the same link set, send a response to the detected message loop to the network element device.
  • the detection efficiency of the message loop can be improved; thereby reducing the additional signaling load in the networking, reducing signaling congestion, and providing guarantee for the normal service processing of subsequent messages, having [stubborn practicality] Sex.
  • FIG. 2 is a flowchart of a method for detecting a message loop according to Embodiment 2 of the present invention.
  • the application scenario of the message loop detection method in this embodiment is a network composed of two DRAs, a client, and a server.
  • the method for detecting a message loop in this embodiment may specifically include the following steps:
  • Step 200 The first DRA receives a Diameter request message sent by the client.
  • Step 201 The first DRA records the identity of the client that sends the Diameter request message in the Route Record A VP of the Diameter request message; Step 202;
  • Step 202 The first DRA sends the Diameter request message that records the identity of the client to the second DRA. Step 203 is performed;
  • Step 203 The second DRA receives the first DRA to send the Diameter request message, and records that the link that receives the Diameter request message is a link between the first DRA and the second DRA. Step 204 is performed;
  • Step 204 the second DRA obtains the routing information that sends the Diameter request message to the Sever; Step 205;
  • the routing information sent from the second DRA to the server by the Diameter request message is configured when the network is configured.
  • the DRA may detect and obtain routing information corresponding to an available link that sends the Diameter request message.
  • Step 205 The second DRA obtains the next message that sends the Diameter request message from the routing information. Jumping link; performing step 206;
  • Step 206 Detect whether the link that sends the next hop of the Diameter request message in the routing information and the link that receives the Diameter request message belong to the same link set; when belonging to the same link set, perform step 207, otherwise Step 209 is performed when the same link set is not included;
  • the routing information of the second DRA to the Server is two, one is the second DRA ⁇ Server, and the other is the second DRA ⁇ the first DRA ⁇ Server.
  • the second DRA ⁇ Server is preferably routing information.
  • the routing information acquired by the second DRA is the routing information of the second DRA ⁇ the first DRA ⁇ Server.
  • the link of the next hop of the second DRA to send the Diameter request message is a link between the second DRA and the first DRA; therefore, at this time, it may also be detected that the Diameter request information is sent in the routing information.
  • next hop is to be sent to the second DRA; when the next hop for sending the Diameter request information in the routing information is to be sent to the first DRA, determining that the next hop of the Diameter request message is sent in the routing information
  • the link belongs to the same link set as the link that receives the Diameter request message.
  • the route information obtained by the second DRA can only be the second DRA ⁇ Server. At this time, the link of the next hop of the Diameter request message is sent and the Diameter request is received.
  • the links of the messages belong to different link sets.
  • Step 207 Send a response to the first DRA to detect the message loop; perform step 208; Step 208: The first DRA sends a response to the detected message loop to the client;
  • This step is used to send a response to the detected message loop to the Client to inform the Client that a message loop has occurred.
  • the client can re-route the retransmission of the Diameter request message.
  • step 208 may not be performed.
  • the first DRA starts reselecting the route from the first DRA to send the Diameter request message. Or the direct alarm is handled by the staff.
  • Step 209 Determine that there is no message loop between the first DRA and the second DRA.
  • the link continues to be forwarded according to the link in the routing information that sends the next hop of the Diameter request message.
  • Diameter requests messages, of course, you can do other operations.
  • the method for detecting a message loop in this embodiment by receiving a Diameter request message sent by the first DRA, and acquiring routing information for sending a Diameter request message to the server; detecting a link for transmitting a Diameter request message and receiving a Diameter request message in the routing information Whether the links belong to the same link set, when belonging to the same link set, send a response to the detected message loop to the first DRA; and the first DRA sends a response to the detected message loop to the client.
  • the detection efficiency of the message loop can be improved; thereby reducing the additional signaling load in the networking, reducing signaling congestion, and providing guarantee for the normal service processing of subsequent messages, which has a reluctant practicability. .
  • FIG. 3 is a flowchart of a method for detecting a message loop according to Embodiment 3 of the present invention.
  • the application scenario of the message loop detection method in this embodiment is between the DRA and the client.
  • the method for detecting a message loop in this embodiment may specifically include the following steps:
  • Step 300 The client sends a Diameter request message to the DRA.
  • Step 301 The DRA receives a Diameter request message sent by the client, and records a link that receives the Diameter request message.
  • Step 302 The DRA obtains the routing information that sends the Diameter request message to the server.
  • Step 303 The DRA obtains, by the obtained routing information, a link that sends the next hop of the Diameter request message.
  • Step 304 The DRA detects whether the link that sends the next hop of the Diameter request message in the routing information and the link that receives the Diameter request message belong to the same link set; when belonging to the same link set, step 305 is performed, otherwise When not belonging to the same link set, step 306 is performed;
  • the routing information of the DRA to the server may be incorrectly configured, and the configuration is incorrectly configured as DRA ⁇ Client ⁇ Server.
  • the DRA detects the routing information and sends the routing information.
  • the link of the next hop of the Diameter request message is the link of the DRA ⁇ Client.
  • the link of the DRA receiving the Diameter request message is the link between the Client ⁇ DRA. Therefore, it can be determined that the Diameter request message is sent in the routing information.
  • Next hop link with The link receiving the Diameter request message belongs to the same link set.
  • the link corresponding to the next hop that sends the Diameter request message in the routing information and the link that receives the Diameter request message do not belong. The same link set.
  • Step 305 The DRA sends a response to the client that detects the message loop.
  • Step 306 Determine that there is no message loop between the DRA and the Client.
  • the DRA determines that there is no message loop between the DRA and the client, it will continue to forward the Diameter request message according to the link of the next hop in which the Diameter request message is sent in the routing information, and of course, other operations can be performed.
  • the method for detecting a message loop in this embodiment receives the Diameter request message sent by the client, and obtains the routing information that sends the Diameter request message to the server.
  • the link that sends the Diameter request message and the chain that receives the Diameter request message are detected in the routing information. Whether the road belongs to the same link set, when it belongs to the same link set, sends a response to the detected message loop to the client.
  • the detection efficiency of the message loop can be improved; thereby reducing the additional signaling load in the networking, reducing signaling congestion, and providing guarantee for the normal service processing of subsequent messages, having a strong Practicality.
  • FIG. 4 is a structural diagram of a network including two DRAs according to Embodiment 4 of the present invention.
  • the detection method of the message loop of the present invention is described in detail by taking two DRAs in the networking shown in FIG. 4 as an example.
  • the network includes DRA1 and DRA2, as well as the client client and server server.
  • the signaling interaction between them is as follows:
  • Step 1 The client device initiates a Diameter request.
  • Step 2 DRA1 receives the Diameter request from the client and performs message routing.
  • DRA1 For the disaster recovery network consisting of DRA1 and DRA2, there are two routes from DRA1 to Server, namely: Route 1: DRA1 ⁇ Server; Route 2: DRAl ⁇ DRA2 ⁇ Server. Route 1 is the preferred route and Route 2 is the alternate route.
  • Route 1 is the preferred route
  • Route 2 is the alternate route.
  • DRA1 finds that the link of route 1 is unavailable (such as if the data configuration error is unavailable or the link is unavailable due to the broken link)
  • the alternate route 2 is selected.
  • DRA1 The Diameter request is sent to DRA2 according to alternate route 2.
  • Step 3 After receiving the Diameter request from DRA1, DRA2 records the Diameter link (DRA1 ⁇ S DRA2) that received the message.
  • the message routing is performed.
  • route 1 DRA2 ⁇ Server
  • route 2 DRA2 ⁇ DRA 1 ⁇ Server.
  • Route 1 is the preferred route and Route 2 is the alternate route.
  • DRA2 finds that the route of route 1 is unavailable (such as data configuration error leading to unavailable or broken link leading to route unavailability), select alternate route 2.
  • DRA2 can detect that the next hop link of the alternate route 2 is DRA2 ⁇ DRA1.
  • the DRA2 record receives the Diameter request and the link is DRA1 ⁇ DRA2.
  • the two links can be found to be the same. Therefore DRA2 can determine that a message loop has occurred between DRA1 and DRA2 at this time.
  • DRA2 returns to DRA1 the Diameter response that detected the message loop.
  • the error code in the Diameter response of the message loop is detected as Loop-Detect or Unable-To-Deliver.
  • Step 4 The DRA1 receives the Diameter response of the detected message loop from DRA2, and receives the Loop-Detect response, and sends the Loop-Detect response to the Client to inform the Client.
  • the method for detecting the message loop in this embodiment can be applied to a basic networking including two DRA devices, and has high practicability.
  • the method for detecting the message loop of the embodiment can reduce the interaction between the two DRAs, and send the response of detecting the message loop to the client as soon as possible; thus, the detection efficiency of the message loop can be improved; Therefore, the additional signaling load in the networking is reduced, the signaling congestion is reduced, and the normal service processing of the subsequent messages is guaranteed, which has strong practicability.
  • FIG. 5 is a schematic structural diagram of a routing proxy device according to Embodiment 5 of the present invention.
  • the routing proxy device in this embodiment may also be referred to as a message routing proxy device, and may specifically be a DRA.
  • the routing proxy device of this embodiment may specifically include: a receiving module 10, an obtaining module 11, a detecting module 12, and a sending module 13.
  • the receiving module 10 in the routing proxy device of the embodiment is configured to receive a request message sent by the network element device.
  • the obtaining module 11 is connected to the receiving module 10, and the obtaining module 11 is configured to obtain routing information for sending the request message received by the receiving module 10 to the server device.
  • the detection module 12 is connected to the acquisition module 11. The detection module 12 is configured to detect whether the link of the next hop that sends the request message in the routing information acquired by the acquisition module 11 and the link that receives the request message belong to the same link set.
  • the sending module 13 is connected to the detecting module 12, and the sending module 13 is configured to: when the detecting module 12 detects that the next hop link that sends the request message in the routing information belongs to the same link set, and the link that receives the request message belongs to the same link set, The network element device sends a response that detects a message loop.
  • the routing agent device in this embodiment is the same as the detection mechanism of the message loop in the foregoing method, and the description of the related method is not described here.
  • the request message in this embodiment may be a Diameter request message.
  • the detection module 12 detects that the next hop link that sends the request message in the routing information belongs to the same link set as the link that receives the request message, and specifically includes two cases. For details, refer to the description of the foregoing related method embodiments.
  • the routing proxy device in this embodiment implements the request message sent by the receiving network element device by using the foregoing module, and obtains the routing information that sends the request message to the server; detects the link in the routing information that sends the request message, and receives the request. Whether the link of the message belongs to the same link set, and when belonging to the same link set, sends a response to the detected message loop to the network element device.
  • the detection efficiency of the message loop can be improved; thereby reducing the additional signaling load in the networking, reducing signaling congestion, and providing guarantee for the normal service processing of subsequent messages, and having four reluctances. Sex.
  • FIG. 6 is a schematic structural diagram of a routing proxy device according to Embodiment 6 of the present invention.
  • the routing proxy device of the embodiment may further include the recording module 14 on the basis of the routing proxy device shown in the fifth embodiment.
  • the recording module 14 is connected to the receiving module 10, and the recording module 14 is configured to record the link of the request message received by the receiving module 10.
  • the obtaining module 11 is further configured to: after obtaining the routing information that is sent by the receiving module 10 to the server device, obtain the link that sends the next hop of the request message from the obtained routing information.
  • the detecting module 12 can be connected to the recording module 14 and the obtaining module 11, respectively.
  • the detecting module 12 is configured to detect, by the acquiring module 11, the link that sends the next hop of the request message and whether the link recorded by the recording module 14 that receives the request message belongs to the same link set.
  • the receiving module 10 receives the request message sent by the network element device.
  • the network element device here may also be a routing proxy device, and may also be a client (client).
  • the routing agent device in this embodiment is the same as the detection mechanism of the message loop in the foregoing method, and the description of the related method is not described here.
  • the routing proxy device in this embodiment implements the detection of the message loop by using the foregoing module, which can improve the detection efficiency of the message loop; thereby reducing the additional signaling load in the networking and reducing signaling congestion, which is a normal service for subsequent messages.
  • the treatment provides a guarantee and is highly practical.
  • the detecting module 12 in the foregoing embodiment may be further configured to detect whether the next hop that sends the request information in the routing information acquired by the acquiring module 11 is to be sent to the network element device; for example, when the The link of the next hop of the request message can obtain the destination network element to be sent of the next hop that sends the request message.
  • the next hop for sending the request information in the routing information acquired by the obtaining module 11 is to be sent to the network element device, it is determined that the link that sends the request message in the routing information belongs to the same chain as the link that receives the request message. Road set.
  • FIG. 7 is a schematic structural diagram of a networking system according to Embodiment 7 of the present invention.
  • the networking system of this embodiment may specifically include a network element device 20 and a routing proxy device 30.
  • Network element setting The device 20 is in communication with the routing agent device 30.
  • the network element device 20 is configured to send a request message to the routing proxy device 30, and the request message may be a Diameter request message.
  • the routing proxy device 30 is configured to receive the request message sent by the network element device 20, and obtain routing information that sends the request message to the server device; and detect the link of the next hop that sends the request message in the obtained routing information. Whether the link that receives the request message belongs to the same link set; when detecting that the next hop link that sends the request message in the routing information belongs to the same link set as the link that receives the request message, Metadevice 20 sends a response that detects a message loop.
  • the networking system of this embodiment can be used to detect whether there is a message loop between the network element device 20 and the routing proxy device 30.
  • the network element device 20 may specifically be a client device or another routing agent device.
  • the networking system of the present embodiment is not limited to include only the network element device 20 and the routing proxy device 30, and may include, for example, a server device.
  • the networking system of this embodiment may further include other routing proxy devices and other network element devices.
  • the networking system of the embodiment can improve the detection efficiency of the message loop by adopting the foregoing routing proxy device, thereby reducing the additional signaling load in the networking, reducing signaling congestion, and providing guarantee for the normal service processing of subsequent messages. , with ⁇ [stubborn practicality.
  • the device embodiments described above are merely illustrative, wherein the units illustrated as separate components may or may not be physically separate, and the components displayed as units may or may not be physical units, ie may be located in one place. , or it can be distributed to at least two network elements. Some or all of the modules may be selected according to actual needs to achieve the objectives of the embodiment. Those of ordinary skill in the art can understand and implement without undue creative work.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

消息循环的检测方法、 路由代理设备及组网系统 本申请要求了 2010年 12月 7日提交的、申请号为 201010590396.1、 发明名称为 "消息循环的检测方法、 路由代理设备及组网系统" 的中国申 请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明实施例涉及通信技术领域， 尤其涉及一种消息循环的检测方法、 路由代理设备及组网系统。 背景技术
底层十办议使用；巟控制传输十办议 ( Stream Control Transmission Protocol; 简称 SCTP )或者传输控制协议（ Transmission Control Protocol: 简称 TCP ) 的 Diameter协议， 是第三代移动通信技术 （ 3rd-generation; 简称 3G ) 网 络的策略和计费控制 （ Policy and Charging Control； 简称 PCC )架构以及 长期演进 （Long Term Evolution; 简称 LTE ) 、 IP 多媒体子系统 （IP Multimedia Subsystem; 简称 IMS ) 网络中广泛应用的协议。 在 Diameter 协议中， Diameter路由代理 （ Diameter Routing Agent; 以下简称 DRA ) 提供 Diameter信令的消息路由功能， 通过部署 DRA组成下一代的信令网 络。
在信令网中， DRA中的消息循环是影响网络正常业务的一个重要缺陷。 为了防止消息循环， 通常在 DRA在转发消息的时候， 需要将接收的消息的 对端标识添力。到消息的路由记录（Route-Record )属性值对 ( Attribute Value Pair; 以下简称 AVP ) 中， 在 DRA接收到一个 Diameter请求消息时， 先检 查请求消息的 Route-Record AVP中是否有自己的标识， 如有则表示发生消息 循环， DRA发送 DIAMETER— LOOP— DETECTED的响应消息， 该响应消息 沿原路返回至客户端 （Client ) , 以告知 Client该路径出现问题。 上述现有的消息循环的检测方法能够良好的检测到 3个以上的 DRA设 备之间的消息循环。 但是对于两个 DRA设备之间的消息循环， 例如 DRA1 接收 Client发送的 Diameter请求消息，并将 Diameter请求消息发送给 DRA2, 并在该 Diameter请求消息的 Route-Record AVP中增力。 Client标识。 DRA2再 将该 Diameter 请求消息发送给 DRA1 , 并在该 Diameter 请求消息的 Route-Record AVP中增加 DRAl的标识。当 DRA1接收到该 Diameter请求消 息后， 检测发现 Route-Record AVP中有自身的标识， 这样， DRA1可以判断 出现了消息循环 , 此时 DRA1 需要沿着原路径先向 DRA2 返回 DIAMETER— LOOP— DETECTED 的 响 应 消 息 ， 再 由 DRA2 将该 DIAMETER— LOOP— DETECTED的响应消息再返回给 DRA1 , 再由 DRA1将 DIAMETER— LOOP— DETECTED的响应消息返回给 Client。 这中在两个 DRA 之间的消息循环的检测方法的处理效率较低。 发明内容
本发明实施例提供一种消息循环的检测方法、路由代理设备及组网系统， 用以解决现有技术中网元设备与路由代理设备之间的消息循环的检测方法的 处理效率较低的缺陷。 本发明实施例提供一种消息循环的检测方法， 包括：
接收网元设备发送的请求消息；
获取将所述请求消息发送至服务端设备的路由信息；
检测所述路由信息中发送所述请求消息的下一跳的链路与接收所述请求 消息的链路是否属于同一链路集；
当检测到所述路由信息中发送所述请求消息的链路与接收所述请求消息 的链路属于同一链路集时， 向所述网元设备发送检测到消息循环的响应。 本发明实施例提供一种路由代理设备， 包括：
接收模块， 用于接收网元设备发送的请求消息； 获取模块， 用于获取将所述请求消息发送给服务端设备的路由信息； 检测模块， 用于检测所述路由信息中发送所述请求消息的下一跳的链路 与接收所述请求消息的链路是否属于同一链路集；
发送模块， 用于当检测到所述路由信息中发送所述请求消息的链路与 接收所述请求消息的链路属于同一链路集时， 向所述网元设备发送检测到 消息循环的响应。
本发明实施例还提供一种组网系统， 包括： 包括网元设备和路由代理设 备；
所述网元设备， 用于向所述路由代理设备发送请求消息；
所述路由代理设备， 用于接收所述网元设备发送的所述请求消息， 并获 取将所述请求消息发送给服务端设备的路由信息； 检测所述路由信息中发送 所述请求消息的下一跳的链路与接收所述请求消息的链路是否属于同一链路 集； 当检测到所述路由信息中发送所述请求消息的链路与接收所述请求消息 的链路属于同一链路集时， 向所述网元设备发送检测到消息循环的响应。
本发明实施例的消息循环的检测方法、 路由代理设备及组网系统， 通过 接收网元设备发送的请求消息， 并获取将请求消息发送至服务端设备的路由 信息； 检测所述路由信息中发送所述请求消息的下一跳的链路与接收所述请 求消息的链路是否属于同一链路集； 当检测到所述路由信息中发送所述请求 消息的链路与接收所述请求消息的链路属于同一链路集时， 向所述网元设备 发送检测到消息循环的响应。 采用本发明实施例的技术方案， 能够提高消息 循环的检测效率； 从而减少组网中额外的信令负荷， 减少信令拥塞， 为后续 消息的正常业务的处理提供了保证， 具有艮强的实用性。 附图说明
为了更清楚地说明本发明实施例或现有技术中的技术方案， 下面将对实 施例或现有技术描述中所需要使用的附图作一简单地介绍， 显而易见地， 下 面描述中的附图是本发明的一些实施例， 对于本领域普通技术人员来讲， 在 不付出创造性劳动性的前提下， 还可以根据这些附图获得其他的附图。
图 1为本发明实施例一提供的消息循环的检测方法的流程图。
图 2为本发明实施例二提供的消息循环的检测方法的流程图。
图 3为本发明实施例三提供的消息循环的检测方法的流程图。
图 4为本发明实施例四提供的包括两个 DRA的组网结构图。 图 6为本发明实施例六提供的路由代理设备的结构示意图。
图 7为本发明实施例七提供的组网系统的结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案和优点更加清楚， 下面将结合本发 明实施例中的附图， 对本发明实施例中的技术方案进行清楚、 完整地描述， 显然， 所描述的实施例是本发明一部分实施例， 而不是全部的实施例。 基于 本发明中的实施例， 本领域普通技术人员在没有作出创造性劳动前提下所获 得的所有其他实施例， 都属于本发明保护的范围。
图 1为本发明实施例一提供的消息循环的检测方法的流程图。 本实施例 的消息循环的检测方法的执行主体为 DRA。 如图 1所示， 本实施例的消息循 环的检测方法， 具体可以包括如下步骤：
步骤 100、 接收网元设备发送的请求消息；
步骤 101、 获取将该请求消息发送给服务端设备的路由信息；
步骤 102、 检测该路由信息中发送该请求消息的下一跳的链路与接收该 请求消息的链路是否是属于同一链路集；
步骤 103、 当检测到该路由信息中发送该请求消息的下一跳链路与接收 该请求消息的链路属于同一链路集时， 向该网元设备发送检测到消息循环的 响应。 具体地，本实施例的请求消息可以为 Diameter请求消息。该 Diameter请 求消息具体可以为请求鉴权消息、或者为上^艮位置消息或者为请求计费消息。 该 DRA接收一网元设备发送的 Diameter请求消息。 然后该 DRA获取从该 DRA将该 Diameter请求消息发送给服务端设备 (如 Server )的路由信息。 并 检测该路由信息中发送该 Diameter 请求消息的下一跳的链路与接收该 Diameter请求消息的链路是否属于同一链路集。 其中该路由信息中发送该请 求消息的下一跳链路与接收该请求消息的链路属于同一链路集具体包括两种 情况， 一种是发送该请求消息的下一跳链路与接收该请求消息的链路属于同 一链路。 另一种情况是， 发送该请求消息的下一跳链路与接收该请求消息的 链路属于同一链路集中的不同链路， 例如发送该请求消息的下一跳链路是通 过该网元设备与该 DRA之间的链路 1发出的； 而接收该网元设备发出的该 Diameter请求消息的链路为该网元设备与该 DRA之间的链路 3； 此时链路 1 和链路 3属于同一链路集中的不同链路。
本实施例中 DRA接收 Diameter请求消息的链路为该网元设备→ DRA之 间的链路。 当 DRA检测获取的该路由信息中发送该 Diameter请求消息的下 一跳的链路为该 DRA→该网元设备之间的链路， 可以确定获取的该路由信息 中发送该 Diameter请求消息的下一跳的链路与接收该 Diameter请求消息的 链路属于同一链路集。 此时， DRA向网元设备发送检测到消息循环的响应。 具体地网元设备接收到该检测到消息循环的响应之后，可以为该 Diameter请 求消息重新选择路由信息， 并重新发送或者直接发出报警信号， 由工作人员 进行处理， 以加快该 Diameter请求消息对应的业务正常运行。
本实施例中的消息循环的检测方法， 可以适用两个网元之间的消息循环 的检测。 例如可以应用于包括两个 DRA的组网系统中两个 DRA之间消息循 环的检测， 以及一个 DRA与客户端 （ Client )之间的消息循环的检测。 也就 是说本实施例中的网元设备具体可以为客户端 （Client ) 或者还可以为一个 DRA。 本实施例的消息循环的检测方法 , 通过接收网元设备发送的 Diameter请 求消息， 并获取将 Diameter请求消息发送给 Server的路由信息； 检测路由信 息中发送 Diameter请求消息的链路与接收 Diameter请求消息的链路是否属于 同一链路集， 当属于同一链路集时， 向该网元设备发送检测到消息循环的响 应。 采用本实施例的技术方案， 能够提高消息循环的检测效率； 从而减少组 网中额外的信令负荷， 减少信令拥塞， 为后续消息的正常业务的处理提供了 保证， 具有 [艮强的实用性。
图 2为本发明实施例二提供的消息循环的检测方法的流程图。 本实施例 的消息循环的检测方法的应用场景为两个 DRA、一个 Client和一个 Server构 成的组网中。 如图 2所示， 本实施例的消息循环的检测方法， 具体可以包括 如下步骤：
步骤 200、 第一 DRA接收 Client发送的 Diameter请求消息； 执行步骤
201 ;
步骤 201、 第一 DRA在该 Diameter请求消息的 Route Record A VP中记 录发送该 Diameter请求消息的该 Client的标识； 执行步骤 202;
步骤 202、第一 DRA将记录有该 Client的标识的该 Diameter请求消息发 送至第二 DRA; 执行步骤 203 ;
步骤 203、 第二 DRA接收该第一 DRA发送该 Diameter请求消息， 并记 录接收该 Diameter请求消息的链路为第一 DRA→第二 DRA之间的链路； 执 行步骤 204;
步骤 204、 第二 DRA获取将该 Diameter请求消息发送给 Sever的路由信 息； 执行步骤 205;
从该第二 DRA将该 Diameter请求消息发送给 Server的路由信息是组网 时配置好的。 该 DRA在发送该 Diameter请求消息之前， 可以检测并获取到 发送该 Diameter请求消息的可用的链路对应的路由信息。
步骤 205、第二 DRA从路由信息中获取发送该 Diameter请求消息的下一 跳的链路； 执行步骤 206;
步骤 206、 检测该路由信息中发送该 Diameter请求消息的下一跳的链路 与接收该 Diameter请求消息的链路是否属于同一链路集； 当属于同一链路集 时， 执行步骤 207、 否则当不属于同一链路集时， 执行步骤 209;
因为本实施例中仅包括两个 DRA, 第二 DRA到 Server的路由信息由两 条， 一条是第二 DRA→ Server, 另一条为第二 DRA→第一 DRA→ Server。 其 中第二 DRA→ Server为优选地路由信息。 当第二 DRA到 Server的路由不可 用时， 第二 DRA获取的路由信息是第二 DRA→第一 DRA→ Server的路由信 息。 此时第二 DRA发送该 Diameter请求消息的下一跳的链路是第二 DRA→ 第一 DRA之间的链路；所以，此时，也可以是检测该路由信息中发送该 Diameter 请求信息的下一跳是否要发送至第二 DRA; 当该路由信息中发送该 Diameter 请求信息的下一跳是要发送至该第一 DRA , 则确定该路由信息中发送该 Diameter请求消息的下一跳的链路与接收该 Diameter请求消息的链路属于同 一链路集。 当第二 DRA到 Server的路由可用时， 此时， 第二 DRA获取到的 路由信息只能是第二 DRA→ Server, 此时发送该 Diameter请求消息的下一跳 的链路与接收该 Diameter请求消息的链路属于不同链路集。
步骤 207、 向第一 DRA发送检测到消息循环的响应； 执行步骤 208; 步骤 208、 第一 DRA将该检测到消息循环的响应发送给该 Client;
该步骤用于将该检测到消息循环的响应发送给 Client,以告知 Client发生 消息循环。 Client可以对该 Diameter请求消息重新选择路由重新发送。 实际 使用中， 也可以不进行步骤 208, 直接在步骤 207之后， 第一 DRA接收到该 检测到消息循环的响应之后，从第一 DRA开始重新选择路由发送该 Diameter 请求消息。 或者直接报警由工作人员做相应的处理。
步骤 209、 确定第一 DRA和第二 DRA之间没有消息循环。
例如， 当第二 DRA确定第一 DRA和第二 DRA之间没有消息循环时， 则会按照该路由信息中发送该 Diameter请求消息的下一跳的链路继续转发该 Diameter请求消息， 当然也可以做其他的操作。
本实施例的消息循环的检测方法， 通过接收第一 DRA发送的 Diameter 请求消息， 并获取将 Diameter请求消息发送给 Server的路由信息； 检测路由 信息中发送 Diameter请求消息的链路与接收 Diameter请求消息的链路是否属 于同一链路集， 当属于同一链路集时， 向第一 DRA发送检测到消息循环的响 应； 并由第一 DRA将检测到消息循环的响应发送给客户端。采用本实施例的 技术方案， 能够提高消息循环的检测效率； 从而减少组网中额外的信令负荷， 减少信令拥塞， 为后续消息的正常业务的处理提供了保证， 具有艮强的实用 性。
图 3为本发明实施例三提供的消息循环的检测方法的流程图。 本实施例 的消息循环的检测方法的应用场景为在 DRA和 Client之间。如图 3所示， 本 实施例的消息循环的检测方法， 具体可以包括如下步骤：
步骤 300、 Client向 DRA发送 Diameter请求消息；
步骤 301、 DRA接收该 Client发送的 Diameter请求消息； 并记录接收该 Diameter请求消息的链路；
步骤 302、 DRA获取将该 Diameter请求消息发送给 Server的路由信息； 步骤 303、 DRA从获取的路由信息中获取发送该 Diameter请求消息的下 一跳的链路；
步骤 304、 DRA检测该路由信息中发送该 Diameter请求消息的下一跳的 链路与接收该 Diameter请求消息的链路是否属于同一链路集； 当属于同一链 路集时， 执行步骤 305、 否则当不属于同一链路集时， 执行步骤 306;
具体地， 当组网中预先配置的路由信息有误的时候， 可能会误将该 DRA 到 Server的路由信息，错误的配置为 DRA→ Client— → Server„此时 DRA 检测该路由信息中发送该 Diameter请求消息的下一跳的链路是 DRA→ Client 的链路。 而 DRA接收该 Diameter请求消息的链路是 Client→ DRA之间的链 路。 因此可以判断该路由信息中发送该 Diameter请求消息的下一跳的链路与 接收该 Diameter请求消息的链路属于同一链路集。 当组网中预先配置的路由 信息正确的时候， 通常为不会出现上述情况， 对应着该路由信息中发送该 Diameter请求消息的下一跳的链路与接收该 Diameter请求消息的链路不属于 同一链路集。
步骤 305、 DRA向 Client发送检测到消息循环的响应；
步骤 306、 确定 DRA和 Client之间没有消息循环。
例如 , 当 DRA确定 DRA和 Client之间没有消息循环时 , 则会按照该路 由信息中发送该 Diameter请求消息的下一跳的链路继续转发该 Diameter请求 消息， 当然也可以做其他的操作。
本实施例的消息循环的检测方法， 通过接收 Client发送的 Diameter请求 消息， 并获取将 Diameter请求消息发送给 Server的路由信息； 检测路由信息 中发送 Diameter请求消息的链路与接收 Diameter请求消息的链路是否属于同 一链路集， 当属于同一链路集时， 向 Client发送检测到消息循环的响应。 采 用本实施例的技术方案， 能够提高消息循环的检测效率； 从而减少组网中额 外的信令负荷， 减少信令拥塞， 为后续消息的正常业务的处理提供了保证， 具有 ^[艮强的实用性。
图 4为本发明实施例四提供的包括两个 DRA的组网结构图。 这里以图 4 所示的组网中的两个 DRA为例详细描述本发明的消息循环的检测方法。
如图 4所示， 该组网中包括 DRA1和 DRA2, 以及客户端 Client和服务 器 Server。 它们之间的信令交互具体为如下步骤：
步骤 1、 Client设备发起一个 Diameter请求；
步骤 2、 DRA1接收来自 Client的 Diameter请求， 进行消息选路， 对于 DRA1和 DRA2组成的容灾组网， DRA1到 Server的路由有 2条， 分别是： 路由 1 : DRA1→ Server; 路由 2: DRAl→DRA2→ Server。 其中路由 1是优选 路由， 路由 2是备用路由。 当 DRA1发现路由 1的链路不可用时 (；具体如数据 配置错误导致不可用或者断链导致路由不可用），选择备用路由 2。然后 DRA1 按照备用路由 2将 Diameter请求发送到 DRA2。
步骤 3、 DRA2接收来自 DRA1的 Diameter请求之后， 记录接收该消息 的 Diameter链路 (DRA1→S DRA2)。 并进行消息选路， 对于 DRA1和 DRA2 组成的容灾组网， DRA2到 Server的路由有 2条， 分别是： 路由 1 : DRA2→ Server; 路由 2: DRA2→ DRA 1→ Server。
其中路由 1是优选路由， 路由 2是备用路由。 当 DRA2发现路由 1的链 路不可用时 (具体如数据配置错误导致不可用或者断链导致路由不可用），选择 备用路由 2。 但是 DRA2选路备用路由 2之后， DRA 2可以检测到该备用路 由 2的下一跳链路为 DRA2→DRA1。 而 DRA2记录的接收该 Diameter请求 得链路为 DRA1→DRA2。 经对比可以发现这两条链路相同。 因此 DRA2可以 确定此时在 DRA1和 DRA2之间出现了消息循环。此时 DRA2向 DRA1返回 检测到消息循环的 Diameter响应。 具体地， 检测到消息循环的 Diameter响应 中的错误码为循环检测到（Loop-Detect )或者无法路由（ Unable-To-Deliver )。
步骤 4、 DRA1接收来自 DRA2的检测到消息循环的 Diameter响应如接 收到 Loop-Detect响应 , 将该 Loop-Detect响应发送至 Client, 以告知 Client。
由上述分析可知， 本实施例的消息循环的检测方法可以适用于包括两个 DRA设备的基本组网中， 具有较高的实用性。
本实施例的消息循环的检测方法， 与现有技术相比， 能够减少在两个 DRA之间的交互， 尽快地将检测到消息循环的响应发送给 Client; 因此能够 提高消息循环的检测效率； 从而减少组网中额外的信令负荷， 减少信令拥塞， 为后续消息的正常业务的处理提供了保证， 具有艮强的实用性。
本领域普通技术人员可以理解： 实现上述方法实施例的全部或部分步骤 可以通过程序指令相关的硬件来完成， 前述的程序可以存储于一计算机可读 取存储介质中， 该程序在执行时， 执行包括上述方法实施例的步骤； 而前述 的存储介质包括： ROM、 RAM, 磁碟或者光盘等各种可以存储程序代码的介 图 5为本发明实施例五提供的路由代理设备的结构示意图。 本实施例的 路由代理设备也可以称之为消息路由代理设备， 例如具体可以为 DRA。 本实 施例的路由代理设备， 具体可以包括： 接收模块 10、 获取模块 11、 检测模块 12和发送模块 13。
本实施例的路由代理设备中的接收模块 10 用于接收网元设备发送的请 求消息。 获取模块 11与接收模块 10连接， 获取模块 11用于获取将接收模块 10接收的请求消息发送给服务端设备的路由信息。 检测模块 12与获取模块 11连接， 检测模块 12用于检测获取模块 11获取的路由信息中发送该请求消 息的下一跳的链路与接收该请求消息的链路是否属于同一链路集。 发送模块 13与检测模块 12连接， 发送模块 13用于当检测模块 12检测到该路由信息 中发送该请求消息的下一跳链路与接收该请求消息的链路属于同一链路集 时， 向该网元设备发送检测到消息循环的响应。
本实施例的路由代理设备， 通过采用上述模块实现对消息循环的检测与 上述相关方法实施例中实现消息循环的检测机制相同， 详细可参考上述相关 方法实施例的记载， 在此不再贅述。
本实施例中的请求消息可以为 Diameter请求消息。 其中检测模块 12检 测该路由信息中发送该请求消息的下一跳链路与接收该请求消息的链路属于 同一链路集具体包括两种情况， 详细参考上述相关方法实施例的记载。
本实施例的路由代理设备， 通过采用上述模块实现接收网元设备发送的 请求消息， 并获取将该请求消息发送给 Server的路由信息； 检测路由信息中 发送该请求消息的链路与接收该请求消息的链路是否属于同一链路集， 当属 于同一链路集时， 向该网元设备发送检测到消息循环的响应。 采用本实施例 的技术方案， 能够提高消息循环的检测效率； 从而减少组网中额外的信令负 荷， 减少信令拥塞， 为后续消息的正常业务的处理提供了保证， 具有 4艮强的 实用性。
图 6为本发明实施例六提供的路由代理设备的结构示意图。如图 6所示， 本实施例的路由代理设备在上述实施例五所示的路由代理设备的基础上， 具 体还可以包括记录模块 14。 该记录模块 14与接收模块 10连接， 记录模块 14 用于记录接收模块 10接收的该请求消息的链路。
其中获取模块 11还用于在获取将接收模块 10接收的请求消息发送给服 务端设备的路由信息之后， 进一步从获取的路由信息中获取发送该请求消息 下一跳的链路。此时检测模块 12可以分别与记录模块 14和获取模块 11连接。 检测模块 12用于检测获取模块 11获取的发送该请求消息下一跳的链路与记 录模块 14记录的接收该请求消息的链路是否属于同一链路集。 发送模块 13 的执行详见上述实施例的记载， 在此不再贅述。
需要说明的是，上述实施例中接收模块 10接收网元设备发送的的请求消 息。 这里的网元设备具体也可以为一个路由代理设备， 还可以为一个客户端 ( Client ) 。
本实施例的路由代理设备， 通过采用上述模块实现对消息循环的检测与 上述相关方法实施例中实现消息循环的检测机制相同， 详细可参考上述相关 方法实施例的记载， 在此不再贅述。
本实施例的路由代理设备， 通过采用上述模块实现对消息循环的检测， 能够提高消息循环的检测效率； 从而减少组网中额外的信令负荷， 减少信令 拥塞， 为后续消息的正常业务的处理提供了保证， 具有很强的实用性。
需要说明的是，上述实施例中的检测模块 12具体还可以用于检测获取模 块 11获取的路由信息中发送该请求信息的下一跳是否要发送至该网元设备； 例如当获取到发送该请求消息下一跳的链路， 便可以获取到发送该请求消息 的下一跳的要发送的目的网元。 当获取模块 11获取的路由信息中发送该请求 信息的下一跳是要发送至该网元设备， 则确定该路由信息中发送该请求消息 的链路与接收该请求消息的链路属于同一链路集。
图 7为本发明实施例七提供的组网系统的结构示意图。 如图 7所示， 本 实施例的组网系统， 具体可以包括网元设备 20和路由代理设备 30。 网元设 备 20与路由代理设备 30通信连接。
其中该网元设备 20用于向路由代理设备 30发送请求消息， 请请求消息 可以为 Diameter请求消息。 路由代理设备 30用于接收该网元设备 20发送的 该请求消息， 并获取将该请求消息发送给服务端设备的路由信息； 检测获取 的路由信息中发送该请求消息的下一跳的链路与接收该请求消息的链路是否 属于同一链路集； 当检测到该路由信息中发送该请求消息的下一跳链路与接 收该请求消息的链路属于同一链路集时，向该网元设备 20发送检测到消息循 环的响应。
检测， 详细可参考上述相关实施例的记载， 在此不再贅述。
本实施例的组网系统可以用于检测网元设备 20和路由代理设备 30之间 否存在消息循环。该网元设备 20具体可以为客户端设备或者为另一个路由代 理设备。但是并不限制本实施例的组网系统中仅包括网元设备 20和路由代理 设备 30, 例如可以包括服务端设备。 具体根据实际需求， 本实施例的组网系 统中还可以包括其他路由代理设备等等网元设备。
本实施例的组网系统， 通过采用上述路由代理设备， 能够提高消息循环 的检测效率； 从而减少组网中额外的信令负荷， 减少信令拥塞， 为后续消息 的正常业务的处理提供了保证， 具有 ^[艮强的实用性。
以上所描述的装置实施例仅仅是示意性的， 其中作为分离部件说明的单 元可以是或者也可以不是物理上分开的， 作为单元显示的部件可以是或者也 可以不是物理单元， 即可以位于一个地方， 或者也可以分布到至少两个网络 单元上。 可以根据实际的需要选择其中的部分或者全部模块来实现本实施例 方案的目的。 本领域普通技术人员在不付出创造性的劳动的情况下， 即可以 理解并实施。
最后应说明的是： 以上实施例仅用以说明本发明的技术方案， 而非对其 限制； 尽管参照前述实施例对本发明进行了详细的说明， 本领域的普通技术 人员应当理解： 其依然可以对前述各实施例所记载的技术方案进行修改， 或 者对其中部分技术特征进行等同替换； 而这些修改或者替换， 并不使相应技 术方案的本质脱离本发明各实施例技术方案的精神和范围。

Claims

权 利 要 求 书
1、 一种消息循环的检测方法， 其特征在于， 包括：
接收网元设备发送的请求消息；
获取将所述请求消息发送至服务端设备的路由信息；
检测所述路由信息中发送所述请求消息的下一跳的链路与接收所述请求 消息的链路是否属于同一链路集；
当检测到所述路由信息中发送所述请求消息的下一跳链路与接收所述请 求消息的链路属于同一链路集时， 向所述网元设备发送检测到消息循环的响 应。
2、 根据权利要求 1所述的消息循环的检测方法， 其特征在于， 还包括： 记录接收所述请求消息的链路。
3、 根据权利要求 1或 2所述的消息循环的检测方法， 其特征在于， 还包 括：
从所述路由信息中获取发送所述请求消息的下一跳的链路。
4、 根据权利要求 3所述的消息循环的检测方法， 其特征在于， 所述检测 所述路由信息中发送所述请求消息的下一跳的链路与接收所述请求消息的链 路是否属于同一链路集， 具体包括： 检测所述路由信息中发送所述请求信息 的下一跳是否要发送至所述网元设备； 当所述路由信息中发送所述请求信息 的下一跳是要发送至所述网元设备， 则确定所述路由信息中发送所述请求消 息的链路与接收所述请求消息的链路属于同一链路集。
5、 一种路由代理设备， 其特征在于， 包括：
接收模块， 用于接收网元设备发送的请求消息；
获取模块， 用于获取将所述请求消息发送给服务端设备的路由信息； 检测模块， 用于检测所述路由信息中发送所述请求消息的下一跳的链路 与接收所述请求消息的链路是否属于同一链路集；
发送模块， 用于当检测到所述路由信息中发送所述请求消息的下一跳链 路与接收所述请求消息的链路属于同一链路集时， 向所述网元设备发送检测 到消息循环的响应。
6、 根据权利要求 5所述的路由代理设备， 其特征在于， 还包括： 记录模块， 用于记录接收所述请求消息的链路。
7、 根据权利要求 5或 6所述的路由代理设备， 其特征在于， 所述获取模 块， 还用于从所述路由信息中获取发送所述请求消息的下一跳的链路。
8、 根据权利要求 7所述的路由代理设备， 其特征在于， 所述检测模块， 具体用于检测所述路由信息中发送所述请求信息的下一跳是否要发送至所述 网元设备； 当所述路由信息中发送所述请求信息的下一跳是要发送至所述网 元设备， 则确定所述路由信息中发送所述请求消息的链路与接收所述请求消 息的链路属于同一链路集。
9、 一种组网系统， 其特征在于， 包括网元设备和路由代理设备； 所述网元设备， 用于向所述路由代理设备发送请求消息；
所述路由代理设备， 用于接收所述网元设备发送的所述请求消息， 并获 取将所述请求消息发送给服务端设备的路由信息； 检测所述路由信息中发送 所述请求消息的下一跳的链路与接收所述请求消息的链路是否属于同一链路 集； 当检测到所述路由信息中发送所述请求消息的下一跳链路与接收所述请 求消息的链路属于同一链路集时， 向所述网元设备发送检测到消息循环的响 应。
10、 根据权利要求 9所述的组网系统， 其特征在于， 所述网元设备为客 户端设备或者另一个路由代理设备。
PCT/CN2011/083564 2010-12-07 2011-12-06 消息循环的检测方法、路由代理设备及组网系统 WO2012075934A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP11846804.0A EP2582093B1 (en) 2010-12-07 2011-12-06 Method for detecting message loop, routing agent apparatus and networking system
US13/787,075 US9231856B2 (en) 2010-12-07 2013-03-06 Method for detecting message loop, routing agent apparatus and networking system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201010590396.1 2010-12-07
CN201010590396.1A CN102143018B (zh) 2010-12-07 2010-12-07 消息循环的检测方法、路由代理设备及组网系统

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US13/787,075 Continuation US9231856B2 (en) 2010-12-07 2013-03-06 Method for detecting message loop, routing agent apparatus and networking system

Publications (1)

Publication Number Publication Date
WO2012075934A1 true WO2012075934A1 (zh) 2012-06-14

Family

ID=44410258

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/083564 WO2012075934A1 (zh) 2010-12-07 2011-12-06 消息循环的检测方法、路由代理设备及组网系统

Country Status (4)

Country Link
US (1) US9231856B2 (zh)
EP (1) EP2582093B1 (zh)
CN (1) CN102143018B (zh)
WO (1) WO2012075934A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014025773A1 (en) * 2012-08-10 2014-02-13 Ibasis, Inc. Signaling traffic reduction in mobile communication systems
WO2014139794A1 (en) * 2013-03-15 2014-09-18 Deutsche Telekom Ag Method for indicating routing capacity related data or routing delay related data by means of signalling messages in a core network of a telecommunications network using diameter messages, a mobile communication networks

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102143018B (zh) * 2010-12-07 2014-04-30 华为技术有限公司 消息循环的检测方法、路由代理设备及组网系统
WO2015000514A1 (en) * 2013-07-03 2015-01-08 Telefonaktiebolaget L M Ericsson (Publ) Selection of a policy and charging control unit by a diameter routing unit
CN105991429B (zh) * 2015-02-10 2019-02-05 中国移动通信集团公司 一种路由重选判定方法及装置
CN107612823B (zh) * 2016-07-11 2021-04-02 中兴通讯股份有限公司 路由重选方法及系统
CN110266530B (zh) * 2019-06-14 2022-05-27 浪潮思科网络科技有限公司 一种基于Opendaylight框架的链路发现方法及装置
TWI809593B (zh) * 2021-12-08 2023-07-21 中華電信股份有限公司 用於網路電話信令迴圈的根因分析的電子裝置和方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US562129A (en) * 1896-06-16 Whiffletree
CN101001411A (zh) * 2007-01-19 2007-07-18 华为技术有限公司 一种消息传送的方法、装置和消息中心
CN101159780A (zh) * 2007-11-01 2008-04-09 中兴通讯股份有限公司 一种电信综合业务接入网关网间路由系统及其方法
CN101730027A (zh) * 2008-10-15 2010-06-09 中国移动通信集团公司 前转业务处理方法、处理系统及循环检测控制器
CN102143018A (zh) * 2010-12-07 2011-08-03 华为技术有限公司 消息循环的检测方法、路由代理设备及组网系统

Family Cites Families (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5862129A (en) * 1996-12-23 1999-01-19 Dsc Telecom L.P. Apparatus and method for the detection and elimination of circular routed SS7 global title translated messages in a telecommunications network
JP3688877B2 (ja) * 1997-08-08 2005-08-31 株式会社東芝 ノード装置及びラベルスイッチングパスのループ検出方法
DE10062375B4 (de) * 2000-12-14 2004-07-15 Siemens Ag Verfahren zum Weiterleiten von Datenpaketen, Weiterleitungseinheit und zugehöriges Programm
US7293106B2 (en) * 2002-05-28 2007-11-06 Hewlett-Packard Development Company, L.P. Method of finding a path between two nodes in a network
US7466815B2 (en) * 2003-06-27 2008-12-16 Tekelec Methods and systems for detecting and preventing signaling connection control part (SCCP) looping
US7606927B2 (en) * 2003-08-27 2009-10-20 Bbn Technologies Corp Systems and methods for forwarding data units in a communications network
US7889712B2 (en) * 2004-12-23 2011-02-15 Cisco Technology, Inc. Methods and apparatus for providing loop free routing tables
US8130759B2 (en) * 2005-07-29 2012-03-06 Opnet Technologies, Inc. Routing validation
US7684350B2 (en) * 2006-03-16 2010-03-23 Cisco Technology, Inc. Method and apparatus for distributing labels in a label distribution protocol multicast network
US8264949B2 (en) * 2006-08-30 2012-09-11 Rockstar Bidco Lp Method and apparatus for selecting between available neighbors in a rapid alternate path calculation
CN101155179B (zh) * 2006-09-30 2010-04-21 华为技术有限公司 一种多协议标签交换中环路拆除的方法
TW200849894A (en) * 2007-06-07 2008-12-16 Inst Information Industry Method, network apparatus, application program, and computer readable medium thereof for detecting a re-sent network packet
US20090210523A1 (en) * 2008-02-14 2009-08-20 Matthew Edward Duggan Network management method and system
CN102362470B (zh) * 2009-03-23 2015-01-28 日本电气株式会社 路径设置服务器和路径设置方法
JP5682620B2 (ja) * 2010-03-17 2015-03-11 日本電気株式会社 経路選択方法、情報処理装置、ネットワークシステムおよび経路選択プログラム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US562129A (en) * 1896-06-16 Whiffletree
CN101001411A (zh) * 2007-01-19 2007-07-18 华为技术有限公司 一种消息传送的方法、装置和消息中心
CN101159780A (zh) * 2007-11-01 2008-04-09 中兴通讯股份有限公司 一种电信综合业务接入网关网间路由系统及其方法
CN101730027A (zh) * 2008-10-15 2010-06-09 中国移动通信集团公司 前转业务处理方法、处理系统及循环检测控制器
CN102143018A (zh) * 2010-12-07 2011-08-03 华为技术有限公司 消息循环的检测方法、路由代理设备及组网系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014025773A1 (en) * 2012-08-10 2014-02-13 Ibasis, Inc. Signaling traffic reduction in mobile communication systems
US9596621B2 (en) 2012-08-10 2017-03-14 Ibasis, Inc. Signaling traffic reduction in mobile communication systems
WO2014139794A1 (en) * 2013-03-15 2014-09-18 Deutsche Telekom Ag Method for indicating routing capacity related data or routing delay related data by means of signalling messages in a core network of a telecommunications network using diameter messages, a mobile communication networks
US9756528B2 (en) 2013-03-15 2017-09-05 Deutsche Telekom Ag Indicating routing capacity related data or routing delay related data via signalling messages in a core network of a telecommunications network using diameter messages

Also Published As

Publication number Publication date
EP2582093B1 (en) 2018-06-20
CN102143018A (zh) 2011-08-03
EP2582093A1 (en) 2013-04-17
US9231856B2 (en) 2016-01-05
US20130183962A1 (en) 2013-07-18
CN102143018B (zh) 2014-04-30
EP2582093A4 (en) 2013-07-24

Similar Documents

Publication Publication Date Title
WO2012075934A1 (zh) 消息循环的检测方法、路由代理设备及组网系统
US10798199B2 (en) Network traffic accelerator
JP5101734B2 (ja) トンネル管理方法、トンネル管理装置および通信システム
WO2016127884A1 (zh) 消息推送方法及装置
WO2009052765A1 (fr) Procédé et dispositif de détection et de traitement de défaillance de nœud dans un réseau poste à poste
WO2018058618A1 (zh) 一种故障处理方法及设备
WO2011157145A2 (zh) 通信设备间的主备倒换方法、通信设备和系统及服务请求设备
JP2013126244A (ja) パケット通信装置および方法
US10440616B2 (en) Failure handling method, packet data network, mobility management entity, and network system
US9806992B2 (en) Re-routing of diameter commands
JP2015523793A (ja) リングネットワークにおけるサービス処理方法及びネットワークデバイス
EP3043598A1 (en) Routing method between base stations, serving gateway and base station
WO2011144111A2 (zh) 链路状态数据库同步检测方法及路由设备
CN109428814B (zh) 一种组播流量传输方法、相关设备和计算机可读存储介质
CN117955903A (zh) 设备管理方法、设备、系统和存储介质
WO2021098477A1 (zh) 信号劣化处理方法、装置及系统
WO2012100711A1 (zh) 一种应用层信令路由保护方法、设备、计算机程序和存储介质
WO2016062021A1 (zh) 业务能力探测方法及装置
WO2017203328A1 (en) Method for providing position information related to legal interception in an ims network
WO2012109873A1 (zh) 对Diameter路由进行管理的方法和装置
US20240372798A1 (en) Systems and methods for cloaking routes
US7623464B2 (en) Rapid protocol failure detection
JP5681297B2 (ja) 中継バックアップ装置及び中継制御方法
WO2024125269A1 (zh) 语音业务的建立方法、网络设备及存储介质
WO2020238799A1 (zh) 一种基于twamp的检测方法及相关设备

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2011846804

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE