WO2024032636A1 - 实现SRV6 policy网络H-VPN分层管理的方法、装置及相关设备 - Google Patents

实现SRV6 policy网络H-VPN分层管理的方法、装置及相关设备 Download PDF

Info

Publication number
WO2024032636A1
WO2024032636A1 PCT/CN2023/111858 CN2023111858W WO2024032636A1 WO 2024032636 A1 WO2024032636 A1 WO 2024032636A1 CN 2023111858 W CN2023111858 W CN 2023111858W WO 2024032636 A1 WO2024032636 A1 WO 2024032636A1
Authority
WO
WIPO (PCT)
Prior art keywords
target
vpn
sid
srv6
service
Prior art date
Application number
PCT/CN2023/111858
Other languages
English (en)
French (fr)
Other versions
WO2024032636A9 (zh
Inventor
孙嘉琪
杨广铭
刘志华
严劲
姚文胜
Original Assignee
中国电信股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中国电信股份有限公司 filed Critical 中国电信股份有限公司
Publication of WO2024032636A1 publication Critical patent/WO2024032636A1/zh
Publication of WO2024032636A9 publication Critical patent/WO2024032636A9/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/58—Association of routers
    • H04L45/586—Association of routers of virtual routers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/64—Routing or path finding of packets in data switching networks using an overlay routing layer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming

Definitions

  • the present disclosure relates to the field of communication technology, and in particular, to a method, device, equipment, media and computer program product for realizing h-VPN hierarchical management of SRV6 policy network.
  • the inner service label is exchanged, and then the service label is superimposed on the outer tunnel and sent to the PE node.
  • VPN SIDs SRV6 service labels
  • the Layer 2 services of SRV6 services directly establish MP-BGP neighbors at the source and sink nodes, and the source and sink nodes directly publish the VPN SID to the opposite end. In this way, routing is not layered, and it is an end-to-end VPN service.
  • a method for implementing H-VPN hierarchical management of an SRV6 policy network is provided, applied to BGP of SPE equipment, and the method includes:
  • the service route carries the service label and color value
  • a target SRV6 policy is generated based on the color value and service label, including:
  • the query obtains the first SRV6 policy
  • the sidlist of the second SRV6 policy is the sidlist of the first SRV6 policy
  • the target SRV6 policy is obtained.
  • the last layer of the target SRV6 policy is a service label.
  • the business scenario includes at least one of the following scenarios:
  • IPV4 H-VPN scenario IPV6 H-VPN scenario, EVPN VPWS H-VPN scenario, EVPN VPLS H-VPN scenario.
  • the first SID type is selected when the business scenario to which the service route belongs is an IPV4 H-VPN scenario.
  • the second device when the first device is an NPE device, the second device is a UPE device; when the first device is a UPE device, the second device is an NPE device.
  • sending the target service route to the second device includes:
  • the update message also carries at least one of the following attributes:
  • the method further includes:
  • a device for implementing H-VPN hierarchical management of SRV6 policy network is provided, which is applied to BGP of SPE equipment.
  • the device includes a routing message receiving module, a judgment module, a first data processing module, a second Data processing module and data sending module.
  • the routing message receiving module is configured to receive the service route sent by the first device, and the service route carries the service label and color value;
  • the judgment module is configured to be based on the business scenario to which the service route belongs, in the preset SID type. Select the target SID type;
  • the first data processing module is configured to generate the target SRV6 policy based on the color value and service label;
  • the second data processing module is configured to associate the target SID type with the target SRV6 policy and generate a target service route.
  • the next hop of the SID corresponding to the target SID type in the target service route is the target SRV6 policy;
  • the data sending module is configured to send the target service route to the second device, so that the second device forwards the data according to the address table lookup in the target service route.
  • an electronic device including: a memory for storing instructions; a processor for calling instructions stored in the memory to implement the above-mentioned SRV6 policy network H-VPN hierarchical management Methods.
  • a computer-readable storage medium on which computer instructions are stored.
  • the above-mentioned method for implementing H-VPN hierarchical management of an SRV6 policy network is implemented.
  • a computer program product stores instructions.
  • the instructions When the instructions are executed by a computer, the computer implements the above-mentioned method for implementing SRV6 policy network H-VPN hierarchical management.
  • a chip including at least one processor and an interface
  • Interface used to provide program instructions or data to at least one processor
  • At least one processor is used to execute program instructions to implement the above-mentioned method of implementing H-VPN hierarchical management of an SRV6 policy network.
  • the methods, devices, equipment and media for implementing H-VPN hierarchical management of SRV6 policy network are based on the business scenario to which the service routing belongs.
  • the target SID type is selected from the preset SID types, and the target SID type is selected according to the color value and business label, generate the target SRV6 policy, and then associate the target SID type with the target SRV6 policy to generate the target service route.
  • the next hop of the SID corresponding to the target SID type in the target service route is the target SRV6 policy; send the target service route to the The second device, so that the second device looks up the table and forwards it according to the address in the target service route.
  • the SPE in this disclosed embodiment does not need to deploy a VPN instance, and can directly realize the exchange of VPN SIDs and realize H-VPN hierarchical management of EVPN L2/L3 services in the SRV6 policy network.
  • Figure 1 shows a schematic diagram of EVPN L3VPN HoVPN business architecture in related technologies
  • Figure 2 shows a flow chart of a method for implementing h-VPN hierarchical management of an SRV6 policy network in an embodiment of the present disclosure
  • Figure 3 shows a mapping diagram in which the next hop of END.BDT6.SID is SRV6-POLICY in the embodiment of the present disclosure
  • Figure 4 shows a schematic diagram of the generation of END.BDT6.SID in the embodiment of the present disclosure
  • Figure 5 shows a schematic diagram of service forwarding where the next hop of END.BDT6.SID is SRV6-POLICY in the embodiment of the present disclosure
  • Figure 6 shows a schematic diagram of a device for implementing H-VPN hierarchical management of an SRV6 policy network in an embodiment of the present disclosure
  • Figure 7 shows a structural block diagram of an electronic device in an embodiment of the present disclosure.
  • BGP/MPLS IP VPN is a plane model, and all PEs are on the same plane.
  • BGP/MPLS IP VPN In order to deploy VPN functions in a hierarchical structure network, BGP/MPLS IP VPN must transform from a flat model to a hierarchical model. For this reason, the solution of Hierarchy of VPN (HVPN) is proposed.
  • HVPN Hierarchy of VPN
  • the HVPN solution distributes PE functions to multiple PE devices. Multiple PEs assume different roles and form a hierarchical structure to jointly complete the functions of one PE. Therefore, this solution is sometimes called layered PE.
  • SRv6 Segment is the form of IPv6 address, which is usually also called SRv6 SID (Segment Identifier). As shown in the figure, the SRv6 SID consists of two parts: Locator and Function. The format is Locator:Function, where the Locator occupies the high-order bits of the IPv6 address and the Function part occupies the remaining part of the IPv6 address.
  • Locator has positioning function, so it must be unique within the SR domain. After a node is configured with a Locator, the system will generate a Locator network segment route and spread it within the domain through IGP. Other nodes in the network can locate this node through Locator segment routing.
  • the Function represents the instruction of the device. These instructions are preset by the device.
  • the Function part is used to instruct the SRv6 SID generation node to perform corresponding functional operations.
  • SRv6-enabled nodes maintain a local SID (Local SID) table, which contains all SRv6 SID information generated on this node.
  • An SRv6 forwarding table (FIB) can be generated based on this table.
  • the Local SID table has the following uses:
  • the inner service label is exchanged, and then the service label is superimposed on the outer tunnel and sent to the PE node.
  • H-VPN+SRV6 tunnels since the SPE is not configured with a VPN instance, there is currently no way to implement the exchange of SRV6 VPN SIDs. There is currently no implementation method for H-VPN+SRV6 services in the industry.
  • the Layer 2 services of SRV6 services all directly establish MP-BGP neighbors between the source and sink nodes. The source and sink nodes directly publish the VPN SID to the opposite end. In this way, routing is not layered and it is an end-to-end VPN service.
  • EVPN L3VPN/VPWS/VPLS cannot implement hierarchical H-VPN deployment because IPV6 VPNSID cannot implement MPLS label exchange. Therefore, point-to-point BGP neighbors can only be used to implement service deployment, and SRV6 routing needs to be opened throughout the entire network. This method increases the routing volume of the entire network and is not conducive to hierarchical management.
  • SRV6 EVPN L3VPN HOVPN services deploy VPN instances on SPE nodes. Services coming from the UPE and NPE directions are all landed on the SPE, and then the routing and forwarding mechanism is checked. After the SPE node deploys VPN, the SPE node needs to maintain VPN service routes.
  • H-VPN hierarchical management of L2/L3 services of the SRV6 network is realized through the exchange of new service SIDs.
  • the SPE node directly implements the exchange of SRV6 VPN SIDs, without the need to check the VPN service routing after the service is deployed, and the SPE There is no need to deploy a VPN instance, and services can directly exchange IPV6 addresses on the SPE node to improve forwarding efficiency.
  • Figure 2 shows a method for implementing H-VPN hierarchical management of SRV6 policy network in the embodiment of the present disclosure, which is applied to BGP of SPE equipment.
  • the method for implementing H-VPN of SRV6 policy network provided in the embodiment of the present disclosure is The VPN layered management method includes steps S202-S210.
  • S202 Receive the service route sent by the first device.
  • the service route carries the service label and color value
  • S204 Based on the business scenario to which the service route belongs, select the target SID type from the preset SID types;
  • S208 associate the target SID type with the target SRV6 policy, and generate a target service route.
  • the next hop of the SID corresponding to the target SID type in the target service route is the target SRV6 policy;
  • S210 Send the target service route to the second device, so that the second device forwards it according to the address table lookup in the target service route.
  • the service route may be a VPNv6 route corresponding to the VPNv6 service.
  • embodiments of the present disclosure can be applied to H-VPN hierarchical deployment scenarios that carry network SRV6 EVPN VPWS/VPLS/L3VPN services.
  • This disclosed embodiment can meet the hierarchical deployment of SRV6 EVPN L2 and L3 services and reduce network pressure.
  • the first device and the second device may be NPE devices and/or UPE devices.
  • the second device is a UPE device.
  • the second device is an NPE device.
  • SRv6 Policy uses the source routing mechanism of Segment Routing to guide packets through the network by encapsulating an ordered list of instructions at the head node.
  • SRv6 can also mark VAS, such as firewalls, application acceleration and other network functions, or user gateways and other functions.
  • VAS such as firewalls, application acceleration and other network functions, or user gateways and other functions.
  • SRv6 Policy can realize the end-to-end requirements of the business and is the main mechanism for realizing SRv6 network programming.
  • SRv6 Policy includes the following elements: Key value, Candidate Path, Segment List, and Binding SID.
  • SRv6 Policy uses the following triplet as a key to globally uniquely identify an SRv6 Policy: Headend, Color, and Endpoint.
  • the head node can import traffic into an SRv6 Policy;
  • the color (Color) identifies the ID of the SRv6 Policy, which can be associated with a series of business attributes, such as low latency, high bandwidth, etc., and can be understood as a business requirement template. ID whose value can be assigned by an administrator.
  • Endpoint Identifies the destination address of the SRv6 Policy.
  • the business scenario in S204 above may include at least one of the following scenarios:
  • IPV4 H-VPN scenario IPV6 H-VPN scenario, EVPN VPWS H-VPN scenario, EVPN VPLS H-VPN scenario.
  • the first SID type, the second SID type, the third SID type and the fourth SID type are only used to represent different SID types.
  • the SID types may also have other names.
  • the first SID type may be End.BDT4 SID
  • the second SID type may be End.BDT6 SID
  • the third SID type may be End.BDX2 SID
  • the fourth SID type may be END.BDT2U SID.
  • End.BDT4 SID End.BDT4 SID is used in SRV6 H-VPN (IPV4 private network) business scenarios to replace it with a new next hop.
  • the bottom layer of the SID LIST is the service label (VPN SID), and the last The outer SID is updated to the DIP and forwarded based on the new IPV6 address table lookup.
  • End.BDT4 SID is used in IPV4 H-VPN scenarios.
  • End.BDT6 SID End.BDT6 SID is used in SRV6 H-VPN (IPV6 private network) business scenarios to replace it with a new next hop.
  • the bottom layer of the SID LIST is the service label (VPN SID), and the last The outer SID is updated to the DIP and forwarded based on the new IPV6 address table lookup.
  • End.BDT6 SID is used in IPV6 H-VPN scenarios.
  • End.BDX2 SID represents the scenario of SRV6 EVPN VPWS H-VPN service, which is used to replace it with a new next hop.
  • the bottom layer of SID LIST is the service label (VPN SID), and the outermost SID is updated. to the DIP, and forward based on the new IPV6 address lookup table.
  • End.BDX2 SID can be used in EVPN VPWS H-VPN scenarios.
  • End.BDT2U SID indicates SRV6 EVPN VPLS H-VPN service
  • the scenario is used to replace it with a new next hop.
  • the bottom layer of the SID list is the service label (VPN SID), and the outermost SID is updated to the DIP, and forwarded based on the new IPV6 address table lookup.
  • VPN SID service label
  • the present disclosure also adds a new SRV6 SID next hop attribute.
  • a new next hop attribute flag is added. If the next hop is an SRV6-POLICY tunnel, the flag bit is 1, and the default is 0.
  • the process of S206 generating the target SRV6 policy is as follows:
  • the query obtains the first SRV6 policy; the second SRV6 policy is generated, and the sidlist of the second SRV6 policy is the sidlist of the first SRV6 policy; based on the second SRV6 policy and business label settings, the target SRV6 policy is obtained.
  • the last layer of the target SRV6 policy is a service label.
  • VPN SID mapping of service tags
  • the NPE For the L3 VPNV6+SRV6 H-VPN service, the NPE publishes the service route to the SPE through MP-BGP and carries VPN SID A, COLOR C. SPE's BGP locally applies for a new END.BDT6B.
  • NPE For L3 VPNV4+SRV6 H-VPN service, NPE publishes VPNv4 routes to SPE through MP-BGP, carrying VPN SID A, COLOR C. SPE's BGP locally applies for a new END.BDT4B.
  • the NPE For the EVPN VPWS+SRV6 H-VPN service, the NPE publishes Type 1 routes to the SPE through MP-BGP, carrying service SID A and COLOR C. SPE's BGP locally applies for a new END.BDX2B.
  • NPE For EVPN VPLS+SRV6 H-VPN services, NPE publishes Type 2 routes to SPE through MP-BGP, carrying service SID A and COLOR C. SPE's BGP locally applies for a new END.BDT2U B.
  • the SRv6 Policy tunnel flag bit is 1, and the next hop attribute is modified to SRV6 POLICY.
  • BGP dynamically applies for an SRV6 POLICY A1, copies the SIDLIST of POLICY S to A1, then copies the business VPN SID A to the last layer of the SIDLIST of A1, and changes END.BDT6/END.BDT4/END .BDX2/END.BDT2U next hop is set to SRV6 POLICY A1.
  • BGP colors different VPN routes
  • NPE service routes such as: private network route 2001::1/128, VPN SID A2:1::100, color: C.
  • SPE searches for the corresponding policy based on color, generates a new END.BDT6 SID A and policy A1, sets the next hop attribute of A to SRV6-POLICY, binds SID A to policy A1, and copies the sidlist of policy S to A1 , and add a layer of VPN SID to the innermost layer of A1.
  • the dynamic POLICY generation rules are as follows:
  • color+endpoint is the policy key
  • color system reserved starting value + color of policy S
  • endpoint is the NPE loopback port, which is created by BGP to dynamically apply to SRRP.
  • BDT6flag specially for END .DT6 service is used, other services cannot superimpose this policy
  • the sidlist of the policy is combined with policyS and VPN SID, and associates END.BDT6 with the policy;
  • the SPE replaces the NPE's VPNSID with END.BDT6.SID A, uses END.BDT6.SID A as the new VPN SID, and sends it to the UPE through an update message.
  • BGP dynamically generates SRV6-POLICY rules as follows:
  • the KEY values of SRV6-POLICY are COLOR and ENDPOINT.
  • the VPNSID of the BGP VPN message sent by NPE/UPE to SPE is A and the COLOR value is C.
  • the COLOR of A1 The value is C, and the ENDPOINT value is 127.0.0::1.
  • SPE searches for SRV6-POLICY locally based on the COLOR value and PEER IP of the NPE/UPE VPN message. If SRV6-POLICY S is found, it copies the SIDLIST of S to A1 and copies VPN SID A to the last layer of A1. , and associate END.BDT6/END.BDT4/END.BDX2/END.BDT2U with A1, and set the next hop SRV6-POLICY A1.
  • FIG 4 shows a schematic diagram of the generation of END.BDT6.SID, which is the BGP protocol label implementation process in the embodiment of the present disclosure.
  • the service routing is VPNv6 routing.
  • the BGP protocol label implementation process includes steps S401-S407.
  • PE is configured with SRv6 and SRv6 VPN, and the intermediate node SPE device does not need to be configured with SRV6 VPN.
  • NPE2 publishes SRv6 Locator routes to other PE devices.
  • S406 SPE's BGP locally applies for END.BDT6 and generates a new policy A.
  • the innermost SIDLIST of A is VPNSID and is associated with END.BDT6. Then it publishes VPNv6 routes and carries VPN SID (END.BDT6) to UPE.
  • CE2 publishes the IPv6 route of this site to NPE. After NPE learns VPN routing information from CE2, it stores it in the VPN instance routing table. At the same time, it is converted to VPNv6 routing.
  • NPE publishes VPNv6 routes to SPE through MP-BGP, carrying VPN SID A, COLOR C.
  • SPE's BGP locally applies for a new END.BDT6 SID B.
  • it checks the policy based on the color, finds policy N, generates a new policy M, copies the sidlist of policy N to the sidlist of policy M, and adds a layer of SID at the end.
  • the update message also carries at least one of the following attributes: RT attribute, target SID type attribute, and color attribute.
  • the update message carries the RT attribute, SRv6 VPN SID B attribute, and COLOR attribute.
  • the VPN route is delivered and associated with SRv6 VPN SID B.
  • Figure 5 shows a schematic diagram of service forwarding where the next hop of END.BDT6.SID is SRV6-POLICY.
  • the service route is VPNv6 route.
  • the service forwarding implementation process is as follows:
  • the UPE learns the network segment route A2:1::/64 corresponding to the SRv6 SID through the IGP protocol.
  • NPE automatically generates the END.DT6 SID A2:1::100 of the VPN instance within the END SID range and generates the Local SID table.
  • NPE After NPE receives the private IPv6 route published by CE2, NPE converts the private IPv6 route into BGP VPNv6 route and publishes it to SPE. This route carries the SRv6 VPN SID attribute, VPNSID A2:1::100, color C.
  • SPE After SPE receives the VPNv6 route, it newly generates END.BDT6A3:1::1, policy M, and copies the sidlist of policy N found through color to policy M, by adding a vpn sid: A2 to the innermost layer of M. :1::100. Then send VPNv6 route to UPE, carrying SRV6 VPN SID A3:1::1.
  • UPE After UPE receives the VPNv6 route, it crosses it to the corresponding VPN instance routing table, then converts it into a normal IPv6 route, and publishes it to CE1.
  • CE1 sends a normal IPv6 packet to UPE.
  • UPE After UPE receives the private network packet from the interface bound to the VPN instance, it searches the routing and forwarding table of the corresponding VPN instance, matches the destination IPv6 prefix, and finds the associated SRv6 VPN SID and next hop information. Then directly use SRv6 VPN SID A3:1::1 as the destination address to encapsulate it into an IPv6 message.
  • SPE receives the message and parses the outer DIP A3:1::1 as local END.BDT6, then adds an SRH header, fills the first label of the SRH header into the DIP, checks the routing table, and sends it to the NPE.
  • the NPE uses A2:1::100 to search the Local SID table, matches the forwarding action corresponding to the END.DT6 SID, removes the IPv6 packet header, then matches the VPN instance based on the END.DT6 SID, and searches the VPN instance routing table for forwarding.
  • certain steps may be omitted, multiple steps may be combined into one step for execution, and/or one step may be decomposed into multiple steps for execution, etc.
  • This disclosed embodiment can realize H-VPN hierarchical management of EVPN L2/L3 services of the SRV6 network; the SRV6 network can deploy H-VPN services, and the SPE nodes directly realize the exchange of VPN SIDs, and the SPE does not need to deploy VPN instances; by adding Exchange type SID, implement EVPN L2/L3VPN H-VPN, so that services can directly exchange IPV6 addresses and generate SRv6 Policy at the SPE node, improving forwarding efficiency.
  • embodiments of the present disclosure also provide a device for implementing H-VPN hierarchical management of an SRV6 policy network, as described in the following embodiments. Since the problem-solving principle of this device embodiment is similar to that of the above-mentioned method embodiment, the implementation of this device embodiment can refer to the implementation of the above-mentioned method embodiment, and repeated details will not be repeated.
  • Figure 6 shows a device for realizing h-VPN hierarchical management of SRV6 policy network in the embodiment of the present disclosure, applied to BGP of SPE equipment.
  • the device for realizing h-VPN hierarchical management of SRV6 policy network 600 including a routing message receiving module 602, a judgment module 604, a first data processing module 606, a second data processing module 608 and a data sending module 610.
  • the routing message receiving module 602 is configured to receive the service route sent by the first device, where the service route carries the service label and color value;
  • the judgment module 604 is configured to select a target SID type from the preset SID types based on the business scenario to which the service route belongs;
  • the first data processing module 606 is configured to generate a target based on the color value and business label SRV6 policy
  • the second data processing module 608 is configured to associate the target SID type with the target SRV6 policy and generate a target service route.
  • the next hop of the SID corresponding to the target SID type in the target service route is the target SRV6 policy;
  • the data sending module 610 is configured to send the target service route to the second device, so that the second device forwards it according to the address table lookup in the target service route.
  • the first data processing module 606 is specifically used to:
  • the query obtains the first SRV6 policy
  • the sidlist of the second SRV6 policy is the sidlist of the first SRV6 policy
  • the target SRV6 policy is obtained.
  • the last layer of the target SRV6 policy is the service label.
  • business scenarios include at least one of the following scenarios:
  • IPV4 H-VPN scenario IPV6 H-VPN scenario, EVPN VPWS H-VPN scenario, EVPN VPLS H-VPN scenario.
  • the judgment module 604 selects the first SID type when the business scenario to which the service route belongs is an IPV4 H-VPN scenario
  • the second device when the first device is an NPE device, the second device is a UPE device; when the first device is a UPE device, the second device is an NPE device.
  • the data sending module 610 sends the target service route to the second device, which may be through an update message.
  • the update message also carries at least one of the following attributes:
  • the device 600 for implementing SRV6 network H-VPN hierarchical management may also include:
  • the acquisition module is configured to obtain the network segment route corresponding to the SRv6 SID through the IGP protocol.
  • This disclosed embodiment can realize H-VPN hierarchical management of EVPN L2/L3 services of the SRV6 network; the SRV6 network can deploy H-VPN services, and the SPE nodes directly realize the exchange of VPN SIDs, and the SPE does not need to deploy VPN instances; by adding Exchange type SID, implement EVPN L2/L3VPN H-VPN, so that services can directly exchange IPV6 addresses and generate SRv6 Policy at the SPE node, improving forwarding efficiency.
  • the features and functions of two or more modules or units described above may be embodied in one module or unit. Conversely, the features and functions of one module or unit described above may be further divided into being embodied by multiple modules or units.
  • the electronic device provided by the embodiment of the present disclosure is described below with reference to FIG. 7 .
  • the electronic device 700 shown in FIG. 7 is only an example and should not bring any limitations to the functions and usage scope of the embodiments of the present disclosure.
  • FIG. 7 shows a schematic architectural diagram of an electronic device 700 provided by an embodiment of the present disclosure.
  • the electronic device 700 includes but is not limited to: at least one processor 710 and at least one memory 720 .
  • Memory 720 is used to store instructions.
  • the memory 720 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 7201 and/or a cache storage unit 7202, and may further include a read-only storage unit (ROM). )7203.
  • RAM random access storage unit
  • ROM read-only storage unit
  • memory 720 may also include a program/utility 7204 having a set of (at least one) program modules 7205 including, but not limited to: an operating system, one or more applications, other programs Modules, as well as program data, each of these examples or some combination may include an implementation of a network environment.
  • program/utility 7204 having a set of (at least one) program modules 7205 including, but not limited to: an operating system, one or more applications, other programs Modules, as well as program data, each of these examples or some combination may include an implementation of a network environment.
  • memory 720 may store an operating system.
  • the operating system may be a real-time operating system (Real Time eXecutive, RTX), LINUX, UNIX, WINDOWS or OS X.
  • RTX Real Time eXecutive
  • LINUX LINUX
  • UNIX UNIX
  • WINDOWS OS X.
  • data may also be stored in memory 720 .
  • the processor 710 may read the data stored in the memory 720.
  • the data may be stored at the same storage address as the instructions, or the data may be stored at a different storage address than the instructions.
  • the processor 710 is configured to call instructions stored in the memory 720 to implement the steps according to various exemplary embodiments of the present disclosure described in the "Example Method" section above.
  • the processor 710 can perform the following steps of the above method embodiment:
  • the service route carries the service label and color value
  • processor 710 may be a general-purpose processor or a special-purpose processor.
  • the processor 710 may include one or more processing cores, and the processor 710 executes various functional applications and data processing by running instructions.
  • processor 710 may include a central processing unit (CPU) and/or a baseband processor.
  • CPU central processing unit
  • baseband processor may include a baseband processor.
  • the processor 710 may determine an instruction based on the priority identification and/or functional category information carried in each control instruction.
  • processor 710 and the memory 720 can be provided separately or integrated together.
  • the processor 710 and the memory 720 may be integrated on a single board or a system on chip (SOC).
  • SOC system on chip
  • electronic device 700 is embodied in the form of a general computing device.
  • Electronic device 700 may also include bus 730 .
  • Bus 730 may be a local bus representing one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or using any of a variety of bus structures.
  • Electronic device 700 may also communicate with one or more external devices 740 (e.g., keyboard, pointing device, Bluetooth device, etc.), may also communicate with one or more devices that enable a user to interact with electronic device 700, and/or with Any device (eg, router, modem, etc.) that enables the electronic device 700 to communicate with one or more other computing devices. This communication can be done through Input/output (I/O) interface 750 is performed.
  • external devices 740 e.g., keyboard, pointing device, Bluetooth device, etc.
  • Any device eg, router, modem, etc.
  • the electronic device 700 may also communicate with one or more networks (eg, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network adapter 760.
  • networks eg, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet.
  • LAN local area network
  • WAN wide area network
  • Internet public network
  • network adapter 760 communicates with other modules of electronic device 700 through bus 730 .
  • the structure illustrated in the embodiment of the present disclosure does not constitute a specific limitation on the electronic device 700 .
  • the electronic device 700 may include more or fewer components than shown in FIG. 7 , or combine some components, or split some components, or arrange different components.
  • the components shown in Figure 7 may be implemented in hardware, software, or a combination of software and hardware.
  • the present disclosure also provides a computer-readable storage medium on which computer instructions are stored.
  • the computer instructions are executed by the processor, the method for implementing H-VPN hierarchical management of the SRV6 policy network described in the above method embodiments is implemented.
  • the computer-readable storage medium in the embodiment of the present disclosure is a computer instruction that can be sent, propagated or transmitted for use by or in combination with an instruction execution system, device or device.
  • computer-readable storage media is non-volatile storage media.
  • more specific examples of computer-readable storage media in this disclosure may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard drive, random access memory (RAM), Read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, U disk, mobile hard disk or the above Any suitable combination.
  • the computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, in which computer instructions (readable program codes) are carried.
  • Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above.
  • computing instructions embodied on a computer-readable storage medium may be transmitted using any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.
  • Embodiments of the present disclosure also provide a computer program product.
  • the computer program product stores instructions. When executed by a computer, the instructions cause the computer to implement the method for implementing H-VPN hierarchical management of an SRV6 policy network described in the above method embodiments.
  • the above instructions may be program code.
  • the program code may be written in any combination of one or more programming languages.
  • Programming languages include object-oriented programming languages such as Java, C++, etc., and also include conventional procedural programming languages such as "C" language or similar programming languages.
  • the program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on.
  • the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device, such as provided by an Internet service. (business comes via Internet connection).
  • LAN local area network
  • WAN wide area network
  • Internet service business comes via Internet connection
  • Embodiments of the present disclosure also provide a chip, including at least one processor and an interface;
  • Interface used to provide program instructions or data to at least one processor
  • At least one processor is used to execute program instructions to implement the method of implementing SRV6 policy network H-VPN hierarchical management described in the above method embodiment.
  • the chip may also include memory for storing program instructions and data, and the memory may be located within or outside the processor.

Landscapes

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

Abstract

本公开提供了一种实现SRV6 policy网络H-VPN分层管理的方法、装置及相关设备，涉及通信技术领域。该方法包括：接收第一设备发送的业务路由，业务路由携带业务标签和颜色color值；基于业务路由所属的业务场景，在预设SID类型中选择目标SID类型；根据color值和业务标签，生成目标SRV6 policy；将目标SID类型和目标SRV6 policy关联，生成目标业务路由，目标业务路由中目标SID类型对应的SID的下一跳为目标SRV6 policy；将目标业务路由发送至第二设备，以使第二设备根据目标业务路由中的地址查表转发。根据本公开实施例，SPE无需部署VPN实例，能够直接实现VPN SID的交换，实现SRV6 policy网络的EVPN L2/L3业务的H-VPN分层管理。

Description

实现SRV6 policy网络H-VPN分层管理的方法、装置及相关设备
相关申请的交叉引用
本公开要求于2022年08月11日提交的申请号为202210964146.2，名称为“实现SRV6 policy网络H-VPN分层管理的方法、装置、设备及介质”的中国专利申请的优先权，该中国专利申请的全部内容通过引用全部并入本文。
技术领域
本公开涉及通信技术领域，尤其涉及一种实现SRV6 policy网络H-VPN分层管理的方法、装置、设备、介质及计算机程序产品。
背景技术
在H-VPN+MPLS隧道，UPE业务报文到达SPE后，内层业务标签交换，然后业务标签叠加外层隧道并送到PE节点。而对于H-VPN+SRV6隧道，由于SPE没有配置VPN实例，暂时没有方法实现SRV6业务标签(VPN SID)的交换，业内暂无H-VPN+SRV6业务实现方法。相关技术中，SRV6业务的二层业务均是在源宿节点直接建MP-BGP邻居，源宿节点直接发布VPN SID到对端，这样路由没有实现分层，是端到端建立的VPN业务。
需要说明的是，在上述背景技术部分公开的信息仅用于加强对本公开的背景的理解，因此可以包括不构成对本领域普通技术人员已知的现有技术的信息。
发明内容
发明人通过研究发现，当前EVPN L3VPN/VPWS/VPLS由于SRV6 VPN SID不能实现类似MPLS标签的交换，故不能实现分层H-VPN部署，所以只能采用点到点建BGP邻居实现业务部署，且SRV6路由需要全网打通，这种方式加大了全网路由量，不利于分层管理。
作为一个实施例，对本申请中的术语的解释是参考中国通信标准化协会的规范协议的定义。
根据本公开的第一方面，提供了一种实现SRV6 policy网络H-VPN分层管理的方法，应用于SPE设备的BGP，方法包括：
接收第一设备发送的业务路由，业务路由携带业务标签和颜色color值；
基于业务路由所属的业务场景，在预设SID类型中选择目标SID类型；
根据color值和业务标签，生成目标SRV6 policy；
将目标SID类型和目标SRV6 policy关联，生成目标业务路由，目标业 务路由中目标SID类型对应的SID的下一跳为目标SRV6 policy；
将目标业务路由发送至第二设备，以使第二设备根据目标业务路由中的地址查表转发。
在本公开的一个实施例中，根据color值和业务标签，生成目标SRV6 policy，包括：
根据color值，查询得到第一SRV6 policy；
生成第二SRV6 policy，第二SRV6 policy的sidlist为第一SRV6 policy的sidlist；
基于第二SRV6 policy和业务标签置，得到目标SRV6 policy。
在本公开的一个实施例中，目标SRV6 policy的最后一层为业务标签。在本公开的一个实施例中，业务场景，包括如下场景中的至少一种：
IPV4 H-VPN场景、IPV6 H-VPN场景、EVPN VPWS H-VPN场景、EVPN VPLS H-VPN场景。
在本公开的一个实施例中，业务路由所属的业务场景为IPV4 H-VPN场景时，选择第一SID类型；
在业务路由所属的业务场景为IPV6 H-VPN场景时，选择第二SID类型；
在业务路由所属的业务场景为EVPN VPWS H-VPN场景时，选择第三SID类型；
在业务路由所属的业务场景为EVPN VPLS H-VPN场景时，选择第四SID类型。
在本公开的一个实施例中，在第一设备为NPE设备的情况下，第二设备为UPE设备；在第一设备为UPE设备的情况下，第二设备为NPE设备。
在本公开的一个实施例中，将目标业务路由发送至第二设备，包括：
通过update消息将目标业务路由发送至第二设备。
在本公开的一个实施例中，update消息还携带如下属性中的至少一种：
RT属性、目标SID类型的属性、color属性。
在本公开的一个实施例中，方法还包括：
通过IGP协议获取SRv6 SID对应的网段路由。
根据本公开的第二方面，提供一种实现SRV6 policy网络H-VPN分层管理的装置，应用于SPE设备的BGP，装置包括路由报文接收模块、判断模块、第一数据处理模块、第二数据处理模块和数据发送模块。
路由报文接收模块，被配置为接收第一设备发送的业务路由，业务路由携带业务标签和颜色color值；
判断模块，被配置为基于业务路由所属的业务场景，在预设SID类型中 选择目标SID类型；
第一数据处理模块，被配置为根据color值和业务标签，生成目标SRV6 policy；
第二数据处理模块，被配置为将目标SID类型和目标SRV6 policy关联，生成目标业务路由，目标业务路由中目标SID类型对应的SID的下一跳为目标SRV6 policy；
数据发送模块，被配置为将目标业务路由发送至第二设备，以使第二设备根据目标业务路由中的地址查表转发。
根据本公开的第三方面，提供一种电子设备，包括：存储器，用于存储指令；处理器，用于调用所述存储器中存储的指令，实现上述的实现SRV6 policy网络H-VPN分层管理的方法。
根据本公开的第四方面，提供一种计算机可读存储介质，其上存储有计算机指令，所述计算机指令被处理器执行时实现上述的实现SRV6 policy网络H-VPN分层管理的方法。
根据本公开的第五方面，提供一种计算机程序产品，计算机程序产品存储有指令，所述指令在由计算机执行时，使得计算机实施上述的实现SRV6 policy网络H-VPN分层管理的方法。
根据本公开的第六方面，提供一种芯片，包括至少一个处理器和接口；
接口，用于为至少一个处理器提供程序指令或者数据；
至少一个处理器用于执行程序指令，以实现上述的实现SRV6 policy网络H-VPN分层管理的方法。
本公开实施例所提供的实现SRV6 policy网络H-VPN分层管理的方法、装置、设备及介质，基于业务路由所属的业务场景，在预设SID类型中选择目标SID类型，根据color值和业务标签，生成目标SRV6 policy，然后将目标SID类型和目标SRV6 policy关联，生成目标业务路由，目标业务路由中目标SID类型对应的SID的下一跳为目标SRV6 policy；；将目标业务路由发送至第二设备，以使第二设备根据目标业务路由中的地址查表转发。本公开实施例SPE无需部署VPN实例，可以直接实现VPN SID的交换，实现SRV6 policy网络的EVPN L2/L3业务的H-VPN分层管理。
应当理解的是，以上的一般描述和后文的细节描述仅是示例性和解释性的，并不能限制本公开。
附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。
显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示出了相关技术中EVPN L3VPN HoVPN业务架构示意图；
图2示出本公开实施例中一种实现SRV6 policy网络H-VPN分层管理的方法流程图；
图3示出本公开实施例中END.BDT6.SID下一跳为SRV6-POLICY的映射示意图；
图4示出本公开实施例中END.BDT6.SID的生成示意图；
图5示出本公开实施例中END.BDT6.SID下一跳为SRV6-POLICY的业务转发示意图；
图6示出本公开实施例中一种实现SRV6 policy网络H-VPN分层管理的装置示意图；
图7示出本公开实施例中一种电子设备的结构框图。
具体实施方式
下面将参考附图更全面地描述示例实施方式。
需要说明的是，示例实施方式能够以多种形式实施，不应被理解为限于在此阐述的范例。
目前的网络设计大多采用传统分层结构，例如，城域网的典型结构是三层模型：核心层、汇聚层、接入层。而BGP/MPLS IP VPN是一种平面模型，所有PE处于同一平面。为了在分层结构网络中部署VPN功能，BGP/MPLS IP VPN必然要从平面模型转变为分层模型。为此，提出了分层VPN(Hierarchy of VPN，简称HVPN)的解决方案。
HVPN解决方案是将PE的功能分布到多个PE设备上，多个PE承担不同的角色，并形成层次结构，共同完成一个PE的功能。因此，这种解决方案有时也被称为分层PE。
SRv6 Segment是IPv6地址形式，通常也可以称为SRv6 SID(Segment Identifier)。如图，SRv6 SID由Locator和Function两部分组成，格式是Locator:Function，其中Locator占据IPv6地址的高比特位，Function部分占据IPv6地址的剩余部分。
Locator具有定位功能，所以要在SR域内唯一。节点配置Locator之后，系统会生成一条Locator网段路由，并且通过IGP在域内扩散。网络里其他节点通过Locator网段路由就可以定位到本节点。
Function代表设备的指令(Instruction)，这些指令都由设备预先设定， Function部分用于指示SRv6 SID的生成节点进行相应的功能操作。
使能SRv6的节点维护一个本地SID(Local SID)表，该表包含所有在本节点生成的SRv6 SID信息，根据该表可以生成一个SRv6转发表(FIB)。
Local SID表有以下用途：
1、定义本地生成的SID，例如End.X SID。
2、指定绑定到这些SID的指令。
3、存储和这些指令相关的转发信息，例如出接口和下一跳等。
在H-VPN+MPLS隧道，UPE业务报文到达SPE后，内层业务标签交换，然后业务标签叠加外层隧道并送到PE节点。
而对于H-VPN+SRV6隧道，由于SPE没有配置VPN实例，暂时没有方法实现SRV6 VPN SID的交换，业内暂无H-VPN+SRV6业务实现方法。目前SRV6业务的二层业务均是在源宿节点直接建MP-BGP邻居，源宿节点直接发布VPN SID到对端，这样路由没有实现分层，是端到端建立的VPN业务。
发明人发现，相关技术中存在如下问题：
当前EVPN L3VPN/VPWS/VPLS由于IPV6 VPNSID不能实现类似MPLS标签的交换，故不能实现分层H-VPN部署，所以只能采用点到点建BGP邻居实现业务部署，且SRV6路由需要全网打通，这种方式加大了全网路由量，不利于分层管理。
对于现有EVPN L3VPN HoVPN业务，通过在SPE节点部署VPN业务，UPE和NPE方向过来的业务均在SPE落地，再查路由转发。且SPE节点在部署VPN后，需要生成大量的VPN业务路由，对SPE产生较大的业务压力。
配置EVPN L3VPN HoVPN模型，UPE和NPE节点过来的业务均需要在SPE落地，再进行查路由转发，业务转发效率较低。
如图1所示相关技术中，SRV6 EVPN L3VPN HOVPN业务通过在SPE节点部署VPN实例，UPE和NPE方向过来的业务均在SPE落地，再查路由转发机制。SPE节点在部署VPN后，SPE节点需要维护VPN业务路由。
配置EVPN L3VPN HoVPN模型，UPE和NPE节点过来的业务均需要在SPE落地，再进行查路由转发，业务转发效率较低。SPE节点在部署VPN后，需要生成大量的VPN业务路由，对SPE产生较大的业务压力。
本公开实施例，通过新增业务SID的交换实现SRV6网络的L2/L3业务的H-VPN分层管理，SPE节点直接实现SRV6 VPN SID的交换，无需业务落地后再查VPN业务路由，且SPE无需部署VPN实例，业务可以在SPE节点直接进行IPV6地址的交换，提高转发效率。
下面结合附图及实施例对本示例实施方式进行详细说明。
图2示出本公开实施例中一种实现SRV6 policy网络H-VPN分层管理的方法，应用于SPE设备的BGP，如图2所示，本公开实施例中提供的实现SRV6 policy网络H-VPN分层管理的方法包括步骤S202-S210。
S202，接收第一设备发送的业务路由，业务路由携带业务标签和颜色color值；
S204，基于业务路由所属的业务场景，在预设SID类型中选择目标SID类型；
S206，根据color值和业务标签，生成目标SRV6 policy；
S208，将目标SID类型和目标SRV6 policy关联，生成目标业务路由，目标业务路由中目标SID类型对应的SID的下一跳为目标SRV6 policy；
S210，将目标业务路由发送至第二设备，以使第二设备根据目标业务路由中的地址查表转发。
在一些实施例中，业务路由可以是VPNv6业务对应的VPNv6路由。
需要说明的是，本公开实施例可以应用于承载网络SRV6 EVPN VPWS/VPLS/L3VPN业务的H-VPN分层部署场景。本公开实施例能够满足SRV6 EVPN L2及L3业务的分层部署，减少网络压力。
本公开实施例中，第一设备和第二设备可以是NPE设备和/或UPE设备。
作为一个示例，在第一设备为NPE设备的情况下，第二设备为UPE设备。
作为另一个示例，在第一设备为UPE设备的情况下，第二设备为NPE设备。
SRv6 Policy利用Segment Routing的源路由机制，通过在头结点封装一个有序的指令列表来指导报文穿越网络。SRv6除了用于标示转发路径的指令外，还能标示VAS，例如：防火墙，应用加速等网络功能，或者用户网关等功能。SRv6 Policy可以实现业务的端到端需求，是实现SRv6网络编程主要的机制。
在一些实施例中，SRv6 Policy包含如下要素：Key值、Candidate Path、Segment List、Binding SID。
作为一个示例，SRv6 Policy使用如下三元组作为Key，全局唯一标识一个SRv6 Policy：头节点(Headend)、颜色(Color)、目的节点(Endpoint)。
其中，头节点(Headend)可以将流量导入一个SRv6 Policy中；颜色(Color)标识SRv6 Policy的ID，可与一系列业务属性相关联，比如低时延、高带宽等，可理解为业务需求模板ID，其值可由管理者分配。目的节点(Endpoint) 标识SRv6 Policy的目的地址。
在一些实施例中，上述S204中的业务场景，可以包括如下场景中的至少一种：
IPV4 H-VPN场景、IPV6 H-VPN场景、EVPN VPWS H-VPN场景、EVPN VPLS H-VPN场景。
上述S204中在业务路由所属的业务场景为IPV4 H-VPN场景时，选择第一SID类型；
上述S204中在业务路由所属的业务场景为IPV6 H-VPN场景时，选择第二SID类型；
上述S204中在业务路由所属的业务场景为EVPN VPWS H-VPN场景时，选择第三SID类型；
上述S204中在业务路由所属的业务场景为EVPN VPLS H-VPN场景时，选择第四SID类型。
在本公开实施例中，术语“第一”、“第二”、“第三”和“第四”等仅用于描述目的，而不能理解为指示或暗示相对重要性。
上述示例中第一SID类型、第二SID类型、第三SID类型和第四SID类型，仅用于表示不同的SID类型，在具体实施中，SID类型也可以有其它的名称。
作为一个示例，第一SID类型可以是End.BDT4 SID，第二SID类型可以是End.BDT6 SID，第三SID类型可以是End.BDX2 SID，第四SID类型可以是END.BDT2U SID。
End.BDT4 SID：End.BDT4 SID用于SRV6 H-VPN(IPV4私网)业务的场景，用于替换为一个新的下一跳，SID LIST最底层为业务标签(VPN SID)，并将最外层SID更新到DIP，并根据新的IPV6地址查表转发。End.BDT4 SID在IPV4 H-VPN场景使用。
End.BDT6 SID：End.BDT6 SID用于SRV6 H-VPN(IPV6私网)业务的场景，用于替换为一个新的下一跳，SID LIST最底层为业务标签(VPN SID)，并将最外层SID更新到DIP，并根据新的IPV6地址查表转发。End.BDT6 SID在IPV6 H-VPN场景使用。
End.BDX2 SID：End.BDX2 SID表示SRV6 EVPN VPWS H-VPN业务的场景，用于替换为一个新的下一跳，SID LIST最底层为业务标签(VPN SID)，并将最外层SID更新到DIP，并根据新的IPV6地址查表转发。End.BDX2 SID可以用于EVPN VPWS H-VPN场景。
END.BDT2U SID：End.BDT2U SID表示SRV6 EVPN VPLS H-VPN业务 的场景，用于替换为一个新的下一跳，SID LIST最底层为业务标签(VPN SID)，并将最外层SID更新到DIP，并根据新的IPV6地址查表转发。可以用于EVPN VPLS H-VPN场景。
在一些实施例中，本公开还新增了SRV6 SID下一跳属性。
对于END.BDT6、END.BDT4、END.BDX2、END.BDT2U，新增下一跳属性标记，如果下一跳为SRV6-POLICY隧道，则标记位1，默认为0。
在一些实施例中，S206生成目标SRV6 policy的过程如下：
根据color值，查询得到第一SRV6 policy；生成第二SRV6 policy，第二SRV6 policy的sidlist为第一SRV6 policy的sidlist；基于第二SRV6 policy和业务标签置，得到目标SRV6 policy。
在本公开的一个实施例中，目标SRV6 policy的最后一层为业务标签。
下面结合上述示例，详细介绍业务标签(VPN SID)的映射。
对于L3 VPNV6+SRV6 H-VPN业务，NPE通过MP-BGP把业务路由发布给SPE，并携带VPN SID A,COLOR C。SPE的BGP本地申请一个新的END.BDT6B。
对于L3 VPNV4+SRV6 H-VPN业务，NPE通过MP-BGP把VPNv4路由发布给SPE，并携带VPN SID A，COLOR C。SPE的BGP本地申请一个新的END.BDT4B。
对于EVPN VPWS+SRV6 H-VPN业务，NPE通过MP-BGP把Type 1路由发布给SPE，并携带业务SID A，COLOR C。SPE的BGP本地申请一个新的END.BDX2B。
对于EVPN VPLS+SRV6 H-VPN业务，NPE通过MP-BGP把Type 2路由发布给SPE，并携带业务SID A，COLOR C。SPE的BGP本地申请一个新的END.BDT2U B。
对于SRV6 POLICY业务，SRv6 Policy隧道标记位为1，修改下一跳属性为SRV6 POLICY。
根据COLOR C查找到POLICY S，BGP动态申请一个SRV6 POLICY A1，将POLICY S的SIDLIST拷贝到A1,再将业务VPN SID A拷贝到A1的SIDLIST最后一层，将END.BDT6/END.BDT4/END.BDX2/END.BDT2U下一跳设置为SRV6 POLICY A1。
作为一个示例，如图3所示NPE上SRv6 policy业务，BGP针对不同VPN路由打上color；
SPE收到NPE业务路由，如：私网路由2001::1/128，VPN SID A2:1::100，color：C。
SPE根据color查找对应policy，新生成一个END.BDT6 SID A及policy A1，并将A的下一跳属性设置为SRV6-POLICY，将SID A与policy A1绑定，将policy S的sidlist拷贝到A1，并在A1最内层加一层VPN SID。
作为一个示例，动态POLICY产生规则如下：
policy Name color C endpoint XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX:XXXX
其中color+endpoint为policy key，color＝系统预留起始值+policy S的color，endpoint为NPE环回口，由BGP向SRRP动态申请创建，同时为该policy增加一个属性：BDT6flag，专为END.DT6业务使用，其他业务不能叠加该policy；policy的sidlist通过policyS和VPN SID组合，并将END.BDT6与policy关联；
SPE将END.BDT6.SID A替换NPE的VPNSID，将END.BDT6.SID A作为新VPN SID，通过update消息发送给UPE。
作为另一个示例，BGP动态生成SRV6-POLICY规则如下：
SRV6-POLICY的KEY值为COLOR和ENDPOINT，假设NPE/UPE发送给SPE的BGP VPN消息的VPNSID为A，COLOR值为C，当SPE为END.BDT标签动态生成SRV6-POLICY A1时，A1的COLOR赋值为C，ENDPOINT赋值为127.0.0::1。SPE根据NPE/UPE VPN消息的COLOR值和PEER IP，在本地查找SRV6-POLICY，如果查到SRV6-POLICY S，则将S的SIDLIST拷贝到A1，并将VPN SID A拷贝到A1的最后一层，同时将END.BDT6/END.BDT4/END.BDX2/END.BDT2U与A1进行关联，下一跳设置SRV6-POLICY A1。
标签推送NPE->SPE->UPE：SPE设备的BGP收到NPE的业务标签A后，动态生成一个END.BDT6/END.BDT4/END.BDX2/END.BDT2U标签，并将该标签作为业务标签，通过BGP UPDATE消息推送UPE设备；反方向处理流程一样，UPE->SPE->NPE。
图4示出了END.BDT6.SID的生成示意图，也就是本公开实施例中BGP协议标签实现过程，在该示例中业务路由为VPNv6路由，如图4所示，BGP协议标签实现过程包括步骤S401-S407。
S401，配置SRv6 VPN。
PE配置SRv6和SRv6 VPN，中间节点SPE设备不需要配置SRV6 VPN。
S402，发布SRv6 Locator路由给其他PE设备。
NPE2发布SRv6 Locator路由给其他PE设备。
S403，发布IPv6路由。
S404，安装VPN实例路由，生成VPNv6路由。
S405，发布VPNv6路由，携带VPN SID，color。
S406，SPE的BGP本地申请END.BDT6，并新生成一个policy A，A的SIDLIST最内层为VPNSID，并与END.BDT6关联，然后发布VPNv6路由，携带VPN SID(END.BDT6)到UPE。
S407，接收VPNv6路由，安装携带SRv6 VPN SID的VPN实例路由。
CE到PE的路由信息交换：CE2把本站点的IPv6路由发布给NPE。NPE从CE2学习到VPN路由信息后，存放到VPN实例路由表中。同时，转换成VPNv6路由。
PE之间路由发布：NPE通过MP-BGP把VPNv6路由发布给SPE，并携带VPN SID A,COLOR C。SPE的BGP本地申请一个新的END.BDT6 SID B，同时根据color查policy，查询到policy N，新生成一个policy M，将policy N的sidlist拷贝到policy M的sidlist，并在最后加一层SID A。将END.BDT6 SID B与policy M进行关联，同时向UPE发送Update报文。
在一些实施例中，update消息还携带如下属性中的至少一种：RT属性、目标SID类型的属性、color属性。
作为一个示例，update消息报文中携带RT属性、SRv6 VPN SID B属性、COLOR属性。
UPE收到VPNv4路由后，VPN路由下发同时关联SRv6 VPN SID B。
图5示出了END.BDT6.SID下一跳为SRV6-POLICY的业务转发示意图，在该示例中业务路由为VPNv6路由，如图5所示，业务转发实现过程如下：
NPE上配置END SID，然后通过IGP协议发布给SPE、UPE。
UPE通过IGP协议学习到SRv6 SID对应的网段路由A2:1::/64。
NPE在END SID范围内自动生成VPN实例的END.DT6 SID A2:1::100，生成Local SID表。
NPE收到CE2发布的私网IPv6路由后，NPE将私网IPv6路由转换成BGP VPNv6路由，发布给SPE。此路由携带SRv6 VPN SID属性，VPNSID A2:1::100、color C。
SPE接收到VPNv6路由后，新生成END.BDT6A3:1::1，policy M，并将通过color查到的policy N的sidlist拷贝到policy M，通过在M的最内层添加一个vpn sid：A2:1::100。然后发送VPNv6路由给UPE，携带SRV6 VPN SID A3:1::1。
UPE接收到VPNv6路由后，将其交叉到对应的VPN实例路由表，然后转换成普通IPv6路由，对CE1发布。
参考图5，数据转发阶段过程如下：
CE1向UPE发送一个普通IPv6报文。
UPE从绑定了VPN实例的接口上收到私网报文以后，查找对应VPN实例的路由转发表，匹配目的IPv6前缀，查找到关联的SRv6 VPN SID以及下一跳信息。然后直接使用SRv6 VPN SID A3:1::1作为目的地址封装成IPv6报文。
SPE收到报文，解析外层DIP A3:1::1为本地END.BDT6，，则添加SRH头，将SRH头第一个标签填入DIP，查路由表发送给NPE。
NPE使用A2:1::100查找Local SID表，匹配到END.DT6 SID对应的转发动作，将IPv6报文头去除，然后根据END.DT6 SID匹配VPN实例，查找VPN实例路由表进行转发。
此外，尽管在附图中以特定顺序描述了本公开中方法的各个步骤，但是，这并非要求或者暗示必须按照该特定顺序来执行这些步骤，或是必须执行全部所示的步骤才能实现期望的结果。
在一些实施例中，可以省略某些步骤，将多个步骤合并为一个步骤执行，以及/或者将一个步骤分解为多个步骤执行等。
本公开实施例可以实现SRV6网络的EVPN L2/L3业务的H-VPN分层管理；SRV6网络能部署H-VPN业务，SPE节点直接实现VPN SID的交换，且SPE无需部署VPN实例；通过新增交换类型SID，实现EVPN L2/L3VPN H-VPN，使业务可以在SPE节点直接进行IPV6地址的交换及SRv6 Policy的生成，提高转发效率。
基于同一发明构思，本公开实施例中还提供了一种实现SRV6 policy网络H-VPN分层管理的装置，如下面的实施例所述。由于该装置实施例解决问题的原理与上述方法实施例相似，因此该装置实施例的实施可以参见上述方法实施例的实施，重复之处不再赘述。
图6示出本公开实施例中一种实现SRV6 policy网络H-VPN分层管理的装置，应用于SPE设备的BGP，如图6所示，该实现SRV6 policy网络H-VPN分层管理的装置600，包括路由报文接收模块602、判断模块604、第一数据处理模块606、第二数据处理模块608和数据发送模块610。
路由报文接收模块602，被配置为接收第一设备发送的业务路由，业务路由携带业务标签和颜色color值；
判断模块604，被配置为基于业务路由所属的业务场景，在预设SID类型中选择目标SID类型；
第一数据处理模块606，被配置为根据color值和业务标签，生成目标 SRV6 policy；
第二数据处理模块608，被配置为将目标SID类型和目标SRV6 policy关联，生成目标业务路由，目标业务路由中目标SID类型对应的SID的下一跳为目标SRV6 policy；
数据发送模块610，被配置为将目标业务路由发送至第二设备，以使第二设备根据目标业务路由中的地址查表转发。
在一些实施例中，第一数据处理模块606，具体用于：
根据color值，查询得到第一SRV6 policy；
生成第二SRV6 policy，第二SRV6 policy的sidlist为第一SRV6 policy的sidlist；
基于第二SRV6 policy和业务标签置，得到目标SRV6 policy。
在一些实施例中，目标SRV6 policy的最后一层为业务标签。
在一些实施例中，业务场景，包括如下场景中的至少一种：
IPV4 H-VPN场景、IPV6 H-VPN场景、EVPN VPWS H-VPN场景、EVPN VPLS H-VPN场景。
在一些实施例中，判断模块604在业务路由所属的业务场景为IPV4 H-VPN场景时，选择第一SID类型；
在业务路由所属的业务场景为IPV6 H-VPN场景时，选择第二SID类型；
在业务路由所属的业务场景为EVPN VPWS H-VPN场景时，选择第三SID类型；
在业务路由所属的业务场景为EVPN VPLS H-VPN场景时，选择第四SID类型。
在一些实施例中，在第一设备为NPE设备的情况下，第二设备为UPE设备；在第一设备为UPE设备的情况下，第二设备为NPE设备。
在一些实施例中，数据发送模块610将目标业务路由发送至第二设备，可以是通过update消息将目标业务路由发送至第二设备。
在一些实施例中，update消息还携带如下属性中的至少一种：
RT属性、目标SID类型的属性、color属性。
在一些实施例中，该实现SRV6网络H-VPN分层管理的装置600，还可以包括：
获取模块，被配置为通过IGP协议获取SRv6 SID对应的网段路由。
本公开中提及的“第一”、“第二”等概念仅用于对不同的装置、模块或单元进行区分，并非用于限定这些装置、模块或单元所执行的功能的顺序或者相互依存关系。
关于上述实施例中的实现SRV6网络H-VPN分层管理的装置，其中各个模块执行操作的具体方式已经在有关该实现SRV6网络H-VPN分层管理的方法的实施例中进行了详细描述，此处将不做详细阐述说明。
本公开实施例可以实现SRV6网络的EVPN L2/L3业务的H-VPN分层管理；SRV6网络能部署H-VPN业务，SPE节点直接实现VPN SID的交换，且SPE无需部署VPN实例；通过新增交换类型SID，实现EVPN L2/L3VPN H-VPN，使业务可以在SPE节点直接进行IPV6地址的交换及SRv6 Policy的生成，提高转发效率。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。
实际上，根据本公开的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
附图中所示的一些方框图是功能实体，不一定必须与物理或逻辑上独立的实体相对应。可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
下面参照图7来描述本公开实施例提供的电子设备。图7显示的电子设备700仅仅是一个示例，不应对本公开实施例的功能和使用范围带来任何限制。
图7示出本本公实施例提供的一种电子设备700的架构示意图。如图7所示，该电子设备700包括但不限于：至少一个处理器710、至少一个存储器720。
存储器720，用于存储指令。
在一些实施例中，存储器720可以包括易失性存储单元形式的可读介质，例如随机存取存储单元(RAM)7201和/或高速缓存存储单元7202，还可以进一步包括只读存储单元(ROM)7203。
在一些实施例中，存储器720还可以包括具有一组(至少一个)程序模块7205的程序/实用工具7204，这样的程序模块7205包括但不限于：操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。
在一些实施例中，存储器720可存储操作系统。该操作系统可以是实时操作系统(Real Time eXecutive，RTX)、LINUX、UNIX、WINDOWS或OS X之类的操作系统。
在一些实施例中，存储器720中还可以存储有数据。
作为一个示例，处理器710可以读取存储器720中存储的数据，该数据可以与指令存储在相同的存储地址，该数据也可以与指令存储在不同的存储地址。
处理器710，用于调用存储器720中存储的指令，实现本说明书上述“示例性方法”部分中描述的根据本公开各种示例性实施方式的步骤。例如，所述处理器710可以执行上述方法实施例的如下步骤：
接收第一设备发送的业务路由，业务路由携带业务标签和颜色color值；
基于业务路由所属的业务场景，在预设SID类型中选择目标SID类型；
根据所述color值和所述业务标签，生成目标SRV6 policy；
将所述目标SID类型和所述目标SRV6 policy关联，生成目标业务路由，所述目标业务路由中所述目标SID类型对应的SID的下一跳为所述目标SRV6 policy；
将目标业务路由发送至第二设备，以使第二设备根据目标业务路由中的地址查表转发。
需要说明的是，上述处理器710可以是通用处理器或者专用处理器。处理器710可以包括一个或者一个以上处理核心，处理器710通过运行指令执行各种功能应用以及数据处理。
在一些实施例中，处理器710可以包括中央处理器(central processing unit，CPU)和/或基带处理器。
在一些实施例中，处理器710可以根据各个控制指令中携带的优先级标识和/或功能类别信息确定一个指令。
本公开中，处理器710和存储器720可以单独设置，也可以集成在一起。
作为一个示例，处理器710和存储器720可以集成在单板或者系统级芯片(system on chip，SOC)上。
如图7所示，电子设备700以通用计算设备的形式表现。电子设备700还可以包括总线730。
总线730可以为表示几类总线结构中的一种或多种，包括存储器总线或者存储器控制器、外围总线、图形加速端口、处理器或者使用多种总线结构中的任意总线结构的局域总线。
电子设备700也可以与一个或多个外部设备740(例如键盘、指向设备、蓝牙设备等)通信，还可与一个或者多个使得用户能与该电子设备700交互的设备通信，和/或与使得该电子设备700能与一个或多个其它计算设备进行通信的任何设备(例如路由器、调制解调器等等)通信。这种通信可以通过 输入/输出(I/O)接口750进行。
并且，电子设备700还可以通过网络适配器760与一个或者多个网络(例如局域网(LAN)，广域网(WAN)和/或公共网络，例如因特网)通信。
如图7所示，网络适配器760通过总线730与电子设备700的其它模块通信。
应当明白，尽管图中未示出，可以结合电子设备700使用其它硬件和/或软件模块，包括但不限于：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
可以理解的是，本公开实施例示意的结构并不构成对电子设备700的具体限定。在本公开另一些实施例中，电子设备700可以包括比图7所示更多或更少的部件，或者组合某些部件，或者拆分某些部件，或者不同的部件布置。图7所示的部件可以以硬件，软件或软件和硬件的组合实现。
本公开还提供了一种计算机可读存储介质，其上存储有计算机指令，计算机指令被处理器执行时实现上述方法实施例描述的实现SRV6 policy网络H-VPN分层管理的方法。
本公开实施例中计算机可读存储介质，为可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的计算机指令。
作为一个示例，计算机可读存储介质是非易失性存储介质。
在一些实施例中，本公开中的计算机可读存储介质的更具体的例子可以包括但不限于：具有一个或多个导线的电连接、便携式计算机磁盘、硬盘、随机访问存储器(RAM)、只读存储器(ROM)、可擦式可编程只读存储器(EPROM或闪存)、光纤、便携式紧凑磁盘只读存储器(CD-ROM)、光存储器件、磁存储器件、U盘、移动硬盘或者上述的任意合适的组合。
本公开实施例中，计算机可读存储介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了计算机指令(可读程序代码)。
这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。
可读存储介质以外的任何可读介质，该可读介质
在一些示例中，计算机可读存储介质上包含的计算指令可以用任何适当的介质传输，包括但不限于无线、有线、光缆、RF等等，或者上述的任意合适的组合。
本公开实施例还提供一种计算机程序产品，计算机程序产品存储有指令，指令在由计算机执行时，使得计算机实施上述方法实施例描述的实现SRV6policy网络H-VPN分层管理的方法。
上述指令可以是程序代码。在具体实施时，程序代码可以由一种或多种程序设计语言的任意组合来编写。
程序设计语言包括面向对象的程序设计语言—诸如Java、C++等，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。
程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。
在涉及远程计算设备的情形中，远程计算设备可以通过任意种类的网络，包括局域网(LAN)或广域网(WAN)，连接到用户计算设备，或者，可以连接到外部计算设备(例如利用因特网服务提供商来通过因特网连接)。
本公开实施例还提供了一种芯片，包括至少一个处理器和接口；
接口，用于为至少一个处理器提供程序指令或者数据；
至少一个处理器用于执行程序指令，以实现上述方法实施例描述的实现SRV6 policy网络H-VPN分层管理的方法。
在一些实施例中，该芯片还可以包括存储器，该存储器，用于保存程序指令和数据，存储器位于处理器之内或处理器之外。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以具体实现为以下形式，即：完全的硬件实施方式、完全的软件实施方式(包括固件、微代码等)，或硬件和软件方面结合的实施方式，这里可以统称为“电路”、“模块”或“系统”。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其它实施方案。
本公开旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由所附的权利要求指出。

Claims (12)

  1. 一种实现SRV6 policy网络H-VPN分层管理的方法，应用于SPE设备的BGP，所述方法包括：
    接收第一设备发送的业务路由，所述业务路由携带业务标签和颜色color值；
    基于所述业务路由所属的业务场景，在预设SID类型中选择目标SID类型；
    根据所述color值和所述业务标签，生成目标SRV6 policy；
    将所述目标SID类型和所述目标SRV6 policy关联，生成目标业务路由，所述目标业务路由中所述目标SID类型对应的SID的下一跳为所述目标SRV6 policy；
    将所述目标业务路由发送至第二设备，以使所述第二设备根据所述目标业务路由中的地址查表转发。
  2. 根据权利要求1所述的方法，其中，根据所述color值和所述业务标签，生成目标SRV6 policy，包括：
    根据所述color值，查询得到第一SRV6 policy；
    生成第二SRV6 policy，所述第二SRV6 policy的sidlist为所述第一SRV6 policy的sidlist；
    基于所述第二SRV6 policy和所述业务标签置，得到目标SRV6 policy。
  3. 根据权利要求2所述的方法，所述目标SRV6 policy的最后一层为所述业务标签。
  4. 根据权利要求1所述的方法，业务场景，包括如下场景中的至少一种：
    IPV4 H-VPN场景、IPV6 H-VPN场景、EVPN VPWS H-VPN场景、EVPN VPLS H-VPN场景。
  5. 根据权利要求4所述的方法，所述业务路由所属的业务场景为IPV4H-VPN场景时，选择第一SID类型；
    在所述业务路由所属的业务场景为IPV6 H-VPN场景时，选择第二SID类型；
    在所述业务路由所属的业务场景为EVPN VPWS H-VPN场景时，选择第三SID类型；
    在所述业务路由所属的业务场景为EVPN VPLS H-VPN场景时，选择第四SID类型。
  6. 根据权利要求1所述的方法，在所述第一设备为NPE设备的情况下，所述第二设备为UPE设备；在所述第一设备为UPE设备的情况下，所述第二设备为NPE设备。
  7. 根据权利要求1所述的方法，其中，将所述目标业务路由发送至第二设备，包括：
    通过update消息将所述目标业务路由发送至第二设备。
  8. 根据权利要求1所述的方法，所述update消息还携带如下属性中的至少一种：
    RT属性、目标SID类型的属性、color属性。
  9. 根据权利要求1所述的方法，所述方法还包括：
    通过IGP协议获取SRv6 SID对应的网段路由。
  10. 一种实现SRV6 policy网络H-VPN分层管理的装置，应用于SPE设备的BGP，所述装置包括：
    路由报文接收模块，被配置为接收第一设备发送的业务路由，所述业务路由携带业务标签和颜色color值；
    判断模块，被配置为基于所述业务路由所属的业务场景，在预设SID类型中选择目标SID类型；
    第一数据处理模块，被配置为根据所述color值和所述业务标签，生成目标SRV6 policy；
    第二数据处理模块，被配置为将所述目标SID类型和所述目标SRV6 policy关联，生成目标业务路由，所述目标业务路由中所述目标SID类型对应的SID的下一跳为所述目标SRV6 policy；
    数据发送模块，被配置为将所述目标业务路由发送至第二设备，以使所述第二设备根据所述目标业务路由中的地址查表转发。
  11. 一种电子设备，包括：
    存储器，用于存储指令；
    处理器，用于调用所述存储器中存储的指令，实现如权利要求1-9任一项所述的实现SRV6 policy网络H-VPN分层管理的方法。
  12. 一种计算机可读存储介质，其上存储有计算机指令，所述计算机指令被处理器执行时实现权利要求1-9中任意一项所述的实现SRV6 policy网络H-VPN分层管理的方法。
PCT/CN2023/111858 2022-08-11 2023-08-09 实现SRV6 policy网络H-VPN分层管理的方法、装置及相关设备 WO2024032636A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210964146.2 2022-08-11
CN202210964146.2A CN117640486A (zh) 2022-08-11 2022-08-11 实现SRV6 policy网络H-VPN分层管理的方法、装置、设备及介质

Publications (2)

Publication Number Publication Date
WO2024032636A1 true WO2024032636A1 (zh) 2024-02-15
WO2024032636A9 WO2024032636A9 (zh) 2024-04-04

Family

ID=89851005

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/111858 WO2024032636A1 (zh) 2022-08-11 2023-08-09 实现SRV6 policy网络H-VPN分层管理的方法、装置及相关设备

Country Status (2)

Country Link
CN (1) CN117640486A (zh)
WO (1) WO2024032636A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9106530B1 (en) * 2013-03-27 2015-08-11 Juniper Networks, Inc. Constrained route distribution for multiple virtual private network services
CN111786884A (zh) * 2019-04-04 2020-10-16 中兴通讯股份有限公司 一种路由方法及路由设备
WO2021258754A1 (zh) * 2020-06-22 2021-12-30 中兴通讯股份有限公司 报文指示方法、装置、设备和存储介质
WO2022068436A1 (zh) * 2020-09-30 2022-04-07 华为技术有限公司 业务处理方法以及相关设备
CN114827022A (zh) * 2021-01-18 2022-07-29 华为技术有限公司 路由消息处理方法、发布方法及装置、通信系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9106530B1 (en) * 2013-03-27 2015-08-11 Juniper Networks, Inc. Constrained route distribution for multiple virtual private network services
CN111786884A (zh) * 2019-04-04 2020-10-16 中兴通讯股份有限公司 一种路由方法及路由设备
WO2021258754A1 (zh) * 2020-06-22 2021-12-30 中兴通讯股份有限公司 报文指示方法、装置、设备和存储介质
WO2022068436A1 (zh) * 2020-09-30 2022-04-07 华为技术有限公司 业务处理方法以及相关设备
CN114827022A (zh) * 2021-01-18 2022-07-29 华为技术有限公司 路由消息处理方法、发布方法及装置、通信系统

Also Published As

Publication number Publication date
WO2024032636A9 (zh) 2024-04-04
CN117640486A (zh) 2024-03-01

Similar Documents

Publication Publication Date Title
CN106936777B (zh) 基于OpenFlow的云计算分布式网络实现方法、系统
US10320664B2 (en) Cloud overlay for operations administration and management
EP3780545B1 (en) Flow specification protocol-based communications method, and device
US8040822B2 (en) Configuring communication services using policy groups
US8661525B2 (en) Implementation method and system of virtual private network
WO2020200200A1 (zh) 路由方法及路由设备
EP4113919A1 (en) Method for forwarding message in srv6 service function chain, sff and sf device
WO2016066072A1 (zh) 实现nvo3网络与mpls网络之间通信的方法和装置
CN109155799A (zh) 经由层三通信的子网扩展
EP3742683B1 (en) Method and device for processing packet by using unified sr label stack
CN107770062A (zh) 一种数据包发送方法、装置及网络架构
CN111937358B (zh) 用于结构边缘设备的多vrf通用设备互联网协议地址
WO2015192501A1 (zh) 地址信息的发布方法及装置
EP3605959B1 (en) Method, device and computer storage medium for implementing double control plane
RU2528149C1 (ru) Способ коммутации туннеля и система сервисов многопротокольной коммутации по меткам
WO2022184169A1 (zh) 报文转发方法、系统、存储介质及电子装置
WO2022062679A1 (zh) 数据处理方法、系统、封装节点和解封装节点
JP6838760B2 (ja) トラフィックエンジニアリングサービスマッピング
CN101534210B (zh) 一种设置组播ip报文优先级的方法和设备
US20240039846A1 (en) Asymmetric Addressing For Limited Domains and Internet
WO2024032636A1 (zh) 实现SRV6 policy网络H-VPN分层管理的方法、装置及相关设备
CN108282404B (zh) 一种路由生成方法、装置及系统
WO2023082779A1 (zh) 报文转发方法、电子设备及存储介质
CN117640487A (zh) 实现srv6 be网络h-vpn分层管理的方法、装置、设备及介质
WO2024103806A1 (zh) 一种以太网段标识符处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 23851857

Country of ref document: EP

Kind code of ref document: A1