WO2023236544A1 - 切片信息的验证方法及装置 - Google Patents

切片信息的验证方法及装置 Download PDF

Info

Publication number
WO2023236544A1
WO2023236544A1 PCT/CN2023/072696 CN2023072696W WO2023236544A1 WO 2023236544 A1 WO2023236544 A1 WO 2023236544A1 CN 2023072696 W CN2023072696 W CN 2023072696W WO 2023236544 A1 WO2023236544 A1 WO 2023236544A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
node
information
mpls
tlv
Prior art date
Application number
PCT/CN2023/072696
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 中兴通讯股份有限公司
Publication of WO2023236544A1 publication Critical patent/WO2023236544A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0893—Assignment of logical groups to network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/34—Source routing
    • 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]

Definitions

  • Embodiments of the present invention relate to the field of communications, and specifically, to a method and device for verifying slice information.
  • Segment Routing is a routing method based on source address, through the message header of the existing Multi-Protocol Label Switching (MPLS) network or Internet Protocol version 6 (InternetProtocol Version 6, IPv6) message header carries a segment routing header (Segment Routing Header, SRH).
  • the SRH carries a series of instruction operations (also called segment operations) for routing and transmission of data in the network.
  • the breakthrough concept of network slicing is proposed in the 5G network architecture.
  • operators can build multiple dedicated, virtualized, and isolated logical networks on a common physical platform to meet the different requirements of different customers for network capabilities.
  • Network slicing forms a logically independent virtual network structure through the combination of network functions.
  • Different network slices correspond to different resource guarantees and service levels. In particular, the difference in charging standards and operation and maintenance costs of different slices may be huge.
  • RFC8029 defines the basic MPLS LSP Ping/Trance route mechanism. This mechanism is widely used for MPLS path detection and fault location, but it is limited to verifying the prefix, link, notification protocol and other information associated with the SID. It lacks the verification of the associated slice identifier. mechanism.
  • Embodiments of the present invention provide a method and device for verifying slice information, so as to at least solve the problem of the lack of a verification mechanism for associated slice identification in related technologies.
  • a method for verifying slice information for a segment routing multi-protocol label switching SR-MPLS network, including: the initiating node sends a first message, wherein the first message carries Slice information to be verified is required so that the receiving node can verify whether the slice information carried in the first message is consistent with the local information of the receiving node.
  • a method for verifying slice information is also provided for a segment routing multi-protocol label switching SR-MPLS network, including: a receiving node receives the first message sent by the initiating node, and verifies the first message sent by the initiating node. Whether the slice information carried in the first message is consistent with the local information of the receiving node.
  • a device for verifying slice information for use in a segment routing multi-protocol label switching SR-MPLS network, including: an initiating module configured to send a first message, wherein: The first message carries slice information to be verified, so that the receiving node verifies whether the slice information carried in the first message is consistent with the local information of the receiving node.
  • a device for verifying slice information is also provided for use in a segment routing multi-protocol label switching SR-MPLS network, including: a receiving module configured to receive the first message sent by the initiating node, and verify the stated Whether the slice information carried in a message is consistent with the local information of the receiving node.
  • a computer-readable storage medium is also provided.
  • a computer program is stored in the computer-readable storage medium, wherein the computer program is configured to execute any of the above methods when running. Steps in Examples.
  • an electronic device including a memory and a processor.
  • a computer program is stored in the memory, and the processor is configured to run the computer program to perform any of the above. Steps in method embodiments.
  • Figure 1 is a hardware structure block diagram of a mobile terminal of a method for verifying slice information according to an embodiment of the present invention
  • Figure 2 is a flow chart of a method for verifying slice information according to an embodiment of the present invention
  • Figure 3 is a flow chart of a method for verifying slice information according to an embodiment of the present invention.
  • Figure 4 is a flow chart of a method for verifying slice information according to an embodiment of the present invention.
  • Figure 5 is a flow chart of a method for verifying slice information according to an embodiment of the present invention.
  • Figure 6 is a flow chart of a method for verifying slice information according to an embodiment of the present invention.
  • Figure 7 is a flow chart of a method for verifying slice information according to an embodiment of the present invention.
  • Figure 8 is a structural block diagram of a device for verifying slice information according to an embodiment of the present invention.
  • Figure 9 is a structural block diagram of a device for verifying slice information according to an embodiment of the present invention.
  • Figure 10 is a structural block diagram of a device for verifying slice information according to an embodiment of the present invention.
  • FIG. 11 is a schematic diagram of the MPLS echo request/reply message format according to an embodiment of the present invention.
  • Figure 12 is a flow chart of a slice information verification method according to a scenario embodiment of the present invention.
  • Figure 13 is a flow chart of a slice information verification method according to a scenario embodiment of the present invention.
  • Figure 14 is a schematic diagram of the sub-TLV format of IPv4 Prefix SID slice according to the scenario embodiment of the present invention.
  • Figure 15 is a schematic diagram of the sub-TLV format of IPv6 Prefix SID slice according to the scenario embodiment of the present invention.
  • Figure 16 is a schematic diagram of the sub-TLV format of the Adjacency SID slice according to the scenario embodiment of the present invention.
  • Figure 17 is a flow chart of a slice information verification method according to a scenario embodiment of the present invention.
  • Figure 18 is a schematic diagram of node networking according to the slice information verification method according to the scenario embodiment of the present invention.
  • Figure 19 is a schematic diagram of the initiating node sending messages according to the scenario embodiment of the present invention.
  • Figure 20 is a schematic diagram of the FEC TLV format according to a scenario embodiment of the present invention.
  • Figure 21 is a schematic diagram of node networking according to the slice information verification method according to the scenario embodiment of the present invention.
  • Figure 22 is a schematic diagram of node networking for specifying a reply path according to a scenario embodiment of the present invention.
  • Figure 23 is a schematic diagram of a node network for returning reverse slicing information to an initiating node according to a scenario embodiment of the present invention.
  • FIG. 1 is a hardware structure block diagram of a mobile terminal of a method for verifying slice information according to an embodiment of the present invention.
  • the mobile terminal may include one or more (only one is shown in Figure 1) processors 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the above-mentioned mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions.
  • processors 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA
  • a memory 104 for storing data
  • the above-mentioned mobile terminal may also include a transmission device 106 and an input and output device 108 for communication functions.
  • the structure shown in Figure 1 is only illustrative, and it does not limit the structure of the above-mentioned mobile terminal.
  • the mobile terminal may also include more or fewer components than shown in FIG. 1 , or have a different configuration than shown in FIG. 1 .
  • the memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the method for verifying slice information in the embodiment of the present invention.
  • the processor 102 runs the computer program stored in the memory 104, thereby Execute various functional applications and data processing, that is, implement the above methods.
  • Memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.
  • the memory 104 may further include memory located remotely relative to the processor 102, and these remote memories may be connected to the mobile terminal through a network. Examples of the above-mentioned networks include but are not limited to the Internet, intranets, local area networks, mobile communication networks and combinations thereof.
  • the transmission device 106 is used to receive or send data via a network.
  • Specific examples of the above-mentioned network may include a wireless network provided by a communication provider of the mobile terminal.
  • the transmission device 106 includes a network adapter (Network Interface Controller, NIC for short), which can be connected to other network devices through a base station to communicate with the Internet.
  • the transmission device 106 may be a radio frequency (Radio Frequency, RF for short) module, which is used to communicate with the Internet wirelessly.
  • NIC Network Interface Controller
  • FIG. 2 is a flow chart of a method for verifying slice information according to an embodiment of the present invention. As shown in Figure 2, the process includes the following steps :
  • Step S202 The initiating node sends a first message, wherein the first message carries slice information to be verified, so that the receiving node verifies that the slice information carried in the first message is consistent with the local location of the receiving node. Is the information consistent?
  • the initiating node sends a first message, wherein the first message carries slice information to be verified, so that the receiving node verifies that the slice information carried in the first message is consistent with the slice information of the receiving node. Whether the local information is consistent can solve the problem of the lack of verification associated slice identification mechanism in the SR-MPLS network, and achieve the effect of detecting and locating faults in the paths in the SR-MPLS slices.
  • the first message also carries a multi-protocol label switching MPLS echo request or MPLS echo response.
  • the method when the first message carries the MPLS loopback request, after the initiating node sends the first message, the method further includes: the initiating node receives the receiving node according to A second message returned from the verification result, and the verification result is confirmed according to the second message, where the second message includes an MPLS echo response.
  • Figure 3 is a flow chart of a method for verifying slice information according to an embodiment of the present invention. As shown in Figure 3, the process includes the following steps:
  • Step S302 The initiating node sends a first message, where the first message carries slice information to be verified, so that the receiving node verifies that the slice information carried in the first message is consistent with the local location of the receiving node. Whether the information is consistent;
  • Step S304 The initiating node receives the second message returned by the receiving node according to the verification result, and confirms the verification result according to the second message, where the second message includes an MPLS echo response.
  • FIG. 4 is a flow chart of a method for verifying slice information according to an embodiment of the present invention. As shown in Figure 4, the process includes the following steps:
  • Step S402 The initiating node receives the MPLS echo request message
  • Step S404 The initiating node sends a first message, where the first message carries slice information to be verified, so as to The receiving node verifies whether the slice information carried in the first message is consistent with the local information of the receiving node.
  • the initiating node when the first message also carries the MPLS loopback request, sends the first message, including: the initiating node sends the first message to Exit node; the initiating node receiving the second message returned by the exit node according to the verification result includes: the initiating node receiving and confirming the verification result from the exit node, and detecting whether the path is connected, wherein the verification result Query its own local table entry for the egress node to verify whether the slice IDs in the sub-TLV (Type type, Length length, Value value) of the Forwarding Equivalence Class (FEC) TLV are consistent with the local table entry. items consistent.
  • sub-TLV Type type, Length length, Value value
  • the above-mentioned MPLS echo request and echo response can contain multiple TLVs, such as FEC TLV and RP TLV, and one TLV can contain multiple sub-TLVs, that is, sub-TLVs.
  • the above-mentioned egress node is an egress node on a forwarding path.
  • the purpose of the initiating node sending the message is to reach the egress node. Whether the message can reach the egress node depends on factors such as the connectivity of the path.
  • the initiating node when the first message carries the MPLS loopback request, sends the first message, further including: the initiating node sending the first messages one by one to the The receiving node, the MPLS label of the slice information to be verified triggers the slice information verification of each of the receiving nodes, wherein the MPLS echo request contains the verification forwarding equivalence class FEC TLV, and the FEC TLV includes sub-TLV information and/ Or the TLV information of the downstream data mapping DDM, where the sub-TLV information includes the first slice information.
  • the above-mentioned receiving node may include only one receiving node or multiple receiving nodes. When the forwarding path has only one hop, then there will be only one receiving node.
  • the initiating node when the first message carries the MPLS echo response, sends the first message, including: the initiating node receives the MPLS echo request message, and the The MPLS echo request message contains the RP TLV.
  • the RP TLV contains the forwarding equivalence class FEC information of the reply path, where the FEC information includes the first slice information; the initiating node sends the first slice information through the reply path.
  • message wherein the reply path is matched by the receiving node according to the FEC information, the first message includes the MPLS label stack corresponding to the reply path and the MPLS echo response, and the MPLS echo response contains The RP TLV.
  • the search and matching can be performed by the tail node of the reply path, or by any receiving node that returns the verification result.
  • Matching that is, the receiving node that returns the verification result can search and match.
  • the initiating node sending the first message further includes: the initiating node receives an MPLS echo request message, and the R flag in the MPLS echo request message is set; The initiating node sends a first message, wherein the MPLS echo response in the first message carries a reverse path target forwarding equivalence class stack TLV, and the The reverse path target forwarding equivalence class stack TLV carries the first slice information.
  • the first message is sent by the initiating node, wherein the first message carries the slice information to be verified, so that the receiving node verifies the slice information carried in the first message. Whether it is consistent with the local information of the receiving node can solve the problem of lack of verification associated slice identification mechanism in the SR-MPLS network, achieving the effect of detecting and locating faults on paths in SR-MPLS slices.
  • a method for verifying slice information is also provided for use in a segment routing multi-protocol label switching SR-MPLS network.
  • Figure 5 is a flow chart of a method for verifying slice information according to an embodiment of the present invention. , as shown in Figure 5, the process includes the following steps:
  • Step S502 The receiving node receives the first message sent by the initiating node, and verifies whether the slice information carried in the first message is consistent with the local information of the receiving node.
  • the receiving node verifies whether the slice information carried in the first message is consistent with the local information of the receiving node needs to satisfy a trigger condition, wherein the trigger condition includes at least the following: One: The IP header contains the router alert option; the IP lifetime TTL has expired; the MPLS lifetime TTL has expired; the label is the MPLS router alert label; the destination IP is in the 127/8 range.
  • the first message also carries a multi-protocol label switching MPLS echo request or MPLS echo response.
  • the receiving node verifies that the slice information carried in the first packet is consistent with the local location of the receiving node. After determining whether the information is consistent, the method further includes: the receiving node returning a second message to the initiating node so that the initiating node can confirm the verification result, wherein the second message includes the MPLS echo response.
  • Figure 6 is a flow chart of a method for verifying slice information according to an embodiment of the present invention. As shown in Figure 6, the process includes the following steps:
  • Step S602 The receiving node receives the first message sent by the initiating node, and verifies whether the slice information carried in the first message is consistent with the local information of the receiving node;
  • Step S604 The receiving node returns a second message to the initiating node, so that the initiating node confirms the verification result, where the second message includes the MPLS echo response.
  • the receiving node returns the verification result to the initiating node for the initiating node to verify the The verification result is confirmed to confirm whether the first slice information has passed the verification.
  • Step S702 The receiving node receives the first message sent by the initiating node through the reply path; wherein the reply path is matched by the receiving node according to the forwarding equivalence class FEC information, and the first message includes The MPLS label stack and MPLS echo response corresponding to the reply path.
  • the MPLS echo reply includes the RP TLV.
  • the RP TLV includes the FEC information of the reply path, where the FEC information includes the first slice. information.
  • the receiving node receiving the first message sent by the initiating node further includes: the receiving node receiving the first message, wherein the MPLS in the first message
  • the echo response carries the reverse path target forwarding equivalence class stack TLV, and the reverse path target forwarding equivalence class stack TLV carries the first slice information.
  • the method according to the above embodiments can be implemented by means of software plus the necessary general hardware platform. Of course, it can also be implemented by hardware, but in many cases the former is Better implementation.
  • the technical solutions of the embodiments of the present invention can be embodied in the form of software products in essence or in part that contribute to the existing technology.
  • the computer software products are stored in a storage medium (such as ROM/RAM, magnetic disc, optical disk), including several instructions to cause a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in various embodiments of the present invention.
  • This embodiment also provides a device for verifying slice information, which is used to implement the above-mentioned embodiments and preferred implementations. What has already been described will not be described again.
  • the term "module” may be a combination of software and/or hardware that implements a predetermined function.
  • the apparatus described in the following embodiments is preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.
  • FIG 8 is a structural block diagram of a device for verifying slice information according to an embodiment of the present invention.
  • the verification device 80 includes: an initiating module 810, configured to send a first message, wherein the first message Slice information to be verified is carried so that the receiving node can verify whether the slice information carried in the first message is consistent with the local information of the receiving node.
  • Figure 9 is a structural block diagram of a device for verifying slice information according to an embodiment of the present invention.
  • the verification device 90 also includes: verification Module 910 is configured to receive and confirm the verification result from the egress node when the MPLS echo request is carried in the first message to detect Test whether the path is connected, wherein the verification result is that the egress node queries its own local entry, and verifies whether the slice IDs in the sub-TLVs of the forwarding equivalence class FEC TLV are consistent with those in the local entry.
  • the initiating module 810 when the first message carries the MPLS loopback request, is further configured to send the first messages to the receiving node one by one,
  • the slice information verification of each receiving node is triggered by setting the MPLS label associated with the slice information to be verified, wherein the MPLS echo request contains the verification forwarding equivalence class FEC TLV, and the FEC TLV contains sub-TLV information and/or
  • the downstream data maps the TLV information of the DDM, and the sub-TLV information includes the first slice information.
  • the initiating module 810 when the first message carries the MPLS echo response, is further configured to receive an MPLS echo request message, and the MPLS echo request message contains the RP TLV, the RP TLV contains the forwarding equivalence class FEC information of the reply path, wherein the FEC information contains the first slice information;
  • the initiating module 810 is further configured to: receive an MPLS echo request message, the R flag in the MPLS echo request message is set; and send a first message, wherein the first message is
  • the MPLS echo response in a message carries a reverse path target forwarding equivalence class stack TLV, and the reverse path target forwarding equivalence class stack TLV carries the first slice information.
  • the above-mentioned electronic device may further include a transmission device and an input-output device, wherein the transmission device is connected to the above-mentioned processor, and the input-output device is connected to the above-mentioned processor.
  • each module or each step of the above-mentioned embodiments of the present invention can be implemented by a general-purpose computing device. They can be concentrated on a single computing device, or distributed among multiple computing devices. over a network, they may be implemented with program code executable by a computing device, such that they may be stored in a storage device for execution by the computing device, and in some cases, may be executed in a sequence different from that described here.
  • the steps shown or described may be implemented by fabricating them separately into individual integrated circuit modules, or by fabricating multiple modules or steps among them into a single integrated circuit module. As such, the invention is not limited to any specific combination of hardware and software.
  • the identity (ID) of a network slice can be referred to as a slice identifier or a slice ID for short, and is used to identify the network slice.
  • the slice ID is also called Network Resource Partition Policy ID (NRP-ID). This article uses slice identifiers to refer to them.
  • the slice identifier can have different meanings and forms. As long as an identifier can be uniquely distinguished within a specific range (such as a physical port/link, the same IGP domain, the entire network range, etc.) Slices or resources can be viewed as slice identifiers.
  • SID MPLS label
  • SID A is associated with slice ID 1
  • SID B is associated with slice ID 2
  • SID A is associated with slice ID 1
  • SID B is associated with slice ID 2
  • RFC8029 defines the basic MPLS LSP Ping/Trance route mechanism. This mechanism is widely used for MPLS path detection and fault location. It is mainly based on the MPLS echo request/reply message. This message is a UDP message. The format is shown in Figure 11. Show.
  • RFC8287 defines the LSP Ping/Traceroute mechanism in SR-MPLS scenarios. However, it is limited to verifying the prefix, link, notification protocol and other information associated with the SID, and lacks a mechanism to verify the associated slice identifier.
  • FIG 12 is a flow chart of a slice information verification method according to a scenario embodiment of the present invention. The method is used in an SR-MPLS network. As shown in Figure 12, the process includes the following steps:
  • Step S1202 The initiating node sends a first message, which contains the MPLS label stack and slice information to be verified.
  • the first message may contain an MPLS echo request (echo request), and the slice information to be verified is included in the FEC TLV in the form of a sub-TLV and is carried in the echo request; the first message may contain an MPLS echo reply.
  • the slice information to be verified is included in the Reply Path TLV in the form of sub-TLV and carried in the echo reply;
  • the first message may contain an MPLS echo reply
  • the slice information to be verified is included in the Reverse-path Target FEC Stack TLV in the form of a sub-TLV and is carried in the echo reply.
  • Step S1204 After the receiving node receives the first message, if the trigger condition is met, it enters the verification process to verify whether the slice information carried in the first message is consistent with the local information of the node.
  • the triggering conditions include but are not limited to one of the following conditions specified in RFC8029:
  • the IP header contains the Router Alert option
  • IP survival time TTL expiration IP TTL expiration
  • MPLS lifetime TTL expiration (MPLS TTL expiration);
  • the label is MPLS Router Alert label
  • the destination IP is in the 127/8 range.
  • the first message received is not necessarily exactly the same as the one sent, and may have undergone operations such as MPLS label stripping and switching.
  • FIG. 13 is a flow chart of the slice information verification method according to the scenario embodiment of the present invention. As shown in Figure 13, when the first message contains MPLS echo reply, the process includes the following steps:
  • Step S1302 the initiating node receives the MPLS echo request message
  • Step S1304 The initiating node sends a first message, which contains the MPLS label stack and slice information to be verified.
  • Figure 14 is a schematic diagram of the sub-TLV format of IPv4 Prefix SID slice according to the scenario embodiment of the present invention.
  • Figure 15 is a schematic diagram of the sub-TLV format of IPv6 Prefix SID slice according to the scenario embodiment of the present invention.
  • Figure 16 is a schematic diagram of the sub-TLV format of the Adjacency SID slice according to the scenario embodiment of the present invention.
  • the slice information does not need to be verified.
  • the sub-TLV may also carry content to be verified, including but not limited to, the prefix associated with the SID, the link, the protocol through which the SID is advertised, and the service Function (service function), algorithm, multi-topology (Multi-Topology) and other information.
  • Figure 17 is a flow chart of a slice information verification method according to a scenario embodiment of the present invention. As shown in Figure 17, when the first message contains an echo request, the process includes the following steps:
  • Step S1702 The initiating node sends a first message, which contains the MPLS label stack and slice information to be verified.
  • the first message may contain an MPLS echo request (echo request), and the slice information to be verified is included in the FECTLV in the form of a sub-TLV and is carried in the echo request;
  • the first message may contain an MPLS echo reply, and the slice information to be verified is included in the echo request.
  • the verified slice information is included in the Reply Path TLV in the form of sub-TLV and carried in the echo reply;
  • the first message may contain an MPLS echo reply
  • the slice information to be verified is included in the Reverse-path Target FEC Stack TLV in the form of a sub-TLV and is carried in the echo reply.
  • Step S1704 After the receiving node receives the first message, if the trigger condition is met, it enters the verification process to verify whether the slice information carried in the first message is consistent with the node's local information.
  • Step S1706 The receiving node returns a second message (ie, verification reply message) based on the verification situation, and the second message contains echo reply.
  • a second message ie, verification reply message
  • Step S1708 The initiating node confirms the verification result according to the received second message.
  • Ping mode The main purpose of Ping mode is to detect the connectivity of the path. It is also used to detect whether the destination node reached is the real destination node of the path. That is, it will verify whether the corresponding FEC of the destination label on the egress node is the same as that in the detection message. The contents of the FEC TLV carried are consistent. In ping mode, the detection packet must contain at least the FEC corresponding to the destination SID of the path.
  • FIG. 18 is a schematic diagram of node networking according to the slice information verification method according to the scenario embodiment of the present invention.
  • ISIS is used as the control plane protocol of SR-MPLS in the IPv4 network.
  • resources are allocated to slice 1 and slice 2 on nodes A, B, C, and D respectively, and the corresponding slice identifiers are Slice ID 1 and Slice ID 2 respectively.
  • Node A assigns the prefix SID related to slice 1 to its upper loopback route prefix A as SID A1; node B allocates the prefix SID related to slice 1 to its upper loopback route prefix B as SID B1; node C assigns its upper loopback route prefix SID as SID B1. C allocates the prefix SID related to slice 1 as SID B1; node D allocates the prefix SID related to slice 1 as SID D1 for its loopback routing prefix D.
  • Nodes locally generate mapping entries between their own assigned SIDs and slices.
  • each node also floods its own SID information externally through IS-IS, carrying the slice ID associated with the SID. After other nodes receive the flooding information, they will locally generate slice-related entries.
  • the slice ID information in the table entries may be in the ILM (in-label mapping) entry or the NHLFE entry. carried in.
  • FIG. 19 is a schematic diagram of an initiating node sending a message according to a scenario embodiment of the present invention.
  • MPLS Echo Request contains FEC TLV
  • FEC TLV contains sub-TLV
  • sub-TLV carries the prefix, notification protocol
  • Figure 20 is a schematic diagram of the FEC TLV format according to a scenario embodiment of the present invention. As shown in Figure 20, it is the encapsulation format of the above FEC TLV.
  • the packet is forwarded normally according to the label stack, passing through nodes A, B, C in sequence, and after reaching node D, because the destination IP of the packet after stripping label D1 is in the 127/8 range, it enters the verification process.
  • Node D queries its own local entry and compares the prefix, notification protocol, and slice ID in the FEC sub-TLV to see if they are consistent with those in the local entry.
  • a verification reply message is returned to explain the verification results. If they are consistent, a verification success message is returned. If they are inconsistent, a verification failure message is returned.
  • node S After receiving the verification reply message, node S confirms the verification result based on the message content.
  • node D receives the message and finds that it has indeed advertised SIDD1 through IS-IS, and the Slice ID associated with D1 is 1, which is the same as the sub-TLV of the FEC TLV in the received authentication request message. If the contents are consistent, the verification is passed.
  • Traceroute mode is used to verify information on each LSR passed by the forwarding path.
  • the FEC TLV needs to contain the FEC information corresponding to all labels in the label stack.
  • This embodiment specifically describes the slice information verification method in traceroute mode.
  • Nodes locally generate mapping entries between their own assigned SIDs and slices.
  • each node also floods its own SID information externally through OSPF and carries the slice ID associated with the SID. After other nodes receive the flooding information, they will locally generate slice-related entries.
  • the slice ID information in the table entries may be in the ILM (in-label mapping) entry or the NHLFE entry. carried in.
  • Node S serves as the initiating node and sends the message ⁇ A1, B1, BC1, D1> ⁇ FEC-A1, FEC-B1, FEC-BC1, FEC-D1>.
  • A1, B1, C1, and D1 are the MPLS label values corresponding to SIDA1, SIDB1, SIDBC1, and SIDD1 respectively.
  • the packet when the verification packet is sent to the intermediate node of the path, the packet also carries the Downstream Detailed Mapping TLV (hereinafter referred to as DDM TLV). When it is sent to the egress node of the path, the DDM TLV does not need to be carried.
  • the TTL of A1 the top label on the stack, is set to 1.
  • the DDM TLV of echo reply carries the forwarding equivalent class stack change sub-TLV (FEC Stack Change sub-TLV), prompting the sending node, next When sending the request message for the first time, it no longer carries FEC-A1.
  • FEC Stack Change sub-TLV forwarding equivalent class stack change sub-TLV
  • Step 303 Node S, as the initiating node, sends the message ⁇ A1, B1, BC1, D1> ⁇ FEC-B1, FEC-BC1, FEC-D1>, and continues to set the TTL setting of the label on the top of the stack to 1.
  • Step 304 After node A receives the message, since its TTL is 1 and the TTL is 0 after decrementing one, it sends the message to the control plane and enters the verification process. Query the local entry content of node A, obtain the prefix, notification protocol, and slice ID information related to label B1, whether it is consistent with FEC B1, and return the verification result message through echo reply.
  • Step 305 Node S, as the initiating node, sends the message ⁇ A1, B1, BC1, D1> ⁇ FEC-B1, FEC-BC1, FEC-D1>, and sets the TTL of the label on the top of the stack to 2.
  • Step 307 Node S, as the initiating node, sends the message ⁇ A1, B1, BC1, D1> ⁇ FEC-B1, FEC-BC1, FEC-D1>, and sets the TTL of the top label of the stack to 2.
  • Step 309 Node S, as the initiating node, sends the message ⁇ A1, B1, BC1, D1> ⁇ FEC-BC1, FEC-D1>, and sets the TTL of the label on the top of the stack to 2.
  • Step 310 After receiving the message, node A sends the message ⁇ B1, BC1, D1> ⁇ FEC-BC1, FEC-D1> to node B according to the normal forwarding process.
  • node B sends the packet to the control plane and enters the verification process. According to the content in FEC STACK, verify whether the link, notification protocol and slice ID information associated with BC1 in the local entry are consistent with FEC-BC1, and return the verification result.
  • node S as the initiating node, sends the message ⁇ A1, B1, BC1, D1> ⁇ FEC-BC1,FEC-D1>, and changes the label on the top of the stack to The TTL is set to 3.
  • Nodes A and B forward the message according to the normal forwarding process.
  • the message sent by node B to node C is: ⁇ BC1, D1> ⁇ FEC-BC1, FEC-D1>.
  • node C Since the TTL of the received label is 1, node C sends the message to the control plane and enters the verification process.
  • node C As the downstream node of link BC1, in addition to the verification result, carries the FEC Stack Change sub-TLV in the echo reply, prompting the sending node to not carry FEC-BC1 when sending the request next time. .
  • node S as the initiating node, sends the message ⁇ A1, B1, BC1, D1> ⁇ FEC-D1>, and sets the TTL of the label on the top of the stack to 3.
  • Nodes A and B forward the message according to the normal forwarding process.
  • the message sent by node B to node C is: ⁇ BC1, D1> ⁇ FEC-D1>.
  • node C Since the received label TTL is 1, node C sends the message to the control plane, enters the verification process, verifies whether the slices and other information associated with SID D1 in the local table entry are consistent with FEC-D1, and returns a verification reply. information.
  • node S as the initiating node, sends the message ⁇ A1, B1, BC1, D1> ⁇ FEC-D1>, and sets the TTL of the label on the top of the stack to 4.
  • nodes A, B, and C forward the message according to the normal forwarding process.
  • the message sent by node C to node D is ⁇ D1> ⁇ FEC-D1>.
  • the initial node controls the TTL of the top-level label to control which node will enter the verification process after receiving the message.
  • Another mode is that each layer of label in the label stack maintains its own TTL and is not affected by the upper layer label. If each node on the MPLS LSP adopts this mode, when sending the verification message, each node needs to be set according to the requirements. The layer's label TTL.
  • the Slice ID on a slicing path uses the same value in the example, the slice ID can also be a local identifier, that is, different Slice IDs are used on the nodes of a slicing path. Make identification.
  • the LSP PING mechanism also includes the function of specifying the reply path. This function can be used to specify the reply path, verify the connectivity of the reply path, and verify the returned LSP. This embodiment explains how to specify the reply path as a specific slice-related path in ping mode, and the related return slice path information verification process.
  • the sending node sends a verification request message, through the reply mode field (5 Reply via Specified Path) of the echo request, indicating that it needs to reply according to the specified path, and also carries the Reply Path (RP) TLV.
  • RP Reply Path
  • the destination node of the Ping After receiving the message, the destination node of the Ping searches for matching return path information based on the FEC information carried in the Reply Path (RP) TLV. If the corresponding MPLS return path can be found, the echo reply message is It is encapsulated and returned in the corresponding MPLS label stack, where the TTL of the top label is set to 255, and the echo reply message carries the RP TLV reflecting the return path. If the corresponding return slice path cannot be found according to FEC, the return node can explain it in the echo reply, thereby notifying the head node of the information.
  • RP Reply Path
  • the sending node After receiving the message, the sending node will perform the FEC verification process to verify whether the FEC information carried in the received RP TLV is consistent with the local information.
  • the verification process is consistent with the FEC verification process in forward ping mode.
  • FIG 22 is a schematic diagram of node networking for specifying a reply path according to a scenario embodiment of the present invention.
  • node A assigns the prefix SID related to slice 1 to its loopback route prefix A, which is SID A1 and related to slice 2.
  • the prefix SID is SID A2; node B allocates the prefix SID related to slice 1 to its upper loopback route prefix B, which is SID B1, and the prefix SID related to slice 2 is SID B2; node D allocates its upper loopback route prefix D with The prefix SID related to slice 1 is SID D1; node X allocates the prefix SID related to slice 2 to its loopback route prefix Y2; Node S allocates the prefix SID related to slice 2 to its upper loopback route prefix S, which is SID S2.
  • node S acts as the initiator, sends a verification request message to verify a certain path in slice 1, and expects the reply message to be returned through the specified slice 2 path.
  • the message sent is: ⁇ A1, B1, D1 > ⁇ FEC-TLV: FEC-D1> ⁇ Reply Path TLV: FEC-X2, FEC-Y2, FEC-S2>.
  • MPLS label stack A1, B1, D1, corresponding to the MPLS labels of SID A1, SID B1, and SID D1 respectively;
  • Target FEC Stack TLV carries sub-TLV: FEC-D1, FEC-D1 contains prefix D and slice ID 1;
  • the Reply Path TLV carries sub-TLVs: FEC-X2, FEC-Y2, and FEC-S2, which carry the FEC information that needs to be passed on the return path.
  • FEC-X2 contains prefix X and slice ID2.
  • node D After node D receives the echo request for verification, since the request message contains the Reply Path TLV, it means that the echo reply needs to return according to the specified slicing path.
  • FEC-X2, FEC-Y2, and FEC-S2 carry the path that needs to be passed on the return path.
  • FEC information node D finds the corresponding SID value based on the prefix + slice ID information in the FEC information, thereby determining that the label stack corresponding to the LSP returned by the corresponding slice is ⁇ X2, Y2, S2>.
  • Node D encapsulates the packet, sets the MPLS TTL at the bottom of the stack to 255 according to the ping mode, and carries the Reply Path TLV, ⁇ X2, Y2, S2> ⁇ Reply Path TLV: FEC-B2, FEC-A2, FEC-S2>.
  • Node B and node A forward the packet according to the regular MPLS process and forward the packet to node S.
  • Node S receives the message ⁇ S2> ⁇ Reply Path TLV: FEC-B2, FEC-A2, FEC-S2>, and verifies the prefix and slice ID information in the local entry associated with S2 according to the egress FEC verification process in ping mode. , whether it is consistent with what is carried in FEC-S2, thereby completing the verification of the specified reverse slicing path.
  • this function can achieve the following purposes:
  • the sending node of the echo request may require the corresponding node to carry the FEC information of the return path when replying. After the sending node receives it, it can verify whether the return path meets expectations, and the return path can be A slice path.
  • Figure 23 is a schematic diagram of node networking for the reverse slicing information return initiating node according to the scenario embodiment of the present invention.
  • node A allocates the prefix SID related to slice 1 to its loopback route prefix A, which is SID A1.
  • the prefix SID related to slice 2 is SID A2;
  • node B allocates the prefix SID related to slice 1 to its upper loopback route prefix B, and the prefix SID related to slice 2 is SID B2;
  • node D assigns its upper loopback route prefix B.
  • prefix D allocates the prefix SID related to slice 1 as SID D1; node X allocates the prefix SID related to slice 2 to its loopback routing prefix X as SID
  • the prefix SID is SID Y2; node S allocates the prefix SID related to slice 2 to its loopback routing prefix S, which is SID S2.
  • a bidirectional path (difference from the previous example, the return path of the bidirectional path has been determined in advance), the forward path is designated to pass through S-A-B-C-D in sequence, corresponding to slice 1.
  • the reverse path is the path within slice 2, passing through D-C-B-A-S in sequence.
  • Slice 1 and slice 2 can be the same slice or different slices, and the forward path can also be a non-slice path.
  • Node S sends a verification request message and sets R-FLAG in the echo request, which means that when the responding node responds to the echo reply, it needs to carry the FEC information corresponding to the reverse path.
  • Node S sends the message ⁇ A1, B1, D1> ⁇ FEC-TLV: FEC-D1>.
  • the forward verification process is similar to the previous example and will not be described again.
  • node D After receiving the message, node D finds that R-FLAG in the echo request is set, so in the echo reply, it needs to carry the Reverse-path Target FEC Stack TLV.
  • the sub-TLVs are carried in sequence: FEC-X2, FEC -Y2, FEC-S2, reflects the FEC information of the return path.
  • the echo reply is encapsulated in the label stack ⁇ X2, Y2, S2> and sent out.
  • node S After node S receives the message, since the destination IP of the message after stripping S2 is in the 127/8 range, it enters the verification process and compares the FEC information carried in the Reverse-path Target FEC Stack TLV with the information associated with the local table entry. Verify consistency to complete the process.
  • the TTL needs to be set appropriately so that it triggers the verification process on the node where verification is expected.
  • the present invention provides a method for verifying slice information, which can be used for path detection and fault location in SR-MPLS-based slices.
  • the method mainly includes: sending a first message carrying slice information to be verified; receiving the first message to verify the slice information.
  • Scenarios applicable to this method include: (1) MPLSLSP ping, used for connectivity detection of slice paths and verification of slice information on egress nodes; (2) MPLS Traceroute, used for verification of slice information on each node of a slice path Verification; (3) When sending MPLS echo request, specify the reply path as a specific slice path.
  • the reply node encapsulates the corresponding message according to the specified information and replies to the sending node.
  • the sending node serves as the exit node of the reply path to verify the slice correlation; (4)
  • the corresponding node is required to carry the FEC of the return path when replying. information.
  • the reply node returns the FEC information of the slice path to the sending node, and the nodes on the return path can verify the relevant slice information on the node.

Landscapes

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

Abstract

本发明实施例提供了一种切片信息验证方法及装置，通过发起节点发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致。

Description

切片信息的验证方法及装置
相关申请的交叉引用
本申请基于2022年6月10日提交的发明名称为“切片信息的验证方法及装置”的中国专利申请CN202210658976.2，并且要求该专利申请的优先权，通过引用将其所公开的内容全部并入本申请。
技术领域
本发明实施例涉及通信领域，具体而言，涉及一种切片信息的验证方法及装置。
背景技术
段路由(Segment Routing，SR)是一种基于源地址的路由的方法，通过在现有的多协议标签交换(Multi-Protocol Label Switching，MPLS)网络的报文头或者互联网协议第6版(InternetProtocol Version 6，IPv6)报文头中携带段路由报文头(Segment Routing Header，SRH)，在SRH中携带有一系列的指示操作(也称为段操作)用于数据在网络中的路由和传输。
5G网络架构中提出了网络切片(NetworkSlicing)这一突破性的概念。通过网络切片，使运营商能够在通用的物理平台之上构建多个专用的、虚拟化的、互相隔离的逻辑网络，来满足不同客户对网络能力的不同要求。网络切片是通过网络功能的组合形成逻辑独立的虚拟网络结构。不同的网络切片，对应了不同的资源保障和服务等级，尤其是不同切片的收费标准和投入的运维成本差别可能是巨大的。
RFC8029定义了基础的MPLS的LSP Ping/Trance route机制，该机制广泛用于MPLS路径的检测和故障定位，但仅限于验证SID关联的前缀、链路、通告协议等信息，缺少验证关联切片标识的机制。
发明内容
本发明实施例提供了一种切片信息的验证方法及装置，以至少解决相关技术中缺少验证关联切片标识机制的问题。
根据本发明的一个实施例，提供了一种切片信息的验证方法，用于段路由多协议标签交换SR-MPLS网络，包括：发起节点发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致。
根据本发明的又一实施例，还提供了一种切片信息的验证方法，用于段路由多协议标签交换SR-MPLS网络，包括：接收节点接收发起节点发送的第一报文，并验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致。
根据本发明的另一实施例，还提供了一种切片信息的验证装置，用于段路由多协议标签交换SR-MPLS网络，包括：发起模块，设置为发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致。
根据本发明的又一实施例，还提供了一种切片信息的验证装置，用于段路由多协议标签交换SR-MPLS网络，包括：接收模块，设置为接收发起节点发送的第一报文，并验证所述第 一报文中携带的切片信息与所述接收节点的本地信息是否一致。
根据本发明的又一个实施例，还提供了一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
根据本发明的又一个实施例，还提供了一种电子装置，包括存储器和处理器，所述存储器中存储有计算机程序，所述处理器被设置为运行所述计算机程序以执行上述任一项方法实施例中的步骤。
附图说明
图1是本发明实施例的一种切片信息的验证方法的移动终端的硬件结构框图；
图2是根据本发明实施例的切片信息的验证方法的流程图；
图3是根据本发明实施例的切片信息的验证方法的流程图；
图4是根据本发明实施例的切片信息的验证方法的流程图；
图5是根据本发明实施例的切片信息的验证方法的流程图；
图6是根据本发明实施例的切片信息的验证方法的流程图；
图7是根据本发明实施例的切片信息的验证方法的流程图；
图8是根据本发明实施例的切片信息的验证装置的结构框图；
图9是根据本发明实施例的切片信息的验证装置的结构框图；
图10是根据本发明实施例的切片信息的验证装置的结构框图；
图11是根据本发明实施例的MPLS echo request/reply报文格式示意图；
图12是根据本发明场景实施例的切片信息验证方法的流程图；
图13是根据本发明场景实施例的切片信息验证方法的流程图；
图14是根据本发明场景实施例的IPv4 Prefix SID切片的sub-TLV格式示意图；
图15是根据本发明场景实施例的IPv6 Prefix SID切片的sub-TLV格式示意图；
图16是根据本发明场景实施例的Adjacency SID切片的sub-TLV格式示意图；
图17是根据本发明场景实施例的切片信息验证方法的流程图；
图18是根据本发明场景实施例的切片信息验证方法的节点组网示意图；
图19是根据本发明场景实施例的发起节点发出报文示意图；
图20是根据本发明场景实施例的FEC TLV格式示意图；
图21是根据本发明场景实施例的切片信息验证方法的节点组网示意图；
图22是根据本发明场景实施例的指定回复路径的节点组网示意图；
图23是根据本发明场景实施例的反向切片信息返回发起节点的节点组网示意图。
具体实施方式
下文中将参考附图并结合实施例来详细说明本发明的实施例。
需要说明的是，本发明的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。
本申请实施例中所提供的方法实施例可以在移动终端、计算机终端或者类似的运算装置中执行。以运行在移动终端上为例，图1是本发明实施例的一种切片信息的验证方法的移动终端的硬件结构框图。如图1所示，移动终端可以包括一个或多个(图1中仅示出一个)处理器102(处理器102可以包括但不限于微处理器MCU或可编程逻辑器件FPGA等的处理装置) 和用于存储数据的存储器104，其中，上述移动终端还可以包括用于通信功能的传输设备106以及输入输出设备108。本领域普通技术人员可以理解，图1所示的结构仅为示意，其并不对上述移动终端的结构造成限定。例如，移动终端还可包括比图1中所示更多或者更少的组件，或者具有与图1所示不同的配置。
存储器104可用于存储计算机程序，例如，应用软件的软件程序以及模块，如本发明实施例中的切片信息的验证方法对应的计算机程序，处理器102通过运行存储在存储器104内的计算机程序，从而执行各种功能应用以及数据处理，即实现上述的方法。存储器104可包括高速随机存储器，还可包括非易失性存储器，如一个或者多个磁性存储装置、闪存、或者其他非易失性固态存储器。在一些实例中，存储器104可进一步包括相对于处理器102远程设置的存储器，这些远程存储器可以通过网络连接至移动终端。上述网络的实例包括但不限于互联网、企业内部网、局域网、移动通信网及其组合。
传输装置106用于经由一个网络接收或者发送数据。上述的网络具体实例可包括移动终端的通信供应商提供的无线网络。在一个实例中，传输装置106包括一个网络适配器(Network Interface Controller，简称为NIC)，其可通过基站与其他网络设备相连从而可与互联网进行通讯。在一个实例中，传输装置106可以为射频(Radio Frequency，简称为RF)模块，其用于通过无线方式与互联网进行通讯。
在本实施例中提供了一种运行于上述移动终端的切片信息的验证方法，图2是根据本发明实施例的切片信息的验证方法的流程图，如图2所示，该流程包括如下步骤：
步骤S202，发起节点发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致。
通过上述步骤，发起节点发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致，可以解决SR-MPLS网络中，缺少验证关联切片标识机制的问题，达到了可以对SR-MPLS的切片中的路径进行检测和故障定位的效果。
在一个示例性实施例中，所述第一报文中还携带有多协议标签交换MPLS回送请求或者MPLS回送应答。
在一个示例性实施例中，在所述第一报文中携带有所述MPLS回送请求的情况下，在发起节点发送第一报文之后，还包括：所述发起节点接收所述接收节点根据验证结果返回的第二报文，并根据所述第二报文确认验证结果，其中，所述第二报文包括MPLS回送应答。图3是根据本发明实施例的切片信息的验证方法的流程图，如图3所示，该流程包括如下步骤：
步骤S302，发起节点发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致；
步骤S304，所述发起节点接收所述接收节点根据验证结果返回的第二报文，并根据所述第二报文确认验证结果，其中，所述第二报文包括MPLS回送应答。
在一个示例性实施例中，在所述第一报文中携带有所述MPLS回送应答的情况下，在所述发起节点发送第一报文之前，还包括：所述发起节点接收MPLS回送请求报文。图4是根据本发明实施例的切片信息的验证方法的流程图，如图4所示，该流程包括如下步骤：
步骤S402，发起节点接收MPLS回送请求报文；
步骤S404，发起节点发送第一报文，其中，所述第一报文携带有待验证的切片信息，以 便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致。
在一个示例性实施例中，当所述第一报文中还携带有所述MPLS回送请求时，所述发起节点发送第一报文，包括：所述发起节点发送所述第一报文至出口节点；所述发起节点接收所述出口节点根据验证结果返回的第二报文包括：所述发起节点接收并确认来自所述出口节点的验证结果，检测路径是否连通，其中，所述验证结果为所述出口节点查询自身本地的表项验证转发等价类(Forwarding Equivalence Class，FEC)TLV的sub-TLV(Type类型、Length长度、Value值)中的切片ID是否均与本地的所述表项中的一致。
其中，本领域的普通技术人员应该知道，上述MPLS的回送请求和回送应答中可以包含多个TLV，例如FEC TLV和RP TLV，一个TLV中可以包含多个子TLV即sub-TLV。
本领域的普通技术人员应该知道，上述出口节点是一条转发路径上的出口节点，发起节点发报文的目的是到出口节点，是否能到出口节点取决于路径的连通性等因素。
本领域的普通技术人员应该知道，在出口节点查询自身本地的表项验证转发等价类FEC sub-TLV中的切片标识(Identifier，ID)是否均与本地的所述表项中的一致时，除了必须包括的切片ID外，还可以包括前缀/链路、通告协议、业务功能、算法、多拓扑等信息。
在一个示例性实施例中，当第一报文中携带有所述MPLS回送请求时，所述发起节点发送第一报文，还包括：所述发起节点逐一发送所述第一报文至所述接收节点，待验证切片信息的MPLS标签触发各所述接收节点的切片信息验证，其中，所述MPLS回送请求中包含验证转发等价类FEC TLV，所述FEC TLV包含sub-TLV信息和/或下游数据映射DDM的TLV信息，所述sub-TLV信息中包含第一切片信息。
本领域的普通技术人员应该知道，上述通过设置关联待验证切片信息的MPLS标签触发各所述接收节点的切片信息验证时，MPLS标签的生存时间(Time To Live，TTL)有多种方式，一种方式是只要设置最初栈顶标签的TTL，后续的标签会拷贝上一个标签的TTL，这种情况下，不需要设置各个标签的TTL；另外，在一个节点上有多个标签的情况下，待验证的标签也不一定是接收到的栈顶标签。
本领域的普通技术人员应该知道，上述接收节点可以只包括一个接收节点，也可以包括多个接收节点，当转发路径只有一跳时，那么就只会存在一个接收节点。
在一个示例性实施例中，当所述第一报文中携带有所述MPLS回送应答时，所述发起节点发送第一报文，包括：所述发起节点接收MPLS回送请求报文，所述MPLS回送请求报文中包含RP TLV，所述RP TLV中包含回复路径的转发等价类FEC信息，其中，所述FEC信息中包含第一切片信息；所述发起节点通过回复路径发送第一报文，其中，所述回复路径由所述接收节点根据所述FEC信息查找匹配，所述第一报文包括所述回复路径对应的MPLS标签栈及MPLS回送应答，所述MPLS回送应答中包含所述RP TLV。
本领域的普通技术人员应该知道，回复路径由所述接收节点根据所述FEC信息查找匹配时，可以是由回复路径的尾节点进行查找匹配，也可以是任一返回验证结果的接收节点进行查找匹配，即返回验证结果的接收节点都可以进行查找匹配。
在一个示例性实施例中，所述发起节点发送所述第一报文，还包括：所述发起节点接收MPLS回送请求报文，所述MPLS回送请求报文中的R标识置位；所述发起节点发送第一报文，其中，所述第一报文中的所述MPLS回送应答携带有反向路径目标转发等价类堆栈TLV，所述 反向路径目标转发等价类堆栈TLV中携带第一切片信息。
在本发明的上述实施例中，通过发起节点发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致，可以解决SR-MPLS网络中，缺少验证关联切片标识机制的问题，达到了可以对SR-MPLS的切片中的路径进行检测和故障定位的效果。
根据本发明的又一实施例，还提供了一种切片信息的验证方法，用于段路由多协议标签交换SR-MPLS网络，图5是根据本发明实施例的切片信息的验证方法的流程图，如图5所示，该流程包括如下步骤：
步骤S502，接收节点接收发起节点发送的第一报文，并验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致。
在一个示例性实施例中，其中，所述接收节点验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致需满足触发条件，其中，所述触发条件包括至少以下之一：IP报文头中包含路由器警报选项；IP生存时间TTL到期；MPLS生存时间TTL到期；标签为MPLS路由器警报标签；目的IP处于127/8范围内。
在一个示例性实施例中，所述第一报文中还携带有多协议标签交换MPLS回送请求或者MPLS回送应答。
在一个示例性实施例中，在所述第一报文中携带有所述MPLS回送请求的情况下，所述接收节点验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致之后，还包括：所述接收节点向所述发起节点返回第二报文，以便所述发起节点对所述验证结果的确认，其中，所述第二报文包括所述MPLS回送应答。图6是根据本发明实施例的切片信息的验证方法的流程图，如图6所示，该流程包括如下步骤：
步骤S602，接收节点接收发起节点发送的第一报文，并验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致；
步骤S604，所述接收节点向所述发起节点返回第二报文，以便所述发起节点对所述验证结果的确认，其中，所述第二报文包括所述MPLS回送应答。
在一个示例性实施例中，当所述第一报文中携带有所述MPLS回送请求时，所述接收节点接收发起节点发送的第一报文，还包括：所述接收节点为第一切片信息关联的段标识；所述接收节点本地生成所述段标识和所述第一切片信息的表项。所述接收节点验证所述第一切片信息与所述接收节点的本地信息是否一致包括：所述接收节点的出口节点根据所述第一报文查询自身本地的所述表项，以验证转发等价类FEC TLV的sub-TLV信息中的切片ID是否均与本地的所述表项中的一致；所述接收节点将验证结果返回至所述发起节点，用于所述发起节点对所述验证结果确认，以确认所述第一切片信息是否验证通过。
在一个示例性实施例中，当所述第一报文中携带有所述MPLS回送请求时，所述接收节点接收发起节点发送的第一报文，还包括：所述接收节点与第一切片信息关联的段标识；所述接收节点本地生成所述段标识和所述第一切片信息的表项；所述接收节点验证所述第一切片信息与所述接收节点的本地信息是否一致包括：所述接收节点根据所述第一报文，待验证切片信息的MPLS标签触发各所述接收节点的切片信息验证，其中，所述MPLS回送请求中包含验证转发等价类FEC TLV，所述FEC TLV包含sub-TLV信息和/或下游数据映射DDM的TLV信 息，所述sub-TLV信息中包含第一切片信息，所述接收节点至少包括所述第一接收节点。
本领域的普通技术人员应该知道，上述步骤中提到的段标识，是和切片关联的段标识(Segment Routing，SID)，它可以是一个前缀段标识prefix SID，也可以是一个邻接SID，此外还可以是其他的SID，这里不做限制，只要能够满足具体实施例的具体需求即可，但是本发明实施例中所提到的prefix SID和邻接SID是两种比较典型的SID，适用于本发明的所有实施例。
在一个示例性实施例中，当所述第一报文中携带有所述MPLS回送应答时，所述接收节点接收发起节点发送的第一报文，还包括：所述接收节点接收所述发起节点通过回复路径发送的第一报文，其中，所述回复路径由所述接收节点根据转发等价类FEC信息查找匹配，所述第一报文包括所述回复路径对应的MPLS标签栈及MPLS回送应答，所述MPLS回送应答中包含RP TLV，所述RP TLV中包含回复路径的所述FEC信息，其中，所述FEC信息中包含第一切片信息。图7是根据本发明实施例的切片信息的验证方法的流程图，如图7所示，该流程包括如下步骤：
步骤S702，所述接收节点接收所述发起节点通过回复路径发送的第一报文；其中，所述回复路径由所述接收节点根据转发等价类FEC信息查找匹配，所述第一报文包括所述回复路径对应的MPLS标签栈及MPLS回送应答，所述MPLS回送应答中包含RP TLV，所述RP TLV中包含回复路径的所述FEC信息，其中，所述FEC信息中包含第一切片信息。
在一个示例性实施例中，所述接收节点接收发起节点发送的第一报文，还包括：所述接收节点接收所述第一报文，其中，所述第一报文中的所述MPLS回送应答携带有反向路径目标转发等价类堆栈TLV，所述反向路径目标转发等价类堆栈TLV中携带第一切片信息。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本发明实施例的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端设备(可以是手机，计算机，服务器，或者网络设备等)执行本发明各个实施例所述的方法。
在本实施例中还提供了一种切片信息的验证装置，该装置用于实现上述实施例及优选实施方式，已经进行过说明的不再赘述。如以下所使用的，术语“模块”可以实现预定功能的软件和/或硬件的组合。尽管以下实施例所描述的装置较佳地以软件来实现，但是硬件，或者软件和硬件的组合的实现也是可能并被构想的。
图8是根据本发明实施例的切片信息的验证装置的结构框图，如图8所示，该验证装置80包括：发起模块810，设置为发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致。
在一个示例性实施例中，所述第一报文中还携带有多协议标签交换MPLS回送请求或者MPLS回送应答。
在一个示例性实施例中，图9是根据本发明实施例的切片信息的验证装置的结构框图，如图9所示，该验证装置90除了图8中的发起模块810外，还包括：验证模块910，设置为在所述第一报文中携带有所述MPLS回送请求时，接收并确认来自出口节点的验证结果，以检 测路径是否连通，其中，所述验证结果为所述出口节点查询自身本地的表项，验证转发等价类FEC TLV的sub-TLV中切片ID是否均与本地的所述表项中的一致。
在一个示例性实施例中，在所述第一报文中携带有所述MPLS回送请求的情况下，所述发起模块810还设置为，逐一发送所述第一报文至所述接收节点，通过设置关联待验证切片信息的MPLS标签触发各所述接收节点的切片信息验证，其中，所述MPLS回送请求中包含验证转发等价类FEC TLV，所述FEC TLV包含sub-TLV信息和/或下游数据映射DDM的TLV信息，所述sub-TLV信息中包含第一切片信息。
在一个示例性实施例中，在所述第一报文中携带有所述MPLS回送应答的情况下，所述发起模块810还设置为，接收MPLS回送请求报文，所述MPLS回送请求报文中包含RP TLV，所述RP TLV中包含回复路径的转发等价类FEC信息，其中，所述FEC信息中包含第一切片信息；
所述发起模块810还设置为通过回复路径发送第一报文，其中，所述回复路径由所述接收节点根据所述FEC信息查找匹配，所述第一报文包括所述回复路径对应的MPLS标签栈及MPLS回送应答，所述MPLS回送应答中包含所述RP TLV。
在一个示例性实施例中，所述发起模块810还设置为，接收MPLS回送请求报文，所述MPLS回送请求报文中的R标识置位；以及发送第一报文，其中，所述第一报文中的所述MPLS回送应答携带有反向路径目标转发等价类堆栈TLV，所述反向路径目标转发等价类堆栈TLV中携带第一切片信息。
根据本发明的又一实施例，还提供了一种切片信息的验证装置，设置为段路由多协议标签交换SR-MPLS网络，图10是根据本发明实施例的切片信息的验证装置的结构框图，如图10所示，该验证装置100包括：接收模块1010，设置为接收发起节点发送的第一报文，并验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致。
在一个示例性实施例中，所述接收模块1010包括：判断子模块，设置为在所述接收节点验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致之前，判断所述接收节点是否满足触发条件，其中，所述触发条件包括至少以下之一：IP报文头中包含路由器警报选项；IP生存时间TTL到期；MPLS生存时间TTL到期；标签为MPLS路由器警报标签；目的IP处于127/8范围内。
需要说明的是，上述各个模块是可以通过软件或硬件来实现的，对于后者，可以通过以下方式实现，但不限于此：上述模块均位于同一处理器中；或者，上述各个模块以任意组合的形式分别位于不同的处理器中。
本发明的实施例还提供了一种计算机可读存储介质，该计算机可读存储介质中存储有计算机程序，其中，该计算机程序被设置为运行时执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述计算机可读存储介质可以包括但不限于：U盘、只读存储器(Read-Only Memory，简称为ROM)、随机存取存储器(Random Access Memory，简称为RAM)、移动硬盘、磁碟或者光盘等各种可以存储计算机程序的介质。
本发明的实施例还提供了一种电子装置，包括存储器和处理器，该存储器中存储有计算机程序，该处理器被设置为运行计算机程序以执行上述任一项方法实施例中的步骤。
在一个示例性实施例中，上述电子装置还可以包括传输设备以及输入输出设备，其中，该传输设备和上述处理器连接，该输入输出设备和上述处理器连接。
本实施例中的具体示例可以参考上述实施例及示例性实施方式中所描述的示例，本实施例在此不再赘述。
显然，本领域的技术人员应该明白，上述的本发明实施例的各模块或各步骤可以用通用的计算装置来实现，它们可以集中在单个的计算装置上，或者分布在多个计算装置所组成的网络上，它们可以用计算装置可执行的程序代码来实现，从而，可以将它们存储在存储装置中由计算装置来执行，并且在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤，或者将它们分别制作成各个集成电路模块，或者将它们中的多个模块或步骤制作成单个集成电路模块来实现。这样，本发明不限制于任何特定的硬件和软件结合。
为了使得本领域的技术人员能够更清楚地理解本发明实施例的技术方案，下面将结合具体的场景实施例对本发明实施例进行阐述。
网络切片的标识(Identity，ID)可简称为切片标识或切片ID，用于标识网络切片。在某些技术中，也将切片ID称为网络资源区分策略标识(Network Resource Partition Policy ID，NRP-ID)。本文中统一用切片标识来指代。
根据具体实现网络切片的技术手段，切片标识可以有不同的含义和形式，一个标识只要能够在特定范围内(如同一个物理端口/链路、同一个IGP域内、整网范围等)唯一的区分出切片或者资源，都可以被看作切片标识。
在SR-MPLS网络中实现切片时，一种主要的方式是在节点或链路上，为每切片分配SID(也即MPLS标签)。例如，同一个节点上，需要划分出两个网络切片，为slice1和slice2分配资源，则可以在该节点上slice 1分配silce ID 1，并且分配对应SID A，slice 2分配silce ID 2，并且分配对应SID B。而标签和切片标识的映射关系(即SID A与slice ID 1关联，SID B与slice ID 2关联)，需要对外通告，例如通过IS-IS或OSPF协议对外洪泛。
RFC8029定义了基础的MPLS的LSP Ping/Trance route机制，该机制广泛用于MPLS路径的检测和故障定位，主要基于MPLS echo request/reply报文，该报文为UDP报文，格式如图11所示。
RFC8287定义了SR-MPLS场景中的LSP Ping/Traceroute机制。但仅限于验证SID关联的前缀、链路、通告协议等信息，缺少验证关联切片标识的机制。
场景实施例一
图12是根据本发明场景实施例的切片信息验证方法的流程图，该方法用于SR-MPLS网络，如图12所示，该流程包括以下步骤：
步骤S1202，发起节点发送第一报文，第一报文中包含MPLS标签栈及待验证的切片信息。
其中，第一报文可以是包含MPLS回送请求(echo request)，待验证的切片信息以sub-TLV的形式包含在FEC TLV中，携带于echo request内；第一报文可能包含MPLS echo reply，待验证的切片信息以sub-TLV的形式包含在Reply Path TLV中，携带于echo reply内；
或者，第一报文可以包含MPLS回送应答(echo reply)，待验证的切片信息以sub-TLV的形式包含在Reverse-path Target FEC Stack TLV中，携带于echo reply内。
步骤S1204，接收节点收到第一报文后，如果满足触发条件，则进入验证流程，验证第一报文中携带的切片信息与节点本地信息是否一致。
其中，触发条件包括但不限于RFC8029中规定的以下条件之一：
IP报文头中包含路由器警报选项(Router Alert option)；
IP生存时间TTL到期(IP TTL expiration)；
MPLS生存时间TTL到期(MPLS TTL expiration)；
标签为MPLS路由器警报标签(MPLS Router Alert label)；
目的IP处于127/8范围内。
本领域的普通技术人员应该知道，收到的第一报文与发出的并不一定完全一致，可能经过了MPLS的标签剥离、交换等操作。
图13是根据本发明场景实施例的切片信息验证方法的流程图，如图13所示，在第一报文包含MPLS echo reply的情况下，该流程包括以下步骤：
步骤S1302，发起节点接收MPLS echo request报文；
步骤S1304，发起节点发送第一报文，第一报文中包含MPLS标签栈及待验证的切片信息。
图14是根据本发明场景实施例的IPv4 Prefix SID切片的sub-TLV格式示意图。图15是根据本发明场景实施例的IPv6 Prefix SID切片的sub-TLV格式示意图。图16是根据本发明场景实施例的Adjacency SID切片的sub-TLV格式示意图。
本领域的普通技术人员应该知道，还可以约定切片ID(slice ID)为特殊值(例如，Slice ID＝0)时，代表不需验证切片信息。根据SID类型的不同，除了验证SID关联切片对应的切片ID以外，sub-TLV中还可能携带的待验证内容包括但不限于，SID关联的前缀、链路、该SID通过何种协议通告、业务功能(service function)、算法、多拓扑(Multi-Topology)等信息。
图17是根据本发明场景实施例的切片信息验证方法的流程图，如图17所示，在第一报文包含echo request的情况下，该流程包括以下步骤：
步骤S1702，发起节点发送第一报文，第一报文中包含MPLS标签栈及待验证的切片信息。
其中，第一报文可以是包含MPLS回送请求(echo request)，待验证的切片信息以sub-TLV的形式包含在FECTLV中，携带于echo request内；第一报文可能包含MPLS echo reply，待验证的切片信息以sub-TLV的形式包含在Reply Path TLV中，携带于echo reply内；
或者，第一报文可以包含MPLS回送应答(echo reply)，待验证的切片信息以sub-TLV的形式包含在Reverse-path Target FEC Stack TLV中，携带于echo reply内。
步骤S1704，接收节点收到第一报文后，如果满足触发条件，则进入验证流程，验证第一报文中携带的切片信息与节点本地信息是否一致。
步骤S1706，接收节点根据验证情况，返回第二报文(即验证回复报文)，所述第二报文中包含echo reply。
步骤S1708，发起节点根据接收到的第二报文，确认验证结果。
场景实施例二
Ping模式主要的目的是用于检测路径的连通性，此外用于检测所到达的目的节点是否是路径真正的目的节点，即会验证目的标签在出节点上的对应的FEC是否与检测报文中携带的FEC TLV的内容一致。在ping模式下，检测报文中至少需要包含路径目的SID对应的FEC。
本实施例具体说明ping模式下的切片信息验证方法，图18是根据本发明场景实施例的切片信息验证方法的节点组网示意图，在IPv4网络中采用ISIS作为SR-MPLS的控制面协议。 如图18所示，节点A、B、C、D上，分别为切片1和切片2分配了资源，对应的切片标识分别为Slice ID 1和Slice ID 2。
节点A为其上loopback路由prefix A分配与切片1相关的prefix SID为SID A1；节点B为其上loopback路由prefix B分配与切片1相关的prefix SID为SID B1；节点C为其上loopback路由prefix C分配与切片1相关的prefix SID为SID B1；节点D为其上loopback路由prefix D分配与切片1相关的prefix SID为SID D1。
节点本地会生成自身分配的SID与切片的映射表项，此外，各节点还会通过IS-IS对外洪泛自身的SID信息，同时携带SID关联的切片ID。其他节点收到该洪泛信息后，会在本地生成与切片相关的表项，表项中切片ID信息，切片ID可能是在ILM(in-label mapping)表项中，也可能在NHLFE表项中携带。
为了验证切片1对应的路径的连通性及出口信息是否正确，节点S发出的报文如图19所示。SID A1的TTL设置为255。图19是根据本发明场景实施例的发起节点发出报文示意图。其中，MPLS Echo Request中包含FEC TLV，FEC TLV中包含sub-TLV，sub-TLV中携带节点D上，待验证的SID D1对应的前缀、通告协议、及切片ID信息。图20是根据本发明场景实施例的FEC TLV格式示意图，如图20所示，为上述FEC TLV的封装格式。
报文按照标签栈正常转发，依次经过节点A、B、C，到节点D后，由于剥离标签D1后的报文，目的IP在127/8范围内，因此进入验证流程。节点D查询自己的本地表项，对比FEC sub-TLV中的前缀、通告协议以及切片ID是否均与本地表项中的一致。在验证后，返回验证回复消息，说明验证结果，如果一致，则返回验证成功消息，不一致则返回验证失败消息。
节点S收到验证回复消息后，根据消息内容，确认验证结果。
在本场景实施例中，节点D收到报文，发现自身确实通过IS-IS对外通告了SIDD1，且D1关联的Slice ID为1，与收到的验证请求消息中的FEC TLV的sub-TLV中的内容一致，则验证通过。
场景实施例三
Traceroute模式用于转发路径经过的逐个LSR上的信息验证，在初次发送验证请求报文时，FEC TLV中需要包含标签栈中所有标签对应的FEC信息。
本实施例具体说明traceroute模式下的切片信息验证方法。
图21是根据本发明场景实施例的切片信息验证方法的节点组网示意图，如图21所示，在IPv6网络中使用OSPF作为SR-MPLS的控制面协议。节点A为其上loopback路由prefix A分配与切片1相关的prefix SID为SID A1；节点B为其上loopback路由prefix B分配与切片1相关的prefix SID为SID B1；节点B为B-C间链路link1分配与切片1相关的adj-SID为SID BC1，节点D为其上loopback路由prefix D分配与切片1相关的prefix SID为SID D1。
节点本地会生成自身分配的SID与切片的映射表项，此外，各节点还会通过OSPF对外洪泛自身的SID信息，并携带SID关联的切片ID。其他节点收到该洪泛信息后，会在本地生成与切片相关的表项，表项中切片ID信息，切片ID可能是在ILM(in-label mapping)表项中，也可能在NHLFE表项中携带。
在使用Traceroute模式对节点S-D的切片1对应路径进行检测时，具体的步骤如下：
步骤301，
节点S作为发起节点，发送报文<A1，B1，BC1，D1><FEC-A1，FEC-B1，FEC-BC1，FEC-D1>，其 中A1，B1，C1，D1分别为SIDA1、SIDB1、SIDBC1、SIDD1对应的MPLS标签值。除FEC TLV外，在将验证报文发给路径的中间节点时，报文中还携带Downstream Detailed Mapping TLV(其后简称DDM TLV)，发给路径的出口节点时，可以不携带DDM TLV。栈顶标签的A1的TTL设置为1。
以下主要介绍与切片验证相关的流程，不再详细对LSP ping/traceroute的通用流程进行描述。
步骤302，节点A收到报文后，由于标签TTL为1，减一后为0，将报文上送控制面，进入验证流程。节点A查询本地表项，获取SID A1相关的前缀、通告协议、及切片ID信息，与FEC A1中是否一致，通过echo reply返回验证结果消息。
此外，由于节点A对于label A1的操作为pop，根据RFC8287的规定，在echo reply的DDM TLV中，携带有转发等价类栈变更子TLV(FEC Stack Change sub-TLV)，提示发送节点，下次发送请求报文时，不再携带FEC-A1。
步骤303，节点S作为发起节点，发送报文<A1，B1，BC1，D1><FEC-B1，FEC-BC1，FEC-D1>，将栈顶标签的TTL设置继续设置为1。
步骤304，节点A收到报文后，由于其TTL为1，TTL减一后为0，因此进入将报文上送控制面，进入验证流程。查询节点A的本地表项内容，获取label B1相关的前缀、通告协议、及切片ID信息，与FEC B1中是否一致，并通过echo reply返回验证结果消息。
步骤305，节点S作为发起节点，发送报文<A1，B1，BC1，D1><FEC-B1，FEC-BC1，FEC-D1>，将栈顶标签的TTL设置为2。
步骤306，节点A收到报文后，根据正常转发流程，将label A1剥离，将label A1的TTL-1后拷贝至labelB1，然后根据labelB1将报文转发到节点B，节点B收到报文后，由于TTL-1＝0，因此将报文上送控制面，进入验证流程。查询节点B，此外，由于节点B是prefix B1的发起节点，因此除验证结果外，在echo reply中携带FEC Stack Change sub-TLV，提示发送节点，下次发送request时，不携带FEC-B1。
步骤307，节点S作为发起节点，发送报文<A1，B1，BC1，D1><FEC-B1，FEC-BC1，FEC-D1>，将栈顶标签的TTL设置为2。
步骤308，节点A收到报文后，根据正常转发流程，将label A1剥离，将label A1的TTL-1后拷贝至labelB1，然后根据labelB1将报文转发到节点B，节点B收到报文后，由于TTL-1＝0，因此将报文上送控制面，进入验证流程。查询节点B，此外，由于节点B是prefix B1的发起节点，因此除验证结果外，在echo reply中携带FEC Stack Change sub-TLV，提示发送节点，下次发送request时，不携带FEC-B1。
步骤309，节点S作为发起节点，发送报文<A1，B1，BC1，D1><FEC-BC1，FEC-D1>，将栈顶标签的TTL设置为2。
步骤310，节点A收到报文后，根据正常转发流程，将报文<B1，BC1，D1><FEC-BC1，FEC-D1>发送到B节点。
S311，节点B上由于TTL-1＝0，将报文上送控制面，进入验证流程。根据FEC STACK中的内容，验证本地表项中BC1关联的链路、通告协议和切片ID信息是否与FEC-BC1一致，并返回验证结果。
S312，节点S作为发起节点，发送报文<A1，B1，BC1，D1><FEC-BC1，FEC-D1>，将栈顶标签 的TTL设置为3。
S313，节点A、B按照正常转发流程对报文进行转发，节点B发送给节点C的报文为：<BC1，D1><FEC-BC1，FEC-D1>。
S314，节点C上由于收到的标签TTL为1，将报文上送控制面，进入验证流程。此外，根据RFC8287中的规定，节点C作为链路BC1的下游节点，除验证结果外，在echo reply中携带FEC Stack Change sub-TLV，提示发送节点，下次发送request时，不携带FEC-BC1。
S315，节点S作为发起节点，发送报文<A1，B1，BC1，D1><FEC-D1>，将栈顶标签的TTL设置为3。
S316，节点A、B按照正常转发流程对报文进行转发，节点B发送给节点C的报文为：<BC1，D1><FEC-D1>。
S317，节点C上由于收到的标签TTL为1，将报文上送控制面，进入验证流程，验证本地表项中与SID D1关联的切片等信息是否与FEC-D1一致，并返回验证回复消息。
S318，节点S作为发起节点，发送报文<A1，B1，BC1，D1><FEC-D1>，将栈顶标签的TTL设置为4。
S319，节点A、B、C按照正常转发流程对报文进行转发，节点C发送给节点D的报文为<D1><FEC-D1>。
S320，节点D收到报文后，由于TTL-1＝0，将报文上送控制面，进入验证流程。验证本地与SID关联的切片等信息，是否与FEC-D1中携带的一致，并通过验证回复消息返回验证结果，此外同时在回复消息中说明，D为路径的出口，从而节点S收到后完成对整条LSP的Traceroute流程。
本领域的普通技术人员应该知道，以上是以转发时将处理后的顶层标签的TTL拷贝至下层标签为例进行的说明。因此在初始节点通过控制顶层标签的TTL，来控制在哪个节点收到报文后会进入验证流程。另一种模式是，标签栈中各层标签保持自身的TTL，不受上层标签的影响，如果MPLS LSP上的各节点采用的是该种模式，在发送验证消息时，则需要根据需求设置各层的标签TTL。
另外虽然本场景实施例中，一条切片路径上的Slice ID在举例中采用了相同的值，但切片ID也可以是一个局部的标识，即一条切片路径的节点上使用了不同的Slice ID对切片进行标识。
场景实施例四
在LSP PING机制中，还包含指定回复路径的功能，该功能可以用于指定回复路径，验证回复路径的连通性，并且可以对返回的LSP进行验证。本实施例说明在ping模式下如何指定回复路径为特定切片相关路径，以及相关的返回切片路径信息验证流程。
发送节点发送验证请求消息，通过其中echo request的reply mode字段(5 Reply via Specified Path)，说明需要按照指定路径回复，同时携带Reply Path(RP)TLV，
Ping的目的节点收到报文后，根据回复路径(Reply Path，RP)TLV中携带的FEC信息，查找是否有匹配的返回路径信息，如果能够查找到对应的MPLS返回路径，则将echo reply消息封装在相应MPLS标签栈中返回，其中顶层标签的TTL设置为255，echo reply消息携带反映返回路径的RP TLV。如果根据FEC查找不到相应的返回切片路径，则返回节点可以在echo reply中进行说明，从而通知头节点该信息。
发送节点收到报文后，会进行FEC的验证流程，验证收到的RP TLV中携带的FEC信息是否与本地信息一致，验证流程与正向ping模式的中的FEC验证流程一致。
图22是根据本发明场景实施例的指定回复路径的节点组网示意图，如图22所示，节点A为其上loopback路由prefix A分配与切片1相关的prefix SID为SID A1，与切片2相关的prefix SID为SID A2；节点B为其上loopback路由prefix B分配与切片1相关的prefix SID为SID B1，与切片2相关的prefix SID为SID B2；节点D为其上loopback路由prefix D分配与切片1相关的prefix SID为SID D1；节点X为其上loopback路由prefix X分配与切片2相关的prefix SID为SID X2；节点Y为其上loopback路由prefix X分配与切片2相关的prefix SID为SID Y2；节点S为其上loopback路由prefix S分配与切片2相关的prefix SID为SID S2。
Ping模式下，节点S作为发起端，发送验证请求消息，对切片1内的某条路径进行验证，并且期望回复消息通过指定的切片2路径返回，发出的报文为：<A1，B1，D1><FEC-TLV：FEC-D1><Reply Path TLV：FEC-X2，FEC-Y2，FEC-S2>。
对于报文的说明如下：
MPLS标签栈：A1、B1、D1，分别对应SID A1、SID B1、SID D1的MPLS标签；
Target FEC Stack TLV中携带sub-TLV：FEC-D1，FEC-D1中包含prefix D及切片ID 1；
Reply Path TLV中携带sub-TLV：FEC-X2、FEC-Y2、FEC-S2，携带了返回路径上需要途经的FEC信息，如FEC-X2中包含了prefix X及切片ID2。
S到D的流程以及D上的验证流程与前文所述的ping模式的流程相同，不再赘述。
节点D收到echo request进行验证后，由于请求消息中包含了Reply Path TLV，说明echo reply需要按指定的切片路径返回，FEC-X2、FEC-Y2、FEC-S2携带了返回路径上需要途经的FEC信息，节点D根据FEC信息中的prefix+切片ID信息查找到对应的SID值，从而确定相应的切片返回LSP对应的标签栈为<X2、Y2、S2>。(如果根据FEC查找不到相应的返回路径，则可能通过其他可达路径返回，并且通过返回码说明该情况，从而使头节点感知尾节点上找不到该FEC存在的路径。)
节点D封装报文，按照ping模式，将栈底MPLS TTL设置为255，并且携带Reply Path TLV，<X2，Y2，S2><Reply Path TLV：FEC-B2，FEC-A2，FEC-S2>。
节点B和节点A按照常规MPLS流程对报文进行转发，将报文转发至节点S。
节点S收到报文<S2><Reply Path TLV：FEC-B2，FEC-A2，FEC-S2>，按照ping模式的出口FEC验证流程，验证S2关联的本地表项中的前缀和切片ID信息，是否与FEC-S2中携带的一致，从而完成对指定反向切片路径的验证。
从以上场景实施例可以看出，该功能可以实现以下目的：
1)确认尾节点是否存在请求消息中提供的FEC对应的路径；
2)根据FEC确定返回LSP后，通过发起节点是否可以收到返回消息，确认该LSP的连通性；
3)发起节点作为返回路径的出口节点，本地表项关联的信息是否与返回消息中的FEC一致。
需要说明的是，为方便区分，本例中以双向不同路径属于切片进行说明，路径属于相同切片的场景同样适用，也同样适用于正向非切片路径的情况。此外，本实施例说明了双向不 共路的场景，但也适用于双向共路的场景，即正反向的路径途经相同的节点。
场景实施例五
在双向路径的情况下，echo request的发送节点，可能要求相应节点回复时携带返回路径的FEC信息，发送节点收到后，可以对该返回路径进行验证，是否符合预期，而该返回路径可以是一条切片路径。
图23是根据本发明场景实施例的反向切片信息返回发起节点的节点组网示意图，如图23所示，节点A为其上loopback路由prefix A分配与切片1相关的prefix SID为SID A1，与切片2相关的prefix SID为SID A2；节点B为其上loopback路由prefix B分配与切片1相关的prefix SID为SID B1，与切片2相关的prefix SID为SID B2；节点D为其上loopback路由prefix D分配与切片1相关的prefix SID为SID D1；节点X为其上loopback路由prefix X分配与切片2相关的prefix SID为SID X2；节点Y为其上loopback路由prefix X分配与切片2相关的prefix SID为SID Y2；节点S为其上loopback路由prefix S分配与切片2相关的prefix SID为SID S2。
一条双向路径(与前例的区别，双向路径的返回路径是事先就已经确定的)，指定正向路径依次经过S-A-B-C-D，对应切片1。反向路径为切片2内的路径，依次经过D-C-B-A-S。切片1与切片2可以是同一个切片，也可以是不同的切片，正向路径也可以是一条非切片的路径。
节点S发送验证请求消息，将echo request中的R-FLAG置位，代表需要响应节点回复echo reply时，需要携带反向路径对应的FEC信息。
节点S发出报文<A1，B1，D1><FEC-TLV：FEC-D1>，正向的验证流程与前例类似，不再描述。
节点D收到报文后，发现echo request中的R-FLAG置位，因此在echo reply中，需要携带Reverse-path Target FEC Stack TLV，该TLV中，依次携带sub-TLV：FEC-X2、FEC-Y2、FEC-S2，反映返回路径的FEC信息。同时由于双向路径的场景下，指定了返回路径，因此按将echo reply封装在标签栈<X2，Y2，S2>中发出。
节点S收到报文后，由于剥离S2后的报文目的IP在127/8范围，进入验证流程，将Reverse-path Target FEC Stack TLV中携带的FEC信息与本地表项关联的信息进行对比，验证是否一致，从而完成整个流程。
如果期望对路径的中间节点，则与场景实施例三中的traceroute模式类似，需要对TTL进行合理的设置，使其在期望验证的节点上触发验证流程。
根据上述场景实施例，本发明提供了一种切片信息的验证方法，可以用于基于SR-MPLS的切片中的路径检测和故障定位。该方法主要包括：发送第一报文，携带待验证的切片信息；接收第一报文，对切片信息进行验证。该方法适用于的场景可以包括：(1)、MPLSLSP ping，用于切片路径的连通性检测及出口节点上切片信息的验证；(2)、MPLS Traceroute，用于切片路径逐个节点上切片信息的验证；(3)、在发送MPLS echo request时，指定回复的路径为特定切片路径。回复节点根据指定信息封装相应的报文，回复给发送节点，发送节点作为回复路径的出口节点对切片相关进行验证；(4)、双向路径的情况下，要求相应节点回复时携带返回路径的FEC信息。返回路径为切片路径的情况下，回复节点返回切片路径的FEC信息回复给发送节点，返回路径上的节点可以对节点上相关的切片信息进行验证。
以上所述仅为本发明的优选实施例而已，并不用于限制本发明，对于本领域的技术人员来说，本发明可以有各种更改和变化。凡在本发明的原则之内，所作的任何修改、等同替换、改进等，均应包含在本发明的保护范围之内。

Claims (26)

  1. 一种切片信息的验证方法，用于段路由多协议标签交换SR-MPLS网络，包括：
    发起节点发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致。
  2. 根据权利要求1所述的方法，其中，所述第一报文中还携带有多协议标签交换MPLS回送请求或者MPLS回送应答。
  3. 根据权利要求2所述的方法，其中，在所述第一报文中携带有所述MPLS回送请求的情况下，在发起节点发送第一报文之后，还包括：
    所述发起节点接收所述接收节点根据验证结果返回的第二报文，并根据所述第二报文确认验证结果，其中，所述第二报文包括MPLS回送应答。
  4. 根据权利要求2所述的方法，其中，在所述第一报文中携带有所述MPLS回送应答的情况下，在所述发起节点发送第一报文之前，还包括：
    所述发起节点接收MPLS回送请求报文。
  5. 根据权利要求2所述的方法，其中，当所述第一报文中携带有所述MPLS回送请求时，
    所述发起节点发送第一报文，包括：
    所述发起节点发送所述第一报文至出口节点；
    所述发起节点接收所述出口节点根据验证结果返回的第二报文包括：
    所述发起节点接收并确认来自所述出口节点的验证结果，其中，所述验证结果为所述出口节点查询自身本地的表项，验证转发等价类FEC TLV的sub-TLV中的切片ID是否与本地的所述表项中的一致。
  6. 根据权利要求2所述的方法，其中，当第一报文中携带有所述MPLS回送请求时，
    所述发起节点发送第一报文，还包括：
    所述发起节点逐一发送所述第一报文至所述接收节点，待验证切片信息的MPLS标签触发各所述接收节点的切片信息验证，其中，所述MPLS回送请求中包含验证转发等价类FEC TLV，所述FEC TLV包含sub-TLV信息和/或下游数据映射DDM的TLV信息，所述sub-TLV信息中包含第一切片信息。
  7. 根据权利要求4所述的方法，其中，
    所述发起节点发送第一报文，包括：
    所述发起节点接收MPLS回送请求报文，所述MPLS回送请求报文中包含RP TLV，所述RP TLV中包含回复路径的转发等价类FEC信息，其中，所述FEC信息中包含第一切片信息；
    所述发起节点通过回复路径发送第一报文，其中，所述回复路径由所述接收节点根据所述FEC信息查找匹配，所述第一报文包括所述回复路径对应的MPLS标签栈及MPLS回送应答， 所述MPLS回送应答中包含所述RP TLV。
  8. 根据权利要求4所述的方法，其中，
    所述发起节点发送所述第一报文，还包括：
    所述发起节点接收MPLS回送请求报文，所述MPLS回送请求报文中的R标识置位；
    所述发起节点发送第一报文，其中，所述第一报文中的所述MPLS回送应答携带有反向路径目标转发等价类堆栈TLV，所述反向路径目标转发等价类堆栈TLV中携带第一切片信息。
  9. 一种切片信息的验证方法，用于段路由多协议标签交换SR-MPLS网络，包括：
    接收节点接收发起节点发送的第一报文，并验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致。
  10. 根据权利要求9所述的方法，其中，所述接收节点验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致需满足触发条件，其中，所述触发条件包括至少以下之一：
    IP报文头中包含路由器警报选项；
    IP生存时间TTL到期；
    MPLS生存时间TTL到期；
    标签为MPLS路由器警报标签；
    目的IP处于127/8范围内。
  11. 根据权利要求10所述的方法，其中，所述第一报文中还携带有多协议标签交换MPLS回送请求或者MPLS回送应答。
  12. 根据权利要求11所述的方法，其中，在所述第一报文中携带有所述MPLS回送请求的情况下，所述接收节点验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致之后，还包括：
    所述接收节点向所述发起节点返回第二报文，以便所述发起节点对所述验证结果的确认，其中，所述第二报文包括所述MPLS回送应答。
  13. 根据权利要求11所述的方法，其中，当所述第一报文中携带有所述MPLS回送请求时，
    所述接收节点接收发起节点发送的第一报文，还包括：
    所述接收节点与第一切片信息关联的段标识；
    所述接收节点本地生成所述段标识和所述第一切片信息的表项；
    所述接收节点验证所述第一切片信息与所述接收节点的本地信息是否一致包括：
    所述接收节点根据所述第一报文查询自身本地的所述表项，以验证转发等价类FEC TLV的sub-TLV信息中的切片ID是否均与本地的所述表项中的一致；
    所述接收节点将验证结果返回至所述发起节点，用于所述发起节点对所述验证结果确认，以确认所述第一切片信息是否验证通过。
  14. 根据权利要求11所述的方法，其中，当所述第一报文中携带有所述MPLS回送请求时，
    所述接收节点接收发起节点发送的第一报文，还包括：
    所述接收节点与第一切片信息关联的段标识；
    所述接收节点本地生成所述段标识和所述第一切片信息的表项；
    所述接收节点验证所述第一切片信息与所述接收节点的本地信息是否一致包括：
    所述接收节点根据所述第一报文，待验证切片信息的MPLS标签触发各所述接收节点的切片信息验证，其中，所述MPLS回送请求中包含验证转发等价类FEC TLV，所述FEC TLV包含sub-TLV信息和/或下游数据映射DDM的TLV信息，所述sub-TLV信息中包含第一切片信息。
  15. 根据权利要求11所述的方法，其中，当所述第一报文中携带有所述MPLS回送应答时，
    所述接收节点接收发起节点发送的第一报文，还包括：
    所述接收节点接收所述发起节点通过回复路径发送的第一报文，其中，所述回复路径由所述接收节点根据转发等价类FEC信息查找匹配，所述第一报文包括所述回复路径对应的MPLS标签栈及MPLS回送应答，所述MPLS回送应答中包含RP TLV，所述RP TLV中包含回复路径的所述FEC信息，其中，所述FEC信息中包含第一切片信息。
  16. 根据权利要求11所述的方法，其中，所述接收节点接收发起节点发送的第一报文，还包括：
    所述接收节点接收所述第一报文，其中，所述第一报文中的所述MPLS回送应答携带有反向路径目标转发等价类堆栈TLV，所述反向路径目标转发等价类堆栈TLV中携带第一切片信息。
  17. 一种切片信息的验证装置，用于段路由多协议标签交换SR-MPLS网络，包括：
    发起模块，设置为发送第一报文，其中，所述第一报文携带有待验证的切片信息，以便接收节点验证所述第一报文中携带的所述切片信息与所述接收节点的本地信息是否一致。
  18. 根据权利要求17所述的装置，其中，所述第一报文中携带有多协议标签交换MPLS回送请求或者MPLS回送应答。
  19. 根据权利要求18所述的装置，还包括：
    验证模块，设置为在所述第一报文中携带有所述MPLS回送请求时，接收并确认来自出口节点的验证结果，以检测路径是否连通，其中，所述验证结果为所述出口节点查询自身本地的表项，验证转发等价类FEC TLV的sub-TLV中的切片ID是否均与本地的所述表项中的一致。
  20. 根据权利要求18所述的装置，其中，在所述第一报文中携带有所述MPLS回送请求 的情况下，
    所述发起模块还设置为，逐一发送所述第一报文至所述接收节点，待验证切片信息的MPLS标签触发各所述接收节点的切片信息验证，其中，所述MPLS回送请求中包含验证转发等价类FEC TLV，所述FEC TLV包含sub-TLV信息和/或下游数据映射DDM的TLV信息，所述sub-TLV信息中包含第一切片信息。
  21. 根据权利要求18所述的装置，其中，在所述第一报文中携带有所述MPLS回送应答的情况下，
    所述发起模块还设置为，接收MPLS回送请求报文，所述MPLS回送请求报文中包含RP TLV，所述RP TLV中包含回复路径的转发等价类FEC信息，其中，所述FEC信息中包含第一切片信息；
    所述发起模块还设置为通过回复路径发送第一报文，其中，所述回复路径由所述接收节点根据所述FEC信息查找匹配，所述第一报文包括所述回复路径对应的MPLS标签栈及MPLS回送应答，所述MPLS回送应答中包含所述RP TLV。
  22. 根据权利要求18所述的装置，其中，所述发起模块还设置为，
    接收MPLS回送请求报文，所述MPLS回送请求报文中的R标识置位；
    发送第一报文，其中，所述第一报文中的所述MPLS回送应答携带有反向路径目标转发等价类堆栈TLV，所述反向路径目标转发等价类堆栈TLV中携带第一切片信息。
  23. 一种切片信息的验证装置，用于段路由多协议标签交换SR-MPLS网络，包括：
    接收模块，设置为接收发起节点发送的第一报文，并验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致。
  24. 根据权利要求23所述的装置，其中，所述接收模块包括：
    判断子模块，设置为在所述接收节点验证所述第一报文中携带的切片信息与所述接收节点的本地信息是否一致之前，判断所述接收节点是否满足触发条件，其中，所述触发条件包括至少以下之一：IP报文头中包含路由器警报选项；IP生存时间TTL到期；MPLS生存时间TTL到期；标签为MPLS路由器警报标签；目的IP处于127/8范围内。
  25. 一种计算机可读存储介质，所述计算机可读存储介质中存储有计算机程序，其中，所述计算机程序被处理器执行时实现所述权利要求1至16任一项中所述的方法。
  26. 一种电子装置，包括存储器、处理器以及存储在所述存储器上并可在所述处理器上运行的计算机程序，其中，所述处理器执行所述计算机程序时实现所述权利要求1至16任一项中所述的方法。
PCT/CN2023/072696 2022-06-10 2023-01-17 切片信息的验证方法及装置 WO2023236544A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210658976.2A CN117255034A (zh) 2022-06-10 2022-06-10 切片信息的验证方法及装置
CN202210658976.2 2022-06-10

Publications (1)

Publication Number Publication Date
WO2023236544A1 true WO2023236544A1 (zh) 2023-12-14

Family

ID=89117484

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/072696 WO2023236544A1 (zh) 2022-06-10 2023-01-17 切片信息的验证方法及装置

Country Status (2)

Country Link
CN (1) CN117255034A (zh)
WO (1) WO2023236544A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110266594A (zh) * 2019-06-28 2019-09-20 Ut斯达康通讯有限公司 跨网络切片的分段路由转发方法及装置
CN112311673A (zh) * 2019-07-24 2021-02-02 瞻博网络公司 在采用分段路由的网络中使用和处理每切片分段标识符
US20210153079A1 (en) * 2019-11-14 2021-05-20 Huawei Technologies Co., Ltd. Resource Allocation Method, Apparatus, and System, and Storage Medium
CN112995030A (zh) * 2021-02-07 2021-06-18 中兴通讯股份有限公司 一种业务处理方法、装置、存储介质及电子装置
CN113411258A (zh) * 2021-06-07 2021-09-17 新华三技术有限公司 报文处理方法及装置
US20220174004A1 (en) * 2020-12-01 2022-06-02 Cisco Technology, Inc. Methods and apparatus for encoding local processing metadata in network headers

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110266594A (zh) * 2019-06-28 2019-09-20 Ut斯达康通讯有限公司 跨网络切片的分段路由转发方法及装置
CN112311673A (zh) * 2019-07-24 2021-02-02 瞻博网络公司 在采用分段路由的网络中使用和处理每切片分段标识符
US20210153079A1 (en) * 2019-11-14 2021-05-20 Huawei Technologies Co., Ltd. Resource Allocation Method, Apparatus, and System, and Storage Medium
US20220174004A1 (en) * 2020-12-01 2022-06-02 Cisco Technology, Inc. Methods and apparatus for encoding local processing metadata in network headers
CN112995030A (zh) * 2021-02-07 2021-06-18 中兴通讯股份有限公司 一种业务处理方法、装置、存储介质及电子装置
CN113411258A (zh) * 2021-06-07 2021-09-17 新华三技术有限公司 报文处理方法及装置

Also Published As

Publication number Publication date
CN117255034A (zh) 2023-12-19

Similar Documents

Publication Publication Date Title
US11265241B2 (en) Path detection method and apparatus
US10581732B2 (en) Target FEC (forwarding equivalence class) stack based FEC query in segment routing environments
US9860150B2 (en) Fast convergence of EVPN networks for multi homing topologies
CN107147508B (zh) 故障检测方法及装置
US20220407802A1 (en) Packet processing method and apparatus, network device, and storage medium
US9497107B1 (en) Seamless path monitoring and rapid fault isolation using bidirectional forwarding detection in a network environment
CN109921987B (zh) 一种bier-te网络检测方法、装置及系统
CN109076018B (zh) 利用is-is协议实现分段路由网络中网元的方法和设备
CN108604997B (zh) 用于对差异化服务编码点(dscp)和显式拥塞通知(ecn)的监视进行配置的控制平面的方法和设备
CN108604999B (zh) 用于监视差异化服务编码点(dscp)和显式拥塞通知(ecn)的数据平面方法和设备
US10574563B2 (en) Seamless bidirectional forwarding detection discriminator based return path determination
US20210119906A1 (en) Loop Avoidance Communications Method, Device, and System
JP7430224B2 (ja) パケット処理方法およびゲートウェイ・デバイス
EP2961117A1 (en) Method, device and system for establishing label switched path
EP3767900B1 (en) Method for discovering forwarding path, and related device thereof
WO2017175033A1 (en) Method and apparatus for enabling non stop routing (nsr) in a packet network
WO2023236544A1 (zh) 切片信息的验证方法及装置
EP3151486A1 (en) Fast convergence of evpn networks for multi homing topologies
WO2023011200A1 (zh) 信息验证方法及装置、存储介质和电子装置
WO2023050817A1 (zh) 确定报文传输路径故障的方法以及装置
EP4383667A1 (en) Information verification method and device, storage medium, and electronic device
CN113132220A (zh) 一种路由信息的处理方法及装置

Legal Events

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

Ref document number: 23818712

Country of ref document: EP

Kind code of ref document: A1