WO2019114779A1

WO2019114779A1 - Information collection

Info

Publication number: WO2019114779A1
Application number: PCT/CN2018/120785
Authority: WO
Inventors: 汪亮; 吴文; 李乐
Original assignee: 新华三技术有限公司
Priority date: 2017-12-13
Filing date: 2018-12-13
Publication date: 2019-06-20
Also published as: CN109218196B; CN109218196A

Abstract

Disclosed are an information collecting method and device, an electronic device and a machine-readable storage medium, which are applied to a network comprising an ingress node, a forwarding node and an egress node. According to an example of the method, after an ingress node sends a request message used for collecting information of a node, the ingress node may receive at least one response message for the request message; the ingress node, if acquiring node information and next hop information from the response message, records a correspondence between the node information and the next hop information, uses all of the responses messages received for the request message to regenerate a request message, and sends the regenerated request message; and the ingress node, if only acquiring the node information from the response message, determines that the node information pertains to an egress node.

Description

collect message

Cross-reference to related applications

The present application claims priority to Chinese Patent Application No. 2017113264694, filed on Dec. 13, 2017, the entire disclosure of which is incorporated herein by reference. The entire text is incorporated herein by reference.

Technical field

The present disclosure relates to the field of communications technologies, and in particular, to an information collecting method, apparatus, device, and machine readable storage medium.

Background technique

On a MPLS (Multi-Protocol Label Switching) network, you can create a tunnel between the ingress node and the egress node, such as an LSP (Label Switched Path) tunnel or TE ( Traffic Engineering, traffic engineering, tunnels, etc.

The ingress node can use MPLS Tracert technology to collect information about each node passing through the ingress node to the egress node, such as an IP address, a label, etc., to be able to locate the failed node.

Specifically, the ingress node may first send a request packet with a TTL (Time To Live) value of 1, and receive a response packet returned by the first node, and collect the first node from the response packet. information. Then, the ingress node sends a request message with a TTL value of 2, receives a response message returned by the second node, and collects information of the second node from the response message, and so on.

In the actual networking, if there is an equivalent path between the ingress node and the egress node, the ingress node may not collect the information of the node when collecting information of each node by using MPLS Tracert technology.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the drawings used in the description of the embodiments of the present disclosure will be briefly described below. It is obvious that the drawings in the following description are only the ones described in the present disclosure. For the embodiments, other drawings may be obtained by those skilled in the art in accordance with the drawings of the embodiments of the present disclosure.

1 is a flowchart of an information collecting method in an embodiment of the present disclosure;

2 is a flowchart of an information collecting method in another embodiment of the present disclosure;

3A is a schematic diagram of an application scenario in an embodiment of the present disclosure;

FIG. 3B is a schematic diagram of operations of the information collecting method in the application scenario shown in FIG. 3A according to an embodiment of the present disclosure; FIG.

3C is a schematic diagram of operations of the related art in the application scenario shown in FIG. 3A;

4 is a structural diagram of an information collecting device in an embodiment of the present disclosure;

5 is a hardware structural diagram of an ingress node in an embodiment of the present disclosure;

6 is a structural diagram of an information collecting device in another embodiment of the present disclosure;

FIG. 7 is a hardware structural diagram of a forwarding node in an embodiment of the present disclosure.

Detailed ways

The terminology used in the present disclosure is for the purpose of describing the particular embodiments, The singular forms "a", "the" and "the" It should also be understood that the term "and/or" as used herein refers to any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used in the present disclosure to describe various information, such information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, the first information may also be referred to as second information without departing from the scope of the present disclosure. Similarly, the second information may also be referred to as first information. Depending on the context, in addition, the word "if" may be interpreted to mean "at time" or "when" or "in response to determination."

The embodiment of the present disclosure proposes an information collecting method, which can be applied to a network including an ingress node, a forwarding node, and an egress node, such as an MPLS network. In the MPLS network, a tunnel, such as an LSP tunnel or a TE tunnel, is created between the ingress node and the egress node, and the node between the ingress node and the egress node is a forwarding node. The ingress node can use the MPLS Tracert technology to collect node information (such as IP address, label, etc.) and next hop information of the forwarding node, and node information (such as IP address, label, and so on) of the egress node. Based on this information, the failed node can be located.

In the above application scenario, referring to FIG. 1 , it is a flowchart of an information collecting method proposed in the embodiment of the present disclosure. This method can be applied to an ingress node. The method can include the following steps.

Step 101: Generate a request message for collecting information of the node.

Step 102: Send the request message, and receive a response message for the request message; if the node information (such as the IP address, label, etc. of the forwarding node) and the next hop information are obtained from the response message, Forwarding the IP address of the next hop of the node, etc., and recording the correspondence between the node information and the next hop information.

In an example, when the ingress node needs to collect the node information of the forwarding node by using the MPLS Tracert technology, it may generate a request packet for collecting information of the node, and send the request packet. If the destination node of the request packet is a forwarding node, the forwarding node may send a response packet for the request packet to the ingress node after receiving the request packet, where the response packet may carry the node of the forwarding node. Information and next hop information. In this way, after receiving the response packet, the ingress node can obtain the node information and the next hop information from the response packet, and locally record the correspondence between the node information and the next hop information.

In another example, if the target node of the request message is an egress node, the egress node may send a response packet for the request message to the ingress node after receiving the request message, and the response message may be Carry the node information of the egress node. The egress node does not have a corresponding next hop. Therefore, the response packet does not carry the next hop information of the egress node. In this way, after receiving the response packet for the request packet, the ingress node can obtain the node information of the egress node from the response packet, and locally record the node information of the egress node. Because the response packet does not carry the next hop information, the ingress node does not obtain the next hop information of the egress node from the response packet, and the next hop information of the egress node is not recorded locally.

Further, after receiving the response message sent by the egress node, the ingress node has collected the node information and the next hop information of the forwarding node and the node information of the egress node. Therefore, the ingress node stops the request packet sending operation, that is, the request packet is no longer sent, and the information collecting process can be ended.

Step 103: If at least two response messages for the request message are received, the request message is regenerated by using the at least two response messages, where the request message includes the next one of the at least two response messages. Jump information. Then, the operation of transmitting the request message and receiving the response message for the request message is returned.

In an example, a timer can also be started for the request message, and the time of the timer can be configured according to experience. Specifically, the ingress node sends a request packet and starts a timer for the request packet. After the timer expires, the ingress node may receive the time period from the time the packet is sent to the end of the timer. The number of response messages to the request message.

If the ingress node receives at least two response packets for the request message, the request message is regenerated by using the at least two response messages, and the regenerated request message may carry the at least The two respond to the next hop information of each message in the message, and then return to step 102.

If the ingress node receives only one response message for the request message, the request message is regenerated by using the one response message. In the regenerated request message, only the next hop information in the one response message may be carried, and then return to step 102.

In the foregoing embodiment, when the forwarding node between the ingress node and the egress node needs to forward the received request message, if the forwarding node has at least two next hops, the at least two next hops may be separately Send the request message. Specifically, if the forwarding node has at least two next hops, if the forwarding node is the target node of the request packet, the forwarding node may send a response packet to the ingress node, where the response packet may carry the forwarding node. The node information, the next hop information corresponding to each of the at least two next hops; if the forwarding node is not the target node of the request packet, the request message is sent to the at least two next hops respectively.

When the forwarding node is not the target node of the received request message, the request message needs to be forwarded.

In the above embodiment, the request message may include, but is not limited to, an mpls echo request message, and the response message may include, but is not limited to, an mpls echo reply message.

Based on the foregoing technical solution, in the embodiment of the present disclosure, when there is an equivalent path between the ingress node and the egress node, the MPLS Tracert technology can be used to collect the node information and the next hop information of each node, so that the collected nodes can be utilized. The node information and the next hop information accurately resolve the path between the ingress node and the egress node.

Based on the same concept as the above method, referring to FIG. 2, it is a flowchart of another information collecting method proposed in the embodiment of the present disclosure, which may be applied to a forwarding node between an ingress node and an egress node, and the forwarding is performed. The node has at least two next hops, and the method may include the following steps.

Step 201: Receive a request message sent by the ingress node, and determine whether the node is the target node of the request message; if the node is the target node of the request message, go to step 202; if the node is not the request message Step 203 is performed on the target node of the text.

Step 202: Send a response message for the request message to the ingress node, where the response message may carry the node information of the local node and the next hop information corresponding to the at least two next hops respectively.

Step 203: Obtain at least two new request messages, and send the obtained new request messages to the at least two next hops respectively. The number of new request packets obtained by the forwarding node is the same as the number of next hops.

In an example, after receiving the request message, if the TTL value carried in the request message is a specified value (such as 1), the forwarding node determines that the node is the target node of the request message. However, if the TTL value carried in the request packet is not a specified value, it is determined that the node is not the target node of the request message. In this case, the forwarding node modifies the TTL value of the request packet (for example, minus 1) to obtain a new request packet, and sends the new request based on the next hop information of the local node carried in the response packet. Message.

Based on the foregoing technical solution, in the embodiment of the present disclosure, when there is an equivalent path between the ingress node and the egress node, the node information and the next hop information of each node may be collected by using the MPLS Tracert technology, so that the node information of each node may be utilized. The next hop information accurately resolves the path between the ingress node and the egress node.

The above information collecting method will be described below in conjunction with the application scenario shown in FIG. 3A. Referring to Figure 3A, network device 301 is an ingress node, network devices 302-305 are forwarding nodes, and network device 306 is an egress node. In addition, network device 302 has two next hops (i.e., network devices 303 and 304), while network devices 303-305 each have only one next hop.

As shown in FIG. 3A, the management IP address of the network device 301 is 1.1.1.1, and the IP address of the interface 3011 is 11.1.1.1. The management IP address of the network device 302 is 2.2.2.2, the IP address of the interface 3021 is 11.1.1.2, the IP address of the interface 3022 is 12.1.1.1, and the IP address of the interface 3023 is 14.1.1.1. For the management IP address and interface IP address of other network devices, refer to Figure 3A, and details are not described herein.

It should be noted that the management IP address of the network device refers to an MPLS LSR-ID (Label Switch Router-IDentity) address. In the service deployment of the MPLS network, an LSR-ID address needs to be assigned to each network device supporting the MPLS service. The meaning of the LSR-ID address is the name of the network device in the MPLS network. The IP address of the above interface is also referred to as an interface IP address hereinafter.

In the above application scenario, in order to collect node information (such as IP address, label, etc.) and next hop information of a forwarding node (such as network devices 301 to 305), node information (such as an IP address) of an egress node (such as network device 306) The label collection method may include the following steps as shown in FIG. 3B.

Step a, the network device 301 sends a request message 1 and starts a timer 1 for the request message 1.

When the network device 301 collects the node information, the next hop information, and the node information of the egress node by using the MPLS Tracert technology, the request message 1 is generated, and the request message 1 is sent through the interface 3011. The packet type of the request packet 1 may be a UDP (User Datagram Protocol) type. In the IP header of the request packet 1, the source IP address is the IP address 11.1.1.1 of the interface 3011, and the destination IP address is 127.0.0.1 (the address represents a local address, which means any network device that receives the packet. The message is processed directly instead of forwarding, and the TTL value is 1. In the UDP header of the request packet 1, the source port is a variable value X (can be dynamically adjusted as needed, and is not limited thereto), and the destination port is a fixed value (for example, 3503), and the destination port indicates that the request packet 1 is used. LSP ping (Label Switching Path ping) is performed, that is, MPLS Tracert technology is being used to collect information about each node in the path. In addition, the request message 1 may further carry mpls echo information, and the mpls echo information may include tunnel information, such as label information corresponding to the interface 3011, and the label information is a tunnel between the network devices 301-306 (such as an LSP tunnel or a TE tunnel). ) tag information. In addition, the mpls echo information may also include the IP address 11.1.1.2 of the interface 3021.

The network device 301 can start the timer 1 for the request message 1, and the time of the timer 1 can be configured according to experience. After the timer 1 times out, the network device 301 can count the number of response messages received by the device for the request message 1 in the period from the transmission of the request message 1 to the end of the timer 1 timeout.

Step b: After receiving the request message 1, the network device 302 decrements the TTL value of the request message 1 by one. The modified TTL value is 0, and the destination port is a fixed value (for example, 3503). Therefore, it is determined that the request message 1 is used to perform LSP ping, and the response packet 1 for the request message 1 is sent to the network device 301.

Since the network device 302 receives the request message 1 through the interface 3021, and the request message 1 carries the IP address 11.1.1.2 of the interface 3021, the network device 302 sends the response message 1 through the interface 3021.

The packet type of the response packet 1 can be of the UDP type. In the IP header of the response packet 1, the source IP address is the IP address 11.1.1.2 of the interface 3021, and the destination IP address is the IP address 11.1.1.1 of the interface 3011 (the source IP address of the request packet 1), and the TTL value is 255. . In the UDP header of the response packet 1, the source port is a fixed value (such as 3503) to indicate that the response packet 1 is used to perform LSP ping, and the destination port is a variable value X (can be dynamically adjusted as needed). In addition, the response message 1 can also carry the mpls echo information, and the mpls echo information can include the node information of the network device 302 (such as the management IP address of the network device 302, the interface IP address, the label of the interface, etc., and the node information is not limited. The next hop information of the network device 302, the next hop information may also be referred to as downstream information.

The next hop information of the network device 302 may include: an IP address of the next hop corresponding to the interface 3022, that is, an IP address 12.1.1.2 of the interface 3031 of the network device 303; and an IP address of the next hop corresponding to the interface 3023, that is, The IP address of the interface 3041 of the network device 304 is 14.1.1.2.

The network device 302 can obtain the next hop information of the network device 302 from the local device based on the tunnel information (such as the label information corresponding to the interface 3011).

Step c: After the timer 1 times out, the network device 301 counts the number of response messages received for the request message 1 in the time period from the sending of the request message 1 to the end of the timer 1 time. Since only the response message 1 is received, the node information and the next hop information of the network device 302 are obtained from the response message 1, and the correspondence between the node information and the next hop information is recorded, and the request message is generated by using the response message 1. In the text 2, the request message 2 is sent, and the timer 2 is started for the request message 2.

The network device 301 can obtain the node information of the network device 302 (such as the IP address 11.1.1.2 of the interface 3021, the management IP address 2.2.2.2, the label of the interface 3021, etc.) and the next hop information (such as the IP address) from the response message 1. 12.1.1.2 and 14.1.1.2), and record the correspondence shown in Table 1. In Table 1, the IP address 11.1.1.2 with the node information as the interface is taken as an example, and the content of the corresponding relationship is not limited.

Table 1

TTLTTL	节点信息Node information	下一跳信息 Next hop information
11	11.1.1.211.1.1.2	12.1.1.2和14.1.1.212.1.1.2 and 14.1.1.2

Based on Table 1, the TTL value of 1 indicates the next hop of the network device 301, 11.1.1.2 is the interface IP address of the next hop, and the next hop to the egress node has two next hops, the two next hops. The IP addresses of the interfaces are 12.1.1.2 and 14.1.1.2.

For the process of generating the request message 2 by using the response message 1, the request message 2 may carry the next hop information in the response message 1, for example, the request message 2 carries the IP address of the next hop interface 12.1.1.2 and 14.1.1.2.

The content of the request message 2 is similar to the content of the request message 1, except that the TTL value of the request message 2 is 2, and the mpls echo information of the request message 2 includes the next hop information in the response message 1. That is, IP addresses 12.1.1.2 and 14.1.1.2. The content of this request message 2 will not be repeated here.

Step d: After receiving the request message 2, the network device 302 decrements the TTL value of the request message 2 by 1 to obtain the request message 3. Since the TTL value of the request message 3 is 1, instead of 0, the network device 302 is not the target node of the request message 3, and needs to continue to forward the request message 3. When forwarding the request message 3, since the network device 302 has two next hops (ie, network devices 303 and 304), the network device 302 transmits the request message 3 through the

interfaces

3022, 3023.

When the network device 302 parses the destination port from the request packet 3 to a fixed value (for example, 3503), it determines that the request packet 3 is used to perform LSP ping, and determines that the request packet 3 needs to be forwarded.

The network device 302 can copy (N-1) request messages 3, thereby obtaining N request messages 3, where N is the next hop count of the network device 302. Thus, network device 302 can send a request message 3 to each next hop.

Step e: After receiving the request message 3, the network device 303 decrements the TTL value of the request message 3 by one. Since the modified TTL value is 0, and the destination port is a fixed value (for example, 3503), it is determined that the request message 3 is used to perform LSP ping, and the response packet 2 for the request message 3 is sent to the network device 301. After receiving the request message 3, the network device 304 decrements the TTL value of the request message 3 by one. Since the modified TTL value is 0, and the destination port is a fixed value (for example, 3503), it is determined that the request message 3 is used to perform LSP ping, and the response packet 3 for the request message 3 is sent to the network device 301.

Since the network device 303 receives the request message 3 through the interface 3031, and the request message 3 carries the IP address 12.1.1.2 of the interface 3031, the network device 303 sends the response message 2 through the interface 3031.

For the same reason, the network device 304 receives the request message 3 through the interface 3041, and the request message 3 carries the IP address 14.1.1.2 of the interface 3041. Therefore, the network device 304 sends the response message 3 through the interface 3041.

The content of the response packet 2 is similar to the content of the response packet 1. The difference between the two is that the source IP address of the response packet 2 is the IP address 12.1.1.2 of the interface 3031, and the mpls echo carried by the response packet 2 is The information may include the node information of the network device 303 (such as the management IP address, the interface IP address, the label of the interface, etc.), and the next hop information of the network device 303 (such as the IP address of the next hop corresponding to the interface 3032, that is, the network device 305). The IP address of interface 3051 is 13.1.1.2).

In addition, the content of the response packet 3 is similar to the content of the response packet 1. The difference between the two may be that the source IP address of the response packet 3 is the IP address 14.1.1.2 of the interface 3041, and the response packet 3 carries. The mpls echo information may include the node information of the network device 304 (such as the management IP address, the interface IP address, the label of the interface, and the like), and the next hop information of the network device 304 (such as the IP address of the next hop corresponding to the interface 3042, that is, the network. The IP address of the interface 3052 of the device 305 is 15.1.1.2).

Step f: After the timer 2 expires, the network device 301 counts the number of response messages received for the request message 2 in the time period from the sending of the request message 2 to the end of the timer 2 counting. The response message 2 and the response message 3 are received. Therefore, the node information and the next hop information of the network device 303 are obtained from the response message 2, and the correspondence between the node information and the next hop information is recorded. The node information and the next hop information of the network device 304 are obtained in the response message 3, and the corresponding relationship between the node information and the next hop information is recorded. Then, the response message 2 and the response message 3 are used to generate the request message 4, the request message 4 is sent, and the timer 3 is started for the request message 4.

After the network device 301 obtains the node information of the network device 303, the next hop information, the node information of the network device 304, and the next hop information, the corresponding relationship table is shown in Table 2.

Table 2

TTLTTL	节点信息Node information	下一跳信息 Next hop information
11	11.1.1.211.1.1.2	12.1.1.2和14.1.1.212.1.1.2 and 14.1.1.2
22	12.1.1.212.1.1.2	13.1.1.213.1.1.2
22	14.1.1.214.1.1.2	15.1.1.215.1.1.2

For the process of generating the request message 4 by using the response message 2 and the response message 3, the request message 4 may carry the next hop information in the response message 2, that is, the IP address 13.1.1.2, and may carry the response message. The next hop information in the text 3, that is, the IP address 15.1.1.2, for example, the request message 4 carries the IP addresses 13.1.1.2 and 15.1.1.2.

The content of the request message 4 may be similar to the content of the request message 1. The difference may be that the TTL value of the request message 4 is 3; the mpls echo information of the request message 4 includes the response message 2 and the response message 3 The next hop information in the middle, namely IP addresses 13.1.1.2 and 15.1.1.2, will not be repeated here.

After receiving the request message 4, the network device 302 decrements the TTL value of the request message 4 by 1 to obtain the request message 5, and sends the request message 5 through the

interfaces

3022 and 3023, respectively. After receiving the request message 5, the network device 303 decrements the TTL value of the request message 5 by 1 to obtain the request message 6, and sends the request message 6 through the interface 3032. After receiving the request message 5, the network device 304 decrements the TTL value of the request message 5 by 1 to obtain the request message 7, and sends the request message 7 through the interface 3042.

In step h, after receiving the request message 6, the network device 305 decrements the TTL value of the request message 6 by 1, because the modified TTL value is 0, and the destination port is a fixed value (such as 3503), therefore, to the network The device 301 sends a response message 4 for the request message 6. After receiving the request message 7, the network device 305 decrements the TTL value of the request message 7 by 1. Since the modified TTL value is 0, and the destination port is a fixed value (such as 3503), the network device 305 sends the TTL value to the network device 301. Response message 5 for request message 7.

Since the network device 305 receives the request message 6 through the interface 3051, and the request message 6 carries the IP address 13.1.1.2 of the interface 3051, the network device 305 sends the response message 4 through the interface 3051.

For the same reason, the network device 305 receives the request message 7 through the interface 3052, and the request message 7 carries the IP address 15.1.1.2 of the interface 3052. Therefore, the network device 305 sends the response message 5 through the interface 3052.

The content of the response packet 4 is similar to that of the response packet 1. The difference is that the source IP address of the response packet 4 is the IP address 13.1.1.2 of the interface 3051, and the mpls echo information carried in the response packet 4 may include the network. The node information of the device 305 and the next hop information of the network device 305 (such as the IP address of the next hop corresponding to the interface 3053, that is, the IP address 16.1.1.2 of the interface 3061 of the network device 306). The content of the response message 5 is similar to that of the response message 4, except that the source IP address is the IP address 15.1.1.2 of the interface 3052.

Step i: After the timer 3 expires, the network device 301 counts the number of response messages received for the request message 4 in the time period from the sending of the request message 4 to the end of the timer 3 counting. Obtaining the response message 4 and the response message 5, the node information and the next hop information of the network device 305 are obtained from the response message 4, and the correspondence between the node information and the next hop information is recorded. The node information and the next hop information of the network device 305 are obtained in the response message 5, and the correspondence between the node information and the next hop information is recorded. Then, the response message 4 is generated by using the response message 4 and the response message 5, the request message 8 is transmitted, and the timer 4 is started for the request message 8.

The correspondence table regenerated by the network device 301 is shown in Table 3. No limitation is imposed on this.

table 3

TTLTTL	节点信息Node information	下一跳信息 Next hop information
11	11.1.1.211.1.1.2	12.1.1.2和14.1.1.212.1.1.2 and 14.1.1.2
22	12.1.1.212.1.1.2	13.1.1.213.1.1.2
22	14.1.1.214.1.1.2	15.1.1.215.1.1.2
33	13.1.1.213.1.1.2	16.1.1.216.1.1.2
33	15.1.1.215.1.1.2	16.1.1.216.1.1.2

For the process of generating the request message 8 by using the response message 4 and the response message 5, since the next hop information carried in the response message 4 and the response message 5 is the IP address 16.1.1.2, the request message 8 is carried. The next hop information is the IP address 16.1.1.2. The content of the request message 8 is similar to the content of the request message 1, and the difference may be that the TTL value of the request message 8 is 4, and the next hop information carried is the IP address 16.1.1.2, which is not repeated. Narration.

Step j: After receiving the request message 8, the network device 302 decrements the TTL value of the request message 8 by 1, and sends the TTL value modified request message 8 through the

interfaces

3022 and 3023 respectively. After receiving the TTL value modified request message 8, the network device 303, 304 decrements the TTL value of the received request message by 1 and sends the TTL value modified request message through the interface 3032/interface 3042, respectively. 8. After receiving the request message 8 whose TTL value is modified again, the network device 305 decrements the TTL value of the received request message by 1, and sends the TTL value modified request message three times through the interface 3053. Finally, the network device 306 receives two request messages, and refers to the two request messages as the request message 9 and the request message 10.

Step k: After receiving the request message 9, the network device 306 decrements the TTL value of the request message 9 by 1. Since the TTL value is 0, the destination port is a fixed value, so the network device 301 sends the request message 9 Respond to message 6. Similarly, a response message 7 for the request message 10 is sent to the network device 301.

Since the network device 306 receives the request message 9/10 through the interface 3061, and the request message 9/10 carries the IP address 16.1.1.2 of the interface 3061, the network device 306 sends the response message 6/response message through the interface 3061. 7.

The content of the response packet 6/7 is similar to that of the response packet 1. The difference is that the source IP address of the response packet 6/7 is the IP address 16.1.1.2 of the interface 3061, and the response packet 6/7 is carried. The mpls echo information may include node information of the network device 306 and does not carry next hop information.

Step 1. After the timer 4 expires, the network device 301 counts the number of response messages received for the request message 8 in the time period from the transmission of the request message 8 to the end of the timer 4 timeout. Since the response message 6 and the response message 7 are received, and the content of the response message 6 and the response message 7 are the same, the node information of the network device 306 is obtained from the response message 6, and the node information is recorded. The correspondence table regenerated by the device 301 is shown in Table 4, and no limitation is imposed thereon.

Table 4

TTLTTL	节点信息Node information	下一跳信息 Next hop information
11	11.1.1.211.1.1.2	12.1.1.2和14.1.1.212.1.1.2 and 14.1.1.2
22	12.1.1.212.1.1.2	13.1.1.213.1.1.2
22	14.1.1.214.1.1.2	15.1.1.215.1.1.2
33	13.1.1.213.1.1.2	16.1.1.216.1.1.2
33	15.1.1.215.1.1.2	16.1.1.216.1.1.2
44	16.1.1.216.1.1.2

The response packet 6/7 does not carry the next hop information. Therefore, the IP address 16.1.1.2 is the node information of the egress node, stops the sending of the request packet, and ends the information collection process. So far, the network device 301 collects the node information and the next hop information of the forwarding node and the node information of the egress node, as shown in Table 4.

In the above embodiment, after the timer expires, if the network device 301 still does not receive the response packet for the request packet, the current hop (that is, the network device corresponding to the TTL value) is considered unreachable, and the TTL value is obtained. Add 1 to get a new request message, and send the new request message to continue to probe the next hop.

In the above embodiment, the timers started for different request messages may be the same time or different. For example, the time of the timer is related to the TTL value of the request message. For example, when the TTL value of the request message is larger, the timer time is larger.

In another example, as shown in FIG. 3C, in step d' corresponding to step d shown in FIG. 3B, the network device 302 does not send the request message 3 through the interface 3022 and the interface 3023, but adopts a hash algorithm. An interface is selected from the interface 3022 and the interface 3023. Assuming that the selection interface 3022 sends the request message 3, only the network device 303 will send a response message for the request message 2 (step e'). In this way, when the network device 301 sends the request message 4 again (step f'), it carries the next hop information of the network device 303, that is, the IP address 13.1.1.2, and does not carry the next hop information of the network device 304. That is, the IP address is 15.1.1.2.

Next, when the network device 302 transmits the request message 5 obtained from the request message 4 (step g'), it continues to select an interface from the interface 3022 and the interface 3023 by using a hash algorithm. Assume that the selection interface 3023 sends the request message 5, the network device 305 will receive the request message 7 obtained from the request message 5 through the interface 3052, and the request message 7 carries the IP address 13.1.1.2 of the interface 3051. Not the IP address 15.1.1.2 of interface 3052. In this case, the network device 305 will not be able to send the correct response message to the network device 301, thereby causing the network device 301 to fail to correctly collect the information of the network device 305.

Based on the same concept as the above method, the embodiment of the present disclosure further provides an information collecting device, which can be applied to an ingress node. As shown in FIG. 4, which is a structural diagram of the device, the device may include:

a generating module 401, configured to generate a request message for collecting information of the node;

The sending module 402 is configured to send a request message.

The receiving module 403 is configured to receive at least one response packet for the request packet.

The processing module 404 is configured to obtain node information and next hop information from the at least one response packet, and record a correspondence between the node information and the next hop information.

The generating module 401 is further configured to regenerate the request message by using the received at least one response message for the request message, where the request message includes all the at least one response message. One-hop information; the re-generated request message is sent by the sending module 402.

The generating module 401 is further configured to: after the sending module 402 sends the request message, start a timer for the request message; after the timer expires, the statistics start from sending the request message to the timer. The number of response messages received for the request message in the time period after the end of the timeout period; if at least two response messages are received, the request message is regenerated by using the at least two response messages; And receiving a response message, and regenerating the request message by using the one response message, where the request message includes next hop information in the one response message.

The processing module 404 is further configured to: obtain node information of the egress node from the response packet, record node information of the egress node, and stop sending the request message.

An electronic device (such as an ingress node) provided by an embodiment of the present disclosure may be as shown in FIG. 5 from a hardware level. The electronic device includes a machine readable storage medium 501 and a processor 502.

Machine-readable storage medium 501 stores machine-executable instructions that are executable by processor 502.

The processor 502 is in communication with the machine readable storage medium 501, reads and executes the machine executable instructions stored in the machine readable storage medium 501, and implements the information collection operations disclosed by the above examples of the present disclosure.

Here, machine-readable storage medium 501 can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as a hard disk drive), solid state drive, any type of storage disk. (such as a disc, dvd, etc.), or a similar storage medium, or a combination thereof.

Based on the same concept as the above method, the embodiment of the present disclosure further provides an information collecting apparatus, which may be applied to a forwarding node between an ingress node and an egress node, and the forwarding node has at least two next hops. As shown in FIG. 6, which is a structural diagram of the device, the device may include:

The receiving module 601 is configured to receive a request message sent by the ingress node;

The sending module 602 is configured to: when the local node is the target node of the request message, send a response message to the ingress node; the response message carries the node information of the local node, and the at least two next hops correspond to The next hop information; when the local node is not the target node of the request message, the at least two request messages are obtained, and the obtained request message is separately sent to the at least two next hops.

In an example, the information collecting apparatus further includes a determining module (not shown in the figure), and the determining module is configured to: after receiving the request message, if the TTL value carried in the request packet is specified The value is determined to be the target node of the request message; if the TTL value carried in the request message is not a specified value, it is determined that the node is not the target node of the request message.

The electronic device (such as a forwarding node) provided by the embodiment of the present disclosure can be seen from the hardware level as shown in FIG. 7 . A machine readable storage medium 701 and a processor 702 are included.

Machine-readable storage medium 701 stores machine-executable instructions that are executable by the processor 702.

The processor 702 is in communication with the machine readable storage medium 701, reads and executes the machine executable instructions stored in the machine readable storage medium 701, and implements the information collection operations disclosed by the above examples of the present disclosure.

Here, machine-readable storage medium 701 can be any electronic, magnetic, optical, or other physical storage device that can contain or store information, such as executable instructions, data, and the like. For example, the machine-readable storage medium may be: RAM (Radom Access Memory), volatile memory, non-volatile memory, flash memory, storage drive (such as a hard disk drive), solid state drive, any type of storage disk. (such as a disc, dvd, etc.), or a similar storage medium, or a combination thereof.

The system, device, module or unit illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product having a certain function. A typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, and a game control. A combination of a tablet, a tablet, a wearable device, or any of these devices.

For the convenience of description, the above devices are described separately by function into various units. Of course, the functions of the various units may be implemented in one or more software and/or hardware in the practice of the present disclosure.

Those skilled in the art will appreciate that embodiments of the present disclosure can be provided as a method, system, or computer program product. Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware aspects. Moreover, embodiments of the present disclosure may take the form of a computer program product embodied on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) including computer usable program code.

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present disclosure. It will be understood that each flow and/or block of the flowchart illustrations and/or FIG. These computer program instructions can be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing device to produce a machine for the execution of instructions for execution by a processor of a computer or other programmable data processing device. Means for implementing the functions specified in one or more of the flow or in a block or blocks of the flow chart.

Moreover, these computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device. The instruction means implements the functions specified in one or more blocks of the flowchart or in a flow or block diagram of the flowchart.

These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

The above description is only for the embodiments of the present disclosure, and is not intended to limit the disclosure. Various changes and modifications of the present disclosure are possible to those skilled in the art. Any modifications, equivalents, improvements, etc. made within the spirit and scope of the present disclosure are intended to be included within the scope of the appended claims.

Claims

An information collecting method is applied to an ingress node, and the method includes:

Generating a request message for collecting information of the node;

Sending the request message;

Receiving at least one response message for the request message;

If the node information and the next hop information are obtained from the at least one response packet,

Recording a correspondence between the node information and the next hop information;

And regenerating the request message by using all the at least one response message received by the request message, where the regenerated request message includes the next one of each of the received at least one response message One-hop information;

Returning an operation of executing the sending request message and receiving at least one response message for the request message;

If the node information is obtained from the at least one response message but the next hop information is not obtained, it is confirmed that the node information belongs to an egress node.
The method according to claim 1, wherein receiving at least one response message for the request message comprises:

After the request message is sent, a timer is started for the request message;

After the timer expires, the number of at least one response message received for the request message received from the time when the request message is sent to the end of the timer is counted.
The method of claim 1 further comprising:

Recording node information of the egress node, and stopping the operation of sending the request message.
An information collecting method is applied to a forwarding node between an ingress node and an egress node, and the forwarding node has at least two next hops, and the method includes:

Receiving a request message sent by the ingress node;

If the forwarding node is a target node of the request message, then

Sending a response packet to the ingress node; the response packet carries node information of the forwarding node, and next hop information corresponding to the at least two next hops;

If the forwarding node is not the target node of the request message, then

Updating the request message to obtain an updated request message, and

Sending the updated request message to the at least two next hops respectively.
The method of claim 4 wherein:

If the TTL value carried in the request packet is a specified value, determining that the forwarding node is a target node of the request packet;

And if the TTL value carried in the request packet is not a specified value, determining that the forwarding node is not a target node of the request packet.
The method of claim 5, wherein the updating the request message comprises:

The TTL value carried in the request packet is updated according to a preset rule.
An information collecting device is applied to an ingress node, the device comprising:

a generating module, configured to generate a request message for collecting information of the node;

a sending module, configured to send the request message;

a receiving module, configured to receive at least one response message for the request message;

a processing module, configured to: if node information and next hop information are obtained from the at least one response packet,

Recording a correspondence between the node information and the next hop information;

And causing the generating module to regenerate the request message by using the at least one response message received by the request message, where the regenerated request message includes each of the received at least one response message The next hop information; and the retransmitted request message is sent by the sending module;

The processing module is further configured to: if the node information is acquired from the at least one response message but the next hop information is not obtained, confirm that the node information belongs to an egress node.
The apparatus of claim 7, wherein the processing module is configured to:

After the sending module sends the request message, start a timer for the request message;

After the timer expires, the receiving module receives at least one response packet for the request packet in a period from the time the packet is sent to the end of the timer. quantity.
The device of claim 7 wherein:

The processing module is further configured to record node information of the egress node, and cause the sending module to stop the operation of sending the request message.
An information collecting apparatus is applied to a forwarding node between an ingress node and an egress node, and the forwarding node has at least two next hops, and the apparatus includes:

a receiving module, configured to receive a request message sent by the ingress node;

Send module for

And when the forwarding node is the target node of the request packet, sending a response packet to the ingress node; the response packet carrying node information of the forwarding node, and the at least two next hops corresponding to Next hop information;

And when the forwarding node is not the target node of the request message, updating the request message to obtain an updated request message, and separately sending the updated request to the at least two next hops Message.
The device according to claim 10, further comprising a determining module for

If the TTL value carried in the request packet is a specified value, determining that the forwarding node is a target node of the request packet;

And if the TTL value carried in the request packet is not a specified value, determining that the forwarding node is not a target node of the request packet.
An electronic device comprising:

Processor; and

a machine-readable storage medium storing machine-executable instructions executable by the processor;

Wherein the processor executes the machine executable instructions to implement the method of claim 1.
An electronic device comprising:

Processor; and

a machine-readable storage medium storing machine-executable instructions executable by the processor;

Wherein the processor executes the machine executable instructions to implement the method of claim 4.
A machine readable storage medium storing machine executable instructions that, when invoked and executed by a processor, cause the processor to implement a right The method of claim 1.
A machine readable storage medium storing machine executable instructions that, when invoked and executed by a processor, cause the processor to implement a right The method described in claim 4.