Legal claims defining the scope of protection. Each claim is shown in both the original legal language and a plain English translation.
1. A Multiprotocol Label Switching traffic engineering (MPLS TE) tunnel establishing method, comprising: receiving, by a second routing device, a first Border Gateway Protocol (BGP) update message sent by a first routing device, wherein the first BGP update message comprises a first virtual private network (VPN) instance identifier, the first VPN instance identifier is used to identify a first VPN instance on the first routing device; sending, by the second routing device, a second BGP update message to the first routing device, wherein the second BGP update message comprises a second VPN instance identifier, wherein the second VPN instance identifier is used to identify a second VPN instance on the second routing device; receiving, by the second routing device, a third BGP update message sent by the first routing device, wherein the third BGP update message comprises a first identifier, and the first identifier is an identifier of a first MPLS TE tunnel, and the first MPLS TE tunnel is an MPLS TE tunnel from the first VPN instance to the second VPN instance; acquiring, by the second routing device, first path information according to the first identifier, wherein the first path information is path information of the first MPLS TE tunnel; and reversing, by the second routing device, the first path information to acquire second path information, and establishing a second MPLS TE tunnel according to the second path information, wherein the second MPLS TE tunnel is an MPLS TE tunnel from the second VPN instance to the first VPN instance.
This invention relates to a method for establishing Multiprotocol Label Switching Traffic Engineering (MPLS TE) tunnels in a network with Virtual Private Network (VPN) instances. The method addresses the challenge of efficiently setting up bidirectional MPLS TE tunnels between VPN instances on different routing devices, reducing manual configuration and ensuring consistent path establishment. The method involves a first routing device and a second routing device exchanging Border Gateway Protocol (BGP) update messages to establish VPN instance identifiers. The first routing device sends a BGP update message containing a first VPN instance identifier to the second routing device, which responds with a BGP update message containing its own VPN instance identifier. The first routing device then sends another BGP update message with an identifier for a first MPLS TE tunnel, which is a unidirectional tunnel from the first VPN instance to the second VPN instance. The second routing device receives this message, retrieves the path information of the first MPLS TE tunnel, reverses the path, and uses the reversed path to establish a second MPLS TE tunnel from the second VPN instance back to the first VPN instance. This automates the creation of bidirectional MPLS TE tunnels, ensuring symmetry and reducing configuration overhead. The method leverages BGP signaling to dynamically establish and manage MPLS TE tunnels between VPN instances, improving network efficiency and reliability.
2. The MPLS TE tunnel establishing method according to claim 1 , wherein the first BGP update message further comprises a first import route target (RT), and the first import RT is an import RT of the first VPN instance, wherein the second BGP update message further comprises a second import RT, wherein the second import RT is an import RT of the second VPN instance, before the sending the second BGP update message to the first routing device, the method further comprises: determining, by the second routing device, a service peer relationship between the first VPN instance and the second VPN instance according to the first import RT and a second export RT, wherein the second export RT is an export RT of the second VPN instance.
This invention relates to Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnel establishment in Virtual Private Network (VPN) environments. The problem addressed is the need to efficiently establish MPLS TE tunnels between VPN instances while ensuring proper service peer relationships are maintained. The method involves two routing devices exchanging Border Gateway Protocol (BGP) update messages to establish an MPLS TE tunnel. The first routing device sends a BGP update message containing a first import Route Target (RT), which identifies the first VPN instance. The second routing device receives this message and sends a second BGP update message containing a second import RT, which identifies the second VPN instance. Before sending the second update, the second routing device determines the service peer relationship between the VPN instances by comparing the first import RT with the second export RT, which is the export RT of the second VPN instance. This ensures that the VPN instances are properly configured to exchange traffic over the established MPLS TE tunnel. The method enables dynamic and scalable MPLS TE tunnel establishment while maintaining VPN service isolation and proper routing policies.
3. The MPLS TE tunnel establishing method according to claim 1 , wherein the third BGP update message further comprises: the first VPN instance identifier, a first export RT, and the second VPN instance identifier.
This invention relates to Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnel establishment in a network environment involving Virtual Private Networks (VPNs). The problem addressed is the efficient and accurate setup of MPLS TE tunnels between VPN instances, particularly when these instances are managed by different autonomous systems or require specific routing policies. The method involves exchanging Border Gateway Protocol (BGP) update messages to establish MPLS TE tunnels. A third BGP update message is used to convey additional information necessary for tunnel establishment. This message includes a first VPN instance identifier, a first export Route Target (RT), and a second VPN instance identifier. The first VPN instance identifier specifies the source VPN instance, while the second VPN instance identifier specifies the destination VPN instance. The first export RT defines the routing policy for traffic exiting the first VPN instance. This information enables precise routing and policy enforcement for traffic traversing the MPLS TE tunnel between the VPN instances. The method ensures that the tunnel is established with the correct routing policies and VPN context, facilitating seamless and secure communication between the VPNs.
4. The MPLS TE tunnel establishing method according to claim 1 , wherein after the receiving, by the second routing device, the first BGP update message sent by the first routing device, the method further comprises: parsing the first BGP update message, acquiring the first import RT from attribute information in the first BGP update message, and acquiring the first VPN instance identifier from a network layer reachability information (NLRI) object in the first BGP update message; or, parsing the first BGP update message, and acquiring the first VPN instance identifier and the first import RT from an NLRI object in the first BGP update message.
In the domain of Multi-Protocol Label Switching Traffic Engineering (MPLS TE), this invention addresses the challenge of efficiently establishing MPLS TE tunnels in a network environment where routing devices exchange information via Border Gateway Protocol (BGP) update messages. The method involves a second routing device receiving a first BGP update message from a first routing device. The second routing device parses the BGP update message to extract key information necessary for tunnel establishment. Specifically, the second routing device acquires a first import Route Target (RT) from the attribute information within the BGP update message and retrieves a first VPN instance identifier from the Network Layer Reachability Information (NLRI) object. Alternatively, the second routing device may acquire both the first import RT and the first VPN instance identifier directly from the NLRI object. This parsing and extraction process enables the second routing device to accurately identify the appropriate VPN instance and import RT, facilitating the establishment of an MPLS TE tunnel with the correct routing parameters. The method ensures that the tunnel is configured with the necessary attributes to support traffic engineering requirements, such as bandwidth allocation and path selection, within the specified VPN context. By automating the extraction of these critical parameters from BGP update messages, the invention streamlines the tunnel establishment process and reduces the risk of misconfiguration.
5. The MPLS TE tunnel establishing method according to claim 1 , wherein attribute information in the second BGP update message comprises a second import route target (RT), and an NLRI object in the second BGP update message comprises the second VPN instance identifier; or wherein an NLRI object in the second BGP update message comprises the second import RT and the second VPN instance identifier.
This invention relates to establishing MPLS Traffic Engineering (TE) tunnels in a network, particularly for Virtual Private Network (VPN) services. The problem addressed is efficiently configuring and managing MPLS TE tunnels in a multi-VPN environment where tunnels must be associated with specific VPN instances while ensuring proper route targeting. The method involves using Border Gateway Protocol (BGP) update messages to establish MPLS TE tunnels. A first BGP update message is sent to advertise a first VPN instance identifier and a first import route target (RT). A second BGP update message is then sent to establish the MPLS TE tunnel, where the tunnel is associated with a second VPN instance. The second BGP update message includes attribute information containing a second import RT or an NLRI object containing the second import RT and the second VPN instance identifier. This ensures the tunnel is correctly linked to the intended VPN instance and route targets, enabling proper traffic forwarding and policy enforcement. The solution simplifies tunnel configuration by leveraging BGP for dynamic tunnel establishment and association with VPN instances, reducing manual configuration and improving scalability in large networks. The use of RTs and VPN instance identifiers in BGP messages ensures accurate tunnel-to-VPN mapping, preventing misrouting and enhancing network reliability.
6. The MPLS TE tunnel establishing method according to claim 1 , wherein: the first VPN instance identifier comprises a first route distinguisher (RD) and a first Internet Protocol (IP) address, wherein the first RD is an RD of the first VPN instance, and the first IP address is an IP address of the first routing device; and the second VPN instance identifier comprises a second RD and a second IP address, wherein the second RD is an RD of the second VPN instance, and the second IP address is an IP address of the second routing device.
In the domain of Multi-Protocol Label Switching Traffic Engineering (MPLS TE), establishing tunnels between Virtual Private Network (VPN) instances across different routing devices presents challenges in ensuring proper identification and routing. The invention addresses this by defining a method for establishing an MPLS TE tunnel between a first VPN instance and a second VPN instance, where each VPN instance is associated with a unique identifier. The first VPN instance identifier includes a first Route Distinguisher (RD) and a first Internet Protocol (IP) address. The first RD is the RD of the first VPN instance, and the first IP address is the IP address of the first routing device associated with that VPN instance. Similarly, the second VPN instance identifier includes a second RD and a second IP address, where the second RD is the RD of the second VPN instance, and the second IP address is the IP address of the second routing device. This method ensures that the MPLS TE tunnel can be correctly established and managed by uniquely identifying the VPN instances and their associated routing devices, facilitating accurate routing and traffic engineering across the network. The use of RDs and IP addresses in the identifiers prevents conflicts and ensures proper tunnel establishment in complex VPN environments.
7. The MPLS TE tunnel establishing method according to claim 1 , wherein the acquiring, by the second routing device, the first path information according to the first identifier comprises: determining, by the second routing device according to the first identifier and a first correspondence, the first MPLS TE tunnel identified by the first identifier, wherein the first correspondence is a correspondence between the first identifier and the first MPLS TE tunnel; and querying, by the second routing device, a second correspondence according to the identifier of the first MPLS TE tunnel, to acquire the first path information, wherein the second correspondence is a correspondence between the identifier of the first MPLS TE tunnel and the first path information.
This invention relates to Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnel establishment in network routing systems. The problem addressed is efficiently acquiring path information for MPLS TE tunnels, particularly when a second routing device needs to establish a tunnel based on an identifier received from a first routing device. The method involves a second routing device receiving a first identifier from a first routing device, where the identifier corresponds to a first MPLS TE tunnel. The second routing device uses a first correspondence—a mapping between the first identifier and the first MPLS TE tunnel—to determine the specific tunnel identified by the identifier. Once the tunnel is identified, the second routing device queries a second correspondence—a mapping between the tunnel's identifier and its path information—to retrieve the necessary path details. This allows the second routing device to establish the MPLS TE tunnel accurately and efficiently by leveraging pre-existing correspondences rather than recalculating path information. The solution improves tunnel establishment by reducing computational overhead and ensuring consistency in path information retrieval, which is critical for maintaining reliable and optimized network traffic routing. The method is particularly useful in scenarios where multiple routing devices need to synchronize tunnel configurations dynamically.
8. The MPLS TE tunnel establishing method according to claim 1 , wherein the acquiring, by the second routing device, the first path information according to the first identifier comprises: querying, by the second routing device, a correspondence between the first identifier and the first path information according to the first identifier, to acquire the first path information, wherein the correspondence between the first identifier and the first path information is acquired by the second routing device from a received path message that is used to establish the first MPLS TE tunnel.
This invention relates to establishing Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnels in a network. The problem addressed is efficiently acquiring path information for establishing MPLS TE tunnels between routing devices, particularly when the path information is not locally available. The method involves a second routing device receiving a first identifier associated with a first MPLS TE tunnel. To establish the tunnel, the second routing device queries a stored correspondence between the first identifier and first path information. This correspondence was previously obtained from a path message used to establish the first MPLS TE tunnel. The path message contains the necessary routing information, such as labels and next-hop addresses, required to forward traffic through the tunnel. By querying this stored correspondence, the second routing device can quickly retrieve the path information without needing to re-compute or request it, improving tunnel establishment efficiency. The method ensures that the second routing device can dynamically acquire path information for MPLS TE tunnels by leveraging pre-existing path messages, reducing latency and resource overhead in network operations. This approach is particularly useful in large-scale networks where multiple tunnels need to be established and maintained efficiently.
9. The MPLS TE tunnel establishing method according to claim 1 , wherein the establishing, by the second routing device, the second MPLS TE tunnel according to the second path information comprises: directly using, by the second routing device, the second path information to establish the second MPLS TE tunnel; or, determining, by the second routing device, whether a link or a node or at least one of a link and a node in the second path information meets a constraint of first tunnel attribute information, and if the second routing device determines that the link and/or the node or the at least one of the link and the node in the second path information meets the constraint of the first tunnel attribute information, using the second path information to establish the second MPLS TE tunnel, wherein the first tunnel attribute information is attribute information that is required for establishing the first MPLS TE tunnel by the first routing device, or, the first tunnel attribute information is attribute information that is preconfigured by the second routing device and required for establishing the second MPLS TE tunnel, or, the first tunnel attribute information is default attribute information that is required for establishing the second MPLS TE tunnel by the second routing device.
This invention relates to methods for establishing Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnels in a network. The problem addressed is the efficient and flexible establishment of MPLS TE tunnels between routing devices, ensuring that the tunnels meet specific constraints such as link or node attributes. The method involves a first routing device establishing a first MPLS TE tunnel based on first path information, which may include a path calculation or a preconfigured path. A second routing device then establishes a second MPLS TE tunnel using second path information. The second routing device can either directly use the second path information to establish the tunnel or verify whether the links or nodes in the second path meet the constraints defined by first tunnel attribute information. If the constraints are satisfied, the second MPLS TE tunnel is established accordingly. The first tunnel attribute information can be derived from the first tunnel's requirements, preconfigured by the second routing device, or based on default settings for the second tunnel. This approach ensures that the second tunnel adheres to necessary constraints while allowing flexibility in path selection.
10. The MPLS TE tunnel establishing method according to claim 9 , wherein before the establishing, by the second routing device, a second MPLS TE tunnel according to the second path information, the method further comprises: receiving, by the second routing device, tunnel establishing policy instruction information sent by the first routing device, wherein the tunnel establishing policy instruction information is used to instruct, when the at least one of the link and the node in the second path information meets the constraint of the first tunnel attribute information, the second routing device to use the second path information to establish the second MPLS TE tunnel.
This invention relates to Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnel establishment in network routing. The problem addressed is the need for efficient and policy-driven establishment of MPLS TE tunnels between routing devices, ensuring compliance with specified tunnel attributes and path constraints. The method involves a first routing device sending tunnel attribute information and second path information to a second routing device. The tunnel attribute information defines constraints for the tunnel, such as bandwidth, priority, or other quality-of-service parameters. The second path information specifies a path for establishing a second MPLS TE tunnel. Before establishing the tunnel, the second routing device receives tunnel establishing policy instruction information from the first routing device. This instruction directs the second routing device to use the second path information to establish the second MPLS TE tunnel only if the links or nodes in the specified path meet the constraints defined by the tunnel attribute information. This ensures that the tunnel is established in accordance with predefined policies and requirements, optimizing network performance and resource utilization. The method enhances flexibility and control in MPLS TE tunnel management by dynamically verifying path compliance before establishment.
11. The MPLS TE tunnel establishing method according to claim 9 , wherein preconfiguring, for the second routing device, the attribute information that is required for establishing the second MPLS TE tunnel comprises: preconfiguring, for the second routing device, a tunnel template that is used to establish the second MPLS TE tunnel, and using the tunnel template to configure, for the second routing device, the attribute information that is required for establishing the second MPLS TE tunnel; and wherein the attribute information that is required for establishing the second MPLS TE tunnel is the first tunnel attribute information.
In the domain of Multi-Protocol Label Switching Traffic Engineering (MPLS TE), establishing tunnels between routing devices requires precise configuration of attribute information to ensure proper traffic routing and quality of service. A challenge arises when dynamically configuring tunnels, particularly when a second routing device needs to establish a tunnel based on preconfigured settings from a first routing device. This invention addresses the need for efficient tunnel establishment by leveraging preconfigured tunnel templates. The method involves preconfiguring a tunnel template on a second routing device, which is then used to establish a second MPLS TE tunnel. The tunnel template contains attribute information necessary for tunnel establishment, such as bandwidth, priority, and path constraints. This preconfiguration ensures that the second routing device can quickly and accurately set up the tunnel without manual intervention. The attribute information used for the second tunnel is derived from the first tunnel's attribute information, ensuring consistency and reducing configuration errors. By using a template, the method simplifies the setup process, improves scalability, and enhances reliability in dynamic network environments. This approach is particularly useful in scenarios where multiple tunnels need to be established with similar attributes, reducing administrative overhead and improving network efficiency.
12. The MPLS TE tunnel establishing method according to claim 1 , wherein the first MPLS TE tunnel comprises a primary label switched path (LSP) and a backup LSP; the acquiring, by the second routing device, first path information according to the first identifier comprises: acquiring, by the second routing device according to role information of LSPs in the first MPLS TE tunnel, first primary path information corresponding to the primary LSP in the first MPLS TE tunnel and first backup path information corresponding to the backup LSP in the first MPLS TE tunnel; and the reversing, by the second routing device, the first path information to acquire second path information, and establishing a second MPLS TE tunnel according to the second path information comprises: reversing, by the second routing device, the first primary path information to acquire second primary path information corresponding to the primary LSP in the first MPLS TE tunnel; and reversing, by the second routing device, the first backup path information, to acquire second backup path information corresponding to the backup LSP in the first MPLS TE tunnel; establishing, by the second routing device, a primary LSP in the second MPLS TE tunnel according to the second primary path information; and establishing, by the second routing device, a backup LSP in the second MPLS TE tunnel according to the second backup path information.
This invention relates to Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnel establishment, specifically for creating a backup tunnel by reversing the path of an existing primary MPLS TE tunnel. The problem addressed is the need for efficient and reliable backup path establishment in MPLS networks to ensure continuous data flow in case of primary path failure. The method involves a first MPLS TE tunnel that includes both a primary Label Switched Path (LSP) and a backup LSP. A second routing device acquires path information for the first tunnel by identifying the roles of the LSPs within it. The device then retrieves the primary path information for the primary LSP and the backup path information for the backup LSP. The second routing device reverses this path information to generate new primary and backup path information for a second MPLS TE tunnel. The reversed primary path information is used to establish a primary LSP in the second tunnel, while the reversed backup path information is used to establish a backup LSP in the second tunnel. This ensures that the second tunnel is established with the same redundancy as the first, but with the roles of the paths reversed, providing an alternative route in case of primary path failure. The technique enhances network resilience by dynamically creating backup tunnels based on existing primary tunnels.
13. The MPLS TE tunnel establishing method according to claim 1 , further comprising: sending, by the second routing device, a fifth BGP update message to the first routing device, wherein the fifth BGP update message comprises the first VPN instance identifier, the second VPN instance identifier, the second import RT, and a second identifier, and the second identifier is an identifier of the second MPLS TE tunnel.
This invention relates to Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnel establishment in a network with Virtual Private Network (VPN) instances. The problem addressed is the need for efficient and accurate establishment of MPLS TE tunnels between routing devices in a network where multiple VPN instances are present, ensuring proper routing and traffic engineering across different VPN domains. The method involves a first routing device and a second routing device, each associated with different VPN instances. The first routing device sends a first Border Gateway Protocol (BGP) update message to the second routing device, containing a first VPN instance identifier, a second VPN instance identifier, and a first import Route Target (RT). The second routing device then establishes a first MPLS TE tunnel between the two devices based on this information. Additionally, the second routing device sends a second BGP update message to the first routing device, which includes the first VPN instance identifier, the second VPN instance identifier, and a second import RT. The first routing device then establishes a second MPLS TE tunnel based on this update. To further enhance the tunnel establishment process, the second routing device sends a fifth BGP update message to the first routing device. This message includes the first VPN instance identifier, the second VPN instance identifier, the second import RT, and a second identifier, which is an identifier of the second MPLS TE tunnel. This ensures that the tunnels are properly identified and managed within the VPN instances, facilitating accurate traffic engineering and routing across the network. The method ensures that MPLS TE tunnels are correctly established and maintained between routing devices in a mult
14. A second routing device, comprising computer executable instructions stored on a non-transitory computer-readable medium, wherein execution of the by a processor causes the processor to: receive a first Border Gateway Protocol (BGP) update message sent by a first routing device, wherein the first BGP update message comprises a first virtual private network (VPN) instance identifier, the first VPN instance identifier is used to identify a first VPN instance on the first routing device; send a second BGP update message to the first routing device, wherein the second BGP update message comprises a second VPN instance identifier, wherein the second VPN instance identifier is used to identify a second VPN instance on the second routing device; receive a third BGP update message sent by the first routing device, wherein the third BGP update message comprises a first identifier, and the first identifier is an identifier of a first Multiprotocol Label Switching traffic engineering (MPLS TE) tunnel, and the first MPLS TE tunnel is an MPLS TE tunnel from the first VPN instance to the second VPN instance; acquire first path information according to the first identifier, wherein the first path information is path information of the first MPLS TE tunnel; and reverse the first path information to acquire second path information, and establish a second MPLS TE tunnel according to the second path information, wherein the second MPLS TE tunnel is an MPLS TE tunnel from the second VPN instance to the first VPN instance.
This invention relates to network routing, specifically to establishing bidirectional Multiprotocol Label Switching Traffic Engineering (MPLS TE) tunnels between Virtual Private Network (VPN) instances on different routing devices. The problem addressed is the need for efficient bidirectional tunnel establishment in VPN environments, where manual configuration or complex signaling can be cumbersome. The system involves two routing devices exchanging Border Gateway Protocol (BGP) update messages to dynamically establish MPLS TE tunnels. The first routing device sends a BGP update message containing a VPN instance identifier for its local VPN instance. The second routing device responds with its own VPN instance identifier. The first routing device then sends another BGP update message containing an identifier for an MPLS TE tunnel from its VPN instance to the second device's VPN instance. The second routing device receives this identifier, retrieves the path information of the tunnel, reverses the path to determine the return path, and establishes a corresponding MPLS TE tunnel from its VPN instance back to the first device's VPN instance. This automated process ensures bidirectional connectivity without manual intervention, improving network efficiency and scalability.
15. The second routing device according to claim 14 , wherein wherein the first BGP update message further comprises a first import route target (RT), and the first import RT is an import RT of the first VPN instance, wherein the second BGP update message further comprises a second import RT, wherein the second import RT is an import RT of the second VPN instance, the instructions when executed by the processor further cause the processor to: determine a service peer relationship between the first VPN instance and the second VPN instance according to the first import RT and a second export RT, wherein the second export RT is an export RT of the second VPN instance.
This invention relates to virtual private network (VPN) routing in network systems, specifically addressing the challenge of dynamically establishing service peer relationships between VPN instances using Border Gateway Protocol (BGP) update messages. The system involves a second routing device that processes BGP update messages to facilitate communication between VPN instances. The first BGP update message includes a first import route target (RT), which is the import RT of a first VPN instance. Similarly, the second BGP update message includes a second import RT, which is the import RT of a second VPN instance. The routing device determines a service peer relationship between the first and second VPN instances by comparing the first import RT with a second export RT, where the second export RT is the export RT of the second VPN instance. This mechanism allows the routing device to dynamically establish and manage VPN instance relationships based on BGP update messages, ensuring proper routing and service connectivity between VPNs. The solution enhances scalability and flexibility in VPN deployments by automating peer relationship determination without manual configuration.
16. The second routing device according to claim 14 , wherein the third BGP update message further comprises: the first VPN instance identifier, a first import route target (RT), and the second VPN instance identifier.
A system for managing virtual private network (VPN) routing in a network environment involves multiple routing devices exchanging Border Gateway Protocol (BGP) update messages to establish and maintain VPN connections. The system addresses the challenge of efficiently distributing VPN routing information across a network while ensuring proper isolation and connectivity between different VPN instances. The system includes a first routing device that generates a BGP update message containing a VPN instance identifier, a route target (RT), and routing information for a specific VPN instance. This update message is sent to a second routing device, which processes the message to establish or update routing paths for the VPN instance. The second routing device may also generate a second BGP update message to propagate the routing information to other devices in the network. In some configurations, the second routing device generates a third BGP update message that includes a first VPN instance identifier, a first import route target (RT), and a second VPN instance identifier. This allows the second routing device to associate routing information between different VPN instances, enabling inter-VPN communication while maintaining proper isolation. The import RT specifies which VPN instances are permitted to receive the routing information, ensuring secure and controlled distribution. The system ensures that routing information is accurately propagated and that VPN instances are correctly isolated or interconnected based on configured policies.
17. The second routing device according to claim 14 , wherein the instructions when executed by the processor further cause the processor to: parse the first BGP update message, acquire the first import RT from attribute information in the first BGP update message, and acquire the first VPN instance identifier from a network layer reachability information (NLRI) object in the first BGP update message; or receive the first BGP update message, parse the first BGP update message, and acquire the first VPN instance identifier and the first import RT from an NLRI object in the first BGP update message.
This invention relates to routing devices in a network, specifically for handling Border Gateway Protocol (BGP) update messages in a Virtual Private Network (VPN) environment. The problem addressed is the efficient parsing and processing of BGP update messages to extract routing information, particularly the import Route Target (RT) and VPN instance identifiers, which are critical for VPN routing and forwarding. The invention describes a second routing device that processes BGP update messages to manage VPN routing. The device includes a processor and memory storing instructions that, when executed, cause the processor to parse a first BGP update message. The parsing involves acquiring a first import RT from attribute information in the message and acquiring a first VPN instance identifier from a Network Layer Reachability Information (NLRI) object. Alternatively, the device may receive, parse, and acquire both the first VPN instance identifier and the first import RT directly from the NLRI object in the BGP update message. This dual approach ensures flexibility in handling different BGP message formats while accurately extracting the necessary routing information for VPN operations. The extracted data is used to update routing tables and ensure proper VPN traffic forwarding. The invention improves the efficiency and accuracy of VPN route processing in network environments.
18. The second routing device according to claim 14 , wherein attribute information in the second BGP update message comprises the second import RT, and an NLRI object in the second BGP update message comprises the second VPN instance identifier; or wherein an NLRI object in the second BGP update message comprises the second import RT and the second VPN instance identifier.
This invention relates to network routing, specifically improving the handling of Border Gateway Protocol (BGP) update messages in a network with multiple Virtual Private Network (VPN) instances. The problem addressed is the efficient distribution of routing information between different VPN instances while ensuring proper access control and isolation. The invention involves a second routing device that processes BGP update messages to facilitate communication between VPN instances. The second routing device receives a BGP update message containing attribute information and a Network Layer Reachability Information (NLRI) object. The attribute information may include a second import Route Target (RT), which is used to control the import of routes into a VPN instance. The NLRI object may contain a second VPN instance identifier, which uniquely identifies the VPN instance, or both the second import RT and the second VPN instance identifier. This allows the routing device to correctly associate the routing information with the appropriate VPN instance and enforce access policies based on the import RT. By encoding the import RT and VPN instance identifier in either the attribute information or the NLRI object, the invention ensures that routing information is properly distributed and filtered according to the intended VPN instance, improving network security and efficiency. This method supports flexible routing configurations while maintaining isolation between different VPN instances.
19. The second routing device according to claim 14 , wherein: the first VPN instance identifier comprises a first route distinguisher (RD) and a first Internet Protocol (IP) address, wherein the first RD is an RD of the first VPN instance, and the first IP address is an IP address of the first routing device; and the second VPN instance identifier comprises a second RD and a second IP address, wherein the second RD is an RD of the second VPN instance, and the second IP address is an IP address of the second routing device.
In the domain of virtual private network (VPN) routing, a technical challenge arises in uniquely identifying VPN instances and routing devices within a network to ensure proper traffic forwarding. This invention addresses the problem by defining a method for generating and using VPN instance identifiers that combine route distinguishers (RDs) and Internet Protocol (IP) addresses to uniquely identify VPN instances and associated routing devices. The invention involves a second routing device that processes VPN instance identifiers. Each identifier includes a route distinguisher (RD) and an IP address. The first VPN instance identifier contains an RD specific to the first VPN instance and an IP address of the first routing device. Similarly, the second VPN instance identifier contains an RD specific to the second VPN instance and an IP address of the second routing device. This structure ensures that VPN instances and their associated routing devices are uniquely identifiable, preventing routing conflicts and enabling accurate traffic forwarding within the network. The solution enhances scalability and reliability in VPN-based networks by providing clear, unambiguous identifiers for routing purposes.
20. The second routing device according to claim 14 , wherein the instructions when executed by the processor further cause the processor to: determine, according to the first identifier and a first correspondence, the first MPLS TE tunnel identified by the first identifier, and query a second correspondence according to the identifier of the first MPLS TE tunnel, to acquire the first path information, wherein the first correspondence is a correspondence between the first identifier and the first MPLS TE tunnel, and the second correspondence is a correspondence between the identifier of the first MPLS TE tunnel and the first path information.
A system and method for managing Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnels in a network involves a second routing device that processes traffic based on identifiers and stored correspondences. The device receives a first identifier associated with a data packet and uses it to determine the corresponding first MPLS TE tunnel by referencing a first correspondence table that maps the first identifier to the tunnel. Once the tunnel is identified, the device queries a second correspondence table using the tunnel's identifier to retrieve the first path information, which defines the route for forwarding the packet. The first correspondence table establishes a relationship between the first identifier and the MPLS TE tunnel, while the second correspondence table links the tunnel's identifier to the path information. This approach enables efficient packet forwarding by leveraging preconfigured mappings, reducing the need for real-time path calculations and improving network performance. The system is particularly useful in large-scale networks where dynamic path determination can introduce latency and complexity.
21. The second routing device according to claim 14 , wherein the instructions when executed by the processor further cause the processor to: query a correspondence between the first identifier and the first path information according to the first identifier, to acquire the first path information, wherein the correspondence between the first identifier and the first path information is acquired by the second routing device from a received path message that is used to establish the first MPLS TE tunnel.
In the field of network routing, particularly in Multiprotocol Label Switching Traffic Engineering (MPLS TE), a challenge exists in efficiently managing and querying path information for established tunnels. This invention addresses the need for a second routing device to dynamically retrieve path information associated with a first MPLS TE tunnel using a first identifier. The second routing device includes a processor and instructions that, when executed, enable the device to query a stored correspondence between the first identifier and first path information. This correspondence is derived from a received path message used to establish the first MPLS TE tunnel. The first path information may include details such as the tunnel's route, constraints, or other relevant parameters. By querying this correspondence, the second routing device can quickly access the necessary path information without requiring additional signaling or manual configuration, improving network efficiency and reducing operational overhead. The solution leverages existing MPLS TE signaling mechanisms to maintain an up-to-date mapping between identifiers and path data, ensuring accurate and timely retrieval of tunnel information for routing decisions or network management tasks.
22. The second routing device according to claim 14 , wherein the instructions when executed by the processor further cause the processor to: determine whether at least one of a link and a node in the second path information meets a constraint of first tunnel attribute information, and after determining that the at least one of the link and the node in the second path information meets the constraint of the first tunnel attribute information, use the second path information to establish the second MPLS TE tunnel, wherein the first tunnel attribute information is attribute information that is required for establishing the first MPLS TE tunnel by the first routing device, or, the first tunnel attribute information is attribute information that is preconfigured by the second routing device and required for establishing the second MPLS TE tunnel, or, the first tunnel attribute information is default attribute information that is required for establishing the second MPLS TE tunnel by the second routing device.
This invention relates to Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnel establishment in a network. The problem addressed is ensuring that a second MPLS TE tunnel meets specific attribute constraints when established by a second routing device, either based on requirements from a first routing device or predefined settings. The second routing device receives path information for the second MPLS TE tunnel and checks whether the links or nodes in the proposed path satisfy certain constraints defined by first tunnel attribute information. This attribute information can be derived from the first routing device's requirements for establishing its own tunnel, preconfigured settings on the second routing device, or default values required for the second tunnel. If the path meets these constraints, the second routing device proceeds to establish the second MPLS TE tunnel using the validated path information. This ensures compatibility and proper resource allocation in the network. The solution enhances reliability and efficiency in MPLS TE tunnel establishment by enforcing attribute-based path validation.
23. The second routing device according to claim 22 , wherein the instructions when executed by the processor further cause the processor to: receive tunnel establishing policy instruction information sent by the first routing device, wherein the tunnel establishing policy instruction information is used to instruct, when the at least one of the link and the node in the second path information meets the constraint of the first tunnel attribute information, the second routing device to use the second path information to establish the second MPLS TE tunnel.
This invention relates to network routing, specifically to establishing Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnels between routing devices. The problem addressed is efficiently setting up MPLS TE tunnels while ensuring they meet specific path constraints, such as avoiding certain links or nodes. The invention involves a second routing device that receives tunnel establishment policy instructions from a first routing device. These instructions include first tunnel attribute information, which defines constraints for the tunnel, such as required bandwidth, path diversity, or exclusion of specific network elements. The second routing device also receives second path information, which describes an alternative route for the tunnel. When the second routing device determines that the second path information meets the constraints specified in the first tunnel attribute information, it uses this path to establish a second MPLS TE tunnel. This ensures that the tunnel adheres to the required network policies while providing flexibility in path selection. The invention improves network reliability and efficiency by dynamically adjusting tunnel paths based on real-time constraints, reducing manual configuration and optimizing traffic flow. This is particularly useful in large-scale networks where multiple tunnels must be managed while adhering to strict performance and security requirements.
24. The second routing device according to claim 22 , wherein the instructions when executed by the processor further cause the processor to use a preconfigured tunnel template that is used to establish the second MPLS TE tunnel, to configure the attribute information that is required for establishing the second MPLS TE tunnel; and wherein the attribute information that is required for establishing the second MPLS TE tunnel is the first tunnel attribute information.
This invention relates to network routing, specifically to the establishment of Multi-Protocol Label Switching Traffic Engineering (MPLS TE) tunnels in a network with multiple routing devices. The problem addressed is the efficient and consistent configuration of tunnel attributes when setting up MPLS TE tunnels between routing devices, ensuring proper traffic engineering and network performance. The invention involves a second routing device in a network that uses a preconfigured tunnel template to establish a second MPLS TE tunnel. The tunnel template contains predefined attribute information necessary for configuring the tunnel, such as bandwidth, path constraints, and other traffic engineering parameters. When establishing the second MPLS TE tunnel, the routing device uses this template to apply the required attribute information, which is derived from a first tunnel attribute set. This approach ensures that the tunnel is configured with consistent and optimized parameters, reducing manual configuration errors and improving network reliability. The preconfigured tunnel template simplifies the setup process by standardizing the attribute configuration across multiple tunnels, allowing for scalable and efficient network management. This method is particularly useful in large-scale networks where multiple MPLS TE tunnels need to be established with similar characteristics. The use of a template ensures that all tunnels adhere to predefined policies and performance requirements, enhancing overall network efficiency and traffic management.
25. The second routing device according to claim 14 , wherein the first MPLS TE tunnel comprises a primary label switched path (LSP) and a backup LSP; wherein the instructions when executed by the processor further cause the processor to: acquire, according to role information of LSPs in the first MPLS TE tunnel, first primary path information corresponding to the primary LSP in the first MPLS TE tunnel and first backup path information corresponding to the backup LSP in the first MPLS TE tunnel; and reverse the first primary path information to acquire second primary path information corresponding to the primary LSP in the first MPLS TE tunnel; reverse the first backup path information to acquire second backup path information corresponding to the backup LSP in the first MPLS TE tunnel; establish a primary LSP in the second MPLS TE tunnel according to the second primary path information; and establish a backup LSP in the second MPLS TE tunnel according to the second backup path information.
In the domain of Multi-Protocol Label Switching Traffic Engineering (MPLS TE), a technical challenge exists in efficiently managing and establishing redundant label switched paths (LSPs) to ensure reliable data transmission. A routing device is configured to handle MPLS TE tunnels, where each tunnel includes a primary LSP and a backup LSP. The device acquires role information of the LSPs within the first MPLS TE tunnel, identifying the primary and backup paths. The device then reverses the first primary path information to generate second primary path information and reverses the first backup path information to generate second backup path information. Using these reversed path details, the device establishes a primary LSP and a backup LSP in a second MPLS TE tunnel. This approach ensures that the second tunnel mirrors the redundancy and path configuration of the first tunnel, enhancing fault tolerance and network reliability. The method automates the creation of backup paths, reducing manual configuration and improving network resilience.
26. The second routing device according to claim 14 , wherein the instructions when executed by the processor further cause the processor to send a fifth BGP update message to the first routing device, wherein the fifth BGP update message comprises the first VPN instance identifier, the second VPN instance identifier, the second export RT, and a second identifier, and the second identifier is an identifier of the second MPLS TE tunnel.
This invention relates to routing devices in a network, specifically for managing Border Gateway Protocol (BGP) updates in a Multi-Protocol Label Switching Traffic Engineering (MPLS TE) environment with Virtual Private Network (VPN) instances. The problem addressed is the efficient and accurate propagation of routing information between routing devices to establish and maintain MPLS TE tunnels across VPN instances. The invention involves a second routing device that receives a BGP update message from a first routing device, where the update includes a first VPN instance identifier, a second VPN instance identifier, an export Route Target (RT), and an identifier of a first MPLS TE tunnel. The second routing device processes this information to establish or update a routing table entry for the first MPLS TE tunnel. Additionally, the second routing device sends a subsequent BGP update message to the first routing device, which includes the first VPN instance identifier, the second VPN instance identifier, a second export RT, and an identifier of a second MPLS TE tunnel. This ensures bidirectional communication and proper routing between the VPN instances over the MPLS TE tunnels. The invention improves network efficiency by dynamically updating routing information and ensuring proper tunnel establishment between VPN instances, reducing manual configuration and potential routing errors. The use of BGP updates with VPN and MPLS TE identifiers allows for scalable and automated network management.
Unknown
October 1, 2019
Browse 5M+ US patents with plain-English claim translations and AI-generated analysis.