Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A method comprising: in response to an initiator node receiving a command to start a connectivity test for a label switched path (LSP), accessing state information stored in memory and determining whether the state information indicates that the LSP comprises an LSP segment that implements entropy label load balancing; in response to determining that the state information indicates that the LSP does not comprise an LSP segment that implements entropy label load balancing, the initiator node generating a first echo request message that comprises a first multipath information type; the initiator node transmitting the first echo request message to a first transit node of the LSP.
To test network connectivity along a Label Switched Path (LSP) that may use entropy label load balancing, the initiating node first checks a stored state to see if entropy label load balancing is already detected on the LSP. If the state indicates no entropy label usage, the initiating node creates a first "echo request" message containing a basic multipath information type. This initial request is then sent to the first node along the LSP to begin the connectivity test. This allows discovery of entropy label usage.
2. The method of claim 1 further comprising the initiator node initializing the state information to indicate the LSP does not comprise an LSP segment that implements entropy load balancing.
Before starting the LSP connectivity test, the initiating node initializes a stored state variable to indicate that entropy label load balancing is NOT currently being used on the LSP. This ensures that the first "echo request" message sent uses the basic multipath information type, allowing the initiator node to discover if entropy labels are in use. This initialization step provides a clean slate for the test.
3. The method of claim 2 further comprising: in response to the initiator node receiving a first echo response from the first transit node, the initiator node updating the state information to indicate that the LSP comprises an LSP segment that implements entropy label load balancing; in response to updating the state information, the initiator node generating a second echo request message that comprises a second multipath information type; the initiator node transmitting the second echo request message to a second transit node of the LSP; wherein the first and second multipath information types are distinct from each other.
If the initiating node receives a response to the first "echo request" message, it updates its stored state to indicate that the LSP now uses entropy label load balancing. Based on the updated state, the initiating node then generates a second "echo request" message containing a different multipath information type designed for entropy labels. This second request is then sent to the next transit node in the LSP. The first and second request message formats are distinct to accommodate the entropy label information.
4. The method of claim 3 further comprising the initiator node copying multipath information from the first echo response to the second echo request before the initiator node transmits the second echo request.
After receiving the first "echo response" message, the initiating node copies the multipath information received in the response into the second "echo request" message, before sending the second request. By incorporating this information, the subsequent request builds upon the knowledge gained from the previous hop, allowing for more comprehensive path discovery and understanding of the network's forwarding behavior.
5. The method of claim 4 further comprising the initiator node copying associated label information from the first echo response to the second echo request before the initiator node transmits the second echo request.
Following receipt of the first "echo response," the initiating node copies label information associated with the multipath data from the initial echo response and includes it in the subsequent second "echo request", before transmission. This inclusion of associated label information ensures that the receiving node has sufficient context regarding the labeling scheme employed along the path, which is particularly crucial when entropy labels are involved.
6. The method of claim 5 wherein the first echo reply comprises downstream mapping information and a set of entropy labels.
The first "echo reply" message received by the initiator node includes both downstream mapping information and a set of entropy labels. The downstream mapping information specifies how traffic is being forwarded at the transit node, and the entropy labels provide details about the load balancing scheme implemented. This combined information helps the initiator node understand the path characteristics.
7. An initiator node comprising: a processor, and; an instruction memory coupled to the processor and configured to store instructions executable by the processor, wherein the processor is configured to implement a method in response to executing the stored instructions, the method comprising: accessing state information stored in memory and determining whether the state information indicates that a label switched path (LSP) comprises an LSP segment that implements entropy label load balancing; in response to determining that the state information indicates that the LSP does not comprise an LSP segment that implements entropy label load balancing, generating a first echo request message that comprises a first multipath information type, and; transmitting the first echo request message to a first transit node of the LSP.
An initiator node, implemented via a processor and associated memory, executes instructions to perform LSP connectivity tests. The node first checks its stored state to determine if entropy label load balancing is used on the LSP. If not, it generates a first "echo request" message containing a basic multipath information type. This initial request is then transmitted to the first transit node along the LSP.
8. The initiator node of claim 7 wherein the method further comprises initializing the state information to indicate the LSP does not comprise an LSP segment that implements entropy load balancing.
The initiator node (described in the previous connectivity test process) initializes the stored state variable to indicate that entropy label load balancing is NOT being used on the LSP. This initialization ensures the first "echo request" uses a basic multipath type to discover entropy labels.
9. The initiator node of claim 8 wherein the method further comprises: in response to receiving a first echo response from the first transit node, updating the state information to indicate that the LSP comprises an LSP segment that implements entropy label load balancing; in response to updating the state information, generating a second echo request message that comprises a second multipath information type; transmitting the second echo request message to a second transit node of the LSP; wherein the first and second multipath information types are distinct from each other.
Upon receiving the first "echo response," the initiator node (that performs LSP connectivity tests) updates its stored state to indicate that entropy label load balancing IS being used. The node then generates a second "echo request" containing a different multipath information type (specific for entropy labels). This second request is sent to the next transit node. The request message formats are distinct.
10. The initiator node of claim 9 wherein the method further comprises copying multipath information from the first echo response to the second echo request before the initiator node transmits the second echo request.
As part of the LSP connectivity testing procedure, the initiator node copies the multipath information received in the first "echo response" message into the subsequent second "echo request" message, before sending it. This ensures that learned information from the first hop is carried forward in the subsequent test.
11. The initiator node of claim 10 wherein the method further comprises copying associated label information from the first echo response to the second echo request before the initiator node transmits the second echo request.
During LSP connectivity tests, the initiator node copies associated label information from the initial "echo response" and includes it in the subsequent "echo request", before transmission. This allows the second transit node to also be aware of the label scheme.
12. The initiator node of claim 11 wherein the first echo reply comprises downstream mapping information and a set of entropy labels.
The first "echo reply" message, that is part of the LSP connectivity test, contains both downstream mapping information and a set of entropy labels. This provides the initiator with details about the path's forwarding behavior and load balancing.
13. A non-transitory computer readable medium storing program instructions that, when executed on a processor of a network node, are configured to cause the processor to: access state information stored in memory and determine whether the state information indicates that a label switched path (LSP) comprises an LSP segment that implements entropy label load balancing; in response to determining that the state information indicates that the LSP does not comprise an LSP segment that implements entropy label load balancing, generating a first echo request message that comprises a first multipath information type; transmit the first echo request message to a first transit node of the LSP.
A non-transitory computer-readable medium stores program instructions for a network node's processor, enabling LSP connectivity tests. The instructions cause the processor to first check a stored state to determine if entropy label load balancing is in use on the LSP. If not, the processor generates a first "echo request" message with a basic multipath type, then transmits this request to the first transit node.
14. The non-transitory computer readable medium of claim 13 , wherein the program instructions are further configured to cause the processor to initialize the state information to indicate the LSP does not comprise an LSP segment that implements entropy load balancing.
The non-transitory computer-readable medium (described in the previous claim) contains further program instructions that cause the processor to initialize the stored state variable to indicate that entropy label load balancing is NOT currently being used on the LSP. This sets the initial state for the LSP connectivity test.
15. The non-transitory computer readable medium of claim 14 , wherein the program instructions are further configured to cause the processor to: update the state information to indicate that the LSP comprises an LSP segment that implements entropy label load balancing in response to the network node receiving a first echo response from the first transit node; in response to updating the state information, generate a second echo request message that comprises a second multipath information type; transmit the second echo request message to a second transit node of the LSP; wherein the first and second multipath information types are distinct from each other.
The non-transitory computer-readable medium contains instructions for the processor to update the stored state, after receiving the first "echo response," to indicate that entropy label load balancing IS being used. The processor then generates a second "echo request" with a different (entropy-label-specific) multipath information type and sends it to the next transit node. The first and second request message formats are different.
Unknown
November 28, 2017
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.