WO2012062102A1 - 一种检测组播转发树上两点间连通性的方法、系统和装置 - Google Patents
一种检测组播转发树上两点间连通性的方法、系统和装置 Download PDFInfo
- Publication number
- WO2012062102A1 WO2012062102A1 PCT/CN2011/074946 CN2011074946W WO2012062102A1 WO 2012062102 A1 WO2012062102 A1 WO 2012062102A1 CN 2011074946 W CN2011074946 W CN 2011074946W WO 2012062102 A1 WO2012062102 A1 WO 2012062102A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- multicast
- detection
- unicast
- time
- detection request
- Prior art date
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/16—Multipoint routing
-
- 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/26—Route discovery packet
Definitions
- the present invention relates to network communication technologies, and in particular, to a method, system and apparatus for detecting connectivity between two points on a multicast forwarding tree. Background technique
- the detection of network faults is basically limited to point-to-point fault detection.
- detection methods such as BFD (Bidirectional Forwarding Detection), OAM (Operation, Administration and Administration and Maintenance, operation, management, and maintenance, and SCTP (Stream Control Transmission Protocol) are all point-to-point fault detection methods.
- the detection mode of the existing IP layer can only be limited to point-to-point fault detection.
- the multicast forwarding tree if it is necessary to detect the connectivity of the multicast source to some nodes of the multicast group, each node needs to be separately performed. Point-to-point fault detection results in a large workload and high operational complexity. Summary of the invention
- an object of the present invention is to provide a method, system, and apparatus for detecting connectivity between two points on a multicast forwarding tree, so as to reduce the workload of the multicast source for detecting connectivity of a multicast group node, and Reduce operational complexity.
- the present invention provides the following technical solutions:
- a method for detecting connectivity between two points on a multicast forwarding tree comprising:
- a multicast source node in the multicast forwarding tree that initiates connectivity detection between two points on the multicast forwarding tree.
- the multicast group address sends a multicast detection request message for detecting the connectivity between the two points.
- the intermediate node in the multicast forwarding tree forwards the message according to the routing table after receiving the multicast detection request message.
- the multicast detection request packet returns a unicast detection response message to the multicast source node every time a direct connection user is determined to be present;
- the multicast source node receives the unicast detection response returned by the intermediate node, and determines that the user that does not receive the corresponding unicast detection response within the set time is in the connectivity fault state.
- a system for detecting connectivity between two points on a multicast forwarding tree including:
- the multicast source node is configured to send a multicast detection request packet for detecting connectivity between two points to the multicast address when the connectivity between the two points in the multicast forwarding tree is initiated, and receive the returned unicast detection response. a packet, and determining that the user that does not receive the corresponding unicast detection response packet within the set time is in a connected fault state;
- the intermediate node on the multicast forwarding tree is configured to: after each receiving the multicast detection request packet, forward the multicast detection request packet according to the routing table, and each time a direct connection user is determined to exist, Returning a unicast detection response message to the multicast source node.
- a device for detecting connectivity between two points on a multicast forwarding tree including:
- the multicast detection request message sending unit is configured to send, to the multicast address, a multicast detection request for detecting connectivity between two points;
- a unicast detection response message receiving unit configured to receive a unicast detection response message returned by the intermediate node
- the determining unit is configured to determine that the user that does not receive the corresponding unicast detection response message within the set time is in a connectivity fault state.
- a device for detecting connectivity between two points on a multicast forwarding tree including:
- the multicast detection request packet receiving unit is configured to receive a multicast detection request message sent by the multicast source node
- a forwarding unit configured to: according to the routing table after each receiving the multicast detection request message Forwarding the multicast detection request message;
- the unicast detection response message sending unit is configured to return a unicast detection response message to the multicast source node every time a direct connection user is determined to exist.
- the embodiment of the present invention provides a method, a system, and a device for detecting connectivity between two points in a multicast forwarding tree, and detecting a multicast source by using MPING (Multicast Packet Internet Groper, multicast ping)
- the multicast source sends a multicast detection request packet to the multicast source.
- the intermediate node forwards the packet based on the routing table after receiving the multicast detection request packet.
- the unicast detection response packet is returned to the multicast source, so that the multicast source can perform connectivity detection on the multicast group node.
- the one-to-many method is used to perform connectivity between two points on the multicast forwarding tree.
- the detection avoids the point-to-point fault detection of each node separately, reduces the workload of the multicast source to detect the connectivity of the multicast group node, and reduces the operation complexity.
- FIG. 1 is a flow chart of a method for detecting connectivity between two points on a multicast forwarding tree according to an embodiment of the present invention
- FIG. 2 is a schematic structural diagram of a multicast network according to an embodiment of the present invention.
- FIG. 3 is a schematic flowchart of detecting connectivity between two points on a multicast forwarding tree by a multicast source node according to an embodiment of the present invention
- FIG. 4 is a schematic flowchart of detecting connectivity between two points on a multicast forwarding tree by an intermediate node according to an embodiment of the present invention
- FIG. 5 is a schematic structural diagram of a system for detecting connectivity between two points on a multicast forwarding tree according to an embodiment of the present invention
- FIG. 6 is a schematic structural diagram of an apparatus for detecting connectivity between two points on a multicast forwarding tree according to an embodiment of the present disclosure
- FIG. 7 is a schematic diagram of a device for detecting connectivity between two points on a multicast forwarding tree according to an embodiment of the present invention.
- the second embodiment of the schematic diagram is a schematic diagram of a device for detecting connectivity between two points on a multicast forwarding tree according to an embodiment of the present invention.
- the embodiment of the invention provides a method, a system and a device for detecting connectivity between two points in a multicast forwarding tree, and detecting connectivity of a multicast source and each node in a multicast group by using multicast ping, on the multicast forwarding tree.
- the multicast source sends a multicast detection request packet.
- the intermediate node in the multicast forwarding tree forwards the packet according to the routing table, and when there is a direct multicast receiving user, the group is sent to the group.
- the broadcast source returns a unicast detection response packet, so that the multicast source can perform connectivity detection on the multicast group node.
- the one-to-many method is used to detect the connectivity between two points in the multicast forwarding tree, which avoids the point-to-point fault detection for each node, and reduces the workload of the multicast source to detect the connectivity of the multicast group node. And reduce the complexity of the operation.
- the method for detecting connectivity between two points on a multicast forwarding tree includes:
- Step S101 The multicast source node that initiates the connectivity detection between the two points in the multicast forwarding tree in the multicast forwarding tree sends a multicast detection request packet for detecting the connectivity between the two points to the multicast group address.
- Step S102 After receiving the multicast detection request packet, the intermediate node in the multicast forwarding tree forwards the multicast detection request packet according to the routing table, and returns a single to the multicast source node every time a direct connection user is determined to exist. Broadcast detection response message;
- Step S103 The multicast source node receives the unicast detection response returned by the intermediate node, and determines that the user that does not receive the corresponding unicast detection response message is in the connectivity fault state within the set time.
- the intermediate node returns a unicast detection response message to the multicast source node, and returns a unicast detection response message to the multicast source node by receiving the path of the multicast detection request message.
- the intermediate node When the intermediate node is looking up the routing table, it is usually based on the multicast routing entry in the routing table. Obtaining the outbound interface, inbound interface, and direct connection user information of the node; when the intermediate node has an outbound interface, it is determined whether there is a directly connected user on the interface; when the node has an outbound interface that is not directly connected to the user, the replication group
- the broadcast detects the request packet and forwards it through the outbound interface that is not directly connected to the user. For the inbound interface, the packet is not required to be forwarded from the inbound interface. Therefore, when the inbound interface is directly connected to the user according to step S102, the unicast detection response packet is returned to the multicast source node.
- Layer 3 switches A, B, and C support multicast routing protocols and have multicast routing protocol functions.
- the Protocol Independent Multicast-Sparse Mode ( protocol-independent multicast sparse mode) protocol has been enabled. Port 1 is located in Vlanl, port 2 is located in Vlan2, port 3 and port 8 are located in Vlan3, port 4 and port 7 are located in Vlan4, port 5 and port 10 are located in Vlan5, port 6 is located in Vlan6, and port 9 is located in Vlan7.
- the PIM protocol has been enabled on each Vlan port; User A, User B, and User C have joined the multicast group 224.1.2.3 through the Internet Group Management Protocol (IGMP) protocol.
- the source has started to send some Service data flow, such as the source address is 10.10.10.10, and the multicast group address is 224.1.2.3. At this point, corresponding multicast routing entries have been formed on switches A, B and C.
- the multicast source node switch A initiates a multicast ping operation, and the destination address is the multicast group address 224.1.2.3;
- Switch A After receiving the multicast ICMP (Internet Control Message Protocol) request packet, Switch A first searches for the multicast routing entry in the routing table and finds four PIM interfaces Vlanl, Vlan2, Vlan3, and Vlan4. At the same time, it is determined that there is a directly connected user in Vlan2, and then a unicast ICMP response message is returned to switch A, and the unicast ICMP echo message can be copied by copying the multicast ICMP request message, and then the copied multicast ICMP request is modified. Packets are generated. Ports 1, 3, and 4 are outgoing ports that are not directly connected to the user, so they are also required. Copy the multicast ICMP request message and send it out from ports 1, 3 and 4.
- ICMP Internet Control Message Protocol
- switch B After receiving the multicast ICMP request packet from port 7, switch B also searches for the multicast routing entry in the local routing table and finds that the user directly connected in Vlan6, and then returns a unicast ICMP response packet from port 7. For the multicast source node switch A, because port 7 is the ingress port, only port 5 is the egress port of the user that is not directly connected to the user, so the duplicate multicast ICMP request packet is sent out from port 5.
- switch C receives a multicast ICMP request packet from port 5 and port 8, and also looks for the multicast routing entry in the local routing table. It finds that there is a directly connected user in Vlan9, and thus from port 5 and port. 8 each returns a unicast ICMP response message to the multicast source node.
- the multicast source node receives four unicast ICMP response messages, one from itself, one from switch B, and two from switch C. These four entries are displayed on switch A, corresponding to the four unicast ICMP response messages.
- the embodiment of the present invention is called a multicast ICMP request message and a unicast ICMP response message.
- the process of detecting connectivity between two points on the multicast forwarding tree of the switch that initiates multicast ping in the multicast forwarding tree includes:
- Step S301 Find a multicast routing table, and obtain information about the outbound interface and the inbound interface, including the number of the interface and the inbound interface, the interface index, and whether the interface has a direct user tag.
- Step S302 Query the corresponding inbound interface according to the interface index of the inbound interface
- Step S303 Determine the inbound interface, traverse the inbound interface list, and if there is a directly connected user, copy the original packet to generate a unicast detection response message, and send it to itself;
- Step S305 Determine the outbound interface, traverse the interface list, and determine whether the interface is empty. If yes, go to step S306, if no, go to step S307;
- Step S306 If the outbound interface is empty, the message is released, and the processing is not continued; Step S307: If the outbound interface is not empty, it is determined whether the interface has a direct connection user.
- Step S308 When a directly connected user is found, the original message is copied to generate a unicast detection response message, and sent to itself, and copied. The original packet is not forwarded directly to the outgoing port of the user; Step S309, receiving the returned unicast detection response message, displaying the corresponding information of the unicast detection response message, and determining that the original information is not received within the set time The node corresponding to the unicast detection response packet is in the connectivity fault state.
- the multicast source node when it sends a multicast detection request packet, it also sends the multicast detection request packet to the outbound interface of the user that is not directly connected to the multicast routing table.
- the multicast source node determines that the interface has a directly connected user, The unicast detection response packet can be returned to itself. However, if the unicast detection response packet is not returned, the connection between the multicast source node and the self is not considered to be a connection failure.
- the test result of connectivity when the multicast source node sends a multicast detection request packet, it also sends the multicast detection request packet to the outbound interface of the user that is not directly connected to the multicast routing table.
- the process of detecting connectivity between two points on the multicast forwarding tree of other intermediate nodes in the multicast forwarding tree includes:
- Step S401 After receiving the multicast detection request packet, the routing table needs to be searched for the information of the outbound interface and the inbound interface, including the number of the outbound interface and the inbound interface, the interface index, and whether the interface is marked with a direct user identifier.
- Step S402 Query the corresponding inbound interface according to the interface index of the inbound interface, determine the inbound interface, and traverse the inbound interface list. If there is a directly connected user, copy the original packet to generate a unicast detection response packet, and return the multicast packet to the multicast.
- Source node
- Step S403 Query the corresponding outgoing interface according to the interface index of the outbound interface, determine the outgoing interface, and traverse the outgoing interface list;
- Step S404 it is determined whether the interface is empty, if yes, step S405 is performed, if not, step S406 is performed;
- Step S405 Determine whether the received multicast detection request message is marked with a sending flag, and if yes, process the multicast detection request message by using a multicast protocol, otherwise release the message.
- step S406 it is determined whether there is a direct connection user on the interface. If there is a direct connection user, the unicast detection response message is sent to the multicast source node. If there is no directly connected user, the multicast detection is forwarded through the outbound interface. Request a message.
- the connectivity between nodes in the multicast forwarding tree can be detected.
- the multicast source node When the unicast detection response packet is received, the multicast source node records the system time as the transmission time. Response time, and calculate the RTT (Round-Trip Time) as the difference between the response time and the transmission time.
- the round-trip delay is an important performance indicator in the computer network. It means that the data is sent from the sender to the The sender receives the acknowledgment from the receiving end (the acknowledgment is sent immediately after the receiving end receives the data). The total delay experienced by this parameter can reflect the distance between the two nodes to some extent.
- the multicast source node and the RTT of the intermediate node that replies to the unicast detection response message are calculated from the time when the multicast detection request data packet is sent to the unicast detection response message. .
- the timestamp is added, and the timestamp is saved, and the current timestamp is obtained when the unicast detection response message is received, and the timestamp and the timestamp are obtained.
- the difference between the saved timestamps is the value of RTT, and the unit of RTT is usually milliseconds.
- the multicast source node may calculate the jitter time each time the unicast detection response message is received except for the first time, and the jitter time is the round-trip delay of the current calculation and the last calculated round-trip time.
- the difference of the delay is as follows: After each multicast detection request message is sent, the number of received unicast detection response messages is accumulated. If the number of received response packets is greater than 1, the current calculation is performed. The RTT value is subtracted from the last calculated RTT value, which is the current jitter time. When the number of received response packets is exactly 2, the average jitter time, the maximum jitter time, and the minimum jitter time are the current jitter times. When the number of response packets received is greater than 2, the current jitter is calculated.
- the current jitter time and the previous maximum jitter time and minimum The jitter time is compared separately. If the current jitter time is greater than the previous maximum jitter time, the current jitter time is taken as the new maximum jitter time. If the current jitter time is less than the previous maximum 'J, the jitter time, the current jitter time is taken as the new one. Minimum jitter time.
- a maximum number of unicast detection response packets can be set, for example,
- the maximum number of received unicast detection response packets can be adjusted according to the size of the multicast forwarding tree and the processing capability of the multicast source node. When the size of the multicast forwarding tree is large, the maximum number of multicast forwarding trees can be increased. The maximum number of unicast detection response packets is received. Conversely, when the size of the multicast forwarding tree is small, the maximum number of unicast detection response packets can be reduced. Similarly, when the multicast source node is processed. If the unicast detection response packet is received, the maximum number of unicast detection response packets can be increased. If the processing capability of the multicast source node is weak, the maximum reception of the unicast detection response packet can be appropriately reduced. Quantity.
- the termination command may be set at the multicast source node, and the user sends the termination command.
- the multicast source node immediately stops processing the received unicast detection response message, and the termination instruction may be a command statement set by the user, or may be a shortcut key, such as ctrl+c, or may be a click operation interface. Set the button, or set according to the user's actual needs and habits.
- the conditions for the multicast source to stop processing the received unicast detection response message include the following three points: 1. The preset timeout period is reached; 2. The maximum unicast detection response message is reached. Receive quantity; 3. Receive a termination command.
- the multicast ping can be re-initiated and re-timed. If the unicast detection response packet is not received, the process can be continued until the user issues a stop command, and a retry number can be set. After the retry number is reached, the multicast ping is not re-initiated.
- the processing capability of the multicast source node is limited. To prevent the number of returned unicast detection response packets from being too large, the multicast source node is overloaded. You can also set a rate limit timer. If the number of multicast pings in a period does not reach the preset maximum number of times, the number of multicast pings in the period does not reach the preset maximum number. If the maximum number of times is not reached, the multicast can continue. Ping, otherwise multicast ping is not allowed. After the rate limit timer expires, the multicast ping count is cleared to 0. In this way, multicast pings can be avoided multiple times in a short period of time, so that the multicast source node receives many unicast detection response packets in a short period of time, and the packets are lost due to insufficient CPU processing capability.
- the embodiment of the present invention further provides a system for detecting connectivity between two points in a multicast forwarding tree.
- the method includes: a multicast source node 501 and an intermediate node 502 on the multicast forwarding tree, where:
- the multicast source node 501 is configured to send a multicast detection request packet for detecting connectivity between two points to the multicast address when the connectivity between the two points in the multicast forwarding tree is initiated, and the receiving intermediate node returns 502.
- the unicast detection response message determines that the user who does not receive the corresponding unicast detection response within the set time is in the connected fault state;
- the intermediate node 502 is configured to: after each receiving the multicast detection request packet, forward the multicast detection request packet according to the routing table, and return a unicast detection to the multicast source node every time a direct connection user is determined to exist. Respond to the message.
- the intermediate node 502 searches the routing table after each receiving the multicast detection request message, and obtains the outbound interface, the inbound interface, and the direct connection user information of the node.
- the node has the outbound interface, it is determined whether the interface is out.
- a user who has a direct connection when the node has an outgoing interface that is not directly connected to the user, the multicast detection request packet is copied, and the outgoing interface is not directly connected to the user. Forwarding; and returning a unicast detection response message to the multicast source node every time a direct connection user is determined to exist.
- the multicast source node can also calculate the round-trip delay when receiving the unicast detection response, so that the user can more fully understand the connectivity between the nodes. At this time, the multicast source node is also used to:
- the system time is recorded as the transmission time
- the system time is recorded as the response time; and the round-trip delay is calculated as the difference between the response time and the transmission time.
- the multicast source node can further calculate the jitter time according to the round-trip delay and calculate the connectivity between the nodes. At this time, the multicast source node is also used to:
- the jitter time is calculated as the difference between the round-trip delay of this calculation and the last calculated round-trip delay.
- the multicast source node has a limited processing capacity. To prevent the number of unicast detection response packets returned in a short period of time, the multicast source node is overloaded. Control the number of multicast pings in a certain period. Before performing multicast ping, first determine that the number of multicast pings in the period does not reach the preset maximum number. If the preset maximum number of times is not reached, you can continue. Multicast ping is performed. Otherwise, multicast ping is not allowed. After the rate limit timer expires, the multicast ping count is cleared to 0. At this point, the multicast source node is also used to:
- the embodiment of the present invention further provides a device for detecting connectivity between two points in a multicast forwarding tree, where the device is set in a multicast source node that initiates multicast ping in the multicast forwarding tree, as shown in FIG.
- the device includes:
- the multicast detection request message sending unit 601 is configured to send a multicast detection request for detecting connectivity between two points to the multicast address.
- the unicast detection response message receiving unit 602 is configured to receive the unicast detection response message returned by the intermediate node;
- the determining unit 603 is configured to determine that the user that does not receive the corresponding unicast detection response message within the set time is in a connected fault state.
- the device further includes:
- the recording unit 604 is configured to: when the multicast detection request message is sent, record the system time as the sending time; and each time the unicast detection response message is received, record the system time as the response time; the round-trip delay calculating unit 605, Used to calculate the round trip delay as the difference between the response time and the send time.
- the device further includes: a jitter time calculation unit 606, configured to calculate a round-trip delay and a last time of the jitter calculation for each time the unicast detection response message is received except for the first time The difference in the calculated round trip delay.
- the jitter time of the round trip of the message is counted, and the stability of the connection between the nodes is evaluated.
- the apparatus further includes a termination unit 607, configured to stop processing the received unicast detection response message and terminate when the termination condition is reached.
- the conditions include: reaching a preset timeout period; or reaching a preset maximum number of unicast detection response messages received; or receiving a termination command.
- the embodiment of the present invention further provides an apparatus for detecting connectivity between two points in a multicast forwarding tree, where the apparatus may be disposed in an intermediate node of the multicast forwarding tree that receives the multicast detection request message, as shown in FIG.
- the device includes:
- the multicast detection request packet receiving unit 701 is configured to receive a multicast detection request packet sent by the multicast source node.
- the forwarding unit 702 is configured to: after receiving the multicast detection request message, forward the multicast detection request message according to the routing table;
- the unicast detection response message sending unit 703 is configured to return a unicast detection response message to the multicast source node every time a direct connection user is determined to exist.
- the unicast detection response is generally used to:
- the unicast detection response packet is returned to the multicast source node by receiving the path of the multicast detection request packet.
- the forwarding unit 702 is specifically configured to:
- the routing table is searched for the outbound interface, the inbound interface, and the directly connected user information of the node.
- the node When the node has an outbound interface, it is determined whether there is a directly connected user on the interface. When the node has an outbound interface that is not directly connected to the user, the multicast detection request packet is copied and forwarded through the outbound interface that is not directly connected to the user. . The interface of the directly connected user also needs to forward the request message.
- the embodiment of the present invention provides a method, a system, and a device for detecting connectivity between two points in a multicast forwarding tree, and detecting a multicast source by using MPING (Multicast Packet Internet Groper, multicast ping)
- the multicast source sends a multicast detection request packet to the multicast source.
- the intermediate node forwards the packet based on the routing table after receiving the multicast detection request packet.
- the unicast detection response packet is returned to the multicast source, so that the multicast source can perform connectivity detection on the multicast group node.
- the one-to-many method is used to perform connectivity between two points on the multicast forwarding tree.
- the detection avoids the point-to-point fault detection of each node separately, reduces the workload of the multicast source to detect the connectivity of the multicast group node, and reduces the operation complexity.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
本发明公开了一种检测组播转发树上两点间连通性的方法、系统和装置，涉及网络通信技术，通过组播ping来检测组播源与组播组中各节点的连通性，组播源发送组播检测请求报文，中间节点在接收到组播检测请求报文后，根据路由表进行转发，并在有直连组播接收用户时，向组播源返回单播检测回应报文，从而实现组播源对组播组节点进行连通性检测的工作，由于使用一对多的方式进行组播转发树上两点间连通性的检测，避免了分别对每一个节点进行点对点故障检测，减少了组播源对组播组节点进行连通性检测的工作量并降低操作复杂度。
Description
一种检测组播转发树上两点间连通性的方法、 系统和装置 技术领域
本发明涉及网络通信技术， 尤其涉及一种检测组播转发树上两点间连 通性的方法、 系统和装置。 背景技术
随着组播技术应用的日益广泛， 对组播维护和故障定位的需求也越来 越大， 准确并迅速的检测故障显得越来越重要。
而目前， 网络故障的检测基本上局限于点对点的故障检测， 即使在组 播转发树上，仍然使用这样的检测方式，例如 BFD ( Bidirectional Forwarding Detection,双向转发检则 )、 OAM( Operations , Administration and Maintenance, 运行、 管理和维护）和 SCTP ( Stream Control Transmission Protocol,流量控 制传输协议）等都是点对点的故障检测的方式。
由于现有 IP层的检测方式只能局限于点对点的故障检测， 在组播转发 树中， 若需要检测组播源对组播组的一些节点的连通性时， 则需要分别对 每一个节点进行点对点故障检测， 导致工作量很大并且操作复杂度较高。 发明内容
有鉴于此， 本发明的发明目的在于提供一种检测组播转发树上两点间 连通性的方法、 系统和装置， 以减少组播源对组播组节点进行连通性检测 的工作量， 并降低操作复杂度。
为实现本发明目的， 本发明提供以下技术方案：
一种检测组播转发树上两点间连通性的方法， 该方法包括：
组播转发树中发起组播转发树上两点间连通性检测的组播源节点， 向
组播组地址发送用于检测两点间连通性的组播检测请求报文； 组播转发树中的中间节点在每次接收到所述组播检测请求报文后， 根 据路由表转发所述组播检测请求报文， 并在每确定存在一个直接连接用户 时 , 向所述组播源节点返回单播检测回应报文；
所述组播源节点接收所述中间节点返回的单播检测回应 ^艮文， 并确定 于设定时间内未接收到对应单播检测回应 ^艮文的用户处于连通故障状态。
一种检测组播转发树上两点间连通性的系统， 包括：
组播源节点， 用于在发起组播转发树上两点间连通性检测时， 向组播 地址发送用于检测两点间连通性的组播检测请求报文， 接收返回的单播检 测回应报文， 并确定于设定时间内未接收到对应单播检测回应报文的用户 处于连通故障状态；
组播转发树上的中间节点， 用于在每次接收到所述组播检测请求报文 后， 根据路由表转发所述组播检测请求报文， 并在每确定存在一个直接连 接用户时， 向所述组播源节点返回单播检测回应报文。
一种检测组播转发树上两点间连通性的装置， 包括：
组播检测请求报文发送单元， 用于向组播地址发送用于检测两点间连 通性的组播检测请求 ^艮文；
单播检测回应报文接收单元， 用于接收所述中间节点返回的单播检测 回应报文；
确定单元， 用于确定于设定时间内未接收到对应单播检测回应报文的 用户处于连通故障状态。
一种检测组播转发树上两点间连通性的装置， 包括：
组播检测请求报文接收单元， 用于接收组播源节点发送的组播检测请 求报文；
转发单元， 用于在每次接收到所述组播检测请求报文后， 根据路由表
转发所述组播检测请求报文；
单播检测回应报文发送单元， 用于在每确定存在一个直接连接用户时， 向所述组播源节点返回单播检测回应报文。
本发明实施例提供一种检测组播转发树上两点间连通性的方法、 系统 和装置， 通过 MPING ( Multicast Packet Internet Groper,组播报文网络搜索， 简称组播 ping )来检测组播源与组播组中各节点的连通性， 组播源发送组 播检测请求报文， 中间节点在接收到组播检测请求报文后， 根据路由表进 行转发， 并在有直连组播接收用户时， 向组播源返回单播检测回应报文， 从而实现组播源对组播组节点进行连通性检测的工作， 由于使用一对多的 方式进行组播转发树上两点间连通性的检测， 避免了分别对每一个节点进 行点对点故障检测， 减少了组播源对组播组节点进行连通性检测的工作量 并降低操作复杂度。 附图说明
图 1 为本发明实施例提供的检测组播转发树上两点间连通性的方法流 程图；
图 2为本发明实施例提供的组播网络结构示意图；
图 3 为本发明实施例提供的组播源节点检测组播转发树上两点间连通 性的流程示意图；
图 4为本发明实施例提供的中间节点检测组播转发树上两点间连通性 的流程示意图；
图 5 为本发明实施例提供的检测组播转发树上两点间连通性的系统结 构示意图；
图 6为本发明实施例提供的检测组播转发树上两点间连通性的装置结 构示意图之一；
图 7为本发明实施例提供的检测组播转发树上两点间连通性的装置结
构示意图之二 具体实施方式
本发明实施例提供一种检测组播转发树上两点间连通性的方法、 系统 和装置， 通过组播 ping来检测组播源与组播组中各节点的连通性， 组播转 发树上的组播源发送组播检测请求报文， 组播转发树上的中间节点在接收 到组播检测请求报文后， 根据路由表进行转发， 并在有直连组播接收用户 时 , 向组播源返回单播检测回应报文 , 从而实现组播源对组播组节点进行 连通性检测的工作。
由于使用一对多的方式进行组播转发树上两点间连通性的检测， 避免 了分别对每一个节点进行点对点故障检测， 减少了组播源对组播组节点进 行连通性检测的工作量并降低操作复杂度。
如图 1 所示， 本发明实施例提供的检测组播转发树上两点间连通性的 方法包括：
步骤 S101、 组播转发树中发起组播转发树上两点间连通性检测的组播 源节点向组播组地址发送用于检测两点间连通性的组播检测请求报文； 步骤 S102、 组播转发树中的中间节点在每次接收到组播检测请求报文 后， 根据路由表转发组播检测请求报文， 并在每确定存在一个直接连接用 户时， 向组播源节点返回单播检测回应报文；
步骤 S103、 组播源节点接收中间节点返回的单播检测回应 ^艮文， 并确 定于设定时间内未接收到对应单播检测回应报文的用户处于连通故障状 态。
在步骤 S102中， 中间节点向组播源节点返回单播检测回应报文， 通常 通过接收到组播检测请求报文的路径向组播源节点返回单播检测回应报 文。
中间节点在在查找路由表时， 通常根据路由表中的组播路由条目， 先
获取该节点的出接口、 入接口和直连用户信息； 当该中间节点具有出接口 时， 判断出接口上是否存在直接连接的用户； 当该节点具有未直接连接用 户的出接口时， 复制组播检测请求报文， 并通过未直接连接用户的出接口 转发。 而对于入接口来讲， 是不需要从入接口转发报文的， 所以只要根据 步骤 S102在入接口有直接连接用户时， 向组播源节点返回单播检测回应报 文即可。
下面以一个实例具体说明检测组播转发树上两点间连通性的方法， 如 图 2所示， 三层交换机 A、 B和 C都是支持组播路由协议的， 且具有组播 路由协议功能^口 PIM-SM ( Protocol Independent Multicast-Sparse Mode, 协 议无关组播稀疏模式）协议已经开启。 端口 1位于 Vlanl 内， 端口 2位于 Vlan2内， 端口 3和端口 8位于 Vlan3内， 端口 4和端口 7位于 Vlan4内， 端口 5和端口 10位于 Vlan5内， 端口 6位于 Vlan6内， 端口 9位于 Vlan7 内， 且每个 Vlan端口 PIM协议都已经开启； 用户 A、 用户 B和用户 C已 经通过 IGMP ( Internet Group Management Protocol, 因特网组管理协议 )协 议加入到组播组 224.1.2.3 , 源端已经开始发送某业务数据流， 如源地址为 10.10.10.10, 组播组地址为 224.1.2.3。 至此， 在交换机 A, B和 C上已经形 成了相应的组播路由条目。
此时组播源节点交换机 A发起组播 ping操作， 目的地址为组播组地址 224.1.2.3;
交换机 A在接收到组播 ICMP ( Internet control Message Protocol, 因特 网控制报文协议）请求报文后， 首先查找路由表中的组播路由条目， 查找 到四个 PIM接口 Vlanl , Vlan2, Vlan3和 Vlan4, 同时判断出 Vlan2内有直 接连接的用户，于是向交换机 A返回一个单播 ICMP应答报文，该单播 ICMP 回应报文可以通过复制组播 ICMP请求报文， 再修改所复制的组播 ICMP 请求报文来生成， 端口 1、 3和 4为未直接连接用户的出端口， 所以还需要
复制组播 ICMP请求报文， 并从端口 1、 3和 4发送出去；
交换机 B从端口 7收到该组播 ICMP请求报文后， 同样是查找本地路 由表中的组播路由条目， 发现 Vlan6 内有直接连接的用户， 于是从端口 7 返回一个单播 ICMP应答报文给组播源节点交换机 A, 由于端口 7为入端 口， 仅端口 5为未直接连接用户的出端口， 所以复制组播 ICMP请求报文 从端口 5发送出去；
这样交换机 C就会从端口 5和端口 8各收到一份组播 ICMP请求报文， 同样查找本地路由表中的组播路由条目， 发现 Vlan9内有直接连接的用户， 于是从端口 5和端口 8各返回一个单播 ICMP应答报文给组播源节点， 至 此， 组播源节点收到四份单播 ICMP应答报文， 一份来自自身， 一份来自 交换机 B , 两份来自交换机 C, 在交换机 A上会显示出这四个条目， 分别 对应这四个单播 ICMP应答报文。
当组播检测请求报文和单播检测应答报文为 ICMP报文时， 本发明实 施例中称为组播 ICMP请求报文和单播 ICMP应答报文。
如图 3所示， 组播转发树中发起组播 ping的交换机进行组播转发树上 两点间连通性检测的流程包括：
步骤 S301、 查找组播路由表， 获取出接口和入接口的信息， 包括出接 口和入接口的数量， 接口索引， 接口上是否打上有直连用户标记等；
步骤 S302、 根据入接口的接口索引查询对应的入接口；
步骤 S303、 对入接口进行判断， 遍历入接口链表， 如果有直连用户， 则拷贝原报文生成单播检测应答报文， 并发送给自身；
步骤 S304、 根据出接口的接口索引查询对应的出接口；
步骤 S305、 对出接口进行判断， 遍历出接口链表， 判断出接口是否为 空， 如果是， 执行步骤 S306, 如果不是， 执行步骤 S307;
步骤 S306、 如果出接口为空， 则释放报文， 不再继续处理；
步骤 S307、 如果出接口不为空， 则判断出接口是否有直连用户； 步骤 S308、 每发现一个直连用户时， 拷贝原报文生成单播检测应答报 文， 并发送给自身， 并拷贝原报文并从未直接连接用户的出端口转发出去； 步骤 S309、 接收返回的单播检测应答报文， 显示单播检测应答报文的 对应信息， 并确定于在设定时间内未接收到对应单播检测应答报文的节点 处于连通故障状态。
当然， 组播源节点也在发送组播检测请求报文时， 也是根据自身的路 由表向未直接连接用户的出接口发送的， 组播源节点在判断出接口有直接 连接的用户时， 也可以向自身返回单播检测应答报文， 但如果不返回单播 检测应答报文， 也不会被认为组播源节点和自身存在连接故障， 由于仅涉 及组播源节点， 所以不影响节点间连通性的检测结果。
如图 4所示， 组播转发树其它中间节点进行组播转发树上两点间连通 性检测的流程包括：
步骤 S401、 在接收到组播检测请求报文后需要查找路由表， 获取出接 口和入接口的信息， 包括出接口和入接口的数量， 接口索引， 接口上是否 打上有直连用户标记等；
步骤 S402、 根据入接口的接口索引查询对应的入接口， 对入接口进行 判断， 遍历入接口链表， 如果有直连用户， 则拷贝原报文生成单播检测应 答报文， 并返回给组播源节点；
步骤 S403、 根据出接口的接口索引查询对应的出接口， 对出接口进行 判断， 遍历出接口链表；
步骤 S404、判断出接口是否为空， 如果是，执行步骤 S405 , 如果不是， 执行步骤 S406;
步骤 S405、 判断接收到的组播检测请求报文中是否打上了上送标记， 如果是， 则使用组播协议处理该组播检测请求报文， 否则释放该报文。
步骤 S406、 判断出接口上是否有直连用户， 如果有直连用户， 需要向 组播源节点回应一个单播检测应答 4艮文， 如果没有直连用户， 则通过该出 接口转发组播检测请求报文。
通过上面的流程， 即可实现组播转发树中节点间连通性的检测。
为便于用户进一步获取节点间的连通情况， 组播源节点在发送组播检 测请求报文时， 记录系统时间为发送时间 , 在每次接收到单播检测回应报 文时， 也记录系统时间为回应时间， 并计算 RTT ( Round-Trip Time, 往返 时延） 为回应时间与发送时间的差值， 往返时延在计算机网络中是一个重 要的性能指标， 它表示从发送端发送数据开始， 到发送端接收到来自接收 端的确认（接收端收到数据后便立即发送确认） 总共经历的时延， 通过该 参数可以在一定程度上反映出两节点间距离的远近。
在本发明实施例中， 计算组播检测请求数据报文从发送到接收到单播 检测应答报文的这一段时间即为组播源节点和回复该单播检测应答报文的 中间节点的 RTT。 在具体实现时， 可以再发送组播检测请求 ^艮文时打上时 间戳， 并将时间戳保存起来， 在接收到单播检测应答报文的时候再获取当 前的时间戳， 该时间戳和所保存的时间戳的差值就是 RTT的数值， RTT的 单位通常为毫秒。
更进一步的， 组播源节点还可以在除第一次以外的每次接收到单播检 测回应报文时 , 计算抖动时间 , 抖动时间为本次计算的往返时延与上次计 算的往返时延的差值， 方法为： 在每次发送组播检测请求报文后， 累计接 收到的单播检测应答报文数量， 如果接收到的响应报文数量大于 1 , 则用本 次计算出来的 RTT值减去上一次计算出来的 RTT值，即为本次的抖动时间。 当接收到的响应报文数量正好为 2 时， 此时平均抖动时间、 最大抖动时间 和最小抖动时间都为当前的抖动时间； 当收到的响应报文数量大于 2 时， 在计算出当前抖动时间后， 将当前抖动时间和之前的最大抖动时间和最小
抖动时间分别进行比较， 如果当前抖动时间大于之前的最大抖动时间， 则 把当前抖动时间作为新的最大抖动时间， 如果当前抖动时间小于之前的最 'J、抖动时间， 则把当前抖动时间作为新的最小抖动时间。
进一步， 为防止返回的单播检测应答报文的数量过大， 给组播源节点 造成过大的负担， 可以设定一个单播检测回应报文的最大接收数量， 例如
10个， 当所接收到的报文达到预先设定的单播检测回应报文的最大接收数 量时， 即使没有达到超时时间， 也停止处理接收到的单播检测回应报文。 所设定的单播检测回应报文的最大接收数量可以根据组播转发树的规模以 及组播源节点的处理能力来调整， 当组播转发树的规模较大时， 则可以适 当增大该单播检测回应报文的最大接收数量， 反之， 当组播转发树的规模 较小时， 则可以适当减小该单播检测回应报文的最大接收数量； 同样， 当 组播源节点的处理能力较强时， 则可以适当增大该单播检测回应报文的最 大接收数量， 反之， 当组播源节点的处理能力较弱时， 则可以适当减小该 单播检测回应报文的最大接收数量。
当然， 为了防止其它意外情况的发生或者在已知直连用户都已经回复 单播检测回应 ^艮文时减少等待终止的时间， 还可以在组播源节点设置终止 指令， 在接收到用户发送的终止指令时， 组播源节点立即停止处理接收到 的单播检测回应报文， 该终止指令可以是用户设置的命令语句， 也可以是 快捷键， 例如 ctrl+c, 还可以是点击操作界面上设定的按钮， 或者根据用户 的实际需要和习惯进行设置。
这样， 使得组播源停止处理接收到的单播检测回应报文的条件则包括 以下三点： 1、 达到预先设定的超时时间； 2、 达到预先设定的单播检测回 应报文的最大接收数量； 3、 接收到终止指令。
如果在达到预先设定的超时时间而没有接收到任何单播检测回应报 文， 为达到较佳的检测效果， 可以立即重新发起组播 ping并重新计时。 若
一直接收不到单播检测回应报文， 则可以一直继续该过程， 直至用户发出 停止指令， 也可以设置一个重试次数， 在达到该重试次数后， 不再重新发 起组播 ping。
由于组播源节点的处理能力有限， 为进一步防止返回的单播检测应答 报文的数量过大， 给组播源节点造成过大的负担， 还可以再设置一个限速 定时器， 在一定周期内控制进行组播 ping的次数， 在进行组播 ping前， 先 确定周期内的组播 ping次数没有达到预先设定的最大次数， 如果没有达到 预先设定的最大次数 ,则可以继续进行组播 ping，否则不允许进行组播 ping , 限速定时器超时后会将组播 ping次数统计清 0。 这样就可以避免短时间内 多次进行组播 ping, 使得组播源节点短时间内收到很多单播检测回应报文， 因 CPU处理能力不够造成报文丟失。
本发明实施例还相应提供一种检测组播转发树上两点间连通性的系 统， 如图 5所示， 包括： 组播源节点 501和组播转发树上的中间节点 502, 其中：
组播源节点 501 , 用于在发起组播转发树上两点间连通性检测时， 向组 播地址发送用于检测两点间连通性的组播检测请求报文， 接收中间节点返 502回的单播检测回应报文，并确定于设定时间内未接收到对应单播检测回 应才艮文的用户处于连通故障状态；
中间节点 502, 用于在每次接收到组播检测请求报文后， 根据路由表转 发组播检测请求报文， 并在每确定存在一个直接连接用户时， 向组播源节 点返回单播检测回应报文。
进一步地， 中间节点 502在每次接收到组播检测请求报文后查找路由 表， 获取该节点的出接口、 入接口和直连用户信息； 当该节点具有出接口 时， 判断出接口上是否存在直接连接的用户； 当该节点具有未直接连接用 户的出接口时， 复制组播检测请求报文， 并通过未直接连接用户的出接口
转发； 并在每确定存在一个直接连接用户时， 向组播源节点返回单播检测 回应报文。
进一步， 组播源节点还可以在接收到单播检测回应 ^艮文时计算往返时 延， 从而使得用户更全面的了解节点间的连通性， 此时， 组播源节点还用 于：
在发送组播检测请求报文时， 记录系统时间为发送时间；
在每次接收到单播检测回应报文时， 记录系统时间为回应时间； 以及 计算往返时延为回应时间与发送时间的差值。
组播源节点还可以进一步根据往返时延来计算抖动时间， 统计节点间 的连通性， 此时， 组播源节点还用于：
在除第一次以外的每次接收到单播检测回应 文时， 计算抖动时间为 本次计算的往返时延与上次计算的往返时延的差值。
由于组播源节点的处理能力有限， 为进一步防止短时间内返回的单播 检测应答报文的数量过大， 给组播源节点造成过大的负担， 还可以再设置 一个限速定时器，在一定周期内控制进行组播 ping的次数，在进行组播 ping 前， 先确定周期内的组播 ping次数没有达到预先设定的最大次数， 如果没 有达到预先设定的最大次数， 则可以继续进行组播 ping, 否则不允许进行 组播 ping, 限速定时器超时后会将组播 ping次数统计清 0。 此时， 组播源 节点还用于：
在向组播组地址发送用于检测两点间连通性的组播检测请求报文前， 确定设定周期内的组播检测请求报文发送次数没有达到预先设定的最大次 数。
组播源节点在达到终止条件时， 停止处理接收到的单播检测回应报文， 其中， 终止条件包括： 达到预先设定的超时时间； 或者达到预先设定的单 播检测回应报文的最大接收数量； 或者接收到终止指令。
本发明实施例还相应的提供一种检测组播转发树上两点间连通性的装 置， 该装置设置于组播转发树中发起组播 ping的组播源节点， 如图 6所示， 该装置包括：
组播检测请求 4艮文发送单元 601 ,用于向组播地址发送用于检测两点间 连通性的组播检测请求 ^艮文；
单播检测回应报文接收单元 602 ,用于接收中间节点返回的单播检测回 应报文；
确定单元 603 ,用于确定于设定时间内未接收到对应单播检测回应报文 的用户处于连通故障状态。
当组播源节点统计往返时延时， 该装置还包括：
记录单元 604, 用于在发送组播检测请求报文时， 记录系统时间为发送 时间； 在每次接收到单播检测回应报文时， 记录系统时间为回应时间； 往返时延计算单元 605 ,用于计算往返时延为回应时间与发送时间的差 值。
进一步， 该装置中还包括： 抖动时间计算单元 606, 用于在除第一次以 外的每次接收到单播检测回应^艮文时， 计算抖动时间为本次计算的往返时 延与上次计算的往返时延的差值。 进而统计报文往返的抖动时间， 评估节 点间的连通的稳定性。
为防止组播源节点的处理负担过重， 或防止其它意外情况的发生， 该 装置中还包括终止单元 607, 用于在达到终止条件时，停止处理接收到的单 播检测回应报文， 终止条件包括： 达到预先设定的超时时间； 或者达到预 先设定的单播检测回应报文的最大接收数量； 或者接收到终止指令。
本发明实施例还提供一种检测组播转发树上两点间连通性的装置， 该 装置可设置于组播转发树中接收到组播检测请求报文的中间节点， 如图 7 所示， 该装置包括：
组播检测请求报文接收单元 701 ,用于接收组播源节点发送的组播检测 请求报文；
转发单元 702, 用于在每次接收到组播检测请求报文后， 根据路由表转 发组播检测请求报文；
单播检测回应报文发送单元 703 ,用于在每确定存在一个直接连接用户 时 , 向组播源节点返回单播检测回应报文。
其中， 单播检测回应 ^艮文发送单元 703具体用于：
在每确定存在一个直接连接用户时， 通过接收到组播检测请求报文的 路径向组播源节点返回单播检测回应报文。
其中， 转发单元 702具体用于：
在每次接收到组播检测请求报文后查找路由表， 获取该节点的出接口、 入接口和直连用户信息；
当该节点具有出接口时， 判断出接口上是否存在直接连接的用户； 当该节点具有未直接连接用户的出接口时， 复制组播检测请求报文， 并通过未直接连接用户的出接口转发。 此处有直连用户的接口也需要转发 请求报文。
本发明实施例提供一种检测组播转发树上两点间连通性的方法、 系统 和装置， 通过 MPING ( Multicast Packet Internet Groper,组播报文网络搜索， 简称组播 ping )来检测组播源与组播组中各节点的连通性， 组播源发送组 播检测请求报文， 中间节点在接收到组播检测请求报文后， 根据路由表进 行转发， 并在有直连组播接收用户时， 向组播源返回单播检测回应报文， 从而实现组播源对组播组节点进行连通性检测的工作， 由于使用一对多的 方式进行组播转发树上两点间连通性的检测， 避免了分别对每一个节点进 行点对点故障检测， 减少了组播源对组播组节点进行连通性检测的工作量 并降低操作复杂度。
本发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权 利要求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在 内。
Claims
1、 一种检测组播转发树上两点间连通性的方法， 其特征在于， 包括： 组播转发树中发起组播转发树上两点间连通性检测的组播源节点， 向 组播组地址发送用于检测两点间连通性的组播检测请求报文；
组播转发树中的中间节点在每次接收到所述组播检测请求报文后， 根 据路由表转发所述组播检测请求报文， 并在每确定存在一个直接连接用户 时 , 向所述组播源节点返回单播检测回应报文；
所述组播源节点接收所述中间节点返回的单播检测回应 4艮文， 并确定 于设定时间内未接收到对应单播检测回应 4艮文的用户处于连通故障状态。
2、 如权利要求 1所述的方法， 其中， 所述向组播源节点返回单播检测 回应 4艮文的方法为：
通过接收到所述组播检测请求报文的路径向所述组播源节点返回所述 单播检测回应报文。
3、 如权利要求 1所述的方法， 其中， 所述组播转发树中的中间节点在 每次接收到所述组播检测请求报文后， 根据路由表转发所述组播检测请求 报文的步骤包括：
组播转发树中的中间节点在每次接收到所述组播检测请求报文后查找 路由表， 获取该节点的出接口、 入接口和直连用户信息；
当该节点具有出接口时， 判断所述出接口上是否存在直接连接的用户； 当该节点具有未直接连接用户的出接口时， 复制所述组播检测请求报 文， 并通过所述未直接连接用户的出接口转发。
4、 如权利要求 1所述的方法， 其中， 所述组播源节点向组播组地址发 送用于检测两点间连通性的组播检测请求报文的方法为：
所述组播源节点根据所述路由表向所有未直接连接用户的出接口发送 所述组播检测请求 4艮文。
5、 如权利要求 1所述的方法， 其中， 还包括：
所述组播源节点在发送所述组播检测请求 4艮文时， 记录系统时间为发 送时间； 并
在每次接收到单播检测回应报文时， 记录系统时间为回应时间； 以及
6、 如权利要求 5所述的方法， 其中， 还包括：
在除第一次以外的每次接收到单播检测回应 文时， 计算抖动时间为 本次计算的往返时延与上次计算的往返时延的差值。
7、 如权利要求 1所述的方法， 其中， 所述组播源节点向组播组地址发 送用于检测两点间连通性的组播检测请求报文之前， 还包括： 确定设定周 期内的组播检测请求报文发送次数没有达到预先设定的最大次数。
8、 如权利要求 1所述的方法， 其中还包括：
在达到终止条件时， 所述组播源节点停止处理接收到的单播检测回应 报文， 所述终止条件包括：
达到预先设定的超时时间； 或者
达到预先设定的单播检测回应报文的最大接收数量； 或者
接收到终止指令。
9、 如权利要求 1-8任一所述的方法， 其中所述组播检测请求报文和所 述单播检测回应报文均为 ICMP报文。
10、 一种检测组播转发树上两点间连通性的系统， 其特征在于， 包括： 组播源节点， 用于在发起组播转发树上两点间连通性检测时， 向组播 地址发送用于检测两点间连通性的组播检测请求报文， 接收返回的单播检 测回应报文， 并确定与设定时间内未接收到对应单播检测回应报文的用户 处于连通故障状态； 组播转发树上的中间节点， 用于在每次接收到所述组播检测请求报文 后， 根据路由表转发所述组播检测请求报文， 并在每确定存在一个直接连 接用户时， 向所述组播源节点返回单播检测回应报文。
11、 一种检测组播转发树上两点间连通性的装置， 其特征在于， 包括： 组播检测请求报文发送单元， 用于向组播地址发送用于检测两点间连 通性的组播检测请求 4艮文；
单播检测回应报文接收单元， 用于接收所述中间节点返回的单播检测 回应报文；
确定单元， 用于确定于设定时间内未接收到对应单播检测回应报文的 用户处于连通故障状态。
12、 如权利要求 11所述的装置， 其中， 还包括：
记录单元， 用于在发送所述组播检测请求^艮文时， 记录系统时间为发 送时间； 在每次接收到单播检测回应报文时， 记录系统时间为回应时间； 往返时延计算单元， 用于计算往返时延为所述回应时间与所述发送时 间的差值。
13、 如权利要求 12所述的装置， 其中， 还包括：
抖动时间计算单元， 用于在除第一次以外的每次接收到单播检测回应 报文时， 计算抖动时间为本次计算的往返时延与上次计算的往返时延的差 值。
14、 如权利要求 11所述的装置， 其中， 还包括：
终止单元， 用于在达到终止条件时， 停止处理接收到的单播检测回应 报文， 所述终止条件包括：
达到预先设定的超时时间； 或者
达到预先设定的单播检测回应报文的最大接收数量； 或者
接收到终止指令。
15、 一种检测组播转发树上两点间连通性的装置， 其特征在于， 包括： 组播检测请求报文接收单元， 用于接收组播源节点发送的组播检测请 求报文；
转发单元， 用于在每次接收到所述组播检测请求报文后， 根据路由表 转发所述组播检测请求报文；
单播检测回应报文发送单元， 用于在每确定存在一个直接连接用户时， 向所述组播源节点返回单播检测回应报文。
16、 如权利要求 15所述的装置， 其中， 所述转发单元在每次接收到所 述组播检测请求报文后查找路由表， 获取该节点的出接口、 入接口和直连 用户信息； 当该节点具有出接口时， 判断所述出接口上是否存在直接连接 的用户； 当该节点具有未直接连接用户的出接口时， 复制所述组播检测请 求报文， 并通过所述未直接连接用户的出接口转发。
Applications Claiming Priority (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201010542906.8 | 2010-11-12 | ||
| CN201010542906.8A CN101984587B (zh) | 2010-11-12 | 2010-11-12 | 一种检测组播转发树上两点间连通性的方法、系统和装置 |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2012062102A1 true WO2012062102A1 (zh) | 2012-05-18 |
Family
ID=43641759
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2011/074946 WO2012062102A1 (zh) | 2010-11-12 | 2011-05-31 | 一种检测组播转发树上两点间连通性的方法、系统和装置 |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN101984587B (zh) |
| WO (1) | WO2012062102A1 (zh) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109218122A (zh) * | 2017-06-30 | 2019-01-15 | 华为技术有限公司 | 一种实现传输性能检测的方法、装置和系统 |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101984587B (zh) * | 2010-11-12 | 2015-06-10 | 中兴通讯股份有限公司 | 一种检测组播转发树上两点间连通性的方法、系统和装置 |
| CN102271067B (zh) * | 2011-08-30 | 2017-08-11 | 南京中兴新软件有限责任公司 | 网络检测方法、装置及系统 |
| CN103236958B (zh) * | 2013-05-02 | 2016-04-20 | 北京京东尚科信息技术有限公司 | 用于在分布式系统中进行检测的系统和方法 |
| CN103475507B (zh) * | 2013-08-28 | 2016-10-05 | 华为技术有限公司 | 转发表项故障检测方法和装置 |
| CN103475654B (zh) * | 2013-09-06 | 2016-10-05 | 北京奇虎科技有限公司 | 网络路径优化方法、设备及网络系统 |
| CN104639385B (zh) * | 2013-11-13 | 2019-02-12 | 中兴通讯股份有限公司 | 检测l2vpn网络用户侧接口连通性的方法及设备 |
| CN107147508B (zh) * | 2016-03-01 | 2022-11-01 | 中兴通讯股份有限公司 | 故障检测方法及装置 |
| CN109039746B (zh) * | 2018-08-07 | 2022-02-25 | 新华三技术有限公司 | 检测双向转发路径检测会话状态的方法及处理器 |
| CN110445677B (zh) * | 2019-07-26 | 2021-05-07 | 新华三大数据技术有限公司 | 组播网络检测方法及转发设备 |
| CN110445678B (zh) * | 2019-07-26 | 2021-02-09 | 新华三大数据技术有限公司 | 组播网络检测方法、装置及转发设备 |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2000075962A2 (en) * | 1999-06-07 | 2000-12-14 | Nortel Networks Limited | Mechanism for splicing trees |
| CN101136788A (zh) * | 2006-08-30 | 2008-03-05 | 华为技术有限公司 | 一种mpls组播的故障定位方法及系统 |
| CN101616019A (zh) * | 2008-06-26 | 2009-12-30 | 华为技术有限公司 | 一种实现网络故障检测的方法、网络节点和系统 |
| CN101984587A (zh) * | 2010-11-12 | 2011-03-09 | 中兴通讯股份有限公司 | 一种检测组播转发树上两点间连通性的方法、系统和装置 |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2006074379A (ja) * | 2004-09-01 | 2006-03-16 | Ntt Docomo Inc | サーバ装置、送信端末、移動通信システム及び移動通信方法 |
-
2010
- 2010-11-12 CN CN201010542906.8A patent/CN101984587B/zh active Active
-
2011
- 2011-05-31 WO PCT/CN2011/074946 patent/WO2012062102A1/zh active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2000075962A2 (en) * | 1999-06-07 | 2000-12-14 | Nortel Networks Limited | Mechanism for splicing trees |
| CN101136788A (zh) * | 2006-08-30 | 2008-03-05 | 华为技术有限公司 | 一种mpls组播的故障定位方法及系统 |
| CN101616019A (zh) * | 2008-06-26 | 2009-12-30 | 华为技术有限公司 | 一种实现网络故障检测的方法、网络节点和系统 |
| CN101984587A (zh) * | 2010-11-12 | 2011-03-09 | 中兴通讯股份有限公司 | 一种检测组播转发树上两点间连通性的方法、系统和装置 |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109218122A (zh) * | 2017-06-30 | 2019-01-15 | 华为技术有限公司 | 一种实现传输性能检测的方法、装置和系统 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101984587B (zh) | 2015-06-10 |
| CN101984587A (zh) | 2011-03-09 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| WO2012062102A1 (zh) | 一种检测组播转发树上两点间连通性的方法、系统和装置 | |
| US8345540B2 (en) | Virtual snooping bridge in computer networks | |
| US8879429B2 (en) | Acknowledgement-based rerouting of multicast traffic | |
| CN100433730C (zh) | 组播点播方法及系统 | |
| WO2015180292A1 (zh) | 检测虚拟专用网络的用户网络侧接口连通性的方法及装置 | |
| WO2018001154A1 (zh) | 流路径的探测 | |
| WO2008037203A1 (en) | Method and node device for realizing the network topology discovery | |
| WO2009052712A1 (fr) | Procédé, système et routeur pour un transfert de flux de multidiffusion | |
| EP2494738A1 (en) | Method and apparatus for tracing a multicast flow | |
| CN109981323B (zh) | 一种检测数据链路层组播路径状态的方法和网络设备 | |
| WO2007073649A1 (fr) | Procede et systeme pour obtenir une unite de transfert maximale de voie dans un reseau | |
| WO2007073648A1 (fr) | Procede et systeme pour detecter une performance de multidiffusion ethernet | |
| WO2014019348A1 (zh) | 操作、管理和维护oam配置的方法、设备及系统 | |
| WO2011134295A1 (zh) | 一种收敛二层组播网络的方法及设备 | |
| WO2015149353A1 (zh) | 一种oam报文处理方法、网络设备和网络系统 | |
| WO2012088910A1 (zh) | 连通性故障检测方法和系统 | |
| WO2014117737A1 (zh) | Oam报文处理方法、设备及系统 | |
| CN101674199A (zh) | 用于实现网络故障时切换的方法及查询器 | |
| WO2013189414A2 (zh) | 网络拓扑自动获取方法及系统、网络查询及管理系统 | |
| WO2014101185A1 (zh) | 组播通道的性能检测方法、装置和系统 | |
| WO2014146541A1 (zh) | Cdn与网络融合系统、调度模块选定方法及计算机存储介质 | |
| CN101610200B (zh) | 组播路由的切换方法及装置 | |
| WO2012152134A1 (zh) | 以太网二层组播快速收敛的方法及以太网系统 | |
| US8848512B2 (en) | Rendezvous point convergence method and apparatus | |
| WO2012079405A2 (zh) | 链路的跟踪处理方法及系统 |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| 121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11839274 Country of ref document: EP Kind code of ref document: A1 |
|
| NENP | Non-entry into the national phase |
Ref country code: DE |
|
| 122 | Ep: pct application non-entry in european phase |
Ref document number: 11839274 Country of ref document: EP Kind code of ref document: A1 |