WO2021189973A1 - 信息发送和处理的方法、节点、控制器、计算机可读介质 - Google Patents

信息发送和处理的方法、节点、控制器、计算机可读介质 Download PDF

Info

Publication number
WO2021189973A1
WO2021189973A1 PCT/CN2020/136214 CN2020136214W WO2021189973A1 WO 2021189973 A1 WO2021189973 A1 WO 2021189973A1 CN 2020136214 W CN2020136214 W CN 2020136214W WO 2021189973 A1 WO2021189973 A1 WO 2021189973A1
Authority
WO
WIPO (PCT)
Prior art keywords
srv6
capability
segment
information
compressed
Prior art date
Application number
PCT/CN2020/136214
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/914,437 priority Critical patent/US20230353492A1/en
Publication of WO2021189973A1 publication Critical patent/WO2021189973A1/zh

Links

Images

Classifications

    • 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]
    • 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/74—Address processing for routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/04—Protocols for data compression, e.g. ROHC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/659—Internet protocol version 6 [IPv6] addresses

Definitions

  • the embodiments of the present disclosure relate to the technical field of segment routing, and in particular to an information sending method, an information processing method, a node, a controller, and a computer-readable medium.
  • IPv6 Internet Protocol Version 6
  • SRv6 Internet Protocol Version 6 Segment Routing
  • the embodiments of the present disclosure provide a method for sending information, a method for processing information, a node, a controller, and a computer-readable medium.
  • an embodiment of the present disclosure provides a method for sending information for a node, and the method includes:
  • the capability announcement information is used to indicate that the node supports the capability of the compressed Internet Protocol version 6 segment routing SRv6 segment identifier.
  • the capability of the node to support compressed SRv6 segment identifiers includes at least one of the following:
  • the node supports the compressed SRv6 segment identifier
  • the SRv6 segment identifies the correspondence between the block information and the SRv6 type.
  • the sending capability announcement information includes:
  • the capability notification information is sent.
  • the capability announcement information includes at least one of the following:
  • the sending capability announcement information includes sending capability announcement information according to the intermediate system-to-intermediate system protocol; the capability announcement information includes at least one of the following:
  • the sending capability announcement information includes sending capability announcement information according to the open shortest path first protocol; the capability announcement information includes at least one of the following:
  • the SRv6 compression capability sub-TLV in the SRv6 capability TLV of the third version of the shortest path first protocol routing information link state announcement is a SRv6 compression capability sub-TLV in the SRv6 capability TLV of the third version of the shortest path first protocol routing information link state announcement.
  • the sending capability announcement information includes sending capability announcement information according to the border gateway-connection state protocol; the capability announcement information includes at least one of the following:
  • the sending capability announcement information includes sending the capability announcement information according to the path calculation unit protocol; the capability announcement information includes at least one of the following: the compression capability identifier in the SRv6 path calculation unit capability sub-TLV of the Open message; SRv6 compression capability sub-TLV of Open message;
  • the stateful path calculation unit requests that the parameter object includes a compressed path identifier, which is used to indicate that the path establishment type is a compressed SRv6 segment identifier path.
  • the method further includes:
  • the segment identification information includes SRv6 segment identification information
  • the segment routing header is encapsulated.
  • the segment identification information includes SRv6 segment identification and corresponding compression related information
  • the encapsulated segment routing header includes: determining whether to compress at least part of the SRv6 segment identifier and encapsulating the segment routing header according to the capability announcement information, the SRv6 segment identifier, and corresponding compression related information.
  • the determining whether to compress at least part of the SRv6 segment identifier and the encapsulated segment routing header includes:
  • the segment identification information includes a compressed SRv6 segment identifier
  • the encapsulated segment routing header includes: at least according to the compressed SRv6 segment identifier, the encapsulated segment routing header.
  • embodiments of the present disclosure provide an information processing method for a controller, including:
  • the capability announcement information is used to indicate the capability of the node to support the compressed SRv6 segment identifier
  • the segment identification information includes SRv6 segment identification information.
  • the segment identification information includes SRv6 segment identification and corresponding compression related information.
  • the compression-related information includes at least one of the following:
  • the compressed correspondence of each SRv6 segment identifier is the correspondence between the length of the block of the SRv6 segment identifying the identification position of the network node and the compressed length.
  • the compression-related information includes at least one of the following items carried by each SRv6 segment identifier:
  • the SRv6 segment identifies the length of the node identifier of the identifier position of the network node
  • the method before the sending segment identification information, the method further includes:
  • the sending segment identification information includes: sending compressed segment identification information with a compressed SRv6 segment identifier.
  • a node which includes:
  • the first sending module is configured to send capability announcement information; the capability announcement information is used to indicate the capability of the node to support the compressed SRv6 segment identifier.
  • the node further includes:
  • the first receiving module is configured to receive segment identification information sent by the controller; the segment identification information includes SRv6 segment identification information;
  • One or more processors configured to encapsulate the segment routing header according to the segment identification information.
  • an embodiment of the present disclosure provides a controller, which includes:
  • the second receiving module is configured to receive capability announcement information sent by a node; the capability announcement information is used to indicate the capability of the node to support the compressed SRv6 segment identifier;
  • the second sending module is configured to send segment identification information; the segment identification information includes SRv6 segment identification information.
  • an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing information sending methods is implemented.
  • embodiments of the present disclosure provide a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing information processing methods is implemented.
  • the embodiments of the present disclosure can achieve complete control face support for compressed SRv6 segment identifiers, and expand the practical application of compressed SRv6 segment identifiers.
  • FIG. 1 is a flowchart of a method for sending information according to an embodiment of the disclosure
  • FIG. 2 is a flowchart of another method for sending information according to an embodiment of the disclosure
  • FIG. 3 is a flowchart of some steps in another method for sending information provided by an embodiment of the disclosure.
  • FIG. 5 is a flowchart of an information processing method provided by an embodiment of the disclosure.
  • FIG. 6 is a flowchart of another information processing method provided by an embodiment of the disclosure.
  • FIG. 7 is a block diagram of the composition of a node provided by an embodiment of the present disclosure.
  • FIG. 8 is a block diagram of another type of node provided by an embodiment of the present disclosure.
  • FIG. 9 is a block diagram of the composition of a controller provided by an embodiment of the disclosure.
  • FIG. 10 is a block diagram of the composition of a computer-readable medium provided by an embodiment of the present disclosure.
  • FIG. 11 is a block diagram of the composition of an SRv6 network provided by an embodiment of the disclosure.
  • FIG. 12 is a schematic diagram of a format of a TLV provided by an embodiment of the disclosure.
  • FIG. 13 is a schematic diagram of the format of another TLV provided by an embodiment of the present disclosure.
  • FIG. 14 is a schematic diagram of the format of another TLV provided by an embodiment of the present disclosure.
  • FIG. 15 is a schematic diagram of another TLV format provided by an embodiment of the disclosure.
  • Segment Routing is an extended source routing technology.
  • the principle is that the source node (head node) encapsulates the Segment List (segment list) carrying routing information instructions in the header of the message to indicate the follow-up How the intermediate node processes the message, so that the message passes through the network along a predetermined path, without the need to maintain path status information on the intermediate node.
  • SR can realize IPv6 (Internet Protocol Version 6) address encapsulation on the data plane, which is SRv6 (Internet Protocol Version 6 Segment Routing) technology.
  • SRv6 defines an extended segment routing header (Segment Routing Header, referred to as SRH) in the message header, and uses an IPv6 address as a segment ID (Segment ID, referred to as SID) in the SRH.
  • the SRv6 network may include multiple nodes, among which at least the head node and the node node can transmit information with the controller.
  • the IPv6 address Since the IPv6 address has a large length of 128 bits, it will cause excessive encapsulation overhead of the SRv6 packet header. For example, when the SRH carries even more than 10 SIDs, the length of the SID list alone exceeds 160 Bytes. For a message with an average payload of 256 Bytes, the encapsulation overhead is about 50%.
  • SRv6 SID SRv6 segment identifier
  • the compressed SRv6 SID can also be referred to as a "short identification", that is, “compression” can also be understood as a transformation of the format of the SRv6 SID.
  • the standard 128-bit SRv6 SID includes fixed parts such as address blocks and changes to the corresponding Node ID (node ID) and Function ID (function ID), which is also called a complete SRv6 SID.
  • the compressed SRv6 SID can only include the changed part of the standard SRv6 SID, such as Node ID, Function ID, and optional Argument (argument), so that the compressed SRv6 SID alone is shorter than 128 bits.
  • the length of the compressed SRv6 SID is called the "compressed length" of the SRv6 SID, that is, the length when the standard SRv6 SID is in compressed form (short identifier); and multiple compressed SRv6 SIDs are combined with a common prefix/address block, etc. , Can form a standard SRv6 SID.
  • a SRv6 SID compression scheme defines a new uSID (Micro SID), which supports dividing a 128-bit IPv6 address (SRv6 SID) into 8 parts, the first part is used to represent uSID block information, and the other 7 parts are each The share is used to represent a compressed uSID, thereby increasing the packaging efficiency of 128-bit SRv6 SID by 7 times.
  • the embodiments of the present disclosure provide a method for sending information for a node.
  • the nodes in the embodiments of the present disclosure are nodes of the SRv6 network, in which at least the head node and the tail node can communicate information with the controller.
  • the method of the embodiment of the present disclosure includes:
  • the capability announcement information is used to indicate the capability of the node to support the compressed SRv6 SID (ie, the "compression capability" of the node).
  • the current node (such as the head node) sends specific capability notification information to the controller or other nodes (such as intermediate nodes) to "notify” the controller or other nodes that they have compression capabilities, that is, they can support (or handle) compression.
  • SRv6 SID (or short identifier).
  • the support for compressed SRv6 SID is realized on the control plane.
  • each node in the SRv6 network is essentially equivalent, and any node can implement the method of the embodiments of the present disclosure, that is, each node may send capability announcement information, or may receive capability announcements from other nodes. information. Therefore, each node may act as a head node in some cases, or may act as an intermediate node in other cases.
  • sending capability announcement information includes: according to the interior gateway protocol (IGP protocol), the border gateway protocol (BGP protocol), the path calculation unit communication protocol (PCE protocol), the border gateway-connection state protocol (BGP-LS protocol) Any one of the following), send capability announcement information.
  • IGP protocol interior gateway protocol
  • BGP protocol border gateway protocol
  • PCE protocol path calculation unit communication protocol
  • BGP-LS protocol border gateway-connection state protocol
  • the capability announcement can be implemented according to the above specific protocols, and the protocols listed above are only exemplary, and are not limited to the control plane protocols applicable to the embodiments of the present disclosure.
  • the capability of supporting compressed SRv6 SID includes at least one of the following:
  • the node supports compressed SRv6 SID
  • the compression capabilities can include: the node supports compressed SRv6 SID, which means that the node can support compressed SRv6 SID; the SRv6 SID compression type supported by the node, which means that the node can support what types of SRv6 SID compression; SRv6 SID block
  • the correspondence between the information and the SRv6 type that is, the correspondence between the block information of the SRv6 SID and the SRv6 type.
  • the SRv6 type includes SRv6 or compressed SRv6, and compressed SRv6 is 16bit, 32bt, 64bt Which type to wait for; and SRv6 SID block can be 48bit, 64bit, 96bit and other forms.
  • the notification of the above compression capability can be realized through the above various formats.
  • the capability announcement information includes at least one of the following:
  • the protocol may be specifically modified to expand a new flag indicating the compression capability (Flag) in the existing TLV or sub-TLV, that is, the compression capability identifier.
  • the compression capability identifier may be a specific field (Flag).
  • the protocol may be modified to expand a new compression capability TLV or compression capability sub-TLV indicating the compression capability.
  • the compression capability identifier, the compression capability TLV, and the compression capability sub-TLV are forms of capability announcement information, and each form has no inevitable limiting relationship with the content of the compression capability it represents.
  • C field compression capability identifier
  • it can indicate whether the node supports compressed SRv6 SID, or it can also indicate the specific SRv6 SID compression type supported by the node. .
  • a compression capability sub-TLV can be extended in a certain TLV to indicate that the node supports compressed SRv6 SID, and/or the SRv6 SID compression type supported by the node.
  • a compression capability sub-TLV can be extended in a TLV to indicate a correspondence between SRv6 SID block information and SRV6 type.
  • the SRv6 type includes SRv6 or compressed SRv6, and
  • the compressed SRv6 is of 16bit, 32bt, 64bt, etc.; and
  • the SRv6 SID block can be of 48bit, 64bit, 96bit, etc.
  • each capability announcement message there may be only one compression capability identifier, SRv6 compression capability TLV, and SRv6 compression capability sub-TLV.
  • SRv6 compression capability TLV For example, referring to Figure 12, only the compression capability identifier (C field) exists, or multiple , As shown in FIG. 13, there are both the compression capability identifier (C field) and the SRv6 compression capability sub-TLV.
  • SRv6 compression capability TLV when there are multiple items of compression capability identifier, SRv6 compression capability TLV, and SRv6 compression capability sub-TLV in each capability announcement information, the meanings of different items may be different from each other, or they may overlap.
  • the following gives an exemplary introduction to the specific form of the capability announcement information when the capability announcement information is sent according to some specific protocols.
  • sending the capability announcement information includes sending the capability announcement information according to the Intermediate System to Intermediate System Protocol (ISIS protocol); the capability announcement information includes at least one of the following:
  • ISIS protocol Intermediate System to Intermediate System Protocol
  • the capability announcement information may specifically include an expanded (newly added) compression capability identifier in the SRv6 capability sub-TLV of its routing capability TLV, or an expanded (newly added) SRv6 compression capability sub-TLV.
  • the compression capability identifier may only indicate whether the node supports compressed SRv6 SID, or it may also indicate the SRv6 SID compression type supported by the node.
  • the SRv6 compression capability sub-TLV can be used to indicate a correspondence between SRv6 SID block information and SRV6 types.
  • SRv6 types include general SRv6 or compressed SRv6, and compressed SRv6 which is 16bit, 32bt, 64bt, etc. Type; and SRv6 SID block can be 48bit, 64bit, 96bit and other forms.
  • sending the capability announcement information includes sending the capability announcement information according to the Open Shortest Path First Protocol (OSPF protocol); the capability announcement information includes at least one of the following:
  • OSPF protocol Open Shortest Path First Protocol
  • the capability announcement information may specifically include the expanded (new) compression capability identifier in the SRv6 capability TLV of the OSPFv3 Router Information LSA, and may also include the expanded (new) SRv6 compression capability sub-TLV.
  • the compression capability identifier may only indicate whether the node supports compressed SRv6 SID, or it may also indicate the SRv6 SID compression type supported by the node.
  • the SRv6 compression capability sub-TLV can be used to indicate a correspondence between SRv6 SID block information and SRV6 types.
  • SRv6 types include general SRv6 or compressed SRv6, and compressed SRv6 which is 16bit, 32bt, 64bt, etc. Type; and SRv6 SID block can be 48bit, 64bit, 96bit and other forms.
  • sending the capability announcement information includes sending the capability announcement information according to the BGP-LS protocol; the capability announcement information includes at least one of the following:
  • the capability announcement information may specifically include an expanded (newly added) compression capability identifier in the SRv6 capability TLV of the SRv6 node attribute, or an expanded (newly added) SRv6 compression capability sub-TLV.
  • the compression capability identifier may only indicate whether the node supports compressed SRv6 SID, or it may also indicate the SRv6 SID compression type supported by the node.
  • the SRv6 compression capability sub-TLV can be used to indicate a correspondence between SRv6 SID block information and SRV6 types.
  • SRv6 types include general SRv6 or compressed SRv6, and compressed SRv6 which is 16bit, 32bt, 64bt, etc. Type; and SRv6 SID block can be 48bit, 64bit, 96bit and other forms.
  • sending the capability announcement information includes sending the capability announcement information according to the PCE protocol; the capability announcement information includes at least one of the following: the compression capability identifier in the SRv6 path calculation unit capability sub-TLV of the Open message; the SRv6 compression capability of the Open message Child TLV;
  • the capability announcement information can specifically include the SRv6 path calculation unit capability sub-TLV (SRv6 PCE Capability sub-TLV) in the open message advertised between the PCC (path calculation client) and the PCE (path calculation unit)
  • SRv6 PCE Capability sub-TLV SRv6 path calculation unit capability sub-TLV
  • the compression capability identifier may only indicate whether the node supports compressed SRv6 SID, or it may also indicate the SRv6 SID compression type supported by the node.
  • the SRv6 compression capability sub-TLV can be used to indicate a correspondence between SRv6 SID block information and SRV6 types.
  • SRv6 types include general SRv6 or compressed SRv6, and compressed SRv6 which is 16bit, 32bt, 64bt, etc. Type; and SRv6 SID block can be 48bit, 64bit, 96bit and other forms.
  • the stateful path calculation unit requests that the parameter object includes a compressed path identifier, which is used to indicate that the path establishment type is a compressed SRv6 SID path.
  • the stateful path calculation unit request parameter object (SRP Object, Stateful PCE Request Parameters object) can also be extended, and the compressed path identifier is added to it, and the added compressed path identifier is used to indicate the path calculation request or the path calculation result
  • the compressed SRv6 SID path should be delivered.
  • the method further includes:
  • S102 Receive SID information sent by the controller; the SID information includes SRv6 SID information.
  • the node After sending the capability announcement information, it may receive the SID information from the controller.
  • the SID information reflects the SRv6 SID information (but the specific form may be different). Therefore, the node can encapsulate the SRH according to the SID information, add the SRH to the SR message, and then send the SR message.
  • the SRv6 SIDs in the SID information sent by the controller are all standard (128bit), but at the same time, the SID information also contains information related to the compression of these SRv6 SIDs (compression related information). ), at this time, the node needs to perform SRv6 SID compression.
  • SID information includes SRv6 SID and corresponding compression related information;
  • encapsulating SRH (S103) includes:
  • the SRv6 SID determines whether to compress at least part of the SRv6 SID and then encapsulate the SRH.
  • the node After the node receives the standard SRv6 SID, it can decide whether to directly use the standard SRv6 SID to encapsulate the SRH or to use the compressed SRv6 SID to encapsulate the SRH according to the corresponding compression related information.
  • encapsulating SRH with compressed SRv6 SID can compress all SRv6 SIDs and then encapsulate SRH; it can also compress only part of SRv6 SIDs and encapsulate SRH, while other SRv6 SIDs directly encapsulate SRH without compression, which is the final SRH.
  • Some SRv6 SIDs may be compressed, while some SRv6 SIDs are not compressed.
  • determining whether to compress at least part of the SRv6 SID and encapsulating the SRH includes:
  • Judgment criterion 1 If there are multiple SRv6 SIDs in the same block and the compression length is the same, it is determined to compress the multiple SRv6 SIDs and encapsulate the SRH;
  • Judgment criterion 2 If there are multiple SRv6 SIDs in the same block, it is determined that the multiple SRv6 SIDs are compressed and the SRH is encapsulated.
  • One criterion for judging is: if multiple SRv6 SIDs are in the same block, and their compressed lengths (ie, compressed lengths) are the same, they are compressed and encapsulated into SRH.
  • the multiple SRv6 SIDs at this time may also be all SRv6 SIDs.
  • another judgment criterion may be: as long as multiple SRv6 SIDs are in the same block, the compression length is not considered, and they are compressed and encapsulated into the SRH.
  • the multiple SRv6 SIDs at this time may also be all SRv6 SIDs.
  • judgment criterion 2 can be used, and judgment criterion 1 can be used when cross-domain.
  • At least a part of the SRv6 SID of the above SID information sent by the controller is compressed (or in short format), so the controller can directly encapsulate these compressed SRv6 SIDs into the SRH middle.
  • the SID information includes compressed SRv6 SID; according to the SID information, encapsulating SRH (S103) includes:
  • the node can directly encapsulate the compressed SRv6 SID in the SID information.
  • the SID information also includes standard SRv6 SIDs
  • these SRv6 SIDs may be encapsulated in a standard manner, or it may be determined whether to compress them and encapsulate them according to the above step S1031.
  • embodiments of the present disclosure provide an information processing method for a controller.
  • the controller in the embodiment of the present disclosure is the controller of the SRv6 network.
  • the SRv6 network includes multiple nodes, and different nodes can transfer information, among which at least the head node and the tail node can transfer information with the controller.
  • the method of the embodiment of the present disclosure includes:
  • S201 Receive capability announcement information sent by a node; the capability announcement information is used to indicate the capability of the node to support the compressed SRv6 SID.
  • S202 Send SID information; the SID information includes SRv6 SID information.
  • the controller receives the capability announcement information sent by the above node, and learns that the node can support compressed SRv6 SID information, so that it can send SID information to the node for the node to encapsulate the SRH.
  • the controller may send the standard SRv6 SID to the node, and at the same time carry corresponding compression related information, so that the node can decide whether to use the compressed SRv6 SID to encapsulate the SRH.
  • the SID information includes SRv6 SID and corresponding compression related information.
  • the compression-related information includes at least one of the following:
  • the compressed correspondence of each SRv6 SID; the compressed correspondence of SRv6 SID is the correspondence between the length of the block at the identification position of the SRv6 SID network node and the compressed length.
  • compression related information may include the above content.
  • the compression indication indicates that the SRH needs to be encapsulated with compressed SRv6 SID.
  • Each length represents the corresponding length information.
  • the identification location of the network node is the identification assigned to a network node in the network topology, indicating the location information of the node, which is used to route and forward the message to the node
  • the block is the address block to which the SID is allocated.
  • the start and end positions of the SRv6 SID where the compressed information is changed are the positions of the SRv6 SID where the compressed information is changed. For example, they may be the start and end positions of the compressed SRv6 SID.
  • the compressed correspondence of SRv6 SID is the correspondence between the length of the block at the identification position of the SRv6 SID network node and the compressed length (for example, the ratio value, or the "type" of the relationship).
  • each piece of SID information there may be only one compression indication.
  • the position of the start SRv6 SID where the compressed information changes and the position of the end SRv6 SID where the compressed information changes may be separate position information, or may be for the corresponding SRv6 SID.
  • the compression-related information includes at least one of the following items carried by each SRv6 SID:
  • the compression-related information sub-TLV can be expanded (added) after each SRv6 SID, and referring to FIG. 14, the compression-related information sub-TLV can include the above lengths.
  • the compressed correspondence of the above SRv6 SID can also be an identifier, which is directly carried (extended) in the TLV of the SRv6 SID.
  • the SID information can also be extended (added) to indicate the compression type of segment routing sub-TLV (Segment Sub-TLV), which carries the standard SRv6 SID, and the extended (new) L field to indicate SRv6 SID is the start position or end position where the compressed information changes. That is, the specific form of the start position identifier where the compressed information changes and the end position identifier where the compressed information changes may be specific fields (such as the L field) in the segment routing sub-TLV.
  • Segment Sub-TLV Segment Sub-TLV
  • L field to indicate SRv6 SID is the start position or end position where the compressed information changes.
  • the controller may first obtain the compressed SRv6 SID, and send the compressed SRv6 SID to the node, so that the node can directly use the compressed SRv6 SID to encapsulate the SRH.
  • the method before sending the SID information (S202), the method further includes:
  • SID information includes:
  • S2021 Send compressed SID information with compressed SRv6 SID.
  • the controller collects SRv6 network topology information, topological attributes, and SRv6 SID reachability related information, and then based on the collected information, calculates SRv6 paths and compresses at least part of SRv6 SIDs in path compression, and compresses them
  • the SRv6 SID is sent to the node (such as the head node), so the SID information sent at this time is the compressed SID information.
  • the controller may implement the collection of network topology information, topology attributes, and attributes related to SRv6 SID reachability through the BGP-LS protocol.
  • SRv6 SID reachability related attributes can actually include the above compression related information.
  • the controller may send the SID information to the node through the BGP protocol or the PCE protocol.
  • the controller advertises the SID information to the node through the BGP protocol.
  • the controller notifies the node of SID information through the PCE protocol.
  • the Explicit Route Object (ERO for short) in the extended PCE protocol carries a compression indication identifier (the C field in the figure) and a compressed SRv6 SID, where the compression indication identifier is used to indicate this SRv6 SID is compressed.
  • the SR Policy (segment routing policy) implements the traffic engineering intent through the Segment List (segment list).
  • the Segment List encodes any forwarding path of the message in the network.
  • the SR Policy is identified by the head-color-endpoint triplet; on a given head-end node, the SR Policy is identified by the color-endpoint 2-tuple.
  • the SR Policy requires at least one candidate path, and the Candidate Path of the SR Policy represents a specific way of transmitting the message from the corresponding SR Policy head end to the endpoint.
  • Each candidate path has a preference value (Preference). The higher the preference value of the path, the more preferable.
  • the effective candidate path with the highest preference value is the active candidate path, that is, the Segment List of SR Policy is the Segment List of its active path.
  • Each candidate path can have one or more segment lists, and each segment list has an associated load balancing weight. The traffic directed to this path is load balanced among all valid Segment Lists according to the weight ratio.
  • the BGP protocol is used to advertise the candidate path of the SR policy to the head node, but the candidate path of the compressed SR policy cannot be advertised through the BGP protocol.
  • the node announces the SRv6 compression capability.
  • the node announces the compression capability of the SRv6 SID that supports compression by sending the above capability announcement information.
  • the compression capability specifically includes at least one of the following: the SRv6 SID that the node supports compression, the SRv6 SID compression type that the node supports, the correspondence between SRv6 SID block information and the SRv6 type, and so on.
  • SRv6 types include general SRv6 or compressed SRv6, and the compressed SRv6 is 16bit, 32bt, 64bt, etc.; and SRv6 SID block can be 48bit, 64bit, 96bit and other forms.
  • the capability announcement information specifically includes at least one of the following: compression capability identifier, SRv6 compression capability TLV, SRv6 compression capability sub-TLV, and so on.
  • S302 The controller notifies the SRv6 SID and corresponding compression related information to the head node.
  • the controller After the controller receives the capability announcement information, it sends the SID information to the head node.
  • the controller may send a Segment List, and the Segment List contains multiple SRv6 SIDs and compression related information corresponding to each extended SRv6 SID.
  • the compression-related information specifically includes at least one of the following: compression indication, the position of the start SRv6 SID where the compressed information changes, the position of the end SRv6 SID where the compressed information changes, and the block of the identification position of each SRv6 SID network node.
  • the length, the length of the node identification of each SRv6 SID network node identification position, the compression length of each SRv6 SID, the compression correspondence relationship of each SRv6 SID, the compression correspondence relationship of SRv6 SID is the block of the identification position of the SRv6 SID network node The corresponding relationship between the length of and the compressed length.
  • the head node judges whether to use compressed SRv6 SID to encapsulate the SRH.
  • the head node determines whether to use compressed SRv6 SID to encapsulate SRH according to the received SID information.
  • the specific judgment conditions may include:
  • Judgment criterion 1 If there are multiple SRv6 SIDs in the same block and the compression length is the same, it is determined to compress the multiple SRv6 SIDs and encapsulate the SRH;
  • Judgment criterion 2 If there are multiple SRv6 SIDs in the same block, it is determined that the multiple SRv6 SIDs are compressed and the SRH is encapsulated.
  • judgment criterion 2 can be used, and judgment criterion 1 can be used when cross-domain.
  • the node announces the SRv6 compression capability.
  • S402 The controller notifies the SRv6 SID and corresponding compression related information to the head node.
  • the controller After the controller receives the capability announcement information, it sends the SID information to the head node.
  • the SID information can be extended (newly added) to indicate the compressed type of segment routing sub-TLV, which carries the standard SRv6 SID, and the extended (newly added) L field is used to indicate that the SRv6 SID is compressed information.
  • S403 The head node judges whether to use compressed SRv6 SID to encapsulate the SRH.
  • Another specific embodiment of the present disclosure may support single-domain or cross-domain scenarios, but is generally used in cross-domain scenarios, which specifically includes:
  • S501 The controller receives the capability announcement information sent by the node.
  • the controller collects related information such as topology information, topology attributes, and attributes related to SRv6 SID reachability of the SRv6 network.
  • the controller may implement the collection of network topology information, topology attributes, and attributes related to SRv6 SID reachability through the BGP-LS protocol.
  • SRv6 SID reachability related attributes can actually include the above compression related information.
  • the controller calculates the SRv6 path and compresses at least part of the SRv6 SID in the path compression based on the collected topology information, topology attributes, and SRv6 SID reachability related information of the SRv6 network.
  • the controller After calculating the path, the controller sends the compressed SID information containing the compressed SRv6 SID to the head node through the BGP protocol or the PCE protocol.
  • the controller advertises the SID information to the node through the BGP protocol.
  • the controller notifies the node of SID information through the PCE protocol.
  • the ERO in the extended PCE protocol carries a compression indication identifier (the C field in the figure) and a compressed SRv6 SID, where the compression indication identifier is used to indicate that the SRv6 SID is compressed.
  • the node encapsulates the SRH at least according to the compressed SRv6 SID.
  • the forwarding device when the compressed SRv6 SID is a 32-bit short identifier, the forwarding device (intermediate node) needs to have a correspondence between the 32-bit short identifier and IPv6.
  • the node announces the mapping relationship between the compressed SRv6 SID and IPv6 through the IGP protocol according to the method of the embodiment of the present disclosure.
  • the embodiments of the present disclosure provide a node, which is used to implement any one of the foregoing information sending methods.
  • the node of the embodiment of the present disclosure includes:
  • the first sending module is configured to send capability announcement information; the capability announcement information is used to indicate the capability of the node to support the compressed SRv6 SID.
  • the node in the embodiment of the present disclosure may actually be any node in the SRv6 network, that is, each node may perform the step of sending capability announcement information, and may also receive the sending capability announcement information sent by other nodes.
  • the node further includes:
  • the first receiving module is configured to receive SID information sent by the controller; the SID information includes SRv6 SID information;
  • One or more processors are configured to encapsulate the SRH according to the SID information.
  • embodiments of the present disclosure provide a controller, which is used to implement any of the foregoing information processing methods
  • the controller of the embodiment of the present disclosure includes:
  • the second receiving module is configured to receive capability announcement information sent by the node; the capability announcement information is used to indicate the capability of the node to support the compressed SRv6 SID;
  • the second sending module is configured to send SID information; SID information includes SRv6 SID information.
  • an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing information sending methods is implemented.
  • an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing information processing methods is implemented.
  • the processor is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.
  • the memory is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically such as SDRAM). , DDR, etc.), read-only memory (ROM), charged erasable programmable read-only memory (EEPROM), flash memory (FLASH);
  • the I/O interface read and write interface
  • the information exchange of the processor includes, but is not limited to, a data bus (Bus), etc.
  • the division between functional modules/units mentioned in the above description does not necessarily correspond to the division of physical components; for example, a physical component may have multiple functions, or a function or step may consist of several physical components. The components are executed cooperatively.
  • Some physical components or all physical components can be implemented as software executed by a processor, such as a central processing unit (CPU), a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as Application specific integrated circuit.
  • a processor such as a central processing unit (CPU), a digital signal processor, or a microprocessor, or as hardware, or as an integrated circuit, such as Application specific integrated circuit.
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include, but are not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), charged erasable programmable read-only memory (EEPROM), flash memory (FLASH) or other disk storage ; CD-ROM, digital versatile disk (DVD) or other optical disk storage; magnetic cassette, tape, magnetic disk storage or other magnetic storage; any other that can be used to store desired information and can be accessed by a computer medium.
  • a communication medium usually 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. .

Landscapes

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

Abstract

本公开实施例提供了一种信息发送的方法，用于节点，所述方法包括：发送能力通告信息；所述能力通告信息用于表示所述节点支持压缩的SRv6段标识的能力。本公开实施例还提供了一种信息处理的方法、节点、控制器、计算机可读介质。

Description

信息发送和处理的方法、节点、控制器、计算机可读介质 技术领域
本公开实施例涉及段路由技术领域，特别涉及一种信息发送的方法、信息处理的方法、节点、控制器、计算机可读介质。
背景技术
IPv6(互联网协议第6版)地址长度较大，为128bit，故会导致使用IPv6地址的SRv6(互联网协议第6版段路由)报文头封装开销过大，进而使大量的现网硬件无法在一个周期内完成读取，需要将报文环回进行读取，吞吐量减半。
为此，实现控制面对SRv6压缩的报文头的支持是期望的。
发明内容
本公开实施例提供一种信息发送的方法、信息处理的方法、节点、控制器、计算机可读介质。
第一方面，本公开实施例提供一种信息发送的方法，用于节点，所述方法包括：
发送能力通告信息；所述能力通告信息用于表示所述节点支持压缩的互联网协议第6版段路由SRv6段标识的能力。
在一些实施例中，所述节点支持压缩的SRv6段标识的能力包括以下至少一项：
所述节点支持压缩的SRv6段标识；
所述节点支持的SRv6段标识压缩类型；
SRv6段标识块信息与SRv6类型的对应关系。
在一些实施例中，所述发送能力通告信息包括：
根据内部网关协议、边界网关协议、路径计算单元通信协议、边界网关-连接状态协议中的任意一种，发送能力通告信息。
在一些实施例中，所述能力通告信息包括以下至少一项：
压缩能力标识；
SRv6压缩能力类型-长度-值三元组TLV；
SRv6压缩能力子TLV。
在一些实施例中，所述发送能力通告信息包括根据中间系统到中间系统协议发送能力通告信息；所述能力通告信息包括以下至少一项：
路由能力TLV的SRv6能力子TLV中的压缩能力标识；
路由能力TLV的SRv6压缩能力子TLV。
在一些实施例中，所述发送能力通告信息包括根据开放式最短路径优先协议发送能力通告信息；所述能力通告信息包括以下至少一项：
第三版最短路径优先协议路由信息链路状态通告的SRv6能力TLV中的压缩能力标识；
第三版最短路径优先协议路由信息链路状态通告的SRv6能力TLV中的SRv6压缩能力子TLV。
在一些实施例中，所述发送能力通告信息包括根据边界网关-连接状态协议发送能力通告信息；所述能力通告信息包括以下至少一项：
SRv6节点属性的SRv6能力TLV中的压缩能力标识；
SRv6节点属性的SRv6能力TLV中的SRv6压缩能力子TLV。
在一些实施例中，所述发送能力通告信息包括根据路径计算单元协议发送能力通告信息；所述能力通告信息包括以下至少一项：Open消息的SRv6路径计算单元能力子TLV中的压缩能力标识；Open消息的SRv6压缩能力子TLV；
或者，
有状态路径计算单元请求参数对象包括压缩路径标识，用于指示路径建立类型为压缩的SRv6段标识路径。
在一些实施例中，在所述发送能力通告信息后还包括：
接收控制器发送的段标识信息；所述段标识信息包括SRv6段标识的信息；
根据所述段标识信息，封装段路由头。
在一些实施例中，所述段标识信息包括SRv6段标识以及相应的压缩相关信息；
所述根据所述段标识信息，封装段路由头包括：根据能力通告信息、SRv6段标识以及相应的压缩相关信息，确定是否将至少部分SRv6段标识压缩后封装段路由头。
在一些实施例中，所述确定是否将至少部分SRv6段标识压缩后封装段路由头包括：
若有多个所述SRv6段标识处于相同的块中，且压缩长度相同，则确定将该多个SRv6段标识压缩后封装段路由头；
或，
若有多个所述SRv6段标识处于相同的块中，则确定将该多个SRv6段标识压缩后封装段路由头。
在一些实施例中，所述段标识信息包括压缩的SRv6段标识；
所述根据所述段标识信息，封装段路由头包括：至少根据所述压缩的SRv6段标识，封装段路由头。
第二方面，本公开实施例提供一种信息处理的方法，用于控制器，包括：
接收节点发送的能力通告信息；所述能力通告信息用于表示所述节点支持压缩的SRv6段标识的能力；
发送段标识信息；所述段标识信息包括SRv6段标识的信息。
在一些实施例中，所述段标识信息包括SRv6段标识以及相应的压缩相关信息。
在一些实施例中，所述压缩相关信息包括以下至少一项：
压缩指示；
压缩信息发生改变的起始SRv6段标识的位置；
压缩信息发生改变的结束SRv6段标识的位置；
每个SRv6段标识网络节点的标识位置的块的长度；
每个SRv6段标识网络节点的标识位置的节点标识的长度；
每个SRv6段标识的压缩长度；
每个SRv6段标识的压缩对应关系；所述SRv6段标识的压缩对应关系为所述SRv6段标识网络节点的标识位置的块的长度与压缩长度的对应关系。
在一些实施例中，所述压缩相关信息包括由每个SRv6段标识携带的以下至少一项：
所述SRv6段标识网络节点的标识位置的块的长度；
所述SRv6段标识网络节点的标识位置的节点标识的长度；
所述SRv6段标识的压缩长度；
每个SRv6段标识的压缩对应关系。
在一些实施例中，在所述发送段标识信息前，还包括：
确定SRv6路径；
将SRv6路径中的至少部分SRv6段标识压缩，得到压缩的SRv6段标识；
所述发送段标识信息包括：发送带有压缩的SRv6段标识的压缩段标识信息。
第三方面，本公开实施例提供一种节点，其包括：
第一发送模块，配置为发送能力通告信息；所述能力通告信息用于表示所述节点支持压缩的SRv6段标识的能力。
在一些实施例中，所述节点还包括：
第一接收模块，配置为接收控制器发送的段标识信息；所述段标识信息包括SRv6段标识的信息；
一个或多个处理器，配置为根据所述段标识信息，封装段路由头。
第四方面，本公开实施例提供一种控制器，其包括：
第二接收模块，配置为接收节点发送的能力通告信息；所述能力通告信息用于表示所述节点支持压缩的SRv6段标识的能力；
第二发送模块，配置为发送段标识信息；所述段标识信息包括SRv6段标识的信息。
第五方面，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现上述任意一种信息发送的方法。
第六方面，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现上述任意一种信息处理的方法。
本公开实施例可实现完整的控制面对压缩的SRv6段标识的支持，扩展了压缩的SRv6段标识的实际应用。
附图说明
附图用来提供对本公开实施例的进一步理解，并且构成说明书的一部分，与本公开实施例一起用于解释本公开，并不构成对本公开的限制。通过参考附图对详细示例实施例进行描述，以上和其它特征和优点对本领域技术人员将变得更加显而易见，在附图中：
图1为本公开实施例提供的一种信息发送的方法的流程图；
图2为本公开实施例提供的另一种信息发送的方法的流程图；
图3为本公开实施例提供的另一种信息发送的方法中部分步骤的流程图；
图4为本公开实施例提供的另一种信息发送的方法中部分步骤的流程图；
图5为本公开实施例提供的一种信息处理的方法的流程图；
图6为本公开实施例提供的另一种信息处理的方法的流程图；
图7为本公开实施例提供的一种节点的组成框图；
图8为本公开实施例提供的另一种节点的组成框图；
图9为本公开实施例提供的一种控制器的组成框图；
图10为本公开实施例提供的一种计算机可读介质的组成框图；
图11为本公开实施例提供的一种SRv6网络的组成框图。
图12为本公开实施例提供的一种TLV的格式示意图；
图13为本公开实施例提供的另一种TLV的格式示意图；
图14为本公开实施例提供的另一种TLV的格式示意图；
图15为本公开实施例提供的另一种TLV的格式示意图。
具体实施方式
为使本领域的技术人员更好地理解本公开实施例的技术方案，下面结合附图对本公开实施例提供的信息发送的方法、信息处理的方法、节点、控制器、计算机可读介质进行详细描述。
在下文中将参考附图更充分地描述本公开实施例，但是所示的实施例可以以不同形式来体现，且不应当被解释为限于本公开阐述的实施例。反之，提供这些实施例的目的在于使本公开透彻和完整，并将使本领域技术人员充分理解本公开的范围。
本公开实施例可借助本公开的理想示意图而参考平面图和/或截面图进行描述。因此，可根据制造技术和/或容限来修改示例图示。
在不冲突的情况下，本公开各实施例及实施例中的各特征可相互组合。
本公开所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本公开所使用的术语“和/或”包括一个或多个相关列举条目的任何和所有组合。如本公开所使用的单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。如本公开所使用的术语“包括”、“由……制成”，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其它特征、整体、步骤、操作、元件、组件和/或其群组。
除非另外限定，否则本公开所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字 典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本公开明确如此限定。
本公开实施例不限于附图中所示的实施例，而是包括基于制造工艺而形成的配置的修改。因此，附图中例示的区具有示意性属性，并且图中所示区的形状例示了元件的区的具体形状，但并不是旨在限制性的。
段路由(Segment Routing，简称为SR)是一种扩展的源路由技术，原理是在源节点(头节点)把携带路由信息指令的Segment List(分段列表)封装在报文头中，指示后续中间节点如何处理报文，以使报文沿预定路径通过网络，而不需要在中间节点上维护路径的状态信息。
SR在数据面可实现IPv6(互联网协议第6版)地址的封装，即为SRv6(互联网协议第6版段路由)技术。SRv6在报文头中定义扩展的段路由头(Segment Routing Header，简称为SRH)，并在SRH中使用IPv6地址为段标识(Segment ID，简称为SID)。
参照图11，SRv6网络中可包括多个节点，其中至少头节点和为节点可与控制器间传递信息。
由于IPv6地址长度较大，为128bit，故会导致SRv6的报文头封装开销过大。例如，SRH中携带甚至超过10个SID时，仅仅SID列表长度就超过160Byte，对平均净荷256Byte的报文来说，封装开销约在50％。
而且，封装开销过大还会进一步使大量的现网硬件无法在一个周期内完成读取，需要将报文环回进行读取，吞吐量减半。
为减少报文头封装开销并降低对硬件的要求，提高转发和处理效率，一些相关技术中提出了在转发面对SRv6段标识(SRv6 SID)进行压缩，即通过一些方式将128bit的SRv6 SID进行“压缩”，得到小于128bit的压缩的SRv6 SID。
应当理解，由于压缩后的压缩的SRv6 SID比128bit更短，故压缩的SRv6 SID也可称为“短小标识”，即“压缩”也可理解为对SRv6 SID的格式的转变。
具体的，标准的128bit的SRv6 SID包括对地址块等固定部分和对应Node ID(节点标识)和Function ID(功能标识)等的变化部分，其也称完整的SRv6 SID。 相对的，压缩的SRv6 SID则可仅包括标准的SRv6 SID中的变化部分，例如包括Node ID、Function ID以及可选的Argument(争论)等部分，从而单独的压缩的SRv6 SID比128bit短，而该压缩的SRv6 SID的长度，称为SRv6 SID的“压缩长度”，即标准的SRv6 SID采用压缩形式(短小标识)时的长度；而多个压缩的SRv6 SID再结合公共的前缀/地址块等，则可组成一个标准的SRv6 SID。
例如，一种SRv6 SID压缩方案定义了新的uSID(Micro SID)，其支持将一个128bit的IPv6地址(SRv6 SID)被分为8份，第1份用于表示uSID块信息，另外7份每份用于表示一个压缩方式的uSID，从而将128bit的SRv6 SID的封装效率提高了7倍。
为实现对压缩的SRv6 SID的完整支持，故实现控制面对SRv6压缩的SRv6SID的支持是期望的。
第一方面，本公开实施例提供一种信息发送的方法，用于节点。
参照图11，本公开实施例中的节点是SRv6网络的节点，其中至少头节点和尾节点可与控制器间传递信息。
参照图1，本公开实施例的方法包括：
S101、发送能力通告信息；能力通告信息用于表示节点支持压缩的SRv6 SID的能力(即节点的“压缩能力”)。
当前节点(如头节点)向控制器或其它节点(如中间节点)发出特定的能力通告信息，以“通告”控制器或其它节点自身具有压缩能力，即自身能支持(或者说能处理)压缩的SRv6 SID(或者说短小标识)。
通过节点发送的能力通告信息，即在控制面实现了对压缩的SRv6 SID的支持。
应当理解，SRv6网络中的各节点实质上是等价的，其中任意节点均可实现本公开实施例的方法，即每个节点均可能发送能力通告信息，也可能接收到来自其它节点的能力通告信息。故每个节点均可能在部分情况下作为头节点，也可能在其它情况下作为中间节点。
在一些实施例中，发送能力通告信息包括：根据内部网关协议(IGP协议)、边界网关协议(BGP协议)、路径计算单元通信协议(PCE协议)、边界网关- 连接状态协议(BGP-LS协来)中的任意一种，发送能力通告信息。
也就是说，能力通告可根据以上的各具体协议实现，单以上列列举的协议只是示例性的，而不是对本公开实施例适用的控制面协议的限定。
在一些实施例中，支持压缩的SRv6 SID的能力(压缩能力)包括以下至少一项：
节点支持压缩的SRv6 SID；
节点支持的SRv6 SID压缩类型；
SRv6 SID块(Block)信息与SRv6类型的对应关系。
从内容上看，压缩能力可包括：节点支持压缩的SRv6 SID，即表明节点能支持压缩的SRv6 SID；节点支持的SRv6 SID压缩类型，即表明节点能支持哪些类型的SRv6 SID压缩；SRv6 SID块信息与SRv6类型的对应关系，即表明SRv6 SID的块信息与SRv6类型之间的对应关系，例如，SRv6类型包括是普调的SRv6或是压缩的SRv6，以及压缩的SRv6为16bit、32bt、64bt等哪种类型；而SRv6 SID块可是48bit、64bit、96bit等形式。
以上压缩能力的通告，可通过以上各种格式实现。
在一些实施例中，能力通告信息包括以下至少一项：
压缩能力标识；
SRv6压缩能力类型-长度-值三元组TLV；
SRv6压缩能力子TLV(Sub-TLV)。
为了在信息中表明节点的压缩能力，具体可以是修改协议，在已有的TLV或子TLV中扩展新的表明压缩能力的标识(Flag)，即压缩能力标识。具体的，压缩能力标识可为特定的字段(Flag)。
或者，也可以是修改协议，扩展新的表明压缩能力的压缩能力TLV或压缩能力子TLV。
应当理解，压缩能力标识、压缩能力TLV、压缩能力子TLV是能力通告信息的形式，而每种形式与其表示的压缩能力的内容并无必然的限定关系。
例如，可参照图12，在某TLV中有压缩能力标识(C字段)，根据C字段值的不同可表示节点是否支持压缩的SRv6 SID，或者，也可表示节点支持的具 体的SRv6 SID压缩类型。
再如，可在某TLV中扩展一个压缩能力子TLV，用于表示节点支持压缩的SRv6 SID，和/或，节点支持的SRv6 SID压缩类型。
再如，参照图13，可在某TLV中扩展一个压缩能力子TLV，用于表示SRv6SID块信息与SRV6类型的一个对应关系，例如，SRv6类型包括是普调的SRv6或是压缩的SRv6，以及压缩的SRv6为16bit、32bt、64bt等哪种类型；而SRv6SID块可是48bit、64bit、96bit等形式。
同时，在每条能力通告信息中，以上压缩能力标识、SRv6压缩能力TLV、SRv6压缩能力子TLV可仅存在一个，如参照图12仅存在压缩能力标识(C字段)，也可同时存在多个，如参照图13同时存在压缩能力标识(C字段)和SRv6压缩能力子TLV。
而且，当每条能力通告信息中压缩能力标识、SRv6压缩能力TLV、SRv6压缩能力子TLV存在多项时，不同的项表示的意义可以互不相同，也可有重合。
下面对根据部分具体协议发送能力通告信息时，能力通告信息的具体形式进行示例性的介绍。
在一些实施例中，发送能力通告信息包括根据中间系统到中间系统协议(ISIS协议)发送能力通告信息；能力通告信息包括以下至少一项：
路由能力TLV的SRv6能力子TLV中的压缩能力标识；
路由能力TLV的SRv6压缩能力子TLV。
对ISIS协议，能力通告信息具体可包括在其路由能力TLV的SRv6能力子TLV中扩展的(新增的)压缩能力标识，或者是扩展(新增的)的SRv6压缩能力子TLV。
例如，压缩能力标识可仅表示节点是否支持压缩的SRv6 SID，或者，也可表示节点支持的SRv6 SID压缩类型。
而SRv6压缩能力子TLV可用于表示SRv6 SID块信息与SRV6类型的一个对应关系，例如，SRv6类型包括是普调的SRv6或是压缩的SRv6，以及压缩的SRv6为16bit、32bt、64bt等哪种类型；而SRv6 SID块块可是48bit、64bit、96bit 等形式。
在一些实施例中，发送能力通告信息包括根据开放式最短路径优先协议(OSPF协议)发送能力通告信息；能力通告信息包括以下至少一项：
第三版最短路径优先协议路由信息链路状态通告(OSPFv3 Router Information LSA)的SRv6能力TLV中的压缩能力标识；
OSPFv3 Router Information LSA的SRv6能力TLV中的SRv6压缩能力子TLV。
对OSPF协议，能力通告信息具体可包括在OSPFv3 Router Information LSA的SRv6能力TLV中扩展的(新增的)压缩能力标识，也可包括扩展的(新增的)SRv6压缩能力子TLV。
例如，压缩能力标识可仅表示节点是否支持压缩的SRv6 SID，或者，也可表示节点支持的SRv6 SID压缩类型。
而SRv6压缩能力子TLV可用于表示SRv6 SID块信息与SRV6类型的一个对应关系，例如，SRv6类型包括是普调的SRv6或是压缩的SRv6，以及压缩的SRv6为16bit、32bt、64bt等哪种类型；而SRv6 SID块可是48bit、64bit、96bit等形式。
在一些实施例中，发送能力通告信息包括根据BGP-LS协议发送能力通告信息；能力通告信息包括以下至少一项：
SRv6节点属性的SRv6能力TLV中的压缩能力标识；
SRv6节点属性的SRv6能力TLV中的SRv6压缩能力子TLV。
对BGP-LS协议，能力通告信息具体可包括在SRv6节点属性的SRv6能力TLV中扩展的(新增的)压缩能力标识，或者是扩展的(新增的)SRv6压缩能力子TLV。
例如，压缩能力标识可仅表示节点是否支持压缩的SRv6 SID，或者，也可表示节点支持的SRv6 SID压缩类型。
而SRv6压缩能力子TLV可用于表示SRv6 SID块信息与SRV6类型的一个 对应关系，例如，SRv6类型包括是普调的SRv6或是压缩的SRv6，以及压缩的SRv6为16bit、32bt、64bt等哪种类型；而SRv6 SID块可是48bit、64bit、96bit等形式。
在一些实施例中，发送能力通告信息包括根据PCE协议发送能力通告信息；能力通告信息包括以下至少一项：Open消息的SRv6路径计算单元能力子TLV中的压缩能力标识；Open消息的SRv6压缩能力子TLV；
对PCE协议，能力通告信息具体可包括在PCC(路径计算客户端)与PCE(路径计算单元)之间通告的open消息中的SRv6路径计算单元能力子TLV(SRv6 PCE Capability sub-TLV)中的扩展的(新增的)压缩能力标识，或者是扩展的(新增的)SRv6压缩能力子TLV。
例如，压缩能力标识可仅表示节点是否支持压缩的SRv6 SID，或者，也可表示节点支持的SRv6 SID压缩类型。
而SRv6压缩能力子TLV可用于表示SRv6 SID块信息与SRV6类型的一个对应关系，例如，SRv6类型包括是普调的SRv6或是压缩的SRv6，以及压缩的SRv6为16bit、32bt、64bt等哪种类型；而SRv6 SID块可是48bit、64bit、96bit等形式。
或者，作为另一种方式，有状态路径计算单元请求参数对象包括压缩路径标识，用于指示路径建立类型为压缩的SRv6 SID路径。
即针对PCE协议，也可扩展有状态路径计算单元请求参数对象(SRP Object，Stateful PCE Request Parameters object)，在其中增加压缩路径标识，该增加的压缩路径标识用于指示算路请求或者算路结果应下发压缩的SRv6 SID路径。
参照图2，在一些实施例中，在发送能力通告信息后还包括：
S102、接收控制器发送的SID信息；SID信息包括SRv6 SID的信息。
S103、根据SID信息，封装SRH。
对节点而言，在发出能力通告信息后，可能接收到来自控制器的SID信息，该SID信息中体现了SRv6 SID的信息(但具体形式可不同)。由此，节点可根 据SID信息封装得到SRH，并将SRH加入SR报文中，再发送SR报文。
作为本公开实施例的一种方式，控制器发送的SID信息中的SRv6 SID都是标准的(128bit的)，但同时，SID信息中还有与这些SRv6 SID的压缩相关的信息(压缩相关信息)，此时需要节点进行SRv6 SID的压缩。
相应的，参照图3，在一些实施例中，SID信息包括SRv6 SID以及相应的压缩相关信息；根据SID信息，封装SRH(S103)包括：
S1031、根据能力通告信息、SRv6 SID以及相应的压缩相关信息，确定是否将至少部分SRv6 SID压缩后封装SRH。
节点接收到标准的SRv6 SID后，可根据相应的压缩相关信息，决定是直接使用标准的SRv6 SID封装SRH，还是用压缩的SRv6 SID封装SRH。
其中，用压缩的SRv6 SID封装SRH可以是将全部SRv6 SID都压缩后封装SRH；也可以是仅对部分SRv6 SID压缩后封装SRH，而其它SRv6 SID则不压缩直接封装SRH，即最后得到的SRH中可有部分SRv6 SID被压缩，而部分SRv6SID未被压缩。
在一些实施例中，确定是否将至少部分SRv6 SID压缩后封装SRH包括：
判断标准1：若有多个SRv6 SID处于相同的块中，且压缩长度相同，则确定将该多个SRv6 SID压缩后封装SRH；
或，
判断标准2：若有多个SRv6 SID处于相同的块中，则确定将该多个SRv6 SID压缩后封装SRH。
可根据不同的标准，判断是否使用压缩的SRv6 SID，以及具体对哪些SRv6SID进行压缩。
一种判断标准是：若多个SRv6 SID处于相同的块中，且它们压缩之后的长度(即压缩长度)相同，则将它们压缩后封装入SRH。当然，应当理解，此时的多个SRv6 SID也可能就是全部的SRv6 SID。
或者，另一种判断标准可以是：只要多个SRv6 SID处于相同的块中，则不考虑压缩长度，就将它们压缩后封装入SRH。当然，应当理解，此时的多个SRv6 SID也可能就是全部的SRv6 SID。
其中，具体采用哪种标准，可根据使用场景确定。例如，在单域的环境下，可使用判断标准2，而在跨域时可使用判断标准1。
作为本公开实施例的一种方式，控制器发送的以上SID信息中有至少一部分SRv6 SID是已经压缩的(或者说是短小格式的)，故控制器可直接将这些压缩的SRv6 SID封装到SRH中。
相应的，参照图4，在一些实施例中，SID信息包括压缩的SRv6 SID；根据SID信息，封装SRH(S103)包括：
S1032、至少根据压缩的SRv6 SID，封装SRH。
即，对SID信息中的已经压缩的SRv6 SID，节点可直接对其进行封装。
当然，应当理解，若SID信息中同时还包括标准的SRv6 SID，则可以是对这些SRv6 SID以标准的方式封装，也可以是根据以上步骤S1031的方式确定是否将它们压缩后封装。
第二方面，本公开实施例提供一种信息处理的方法，用于控制器。
参照图11，本公开实施例中的控制器是SRv6网络的控制器，SRv6网络包括多个节点，不同节点间可以传递信息，其中至少头节点和尾节点可与控制器间传递信息。
参照图5，本公开实施例的方法包括：
S201、接收节点发送的能力通告信息；能力通告信息用于表示节点支持压缩的SRv6 SID的能力。
S202、发送SID信息；SID信息包括SRv6 SID的信息。
控制器接收到以上节点发送的能力通告信息，获知节点能支持压缩的SRv6SID的信息，从而可向节点发送SID信息，供节点封装SRH。
作为本公开实施例的一种方式，控制器可将标准的SRv6 SID发送给节点， 并同时携带对应的压缩相关信息，以供节点决定是否采用压缩的SRv6 SID封装SRH。
相应的，在一些实施例中SID信息包括SRv6 SID以及相应的压缩相关信息。
在一些实施例中，压缩相关信息包括以下至少一项：
压缩指示；
压缩信息发生改变的起始SRv6 SID的位置；
压缩信息发生改变的结束SRv6 SID的位置；
每个SRv6 SID网络节点的标识位置(Locater)的块(Block)的长度；
每个SRv6 SID网络节点的标识位置的节点标识的长度；
每个SRv6 SID的压缩长度；
每个SRv6 SID的压缩对应关系；SRv6 SID的压缩对应关系为SRv6 SID网络节点的标识位置的块的长度与压缩长度的对应关系。
具体的，压缩相关信息可包括以上的内容。
其中，压缩指示表明需要用压缩的SRv6 SID封装SRH。
各长度则表示相应的长度信息。
其中，网络节点的标识位置(Locater)是网络拓扑中分配给一个网络节点的标识，表明节点的位置信息，用于路由和转发报文到该节点，块(Block)则是分配SID的地址块。
压缩信息发生改变的起始和结束SRv6 SID的位置则是与压缩相关的信息发生改变的SRv6 SID的位置，例如可以是压缩的SRv6 SID的起始和结束位置。
SRv6 SID的压缩对应关系则是SRv6 SID网络节点的标识位置的块的长度与压缩长度的对应关系(例如为比例值，或者说是关系的“种类”)。
其中，每条SID信息中，压缩指示可仅有一个。
而以上各长度和压缩对应关系可以是针对每个SRv6 SID的。
而压缩信息发生改变的起始SRv6 SID的位置和压缩信息发生改变的结束SRv6 SID的位置可以是单独的位置信息，也可以是针对相应的SRv6 SID的。
在一些实施例中，压缩相关信息包括由每个SRv6 SID携带的以下至少一项：
SRv6 SID网络节点的标识位置的块的长度；
SRv6 SID网络节点的标识位置的节点标识的长度；
SRv6 SID的压缩长度；
SRv6 SID的压缩对应关系。
如前，由于以上各长度和压缩对应关系是针对每个SRv6 SID的，故它们可由每个SRv6 SID自身携带。
当然，每个SRv6 SID自身携带以上信息的具体方式可以是多样的。
例如，可在每个SRv6 SID后扩展(新增)压缩相关信息子TLV，而参照图14，该压缩相关信息子TLV可包括该以上各长度。
再如，以上SRv6 SID的压缩对应关系也可为一个标识，直接携带(扩展)在SRv6 SID的TLV中。
另外，也可以在SID信息中扩展(新增)表示压缩类型的段路由子TLV(Segment Sub-TLV)，其中携带有标准的SRv6 SID，以及扩展的(新增的)L字段，用于表示SRv6 SID为压缩信息发生改变的起始位置或结束位置。即，压缩信息发生改变的起始位置标识、压缩信息发生改变的结束位置标识的具体形式可以是段路由子TLV中的特定字段(如L字段)。
作为本公开实施例的另一种方式，控制器可以先得到压缩的SRv6 SID，并将压缩的SRv6 SID发送给节点，供节点直接使用压缩的SRv6 SID封装SRH。
参照图6，在一些实施例中，在发送SID信息(S202)前，还包括：
S2001、确定SRv6路径。
S2002、将SRv6路径中的至少部分SRv6 SID压缩，得到压缩的SRv6 SID。
而发送SID信息(S202)包括：
S2021、发送带有压缩的SRv6 SID的压缩SID信息。
控制器收集SRv6网络的拓扑信息、拓扑属性及SRv6 SID可达性相关的属性等相关信息，再基于收集到的信息，计算SRv6路径并对路径压缩中的至少部分SRv6 SID进行压缩，并将压缩的SRv6 SID发送给节点(如头节点)，故此时 发送的SID信息即为压缩的SID信息。
具体的，控制器可以通过BGP-LS协议实现对网络拓扑信息、拓扑属性及SRv6 SID可达性相关的属性的收集。
其中，SRv6 SID可达性相关属性实际可包含以上的压缩相关信息。
具体的，控制器可通过BGP协议或者PCE协议将SID信息发送至节点。
例如，控制器通过BGP协议将SID信息通告节点。
例如，控制器通过PCE协议将SID信息通告节点。
具体的，参照图15，扩展PCE协议中显式路由对象(Explicit Route Object，简称为ERO)携带压缩指示标识(如图中的C字段)和压缩的SRv6 SID，其中压缩指示标识用于表明该SRv6 SID是压缩的。
在一些相关技术中，SR Policy(段路由策略)通过Segment List(分段列表)来实现流量工程意图。Segment List对报文在网络中的任意转发路径进行编码，SR Policy由头端-颜色-端点三元组标识；在给定的头端节点上，SR Policy由颜色-端点二元组标识。
SR Policy需要至少一条候选路径，SR Policy的候选路径(Candidate Path)代表将报文从相应SR Policy头端传送到端点的特定方式。每条候选路径有一个偏好值(Preference)，路径的偏好值越高则越优选，其中具有最高偏好值的有效候选路径是活动候选路径，即SR Policy的Segment List是其活动路径的Segment List。每条候选路径可具有一个或者多个Segment List，每个Segment List具有关联的负载均衡权重。引导至此路径的流量根据权重比例，在所有的有效Segment List之间进行负载均衡。
在以上相关技术中，使用BGP协议来向头节点通告SR policy的候选路径，但不能通过BGP协议通告压缩的SR policy的候选路径。
本公开的一种具体的实施例包括：
S301、节点通告SRv6压缩能力。
节点通过发送以上能力通告信息，通告其支持压缩的SRv6 SID的压缩能力。
其中，压缩能力具体包括以下至少一项：节点支持压缩的SRv6 SID、节点 支持的SRv6 SID压缩类型、SRv6 SID块信息与SRv6类型的对应关系等。例如，SRv6类型包括是普调的SRv6或是压缩的SRv6，以及压缩的SRv6为16bit、32bt、64bt等哪种类型；而SRv6 SID块可是48bit、64bit、96bit等形式。
其中，能力通告信息具体包括以下至少一项：压缩能力标识、SRv6压缩能力TLV、SRv6压缩能力子TLV等。
S302、控制器通告SRv6 SID及相应的压缩相关信息给头节点。
控制器接收到能力通告信息后，向头节点发送SID信息。
具体的，控制器发送的可以是一个Segment List，Segment List中包含多个SRv6 SID，以及扩展的每个SRv6 SID相应的压缩相关信息。
其中，压缩相关信息具体包括以下至少一项：压缩指示、压缩信息发生改变的起始SRv6 SID的位置、压缩信息发生改变的结束SRv6 SID的位置、每个SRv6 SID网络节点的标识位置的块的长度、每个SRv6 SID网络节点的标识位置的节点标识的长度、每个SRv6 SID的压缩长度、每个SRv6 SID的压缩对应关系、SRv6 SID的压缩对应关系为SRv6 SID网络节点的标识位置的块的长度与压缩长度的对应关系。
S303、头节点判断是否采用压缩的SRv6 SID封装SRH。
头节点根据接收到的SID信息，确定是否使用压缩的SRv6 SID封装SRH。
其中，具体判断条件可包括：
判断标准1：若有多个SRv6 SID处于相同的块中，且压缩长度相同，则确定将该多个SRv6 SID压缩后封装SRH；
或，
判断标准2：若有多个SRv6 SID处于相同的块中，则确定将该多个SRv6 SID压缩后封装SRH。
其中，具体采用哪种标准，可根据使用场景确定。例如，在单域的环境下，可使用判断标准2，而在跨域时可使用判断标准1。
本公开的另一种具体的实施例包括：
S401、节点通告SRv6压缩能力。
S402、控制器通告SRv6 SID及相应的压缩相关信息给头节点。
控制器接收到能力通告信息后，向头节点发送SID信息。
其中，可在SID信息中扩展(新增)表示压缩类型的段路由子TLV，其中携带有标准的SRv6 SID，以及扩展的(新增的)L字段，用于表示SRv6 SID为压缩信息发生改变的起始位置或结束位置。
S403、头节点判断是否采用压缩的SRv6 SID封装SRH。
本公开的另一种具体的实施例可支持单域或者跨域场景，但是一般用于跨域场景下，其具体包括：
S501、控制器接收节点发送的能力通告信息。
S502、控制器收集SRv6网络的拓扑信息、拓扑属性及SRv6 SID可达性相关的属性等相关信息。
具体的，控制器可以通过BGP-LS协议实现对网络拓扑信息、拓扑属性及SRv6 SID可达性相关的属性的收集。
其中，SRv6 SID可达性相关属性实际可包含以上的压缩相关信息。
S503、控制器基于收集到的SRv6网络的拓扑信息、拓扑属性及SRv6 SID可达性相关的属性等相关信息，计算SRv6路径并对路径压缩中的至少部分SRv6SID进行压缩。
S504、控制器计算完路径后，通过BGP协议或者PCE协议将含有压缩的SRv6 SID的压缩SID信息发送给头节点。
例如，控制器通过BGP协议将SID信息通告节点。
例如，控制器通过PCE协议将SID信息通告节点。
具体的，参照图15，扩展PCE协议中ERO携带压缩指示标识(如图中的C字段)和压缩的SRv6 SID，其中压缩指示标识用于表明该SRv6 SID是压缩的。
S505、节点至少根据压缩的SRv6 SID，封装SRH。
本公开的另一种具体的实施例用于压缩的SRv6 SID是32bit的短小标识时， 其中，转发设备(中间节点)需要有32bit的短小标识与IPv6的对应关系。
本实施例具体包括：
S601、节点通告SRv6压缩能力。
S602、节点通过IGP协议，按照本公开实施例的方法通告压缩的SRv6 SID与IPv6的映射关系。
S603、其它节点根据收到的映射关系，建议映射表，得到32bit的短小标识与IPv6的对应关系。
第三方面，本公开实施例提供一种节点，其用于实现上述任意一种信息发送的方法。
参照图7，本公开实施例的节点包括：
第一发送模块，配置为发送能力通告信息；能力通告信息用于表示节点支持压缩的SRv6 SID的能力。
应当理解，本公开实施例的节点实际可为SRv6网络中的任意节点，即每个节点都可能执行发送能力通告信息的步骤，也可能接收到其它节点发送的发送能力通告信息。
参照图8，在一些实施例中，节点还包括：
第一接收模块，配置为接收控制器发送的SID信息；SID信息包括SRv6 SID的信息；
一个或多个处理器，配置为根据SID信息，封装SRH。
第四方面，本公开实施例提供一种控制器，其用于实现上述任意一种信息处理的方法
参照图9，本公开实施例的控制器包括：
第二接收模块，配置为接收节点发送的能力通告信息；能力通告信息用于表示节点支持压缩的SRv6 SID的能力；
第二发送模块，配置为发送SID信息；SID信息包括SRv6 SID的信息。
第五方面，参照图10，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，程序被处理器执行时实现上述任意一种信息发送的方法。
第六方面，参照图10，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，程序被处理器执行时实现上述任意一种信息处理的方法。
其中，处理器为具有数据处理能力的器件，其包括但不限于中央处理器(CPU)等；存储器为具有数据存储能力的器件，其包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)；I/O接口(读写接口)连接在处理器与存储器间，能实现存储器与处理器的信息交互，其包括但不限于数据总线(Bus)等。
本领域普通技术人员可以理解，上文中所公开的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。
在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。
某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器(CPU)、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)或其它磁盘存储器；只读光盘(CD-ROM)、数字多功能盘(DVD)或其它光盘存 储器；磁盒、磁带、磁盘存储或其它磁存储器；可以用于存储期望的信息并且可以被计算机访问的任何其它的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其它传输机制之类的调制数据信号中的其它数据，并且可包括任何信息递送介质。
本公开已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其它实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本公开的范围的情况下，可进行各种形式和细节上的改变。

Claims (22)

  1. 一种信息发送的方法，用于节点，所述方法包括：
    发送能力通告信息；所述能力通告信息用于表示所述节点支持压缩的互联网协议第6版段路由SRv6段标识的能力。
  2. 根据权利要求1所述的方法，其中，所述节点支持压缩的SRv6段标识的能力包括以下至少一项：
    所述节点支持压缩的SRv6段标识；
    所述节点支持的SRv6段标识压缩类型；
    SRv6段标识块信息与SRv6类型的对应关系。
  3. 根据权利要求1所述的方法，其中，所述发送能力通告信息包括：
    根据内部网关协议、边界网关协议、路径计算单元通信协议、边界网关-连接状态协议中的任意一种，发送能力通告信息。
  4. 根据权利要求1所述的方法，其中，所述能力通告信息包括以下至少一项：
    压缩能力标识；
    SRv6压缩能力类型-长度-值三元组TLV；
    SRv6压缩能力子TLV。
  5. 根据权利要求1所述的方法，其中，所述发送能力通告信息包括根据中间系统到中间系统协议发送能力通告信息；所述能力通告信息包括以下至少一项：
    路由能力TLV的SRv6能力子TLV中的压缩能力标识；
    路由能力TLV的SRv6压缩能力子TLV。
  6. 根据权利要求1所述的方法，其中，所述发送能力通告信息包括根据开放式最短路径优先协议发送能力通告信息；所述能力通告信息包括以下至少一项：
    第三版最短路径优先协议路由信息链路状态通告的SRv6能力TLV中的压缩能力标识；
    第三版最短路径优先协议路由信息链路状态通告的SRv6能力TLV中的SRv6压缩能力子TLV。
  7. 根据权利要求1所述的方法，其中，所述发送能力通告信息包括根据边界网关-连接状态协议发送能力通告信息；所述能力通告信息包括以下至少一项：
    SRv6节点属性的SRv6能力TLV中的压缩能力标识；
    SRv6节点属性的SRv6能力TLV中的SRv6压缩能力子TLV。
  8. 根据权利要求1所述的方法，其中，所述发送能力通告信息包括根据路径计算单元通信协议发送能力通告信息；
    所述能力通告信息包括以下至少一项：Open消息的SRv6路径计算单元能力子TLV中的压缩能力标识；Open消息的SRv6压缩能力子TLV；
    或者，
    有状态路径计算单元请求参数对象包括压缩路径标识，用于指示路径建立类型为压缩的SRv6段标识路径。
  9. 根据权利要求1所述的方法，其中，在所述发送能力通告信息后还包括：
    接收控制器发送的段标识信息；所述段标识信息包括SRv6段标识的信息；
    根据所述段标识信息，封装段路由头。
  10. 根据权利要求9所述的方法，其中，
    所述段标识信息包括SRv6段标识以及相应的压缩相关信息；
    所述根据所述段标识信息，封装段路由头包括：根据所述能力通告信息、SRv6段标识以及相应的压缩相关信息，确定是否将至少部分SRv6段标识压缩后封装段路由头。
  11. 根据权利要求10所述的方法，其中，所述确定是否将至少部分SRv6段标识压缩后封装段路由头包括：
    若有多个所述SRv6段标识处于相同的块中，且压缩长度相同，则确定将该多个SRv6段标识压缩后封装段路由头；
    或，
    若有多个所述SRv6段标识处于相同的块中，则确定将该多个SRv6段标识压缩后封装段路由头。
  12. 根据权利要求9所述的方法，其中，
    所述段标识信息包括压缩的SRv6段标识；
    所述根据所述段标识信息，封装段路由头包括：至少根据所述压缩的SRv6段标识，封装段路由头。
  13. 一种信息处理的方法，用于控制器，包括：
    接收节点发送的能力通告信息；所述能力通告信息用于表示所述节点支持压缩的SRv6段标识的能力；
    发送段标识信息；所述段标识信息包括SRv6段标识的信息。
  14. 根据权利要求13所述的方法，其中，
    所述段标识信息包括SRv6段标识以及相应的压缩相关信息。
  15. 根据权利要求14所述的方法，其中，所述压缩相关信息包括以下至少 一项：
    压缩指示；
    压缩信息发生改变的起始SRv6段标识的位置；
    压缩信息发生改变的结束SRv6段标识的位置；
    每个SRv6段标识网络节点的标识位置的块的长度；
    每个SRv6段标识网络节点的标识位置的节点标识的长度；
    每个SRv6段标识的压缩长度；
    每个SRv6段标识的压缩对应关系；所述SRv6段标识的压缩对应关系为所述SRv6段标识网络节点的标识位置的块的长度与压缩长度的对应关系。
  16. 根据权利要求15所述的方法，其中，所述压缩相关信息包括由每个SRv6段标识携带的以下至少一项：
    所述SRv6段标识网络节点的标识位置的块的长度；
    所述SRv6段标识网络节点的标识位置的节点标识的长度；
    所述SRv6段标识的压缩长度；
    每个SRv6段标识的压缩对应关系。
  17. 根据权利要求13所述的方法，其中，在所述发送段标识信息前，还包括：
    确定SRv6路径；
    将SRv6路径中的至少部分SRv6段标识压缩；
    所述发送段标识信息包括：发送带有压缩的SRv6段标识的压缩段标识信息。
  18. 一种节点，其包括：
    第一发送模块，配置为发送能力通告信息；所述能力通告信息用于表示所 述节点支持压缩的SRv6段标识的能力。
  19. 根据权利要求18所述的节点，其中，还包括：
    第一接收模块，配置为接收控制器发送的段标识信息；所述段标识信息包括SRv6段标识的信息；
    一个或多个处理器，配置为根据所述段标识信息，封装段路由头。
  20. 一种控制器，其包括：
    第二接收模块，配置为接收节点发送的能力通告信息；所述能力通告信息用于表示所述节点支持压缩的SRv6段标识的能力；
    第二发送模块，配置为发送段标识信息；所述段标识信息包括SRv6段标识的信息。
  21. 一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现根据权利要求1至12中任意一项所述的信息发送的方法。
  22. 一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现根据权利要求13至17中任意一项所述的信息处理的方法。
PCT/CN2020/136214 2020-03-25 2020-12-14 信息发送和处理的方法、节点、控制器、计算机可读介质 WO2021189973A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US17/914,437 US20230353492A1 (en) 2020-03-25 2020-12-14 Information sending and processing methods, node, controller, and non-transitory computer-readable storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010220471.9A CN112511429A (zh) 2020-03-25 2020-03-25 信息发送和处理的方法、节点、控制器、计算机可读介质
CN202010220471.9 2020-03-25

Publications (1)

Publication Number Publication Date
WO2021189973A1 true WO2021189973A1 (zh) 2021-09-30

Family

ID=74953282

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/136214 WO2021189973A1 (zh) 2020-03-25 2020-12-14 信息发送和处理的方法、节点、控制器、计算机可读介质

Country Status (3)

Country Link
US (1) US20230353492A1 (zh)
CN (1) CN112511429A (zh)
WO (1) WO2021189973A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114866452A (zh) * 2022-05-18 2022-08-05 中电信数智科技有限公司 基于AIOps的SRv6分布式报文转发方法及系统

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113242180B (zh) * 2021-07-12 2021-12-14 广东省新一代通信与网络创新研究院 报文转发方法、装置、设备、可读存储介质及程序产品
CN113645135A (zh) * 2021-08-02 2021-11-12 迈普通信技术股份有限公司 一种sid压缩方法、报文转发方法、装置及电子设备
CN116566880A (zh) * 2022-01-30 2023-08-08 华为技术有限公司 路由通告的方法、网络设备和系统

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140369356A1 (en) * 2013-03-15 2014-12-18 Cisco Technology, Inc. Opportunistic compression of routing segment identifier stacks
CN105210336A (zh) * 2013-05-17 2015-12-30 思科技术公司 用于ldp/sr互操作性的分段路由映射服务器

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100689473B1 (ko) * 2000-08-29 2007-03-08 삼성전자주식회사 통신시스템에서 프로토콜 헤더 압축장치 및 방법
US7602778B2 (en) * 2005-06-29 2009-10-13 Cisco Technology, Inc. System and methods for compressing message headers
CN101848492A (zh) * 2010-06-10 2010-09-29 中兴通讯股份有限公司 媒体网关间的报文传输方法、媒体网关和无线通信系统
US9660897B1 (en) * 2013-12-04 2017-05-23 Juniper Networks, Inc. BGP link-state extensions for segment routing
CN109218189B (zh) * 2017-07-03 2022-04-29 中兴通讯股份有限公司 跨域的路径的标识信息的确定方法、装置及存储介质
CN108429685B (zh) * 2018-04-28 2020-08-04 电子科技大学 一种基于分段路由技术的服务功能链寻路方法
US11025522B2 (en) * 2019-05-04 2021-06-01 Juniper Networks, Inc. Path monitoring system (PMS) controller or ingress node based multiprotocal label switching (MPLS) ping and traceroute in inter- autonomous system (AS) segment routing (SR) networks
US11140074B2 (en) * 2019-09-24 2021-10-05 Cisco Technology, Inc. Communicating packets across multi-domain networks using compact forwarding instructions

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140369356A1 (en) * 2013-03-15 2014-12-18 Cisco Technology, Inc. Opportunistic compression of routing segment identifier stacks
CN105210336A (zh) * 2013-05-17 2015-12-30 思科技术公司 用于ldp/sr互操作性的分段路由映射服务器

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
C. FILSFILS, ED. P. CAMARILLO, ED. CISCO SYSTEMS, INC. D. CAI ALIBABA D. VOYER BELL CANADA I. MEILIK BROADCOM K. PATEL ARRCUS, INC: "Network Programming extension: SRv6 uSID instruction, draft-filsfils-spring-net-pgm-extension-srv6-usid-04.", NETWORK PROGRAMMING EXTENSION: SRV6 USID INSTRUCTION; DRAFT-FILSFILS-SPRING-NET-PGM-EXTENSION-SRV6-USID-04.TXT; INTERNET-DRAFT: SPRING, no. 4, 25 February 2020 (2020-02-25), pages 1 - 14, XP015137883 *
RAN. CHEN SHAOFU. PENG ZTE CORPORATION: "IGP Extensions for Shorter SRv6 SID, draft-chen-lsr-igp-shorter-srv6-extensions-01.", IGP EXTENSIONS FOR SHORTER SRV6 SID; DRAFT-CHEN-LSR-IGP-SHORTER-SRV6-EXTENSIONS-01.TXT; INTERNET-DRAFT: LSR WG, no. 1, 11 May 2020 (2020-05-11), pages 1 - 8, XP015139502 *
Z. LI C. LI HUAWEI TECHNOLOGIES C. XIE CHINA TELECOM K. LEE LG U+ H. TIAN F. ZHAO CAICT J. GUICHARD FUTUREWEI TECHNOLOGIES C. LI C: "Compressed SRv6 Network Programming; draft-li-spring-compressed-srv6-np-02.txt", COMPRESSED SRV6 NETWORK PROGRAMMING; DRAFT-LI-SPRING-COMPRESSED-SRV6-NP-02.TXT; INTERNET-DRAFT: SPRING WORKING GROUP, no. 2, 25 February 2020 (2020-02-25), pages 1 - 24, XP015137894 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114866452A (zh) * 2022-05-18 2022-08-05 中电信数智科技有限公司 基于AIOps的SRv6分布式报文转发方法及系统

Also Published As

Publication number Publication date
US20230353492A1 (en) 2023-11-02
CN112511429A (zh) 2021-03-16

Similar Documents

Publication Publication Date Title
WO2021189973A1 (zh) 信息发送和处理的方法、节点、控制器、计算机可读介质
WO2021179732A1 (zh) 报文封装方法、报文转发方法、通告方法、电子设备、和存储介质
JP6204510B2 (ja) ハイブリッドネットワーク内のトポロジ発見
US10499313B2 (en) Efficient hybrid resource and schedule management in time slotted channel hopping networks
JP6047229B2 (ja) 情報中心ネットワークにおける名前ベースの近隣探索及びマルチホップサービス探索
US20170126569A1 (en) Enhanced neighbor discovery to support load balancing
CN110891026B (zh) 一种流量调度方法、设备及系统
US9451525B2 (en) Method, device and system for starting routing function and transmitting data
CN107454000B (zh) 网络数据传输装置及方法
WO2021233327A1 (zh) 报文处理方法及装置、通告方法及装置、网桥节点、源设备、存储介质及报文处理系统
JP5656137B2 (ja) ボーダ・ゲートウェイ・プロトコル・ルートの更新方法およびシステム
EP3972207B1 (en) Message processing method, device, and computer storage medium
KR20170036760A (ko) 타임 슬롯화 채널 홉핑 네트워크에서의 효율적인 중앙 집중식 자원 및 스케줄 관리
WO2016029862A1 (zh) 一种链路状态信息通告方法和设备
US20170093685A1 (en) Generating service-optimized paths based on enhanced eigrp telemetry
WO2019119346A1 (zh) 一种通信路径确定方法及网络设备
WO2021143279A1 (zh) 段路由业务处理方法和装置、路由设备及存储介质
BR112021012433A2 (pt) Método e dispositivo de comunicação, e meio de armazenamento
JP2006197591A (ja) イーサネットを介したｍｐｌｓマルチキャストパケットの転送装置及び方法
WO2022048514A1 (zh) 数据包的传输方法及装置
US20180006940A1 (en) Method, apparatus and system for transmitting and receiving data packets
JP2016524383A (ja) 通信インタフェースを選択する方法およびデバイス
WO2011150835A1 (zh) 一种请求获取路由信息的方法和相应的路由设备
WO2015039616A1 (zh) 一种报文处理方法及设备
WO2021189993A1 (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: 20927195

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 01/03/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 20927195

Country of ref document: EP

Kind code of ref document: A1