WO2020052230A1 - 一种传输控制方法、节点、网络系统及存储介质 - Google Patents

一种传输控制方法、节点、网络系统及存储介质 Download PDF

Info

Publication number
WO2020052230A1
WO2020052230A1 PCT/CN2019/082206 CN2019082206W WO2020052230A1 WO 2020052230 A1 WO2020052230 A1 WO 2020052230A1 CN 2019082206 W CN2019082206 W CN 2019082206W WO 2020052230 A1 WO2020052230 A1 WO 2020052230A1
Authority
WO
WIPO (PCT)
Prior art keywords
label
message
slice
identification information
node
Prior art date
Application number
PCT/CN2019/082206
Other languages
English (en)
French (fr)
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 中兴通讯股份有限公司
Priority to US17/274,912 priority Critical patent/US11700198B2/en
Priority to EP19860156.9A priority patent/EP3832957A4/en
Publication of WO2020052230A1 publication Critical patent/WO2020052230A1/zh

Links

Images

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
    • H04L12/4641—Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • H04L12/4645—Details on frame tagging
    • 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
    • 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
    • H04L12/4633—Interconnection of networks using encapsulation techniques, e.g. tunneling
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/30—Peripheral units, e.g. input or output ports
    • H04L49/3009—Header conversion, routing tables or routing tags
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing

Definitions

  • the embodiments of the present disclosure relate to, but are not limited to, a transmission control method, a node, a network system, and a computer-readable storage medium.
  • the core requirement of the 5G slice for the bearer network is that different slices need their own dedicated bearer subnetworks.
  • the different dedicated subnetworks can be either strict hard isolation of resources or soft isolation that achieves approximately hard isolation.
  • the packet network has never been designed to support hard isolation. It supports statistical multiplexing. It is more economical than a dedicated network or a TDM (Time Division Multiplex) network. It can be seen that in order to support 5G slicing requirements, the packet network needs to be underlayed. (Bottom layer) Network resources are sliced to meet the requirements of different overlay (upper layer) services, such as VPN (Virtual Private Network) services. At present, the industry has proposed a variety of 5G bearer network slicing technologies.
  • IGP Interior, Gateway, and Interior Gateway Protocol
  • IGP Interior, Gateway, and Interior Gateway Protocol
  • IGP Interior, Gateway, and Interior Gateway Protocol
  • At least one embodiment of the present disclosure provides a transmission control method, a node, a network system, and a computer-readable storage medium.
  • At least one embodiment of the present disclosure provides a transmission control method, including: a node encapsulates an upper-layer service identification information corresponding to the message in a message, and transmits the lower-layer network resource dedicated to the service corresponding to the upper-layer service identification information to transmit the The packet goes to the next hop.
  • An embodiment of the present disclosure provides a transmission control method including: when a node receives a message, the message is forwarded using a service-specific underlying network resource corresponding to the upper-layer service identification information carried in the message.
  • An embodiment of the present disclosure provides a node including a memory and a processor.
  • the memory stores a program, and when the program is read and executed by the processor, implements the transmission control method according to any one of the embodiments.
  • At least one embodiment of the present disclosure provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and the one or more programs can be executed by one or more processors to implement any The transmission control method according to an embodiment.
  • An embodiment of the present disclosure provides a network system including an ingress node, at least one intermediate node, and an egress node, wherein the ingress node is configured to encapsulate the upper-layer service identification information corresponding to the packet in a packet, and use the The service-specific underlying network resources corresponding to the upper-layer service identification information transmit the message to the next hop; the intermediate node is configured to, when receiving the message, use the corresponding to the upper-layer service identification information carried in the message.
  • the service-specific underlying network resources forward the message; the egress node is configured to forward the message using the service-specific underlying network resources corresponding to the upper-layer service identification information carried in the message when the message is received .
  • the node when a node receives a message, the node encapsulates the upper-layer service identification information corresponding to the message, and uses the service-specific information corresponding to the upper-layer service identification information.
  • the underlying network resources transmit the message to the next hop without the need to maintain complex IGP multi-topologies or multi-algorithm types to provide slicing, reducing overhead.
  • FIG. 1 is a flowchart of a transmission control method according to an embodiment of the present disclosure
  • FIG. 2 is a schematic diagram of a packet encapsulation format of a slice label provided by an embodiment of the present disclosure, followed by a direct IP address corresponding to an overlay service identifier;
  • 3a to 3c are schematic diagrams of an extended MPLS (Multiprotocol Label Switching) label protocol and an SR (Segment Routing) segment protocol;
  • MPLS Multiprotocol Label Switching
  • SR Segment Routing
  • 5 is a network topology diagram of specific embodiments 1 and 2 of the present disclosure.
  • FIG. 8 is a network topology diagram of a third embodiment of the present disclosure.
  • FIG. 10 is a network topology diagram of the fourth embodiment of the present disclosure.
  • FIG. 11 is a flowchart of a fourth embodiment of the present disclosure.
  • FIG. 12 is a block diagram of a node according to an embodiment of the present disclosure.
  • FIG. 13 is a block diagram of a storage medium according to an embodiment of the present disclosure.
  • FIG. 14 is a structural diagram of a network system according to an embodiment of the present disclosure.
  • slice-id is the key information for associating the overlay service with the underlay network resources. Therefore, this application proposes the concept of a slice label.
  • a slice label will associate the overlay service belonging to a specified slice with the underlay network resources. In addition, it enables the bearer network to more accurately identify massive services and provides QoS (Quality of Service) guarantee based on service classification.
  • the MPLS LSP Label Switched Path
  • the MPLS slice LSP will play a role of associating the slice overlay service with the slice-specific underlay network resource.
  • a loopback route of a node as a FEC (Forwarding Equivalence Class, Forwarding Equivalence Class) with a slice capability, called FEC with slice-capability (hereinafter referred to as slice FEC), and assign a slice FEC with The MPLS label with slice capability is called label with slice-capability (hereinafter referred to as slice label), and the binding relationship between the slice FEC and the slice label is notified to other nodes. Subsequent packet transmission is based on the slice label and the overlay service identifier.
  • FEC Forwarding Equivalence Class, Forwarding Equivalence Class
  • slice label label with slice-capability
  • an embodiment of the present disclosure provides a transmission control method, including:
  • Step 101 The node encapsulates the upper-layer (overlay) service identification information corresponding to the message in a message.
  • the message is generated by the node itself or received from other nodes (for example, a message received from a CE).
  • the upper-layer service identification information has a mapping relationship with an underlay network resource.
  • Step 102 The node transmits the message to a next hop by using a service-specific underlay network resource corresponding to the upper-layer service identification information.
  • the message transmitted in step 102 is a message in which the overlay service identification information is encapsulated in step 101.
  • the method described in this embodiment compared with the related art, it is not necessary to run a complex IGP multi-topology or multi-algorithm type to provide slices, which reduces the overhead.
  • the methods based on IGP multi-topology or IGP FlexAlgorithm technology all need to assign different MPLS labels to the same prefix FEC belonging to different topologies or different Flexe Algorithms, that is, to establish the same destination for different slices (that is, Multiple different MPLS LSPs with the same prefix (FEC).
  • FEC MPLS LSPs with the same prefix
  • the solution provided in this embodiment only needs to establish a single MPLS LSP with slice capability for different slices to the same destination, which greatly saves label resources and simplifies maintenance overhead.
  • the method described in this embodiment is applicable, for example, to a scenario where the virtual networks of all slices are homogeneous.
  • the overlay service identification information includes at least one of the following: slice-id, traffic engineering constraint indication information (color), where the slice-id will lock a slice, which is a large Service classification, which limits access to the underlay network resources of the target slice (that is, the slice indicated by the slice-id); and color will provide more refined flow classification within the slice, which is a smaller service classification under the large service classification.
  • the color in SR policy defined in draft-ietf-spring-segment-routing-policy-01 has the same meaning, and the value of color corresponds to a set of TE (Traffic Engineering) traffic constraints (such as bandwidth, delay, affinity, etc.). For example, a color of 0 indicates that there is no traffic engineering requirement for the overlay service, and a color of 0 indicates that the overlay service has traffic engineering demand.
  • This embodiment can provide finer classification of service flows and achieve more QoS level control.
  • the upper-layer service identification information corresponding to the message can be obtained from a VPN (Virtual Private Network) instance.
  • R1 receives a packet from the CE side that belongs to vpn-1 instance, that is, the packet is vpn-1, and vpn-1 belongs to slice-1.
  • a message is transmitted along an MPLS LSP, and when the message hits a corresponding FTN (FEC to NHLFE Map, forwarding equivalence class to next hop label forwarding unit mapping) entry on the ingress node of the MPLS
  • FTN FEC to NHLFE Map, forwarding equivalence class to next hop label forwarding unit mapping
  • the packet also encapsulates the overlay service identification information immediately after the slice label. That is, the encapsulation of the upper-layer service identification information corresponding to the message in the message includes:
  • a packaging position of the upper-layer service identification information in the label stack and a packaging position of the slice label in the label stack satisfy a preset relationship.
  • the upper-layer service identification information immediately follows the slice label in the label stack.
  • the upper-level service identification information may also be encapsulated in other agreed positions (for example, always immediately following the label at the bottom of the stack).
  • FIG. 2 is a schematic diagram of encapsulation of slice labels and upper-layer service identification information in an embodiment.
  • the label stack includes other labels (if possible), slice labels, upper-layer service identification information (slice-id + color), and payloads (IP, MPLS, etc.).
  • slice-id and color each occupy 16 bits.
  • the entire 32 bits may be used to represent slice-id or color.
  • the encapsulation and decapsulation of overlay service identification information in an MPLS packet must have a consistent understanding of its encapsulation format.
  • the upper-layer service identification information occupies 32 bits is only an example, and more or less bits may be used.
  • the method further includes, when the node receives a label binding announcement carrying preset information, establishing an FTN entry including a preset slice flag.
  • the preset slice flag may be set as required, and the preset slice flag is used to indicate that the FTN entry is a binding of a slice FEC and a slice label.
  • the preset information is used to indicate that the binding relationship between the slice FEC and the slice label is carried in the label binding announcement, and can be used to distinguish it from the FEC and the label in related technologies.
  • Label binding notification is used to announce the binding relationship between slice FEC and slice labels.
  • the carrying the preset information includes retaining an existing label binding notification message structure, and adding a preset flag therein.
  • the carrying the preset information includes: a type field in the Type Length Value (TLV) information in the label binding announcement is a preset value.
  • the preset value is different from the value of the type field in the tag TLV in the related art.
  • the label TLV is, for example, Slice TLabel TLV, which is similar to the existing Generic Label TLV, but some fields have different values, or Slice-Prefix-SID Sub-TLV, which is similar to the existing Prefix-SID Sub-TLV, but Some fields have different values, or they are Slice-Label-Index TLVs, similar to Label-Index TLVs, but some fields have different values.
  • the label binding announcement further includes encapsulation manner information of upper-layer service identification information
  • the FTN entry including the preset slice flag further includes encapsulation manner information of the upper-layer service identification information.
  • the encapsulated upper-layer service identification information includes:
  • the encapsulation method of the upper-layer service identification information is, for example, that the overlay service information is composed of a 16-bit slice-id and the low 16-bit color, or the overlay service information is composed of a 32-bit slice-id and the overlay service information Consists of 32-bit color, and so on.
  • the label binding announcement may not include the encapsulation mode of the upper-level service identification information, and in this case, the encapsulation is performed in a predefined manner.
  • Figure 3a is a specific implementation of extended label LDP to support slice FEC label binding information notification.
  • a new Slice Label TLV is added, which is completely similar to the existing Generic Label TLV, except that the TYPE is selected.
  • the value is TBD (TBD is a new value to be allocated that is not duplicated with the existing value, the same below), where the enc field indicates how the overlay service identification information is encapsulated (for example, a value of enc of 0 indicates that the overlay service information is 16-
  • the bit-id of the bit and the color of the lower 16-bit are only examples here. You can take other values as needed, or define more).
  • the interpretation of other fields is exactly the same as Generic Label TLV.
  • this embodiment provides The implementation method enables old devices that do not recognize SliceLabel and TLV to directly discard the received label binding information notification message of the slice FEC, while new devices that recognize SliceLabel and TLV will process and install entries normally.
  • Figure 3b is a specific implementation of label binding information announcement that extends ISIS to support slice FEC. It is based on draft-ietf-isis-segment-routing-extensions-16 and adds a slice-prefix -SID Sub-TLV is completely similar to the existing Prefix-SID Sub-TLV, except that the value of TYPE is TBD, and the Slice-Flag flag is added to the Flags field (for example, the value of the Slice-Flag flag can be 0 indicates that the overlay service information is composed of a high 16-bit slice-id and a low 16-bit color. This is just an example. Other values can be defined as required.
  • FIG. 3c is a specific implementation of the label binding information announcement of extended SR-BGP supporting slice FEC, which is based on draft-ietf-idr-bgp-prefix-sid-20 and adds a slice -Label-Index TLV, which is carried with the BGP Prefix-SID attribute, is completely similar to the existing Label-Index TLV, except that the TYPE value is TBD, and the Slice-Flag flag is added to the Flags field (for example, it can take a value 0 means that the overlay service information is composed of a high 16-bit slice-id and a low 16-bit color. This is just an example. Other values can be defined as required.
  • the encapsulating the slice label and the upper-layer service identification information in a label stack of the message according to the FTN entry hit by the message includes:
  • the slice label and the upper-layer service identification information are encapsulated in a tag stack of the message according to the hit FTN entry.
  • the encapsulating the upper-layer service identification information corresponding to the message in the message includes at least one of the following:
  • the newly defined routing extension header of the message carries the upper-layer service identification information corresponding to the message.
  • an embodiment of the present disclosure provides a transmission control method, including:
  • Step 401 When a node receives a message, it forwards the message using the service-specific underlying network resources corresponding to the upper-layer service identification information carried in the message.
  • the upper-layer service identification information is carried in a label stack of the message, and a position of the upper-layer service identification information in the label stack and an in-label mapping entry matched by the message are matched.
  • the position of the slice label in the label stack satisfies a preset relationship.
  • the upper-layer service identification information is carried in at least one of the following:
  • the node before forwarding the message by using the service-specific underlying network resources corresponding to the upper-layer service identification information carried in the message, the node further includes the entry label mapping entry according to the message hit.
  • Label exchange is performed, and when performing label exchange, the upper-layer service identification information in the label stack is retained.
  • the forwarding the message by using the service-specific underlying network resources corresponding to the upper-layer service identification information carried in the message includes:
  • the message is forwarded using the service-specific underlying network resources corresponding to the upper-layer service identification information carried in the message. This scheme is used to distinguish from existing transmission control schemes that do not carry an overlay service identifier.
  • the in-label mapping entry hit by the message does not include a preset slice flag, the message is forwarded according to an existing scheme.
  • the method further includes, when the node receives a label binding announcement carrying preset information, establishing an in-label mapping entry including the preset slice flag.
  • the label binding announcement containing preset information indicates that the current binding is a slice label and a slice FEC, and the one that does not contain preset information is not a binding of a slice label and a slice FEC.
  • the preset information may be an additional flag in addition to the tag TLV in the existing tag binding announcement, or the value of the Type field of the tag TLV in the tag binding announcement may be set to a preset value (the preset (The value is different from the value defined in the Type field of the tag TLV). Of course, the meaning of the existing value of the Type field can also be modified as the preset value.
  • An entry containing a preset slice flag indicates that the slice label and the slice FEC are currently bound.
  • An entry that does not include a preset slice flag is not a binding of the slice label and the slice FEC.
  • the method before using the service-specific underlying network resources corresponding to the upper-layer service identification information carried in the message to forward the message, the method further includes popping all the information according to the in-label mapping entry that the message hits. The corresponding slice label in the label stack of the message and the upper-level service identification information pop up.
  • the pop-up upper-layer service identification information in the tag stack includes:
  • the upper-layer service identification information in the label stack is popped up.
  • the method further includes that the node configures a forwarding equivalence class, assigns a slice label to the forwarding equivalence class, and creates an in-label mapping entry for the forwarding equivalence class, the in-label
  • the mapping table entry includes the preset slice flag.
  • the method further includes that the node sends a label binding announcement carrying preset information to other nodes, where the preset information is used to indicate that the current binding relationship is a forwarding equivalence class and a slice label. Binding relationship.
  • the label binding announcement sent by the node further includes information of an encapsulation manner of upper-layer service identification information.
  • the carrying preset information is: a type field in the tag type length value information in the tag binding announcement is a preset value.
  • the solution introduced in this application is applicable to the scenario where the vast majority of services use the shortest path forwarding to ensure their SLA (Service Level Agreement).
  • SLA Service Level Agreement
  • the user service quality is improved. Most of them are to provide sufficient bandwidth and delay guarantee along the shortest path through network planning. For example, when the bandwidth is insufficient, parallel links are added in time.
  • the network administrator makes RSVP-TE (Reservation, Protocol, and Engineering) resources reservation. (Remaining protocol traffic engineering) and even SR-TE (Segment Routing, Engineering, Segmentation Routing Traffic Engineering) dynamic TE path calculation results are concerned, this TE path is considered more uncontrollable, complex operation and maintenance.
  • RSVP-TE Resource Management
  • SR-TE Segment Routing, Engineering, Segmentation Routing Traffic Engineering
  • MPLS-TE LSP in the TE scenario, such as RSVP-TE LSP, SR-TE LSP, or MPLS Best-effort LSP in the non-TE scenario (best-effort forwarding based on the shortest path, referred to as MPLS-BE LSP)
  • MPLS-BE LSP MPLS Best-effort LSP
  • LDP Label Distribution Protocol
  • BGP Border Gateway Protocol
  • SR-BE SR Best-effort
  • This application describes an upgrade method, that is, to establish a single MPLS slice LSP to serve multiple different slices for a certain FEC, we call it MPLS-TE LSP with slice-capability, MPLS-BE LSP with slice-capability, such as this
  • MPLS slice LSP is not established for a specific slice, but it has the ability to carry slice information.
  • the forwarding information contained in this slice LSP is not related to the specific slice.
  • the overlay services of a specific slice can be carried on MPLS-TE LSP with slice-capability or MPLS-BE LSP with slice-capability, and of course, can also be carried on traditional MPLS-TE LSP or MPLS-BE LSP.
  • FEC Forwarding Equivalence Class
  • slicing slices-capability
  • slice label label with slice-capability
  • ILM Incoming Label Map
  • Node D can notify other nodes S of the binding relationship between the slice FEC and the corresponding slice label through label protocols such as LDP, BGP, and SR (herein referred to as SR-MPLS, that is, SR applies the MPLS forwarding plane), and S node receives After that, you can continue to assign MPLS labels to the slice FEC and create corresponding ILM entries.
  • the entry is marked with a preset slice flag, and the label operation is SWAP (Swap). Then the message that hits this ILM entry will be based on the message.
  • the overlay service identification information after the slice label in the label stack forwards the message using the service's dedicated underlay network resources; the S node can also create a corresponding FTN entry for the slice FEC, and the entry is marked with a preset slice flag, then hit this
  • the FTN entry packet also encapsulates the overlay service identification information (which can be encapsulated immediately after the slice label), and then forwards the message using the service-specific underlay network resources.
  • prefix-D the configuration for a certain loopback route
  • a slice FEC is a common prefix FEC, but it is marked with a preset slice flag. It is not a new type of FEC. For example, for LDP and BGP protocols, you can assign MPLS labels to the prefix-D as usual and create corresponding ones.
  • ILM entries marked with preset slice flags in ILM entries; for SR-MPLS protocols, such as ISIS (Intermediate System to Intermediate System), OSPF (Open Shortest Path Path First, Open Shortest Path (Priority Protocol) and BGP, as usual, prefix-D can be assigned prefix-sid (Segment ID, segment ID), corresponding ILM entries are created, and preset slice flags are also marked in the ILM entries.
  • ISIS Intermediate System to Intermediate System
  • OSPF Open Shortest Path First, Open Shortest Path (Priority Protocol)
  • BGP as usual
  • prefix-D can be assigned prefix-sid (Segment ID, segment ID), corresponding ILM entries are created, and preset slice flags are also marked in the ILM entries.
  • Node D serves as the egress node (ie, egress node) of the slice FEC, and the label operation in the ILM entry is POP and is marked with a preset slice flag.
  • a node When a node receives a packet that hits this ILM entry, it will pop off the top-level slice label in the label stack of the packet and the overlay service identification information immediately following the slice label, and then use the service corresponding to the overlay service identification information.
  • Dedicated underlay network resources process the message.
  • the overlay service identification information may include two parts: slice-id and color.
  • Node D announces the label binding message of the slice FEC to the neighbor node S through the MPLS label protocol.
  • MPLS label protocols such as LDP, BGP
  • SR routing protocols such as ISIS, OSPF, BGP
  • ISIS, OSPF, BGP SR routing protocols
  • the announcement of the label binding information of the sliced FEC may be supported by adding a preset flag to an existing FEC notification message (that is, the foregoing label binding announcement).
  • the preset flag may be the aforementioned preset slice flag, or may be another flag.
  • the value of the type field in the FEC notification message is set to a value different from the existing value, and the label binding information of the slice FEC is notified.
  • node S After receiving the label binding announcement of the slice FEC, node S can serve as a transit node (ie, an intermediate node) of the slice FEC, assign a slice label to the slice FEC, and create a corresponding ILM entry.
  • the entry is marked with a preset slice flag.
  • the label operation is SWAP.
  • Underlay network resources forward packets, in which the overlay service identification information in the packets is to be retained during forwarding; in some special scenarios, such as tracerout, the S node may receive the MPLS packet and find that the TTL of the top slice label times out, and perform FEC calibration according to RFC8029 During the verification and label verification, the overlay service identification information immediately after slicing the label should be ignored, and should not be mistaken for the label to affect the verification result.
  • Node S can also serve as the ingress node (that is, the ingress node) of the slice FEC, and create a corresponding FTN entry for the slice FEC.
  • the FTN entry is marked with a preset slice flag, and the node receives a report that hits the FTN entry.
  • the overlay service identification information is also encapsulated immediately after the slice label. Note that the overlay service identification information immediately after the slice label in the message cannot itself be regarded as a label, but as a whole with the slice label. It does not affect the setting of the EXP, TTL, and S fields of the slice label in the message.
  • each layer 3 interface resource will be divided into multiple layer 2 sub-interfaces that belong to different slices. For example, sub-if-1 configured for each layer 3 interface belongs to slice-1, sub-if- 2 belongs to slice-2, and sub-if-3 belongs to slice-3. Note that for the sake of concise network planning, no complicated configuration will be performed on each sub-interface, for example, no additional IP address will be configured on the sub-interface and the IGP or LDP protocol will be enabled.
  • the transmission control method provided in this embodiment includes:
  • Step 601 Establish an MPLS-BE slice LSP from node R1 to node R3 through LDP, where node R1 is an ingress node of the LSP, node R2 is a transit node, and node R3 is an egress node.
  • node R3 configures its loopback route (such as prefix-R3) as a slice FEC, and node R3 will allocate a slice label label3 for prefix-R3, and at the same time advertise the prefix-R3 and the upstream neighbor node R2 through LDP.
  • the binding relationship of the slice label label3 (including the SliceLabel TLV instead of the GenericLabel TLV in the notification message).
  • An ILM entry will be created on node R3, and the label operation of the ILM entry is POP.
  • the ILM entry is marked with a preset slice flag and indicates the role of the egress node.
  • step 602 after receiving the above label binding announcement from node R3, node R2 re-assigns label label2 to prefix-R3, and at the same time continues to announce the binding relationship between prefix-R3 and slice label label2 to upstream neighbor node R1 through LDP.
  • An ILM entry will be created on node R2.
  • the ILM entry contains a preset slice flag, the label operation is SWAP, which acts as the transit node role, the forwarding outbound interface is port3, and the outgoing label is label3.
  • step 603 after receiving the label binding notification from the node R2, the node R1 creates an FTN entry.
  • the FTN entry includes a preset slice flag, and serves as the role of the ingress node.
  • the outbound interface is port1, and the outbound label is label2.
  • the node R1 learns the VPN routes related to vpn-1, vpn-2, and vpn-3 services from the node R3 through BGP.
  • the VPN labels carried with the route advertisement are vpn-label1, vpn-label2, and vpn- label3, these VPN routes will be iterated according to the BGP next hop (R3) to the MPLS-BE slice LSP created by LDP, that is, the FTN entry created on node R1.
  • the packet supports the overlay service identification information of the VPN service when it is encapsulated.
  • the VPN route can provide its overlay service identification information when iterating over the public network MPLS LSP to map to a specific Underlay network resources.
  • the label stack encapsulated on node R1 for packets forwarded from CE1-1 to CE1-2 is:
  • a feasible implementation scheme of queue scheduling may be to use color as a queue scheduling factor to select a queue in which to place packets in the local queue resource of the port1.sub-if-1 sub-interface, or other schemes.
  • the overlay service identity is retained at this time.
  • the packets forwarded from CE2-1 to CE2-2 and the packets forwarded from CE3-1 to CE3-2 will be forwarded using slice-2 and slice-3 dedicated underlay network resources, respectively.
  • the overlay service identification information can be carried along the MPLS-BE slice LSP, which greatly improves the current EXP (or TC) field for MPLS packets that can only be based on the 3 bits in the packet label.
  • the 32-bit overlay service identification information ⁇ slice-id, color> can provide much finer traffic classification than the 3-bit EXP.
  • a node may serve as an ingress node, an intermediate node, and an egress node of different LSPs at the same time.
  • a node may have both FTN and ILM entries.
  • FIG. 5 The network structure of this embodiment is shown in FIG. 5.
  • This embodiment describes the establishment of SR-BE with slice-capability through IGP.
  • SR such as ISIS-SR
  • LDP MPLS-BE slice LSPs
  • Step 701 Establish an MPLS-BE slice LSP from node R1 to node R3 through the SR. For this reason, on node R3, configure its loopback route (such as prefix-R3) as a slice FEC and configure the corresponding slice-prefix-sid (such as sid3) for prefix-R3 within the SR function, and slice-prefix-sid will Flooded in the network with prefix-R3 (Slice-Prefix-SID Sub-TLV is included in the prefix flood message).
  • the node R3 will create an ILM entry (assuming that the absolute label label3 is converted based on the SRGB (SR Global Block Block Global Routing Block) conversion of sid3 and R3).
  • the label operation is POP.
  • the ILM entry is marked with a preset slice flag. And indicate the role of egress node.
  • Step 702 After receiving the prefix-R3 flood message from node R3, node R2 continues to flood node R1. At the same time, an ILM entry will be created on node R2 (assuming that the absolute label label2 is obtained based on the SRGB conversion of sid3 and node R2). The ILM entry contains a preset slice flag.
  • the label operation is SWAP, which serves as the transit node role.
  • the forwarding outbound interface is port3, with an output label of label3.
  • step 703 after receiving the prefix-3 flood message from node R2, node R1 creates an FTN entry, which contains a preset slice flag, and acts as the ingress node role.
  • the forwarding outbound interface is port1 and the outgoing label is label2.
  • step 704 the next packet forwarding process of the VPN service carried on the MPLS-BE slice LSP is similar to the first embodiment.
  • the node R1 learns from VPN R3 through BGP and learns about VPN-1, VPN-2, and VPN-3 services.
  • VPN routing Assume that the VPN labels carried with the route advertisement are vpn-label1, vpn-label2, and vpn-label3. These VPN routes will be iterated to the MPLS-BE created by LDP above based on the BGP next hop (R3).
  • Slice LSP that is, the FTN entry created on node R1. Because the FTN entry contains a preset slice flag, the packet supports the overlay service identification information of the VPN service when it is encapsulated.
  • the VPN route can provide its overlay service identification information when iterating over the public network MPLS LSP to map to a specific Underlay network resources. For example, the label stack encapsulated on node R1 for packets forwarded from CE1-1 to CE1-2 is:
  • a feasible implementation scheme of queue scheduling may be to use color as a queue scheduling factor to select a queue in which to place packets in the local queue resource of the port1.sub-if-1 sub-interface, or other schemes.
  • step 705 after receiving the message, node R2 hits the ILM entry according to the top label label2. Because the hit ILM entry has a preset slice flag, node R2 knows that the label2 in the message is followed by 32 bits.
  • the overlay in the packet is forwarded.
  • This embodiment is similar to the first embodiment.
  • IGP such as ISIS
  • LDP on the link (link1, link2, link3, link4).
  • link1 and link3 to belong to slice-1 and link2 and link4 to belong to slice-2.
  • L3VPN services there are two L3VPN services: vpn-1, vpn-2, R1 and R4 as PE (Provider Edge, Provider Edge Router) equipment.
  • PE Provider Edge, Provider Edge Router
  • R1 and R4 can advertise and learn VPN routes to each other through BGP. As shown in Figure 9, it includes:
  • Step 901 Establish an MPLS-BE slice LSP from node R1 to node R4 through LDP. For this reason, on node R4, configure its loopback route (such as prefix-R4) as a slice FEC, node R4 will assign prefix-R4 to label label4, and at the same time advertise prefix-R4 to upstream neighbor nodes R2 and R3 through LDP Binding relationship with slice label label4.
  • An ILM entry will be created on node R4, the label operation is POP, and the entry is marked with a preset slice flag, indicating that it plays the role of an egress node.
  • Step 902 After receiving the above-mentioned slice label notification from node R4, node R2 re-assigns label2 to prefix-R4, and at the same time continues to announce the binding relationship between prefix-R4 and slice label label2 to upstream neighbor node R1 through LDP.
  • An ILM entry will be created on node R2. The entry contains a preset slice flag, the label operation is SWAP, which acts as the transit node role, the forwarding outbound interface is link3, and the outgoing label is label4.
  • Node R3 also receives the above label binding notification from node R4, which is similar to the processing of node R2, re-assigns label3 to prefix-R4 and announces to upstream neighbor node R1.
  • the entry contains a preset slice flag.
  • the label operation is SWAP, which acts as the transit node role.
  • the forwarding outbound interface is link4 and the outgoing label is label4.
  • step 903 after receiving the above-mentioned label binding announcement of the node R2 and the node R3, the node R1 creates an FTN entry, which includes a preset slice flag as the role of the ingress node, and the forwarding information is "the outgoing interface is link1, the outgoing label ECMP (Equivalent Cost Multi-path Load Balancing) formed by "label2" and "outgoing interface is link2, and outgoing label is label3".
  • ECMP Equivalent Cost Multi-path Load Balancing
  • node R1 learns VPN-1 and vpn-2 service-related VPN routes from node R3 through BGP. Assuming that the VPN labels carried with the route advertisement are vpn-label1 and vpn-label2, these VPN routes will be According to the BGP next hop (node R4), the MPLS-BE slice LSP created through LDP, that is, the FTN entry created on node R1, is iterated. Because the FTN entry contains a preset slice flag, the packet can carry the VPN service identifier when it is encapsulated. The VPN route can provide its overlay service identifier information when iterating over the public network MPLS and LSP to map to specific underlay network resources. . For example, the label stack encapsulated on node R1 for packets forwarded from CE1-1 to CE1-2 is:
  • the label stack on node R1 for the packets forwarded from CE2-1 to CE2-2 is:
  • step 905 after receiving the message, the node R2 hits the ILM entry according to the top label label2. Because the ILM entry has a preset slice flag, the node R2 knows that the label2 in the message is followed by a 32-bit overlay service.
  • the overlay service identifier in the packet will not pop up when forwarding.
  • the node R3 exchanges the label label3 to label4 and forwards it to R4.
  • the overlay service identification information in the message will not pop up when forwarding.
  • Underlay network resources such as resources such as link4 and its queues in this embodiment.
  • This embodiment describes the establishment of SR-BE with slice-capability through BGP-LU, which is similar to the second embodiment, except that a cross-domain MPLS-BE slice LSP is established through BGP-LU.
  • PE1 and PE2 respectively Belonging to different ASs (autonomous systems), they will establish a BGP LSP across ASs and advertise and learn VPN routes to each other through BGP. IGP is reachable in each AS.
  • PE1 and PE2 are configured to assign the corresponding VRF instances vrf1 and vrf2 to slice-1, slice-2, slice-3, CE1-1 and CE1, respectively.
  • -2 is a customer of the vrf1 instance
  • CE2-1 and CE2-2 are customers of the vrf2 instance. As shown in Figure 11, it includes:
  • Step 1101 Establish an MPLS-BE slice LSP from node PE1 to node PE2 through BGP-LU.
  • node PE2 configure its loopback route (such as prefix-PE2) as a slice FEC, and node PE2 will assign prefix-PE2 to label-pe2, and at the same time advertise prefix-PE2 to the upstream neighbor ASBR2 through BGP.
  • the BGP Prefix-SID attribute carries the Slice-Label-Index TLV.
  • An ILM entry will be created on node PE2, and the label operation is POP. The entry is marked with a preset slice flag, and it indicates the role of the egress node.
  • step 1102 after receiving the prefix-PE2 routing advertisement of the node PE2, the node ASBR2 reassigns the label label-asbr2 to the prefix-PE2, and continues to advertise to the upstream neighbor ASBR1 through BGP.
  • An ILM entry will be created on node ASBR2.
  • the ILM entry contains a preset slice flag, the label operation is SWAP, which acts as the transit node role, the far-end next hop is node PE2, and the outgoing label is label-pe2.
  • step 1103 after receiving the prefix-PE2 routing advertisement sent by the node ASBR2, the node ASBR1 re-assigns the label label-asbr1 to the prefix-PE2, and continues to advertise to the upstream neighbor PE1 through BGP.
  • An ILM entry will be created on node ASBR1.
  • the ILM entry contains a preset slice flag.
  • the label operation is SWAP, which acts as a transit node.
  • the next hop is directly connected to node ASBR2.
  • the outbound interface is link0.
  • the outbound label is label-asbr2. .
  • step 1104 after receiving the prefix-PE2 routing advertisement sent by the node ASBR1, the node PE1 creates an FTN entry.
  • the FTN entry contains a preset slice flag, and serves as the ingress node role.
  • the remote next hop is the node ASBR1.
  • the label is label-asbr1.
  • node PE1 learns VPN-1 and vpn-2 service-related VPN routes from node PE2 through BGP. Assuming that the VPN labels carried with the route advertisement are vpn-label1 and vpn-label2, these VPN routes will be According to the BGP next hop (PE2), iterates to the MPLS-BE slice LSP created through the BGP-LU, that is, the FTN entry created on PE1. Because the FTN entry contains a preset slice flag, the packet can carry the VPN service identifier when it is encapsulated. The VPN route can provide its overlay service identifier information when iterating over the public network MPLS and LSP to map to specific underlay network resources. . For example, the label stack encapsulated on node PE1 for packets forwarded from CE1-1 to CE1-2 is:
  • the label stack on node PE1 for the packets forwarded from CE2-1 to CE2-2 is:
  • Step 1106 For the above-mentioned packet forwarded from CE1-1 to CE1-2, after the node ASBR1 receives the packet, the tunnel label of te-tunnel1 terminates, and the ILM entry is hit according to the top-level label label-asbr1.
  • the label operation type in the item is SWAP.
  • the label label-asbr1 is exchanged for label-asbr2 and then forwarded to the node ASBR2.
  • Network resources such as queue resources).
  • each te-tunnel in this embodiment may be replaced with an SR policy.
  • MPLS-TE LSP can also be upgraded to MPLS-TE LSP with slice-capability.
  • RFC3209 can be extended to newly define RSVP slice-path messages and slice-reserve messages, which are completely similar to the existing RSVP path message and reserve message usage methods, except that it indicates that the created LSP is an Slice the LSP.
  • the head node will send an RSVP slice-path message to the tail node along the TE path, and the tail node will respond to the RSVP slice-reserve message along the TE path in the opposite direction.
  • One RSVP-TE slice LSP One RSVP-TE slice LSP.
  • the forwarding behavior of the RSVP-TE slice LSP is similar to the MPLS-BE slice LSP described in the previous embodiment.
  • the RSVP-TE LSP label in the message is immediately followed by Overlay service identification information. The specific steps are not repeated here.
  • the SR-TE tunnel can be configured on the head node of the SR-TE tunnel as a tunnel with slicing capability.
  • SR-TE itself does not have a protocol process similar to RSVP-TE, and its forwarding information is generally a label stack consisting of multiple prefix-sid (or adjacency-sid corresponding labels).
  • ISIS protocol extension we new Slice-Prefix-SID Sub-TLV is defined to replace the existing Prefix-SID Sub-TLV.
  • the forwarding information of an SR-TE slice LSP will be composed of multiple slices prefix-sid (prefix-segment-identifier) or slice segment adjacency -sid (prefix adjacency segment identification) corresponding to the label stack.
  • prefix-segment-identifier prefix-segment-identifier
  • slice segment adjacency -sid prefix adjacency segment identification
  • Node R1 learns VPN-1, vpn-2, and vpn-3 service-related VPN routes from R3 through BGP.
  • the VPN labels carried with the route advertisement are vpn-label1, vpn-label2, and vpn-label3.
  • VPN routes can provide their overlay service identification information when iterating over public network MPLS and LSPs, which is used to map to specific underlay network resources.
  • label stack encapsulated on node R1 for packets forwarded from CE1-1 to CE1-2 is:
  • the label stack encapsulated by the message is:
  • the overlay service identifier may be carried only at the bottom of the label stack, that is, the label package encapsulated by the message is:
  • the solution provided by this application can also be applied to the IPv6 forwarding plane, draft-bashandy-isis-srv6-extensions-03, draft-ietf-6man-segment-routing-header-14 and draft-filsfils-spring-srv6- network-programming-05 describes how to apply SR technology to the IPv6 forwarding plane, referred to as SRv6 for short.
  • SRv6 an SRH (Segment Routing Header, Segment Routing Extension Header) is defined to encapsulate the Segment List.
  • the main Segment types are still Node Segment and Adjacency Segment.
  • the Segment List encapsulated in SRH can be a list consisting of 128-bit IPv6 addresses, a list consisting of a 32-bit SID index, or even a list consisting of a 32-bit MPLS Label.
  • the next segment needs to be obtained from the SRH one by one. If it is a node segment, it is converted into the corresponding IPv6 address and copied to the destination IP address field in the IPv6 header.
  • the shortest path is forwarded to the next Segment Node; if it is Adjacency, the segment will continue to obtain the next segment from the SRH and forwarded to the link corresponding to the Adjacency Segment.
  • the SRv6 TE tunnel (or SRv6 policy) can also be configured to have slicing capability and iterate to the SRv6TE tunnel VPN service packets when forwarding, the corresponding overlay
  • the service identification information can be encapsulated in the SRH. This can be a new sub-TLV in the SRH for storing the overlay service identification information.
  • a new routing extension header can be introduced (Routing Extension Header), which contains overlay service identification information (copied from the overlay service identification information stored in the SRH), and is used to instruct the packet to be forwarded by the shortest path between two adjacent Segment Nodes according to the forwarding resources of a specific slice.
  • the routing extension header can follow the IPv6 header, of course, it can also be located in other locations;
  • For the Adjacency segment forwarding support slice capability you can directly use the specific slice forwarding resources to the corresponding link according to the overlay service identification information stored in the SRH Forward. The specific forwarding process is not repeated here. Of course, for the Adjacency segment, it can also be forwarded to the corresponding link using the forwarding resources of a specific slice according to the overlay service identification information carried in the new routing extension header.
  • the overlay service identification information may be carried only in the routing extension header, and the overlay service identification information may not be carried in the SRH.
  • an embodiment of the present disclosure provides a node 120 including a memory 1210 and a processor 1220.
  • the memory 1210 stores a program, and the program is implemented by the processor 1220 when read and executed.
  • the transmission control method according to an embodiment.
  • an embodiment of the present disclosure provides a computer-readable storage medium 130.
  • the computer-readable storage medium storage 130 has one or more programs 1310, and the one or more programs 1310 may be A plurality of processors execute to implement the transmission control method according to any one of the embodiments.
  • an embodiment of the present disclosure provides a network system including an ingress node 1401, at least one intermediate node 1402, and an egress node 1403, where:
  • the ingress node 1401 is configured to encapsulate the upper-layer service identification information corresponding to the message in a message, and use the service-specific lower-layer network resources corresponding to the upper-layer service identification information to transmit the message to the next hop;
  • the intermediate node 1402 is configured to, when receiving a message, forward the message by using the service-specific underlying network resources corresponding to the upper-layer service identification information carried in the message;
  • the egress node 1403 is configured to forward the message using a service-specific underlying network resource corresponding to the upper-layer service identification information carried in the message when the message is received.
  • encapsulating the upper-layer service identification information corresponding to the message in the message by the ingress node 1401 includes encapsulating the upper-layer service identification information in a label stack of the message, and the The position of the upper-layer service identification information in the label stack and the position of the slice label in the FTN entry hit by the packet in the label stack satisfy a preset relationship.
  • the intermediate node 1402 and the egress node 1403 are further configured to send a label binding notification carrying preset information to other nodes, where the preset information is used to indicate that the current binding relationship is slice forwarding. Binding relationship between equivalence classes and slice labels;
  • the intermediate node 1402 is further configured to, upon receiving the label binding announcement carrying the preset information, establish an entry label mapping entry including a preset slice flag;
  • the ingress node 1401 is further configured to, upon receiving the label binding announcement carrying the preset information, establish an FTN entry including a preset slice flag.
  • computer storage medium includes volatile and non-volatile implemented in any method or technology used to store information such as computer-readable instructions, data structures, program modules or other data.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cartridges, magnetic tape, disk storage or other magnetic storage devices, or may Any other medium used to store desired information and which can be accessed by a computer.
  • a communication medium typically contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .
  • a transmission control method, node, network system, and storage medium provided by embodiments of the present invention have the following beneficial effects:
  • a node When a node receives a message, it encapsulates the upper-layer service corresponding to the message in the message.
  • the identification information uses the service-specific underlying network resources corresponding to the upper-layer service identification information to transmit the message to the next hop, without the need to maintain complex IGP multi-topologies or multi-algorithm types to provide slicing, which reduces overhead.

Landscapes

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

Abstract

本公开公开了一种传输控制方法、节点、网络系统及存储介质。该传输控制方法包括：节点在报文中封装所述报文对应的上层业务标识信息，使用所述上层业务标识信息对应的业务专属的底层网络资源传输所述报文至下一跳。

Description

一种传输控制方法、节点、网络系统及存储介质 技术领域
本公开实施例涉及但不限于一种传输控制方法、节点、网络系统及计算机可读存储介质。
背景技术
5G切片(slice)对承载网的核心需求，就是不同切片需要有其专属承载子网络，不同专属子网络可以是严格的资源硬隔离，也可以是达到近似硬隔离效果的软隔离。分组网络从来没有被设计成支持硬隔离，它支持的是统计复用，相比专网或TDM(Time Division Multiplex，时分复用)网络更加经济，可见为了支持5G切片需求，分组网络需要在underlay(底层)网络资源上做切片划分，以满足不同的overlay(上层)业务的需求，如VPN(Virtual Private Network，虚拟私有网络)业务。当前业界提出了多种5G承载网切片技术，比如有的采用IGP(Interior Gateway Protocol，内部网关协仪)多拓扑技术，将同一张物理网络拓扑划分成多张逻辑子拓扑，将不同的overlay业务归属至不同的逻辑子拓扑；还有的采用IGP Flex Algorithm(灵活算法)技术，在同一拓扑内运行多种IGP算法计算得到多种转发路径，将不同的overlay业务迭代到不同的转发路径。这些方法在本质上都是类似的，均需要在分组网络设备中维护多张IGP路由表，实施开销和成本很高。
发明内容
本公开至少一实施例提供了一种传输控制方法、节点、网络系统及计算机可读存储介质。
本公开至少一实施例提供一种传输控制方法，包括：节点在报文中封装所述报文对应的上层业务标识信息，使用所述上层业务标识信息对应的 业务专属的底层网络资源传输所述报文至下一跳。
本公开一实施例提供一种传输控制方法，包括：节点接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文。
本公开一实施例提供一种节点，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现任一实施例所述的传输控制方法。
本公开至少一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现任一实施例所述的传输控制方法。
本公开一实施例提供一种网络系统，包括入节点、至少一个中间节点和出节点，其中：所述入节点设置为，在报文中封装所述报文对应的上层业务标识信息，使用所述上层业务标识信息对应的业务专属的底层网络资源传输所述报文至下一跳；所述中间节点设置为，接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文；所述出节点设置为，接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文。
与相关技术相比，本公开至少一实施例中，节点接收到报文时，在所述报文中封装所述报文对应的上层业务标识信息，使用所述上层业务标识信息对应的业务专属的底层网络资源传输所述报文至下一跳，无需维护复杂的IGP多拓扑或者多算法类型来提供切片，降低了开销。
本公开的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本公开而了解。本公开的目的和其他优点可通过在说明书、权利要求书以及附图中所特别指出的结构来实现和获得。
附图说明
附图用来提供对本公开技术方案的进一步理解，并且构成说明书的一部分，与本申请的实施例一起用于解释本公开的技术方案，并不构成对本公开技术方案的限制。
图1为本公开一实施例提供的传输控制方法流程图；
图2为本公开一实施例提供的Slice label(切片标签)后直接跟随overlay业务标识相应IP地址的报文封装格式示意图；
图3a～图3c为扩展MPLS(Multiprotocol Label Switching，多协议标签交换)标签协议以及SR(Segment Routing，分段路由)协议的示意图；
图4为本公开一实施例提供的传输控制方法流程图；
图5是本公开具体实施例一、二的网络拓扑图；
图6为本公开具体实施例一的流程图；
图7为本公开具体实施例二的流程图；
图8为本公开具体实施例三的网络拓扑图；
图9为本公开具体实施例三的流程图；
图10为本公开具体实施例四的网络拓扑图；
图11为本公开具体实施例四的流程图；
图12为本公开一实施例提供的节点框图；
图13为本公开一实施例提供的存储介质框图；
图14为本公开一实施例提供的网络系统架构图。
具体实施方式
为使本公开的目的、技术方案和优点更加清楚明白，下文中将结合附图对本公开的实施例进行详细说明。需要说明的是，在不冲突的情况下，本申请中的实施例及实施例中的特征可以相互任意组合。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
相关技术中，需要在分组网络设备中维护多张IGP路由表，实施开销和成本很高。仔细考虑5G承载的关键诉求，就会发现让IGP运行的这么复杂没有必要，只需要通过某种简单的方式将overlay业务映射到其专属的underlay网络资源上即可，这些专属网络资源可以是三层接口、二层接口、队列、处理器等。在5G承载网络中，一个基本需求是underlay网络资源需要做切片划分，即一些underlay网络资源需要被配置专属的切片标识(slice-id)，另一个基本需求是overlay业务是专属切片内的业务，也会被配置其专属的slice-id。可见slice-id是关联overlay业务与underlay网络资源的关键信息，因此，本申请提出一种切片(slice)标签(label)的概念，切片标签将属于指定切片的overlay业务与underlay网络资源进行关联，另外还使得承载网络更精准的识别海量业务并提供基于业务分类的QoS(Quality of Service，服务质量)保障。基于切片标签通告和建立的MPLS LSP(Label Switched Path，标签交换路径)称为MPLS切片LSP，MPLS切片LSP将起到将切片的overlay业务与切片专属的underlay网络资源关联的作用。可以通过配置将节点的某个loopback路由作为一个具有切片能力的FEC(Forwarding Equivalence Class，转发等价类)，称为FEC with slice-capability(后文简称切片FEC)，并为该切片FEC分配具有切片能力的MPLS标签，称为label with slice-capability(后文简称为切片标签)，并将切片FEC与切片标签的绑定关系通告给其他节点。后续基于切片标签和overlay业务标识进行报文的传输。
如图1所示，本公开一实施例提供一种传输控制方法，包括：
步骤101，节点在报文中封装所述报文对应的上层(overlay)业务标识信息；
其中，所述报文是节点自身产生的，或者，从其他节点接收到的(比 如，从CE接收到的报文)。
其中，所述上层业务标识信息与底层(underlay)网络资源存在映射关系。
步骤102，所述节点使用所述上层业务标识信息对应的业务专属的底层(underlay)网络资源传输所述报文至下一跳。
其中，步骤102中传输的报文是步骤101中已封装overlay业务标识信息的报文。
采用本实施例所述方法，与相关技术相比，不需要运行复杂的IGP多拓扑或者多算法类型来提供切片，降低了开销。相关技术中，基于IGP多拓扑或者IGP Flex Algorithm技术的方法，均需要为属于不同的拓扑或者不同的Flexe Algorithm的相同prefix FEC分配不同的MPLS标签，即为不同的切片建立到相同目的地(即相同prefix FEC)的多条不同的MPLS LSP。相比之下，本实施例提供的方案只需要为不同的切片建立到相同目的地的单条具有切片能力的MPLS LSP，极大的节约了标签资源和简化了维护开销。本实施例所述的方法比如适用于所有切片的虚拟网络为同构的场景。
在一实施例中，所述overlay业务标识信息包括以下至少之一：切片标识(slice-id)、流量工程约束指示信息(color)，其中，slice-id将锁定一个切片，是一种大的业务分类，它限制了只能访问目标切片(即slice-id指示的切片)的underlay网络资源；而color将提供切片内更精细化的流分类，是大业务分类下的更小业务分类，与draft-ietf-spring-segment-routing-policy-01中定义的SR policy中的color含义相同，color取值对应一个TE(Traffic Engineering，流量工程)约束条件(如带宽、延迟、亲和力等)集合。比如，color为0表示overlay业务没有流量工程需求，color非0则表示overlay业务有流量工程需求。该实施例可以提供更精细的业务流分类，实现更多QoS等级控制。
其中，报文对应的上层业务标识信息可以从VPN(虚拟私有网络)实例中获取。比如，R1从属于vpn-1实例的CE侧接收到报文，即报文为vpn-1 的报文，而vpn-1归属于slice-1，当没有流量工程需求时，color＝0，此时overlay业务标识信息为slice-id＝1,color＝0。如果有流量工程需求，根据流量工程需求确定color值后得到overlay业务标识信息。
在一实施例中，报文沿MPLS LSP传输，该报文在MPLS LSP的入口节点上命中相应的FTN(FEC to NHLFE Map，转发等价类至下一跳标签转发单元映射)表项时，当FTN表项中包含有预设切片标志，则该报文中将除了封装所述报文命中的FTN表项中的切片标签，还紧随切片标签之后封装所述overlay业务标识信息。即，所述在所述报文中封装所述报文对应的上层业务标识信息包括：
根据所述报文命中的FTN表项在所述报文的标签栈中封装切片标签和所述上层业务标识信息。
在一实施例中，所述上层业务标识信息在所述标签栈中的封装位置与所述切片标签在所述标签栈中的封装位置满足预设关系。比如，所述上层业务标识信息在所述标签栈中紧随所述切片标签。需要说明的是，上层业务标识信息根据需要也可以封装在其他约定位置(比如始终紧随在栈底标签之后)。图2为一实施例中切片标签和上层业务标识信息的封装示意图。如图2所示，标签栈中包括其他标签(如果可能)、切片标签、上层业务标识信息(slice-id+color)、载荷(IP、MPLS等)。本实施例中，slice-id和color各占16比特。注意有些其它的具体实施方式可能会将整个32比特都用来表示slice-id或者color，不管怎样，在MPLS报文中封装与解封装overlay业务标识信息必须要对其封装格式理解一致。另外，上层业务标识信息占用32比特仅为示例，可以使用更多或更少比特。
在一实施例中，所述方法还包括，所述节点接收到携带预设信息的标签绑定通告时，建立包含预设切片标志的FTN表项。其中，所述预设切片标志可以根据需要设定，该预设切片标志是用于指示该FTN表项中是切片FEC和切片标签的绑定。所述预设信息是用于指示标签绑定通告中携带的是切片FEC和切片标签的绑定关系，可以用来和相关技术中的FEC 和标签进行区分。标签绑定通告是用来通告切片FEC和切片标签的绑定关系。
在一实施例中，所述携带预设信息包括，保留已有的标签绑定通告消息的架构，在其中增加预设标志。
在一实施例中，所述携带预设信息包括：所述标签绑定通告中的标签类型长度值(Type Length Value，简称TLV)信息中的类型字段为预设值。该预设值是不同于相关技术中的标签TLV中的类型字段的取值。标签TLV比如为Slice Label TLV，与已有的Generic Label TLV类似，但部分字段取值不一样，或者，为Slice-Prefix-SID Sub-TLV，与已有的Prefix-SID Sub-TLV类似，但部分字段取值不一样，或者，为Slice-Label-Index TLV，与Label-Index TLV类似，但部分字段取值不一样。当然，也可以自定义一种TLV格式来携带切片FEC与切片标签的绑定关系。
在一实施例中，所述标签绑定通告中还包括上层业务标识信息的封装方式信息，所述包含所述预设切片标志的FTN表项中还包括所述上层业务标识信息的封装方式信息；
所述封装上层业务标识信息包括：
根据所命中的FTN表项中的上层业务标识信息的封装方式信息在所述报文的标签栈中封装上层业务标识信息。其中，上层业务标识信息的封装方式比如为overlay业务信息由高16-bit的slice-id和低16-bit的color组成，或者，overlay业务信息由32-bit的slice-id组成，overlay业务信息由32-bit的color组成，等等。需要说明的是，标签绑定通告中也可以不包括上层业务标识信息的封装方式，此时采取预定义方式封装。
图3a是扩展LDP支持切片FEC的标签绑定信息通告的一种具体实施方式，是在RFC5036的基础上，新增一种Slice Label TLV，与已有的Generic Label TLV完全类似，只不过TYPE取值为TBD(TBD为待分配的与现有取值不重复的新值，下同)，其中enc字段指示overlay业务标识信息的封装方式(比如，enc取值0表示overlay业务信息由高16-bit的slice-id 和低16-bit的color组成，此处仅为示例，可以根据需要取其他值，或者，进行更多定义)，其它字段的解释与Generic Label TLV完全相同。通过这种引入新的Slice Label TLV的实现方式，与在现有的Generic Label TLV中扩展添加预设标志或者在现有的FEC TLV中扩展添加预设标志的实现方式相比，本实施例提供的实现方式，使得不识别Slice Label TLV的旧设备将直接丢弃所接收到的切片FEC的标签绑定信息通告消息，而能识别Slice Label TLV的新设备则正常处理并安装表项。
类似的，图3b是扩展ISIS支持切片FEC的标签绑定信息通告的一种具体实施方式，是在draft-ietf-isis-segment-routing-extensions-16的基础上，新增一种Slice-Prefix-SID Sub-TLV，与已有的Prefix-SID Sub-TLV完全类似，只不过TYPE取值为TBD，在Flags字段中新增Slice-Flag标志位(比如，Slice-Flag标志位可取值为0表示overlay业务信息由高16-bit的slice-id和低16-bit的color组成，此处仅为示例，可根据需要定义其他取值)，其它字段的解释与Prefix-SID Sub-TLV完全相同。通过这种引入新的Slice-Prefix-SID Sub-TLV的方式，与在现有的Prefix-SID Sub-TLV中扩展添加预设标志或者在现有的prefix通告(如TLV-135(Extended IPv4 reachability)定义于RFC5305，或TLV-235(Multitopology IPv4 Reachability)定义于RFC5120，或TLV-236(IPv6 IP Reachability)定义于RFC5308，或TLV-237(Multitopology IPv6 IP Reachability)定义于RFC5120)中扩展添加预设标志实现方式相比，本实施例中的实现方式，使得不识别Slice-Prefix-SID Sub-TLV的旧设备，将直接丢弃所接收到的切片FEC的标签绑定信息通告消息，而能识别Slice-Prefix-SID Sub-TLV的新设备则正常处理并安装表项。
类似的，图3c是扩展SR-BGP支持切片FEC的标签绑定信息通告的一种具体实施方式，是在draft-ietf-idr-bgp-prefix-sid-20的基础上，新增一种Slice-Label-Index TLV，随BGP Prefix-SID属性携带，与已有的Label-Index TLV完全类似，只不过TYPE取值为TBD，在Flags字段中新增Slice-Flag标志位(比如，可取值为0表示overlay业务信息由高16-bit的 slice-id和低16-bit的color组成，此处仅为示例，可根据需要定义其他取值)，其它字段的解释与Label-Index TLV完全相同。通过这种引入新的Slice-Label-Index TLV的方式，与在现有的Label-Index TLV中扩展添加切片标志或者在现有的prefix通告(如Labeled IPv4/IPv6 unicast prefixes定义于RFC8277，简称BGP-LU路由)中扩展添加预设标志的实现方式相比，本实施例提供的实现方式，使得不识别Slice-Label-Index TLV的旧设备将直接丢弃所接收到的切片FEC的标签绑定信息通告消息，而能识别Slice-Label-Index TLV的新设备则正常处理并安装表项。
其它MPLS标签协议(如BGP)以及SR路由协议(如OSPF)的扩展也按此兼容原则，不再赘述。
在一实施例中，所述根据所述报文命中的FTN表项在所述报文的标签栈中封装切片标签和所述上层业务标识信息包括：
当所述报文命中的FTN表项中包含预设切片标志时，根据所命中的FTN表项在所述报文的标签栈中封装切片标签和所述上层业务标识信息。
在一实施例中，所述在报文中封装所述报文对应的上层业务标识信息包括以下至少之一：
在所述报文的分段路由扩展头中封装所述报文对应的上层业务标识信息；
或者，在所述报文的新定义路由扩展头中携带所述报文对应的上层业务标识信息。
如图4所示，本公开一实施例提供一种传输控制方法，包括：
步骤401，节点接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文。
在一实施例中，所述上层业务标识信息在所述报文的标签栈中携带，且所述上层业务标识信息在所述标签栈中的位置与所述报文命中的入标签映射表项中的切片标签在所述标签栈中的位置满足预设关系。
在一实施例中，所述上层业务标识信息在以下至少之一携带：
所述报文的分段路由扩展头；
所述报文中新定义的路由扩展头。
在一实施例中，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文前还包括，所述节点根据所述报文命中的入标签映射表项进行标签交换，且进行标签交换时，保留所述标签栈中的所述上层业务标识信息。比如，标签栈中包括label1和slice-id＝1,color＝0，进行标签交换后，为label2和slice-id＝1,color＝0。
在一实施例中，所述使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文包括：
当所述报文命中的入标签映射表项中包括预设切片标志时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文。该方案用于与已有的不携带overlay业务标识的传输控制方案进行区分。当所述报文命中的入标签映射表项中不包括预设切片标志时，按已有方案转发所述报文。
在一实施例中，所述方法还包括，所述节点接收到携带预设信息的标签绑定通告时，建立包含所述预设切片标志的入标签映射表项。包含预设信息的标签绑定通告表示当前是切片标签和切片FEC的绑定，不包含预设信息的则不是切片标签和切片FEC的绑定。预设信息可以是在已有标签绑定通告中的标签TLV之外额外增加的一个标志，也可以是将标签绑定通告中的标签TLV的Type字段取值设置为预设值(该预设值不同于标签TLV中Type字段已进行定义的取值)，当然，也可以将Type字段的已有取值的含义修改后作为该预设值。包含预设切片标志的表项表示当前是切片标签和切片FEC的绑定，不包含预设切片标志的表项则不是切片标签和切片FEC的绑定。
在一实施例中，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文前还包括，根据所述报文命中的入标签 映射表项，弹出所述报文的标签栈中对应的切片标签以及弹出所述上层业务标识信息。
在一实施例中，所述弹出所述标签栈中的上层业务标识信息包括：
当所述报文命中的入标签映射表项中包括预设切片标志时，弹出所述标签栈中的上层业务标识信息。
在一实施例中，所述方法还包括，所述节点配置转发等价类，为所述转发等价类分配切片标签，为所述转发等价类创建入标签映射表项，所述入标签映射表项中包括所述预设切片标志。
在一实施例中，所述方法还包括，所述节点发送携带预设信息的标签绑定通告至其他节点，所述预设信息用于指示当前绑定关系为转发等价类与切片标签的绑定关系。
在一实施例中，所述节点发送的所述标签绑定通告中还包括上层业务标识信息的封装方式信息。
在一实施例中，所述携带预设信息为：所述标签绑定通告中的标签类型长度值信息中的类型字段为预设值。
本申请所介绍的方案适用于绝大多数业务都是通过最短路径转发来保证其SLA(Service Level Agreement，服务等级协定)的场景，在一些大型运营商的现网部署中，满足用户服务质量更多的是通过网络规划使得沿最短路径提供足够的带宽与时延保证，比如当带宽不够时及时增加平行链路，在这些网络中网络管理员对RSVP-TE(Resource Reservation Protocol Traffic Engineering，资源预留协议流量工程)乃至SR-TE(Segment Routing Traffic Engineering，分段路由流量工程)的动态TE路径计算结果都持担忧态度，这种TE路径更多的被认为是不可控、运维复杂。当然，本申请所介绍的方案也同样适用于TE场景。不管是TE场景下的MPLS-TE LSP，如RSVP-TE LSP、SR-TE LSP，还是非TE场景下的MPLS Best-effort LSP(基于最短路径尽力而为的转发，简称MPLS-BE LSP)，如LDP(Label Distribution Protocol，标签分发协议)LSP、BGP(Border Gateway Protocol， 边界网关协议)LSP、SR Best-effort(简称SR-BE)LSP，都可采用本申请所述的方法升级为MPLS切片LSP。本申请描述一种升级方法，即针对某个FEC建立单个MPLS切片LSP服务多个不同的切片，我们称之为MPLS-TE LSP with slice-capability、MPLS-BE LSP with slice-capability，即这样的MPLS切片LSP不是为具体某个切片建立的，但是它具有携带切片信息的能力，这类切片LSP所包含的转发信息与具体切片无关。根据隧道策略，特定切片的overlay业务可以承载在MPLS-TE LSP with slice-capability或MPLS-BE LSP with slice-capability，当然也可以承载在传统的MPLS-TE LSP或MPLS-BE LSP上。
1)对于MPLS-BE LSP with slice-capability的创建：
在MPLS网络内的某个节点D上，可以通过配置将其某个loopback路由作为一个具有切片能力的FEC(Forwarding Equivalence Class，转发等价类)，称为FEC with slice-capability(后文简称切片FEC)，并为该切片FEC分配具有切片能力的MPLS标签，称为label with slice-capability(后文简称为切片标签)，创建相应的ILM(Incoming Label Map，入标签映射)表项，该ILM表项中打上预设切片标志，则命中此ILM表项的标签报文将根据报文的标签栈中切片标签之后的overlay业务标识信息使用对应的underlay网络资源(即overlay业务标识信息指示的业务专属的underlay网络资源)处理报文。D节点可以通过标签协议，如LDP、BGP、SR(此处特指SR-MPLS，即SR应用MPLS转发平面)，向其它节点S通告切片FEC与相应切片标签的绑定关系，S节点收到后，可以继续为该切片FEC分配MPLS标签并创建相应的ILM表项，表项中打上预设切片标志，标签操作为SWAP(交换)，则命中此ILM表项的报文将根据报文的标签栈中切片标签之后的overlay业务标识信息使用该业务专属的underlay网络资源转发报文；S节点还可以为该切片FEC创建相应的FTN表项，表项中打上预设切片标志，则命中此FTN表项的报文除了封装切片标签以外，还封装overlay业务标识信息(可以紧随切片标签封装)，然后使用该业务专属的underlay网络资源转发报文。
2)对于MPLS-TE LSP with slice-capability的创建：
与MPLS-BE LSP with slice-capability的创建类似，只不过是在TE LSP的头节点上配置相应的TE FEC为具有切片能力的FEC，则头节点将触发建立一条MPLS-TE切片LSP。我们将在后续的具体实施例中讨论RSVP-TE和SR-TE两种情况。
本公开一实施例提供的MPLS切片标签的通告及其转发机制包括以下步骤：
对于MPLS-BE LSP with slice-capability的创建：
第一步
在MPLS网络内的某个节点D上，针对其某个loopback路由(记为prefix-D)配置将作它作为切片FEC。切片FEC就是普通的prefix FEC，只不过打上了预设切片标志，并不是一种新的FEC类型，比如：对于LDP、BGP协议来说，可以照常为该prefix-D分配MPLS标签，创建相应的ILM表项，在ILM表项中打上预设切片标志；对于SR-MPLS的协议，如ISIS(Intermediate System to Intermediate System，中间系统至中间系统协议)、OSPF(Open Shortest Path First，开放式最短路径优先协议)、BGP来说，可以照常为prefix-D分配prefix-sid(Segment ID，分段标识)，创建相应的ILM表项，同样也在ILM表项中打上预设切片标志。
节点D作为该切片FEC的egress节点(即出节点)，ILM表项中标签操作为POP且打上预设切片标志。节点接收到命中此ILM表项的报文时，将弹掉该报文的标签栈中顶层的切片标签以及该切片标签之后紧随的overlay业务标识信息，然后使用该overlay业务标识信息对应的业务专属的underlay网络资源处理该报文。其中，overlay业务标识信息可以包含两部分内容：slice-id和color。
第二步
节点D通过MPLS标签协议向邻居节点S通告切片FEC的标签绑定消息。
能支持通告prefix类型FEC的标签绑定消息的MPLS标签协议(如LDP、BGP)以及SR路由协议(如ISIS、OSPF、BGP)等，均可扩展以支持切片FEC的标签绑定信息的通告。
在一实施例中，切片FEC的标签绑定信息的通告可以在现有的FEC通告消息(即前述标签绑定通告)中增加预设标志的方式来支持。该预设标志可以是前述的预设切片标志，也可以是其他标志。在另一实施例中，将FEC通告消息中的类型字段的值设置为不同于已有取值的值，通告切片FEC的标签绑定信息。
节点S收到切片FEC的标签绑定通告后，可作为该切片FEC的transit节点(即中间节点)，为该切片FEC分配切片标签并创建相应的ILM表项，表项中打上预设切片标志，标签操作为SWAP。节点接收到命中此ILM表项的MPLS报文时，对报文的顶层切片标签做标签交换后，再根据报文中紧随切片标签之后的overlay业务标识信息使用overlay业务标识信息对应的业务专属的underlay网络资源转发报文，其中，转发时报文中的overlay业务标识信息要保留；有些特殊的场景如tracerout，S节点可能收到MPLS报文发现顶层切片标签的TTL超时，在按照RFC8029做FEC校验和标签校验时，切片标签后紧随的overlay业务标识信息应该要被忽略，不能误当成标签影响校验结果。
节点S还可以作为该切片FEC的ingress节点(即入节点)，为该切片FEC创建相应的FTN表项，该FTN表项中打上预设切片标志，则节点接收到命中此FTN表项的报文时，除了在所述报文中封装切片标签以外，还紧随切片标签之后封装overlay业务标识信息。注意报文中紧随切片标签之后封装的overlay业务标识信息，本身不能被当成label，而是与切片标签作为一个整体，它不影响报文中切片标签的EXP、TTL、S字段的设置。
具体实施例一
本实施例描述LDP LSP with slice-capability，如图5所示的MPLS承载网络，在各节点(R1、R2、R3)和三层接口(port1、port2、port3、port4)上使能IGP(如ISIS)和LDP。另外为了支持5G切片划分，各三层接口资源会被划分出多个二层子接口分属不同的切片，比如配置各三层接口的sub-if-1归属于slice-1，sub-if-2归属于slice-2，sub-if-3归属于slice-3。注意为了网络规划简洁起见，不会再对各子接口做复杂的配置，比如不会在子接口上额外配置IP地址以及使能IGP或LDP协议。假设有三个L3VPN(Layer 3 Virtual Private Network，三层虚拟私有网络)业务：vpn-1、vpn-2、vpn-3，节点R1和节点R3作为VPN接入设备，在节点R1和节点R3上配置将相应的VRF(Virtual Routing Forwarding，虚拟路由转发)实例vrf1、vrf2、vrf3分别归属到切片slice-1、slice-2、slice-3，CE1-1和CE1-2是vrf1实例的客户，CE2-1和CE2-2是vrf2实例的客户，CE3-1和CE3-2是vrf3实例的客户。节点R1和节点R3之间可以通过BGP相互通告和学习VPN路由。如图6所示，本实施例提供的传输控制方法包括：
步骤601，通过LDP建立一条从节点R1至节点R3的MPLS-BE切片LSP，其中节点R1为该LSP的ingress节点，节点R2为transit节点，节点R3为egress节点。为此，在节点R3点上，将其loopback路由(如prefix-R3)配置为切片FEC，节点R3将为prefix-R3分配入切片标签label3，同时通过LDP向上游邻居节点R2通告prefix-R3与切片标签label3的绑定关系(在通告消息中包含Slice Label TLV而不是Generic Label TLV)。节点R3上将创建ILM表项，该ILM表项的标签操作为POP，该ILM表项中打上预设切片标志，并表明作为egress节点角色。
步骤602，节点R2收到节点R3的上述标签绑定通告后，重新为prefix-R3分配入标签label2，同时继续通过LDP向上游邻居节点R1通告prefix-R3与切片标签label2的绑定关系。节点R2上将创建ILM表项，该ILM表项中包含预设切片标志，标签操作为SWAP即作为transit节点角色，转发出接口为port3，出标签为label3。
步骤603，节点R1收到节点R2的上述标签绑定通告后，创建FTN 表项，该FTN表项中包含预设切片标志，作为ingress节点角色，转发出接口为port1，出标签为label2。
步骤604，节点R1通过BGP从节点R3学习到vpn-1、vpn-2、vpn-3业务相关的VPN路由，假设随路由通告时携带的VPN标签分别为vpn-label1、vpn-label2、vpn-label3，这些VPN路由都将会根据BGP下一跳(R3)迭代到上述通过LDP创建的MPLS-BE切片LSP，即节点R1上创建的FTN表项。由于该FTN表项中含有预设切片标志，所以报文在封装时支持携带VPN业务的overlay业务标识信息，VPN路由在迭代公网MPLS LSP时可以提供其overlay业务标识信息，用于映射到特定的underlay网络资源。比如节点R1上针对从CE1-1向CE1-2转发的报文封装的标签栈为：
外层标签：label2
overlay业务标识：slice-id＝1,color＝0
内层标签：vpn-label1
节点R1在将报文向节点R2转发时，将会使用<slice-id＝1,color＝0>专属的underlay网络资源，比如本实施例中专属于slice-1的port1.sub-if-1子接口及其队列等资源。此时一种可行的队列调度实现方案可以是使用color作为队列调度因子在port1.sub-if-1子接口的局部队列资源中选择将报文入驻哪个队列，或者其它方案。
步骤605，节点R2收到报文后，根据顶层标签label2命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点R2知道报文中label2的后面紧跟的是32比特的overlay业务标识信息<slice-id＝1,color＝0>，于是节点R2根据所命中的ILM表项中的标签操作类型SWAP，将标签label2交换成label3后向节点R3转发，转发时报文中的overlay业务标识信息不会弹出，转发时将会使用<slice-id＝1,color＝0>专属的underlay网络资源，比如本实施例中的port3.sub-if-1子接口及其队列等资源。
此时标签栈为：
外层标签：label3
overlay业务标识：slice-id＝1,color＝0
内层标签：vpn-label1
此时保留了overlay业务标识。
步骤606，节点R3收到报文后，根据顶层标签label3命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点R3知道报文中label3的后面紧跟的是32比特的overlay业务标识<slice-id＝1,color＝0>，于是节点R3根据命中的ILM表项中的标签操作类型POP，将标签label3以及overlay业务标识信息弹出，然后继续根据vpn-label1以及私网IP载荷查表向CE1-2转发，此时转发时仍可使用<slice-id＝1,color＝0>确定面向CE1-2私网客户侧的网络资源(如队列资源等)。需要说明的是，也可以不使用<slice-id＝1,color＝0>对应的underlay网络资源转发所述报文。
类似的，从CE2-1向CE2-2转发的报文，以及从CE3-1向CE3-2转发的报文，将分别使用slice-2和slice-3专属的underlay网络资源转发。
从以上步骤可知，overlay业务标识信息能够沿MPLS-BE切片LSP转发时携带，极大的改善了当前对于MPLS报文只能根据报文的标签中的3个比特的EXP(或称TC)字段做QoS的缺陷，32个比特的overlay业务标识信息<slice-id,color>远比3个比特的EXP能提供更精细的流分类。
需要说明的是，节点可能同时充当不同LSP的入节点、中间节点和出节点。节点上可能既有FTN表项也有ILM表项。
具体实施例二
本实施例的网络结构如图5所示。本实施例描述通过IGP建立SR-BE with slice-capability，此例中使用SR(比如ISIS-SR)替代LDP去建立MPLS-BE切片LSP，如图7所示，包括：
步骤701，通过SR建立一条从节点R1至节点R3的MPLS-BE切片 LSP。为此，在节点R3上，将其loopback路由(如prefix-R3)配置为切片FEC以及在SR功能内为prefix-R3配置相应的slice-prefix-sid(如sid3)，slice-prefix-sid将随prefix-R3在网络内泛洪(在prefix泛洪消息中包含Slice-Prefix-SID Sub-TLV)。节点R3上将创建ILM表项(假设根据sid3和R3的SRGB(SR Global Block分段路由全局标签块)换算得到绝对标签label3)，标签操作为POP，该ILM表项中打上预设切片标志，并表明作为egress节点角色。
步骤702，节点R2收到节点R3的prefix-R3泛洪消息后，继续向节点R1泛洪。同时节点R2上将创建ILM表项(假设根据sid3和节点R2的SRGB换算得到绝对标签label2)，该ILM表项中包含预设切片标志，标签操作为SWAP即作为transit节点角色，转发出接口为port3，出标签为label3。
步骤703，节点R1收到节点R2的prefix-3泛洪消息后，创建FTN表项，表项中包含预设切片标志，作为ingress节点角色，转发出接口为port1，出标签为label2。
步骤704，接下来的VPN业务承载在上述MPLS-BE切片LSP的报文转发流程与具体实施例一类似，节点R1通过BGP从R3学习到vpn-1、vpn-2、vpn-3业务相关的VPN路由，假设随路由通告时携带的VPN标签分别为vpn-label1、vpn-label2、vpn-label3，这些VPN路由都将会根据BGP下一跳(R3)迭代到上述通过LDP创建的MPLS-BE切片LSP，即节点R1上创建的FTN表项。由于该FTN表项中含有预设切片标志，所以报文在封装时支持携带VPN业务的overlay业务标识信息，VPN路由在迭代公网MPLS LSP时可以提供其overlay业务标识信息，用于映射到特定的underlay网络资源。比如节点R1上针对从CE1-1向CE1-2转发的报文封装的标签栈为：
外层标签：label2
overlay业务标识：slice-id＝1,color＝0
内层标签：vpn-label1
节点R1在将报文向节点R2转发时，将会使用<slice-id＝1,color＝0>专属的underlay网络资源，比如本实施例中专属于slice-1的port1.sub-if-1子接口及其队列等资源。此时一种可行的队列调度实现方案可以是使用color作为队列调度因子在port1.sub-if-1子接口的局部队列资源中选择将报文入驻哪个队列，或者其它方案。
步骤705，节点R2收到报文后，根据顶层标签label2命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点R2知道报文中label2的后面紧跟的是32比特的overlay业务标识信息<slice-id＝1,color＝0>，于是节点R2根据所命中的ILM表项中的标签操作类型SWAP，将标签label2交换成label3后向节点R3转发，转发时报文中的overlay业务标识信息不会弹出，转发时将会使用<slice-id＝1,color＝0>专属的underlay网络资源，比如本实施例中的port3.sub-if-1子接口及其队列等资源。
步骤706，节点R3收到报文后，根据顶层标签label3命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点R3知道报文中label3的后面紧跟的是32比特的overlay业务标识<slice-id＝1,color＝0>，于是节点R3根据命中的ILM表项中的标签操作类型POP，将标签label3以及overlay业务标识信息弹出，然后继续根据vpn-label1以及私网IP载荷查表向CE1-2转发，此时转发时仍可使用<slice-id＝1,color＝0>确定面向CE1-2私网客户侧的网络资源(如队列资源等)。需要说明的是，也可以不使用<slice-id＝1,color＝0>对应的underlay网络资源转发所述报文。
具体实施例三
本实施例与具体实施例一类似，此例中我们以物理链路为单位划分到不同的切片，如图8所示，首先仍然在各节点(R1、R2、R3、R4)和三层链路(link1、link2、link3、link4)上使能IGP(如ISIS)和LDP。另外，配置link1和link3归属于slice-1，link2和link4归属于slice-2。假设有两 个L3VPN业务：vpn-1、vpn-2，R1和R4作为PE(Provider Edge，服务商边缘路由器)设备，在R1和R4上配置将相应的VRF实例vrf1、vrf2分别归属到切片slice-1、slice-2，CE1-1和CE1-2是vrf1实例的客户，CE2-1和CE2-2是vrf2实例的客户。R1和R4之间可以通过BGP相互通告和学习VPN路由。如图9所示，包括：
步骤901，通过LDP建立一条从节点R1至节点R4的MPLS-BE切片LSP。为此，在节点R4上，将其loopback路由(如prefix-R4)配置为切片FEC，节点R4将为prefix-R4分配入标签label4，同时通过LDP向上游邻居节点R2和节点R3通告prefix-R4与切片标签label4的绑定关系。节点R4上将创建ILM表项，标签操作为POP，表项中打上预设切片标志，并表明作为egress节点角色。
步骤902，节点R2收到节点R4的上述切片标签通告后，重新为prefix-R4分配入标签label2，同时继续通过LDP向上游邻居节点R1通告prefix-R4与切片标签label2的绑定关系。节点R2上将创建ILM表项，表项中包含预设切片标志，标签操作为SWAP即作为transit节点角色，转发出接口为link3，出标签为label4。
节点R3也收到节点R4的上述标签绑定通告，与节点R2的处理类似，重新为prefix-R4分配入标签label3并向上游邻居节点R1通告。创建ILM表项，表项中包含预设切片标志，标签操作为SWAP即作为transit节点角色，转发出接口为link4，出标签为label4。
步骤903，节点R1收到节点R2与节点R3的上述标签绑定通告后，创建FTN表项，表项中包含预设切片标志，作为ingress节点角色，转发信息为“出接口为link1，出标签为label2”与“出接口为link2，出标签为label3”形成的ECMP(Equivalent Cost Multi-path负载均衡)。
步骤904，节点R1通过BGP从节点R3学习到vpn-1、vpn-2业务相关的VPN路由，假设随路由通告时携带的VPN标签分别为vpn-label1、vpn-label2，这些VPN路由都将会根据BGP下一跳(节点R4)迭代到上 述通过LDP创建的MPLS-BE切片LSP，即节点R1上创建的FTN表项。由于该FTN表项中含有预设切片标志，所以报文在封装时支持携带VPN业务标识，VPN路由在迭代公网MPLS LSP时可以提供其overlay业务标识信息，用于映射到特定的underlay网络资源。比如节点R1上针对从CE1-1问CE1-2转发的报文封装的标签栈为：
外层标签：label2
overlay业务标识：slice-id＝1,color＝0
内层标签：vpn-label1
节点R1会将报文向节点R2转发，即使用<slice-id＝1,color＝0>专属的underlay网络资源，比如本实施例中专属于slice-1的link1及其队列等资源。即VPN路由在迭代至公网的ECMP转发信息时，根据overlay业务标识信息仅使用ECMP中属于相应切片的特定ECMP成员。
而节点R1上针对从CE2-1问CE2-2转发的报文封装的标签栈为：
外层标签：label3
overlay业务标识：slice-id＝2,color＝0
内层标签：vpn-label2
节点R1将报文向节点R3转发，使用<slice-id＝2,color＝0>专属的underlay网络资源，比如本实施例中专属于slice-2的link2及其队列等资源。
步骤905，节点R2收到报文后，根据顶层标签label2命中ILM表项，由于ILM表项中有预设切片标志，所以节点R2知道报文中label2的后面紧跟的是32比特的overlay业务标识信息<slice-id＝1,color＝0>，于是节点R2根据ILM表项中的标签操作类型SWAP，将标签label2交换成label4后向R4转发，转发时报文中的overlay业务标识不会弹出，转发时使用<slice-id＝1,color＝0>专属的underlay网络资源，比如本实施例中的link3及其队列等资源。
类似的，节点R3收到报文后，将标签label3交换成label4后向R4转发，转发时报文中的overlay业务标识信息不会弹出，转发时使用<slice-id＝2,color＝0>专属的underlay网络资源，比如本实施例中的link4及其队列等资源。
步骤906，节点R4从节点R2收到报文后，根据顶层标签label4命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点R4知道报文中label4的后面紧跟的是32比特的overlay业务标识信息<slice-id＝1,color＝0>，于是节点R4根据命中的ILM表项中的标签操作类型POP，将标签label4以及overlay业务标识弹出，然后继续根据vpn-label1以及私网IP载荷查表向CE1-2转发，此时转发时仍可使用<slice-id＝1,color＝0>确定面向CE1-2私网客户侧的网络资源。
类似的，节点R4从节点R3收到报文后，将标签label4以及overlay业务标识弹出，然后继续根据vpn-label2以及私网IP载荷查表向CE2-2转发，此时转发时仍可使用<slice-id＝2,color＝0>确定面向CE2-2私网客户侧的网络资源。
具体实施例四
本实施例描述通过BGP-LU建立SR-BE with slice-capability，与具体实施例二类似，只不过通过BGP-LU建立跨域的MPLS-BE切片LSP，如图10所示，PE1和PE2分别属于不同的AS(自治系统)，它们之间将建立一条跨AS的BGP LSP并通过BGP相互通告和学习VPN路由。各AS内均IGP可达。在AS1内，在te-tunnel1的头节点上配置te-tunnel1归属于slice-1，在te-tunnel2的头节点上配置te-tunnel2归属于slice-2；在AS2内，在te-tunnel3的头节点上配置te-tunnel3归属于slice-1，在te-tunnel4的头节点上配置te-tunnel4归属于slice-2。注意这些专属于某个切片的te-tunnel一般还满足overlay业务的相应流量工程需求(即具有与overlay业务一致的color)。配置域间链路link0可用于所有切片。假设有两个 L3VPN业务：vpn-1、vpn-2，在PE1和PE2上配置将相应的VRF实例vrf1、vrf2分别归属到切片slice-1、slice-2、slice-3，CE1-1和CE1-2是vrf1实例的客户，CE2-1和CE2-2是vrf2实例的客户。如图11所示，包括：
步骤1101，通过BGP-LU建立一条从节点PE1至节点PE2的MPLS-BE切片LSP。为此，在节点PE2上，将其loopback路由(如prefix-PE2)配置为切片FEC，节点PE2将为prefix-PE2分配入标签label-pe2，同时通过BGP向上游邻居ASBR2通告prefix-PE2，随BGP Prefix-SID属性携带Slice-Label-Index TLV。节点PE2上将创建ILM表项，标签操作为POP，表项中打上预设切片标志，并表明作为egress节点角色。
步骤1102，节点ASBR2收到节点PE2的上述prefix-PE2路由通告后，重新为prefix-PE2分配入标签label-asbr2，同时继续通过BGP向上游邻居ASBR1通告。节点ASBR2上将创建ILM表项，该ILM表项中包含预设切片标志，标签操作为SWAP即作为transit节点角色，远端下一跳为节点PE2，出标签为label-pe2。
步骤1103，节点ASBR1收到节点ASBR2发送的上述prefix-PE2路由通告后，重新为prefix-PE2分配入标签label-asbr1，同时继续通过BGP向上游邻居PE1通告。节点ASBR1上将创建ILM表项，该ILM表项中包含预设切片标志，标签操作为SWAP即作为transit节点角色，直连下一跳为节点ASBR2，出接口为link0，出标签为label-asbr2。
步骤1104，节点PE1收到节点ASBR1发送的上述prefix-PE2路由通告后，创建FTN表项，该FTN表项中包含预设切片标志，作为ingress节点角色，远端下一跳为节点ASBR1，出标签为label-asbr1。
步骤1105，节点PE1通过BGP从节点PE2学习到vpn-1、vpn-2业务相关的VPN路由，假设随路由通告时携带的VPN标签分别为vpn-label1、vpn-label2，这些VPN路由都将会根据BGP下一跳(PE2)迭代到上述通过BGP-LU创建的MPLS-BE切片LSP，即PE1上创建的FTN表项。由于该FTN表项中含有预设切片标志，所以报文在封装时支持携带VPN业 务标识，VPN路由在迭代公网MPLS LSP时可以提供其overlay业务标识信息，用于映射到特定的underlay网络资源。比如节点PE1上针对从CE1-1向CE1-2转发的报文封装的标签栈为：
外层标签：te-tunnel1的标签
次外层标签：label-asbr1
overlay业务标识：slice-id＝1,color＝100
内层标签：vpn-label1
节点PE1在将报文向节点ASBR1转发时，使用<slice-id＝1,color＝100>专属的underlay网络资源，比如本实施例中专属于slice-1的te-tunnel1资源。即VPN路由在迭代至公网BGP-LU路由时，根据overlay业务标识信息使得BGP-LU继续迭代至属于相应切片的外层隧道te-tunnel1。
而节点PE1上针对从CE2-1向CE2-2转发的报文封装的标签栈为：
外层标签：te-tunnel2的标签
次外层标签：label-asbr1
overlay业务标识：slice-id＝2,color＝200
内层标签：vpn-label2
节点PE1在将报文向节点ASBR1转发时，使用<slice-id＝2,color＝200>专属的underlay网络资源，比如本实施例中专属于slice-2的te-tunnel2资源。即VPN路由在迭代至公网BGP-LU路由时，根据overlay业务标识信息使得BGP-LU继续迭代至属于相应切片的外层隧道te-tunnel2。
步骤1106，针对上述从CE1-1向CE1-2转发的报文，节点ASBR1收到报文后，te-tunnel1的隧道标签终结，根据顶层标签label-asbr1命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点ASBR1知道报文中label-asbr1的后面紧跟的是32比特的overlay业务标识<slice-id＝1,color＝100>，于是节点ASBR1根据命中的ILM表项中的标签操作类型SWAP，将标签label-asbr1交换成label-asbr2后向节点ASBR2转发，转发 时报文中的overlay业务标识信息不会弹出，转发时将会使用<slice-id＝1,color＝100>专属的underlay网络资源，比如本实施例中多业务共享的link0接口及其队列等资源。
步骤1107，节点ASBR2收到报文后，根据顶层标签label-asbr2命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点ASBR2知道报文中label-asbr2的后面紧跟的是32比特的overlay业务标识信息<slice-id＝1,color＝100>，于是节点ASBR2根据ILM表项中的标签操作类型SWAP，将标签label-asbr2交换成label-pe2后向PE2转发，转发时报文中的overlay业务标识信息不会弹出，转发时将会使用<slice-id＝1,color＝100>专属的underlay网络资源，比如本实施例中专属于slice-1的te-tunnel3资源，即BGP-LU路由根据overlay业务标识信息迭代至属于相应切片的外层隧道te-tunnel3。
步骤1108，节点PE2收到报文后，te-tunnel3的隧道标签终结，根据顶层标签label-pe2命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点PE2知道报文中label-pe2的后面紧跟的是32比特的overlay业务标识信息<slice-id＝1,color＝100>，于是节点PE2根据命中的ILM表项中的标签操作类型POP，将标签label-pe2以及overlay业务标识弹出，然后继续根据vpn-label1以及私网IP载荷查表向CE1-2转发，此时转发时仍可使用<slice-id＝1,color＝100>确定面向CE1-2私网客户侧的网络资源(如队列资源等)。
类似的，针对上述从CE2-1向CE2-2转发的报文，节点ASBR1、ASBR2、PE2的处理与以上实现类似，不再赘述。
需要说明的是，在其他实施例中，本实施例中的各te-tunnel可以使用SR policy(策略)替代。
具体实施例五
实际上，如前文所述，MPLS-TE LSP也可以升级为MPLS-TE LSP with  slice-capability。
以传统的RSVP-TE协议为例，可以扩展RFC3209新定义RSVP slice-path消息与slice-reserve消息，与已有RSVP path消息和reserve消息的使用方法完全类似，只不过表明所创建的LSP是一条切片LSP。可以在RSVP-TE LSP的头节点上配置该LSP为切片LSP，则头节点将沿TE路径向尾节点发送RSVP slice-path消息，尾节点沿反方向TE路径回复RSVP slice-reserve消息，建立起一条RSVP-TE切片LSP。RSVP-TE切片LSP的转发行为与前述实施例中所述的MPLS-BE切片LSP类似，在报文转发沿RSVP-TE切片LSP转发时，报文中RSVP-TE LSP的标签之后紧跟的是overlay业务标识信息。具体步骤不再赘述。
以SR-TE tunnel(或SR policy)为例，可以在SR-TE tunnel的头节点上配置该SR-TE tunnel为具有切片能力的tunnel。SR-TE本身没有类似于RSVP-TE的协议过程，它的转发信息一般是由多个prefix-sid(或adjacency-sid对应的标签组成的标签栈，如前所述ISIS的协议扩展，我们新定义了Slice-Prefix-SID Sub-TLV替代现有的Prefix-SID Sub-TLV，类似的，我们也可以新定义Slice-Adj-SID sub-TLV/Slice-LAN-Adj-SID sub-TLV来替代Adj-SID sub-TLV/LAN-Adj-SID sub-TLV，那么一条SR-TE切片LSP的转发信息将是由多个slice prefix-sid(prefix-segment-identifier，前缀分段标识)或slice adjacency-sid(前缀邻接分段标识)对应的标签组成的标签栈，在报文沿SR-TE切片LSP转发时，每层slice prefix-sid或slice adjacency-sid对应的切片标签之后都紧跟overlay业务标识信息，每层切片标签都对应了一条SR-BE切片LSP，其转发行为与前述实施例中所述的MPLS-BE切片LSP是完全类似的。
比如，与具体实施例二类似，按照图5所示的网络，假设从R1上建立一条至R3的具有切片能力的SR-TE tunnel，其SID(Segment Identifier，分段标识)List(列表)为{Node-SID(for R2),Adjacency-SID(for R2-R3),Node-SID(for R3)}，其中包含的Node-SID与Adjacency-SID都是具有切片能力的SID，这样的SID list会根据SRGB信息翻译成标签栈，假设为 {label2(for R2),label23(for R2-R3),label3(for R3)}。节点R1通过BGP从R3学习到vpn-1、vpn-2、vpn-3业务相关的VPN路由，假设随路由通告时携带的VPN标签分别为vpn-label1、vpn-label2、vpn-label3，这些VPN路由都有流量工程路径转发的需求(比如vpn-1业务相关的VPN路由具有color＝100，vpn-2业务相关的VPN路由具有color＝200，vpn-3业务相关的VPN路由具有color＝300)，将会根据BGP下一跳(R3)和相应的隧道策略迭代到上述SR-TE tunnel，由于该SR-TE tunnel表项中含有预设切片标志，所以报文在封装时支持携带VPN业务的overlay业务标识信息，VPN路由在迭代公网MPLS LSP时可以提供其overlay业务标识信息，用于映射到特定的underlay网络资源。比如节点R1上针对从CE1-1向CE1-2转发的报文封装的标签栈为：
外层标签：label2(for R2)
overlay业务标识：slice-id＝1,color＝100
外层标签：label23(for R2-R3)
overlay业务标识：slice-id＝1,color＝100
外层标签：label3(for R3)
overlay业务标识：slice-id＝1,color＝100
内层标签：vpn-label1
节点R1在将报文向节点R2转发时，将会使用<slice-id＝1,color＝100>专属的underlay网络资源，比如本实施例中专属于slice-1的port1.sub-if-1子接口及其队列等资源。此时一种可行的队列调度实现方案可以是使用color作为队列调度因子在port1.sub-if-1子接口的局部队列资源中选择将报文入驻哪个队列，或者其它方案。
节点R2收到报文后，根据顶层标签label2命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点R2知道报文中label2的后面紧跟的是32比特的overlay业务标识信息<slice-id＝1,color＝100>，于是节点R2根据所命中的ILM表项中的标签操作类型POP，将标签label2以及紧 随其后的overlay业务标识信息弹出。然后继续根据label23查表命中ILM表项，同样由于命中的ILM表项中有预设切片标志，所以节点R2知道报文中label23的后面紧跟的是32比特的overlay业务标识信息<slice-id＝1,color＝100>，于是节点R2根据所命中的ILM表项中的标签操作类型SWAP(此时没有出标签可交换)，将标签label23以及紧随其后的overlay业务标识信息移除后向节点R3转发，转发时将会使用<slice-id＝1,color＝100>专属的underlay网络资源，比如本实施例中的port3.sub-if-1子接口及其队列等资源。报文封装的标签栈为：
外层标签：label3(for R3)
overlay业务标识：slice-id＝1,color＝100
内层标签：vpn-label1
节点R3收到报文后，根据顶层标签label3命中ILM表项，由于命中的ILM表项中有预设切片标志，所以节点R3知道报文中label3的后面紧跟的是32比特的overlay业务标识<slice-id＝1,color＝100>，于是节点R3根据命中的ILM表项中的标签操作类型POP，将标签label3以及overlay业务标识信息弹出，然后继续根据vpn-label1以及私网IP载荷查表向CE1-2转发，此时转发时仍可使用<slice-id＝1,color＝100>确定面向CE1-2私网客户侧的网络资源(如队列资源等)。需要说明的是，也可以不使用<slice-id＝1,color＝100>对应的underlay网络资源转发所述报文。
需要说明的是，在另一实施例中，也可以只在标签栈的栈底携带overlay业务标识，即报文封装的标签栈为：
外层标签：label2(for R2)
外层标签：label23(for R2-R3)
外层标签：label3(for R3)
内层标签：vpn-label1
overlay业务标识：slice-id＝1,color＝100。
该封装方式下，不需携带多个相同的overlay业务标识。
具体实施例六
实际上，在IPv6转发平面也可应用本申请提供的方案，draft-bashandy-isis-srv6-extensions-03、draft-ietf-6man-segment-routing-header-14与draft-filsfils-spring-srv6-network-programming-05描述了如何将SR技术应用于IPv6转发平面，简称为SRv6。在SRv6中定义了SRH(Segment Routing Header,分段路由扩展头)用于封装Segment List(分段列表)，主要的Segment类型仍然是Node Segment(节点分段)与Adjacency Segment(邻接分段)。SRH中封装的Segment List可以是由128比特IPv6地址组成的列表，也可以是由32比特SID索引组成的列表，甚至还可以是由32比特MPLS Label组成的列表等。不管是哪种情况，报文在沿Segment List逐段的转发时，需要逐个从SRH中获取下一个segment，如果是Node Segment则转换成相应的IPv6地址拷贝到IPv6header中的目的IP地址字段，按最短路径转发至下一个Segment Node(分段节点)；如果是Adjacency Segment则继续从SRH中获取下一个segment，向Adjacency Segment对应的链路转发。
与SR-MPLS的TE tunnel(或SR policy)类似的是，SRv6的TE tunnel(或SRv6 policy)也可以配置为具有切片能力，迭代到SRv6TE tunnel的VPN业务的报文在转发时，相应的overlay业务标识信息可以封装在SRH中，这可以在SRH中新扩展一种sub-TLV用于存放overlay业务标识信息。在此基础上：1)为了让Node Segment的在两相邻Segment Node之间(它们之间的节点可能是不具备SRv6能力的)的最短路径转发支持切片能力，可以引入一个新的路由扩展头(Routing Extension Header)，其中包含了overlay业务标识信息(拷贝自SRH中存放的overlay业务标识信息)，用于指示报文在两相邻Segment Node之间按照特定切片的转发资源进行最短路径转发，该路由扩展头可以紧随IPv6头，当然也可以 位于其他位置；2)对于Adjacency Segment的转发支持切片能力，可以直接根据SRH中存放的overlay业务标识信息使用特定切片的转发资源向相应的链路转发。具体转发过程不再赘述。当然，对于Adjacency Segment，也可以根据新的路由扩展头中携带的overlay业务标识信息使用特定切片的转发资源向相应的链路转发。
需要说明的是，在另一实施例中，可以只在路由扩展头中携带overlay业务标识信息，不在SRH中携带overlay业务标识信息。
如图12所示，本公开一实施例提供一种节点120，包括存储器1210和处理器1220，所述存储器1210存储有程序，所述程序在被所述处理器1220读取执行时，实现任一实施例所述的传输控制方法。
如图13所示，本公开一实施例提供一种计算机可读存储介质130，所述计算机可读存储介质存储130有一个或者多个程序1310，所述一个或者多个程序1310可被一个或者多个处理器执行，以实现任一实施例所述的传输控制方法。
如图14所示，本公开一实施例提供一种网络系统，包括入节点1401、至少一个中间节点1402和出节点1403，其中：
所述入节点1401设置为，在报文中封装所述报文对应的上层业务标识信息，使用所述上层业务标识信息对应的业务专属的底层网络资源传输所述报文至下一跳；
所述中间节点1402设置为，接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文；
所述出节点1403设置为，接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文。
在一实施例中，所述入节点1401在所述报文中封装所述报文对应的上层业务标识信息包括：在所述报文的标签栈中封装所述上层业务标识信息，且所述上层业务标识信息在所述标签栈中的位置与所述报文命中的FTN表项中的切片标签在所述标签栈中的位置满足预设关系。
在一实施例中，所述中间节点1402和所述出节点1403还设置为，发送携带预设信息的标签绑定通告至其他节点，所述预设信息用于指示当前绑定关系为切片转发等价类与切片标签的绑定关系；
所述中间节点1402还设置为，接收到携带所述预设信息的所述标签绑定通告时，建立包含预设切片标志的入标签映射表项；
所述入节点1401还设置为，接收到携带所述预设信息的所述标签绑定通告时，建立包含预设切片标志的FTN表项。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
工业实用性
如上所述，本发明实施例提供的一种传输控制方法、节点、网络系统 及存储介质具有以下有益效果：节点接收到报文时，在所述报文中封装所述报文对应的上层业务标识信息，使用所述上层业务标识信息对应的业务专属的底层网络资源传输所述报文至下一跳，无需维护复杂的IGP多拓扑或者多算法类型来提供切片，降低了开销。

Claims (26)

  1. 一种传输控制方法，包括：
    节点在报文中封装所述报文对应的上层业务标识信息，使用所述上层业务标识信息对应的业务专属的底层网络资源传输所述报文至下一跳。
  2. 根据权利要求1所述的传输控制方法，其中，所述上层业务标识信息包括以下至少之一：切片标识、流量工程约束指示信息。
  3. 根据权利要求1所述的传输控制方法，其中，所述在报文中封装所述报文对应的上层业务标识信息包括：
    根据所述报文命中的转发等价类至下一跳标签转发单元映射FTN表项在所述报文的标签栈中封装切片标签和所述上层业务标识信息。
  4. 根据权利要求3所述的传输控制方法，其中，所述上层业务标识信息在所述标签栈中的封装位置与所述切片标签在所述标签栈中的封装位置满足预设关系。
  5. 根据权利要求4所述的传输控制方法，其中，所述上层业务标识信息在所述标签栈中的封装位置与所述切片标签在所述标签栈中的封装位置满足预设关系包括：所述上层业务标识信息在所述标签栈中紧随所述切片标签。
  6. 根据权利要求3所述的传输控制方法，其中，所述根据所述报文命中的FTN表项在所述报文的标签栈中封装切片标签和所述上层业务标识信息包括：
    当所述报文命中的FTN表项中包含预设切片标志时，根据所命中的FTN表项在所述报文的标签栈中封装切片标签和所述上层业务标识信息。
  7. 根据权利要求6所述的传输控制方法，其中，所述方法还包括， 所述节点接收到标签绑定通告时，当所述标签绑定通告中携带预设信息时，建立包含所述预设切片标志的FTN表项。
  8. 根据权利要求7所述的传输控制方法，其中，所述携带预设信息包括：所述标签绑定通告中的标签类型长度值信息中的类型字段为预设值。
  9. 根据权利要求7所述的传输控制方法，其中，所述标签绑定通告中还包括上层业务标识信息的封装方式信息，所述包含所述预设切片标志的FTN表项中还包括所述上层业务标识信息的封装方式信息；
    所述封装上层业务标识信息包括：
    根据所命中的FTN表项中的上层业务标识信息的封装方式信息在所述报文的标签栈中封装上层业务标识信息。
  10. 根据权利要求1或2所述的传输控制方法，其中，所述在报文中封装所述报文对应的上层业务标识信息包括以下至少之一：
    在所述报文的分段路由扩展头中封装所述报文对应的上层业务标识信息；
    在所述报文的新定义路由扩展头中携带所述报文对应的上层业务标识信息。
  11. 一种传输控制方法，包括：
    节点接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文。
  12. 根据权利要求11所述的传输控制方法，其中，所述上层业务标识信息在所述报文的标签栈中携带，且所述上层业务标识信息在所述标签栈中的位置与所述报文命中的入标签映射表项中的切片标签在所述标签栈中的位置满足预设关系。
  13. 根据权利要求11所述的传输控制方法，其中，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文前还包括，所述节点根据所述报文命中的入标签映射表项进行标签交换，且进行标签交换时，保留所述标签栈中的所述上层业务标识信息。
  14. 根据权利要求11所述的传输控制方法，其中，所述使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文包括：
    当所述报文命中的入标签映射表项中包括预设切片标志时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文。
  15. 根据权利要求14所述的传输控制方法，其中，所述方法还包括，所述节点接收到携带预设信息的标签绑定通告时，建立包含所述预设切片标志的入标签映射表项。
  16. 根据权利要求11所述的传输控制方法，其中，
    使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文前还包括，根据所述报文命中的入标签映射表项，弹出所述报文的标签栈中对应的切片标签以及弹出所述上层业务标识信息。
  17. 根据权利要求16所述的传输控制方法，其中，所述弹出所述标签栈中的上层业务标识信息包括：
    当所述报文命中的入标签映射表项中包括预设切片标志时，弹出所述标签栈中的上层业务标识信息。
  18. 根据权利要求16所述的传输控制方法，其中，所述方法还包括，所述节点配置转发等价类，为所述转发等价类分配切片标签，为 所述转发等价类创建入标签映射表项，所述入标签映射表项中包括预设切片标志。
  19. 根据权利要求11所述的传输控制方法，其中，所述方法还包括，所述节点发送携带预设信息的标签绑定通告至其他节点，所述预设信息用于指示当前绑定关系为切片转发等价类与切片标签的绑定关系。
  20. 根据权利要求19所述的传输控制方法，其中，所述节点发送的所述标签绑定通告中还包括上层业务标识信息的封装方式信息。
  21. 根据权利要求15或19所述的传输控制方法，其中，所述携带预设信息为：所述标签绑定通告中的标签类型长度值信息中的类型字段为预设值。
  22. 一种节点，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求1至21任一所述的传输控制方法。
  23. 一种计算机可读存储介质，所述计算机可读存储介质存储有一个或者多个程序，所述一个或者多个程序可被一个或者多个处理器执行，以实现如权利要求1至21任一所述的传输控制方法。
  24. 一种网络系统，包括入节点、至少一个中间节点和出节点，其中：
    所述入节点设置为，在报文中封装所述报文对应的上层业务标识信息，使用所述上层业务标识信息对应的业务专属的底层网络资源传输所述报文至下一跳；
    所述中间节点设置为，接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文；
    所述出节点设置为，接收到报文时，使用所述报文中携带的上层业务标识信息对应的业务专属的底层网络资源转发所述报文。
  25. 根据权利要求24所述的网络系统，其中，所述入节点在所述报文中封装所述报文对应的上层业务标识信息包括：在所述报文的标签栈中封装所述上层业务标识信息，且所述上层业务标识信息在所述标签栈中的位置与所述报文命中的FTN表项中的切片标签在所述标签栈中的位置满足预设关系。
  26. 根据权利要求24或25所述的网络系统，其中，
    所述中间节点和所述出节点还设置为，发送携带预设信息的标签绑定通告至其他节点，所述预设信息用于指示当前绑定关系为切片转发等价类与切片标签的绑定关系；
    所述中间节点还设置为，接收到携带所述预设信息的所述标签绑定通告时，建立包含预设切片标志的入标签映射表项；
    所述入节点还设置为，接收到携带所述预设信息的所述标签绑定通告时，建立包含预设切片标志的FTN表项。
PCT/CN2019/082206 2018-09-14 2019-04-11 一种传输控制方法、节点、网络系统及存储介质 WO2020052230A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US17/274,912 US11700198B2 (en) 2018-09-14 2019-04-11 Transmission control method, node, network system and storage medium
EP19860156.9A EP3832957A4 (en) 2018-09-14 2019-04-11 TRANSMISSION CONTROL METHOD, NODE, NETWORK SYSTEM, AND STORAGE MEDIA

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811074914.7A CN110912795B (zh) 2018-09-14 2018-09-14 一种传输控制方法、节点、网络系统及存储介质
CN201811074914.7 2018-09-14

Publications (1)

Publication Number Publication Date
WO2020052230A1 true WO2020052230A1 (zh) 2020-03-19

Family

ID=69778151

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/082206 WO2020052230A1 (zh) 2018-09-14 2019-04-11 一种传输控制方法、节点、网络系统及存储介质

Country Status (4)

Country Link
US (1) US11700198B2 (zh)
EP (1) EP3832957A4 (zh)
CN (1) CN110912795B (zh)
WO (1) WO2020052230A1 (zh)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3968582A1 (en) * 2020-09-11 2022-03-16 Juniper Networks, Inc. Apparatus, system, and method for steering traffic over network slices
WO2022088951A1 (zh) * 2020-10-26 2022-05-05 中兴通讯股份有限公司 信息处理方法、基站、承载网设备、核心网设备及介质
EP4007235A1 (en) * 2020-11-30 2022-06-01 Huawei Technologies Co., Ltd. Route advertisement method, route generation method, and device
EP4009608A1 (en) * 2020-11-27 2022-06-08 Huawei Technologies Co., Ltd. Segment routing-based data transmission method and apparatus
CN115334589A (zh) * 2021-05-11 2022-11-11 中国移动通信有限公司研究院 报文传输方法、装置、相关设备及存储介质
EP4161002A4 (en) * 2020-07-06 2023-12-20 Huawei Technologies Co., Ltd. MESSAGE PROCESSING METHOD AND NETWORK DEVICE
EP4239973A4 (en) * 2020-11-27 2024-01-17 Huawei Technologies Co., Ltd. PACKET SENDING METHOD, DEVICE AND SYSTEM
EP4236245A4 (en) * 2020-11-27 2024-01-17 Huawei Technologies Co., Ltd. ROUTE ANNOUNCEMENT METHOD, APPARATUS AND SYSTEM
EP4203425A4 (en) * 2020-09-07 2024-02-07 Huawei Technologies Co., Ltd. MESSAGE TRANSFER METHOD, DEVICE AND SYSTEM
EP4239954A4 (en) * 2020-11-25 2024-04-10 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR COMMUNICATIONS, APPARATUS AND COMPUTER-READABLE STORAGE MEDIUM
EP4290812A4 (en) * 2021-03-02 2024-07-24 Huawei Tech Co Ltd PACKET TRANSMISSION METHOD AND APPARATUS

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109831382B (zh) * 2019-02-13 2020-08-14 华为技术有限公司 一种路径计算方法、装置及设备
CN115442295A (zh) * 2019-07-12 2022-12-06 华为技术有限公司 数据传输方法、网络节点及存储介质
CN113498084B (zh) * 2020-04-07 2022-07-29 烽火通信科技股份有限公司 一种层次化的基于切片的5g业务承载方法及系统
CN111541612B (zh) * 2020-04-21 2021-09-21 清华大学 一种发送、接收方法及其装置
CN111541613B (zh) * 2020-04-27 2022-03-22 鹏城实验室 一种基于SRv6的数据处理方法及相关设备
CN112187641B (zh) * 2020-06-24 2022-03-11 华为技术有限公司 一种路由信息发送方法、报文发送方法及相关装置
CN112491708A (zh) * 2020-10-15 2021-03-12 中兴通讯股份有限公司 IPv6报文的路由头封装方法及装置
CN114465920B (zh) * 2020-11-09 2024-04-12 华为技术有限公司 确定对应关系的方法、装置以及系统
CN114827022A (zh) * 2021-01-18 2022-07-29 华为技术有限公司 路由消息处理方法、发布方法及装置、通信系统
CN114844962A (zh) * 2021-02-02 2022-08-02 华为技术有限公司 一种报文处理方法及相关装置
CN114915584A (zh) * 2021-02-10 2022-08-16 华为技术有限公司 报文转发方法、装置及系统
CN115348202A (zh) * 2021-05-12 2022-11-15 中国移动通信有限公司研究院 基于网络切片的数据传输方法、装置、设备及存储介质
CN115484152A (zh) * 2021-06-16 2022-12-16 华为技术有限公司 信息处理的方法、装置以及系统
US11844012B2 (en) 2021-07-02 2023-12-12 Cisco Technology, Inc. Mapping and stitching network slices across various domains based on a border gateway protocol attribute
WO2023016566A1 (zh) * 2021-08-13 2023-02-16 中国移动通信有限公司研究院 资源分配方法、装置及网络节点
CN114205282B (zh) * 2021-12-08 2023-06-20 中国电信股份有限公司 SRv6 Policy的调度方法、系统、路由器和控制器
CN114205293B (zh) * 2021-12-20 2024-04-09 网络通信与安全紫金山实验室 路径确定方法、装置、电子设备及存储介质
CN114285794B (zh) * 2021-12-22 2023-08-18 网宿科技股份有限公司 报文转发控制方法、报文传输网络、电子设备及存储介质
CN117135643A (zh) * 2022-05-18 2023-11-28 中国移动通信有限公司研究院 资源配置方法、装置及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106550410A (zh) * 2015-09-17 2017-03-29 华为技术有限公司 一种通信控制方法和控制器、用户设备、功能实例
CN107517488A (zh) * 2016-06-15 2017-12-26 华为技术有限公司 报文处理的方法及设备
CN108307516A (zh) * 2016-09-30 2018-07-20 华为技术有限公司 数据传输方法及相关设备
US20180220276A1 (en) * 2017-01-27 2018-08-02 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network supporting virtual network customers

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104081719B (zh) * 2012-01-26 2017-12-15 西门子公司 在物理网络上控制应用的通信服务的控制器和方法
US9426068B2 (en) * 2012-02-24 2016-08-23 Futurewei Technologies, Inc. Balancing of forwarding and address resolution in overlay networks
US9838218B2 (en) * 2013-10-24 2017-12-05 Kt Corporation Method for providing overlay network interworking with underlay network and system performing same
US9369379B2 (en) * 2014-09-30 2016-06-14 Alcatel Lucent System and method providing secured contexts in MPLS LFIB
US9590902B2 (en) * 2014-11-10 2017-03-07 Juniper Networks, Inc. Signaling aliasing capability in data centers
EP3276892A4 (en) * 2015-03-24 2018-09-05 Nec Corporation Network system, network control method, and control device
CN106341832B (zh) * 2015-07-07 2020-11-06 中国移动通信集团公司 网络切片的管理及选择方法、系统、基站、路由交换设备
US10536946B2 (en) * 2015-12-08 2020-01-14 Huawei Technologies Co., Ltd. Method and system for performing network slicing in a radio access network
US11044203B2 (en) * 2016-01-19 2021-06-22 Cisco Technology, Inc. System and method for hosting mobile packet core and value-added services using a software defined network and service chains
US10686568B2 (en) * 2016-12-29 2020-06-16 Microsoft Technology Licensing, Llc Active flow diagnostics for cloud-hosted networks
CN111726286A (zh) * 2017-03-14 2020-09-29 华为技术有限公司 Evpn报文处理方法、设备及系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106550410A (zh) * 2015-09-17 2017-03-29 华为技术有限公司 一种通信控制方法和控制器、用户设备、功能实例
CN107517488A (zh) * 2016-06-15 2017-12-26 华为技术有限公司 报文处理的方法及设备
CN108307516A (zh) * 2016-09-30 2018-07-20 华为技术有限公司 数据传输方法及相关设备
US20180220276A1 (en) * 2017-01-27 2018-08-02 Huawei Technologies Co., Ltd. Method and apparatus for charging operations in a communication network supporting virtual network customers

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
HOMMA, SHUNSUKE: "Gateway Function for Network Slicing draft-homma-nfvrg-slice-gateway-00", 2 July 2018 (2018-07-02), pages 1 - 25, XP015127391, Retrieved from the Internet <URL:https://www.ietf.org/archive/id/draft-homma-nfvrg-slice-gateway-00.txt> *
See also references of EP3832957A4 *

Cited By (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4161002A4 (en) * 2020-07-06 2023-12-20 Huawei Technologies Co., Ltd. MESSAGE PROCESSING METHOD AND NETWORK DEVICE
EP4203425A4 (en) * 2020-09-07 2024-02-07 Huawei Technologies Co., Ltd. MESSAGE TRANSFER METHOD, DEVICE AND SYSTEM
EP3968582A1 (en) * 2020-09-11 2022-03-16 Juniper Networks, Inc. Apparatus, system, and method for steering traffic over network slices
WO2022088951A1 (zh) * 2020-10-26 2022-05-05 中兴通讯股份有限公司 信息处理方法、基站、承载网设备、核心网设备及介质
EP4236233A4 (en) * 2020-10-26 2024-04-10 ZTE Corporation INFORMATION PROCESSING METHOD, BASE STATION, CARRIER NETWORK DEVICE, CORE NETWORK DEVICE AND MEDIUM
EP4239954A4 (en) * 2020-11-25 2024-04-10 Huawei Technologies Co., Ltd. METHOD AND APPARATUS FOR COMMUNICATIONS, APPARATUS AND COMPUTER-READABLE STORAGE MEDIUM
EP4009608A1 (en) * 2020-11-27 2022-06-08 Huawei Technologies Co., Ltd. Segment routing-based data transmission method and apparatus
EP4239973A4 (en) * 2020-11-27 2024-01-17 Huawei Technologies Co., Ltd. PACKET SENDING METHOD, DEVICE AND SYSTEM
EP4236245A4 (en) * 2020-11-27 2024-01-17 Huawei Technologies Co., Ltd. ROUTE ANNOUNCEMENT METHOD, APPARATUS AND SYSTEM
EP4007235A1 (en) * 2020-11-30 2022-06-01 Huawei Technologies Co., Ltd. Route advertisement method, route generation method, and device
EP4290812A4 (en) * 2021-03-02 2024-07-24 Huawei Tech Co Ltd PACKET TRANSMISSION METHOD AND APPARATUS
CN115334589A (zh) * 2021-05-11 2022-11-11 中国移动通信有限公司研究院 报文传输方法、装置、相关设备及存储介质

Also Published As

Publication number Publication date
EP3832957A4 (en) 2022-05-04
CN110912795A (zh) 2020-03-24
US20220052945A1 (en) 2022-02-17
CN110912795B (zh) 2022-04-15
EP3832957A1 (en) 2021-06-09
US11700198B2 (en) 2023-07-11

Similar Documents

Publication Publication Date Title
WO2020052230A1 (zh) 一种传输控制方法、节点、网络系统及存储介质
US11936552B2 (en) Method and device for implementing VPN cross-domain, and border node
CN111385206B (zh) 报文转发的方法、网络系统、相关设备及计算机存储介质
US11689452B2 (en) Method for forwarding service data, network device, and network system
CN109863725B (zh) 基于最大分段标识符深度的分段路由方法及电子设备
US9912577B2 (en) Segment routing—egress peer engineering (SP-EPE)
US9306855B2 (en) System and method for using label distribution protocol (LDP) in IPv6 networks
US7006499B2 (en) Source identifier for MAC address learning
US8385341B2 (en) Ethernet frame broadcast emulation
WO2016066072A1 (zh) 实现nvo3网络与mpls网络之间通信的方法和装置
WO2016198015A1 (zh) 一种报文传输的方法、装置和系统
EP3488564B1 (en) Method for fast convergence in layer 2 overlay network and non-transitory computer readable storage medium
US11743166B2 (en) Provisioning non-colored segment routing label switched paths via segment routing policies in border gateway protocol
US11671352B2 (en) Message sending method, binding relationship advertising method, apparatus, and storage medium
WO2020107977A1 (zh) 一种路径构建的方法及相关设备
US20060203747A1 (en) Network topology systems and methods
WO2019205836A1 (zh) 一种数据报文转发的方法及装置
Radhakrishnan et al. Egress Engineering over BGP Label Unicast in MPLS-based Networks
WO2022042610A1 (zh) 信息处理方法、网络控制器、节点及计算机可读存储介质
Aron Design of MPLS networks VPN and TE with testing its resiliency and reliability

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: 19860156

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019860156

Country of ref document: EP

Effective date: 20210302

NENP Non-entry into the national phase

Ref country code: DE