WO2021208843A1 - 分段路由头压缩方法及装置、业务处理方法及装置 - Google Patents

分段路由头压缩方法及装置、业务处理方法及装置 Download PDF

Info

Publication number
WO2021208843A1
WO2021208843A1 PCT/CN2021/086543 CN2021086543W WO2021208843A1 WO 2021208843 A1 WO2021208843 A1 WO 2021208843A1 CN 2021086543 W CN2021086543 W CN 2021086543W WO 2021208843 A1 WO2021208843 A1 WO 2021208843A1
Authority
WO
WIPO (PCT)
Prior art keywords
segment
compressed
identifier
segment identifier
node
Prior art date
Application number
PCT/CN2021/086543
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 JP2022562524A priority Critical patent/JP2023523566A/ja
Priority to EP21788701.7A priority patent/EP4138348A4/en
Publication of WO2021208843A1 publication Critical patent/WO2021208843A1/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
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • 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/0803—Configuration setting
    • 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
    • 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
    • H04L49/00—Packet switching elements
    • H04L49/30—Peripheral units, e.g. input or output ports
    • H04L49/3009—Header conversion, routing tables or routing tags

Definitions

  • the present disclosure relates to the field of wireless communication technology, and in particular to a method and device for segment routing header compression, a method and device for service processing, computer equipment, and a computer-readable medium.
  • Segment Routing is a technology that realizes source routing.
  • RFC8402 defines two standard SR mechanisms, namely, SR-MPLS and SR-MPLS based on the MPLS (Multi-Protocol Label Switching, multi-protocol label switching) forwarding plane.
  • SRv6 based on IPv6 (Internet Protocol Version 6, Internet Protocol Version 6) forwarding plane.
  • SRv6 can be implemented directly based on the IPv6 extended routing header, without adding additional encapsulation, and realizes the unification of IP (Internet Protocol) forwarding and tunnel forwarding.
  • SRv6 uses the same 128-bit format as the IPv6 address
  • the SID (Segment ID) is divided into two parts: Locator and Function, which can realize flexible network and service mixed programming. Therefore, SRv6 has been widely recognized in the industry.
  • the description of the service path uses a SID list composed of a series of 128-bit SIDs, which causes the problem of excessive overhead of the message header.
  • SRH Segment Routing Header
  • uSID raft-filsfils-spring-net-pgm-extension-srv6-usid-02
  • C-SID common compressed SID
  • the forwarding node In the SRv6 scheme, the forwarding node (Transit) only needs to process normal IPv6 forwarding, and the end node (Endpoint) needs to process the SRH header.
  • all end nodes are required to adopt the compressed SID format (C-SID).
  • C-SID compressed SID format
  • the solution allows the last hop end node to use uncompressed format, but does not allow intermediate nodes to use uncompressed format), that is to say, end nodes participating in IPv6 packet forwarding must have the ability to support compressed SID, which affects the SRH processing of network nodes
  • embodiments of the present disclosure provide a method for segment routing header compression, including:
  • Generating a segment list including a configured compressed segment identifier and a configured non-compressed segment identifier
  • segment routing header of a service message wherein the segment routing header of the service message includes the segment list and a routing type field used to indicate the format of the segment routing header, and the segment routing header format is the same as The formats of the compressed segment identifiers match.
  • the embodiments of the present disclosure also provide a service processing method, which is applied to nodes of a segmented routing path, each node on the segmented routing path is configured with a compressed segment identifier or a non-compressed segment identifier, and the segment
  • the critical node on the segment routing path is configured with a compressed segment identifier that additionally has the function of converting the segment identifier pointed to by the remaining number of segments to segment identifier type conversion, and the critical node is a two-phase segment that has been configured with different types of segment identifiers.
  • a node that has been configured with a compressed segment identifier among neighboring nodes, and the method includes:
  • segment list and the route type field used to indicate the format of the segment routing header from the segment routing header of the received service message, the segment list including the configured compressed segment identifier and the configured non-compressed Segment identification
  • the segment identifier pointed to by the remaining segment quantity is converted into the segment identifier type
  • the service message is forwarded to the next hop node, and the service message carries the segment identification type pointed to by the number of remaining segments.
  • an embodiment of the present disclosure also provides a segment routing header compression device, including a configuration module, a first generation module, and a second generation module,
  • the configuration module is configured to configure compressed segment identifiers or non-compressed segment identifiers for each node on the segmented routing path, and configure critical nodes in the segmented routing path with additional segments that point to the number of remaining segments.
  • the segment identifier is a compressed segment identifier of the function of performing segment identifier type conversion
  • the critical node is a node that has been configured with a compressed segment identifier among two adjacent nodes that have been configured with different types of segment identifiers;
  • the first generating module is configured to generate a segment list, the segment list including a configured compressed segment identifier and a configured non-compressed segment identifier;
  • the second generating module is configured to generate a segment routing header of a service message, wherein the segment routing header of the service message includes the segment list and a routing type field used to indicate the format of the segment routing header ,
  • the format of the segment routing header matches the format of the compressed segment identifier.
  • the embodiments of the present disclosure also provide a service processing device, which is applied to nodes of a segmented routing path, each node on the segmented routing path is configured with a compressed segment identifier or a non-compressed segment identifier, and the segment The critical node on the segment routing path is configured with a compressed segment identifier that additionally has the function of converting the segment identifier pointed to by the remaining number of segments to segment identifier type conversion, and the critical node is a two-phase segment that has been configured with different types of segment identifiers.
  • the service processing device includes an acquisition module, a processing module, a conversion module, and a forwarding module,
  • the acquiring module is configured to acquire a segment list and a route type field used to indicate the format of the segment routing header from the segment routing header of the received service message, and the segment list includes the configured compressed segments Identification and configured uncompressed segment identification;
  • the processing module is configured to process the current segment identifier in the segment list, and modify the number of remaining segments according to the route type field;
  • the conversion module is configured to, if the current node is a critical node, convert the segment identifier pointed to by the remaining number of segments;
  • the forwarding module is configured to forward the service message to the next hop node, and the service message carries the segment identification type pointed to by the number of remaining segments.
  • the embodiments of the present disclosure also provide a computer device, including: one or more processors and a storage device; wherein, one or more programs are stored on the storage device, and when the one or more programs are When executed by or multiple processors, the foregoing one or more processors implement the segment routing header compression method or service processing method as provided in the foregoing embodiment.
  • the embodiments of the present disclosure also provide a computer-readable medium on which a computer program is stored, wherein the computer program implements the segment routing header compression method or service processing provided in the foregoing embodiment when the computer program is executed. method.
  • FIG. 1 is a flowchart of a method for compressing a segment routing header provided by an embodiment of the disclosure
  • FIG. 2 is a flowchart of a service processing method provided by an embodiment of the disclosure
  • FIG. 3 is a flowchart of modifying the number of remaining segments according to the route type field provided by an embodiment of the present disclosure
  • Figure 4 is a network topology provided by specific example 1 of the present disclosure.
  • FIG. 5 is a schematic diagram of the SRH structure of the A->Z service message transmission direction provided by specific example 1 of the disclosure;
  • FIG. 6 is a schematic diagram of the SRH structure of the Z->A service message transmission direction provided by specific example 1 of the disclosure.
  • FIG. 7 is a schematic diagram of the service processing process in the transmission direction of the A->Z service message provided by the specific example 1 of the disclosure.
  • FIG. 8 is a schematic diagram of the service processing process in the transmission direction of the Z->A service message provided by the specific example 1 of the disclosure.
  • Figure 9 is a network topology provided by specific example 2 of the present disclosure.
  • FIG. 10 is a schematic diagram of the SRH_Ext structure of the A->Z service message transmission direction provided by specific example 2 of the disclosure.
  • FIG. 11 is a schematic diagram of the SRH_Ext structure of the Z->A service message transmission direction provided by specific example 2 of the disclosure.
  • FIG. 12 is a schematic diagram of the service processing process in the transmission direction of the A->Z service message provided by the specific example 2 of the disclosure.
  • FIG. 13 is a schematic diagram of the service processing process in the Z->A service message transmission direction provided by specific example 2 of the disclosure.
  • FIG. 14 is a schematic diagram of the SRH structure of the A->Z service message transmission direction provided by specific example 3 of the disclosure.
  • 15 is a schematic diagram of the SRH structure of the Z->A service message transmission direction provided by specific example 3 of the disclosure.
  • 16 is a schematic diagram of the service processing process in the transmission direction of the A->Z service message provided by the specific example 3 of the disclosure;
  • FIG. 17 is a schematic diagram of the service processing process in the transmission direction of the Z->A service message provided by the specific example 3 of the disclosure.
  • FIG. 18 is a schematic structural diagram of a segment routing header compression device provided by an embodiment of the disclosure.
  • FIG. 19 is a schematic structural diagram of a service processing apparatus provided by an embodiment of the disclosure.
  • the embodiment of the present disclosure provides a segment routing header compression method. As shown in FIG. 1, the segment routing header compression method includes the following steps S11 to S13.
  • Step S11 configure compressed segment identifiers or uncompressed segment identifiers for each node on the segment routing path, and configure critical nodes in the segment routing path with additional segments that point to the remaining segment number (Segments Lef, SL).
  • Segment identifier The compressed segment identifier of the function that performs segment identifier type conversion.
  • the critical node is a node that has been configured with a compressed segment identifier among two adjacent nodes that have been configured with segment identifiers of different types.
  • the types of segment identifiers include compressed segment identifiers and uncompressed segment identifiers.
  • the segment routing path is node A-node B-node C, where node A and node B are configured with compressed segment identifiers, node C is configured with uncompressed segment identifiers, and node B and node C are configured with segment identifiers.
  • the types are different, and node B is configured with a compressed segment identifier, therefore, node B is a critical node in the segment routing path.
  • the segment routing header compression device configures either a compressed segment identifier or a non-compressed segment identifier for each node on the segment routing path, and the critical node is configured with additional SL (remaining points).
  • the segment identifier pointed to by the number of segments is a compressed segment identifier for the function of converting the segment identifier type. That is to say, there are two types of compressed segment identifiers. One is the compressed segment identifier configured on non-critical nodes. This type of compressed segment identifier can be implemented using existing compressed segment identifiers; the other is configured on non-critical nodes.
  • the compressed segment identifier on the critical node This type of compressed segment identifier has the function of converting the segment identifier pointed to by the SL into the type of the segment identifier. For example, it can be implemented by defining the function field of the segment identifier.
  • each node can diffuse the compressed segment identifier and uncompressed segment identifier through IGP (Interior Gateway Protocol) to the entire SR domain .
  • IGP Interior Gateway Protocol
  • Step S12 a segment list is generated, the segment list includes the configured compressed segment identifier and the configured uncompressed segment identifier.
  • the source node of the segment routing path calculates and generates a segment list, and the segment list is pressed into the compressed segment identifier or the non-compressed segment identifier of each node according to the needs of network programming.
  • the segment list the segment identifiers of the nodes on the segment routing path are arranged according to the forwarding order of the service message.
  • Step S13 Generate a segment routing header of the service message, where the segment routing header of the service message includes a segment list and a routing type field used to indicate the format of the segment routing header.
  • the format of the compressed segment identifier matches.
  • the segment list is carried in the segment routing header (Segment Routing Header, SRH) of the service message.
  • the segment routing header of the service message also includes a routing type (Routing type) field.
  • the segment routing header format matches the format of the compressed segment identifier.
  • Different segment routing header formats define different SL modification methods, and the SL modification methods defined by different segment routing header formats follow Explain in detail.
  • each node on the segment routing path is configured with a compressed segment identifier or a non-compressed segment identifier, and critical nodes are configured with additional segment identifiers pointing to SL for segmentation.
  • the critical node is the node with the compressed segment identifier configured among the two adjacent nodes that have been configured with different types of segment identifiers; the segment list is generated, and the segment list includes the configured compression Segment identification and non-compressed segment identification; generating a segment routing header of a service message, wherein the segment routing header of the service message includes a segment list and a routing type field used to indicate the format of the segment routing header.
  • the segment routing header format matches the format of the compressed segment identifier; the embodiment of the present disclosure performs configuration compression by performing segment identifier type conversion and defining a segment routing header format that matches the format of the compressed segment identifier.
  • the critical node is a node that has been configured with a compressed segment identifier and the next hop node is a node that has been configured with a non-compressed segment identifier.
  • the segment routing path is node A-node B-node C
  • the service report The file transmission path is ABC, where node A and node B are configured with compressed segment identifiers, node C is configured with uncompressed segment identifiers, and node B is the critical node.
  • the function of converting the segment identifier pointed to by the SL to the segment identifier type is a first conversion function
  • the first conversion function is converting the type of the segment identifier pointed to by the SL into an uncompressed segment identifier
  • the critical node is a node that has been configured with a compressed segment identifier and the previous hop node is a node that has been configured with a non-compressed segment identifier.
  • the segment routing path is node A-node B-node C
  • the service report The file transmission path is CBA, where node A and node B are configured with compressed segment identifiers, node C is configured with uncompressed segment identifiers, and node B is the critical node.
  • the function of converting the segment identifier pointed to by the SL to the segment identifier type is a second conversion function
  • the second conversion function is converting the type of the segment identifier pointed to by the SL into a compressed segment identifier
  • the segment routing header of the service message may further include a flag (Flag) field used to indicate the type of segment identification pointed to by the SL. For example, a value of 1 in the Flag field indicates the segment pointed to by the current SL.
  • the segment identifier is a compressed segment identifier, and a value of 0 in the Flag field indicates that the segment identifier pointed to by the current SL is an uncompressed segment identifier.
  • the processing content includes: modify the Flag flag and change the SL to indicate the compressed segment identifier .
  • End.zip can also include the End operation of the compressed segment identifier itself, where different compressed segment identifiers have different End operation schemes, that is, the embodiments of the present disclosure are compatible with different The compression scheme for the segment identification.
  • the segment routing header of the service message also includes an extension (SRH_Ext) field, and the extension field is used to indicate the first A segment routing header format, and perform the following functions: after a compressed segment identification process is completed, the value of SL is reduced by n, where n is the ratio of the compressed segment identification length to the shortest supported compressed segment identification length, n It is a positive integer; and, after the processing of an uncompressed segment identifier is completed, the value of SL is reduced by m, where m is the ratio of the uncompressed segment identifier length to the shortest supported compressed segment identifier length, and m is a positive integer.
  • the segment routing header of the service message can adopt a new field, defined as SRH_Ext.
  • the SRH_Ext field can support mixed programming of compressed segment identifiers and uncompressed segment identifiers, and even compressed segment identifiers of different lengths.
  • the SL operation is redefined according to the shortest length of the compressed segment identifier. For example, when the supported minimum compressed segment identifier length is 16 bits, the SRH_Ext field defines the following functions:
  • the SL is reduced by 8 in the End operation.
  • the segment routing header uses the existing routing type field, but the function of the routing type field needs to be redefined.
  • the routing type field is used to indicate the second segment routing header format, and the second segment routing header format includes: p compressed segment identifiers occupy t bits of the uncompressed segment identifier length, and t is a positive integer, p is the value obtained by rounding the ratio of the identifier length of an uncompressed segment to the identifier length of a compressed segment.
  • the route type field is used to perform the following function: after all compressed segment identifiers within the length of an uncompressed segment identifier have been processed, the SL is reduced by 1. It should be noted that the route type field can also perform the following functions according to the existing definition: after the processing of an uncompressed segment identification is completed, the value of SL is reduced by 1.
  • SL still represents the number of segment identifiers within the length of an uncompressed segment identifier (128 bits).
  • the compressed segment identifier When the compressed segment identifier is used in the segment routing header of the business message, it is required Combining multiple compressed segment identifiers occupies 128 bits. If it cannot occupy exactly an integer multiple of 128 bits (the integer is t, t is greater than or equal to 1), then fill the reserved field to make up an integer multiple of 128 bits.
  • the SL is reduced by 1. After processing an uncompressed segment identifier, the SL is reduced by 1 in the End operation.
  • the compressed segment identifier is compressed in a uSID (draft-filsfils-spring-net-pgm-extension-srv6-usid-02) manner.
  • uSID raft-filsfils-spring-net-pgm-extension-srv6-usid-02
  • the compressed segment identifier is compressed in a C-SID (draft-li-spring-compressed-srv6-np-00) mode.
  • the segment routing header of the service message or the segment The list can also set a counter (Sub_SL) field used to record the number of unprocessed compressed segment identifiers; each time a compressed segment identifier is processed, the value of the counter field is reduced by 1, where the initial value of the counter field is p(p It is a value obtained by rounding the ratio of the identifier length of an uncompressed segment to the identifier length of a compressed segment).
  • the value of the counter field is zero.
  • the embodiment of the present disclosure also provides a service processing method, which is applied to nodes on a segmented routing path, each node on the segmented routing path is configured with a compressed segment identifier or a non-compressed segment identifier,
  • the critical node is equipped with a compressed segment identifier that additionally has the function of converting the segment identifier pointed to by the SL to the segment identifier type.
  • the critical node is the one that has been configured with the compressed segment identifier among the two adjacent nodes that have been configured with different types of segment identifiers. node.
  • the service processing method includes the following steps S21 to S24.
  • Step S21 Obtain the segment list and the route type field used to indicate the format of the segment routing header from the segment routing header of the received service message.
  • the segment list includes the configured compressed segment identifier and the configured non- Compressed segment ID.
  • the segment routing header compression device Before forwarding the service message, the segment routing header compression device generates a segment list including the compressed segment identifier and the uncompressed segment identifier, and carries the segment list in the segment routing header of the service message.
  • the node on the segment routing path receives the service message sent by the previous hop node, it obtains the segment list from the segment routing header of the service message, and obtains the format used to represent the segment routing header The route type field.
  • Step S22 Process the current segment identifier in the segment list, and modify the SL according to the route type field.
  • the service processing device processes the current segment identifier in the segment list, and the segment identifier is a compressed segment identifier or a non-compressed segment identifier.
  • Different routing types define different ways to modify SL after processing a segment identifier. Therefore, it is necessary to determine the routing type and modify the SL according to the routing type.
  • the SL modification methods under different routing types will be detailed later in conjunction with Figure 3. illustrate.
  • step S23 if the current node is a critical node, the segment identifier pointed to by SL is converted into segment identifier type.
  • the segment identifier types include compressed segment identifiers and uncompressed segment identifiers.
  • the conversion of segment identifier types includes: converting compressed segment identifiers to uncompressed segment identifiers, or converting uncompressed segment identifiers to compressed segments logo.
  • segment identifier which can be a compressed segment identifier or a non-compressed segment identifier
  • SL Segment identification type conversion
  • step S24 the service message is forwarded to the next hop node, and the service message carries the segment identification type pointed to by the SL.
  • the service processing device carries the converted segment identification type obtained in step S23 in the service message, and forwards the service message to the next hop node.
  • the segment list and the route type field used to indicate the format of the segment routing header are obtained from the segment routing header of the received service message, and the segment list includes the configured compression Segment identifier and configured uncompressed segment identifier; process the current segment identifier in the segment list, and modify the SL according to the routing type field; if the current node is a critical node, the segment identifier pointed to by SL is used for segment identification Type conversion; forwarding a service message to the next hop node, the service message carries the segment identification type pointed to by SL; the embodiment of the present disclosure performs segment identification type conversion by converting the segment identification pointed to by SL at the critical node, And modify the SL according to the route type field, which can realize the hybrid networking and hybrid programming of the node configured with the compressed segment identifier and the node configured with the non-compressed segment identifier, making SRv6 suitable for more complex networking environments, which is conducive to rapid advancement.
  • SRv6 is deployed
  • the critical node is a node that has been configured with a compressed segment identifier and the next hop node is a node that has been configured with a non-compressed segment identifier; in this case, the segment identifier pointed to by the SL is classified as a segment identifier type
  • the conversion includes: modifying the type of the segment identifier pointed to by the SL to the non-compressed segment identifier. That is to say, in the message transmission direction, the previous hop node of the critical node is the node that has been configured with the compressed segment identifier, and the next hop node of the critical node is the node that has been configured with the uncompressed segment identifier.
  • the critical node is a node that has been configured with a compressed segment identifier and the previous hop node is a node that has been configured with a non-compressed segment identifier; in this case, the segment identifier pointed to by the SL is classified as a segment identifier type
  • the conversion includes: modifying the type of the segment identifier pointed to by the SL to the compressed segment identifier.
  • the previous hop node of the critical node is the node configured with the uncompressed segment identifier
  • the next hop node of the critical node is the node configured with the compressed segment identifier.
  • the function of converting the segment identifier pointed to by the SL to the segment identifier type can be implemented by setting a flag field.
  • the segment routing header of the service message further includes a flag (Flag) field for indicating the segment identifier type pointed to by the SL, and the segment identifier type includes a compressed segment identifier and an uncompressed segment identifier.
  • Flag 0 represents a non-compressed segment identifier
  • step S23 before performing the segment identifier type conversion on the segment identifier pointed to by the SL, it further includes: obtaining the identifier field from the segment routing header of the service message.
  • the critical node is a configured compressed segment identifier and the next hop node is a node configured with a non-compressed segment identifier
  • the type of the segment identifier pointed to by the SL is modified to a non-compressed segment identifier Including: modifying the value of the flag field to a value representing the identifier of the uncompressed segment, for example, modifying the value of the Flag field to 0.
  • the modification of the type of the segment identifier pointed to by the SL to the compressed segment identifier includes : Modify the value of the flag field to a value representing the identifier of the compressed segment, for example, modify the value of the Flag field to 1.
  • the segment routing header format is defined in the routing type field, and different segment routing header formats are defined below is a detailed description of the SL modification method under different segment routing header formats with reference to FIG. 3.
  • the modification of the SL according to the route type field includes the following steps S231 to S233.
  • Step S231 Determine the segment routing header format according to the routing type field. If the segment routing header format is the first segment routing header format, perform step S232; if the segment routing header format is the second segment routing header format, then Step S233 is executed.
  • the segment routing header format can be determined according to the value of the routing type field. If the value of the routing type field is the first preset value, it is considered to be the first segment routing header format. If the value of the routing type field is If it is the second preset value, it is considered to be the second segment routing header format. For example, the first preset value may be 6, and the second preset value may be 4.
  • the value of the routing type field is the first preset value, which means that the segment routing header of the service message also includes an extension (SRH_Ext) field, and the SL is modified according to the manner defined by the SRH_Ext field.
  • the value of the route type field is the second preset value, which means that the SL is still modified according to the method defined by the route type field (except that the SL modification method defined by the route type field in the embodiment of the present disclosure is different from the existing SL modification method).
  • Step S232 after the processing of a compressed segment identification is completed, the value of SL is subtracted by n, where n is the ratio of the compressed segment identification length to the shortest supported compressed segment identification length, and n is a positive integer; and, After the processing of an uncompressed segment identifier is completed, the value of SL is reduced by m, where m is the ratio of the uncompressed segment identifier length to the shortest supported compressed segment identifier length, and m is a positive integer.
  • the SL should also be based on the shortest supported compression segment identifier length (for example, 16 Digits).
  • step S233 after all compressed segment identifiers within the length of an uncompressed segment identifier have been processed, the SL is reduced by 1.
  • the compressed segment identifier When the compressed segment identifier is used in the segment routing header of the business message, it is required Combining multiple compressed segment identifiers occupies 128 bits. If it cannot occupy exactly an integer multiple of 128 bits (the integer is t, t is greater than or equal to 1), then fill the reserved field to make up an integer multiple of 128 bits. In this case, after processing the compressed segment identifier, only when all the compressed segment identifiers in a 128-bit are processed, the SL is reduced by 1.
  • the completion of all compressed segment identifier processing within the length of the one uncompressed segment identifier includes: all bits after the currently processed segment identifier in the segment list are all zeros.
  • a counter for recording the number of unprocessed compressed segment identifiers is set in the segment routing header of the service message or in the segment list. After processing a compressed segment identifier, the value of Sub_SL is reduced. 1. The initial value of Sub_SL is p. In this case, the completion of all compressed segment identification processing within the one non-compressed segment identification length includes: the value of the counter field is zero.
  • Sub_SL and the value of SL may not be 0 at the same time.
  • SL is already 0, but Sub_SL is not 0, which means that the current processing is in the segment list
  • Example 1 The networking topology of Example 1 is shown in Figure 4.
  • An A-B-D-F-M-Z SRv6 path needs to be created. This path involves mixed programming of compressed SID nodes and non-compressed SID nodes.
  • the AG node is configured with a 32-bit compressed segment identifier and compressed using the uSid compression scheme.
  • the common prefix (uSID Block) of the compressed SID is 32 bits, and each compressed segment identifier is 32 bits. Therefore, one 128 bits are removed After uSID Block, it can represent the compressed SID of 3 SRv6 nodes.
  • Nodes M, N, and Z are configured with 128-bit uncompressed SIDs.
  • FIG. 5 is a schematic diagram of the SRH structure of the A->Z service message transmission direction.
  • SRH as shown in Figure 5 is used to represent the VPN4 service forwarding path of ABDFMZ, where F node uses F:77 to indicate End.
  • the uzip operation realizes the switch from compressed SID to uncompressed SID.
  • Figure 6 is a schematic diagram of the SRH structure of the Z->A service message transmission direction.
  • the SRH shown in Figure 6 is used to represent the VPN4 service forwarding path of the ZMFDBA, where the F node is configured with a 128-bit uncompressed SID, and F: 78 is used to indicate that the End.zip operation is to be performed to realize the switch from the uncompressed SID to the compressed SID.
  • Routing type 4, indicating that the SRH format is the second segment routing header format, that is, the routing type field in the SRH is compatible with the existing SRH.
  • SL is reduced by 1, as shown in the code:
  • the service processing flow of the Z->A service message transmission direction is shown in Figure 8.
  • Example 2 The networking topology of Example 2 is shown in Figure 9.
  • An A-B-D-F-M-Z SRv6 path needs to be created, which involves mixed programming of compressed SID nodes and non-compressed SID nodes.
  • the A-G node uses a 32-bit compressed SID, while the M, N, and Z nodes are configured with a 128-bit uncompressed SID.
  • Figure 10 is a schematic diagram of the SRH_Ext structure of the A->Z service message transmission direction.
  • SRH_Ext as shown in Figure 10 is used to represent the L2VPN service forwarding path of ABDFMZ, where F node uses F:77 to indicate End.
  • the uzip operation realizes the switch from compressed SID to uncompressed SID.
  • Figure 11 is a schematic diagram of the SRH_Ext structure of the Z->A service message transmission direction.
  • the SRH_Ext as shown in Figure 11 is used to represent the L2VPN service forwarding path of ZMFDBA, and the F node uses F: 78 to indicate End.
  • the zip operation realizes the switch from the uncompressed SID to the compressed SID.
  • Example 3 The networking topology of Example 3 is shown in Figure 9.
  • An A-B-D-F-M-Z SRv6 path needs to be created, which involves mixed programming of compressed SID nodes and non-compressed SID nodes.
  • the A-G node uses a 32-bit compressed SID, while the M, N, and Z nodes are configured with a 128b-bit uncompressed SID.
  • Figure 14 is a schematic diagram of the SRH structure of the A->Z service message transmission direction.
  • the SRH shown in Figure 14 is used to represent the L2VPN service forwarding path of ABDFMZ, and the F node uses F: 77 to indicate that End.
  • the uzip operation realizes the switch from compressed SID to uncompressed SID.
  • Figure 15 is a schematic diagram of the SRH structure of the Z->A service message transmission direction.
  • the SRH shown in Figure 15 is used to represent the L2VPN service forwarding path of ZMFDBA, where the F node is a 128-bit encoding, and F: 78 indicates that the End.zip operation is to be performed to realize the switch from the uncompressed SID to the compressed SID.
  • the compatible processing method includes: SL still indicates the number of SIDs of 128 bits, when compressed SID is used in SRH, multiple compressed SIDs are combined to occupy 128 bits When multiple compressed SIDs are combined to be an integer multiple of 128 bits, the reserved bytes need to be filled to make up an integer multiple of 128 bits. For example, as shown in Figure 14, in the A->Z service message transmission direction, there are only three compressed SIDs in the segment list. At this time, to make up a complete 128-bit code, all 0 codes must be added at the end.
  • the service processing flow of the A->Z service message transmission direction is shown in Figure 16.
  • the embodiments of the present disclosure provide an SRH compression method that supports both compressed SID format and uncompressed SID format in the SRH header of SRv6, so that the SRv6 forwarding path can include nodes represented by compressed SIDs and can also include nodes represented by non-compressed SIDs.
  • the node of SRv6 expands the application scenarios of SRv6. Define a new flag field to indicate whether the SID pointed to by the SL in the SRH is a compressed SID or an uncompressed SID, and define a new function to realize the compressed SID to uncompressed SID and uncompressed SID to compressed in the SRv6 forwarding path SID conversion processing.
  • the segment routing header compression device includes a configuration module 101, a first generation module 102, and a second generation module. 103.
  • the configuration module 101 is configured to configure a compressed segment identifier or a non-compressed segment identifier for each node on the segmented routing path, and configure critical nodes in the segmented routing path to additionally have the number of remaining segments (SL
  • the segment identifier pointed to by) is a compressed segment identifier that performs a function of segment identifier type conversion, and the critical node is a node that has been configured with a compressed segment identifier among two adjacent nodes that have been configured with different types of segment identifiers.
  • the first generating module 102 is configured to generate a segment list, the segment list including a configured compressed segment identifier and a configured non-compressed segment identifier.
  • the second generation module 103 is configured to generate a segment routing header of a service message, where the segment routing header of the service message includes the segment list and a routing type field used to indicate the format of the segment routing header, The format of the segment routing header matches the format of the compressed segment identifier.
  • the critical node is a node that has been configured with a compressed segment identifier
  • the next hop node is a node that has been configured with a non-compressed segment identifier
  • the segment identifier pointed to by the remaining segment number (SL) is performed
  • the function of segment identifier type conversion is a first conversion function, and the first conversion function is to convert the type of the segment identifier pointed to by the SL into an uncompressed segment identifier.
  • the critical node is a node that has been configured with a compressed segment identifier
  • the previous hop node is a node that has been configured with a non-compressed segment identifier
  • the segment identifier pointed to by the remaining segment number (SL) is performed
  • the function of segment identifier type conversion is a second conversion function, and the second conversion function is to convert the type of the segment identifier pointed to by the SL into a compressed segment identifier.
  • the segment routing header of the service message further includes a flag field for indicating the type of segment identification pointed to by the SL;
  • the first conversion function includes segment routing of the received service message The value of the flag field in the header is modified to indicate the value of the uncompressed segment identifier; and/or, the second conversion function includes modifying the value of the flag field in the segment routing header of the received service message to indicate Compress the value of the segment ID.
  • the segment routing header of the service message further includes an extension field, the extension field is used to indicate the format of the first segment routing header, and performs the following function: after a compressed segment identification process is completed , The value of SL is subtracted by n, where n is the ratio of the length of the compressed segment identifier to the shortest supported compressed segment identifier length, and n is a positive integer; and, after the processing of an uncompressed segment identifier is completed, the SL The value of minus m, m is the ratio of the length of the uncompressed segment identifier to the shortest supported compressed segment identifier length, and m is a positive integer.
  • the routing type field is used to indicate a second segment routing header format
  • the second segment routing header format includes: p compressed segment identifiers occupy t bits of uncompressed segment identifier length Bit, t is a positive integer, p is the value obtained by rounding the ratio of the length of an uncompressed segment identifier to the length of a compressed segment identifier, if the sum of p compressed segment identifier lengths is less than t uncompressed segments To identify the length, use reserved bytes to fill the remaining length;
  • the route type field is used to perform the following function: after all compressed segment identifiers within the length of an uncompressed segment identifier have been processed, the SL is reduced by one.
  • the completion of processing all compressed segment identifiers within the length of the one uncompressed segment identifier includes: all bits after the currently processed segment identifier in the segment list are all zeros.
  • the segment routing header of the service message or the segment list further includes a counter field for recording the number of unprocessed compressed segment identifiers; each time a compressed segment identifier is processed, the The value of the counter field is reduced by 1, and the initial value of the counter field is p; all compressed segment identifiers within the length of the one uncompressed segment identifier have been processed, including: the value of the counter field is zero.
  • the embodiments of the present disclosure also provide a service processing device, which is applied to nodes of a segmented routing path, and each node on the segmented routing path is configured with a compressed segment identifier or a non-compressed segment identifier.
  • the critical node on the segment routing path is configured with a compressed segment identifier that additionally has the function of converting the segment identifier pointed to by the remaining segment quantity (SL), and the critical node is configured with different types of segments.
  • SL remaining segment quantity
  • the service processing apparatus includes an acquisition module 201, a processing module 202, a conversion module 203, and a forwarding module 204.
  • the obtaining module 201 is configured to obtain a segment list and a route type field used to indicate the format of the segment routing header from the segment routing header of the received service message, where the segment list includes the configured compressed segment identifier And the configured uncompressed segment identifier.
  • the processing module 202 is configured to process the current segment identifier in the segment list, and modify the SL according to the route type field.
  • the conversion module 203 is configured to convert the segment identifier type pointed to by the SL if the current node is a critical node.
  • the forwarding module 204 is configured to forward the service message to the next hop node, and the service message carries the segment identification type pointed to by the SL.
  • the critical node is a node that has been configured with a compressed segment identifier and the next hop node is a node that has been configured with a non-compressed segment identifier; the conversion module 203 is configured to modify the type of the segment identifier pointed to by the SL Identifies the uncompressed segment.
  • the critical node is a node that has been configured with a compressed segment identifier and the previous hop node is a node that has been configured with a non-compressed segment identifier; the conversion module 203 is configured to modify the type of the segment identifier pointed to by the SL Identifies the compressed segment.
  • the segment routing header of the service message further includes a flag field used to indicate the type of segment identification pointed to by the SL.
  • the obtaining module 201 is further configured to obtain the flag field from the segment routing header of the service message before the conversion module 203 converts the segment identifier pointed to by the SL to the segment identifier type.
  • the processing module 202 is configured to modify the value of the flag field to a value representing a non-compressed segment identifier; and/or to modify the value of the flag field to a value representing a compressed segment identifier.
  • the processing module 202 is configured to, when the segment routing header is in the first segment routing header format, after the processing of a compressed segment identification is completed, the value of SL is reduced by n, where n is the The ratio of the length of the compressed segment identifier to the length of the shortest supported compressed segment identifier, where n is a positive integer; and, after the processing of an uncompressed segment identifier is completed, the value of SL is reduced by m, where m is the uncompressed segment identifier The ratio of the length to the supported shortest compressed segment identifier length, m is a positive integer.
  • the processing module 202 is configured to, when the segment routing header is in the second segment routing header format, after all compressed segment identifiers within the length of an uncompressed segment identifier are processed, the SL minus 1; where p compressed segment identifiers occupy t bits of uncompressed segment identifier length, t is a positive integer, and p is the ratio of the identifier length of an uncompressed segment to the length of a compressed segment identifier. The value obtained by rounding, if the sum of the lengths of p compressed segment identifiers is less than the length of t uncompressed segment identifiers, the remaining length is filled with reserved bytes.
  • the completion of processing all compressed segment identifiers within the length of the one uncompressed segment identifier includes: all bits after the currently processed segment identifier in the segment list are all zeros.
  • the segment routing header of the service message or the segment list further includes a counter field for recording the number of unprocessed compressed segment identifiers; each time a compressed segment identifier is processed, the The value of the counter field is reduced by 1, and the initial value of the counter field is p; all compressed segment identifiers within the length of the one uncompressed segment identifier have been processed, including: the value of the counter field is zero.
  • the embodiments of the present disclosure also provide a computer device, which includes: one or more processors and a storage device; wherein, one or more programs are stored on the storage device, and when the one or more programs are When executed by or multiple processors, the foregoing one or more processors implement the segment routing header compression method provided in the foregoing embodiment.
  • the embodiments of the present disclosure also provide a computer-readable medium on which a computer program is stored, wherein the computer program implements the service processing method provided in the foregoing embodiment when the computer program is executed.
  • Such software may be distributed on a computer-readable medium
  • the computer-readable medium may include a computer storage medium (or non-transitory medium) and a communication medium (or transitory medium).
  • the term computer storage medium includes volatile and non-volatile data implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data).
  • Information such as computer-readable instructions, data structures, program modules, or other data.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tapes, magnetic disk storage or other magnetic storage devices, or Any other medium used to store desired information and that can be accessed by a computer.
  • communication media usually contain computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as carrier waves or other transmission mechanisms, and may include any information delivery media. .

Landscapes

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

Abstract

本公开提供一种分段路由头压缩方法，为分段路由路径上各节点配置压缩分段标识或非压缩分段标识，并为临界节点配置额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识；生成分段列表，分段列表包括已配置的压缩分段标识和非压缩分段标识；生成业务报文的分段路由头，业务报文的分段路由头包括分段列表和用于表示分段路由头格式的路由类型字段,分段路由头格式与压缩分段标识的格式相匹配。本公开还提供一种业务处理方法、一种分段路由头压缩装置、一种业务处理装置、一种计算机设备和一种计算机可读介质。

Description

分段路由头压缩方法及装置、业务处理方法及装置
相关申请的交叉引用
本申请要求于2020年4月13日提交的中国专利申请NO.202010285171.9的优先权，该中国专利申请的内容通过引用的方式整体合并于此。
技术领域
本公开涉及无线通信技术领域，具体涉及分段路由头压缩方法及装置、业务处理方法及装置、计算机设备及计算机可读介质。
背景技术
分段路由(Segment Routing，SR)是一种实现源路由的技术，RFC8402定义了两种标准的SR机制，即基于MPLS(Multi-Protocol Label Switching，多协议标签交换)转发面的SR-MPLS和基于IPv6(Internet Protocol Version 6，互联网协议第6版)转发面的SRv6。SRv6可直接基于IPv6扩展路由头实现，无需添加额外封装，实现了IP(Internet Protocol，网际互连协议)转发和隧道转发的统一，同时由于SRv6采用了与IPv6地址相同的128位(bit)格式的SID(Segment ID，分段标识)，并将SID分为定位符(Locator)和功能(Function)两部分，可以实现灵活的网络和业务混合编程，因此SRv6得到了业界的广泛认可。
但是，SRv6方案下，业务路径的描述采用了一系列128位的SID所组成的SID列表，造成报文头开销过大的问题。为解决该问题，业界提出了多种SRH((Segment Routing Header，分段路由头)压缩的解决方案，比如uSID方案(draft-filsfils-spring-net-pgm-extension-srv6-usid-02)、以及普通压缩SID(C-SID)方案 (draft-li-spring-compressed-srv6-np-00)。
在SRv6方案中，转发节点(Transit)只需处理普通IPv6转发，端节点(Endpoint)则需要处理SRH头，而在上述SRH头压缩方案中，要求所有端节点均采用压缩SID格式(C-SID方案允许最后一跳端节点采用非压缩格式，但不允许中间节点采用非压缩格式)，也就是说，参与IPv6报文转发的端节点必须具有支持压缩SID的能力，这对网络节点的SRH处理能力，对网络的SID规划提出了很高的要求，一定程度上限制了SRv6的推广应用。
公开内容
第一方面，本公开实施例提供一种分段路由头压缩方法，包括：
为分段路由路径上各节点配置压缩分段标识或非压缩分段标识，并为所述分段路由路径中的临界节点配置额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点；
生成分段列表，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；
生成业务报文的分段路由头，其中，所述业务报文的分段路由头包括所述分段列表和用于表示分段路由头格式的路由类型字段，所述分段路由头格式与所述压缩分段标识的格式相匹配。
第二方面，本公开实施例还提供一种业务处理方法，应用于分段路由路径的节点，所述分段路由路径上各节点配置有压缩分段标识或非压缩分段标识,所述分段路由路径上的临界节点配置有额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点，所述方法包括：
从接收到的业务报文的分段路由头中获取分段列表和用于表示分段路由头格式的路由类型字段，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；
处理所述分段列表中当前分段标识，并根据所述路由类型字段修改剩余分段数量；
若当前节点为临界节点，则将剩余分段数量指向的分段标识进行分段标识类型转换；
向下一跳节点转发所述业务报文，所述业务报文中携带剩余分段数量指向的分段标识类型。
第三方面，本公开实施例还提供一种分段路由头压缩装置，包括配置模块、第一生成模块和第二生成模块，
所述配置模块配置为，为分段路由路径上各节点配置压缩分段标识或非压缩分段标识，并为所述分段路由路径中的临界节点配置额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点；
所述第一生成模块配置为，生成分段列表，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；
所述第二生成模块配置为，生成业务报文的分段路由头，其中，所述业务报文的分段路由头包括所述分段列表和用于表示分段路由头格式的路由类型字段，所述分段路由头格式与所述压缩分段标识的格式相匹配。
第四方面，本公开实施例还提供一种业务处理装置，应用于分段路由路径的节点，所述分段路由路径上各节点配置有压缩分段标识或非压缩分段标识,所述分段路由路径上的临界节点配置有额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点；所述业务处理装置包括获取模块、处理模块、转换模块和转发模块，
所述获取模块配置为，从接收到的业务报文的分段路由头中获取分段列表和用于表示分段路由头格式的路由类型字段，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；
所述处理模块配置为，处理所述分段列表中当前分段标识，并 根据所述路由类型字段修改剩余分段数量；
所述转换模块配置为，若当前节点为临界节点，则将剩余分段数量指向的分段标识进行分段标识类型转换；
所述转发模块配置为，向下一跳节点转发所述业务报文，所述业务报文中携带剩余分段数量指向的分段标识类型。
第五方面，本公开实施例还提供一种计算机设备，包括：一个或多个处理器以及存储装置；其中，存储装置上存储有一个或多个程序，当上述一个或多个程序被上述一个或多个处理器执行时，使得上述一个或多个处理器实现如前述实施例所提供的分段路由头压缩方法或业务处理方法。
第六方面，本公开实施例还提供了一种计算机可读介质，其上存储有计算机程序，其中，该计算机程序被执行时实现如前述实施例所提供的分段路由头压缩方法或业务处理方法。
附图说明
图1为本公开实施例提供的分段路由头压缩方法的流程图；
图2为本公开实施例提供的业务处理方法的流程图；
图3为本公开实施例提供的根据路由类型字段修改剩余分段数量的流程图；
图4为本公开具体实例1提供的网络拓图；
图5为本公开具体实例1提供的A->Z业务报文传输方向的SRH结构的示意图；
图6为本公开具体实例1提供的Z->A业务报文传输方向的SRH结构的示意图；
图7为本公开具体实例1提供的A->Z业务报文传输方向的业务处理过程的示意图；
图8为本公开具体实例1提供的Z->A业务报文传输方向的业务处理过程的示意图；
图9为本公开具体实例2提供的网络拓图；
图10为本公开具体实例2提供的A->Z业务报文传输方向的 SRH_Ext结构的示意图；
图11为本公开具体实例2提供的Z->A业务报文传输方向的SRH_Ext结构的示意图；
图12为本公开具体实例2提供的A->Z业务报文传输方向的业务处理过程的示意图；
图13为本公开具体实例2提供的Z->A业务报文传输方向的业务处理过程的示意图；
图14为本公开具体实例3提供的A->Z业务报文传输方向的SRH结构的示意图；
图15为本公开具体实例3提供的Z->A业务报文传输方向的SRH结构的示意图；
图16为本公开具体实例3提供的A->Z业务报文传输方向的业务处理过程的示意图；
图17为本公开具体实例3提供的Z->A业务报文传输方向的业务处理过程的示意图；
图18为本公开实施例提供的分段路由头压缩装置的结构示意图；
图19为本公开实施例提供的业务处理装置的结构示意图。
具体实施方式
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现，本文阐述的实施例不应当被解释为限制性的。反之，提供这些实施例的目的在于使本公开尽可能地透彻和完整，并使本领域技术人员充分理解本公开的范围。
如本文所使用的，术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本文所使用的，单数形式“一个”和“该”意欲包括至少一个，不排除多个，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在特定特征、整体、步骤、操作、元件和/或组件，但不排除存在或可添加一个或 多个其他特征、整体、步骤、操作、元件、组件和/或其群组。
本文所述实施例可借助本公开的理想示意图而参考平面图和/或截面图进行描述。因此，可根据制造技术和/或容限来修改示例图示。因此，本公开实施例不限于附图中所示的实施例，而是包括基于制造工艺而形成的配置修改了的实施例。
除非另外限定，否则本文所用的所有术语(包括技术术语和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
本公开实施例提供一种分段路由头压缩方法，如图1所示，所述分段路由头压缩方法包括以下步骤S11至S13。
步骤S11，为分段路由路径上各节点配置压缩分段标识或非压缩分段标识，并为分段路由路径中的临界节点配置额外具有将剩余分段数量(Segments Lef，SL)指向的分段标识进行分段标识类型转换的功能的压缩分段标识。
所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点。在本公开实施例中，分段标识的类型包括压缩分段标识和非压缩分段标识。例如，分段路由路径为节点A-节点B-节点C，其中，为节点A和节点B配置压缩分段标识，为节点C配置非压缩分段标识，节点B与节点C的分段标识的类型不同，且节点B配置的是压缩分段标识，因此，节点B为该分段路由路径中的临界节点。
在本步骤中，分段路由头压缩装置为分段路由路径上的每个节点要么配置压缩分段标识，要么配置非压缩分段标识，并为其中的临界节点配置额外具有将SL(剩余分段数量)指向的分段标识进行分段标识类型转换的功能的压缩分段标识。也就是说，压缩分段标识包括两种，一种为配置在非临界节点上的压缩分段标识，该种压缩分段标识可以采用现有的压缩分段标识实现；另一种为配置在临界节点上的压缩分段标识，该种压缩分段标识具有将SL指向的分段标识进行 分段标识类型转换的功能，例如可以通过定义该分段标识的功能字段实现。
分段路由头压缩装置将压缩分段标识和非压缩分段标识配置到相应的节点后，各节点可以将压缩分段标识和非压缩分段标识通过IGP(内部网关协议)扩散到整个SR域。
步骤S12，生成分段列表，分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识。
在本步骤中，分段路由路径的源节点计算生成分段列表，分段列表按网络编程需要，压入各节点的压缩分段标识或者非压缩分段标识。在分段列表中，分段路由路径上各节点的分段标识按照业务报文的转发顺序排列。
步骤S13，生成业务报文的分段路由头，其中，业务报文的分段路由头包括分段列表和用于表示分段路由头格式的路由类型字段，所述分段路由头格式与所述压缩分段标识的格式相匹配。
在本步骤中，将分段列表携带在业务报文的分段路由头(Segment Routing Header，SRH)中，业务报文的分段路由头还包括路由类型(Routing type)字段，路由类型字段用于表示分段路由头格式，分段路由头格式与压缩分段标识的格式相匹配，不同的分段路由头格式定义的SL的修改方式不同，不同分段路由头格式定义的SL修改方式后续再详细说明。
本公开实施例提供的分段路由头压缩方法中，为分段路由路径上各节点配置压缩分段标识或非压缩分段标识，并为临界节点配置额外具有将SL指向的分段标识进行分段标识类型转换的功能的压缩分段标识，临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点；生成分段列表，分段列表包括已配置的压缩分段标识和非压缩分段标识；生成业务报文的分段路由头，其中，业务报文的分段路由头包括分段列表和用于表示分段路由头格式的路由类型字段，所述分段路由头格式与所述压缩分段标识的格式相匹配；本公开实施例通过进行分段标识类型转换以及定义与压缩分段标识的格式相匹配的分段路由头格式，可以实现配置压缩分段标识的节点 和配置非压缩分段标识的节点的混合组网和混合编程，使得SRv6可适用于更复杂的组网环境，有利于快速推进SRv6在现网的落地部署。
在一些实施方式中，临界节点为已配置压缩分段标识、且下一跳节点为已配置非压缩分段标识的节点，例如，分段路由路径为节点A-节点B-节点C，业务报文传输路径为A-B-C，其中，节点A和节点B配置有压缩分段标识，节点C配置有非压缩分段标识，节点B即为临界节点。该情况下，所述将SL指向的分段标识进行分段标识类型转换的功能为第一转换功能，第一转换功能为将SL指向的分段标识的类型转换为非压缩分段标识。
在一些实施方式中，临界节点为已配置压缩分段标识、且上一跳节点为已配置非压缩分段标识的节点，例如，分段路由路径为节点A-节点B-节点C，业务报文传输路径为C-B-A，其中，节点A和节点B配置有压缩分段标识，节点C配置有非压缩分段标识，节点B即为临界节点。该情况下，所述将SL指向的分段标识进行分段标识类型转换的功能为第二转换功能，第二转换功能为将SL指向的分段标识的类型转换为压缩分段标识。
在一些实施方式中，所述业务报文的分段路由头还可以包括用于表示SL指向的分段标识类型的标志(Flag)字段，例如，Flag字段的值为1表示当前SL指向的分段标识为压缩分段标识，Flag字段的值为0表示当前SL指向的分段标识为非压缩分段标识。
所述第一转换功能包括将接收到的业务报文的分段路由头中的标志字段的值修改为表示非压缩分段标识的值(即Flag＝0)。也就是说，定义第一转换功能为End.uzip，用于实现由压缩分段标识到非压缩分段标识的转换处理，其处理内容包括：修改Flag标志，将SL改为指示非压缩分段标识。需要说明的是，End.uzip的处理内容还可以包括压缩分段标识本身的End(终结)操作，其中，不同的压缩分段标识有不同的End操作方案，也就是说，本公开实施例可兼容不同分段标识的压缩方案。
所述第二转换功能包括将接收到的业务报文的分段路由头中的标志字段的值修改为表示压缩分段标识的值(即Flag＝1)。也就是 说，定义第二转换功能为End.zip，用于实现由非压缩分段标识到压缩分段标识的转换处理，其处理内容包括：修改Flag标志，将SL改为指示压缩分段标识。需要说明的是，End.zip的处理内容同样还可以包括压缩分段标识本身的End(终结)操作，其中，不同的压缩分段标识有不同的End操作方案，即本公开实施例可兼容不同分段标识的压缩方案。
在一些实施方式中，路由类型字段的值为第一预设值，例如，Routing type＝6，相应的，业务报文的分段路由头还包括扩展(SRH_Ext)字段，扩展字段用于表示第一分段路由头格式，并执行以下功能：在一个压缩分段标识处理完成之后，将SL的值减n，n为压缩分段标识长度与所支持的最短压缩分段标识长度的比值，n为正整数；以及，在一个非压缩分段标识处理完成后，将SL的值减m，m为非压缩分段标识长度与所支持的最短压缩分段标识长度的比值，m为正整数。
也就是说，业务报文的分段路由头可采用新的字段，定义为SRH_Ext，该SRH_Ext字段可支持压缩分段标识和非压缩分段标识的混合编程，甚至是不同长度的压缩分段标识的编程，此时根据压缩分段标识的最短长度来重新定义SL操作，例如，所支持的最短压缩分段标长度为16位时，SRH_Ext字段定义以下功能：
处理完16位的压缩分段标识后，End操作中将SL减1；
处理完32位的压缩分段标识后，End操作中将SL减2；
处理完64位的压缩分段标识后，End操作中将SL减4；
处理完一个非压缩分段标识(一个非压缩分段标识的长度为128位)后，End操作中将SL减8。
在一些实施方式中，路由类型字段的值为第二预设值，例如，Routing type＝4，此时，分段路由头沿用现有的路由类型字段，但是需要重新定义路由类型字段的功能，用以同时兼容压缩分段标识和非压缩分段标识。具体的，路由类型字段用于表示第二分段路由头格式，第二分段路由头格式包括：p个压缩分段标识占用t个非压缩分段标识长度的比特位，t为正整数，p为对一个非压缩分段标识长度与一 个压缩分段标识长度的比值进行取整得到的值，若p个压缩分段标识长度之和小于t个非压缩分段标识长度，则利用保留字节填充剩余长度。该情况下，路由类型字段用于执行以下功能：在一个非压缩分段标识长度内的全部压缩分段标识均处理完成之后，将SL减1。需要说明的是，路由类型字段还可以按照现有的定义执行以下功能：在一个非压缩分段标识处理完成之后，将SL的值减1。
也就是说，在Routing type＝4时，SL仍然表示一个非压缩分段标识长度(128位)内的分段标识的数量，业务报文的分段路由头中采用压缩分段标识时，需要将多个压缩分段标识组合起来占用128位，如果无法正好占用整数倍(该整数为t，t大于等于1)个128位,则填充保留字段，凑成128位的整数倍。在处理完压缩分段标识后，仅当一个128位中的全部压缩分段标识均处理完后，才将SL减1。在处理完一个非压缩分段标识后，End操作中将SL减1。
在处理压缩分段标识时，需要判断一个128位中的全部压缩分段标识是否都处理完，才能确定是否修改SL的值。
在一些实施方式中，例如，压缩分段标识采用uSID(draft-filsfils-spring-net-pgm-extension-srv6-usid-02)方式压缩。该情况下，所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成是指：分段列表中当前处理的分段标识之后的比特位全部为零。
在一些实施方式中，例如，压缩分段标识采用C-SID(draft-li-spring-compressed-srv6-np-00)方式压缩，该情况下，业务报文的分段路由头中或分段列表中还可以设置用于记录未处理压缩分段标识数量的计数器(Sub_SL)字段；每处理完成一个压缩分段标识，将计数器字段的值减1，其中，计数器字段的初始值为p(p为对一个非压缩分段标识长度与一个压缩分段标识长度的比值进行取整得到的值)。该情况下，所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成包括：计数器字段的值为零。
本公开实施例还提供一种业务处理方法，所述方法应用于分段 路由路径的节点，分段路由路径上各节点配置有压缩分段标识或非压缩分段标识,分段路由路径上的临界节点配置有额外具有将SL指向的分段标识进行分段标识类型转换的功能的压缩分段标识，临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点。如图2所示，所述业务处理方法包括以下步骤S21至S24。
步骤S21，从接收到的业务报文的分段路由头中获取分段列表和用于表示分段路由头格式的路由类型字段，分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识。
在进行业务报文转发之前，分段路由头压缩装置生成包括压缩分段标识和非压缩分段标识的分段列表，并将分段列表携带在业务报文的分段路由头中。在本步骤中，分段路由路径上的节点接收到上一跳节点发送的业务报文后，从业务报文的分段路由头中获取分段列表，并获取用于表示分段路由头格式的路由类型字段。
步骤S22，处理分段列表中当前分段标识，并根据路由类型字段修改SL。
在本步骤中，业务处理装置处理分段列表中当前分段标识，该分段标识为压缩分段标识或非压缩分段标识。不同的路由类型定义的在处理完一个分段标识之后SL的修改方式不同，因此，需要确定路由类型，并根据路由类型进行SL的修改，不同路由类型下的SL修改方式后续结合图3再详细说明。
步骤S23，若当前节点为临界节点，则将SL指向的分段标识进行分段标识类型转换。
分段标识类型包括压缩分段标识和非压缩分段标识，进行分段标识类型转换包括：将压缩分段标识转换为非压缩分段标识，或者，将非压缩分段标识转换为压缩分段标识。
需要说明的是，若当前节点为非临界节点，则执行配置在当前节点的分段标识(可以为压缩分段标识或非压缩分段标识)定义的功能，无需将SL指向的分段标识进行分段标识类型转换。
步骤S24，向下一跳节点转发业务报文，业务报文中携带SL指向的分段标识类型。
在本步骤中，业务处理装置将步骤S23得到的转换后的分段标识类型携带在业务报文中，并将业务报文转发至下一跳节点。
本公开实施例提供的业务处理方法中，从接收到的业务报文的分段路由头中获取分段列表和用于表示分段路由头格式的路由类型字段，分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；处理分段列表中当前分段标识，并根据路由类型字段修改SL；若当前节点为临界节点，则将SL指向的分段标识进行分段标识类型转换；向下一跳节点转发业务报文，所述业务报文中携带SL指向的分段标识类型；本公开实施例通过在临界节点将SL指向的分段标识进行分段标识类型转换，并根据路由类型字段修改SL，可以实现配置压缩分段标识的节点和配置非压缩分段标识的节点的混合组网和混合编程，使得SRv6可适用于更复杂的组网环境，有利于快速推进SRv6在现网的落地部署。
在一些实施方式中，临界节点为已配置压缩分段标识、且下一跳节点为已配置非压缩分段标识的节点；该情况下，所述将SL指向的分段标识进行分段标识类型转换(即步骤S23)包括：将SL指向的分段标识的类型修改为非压缩分段标识。也就是说，在报文传输方向上，临界节点的上一跳节点为已配置压缩分段标识的节点，临界节点的下一跳节点为已配置非压缩分段标识的节点。
在一些实施方式中，临界节点为已配置压缩分段标识、且上一跳节点为已配置非压缩分段标识的节点；该情况下，所述将SL指向的分段标识进行分段标识类型转换(即步骤S23)包括：将SL指向的分段标识的类型修改为压缩分段标识。也就是说，在报文传输方向上，临界节点的上一跳节点为已配置非压缩分段标识的节点，临界节点的下一跳节点为已配置压缩分段标识的节点。
在一些实施方式中，将SL指向的分段标识进行分段标识类型转换的功能可以通过设置标志字段实现。具体的，业务报文的分段路由头还包括用于表示SL指向的分段标识类型的标志(Flag)字段，分段标识类型包括压缩分段标识和非压缩分段标识。例如，可以定义Flag＝0表示非压缩分段标识，Flag＝1表示压缩分段标识。
相应的，在步骤S23中，将SL指向的分段标识进行分段标识类型转换之前，还包括：从业务报文的分段路由头中获取标志字段。
相应的，针对临界节点为已配置压缩分段标识、且下一跳节点为已配置非压缩分段标识的节点的情形，所述将SL指向的分段标识的类型修改为非压缩分段标识包括：将标志字段的值修改为表示非压缩分段标识的值，例如，将Flag字段的值修改为0。
相应的，针对临界节点为已配置压缩分段标识、且上一跳节点为已配置非压缩分段标识的节点的情形，所述将SL指向的分段标识的类型修改为压缩分段标识包括：将标志字段的值修改为表示压缩分段标识的值，例如，将Flag字段的值修改为1。
在业务报文转发过程中，处理完分段标识之后，需要对SL进行修改，在本公开实施例中，在路由类型字段中定义了分段路由头格式，并定义了不同分段路由头格式下SL的修改方式，以下结合图3对不同分段路由头格式下的SL修改方式进行详细说明。
在一些实施方式中，如图3所示，所述根据所述路由类型字段修改SL(即步骤S23)包括以下步骤S231至S233。
步骤S231，根据路由类型字段确定分段路由头格式，若分段路由头格式为第一分段路由头格式，则执行步骤S232；若分段路由头格式为第二分段路由头格式，则执行步骤S233。
在一些实施方式中，可根据路由类型字段的值确定分段路由头格式，若路由类型字段的值为第一预设值，则认为是第一分段路由头格式，若路由类型字段的值为第二预设值，则认为是第二分段路由头格式，例如，第一预设值可以为6，第二预设值可以为4。路由类型字段的值为第一预设值，表示业务报文的分段路由头中还包括扩展(SRH_Ext)字段，则根据SRH_Ext字段定义的方式修改SL。路由类型字段的值为第二预设值，表示仍然根据路由类型字段定义的方式修改SL(只不过本公开实施例中路由类型字段定义的SL修改方式与现有的SL修改方式不同)。
步骤S232，在一个压缩分段标识处理完成之后，将SL的值减n，n为所述压缩分段标识长度与所支持的最短压缩分段标识长度的比 值，n为正整数；以及，在一个非压缩分段标识处理完成后，将SL的值减m，m为非压缩分段标识长度与所支持的最短压缩分段标识长度的比值，m为正整数。
在本步骤中，Routing type＝6时，根据压缩分段标识的最短长度来重新定义修改SL的操作，比如：所支持的最短压缩分段标长度为16位时，处理完16位的压缩分段标识后，End操作中将SL减1(n＝16/16＝1)；处理完32位的压缩分段标识后，End操作中将SL减2(n＝32/16＝2)；处理完64位的压缩分段标识后，End操作中将SL减4(n＝64/16＝4)；以及，处理完128位的非压缩分段标识后，End操作中将SL减8(m＝128/16＝8)。
需要说明的是，为了保证校验正确，相应的，在分段路由头中的Last Entry(末端指示)字段中定义，校验时SL也应按照所支持的最短压缩分段标识长度(例如16位)的倍数来计算。
步骤S233，在一个非压缩分段标识长度内的全部压缩分段标识均处理完成之后，将SL减1。
在第二分段路由头格式中，p个压缩分段标识占用t个非压缩分段标识长度的比特位，t为正整数，p为对一个非压缩分段标识长度与一个压缩分段标识长度的比值进行取整得到的值，若p个压缩分段标识长度之和小于t个非压缩分段标识长度，则利用保留字节填充剩余长度。也就是说，在Routing type＝4时，SL仍然表示一个非压缩分段标识长度(128位)内的分段标识的数量，业务报文的分段路由头中采用压缩分段标识时，需要将多个压缩分段标识组合起来占用128位，如果无法正好占用整数倍(该整数为t，t大于等于1)个128位,则填充保留字段，凑成128位的整数倍。该情况下，在处理完压缩分段标识后，仅当一个128位中的全部压缩分段标识均处理完，才将SL减1。
需要说明的是，在本步骤中，在一个非压缩分段标识处理完成之后，将SL的值减1。
在本公开实施例中，在处理压缩分段标识时，需要判断一个128位中的全部压缩分段标识是否都处理完，才能确定是否修改SL的值。
在一些实施方式中，例如对于采用uSID方式压缩的压缩分段标识，可以通过判断剩余比特位的方式判断128位中的全部压缩分段标识是否都处理完成。该情况下，所述一个非压缩分段标识长度内的全部压缩分段标识处理均完成包括：分段列表中当前处理的分段标识之后的比特位全部为零。
在一些实施方式中，例如对于采用C-SID方式压缩的压缩分段标识，可以通过设置计数器的方式判断128位中的全部压缩分段标识是否都处理完成。具体的，在业务报文的分段路由头中或分段列表中设置用于记录未处理压缩分段标识数量的计数器(Sub_SL)字段，每处理完一个压缩分段标识，将Sub_SL的值减1，Sub_SL的初始值为p。该情况下，所述一个非压缩分段标识长度内的全部压缩分段标识处理均完成包括：计数器字段的值为零。
需要说明的是，Sub_SL的值与SL的值不一定同时为0，在处理压缩分段标识时，有可能SL已经为0，但Sub_SL并不为0，此时表示当前处理到分段列表中的最后一个128位，但还有压缩分段标识未处理完，不应当做最后一跳处理。
为了清楚描述本公开实施例的方案，以下分别通过3个具体实例对本公开实施例的方案进行详细说明。
实例1
实例1的组网拓扑如图4所示，现有一个VPN4业务，需创建A-B-D-F-M-Z的SRv6路径，该路径涉及压缩SID节点与非压缩SID节点的混合编程。A-G节点配置有32位的压缩分段标识，且采用uSid的压缩方案压缩，压缩SID的共同前缀(uSID Block)为32位，每个压缩分段标识为32位，因此，一个128位中除去uSID Block后可表示3个SRv6节点的压缩SID。节点M、N、Z配置有128位的非压缩SID。
SRH压缩过程中，进行如下定义：
(1)在SRH中定义Flag＝1表示当前为压缩SID，Flag＝0表示当前为非压缩SID；
(2)定义压缩SID与非压缩SID的临界节点的第一转换功能End.uzip(编码为0x77)，实现将SL指向的分段标识的类型由压缩SID转换为非压缩SID，代码如下：
Figure PCTCN2021086543-appb-000001
(3)定义非压缩SID与压缩SID的临界节点的第二转换功能End.zip(编码为0x78)，实现将SL指向的分段标识的类型由压非缩SID转换为压缩SID，代码如下：
Figure PCTCN2021086543-appb-000002
图5为A->Z业务报文传输方向的SRH结构的示意图，在A节点，采用如图5所示的SRH表示A-B-D-F-M-Z的VPN4业务转发路径，其中F节点采用F:77表示要执行End.uzip操作，实现压缩SID向非压缩SID的切换。
图6为Z->A业务报文传输方向的SRH结构的示意图，在Z节点，采用如图6所示的SRH表示Z-M-F-D-B-A的VPN4业务转发路径，其中F节点配置128位的非压缩SID，并且采用F:78表示要执行End.zip操作，实现非压缩SID向压缩SID的切换。
在本具体实例1中，Routing type＝4，说明SRH格式为第二分段路由头格式，即SRH中的路由类型字段兼容现有SRH。在压缩SID的End操作中，一个128位中的所有压缩SID(即采用uSID方式压缩的压缩SID)均处理完时，再将SL减1，如代码下：
Figure PCTCN2021086543-appb-000003
Figure PCTCN2021086543-appb-000004
A->Z业务报文传输方向的业务处理流程如图7所示，分段路由路径为A-B-D-F-M-Z，根据DA＝20:02:Z:11::执行End.DX4的功能。Z->A业务报文传输方向的业务处理流程如图8所示，分段路由路径为Z-M-F-D-B-A，根据DA＝20:02:A:11::执行End.DX4的功能。
实例2
实例2的组网拓扑如图9所示，现有一个L2VPN业务，需创建A-B-D-F-M-Z的SRv6路径，涉及压缩SID节点与非压缩SID节点的混合编程。A-G节点采用32位的压缩SID，而M、N、Z节点配置有128位的非压缩SID。在本实例中，SRH为第二分段路由头格式，即采用新定义的SRH_Ext字段，即Routing Type＝6，该SRH_Ext不涉及与现有SRH头的兼容处理。
SRH压缩过程中，进行如下定义：
(1)在SRH_Ext中定义Flag＝1表示当前为压缩SID，Flag＝0表示当前为非压缩SID。
(2)定义压缩SID与非压缩SID的临界节点的第一转换功能End.uzip(编码为0x77)，实现将SL指向的分段标识的类型由压缩SID转换为非压缩SID，代码如下：
Figure PCTCN2021086543-appb-000005
Figure PCTCN2021086543-appb-000006
(3)定义非压缩SID与压缩SID的临界节点的第二转换功能End.zip(编码为0x78)，实现将SL指向的分段标识的类型由非压缩SID转换为压缩SID，代码如下：
Figure PCTCN2021086543-appb-000007
图10为A->Z业务报文传输方向的SRH_Ext结构的示意图，在A节点，采用如图10所示的SRH_Ext表示A-B-D-F-M-Z的L2VPN业务转发路径，其中F节点采用F:77表示要执行End.uzip操作，实现压缩SID向非压缩SID的切换。
图11为Z->A业务报文传输方向的SRH_Ext结构的示意图，在Z节点，采用如图11所示的SRH_Ext表示Z-M-F-D-B-A的L2VPN业务转发路径，其中F节点采用F:78表示要执行End.zip操作，实现非压缩SID向压缩SID的切换。
由于本具体实例2采用新的Routing type(6)，不需要考虑兼容现有SRH处理。假设该SRH_Ext支持最小长度的压缩SID为16位， 由于这里压缩SID为32位，在压缩SID的End操作中将SL减2，而在非压缩SID的End操作中将SL减8。
A->Z业务报文传输方向的业务处理流程如图12所示，分段路由路径为A-B-D-F-M-Z，根据DA＝20:02:Z:15::执行End.DX2的功能。Z->A业务报文传输方向的业务处理流程如图13所示，分段路由路径为Z-M-F-D-B-A，根据DA＝20:02:A:15::执行End.DX2的功能。
实例3
实例3的组网拓扑如图9所示，现有一个L2VPN业务，需创建A-B-D-F-M-Z的SRv6路径，涉及压缩SID节点与非压缩SID节点的混合编程。A-G节点采用32位的压缩SID，而M、N、Z节点配置有128b位的非压缩SID。实例3与实例2的区别在于，本实例中SRH为第二分段路由头格式，即不额外增加扩展字段，而是兼容现有的SRH的处理，即Routing Type＝4。
SRH压缩过程中，进行如下定义：
(1)在SRH中定义Flag＝1表示当前为压缩SID，Flag＝0表示当前为非压缩SID，此时在非压缩SID的节点(例如M节点)看到的Flag为0，与现有SRH相同；
(2)定义压缩SID与非压缩SID的临界节点的第一转换功能End.uzip(编码为0x77)，实现将SL指向的分段标识的类型由压缩SID转换为非压缩SID，代码如下：
Figure PCTCN2021086543-appb-000008
(3)定义非压缩SID与压缩SID的临界节点的第二转换功能End.zip(编码为0x78)，实现将SL指向的分段标识的类型由非压缩SID转换为压缩SID，代码如下：
Figure PCTCN2021086543-appb-000009
图14为A->Z业务报文传输方向的SRH结构的示意图，在A节点，采用如图14所示的SRH表示A-B-D-F-M-Z的L2VPN业务转发路径，其中F节点采用F:77表示要执行End.uzip操作，实现压缩SID向非压缩SID的切换。
图15为Z->A业务报文传输方向的SRH结构的示意图，在Z节点，采用如图15所示的SRH表示Z-M-F-D-B-A的L2VPN业务转发路径，其中F节点为128位编码，并采用F:78表示要执行End.zip操作，实现非压缩SID向压缩SID的切换。
由于本具体实例3采用兼容现有的SRH方案，即Routing type＝4，兼容处理方法包括：SL仍然表示128位的SID数量，SRH中采用压缩SID时，将多个压缩SID组合起来占用128位的整数倍，多个压缩SID组合起来非128位的整数倍时，需填充保留字节，凑成128位的整数倍。例如，如图14所示，A->Z业务报文传输方向，分段列表中只有三个压缩SID，此时为凑成一个完整的128位，在后面要添加全0码。
在处理非压缩SID时，End操作中将SL减1。而处理压缩SID时，仅当一个128位中的全部压缩SID均处理，才将SL减1，其中， 通过设置Sub_SL记录128位内未处理压缩分段标识的数量，代码如下：
Figure PCTCN2021086543-appb-000010
需要说明的是，在处理压缩SID时，有可能SL已经为0，但Sub_SL并不为0，此时表示处理到分段列表的最后一个128位，但还有压缩SID未处理完，此时不应当做最后一跳处理。
A->Z业务报文传输方向的业务处理流程如图16所示，分段路由路径为A-B-D-F-M-Z，根据DA＝20:02:Z:15::执行End.DX2的功能。Z->A业务报文传输方向的业务处理流程如图17所示，分段路由路径为Z-M-F-D-B-A，根据DA＝20:02:A:15::执行End.DX2的功能。
本公开实施例提供一种在SRv6的SRH头中同时支持压缩SID格式和非压缩SID格式的SRH压缩方法，使得SRv6转发路径既可以包含采用压缩SID表示的节点，也可以包含采用非压缩SID表示的节点，扩展了SRv6的应用场景。通过定义新的标志字段来指示SRH中SL所指向的SID是压缩SID还是非压缩SID，并通过定义新的功能(function)来实现SRv6转发路径中压缩SID到非压缩SID、非压 缩SID到压缩SID的转换处理。
基于相同的技术构思，本公开实施例还提供一种分段路由头压缩装置，如图18所示，所述分段路由头压缩装置包括配置模块101、第一生成模块102和第二生成模块103，配置模块101配置为，为分段路由路径上各节点配置压缩分段标识或非压缩分段标识，并为所述分段路由路径中的临界节点配置额外具有将剩余分段数量(SL)指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点。
第一生成模块102配置为，生成分段列表，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识。
第二生成模块103配置为，生成业务报文的分段路由头，其中，所述业务报文的分段路由头包括所述分段列表和用于表示分段路由头格式的路由类型字段，所述分段路由头格式与所述压缩分段标识的格式相匹配。
在一些实施方式中，所述临界节点为已配置压缩分段标识、且下一跳节点为已配置非压缩分段标识的节点，所述将剩余分段数量(SL)指向的分段标识进行分段标识类型转换的功能为第一转换功能，所述第一转换功能为将SL指向的分段标识的类型转换为非压缩分段标识。
在一些实施方式中，所述临界节点为已配置压缩分段标识、且上一跳节点为已配置非压缩分段标识的节点，所述将剩余分段数量(SL)指向的分段标识进行分段标识类型转换的功能为第二转换功能，所述第二转换功能为将SL指向的分段标识的类型转换为压缩分段标识。
在一些实施方式中，所述业务报文的分段路由头还包括用于表示SL指向的分段标识类型的标志字段；所述第一转换功能包括将接收到的业务报文的分段路由头中的标志字段的值修改为表示非压缩分段标识的值；和/或，所述第二转换功能包括将接收到的业务报文 的分段路由头中的标志字段的值修改为表示压缩分段标识的值。
在一些实施方式中，所述业务报文的分段路由头还包括扩展字段，所述扩展字段用于表示第一分段路由头格式，并执行以下功能：在一个压缩分段标识处理完成之后，将SL的值减n，n为所述压缩分段标识长度与所支持的最短压缩分段标识长度的比值，n为正整数；以及，在一个非压缩分段标识处理完成后，将SL的值减m，m为非压缩分段标识长度与所支持的最短压缩分段标识长度的比值，m为正整数。
在一些实施方式中，所述路由类型字段用于表示第二分段路由头格式，所述第二分段路由头格式包括：p个压缩分段标识占用t个非压缩分段标识长度的比特位，t为正整数，p为对一个非压缩分段标识长度与一个压缩分段标识长度的比值进行取整得到的值，若p个压缩分段标识长度之和小于t个非压缩分段标识长度，则利用保留字节填充剩余长度；
所述路由类型字段用于执行以下功能：在一个非压缩分段标识长度内的全部压缩分段标识均处理完成之后，将SL减1。
在一些实施方式中，所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成包括：所述分段列表中当前处理的分段标识之后的比特位全部为零。
在一些实施方式中，所述业务报文的分段路由头中或所述分段列表中还包括用于记录未处理压缩分段标识数量的计数器字段；每处理完成一个压缩分段标识，将所述计数器字段的值减1，所述计数器字段的初始值为p；所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成包括：所述计数器字段的值为零。
基于相同的技术构思，本公开实施例还提供一种业务处理装置，应用于分段路由路径的节点，所述分段路由路径上各节点配置有压缩分段标识或非压缩分段标识,所述分段路由路径上的临界节点配置有额外具有将剩余分段数量(SL)指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识 的两相邻节点中已配置压缩分段标识的节点；如图19所示，所述业务处理装置包括获取模块201、处理模块202、转换模块203和转发模块204。获取模块201配置为，从接收到的业务报文的分段路由头中获取分段列表和用于表示分段路由头格式的路由类型字段，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识。
处理模块202配置为，处理所述分段列表中当前分段标识，并根据所述路由类型字段修改SL。
转换模块203配置为，若当前节点为临界节点，则将SL指向的分段标识进行分段标识类型转换。
转发模块204配置为，向下一跳节点转发所述业务报文，所述业务报文中携带SL指向的分段标识类型。
在一些实施方式中，所述临界节点为已配置压缩分段标识、且下一跳节点为已配置非压缩分段标识的节点；转换模块203配置为，将SL指向的分段标识的类型修改为非压缩分段标识。
在一些实施方式中，所述临界节点为已配置压缩分段标识、且上一跳节点为已配置非压缩分段标识的节点；转换模块203配置为，将SL指向的分段标识的类型修改为压缩分段标识。
在一些实施方式中，所述业务报文的分段路由头还包括用于表示SL指向的分段标识类型的标志字段。
获取模块201还配置为，在转换模块203将SL指向的分段标识进行分段标识类型转换之前，从所述业务报文的分段路由头中获取标志字段。
处理模块202配置为，将所述标志字段的值修改为表示非压缩分段标识的值；和/或，将所述标志字段的值修改为表示压缩分段标识的值。
在一些实施方式中，处理模块202配置为，当所述分段路由头为第一分段路由头格式时，在一个压缩分段标识处理完成之后，将SL的值减n，n为所述压缩分段标识长度与所支持的最短压缩分段标识长度的比值，n为正整数；以及，在一个非压缩分段标识处理完成后，将SL的值减m，m为非压缩分段标识长度与所支持的最短压缩分 段标识长度的比值，m为正整数。
在一些实施方式中，处理模块202配置为，当所述分段路由头为第二分段路由头格式时，在一个非压缩分段标识长度内的全部压缩分段标识均处理完成之后，将SL减1；其中，p个压缩分段标识占用t个非压缩分段标识长度的比特位，t为正整数，p为对一个非压缩分段标识长度与一个压缩分段标识长度的比值进行取整得到的值，若p个压缩分段标识长度之和小于t个非压缩分段标识长度，则利用保留字节填充剩余长度。
在一些实施方式中，所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成包括：所述分段列表中当前处理的分段标识之后的比特位全部为零。
在一些实施方式中，所述业务报文的分段路由头中或所述分段列表中还包括用于记录未处理压缩分段标识数量的计数器字段；每处理完成一个压缩分段标识，将所述计数器字段的值减1，所述计数器字段的初始值为p；所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成包括：所述计数器字段的值为零。
本公开实施例还提供了一种计算机设备，该计算机设备包括：一个或多个处理器以及存储装置；其中，存储装置上存储有一个或多个程序，当上述一个或多个程序被上述一个或多个处理器执行时，使得上述一个或多个处理器实现如前述实施例所提供的分段路由头压缩方法。
本公开实施例还提供了一种计算机可读介质，其上存储有计算机程序，其中，该计算机程序被执行时实现如前述实施例所提供的业务处理方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、装置中的全部或部分功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物 理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器(如中央处理器、数字信号处理器或微处理器)执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则与特定实施例相结合描述的特征、特性和/或元素可单独使用，或可与结合其他实施例描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本公开的范围的情况下，可进行各种形式和细节上的改变。

Claims (18)

  1. 一种分段路由头压缩方法，包括：
    为分段路由路径上各节点配置压缩分段标识或非压缩分段标识，并为所述分段路由路径中的临界节点配置额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点；
    生成分段列表，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；
    生成业务报文的分段路由头，其中，所述业务报文的分段路由头包括所述分段列表和用于表示分段路由头格式的路由类型字段，所述分段路由头格式与所述压缩分段标识的格式相匹配。
  2. 如权利要求1所述的方法，其中，所述临界节点为已配置压缩分段标识、且下一跳节点为已配置非压缩分段标识的节点，所述将剩余分段数量指向的分段标识进行分段标识类型转换的功能为第一转换功能，所述第一转换功能为将剩余分段数量指向的分段标识的类型转换为非压缩分段标识；和/或，
    所述临界节点为已配置压缩分段标识、且上一跳节点为已配置非压缩分段标识的节点，所述将剩余分段数量指向的分段标识进行分段标识类型转换的功能为第二转换功能，所述第二转换功能为将剩余分段数量指向的分段标识的类型转换为压缩分段标识。
  3. 如权利要求2所述的方法，其中，所述业务报文的分段路由头还包括用于表示剩余分段数量指向的分段标识类型的标志字段；
    所述第一转换功能包括将接收到的业务报文的分段路由头中的标志字段的值修改为表示非压缩分段标识的值；和/或，所述第二转换功能包括将接收到的业务报文的分段路由头中的标志字段的值修改为表示压缩分段标识的值。
  4. 如权利要求1至3中任一项所述的方法，其中，所述业务报文的分段路由头还包括扩展字段，所述扩展字段用于表示第一分段路由头格式，并执行以下功能：
    在一个压缩分段标识处理完成之后，将剩余分段数量的值减n，n为所述压缩分段标识长度与所支持的最短压缩分段标识长度的比值，n为正整数；以及，在一个非压缩分段标识处理完成后，将剩余分段数量的值减m，m为非压缩分段标识长度与所支持的最短压缩分段标识长度的比值，m为正整数。
  5. 如权利要求1至3中任一项所述的方法，其中，所述路由类型字段用于表示第二分段路由头格式，所述第二分段路由头格式包括：p个压缩分段标识占用t个非压缩分段标识长度的比特位，t为正整数，p为对一个非压缩分段标识长度与一个压缩分段标识长度的比值进行取整得到的值，若p个压缩分段标识长度之和小于t个非压缩分段标识长度，则利用保留字节填充剩余长度；
    所述路由类型字段用于执行以下功能：在一个非压缩分段标识长度内的全部压缩分段标识均处理完成之后，将SL减1。
  6. 如权利要求5所述的方法，其中，所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成包括：所述分段列表中当前处理的分段标识之后的比特位全部为零。
  7. 如权利要求5所述的方法，其中，所述业务报文的分段路由头中或所述分段列表中还包括用于记录未处理压缩分段标识数量的计数器字段；每处理完成一个压缩分段标识，将所述计数器字段的值减1，所述计数器字段的初始值为p；
    所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成包括：所述计数器字段的值为零。
  8. 一种业务处理方法，应用于分段路由路径的节点，所述分段路由路径上各节点配置有压缩分段标识或非压缩分段标识,所述分段路由路径上的临界节点配置有额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点，所述方法包括：
    从接收到的业务报文的分段路由头中获取分段列表和用于表示分段路由头格式的路由类型字段，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；
    处理所述分段列表中当前分段标识，并根据所述路由类型字段修改剩余分段数量；
    若当前节点为临界节点，则将剩余分段数量指向的分段标识进行分段标识类型转换；
    向下一跳节点转发所述业务报文，所述业务报文中携带剩余分段数量指向的分段标识类型。
  9. 如权利要求8所述的方法，其中，所述临界节点为已配置压缩分段标识、且下一跳节点为已配置非压缩分段标识的节点；所述将剩余分段数量指向的分段标识进行分段标识类型转换包括：将剩余分段数量指向的分段标识的类型修改为非压缩分段标识；和/或，
    所述临界节点为已配置压缩分段标识、且上一跳节点为已配置非压缩分段标识的节点；所述将剩余分段数量指向的分段标识进行分段标识类型转换包括：将剩余分段数量指向的分段标识的类型修改为压缩分段标识。
  10. 如权利要求9所述的方法，其中，所述业务报文的分段路由头还包括用于表示剩余分段数量指向的分段标识类型的标志字段；
    所述将剩余分段数量指向的分段标识进行分段标识类型转换之前，所述方法还包括：
    从所述业务报文的分段路由头中获取标志字段；
    所述将剩余分段数量指向的分段标识的类型修改为非压缩分段标识包括：将所述标志字段的值修改为表示非压缩分段标识的值；和/或，
    所述将剩余分段数量指向的分段标识的类型修改为压缩分段标识包括：将所述标志字段的值修改为表示压缩分段标识的值。
  11. 如权利要求8至10中任一项所述的方法，其中，所述根据所述路由类型字段修改剩余分段数量包括：
    若所述分段路由头为第一分段路由头格式，则在一个压缩分段标识处理完成之后，将剩余分段数量的值减n，n为所述压缩分段标识长度与所支持的最短压缩分段标识长度的比值，n为正整数；以及，
    在一个非压缩分段标识处理完成后，将剩余分段数量的值减m，m为非压缩分段标识长度与所支持的最短压缩分段标识长度的比值，m为正整数。
  12. 如权利要求8至10中任一项所述的方法，其中，所述根据所述路由类型字段修改剩余分段数量包括：
    若所述分段路由头为第二分段路由头格式，则在一个非压缩分段标识长度内的全部压缩分段标识均处理完成之后，将剩余分段数量减1；其中，p个压缩分段标识占用t个非压缩分段标识长度的比特位，t为正整数，p为对一个非压缩分段标识长度与一个压缩分段标识长度的比值进行取整得到的值，若p个压缩分段标识长度之和小于t个非压缩分段标识长度，则利用保留字节填充剩余长度。
  13. 如权利要求12所述的方法，其中，所述一个非压缩分段标识长度内的全部压缩分段标识均处理完成包括：所述分段列表中当前处理的分段标识之后的比特位全部为零。
  14. 如权利要求12所述的方法，其中，所述业务报文的分段路由头中或所述分段列表中还包括用于记录未处理压缩分段标识数量 的计数器字段；每处理完成一个压缩分段标识，将所述计数器字段的值减1，所述计数器字段的初始值为p；
    所述一个非压缩分段标识长度内全部压缩分段标识均处理完成包括：所述计数器字段的值为零。
  15. 一种分段路由头压缩装置，包括配置模块、第一生成模块和第二生成模块，
    所述配置模块配置为，为分段路由路径上各节点配置压缩分段标识或非压缩分段标识，并为所述分段路由路径中的临界节点配置额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点；
    所述第一生成模块配置为，生成分段列表，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；
    所述第二生成模块配置为，生成业务报文的分段路由头，其中，所述业务报文的分段路由头包括所述分段列表和用于表示分段路由头格式的路由类型字段，所述分段路由头格式与所述压缩分段标识的格式相匹配。
  16. 一种业务处理装置，应用于分段路由路径的节点，所述分段路由路径上各节点配置有压缩分段标识或非压缩分段标识,所述分段路由路径上的临界节点配置有额外具有将剩余分段数量指向的分段标识进行分段标识类型转换的功能的压缩分段标识，所述临界节点为已配置不同类型分段标识的两相邻节点中已配置压缩分段标识的节点；所述业务处理装置包括获取模块、处理模块、转换模块和转发模块，
    所述获取模块配置为，从接收到的业务报文的分段路由头中获取分段列表和用于表示分段路由头格式的路由类型字段，所述分段列表包括已配置的压缩分段标识和已配置的非压缩分段标识；
    所述处理模块配置为，处理所述分段列表中当前分段标识，并 根据所述路由类型字段修改剩余分段数量；
    所述转换模块配置为，若当前节点为临界节点，则将剩余分段数量指向的分段标识进行分段标识类型转换；
    所述转发模块配置为，向下一跳节点转发所述业务报文，所述业务报文中携带剩余分段数量指向的分段标识类型。
  17. 一种计算机设备，包括：
    一个或多个处理器；
    存储装置，其上存储有一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求1至7中任一项所述的分段路由头压缩方法或如权利要求8至14中任一项所述的业务处理方法。
  18. 一种计算机可读介质，其上存储有计算机程序，其中，所述程序被执行时实现如权利要求1至7中任一项所述的分段路由头压缩方法或如权利要求8至14中任一项所述的业务处理方法。
PCT/CN2021/086543 2020-04-13 2021-04-12 分段路由头压缩方法及装置、业务处理方法及装置 WO2021208843A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2022562524A JP2023523566A (ja) 2020-04-13 2021-04-12 セグメントルーティングヘッダ圧縮方法、サービス処理方法、セグメントルーティングヘッダ圧縮装置及びサービス処理装置
EP21788701.7A EP4138348A4 (en) 2020-04-13 2021-04-12 METHOD AND APPARATUS FOR COMPRESSION OF SEGMENT ROUTING HEADERS AND METHOD AND APPARATUS FOR SERVICE PROCESSING

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010285171.9 2020-04-13
CN202010285171.9A CN113542118B (zh) 2020-04-13 2020-04-13 分段路由头压缩方法、业务处理方法及装置

Publications (1)

Publication Number Publication Date
WO2021208843A1 true WO2021208843A1 (zh) 2021-10-21

Family

ID=78084029

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/086543 WO2021208843A1 (zh) 2020-04-13 2021-04-12 分段路由头压缩方法及装置、业务处理方法及装置

Country Status (4)

Country Link
EP (1) EP4138348A4 (zh)
JP (1) JP2023523566A (zh)
CN (1) CN113542118B (zh)
WO (1) WO2021208843A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023193471A1 (zh) * 2022-04-08 2023-10-12 中兴通讯股份有限公司 地址设置方法、装置、存储介质及电子装置
CN118075358A (zh) * 2024-04-17 2024-05-24 南通余弦数智科技有限公司 一种基于通用人工智能的通讯数据传输处理系统

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114285907B (zh) * 2021-12-03 2023-05-26 中国联合网络通信集团有限公司 数据传输方法、装置、电子设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105075194A (zh) * 2013-03-11 2015-11-18 思科技术公司 有索引的段id
US20190081897A1 (en) * 2017-09-12 2019-03-14 Google Llc Mechanism and apparatus for path protection when using compressed segment routing label stacks
US20190394211A1 (en) * 2018-06-26 2019-12-26 Cisco Technology, Inc. Providing Processing and Network Efficiencies in Protecting Internet Protocol Version 6 Segment Routing Packets and Functions Using Security Segment Identifiers
CN110855531A (zh) * 2019-12-02 2020-02-28 锐捷网络股份有限公司 一种转发路径检测方法及装置

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100689473B1 (ko) * 2000-08-29 2007-03-08 삼성전자주식회사 통신시스템에서 프로토콜 헤더 압축장치 및 방법
US9537769B2 (en) * 2013-03-15 2017-01-03 Cisco Technology, Inc. Opportunistic compression of routing segment identifier stacks
CN109218189B (zh) * 2017-07-03 2022-04-29 中兴通讯股份有限公司 跨域的路径的标识信息的确定方法、装置及存储介质
CN108429685B (zh) * 2018-04-28 2020-08-04 电子科技大学 一种基于分段路由技术的服务功能链寻路方法
CN110557329A (zh) * 2018-05-30 2019-12-10 中兴通讯股份有限公司 一种报文转发的方法、装置和节点

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105075194A (zh) * 2013-03-11 2015-11-18 思科技术公司 有索引的段id
US20190081897A1 (en) * 2017-09-12 2019-03-14 Google Llc Mechanism and apparatus for path protection when using compressed segment routing label stacks
US20190394211A1 (en) * 2018-06-26 2019-12-26 Cisco Technology, Inc. Providing Processing and Network Efficiencies in Protecting Internet Protocol Version 6 Segment Routing Packets and Functions Using Security Segment Identifiers
CN110855531A (zh) * 2019-12-02 2020-02-28 锐捷网络股份有限公司 一种转发路径检测方法及装置

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4138348A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023193471A1 (zh) * 2022-04-08 2023-10-12 中兴通讯股份有限公司 地址设置方法、装置、存储介质及电子装置
CN118075358A (zh) * 2024-04-17 2024-05-24 南通余弦数智科技有限公司 一种基于通用人工智能的通讯数据传输处理系统

Also Published As

Publication number Publication date
EP4138348A1 (en) 2023-02-22
JP2023523566A (ja) 2023-06-06
EP4138348A4 (en) 2024-05-01
CN113542118A (zh) 2021-10-22
CN113542118B (zh) 2024-01-23

Similar Documents

Publication Publication Date Title
CN109688057A (zh) 基于ipv6的段路由网络的报文转发方法及装置
WO2021208843A1 (zh) 分段路由头压缩方法及装置、业务处理方法及装置
US20070147363A1 (en) Network edge device configured for adding protocol service header identifying service encoding of IP packet payload
CN110401599B (zh) 数据包的处理方法及装置、存储介质、电子装置
CN112511428A (zh) 报文封装方法、报文转发方法、通告方法、电子设备、和存储介质
EP3742685B1 (en) Packet processing method and device
US8140709B2 (en) Two stage internet protocol header compression
CN112511988B (zh) 报文转发方法、设备、系统、网络设备和存储介质
WO2021213507A1 (zh) 数据包处理的方法及设备
CN105024985A (zh) 一种报文处理方法及装置
WO2022111606A1 (zh) 一种报文传输、段列表生成、压缩段标识获取方法及装置
WO2021088629A1 (zh) DetNet数据包处理方法及装置
WO2015172675A1 (zh) 报文处理方法及装置
CN116319617A (zh) 一种在sr网络中转发报文的方法、设备和系统
CN107370654B (zh) 一种伪线数据报文的封装、解封装方法和相关装置
WO2017041534A1 (zh) 一种电力线网络通信的方法及装置、计算机存储介质
US11251905B2 (en) Method for receiving code block stream, method for transmitting code block stream, and communications apparatus
CN112187641B (zh) 一种路由信息发送方法、报文发送方法及相关装置
CN115362661A (zh) 对用于分段路由的具有不同大小的分段进行混合
CN113497760B (zh) 分段路由头压缩方法、业务处理方法及装置
RU2795936C1 (ru) Способ и устройство для сжатия заголовка сегментной маршрутизации, способ и устройство для обработки услуги
EP4300913A1 (en) Multicast packet sending method and device
WO2023165244A1 (zh) 报文的发送方法、装置、存储介质及电子装置
CN116032839A (zh) 报文传输方法、装置、设备及存储介质
CN115865770A (zh) 一种SRv6混编压缩的方法、节点设备和网络系统

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022562524

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2021788701

Country of ref document: EP

Effective date: 20221114