RU2795936C1 - Method and device for segment routing header compression, method and device for service processing - Google Patents

Abstract

FIELD: communications.

SUBSTANCE: configuring (S11) a compressed segment identifier or an uncompressed segment identifier for each node in the segment routing path and configuring (S11), for a critical node, a compressed segment identifier, additionally performing a segment identifier type conversion for the segment identifier indicated by the field Segment Left; generating (S12) a segment list comprising configured compressed segment IDs and uncompressed segment IDs; and generating (S13) a segment routing header of the service packet, wherein the segment routing header of the service packet comprises a list of segments and a routing type field for specifying a segment routing header format, the segment routing header format corresponding to a compressed segment identifier format.

EFFECT: improving the compression of the segment routing header.

9 cl, 19 dwg

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] The present application claims priority under Chinese Patent Application No. 202010285171.9, filed April 13, 2020, the contents of which are incorporated herein by reference in their entirety.

FIELD OF TECHNOLOGY

[0002] Embodiments of the present invention relate to the field of wireless communication technology and, in particular, to a method and apparatus for compressing a segment routing header, a method and apparatus for processing a service, a computer device, and a computer-readable medium.

BACKGROUND OF THE INVENTION

[0003] Segment Routing (SR, Segment Routing) is a technology for implementing source routing. The RFC8402 protocol defines two standard SR mechanisms: SR-MPLS, based on the forwarding plane according to Multi-Protocol Label Switching (MPLS, Multi-Protocol Label Switching), and SRv6, based on the forwarding plane according to the Internet Protocol version 6 (IPv6, Internet Protocol version 6). The SRv6 protocol can be implemented directly based on the IPv6 extended routing header without additional encapsulation, resulting in unification of data forwarding and Internet Protocol (IP) data tunneling. Meanwhile, since SRv6 uses a segment ID (SID, Segment ID) in 128-bit format, and the SID is divided into two parts, namely, the location indicator (Locator) and the function (Function), flexible network and service hybrid programming can be achieved, due to which SRv6 technology is widely used in the industry.

[0004] However, in the SRv6 solution, a list of SIDs composed of a sequence of 128-bit SIDs is used to describe the service path, which leads to the problem of greatly increasing the packet header overhead. To address this problem, several solutions have been proposed in the art related to Segment Routing Header (SRH) compression, such as the uSID solution (draft-filsfils-spring-net-pgm-extension-srv6-usid-02) and traditional compressed SID solution (C-SID, Compressed SID) (draft-1i-spring-compressed-srv6-np-00).

[0005] According to the SRv6 solution, the forwarding node (Transit) only needs to process the normal IPv6 data forwarding, and the end node (Endpoint) needs to process the SRH header. However, in the specified SRH header compression decision, all end nodes are required to use the compressed SID format (whereas, according to the C-SID decision, the use of the uncompressed format is allowed at the end node of the last hop (hop), but not allowed at the intermediate node), that is, the end node involved in IPv6 packet forwarding, must be able to support compressed SID, which greatly increases the requirements for the SRH processing capabilities of network nodes and network SID scheduling, which limits the distribution and use of SRv6 to a certain extent.

SUMMARY OF THE INVENTION

[0006] According to a first aspect, embodiments of the present invention provide a method for compressing a segment routing header, including:

[0007] configuring a compressed segment identifier or an uncompressed segment identifier for each node in the segment routing path and configuring, for a critical node in the segment routing path, a compressed segment identifier further having the function of performing a segment identifier type conversion for the segment identifier indicated by the Segments Left field ( SL, remaining segments), wherein the critical node is a node configured using a compressed segment ID, of two adjacent nodes configured using different types of segment IDs;

[0008] generating a list of segments containing a configured compressed segment identifier and a configured uncompressed segment identifier;

[0009] generating a segment routing header of the service packet, wherein the segment routing header of the service packet contains a list of segments and a routing type field for specifying the format of the segment routing header, wherein the format of the segment routing header corresponds to the compressed segment identifier format.

[0010] According to a second aspect, embodiments of the present invention also provide a service processing method applicable to segment routing path nodes, wherein each segment routing path node is configured using a compressed segment identifier or an uncompressed segment identifier, a critical node in the segment routing path is configured using a compressed segment identifier, further having the function of performing an identifier type conversion for the segment identifier indicated by SL, and the critical node is a node configured using the compressed segment identifier, from two adjacent nodes configured using different types of segment identifiers, the method including:

[0011] obtaining a segment list and a routing type field for specifying a segment routing header format from a segment routing header of a received service packet, wherein the segment list contains a configured compressed segment identifier and a configured uncompressed segment identifier;

[0012] processing the current segment ID in the segment list and changing the SL according to the routing type field;

[0013] if the current node is a critical node, performing a type conversion of the segment identifier for the segment identifier indicated by the SL; And

[0014] forwarding the service packet to the next hop node, wherein the service packet carries the segment ID type indicated by the SL.

[0015] According to a third aspect, embodiments of the present invention also provide an apparatus for compressing a segment routing header, comprising a first generation module and a second generation module, wherein

[0016] the configuration module is configured to configure a compressed segment identifier or an uncompressed segment identifier for each node in the segment routing path and configure, for a critical node in the segment routing path, a compressed segment identifier, additionally having the function of performing segment identifier type conversion for the segment identifier, indicated by the Segments Left (SL) field, wherein the critical node is a node configured using a compressed segment identifier, of two adjacent nodes configured using different types of segment identifiers;

[0017] the first generation module is configured to generate a list of segments containing a configured compressed segment identifier and a configured uncompressed segment identifier;

[0018] The second generation module is configured to generate a segment routing header of the service packet, wherein the segment routing header of the service packet contains a list of segments and a routing type field to indicate the format of the segment routing header, and the format of the segment routing header corresponds to the compressed segment identifier format.

[0019] According to a fourth aspect, embodiments of the present invention also provide a service processing apparatus applicable to segment routing path nodes, wherein each segment routing path node is configured using a compressed segment identifier or an uncompressed segment identifier, a critical node in the segment routing path is configured with using a compressed segment ID further having a function of performing segment ID type conversion on the segment ID specified by the SL, and the critical node is a node configured using the compressed segment ID, of two adjacent nodes configured using different types of segment ID; and the service processing device comprises an acquisition module, a processing module, a conversion module, and a forwarding module, wherein

[0020] the acquisition module is configured to obtain a segment list and a routing type field to indicate the segment routing header format from the segment routing header of the received service packet, and the segment list contains a configured compressed segment identifier and a configured uncompressed segment identifier;

[0021] The processing module is configured to process the current segment ID in the segment list and change the SL according to the routing type field;

[0022] The conversion module is configured to convert the segment identifier type to the segment identifier indicated by the SL if the current node is a critical node; And

[0023] The forwarding module is configured to forward the service packet to the next hop node, wherein the service packet carries the segment identifier type indicated by the SL.

[0024] In accordance with a fifth aspect, embodiments of the present invention also provide a computing device comprising one or more processors and a storage device that stores one or more programs, the execution of which causes the one or more processors to execute a compression method. segment routing header or service processing method represented by the above-described embodiments of the invention.

[0025] According to a sixth aspect, embodiments of the present invention also provide a computer-readable medium storing a computer program executing the segment routing header compression method or service processing method of the above-described embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

[0026] FIG. 1 is a flowchart of a segment routing header compression method according to an embodiment of the present invention;

[0027] in FIG. 2 is a flowchart of a service processing method according to an embodiment of the present invention;

[0028] in FIG. 3 is a flowchart of changing SL according to a routing type field according to an embodiment of the present invention;

[0029] in FIG. 4 is a diagram of a network topology represented by Specific Embodiment 1 of the present invention;

[0030] in FIG. 5 is a block diagram of the SRH in the transmission direction A->Z of a service packet transmission of the Specific Embodiment 1 of the present invention;

[0031] in FIG. 6 is a block diagram of the SRH in the transmission direction Z->A of the service packet transmission of the Specific Embodiment 1 of the present invention;

[0032] in FIG. 7 is a flow chart of service processing in the A->Z transmission direction of a service packet in Embodiment 1 of the present invention;

[0033] in FIG. 8 is a flow chart of service processing in the Z->A direction of service packet transmission in Embodiment 1 of the present invention;

[0034] in FIG. 9 is a diagram of a network topology represented by Embodiment 2 of the present invention;

[0035] in FIG. 10 is a block diagram of SRH_Ext in the transmission direction A->Z of a service packet in Embodiment 2 of the present invention;

[0036] in FIG. 11 is a block diagram of SRH_Ext in the transmission direction Z->A of a service packet in Embodiment 2 of the present invention;

[0037] in FIG. 12 is a flow chart of service processing in the transmission direction A->Z of a service packet in Embodiment 2 of the present invention;

[0038] in FIG. 13 is a flow chart of service processing in the direction Z->A of service packet transmission in Embodiment 2 of the present invention;

[0039] in FIG. 14 is a block diagram of the SRH in the transmission direction A->Z of the service packet transmission of the Embodiment 3 of the present invention;

[0040] in FIG. 15 is a block diagram of the SRH in the transmission direction Z->A of a service packet according to Embodiment 3 of the present invention;

[0041] in FIG. 16 is a flow chart of service processing in the transmission direction A->Z of a service packet in Embodiment 3 of the present invention;

[0042] in FIG. 17 is a flow chart of service processing in the Z->A service packet transmission direction of Embodiment 3 of the present invention;

[0043] in FIG. 18 is a block diagram of an apparatus for compressing a segment routing header according to an embodiment of the present invention;

[0044] in FIG. 19 is a block diagram of a service processing apparatus according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

[0045] The following describes in more detail the embodiments of the present invention with reference to the accompanying drawings, however, these examples can be implemented in various forms, and implementation should not be limited to the options given in this description. Rather, the purpose of presenting these embodiments of the invention is to more thoroughly and completely describe the present invention and to enable those skilled in the art to understand the invention.

[0046] In this description, the combination "and/or" is used to refer to any combination or all combinations of one or more related enumerated elements.

[0047] The terminology used is only used to describe specific embodiments of the invention and is not intended to limit the invention. In this document, singular forms also include plural forms, unless the context clearly dictates otherwise. In addition, it should be understood that the terms "comprises" and/or "consisting of", as used in this description, indicate the presence of specific features, collection, steps, operations, elements and/or components, but do not exclude the presence or addition of one or more than other signs, aggregates, steps, operations, elements, components and / or groups of components.

[0048] The described embodiments of the invention may be given with reference to top views and/or cross sections based on the ideal diagrams of the present invention. Accordingly, the typical illustrations may be modified according to manufacturing techniques and/or tolerances. Thus, embodiments of the present invention are not limited to those shown in the drawings, but include modifications based on configurations obtained during the manufacturing process.

[0049] Unless otherwise indicated, all terms (including technical and scientific terms) used in this description have the meaning generally accepted in the art. In addition, it should be appreciated that terms defined in general dictionaries should be construed as having meanings consistent with their meanings in the context of the relevant art and the present specification, and these terms should not be considered as having idealized or overly formal meanings unless not explicitly stated otherwise.

[0050] According to an embodiment of the present invention, a method for compressing a segment routing header is provided. As shown in FIG. 1, the segment routing header compression method includes steps S11-S13 described below.

[0051] S11: configuring a compressed segment identifier or an uncompressed segment identifier for each node in the segment routing path and configuring, for a critical node in the segment routing path, a compressed segment identifier further having the function of performing segment identifier type conversion for the segment identifier indicated by the Segments field Left (SL).

[0052] A critical node is a node configured using a compressed segment identifier, from two adjacent nodes configured using different types of segment identifiers. According to an embodiment of the present invention, the type of segment identifiers includes compressed segment identifiers and uncompressed segment identifiers. For example, a segment routing path is configured as Node A-Node B-Node C, where a compressed segment ID is configured for Node A and Node B, and an uncompressed segment ID is configured for Node C. The segment ID types of Node B and Node C are different, and the Node B is configured using the compressed segment identifier. Therefore, Node B is a critical node in the segment routing path.

[0053] In this step, the segment routing header compression device configures either a compressed segment identifier or an uncompressed segment identifier for each node in the segment routing path, and also configures, for the critical node of this path, a compressed segment identifier, further having the function of performing segment identifier type conversion for the segment IDs indicated by the Segments Left field, i.e. SL. That is, there are two types of compressed shard IDs: one type represents compressed shard IDs that are configured for non-critical nodes and can be implemented using existing compressed shard IDs; the other type represents a compressed shard ID that is configured for a critical node and has the function of performing a shard ID type conversion on the shard IDs specified by the SL, for example, such an ID can be implemented by a function field specifying the shard ID.

[0054] After the segment routing header compressor configures the compressed segment identifiers and uncompressed segment identifiers for the respective nodes, each node can distribute the compressed segment identifiers and uncompressed segment identifiers to the entire SR domain through the Interior Gateway Protocol (IGP) .

[0055] S12: generating a list of segments containing a configured compressed segment identifier and a configured uncompressed segment identifier.

[0056] In this step, the segment routing path source node calculates and generates a segment list, and the segment list is compressed into compressed segment identifiers or uncompressed segment identifiers of the respective nodes according to the network programming requirements. In the segment list, the segment identifiers of the nodes in the segment routing path are listed in the order in which service packets are forwarded.

[0057] S13: Generation of a segment routing header of the service packet, wherein the segment routing header of the service packet contains a list of segments and a routing type field to indicate the format of the segment routing header, the format of the segment routing header corresponds to the compressed segment identifier format.

[0058] In this step, the list of segments is carried in the segment routing header (SRH) of the service packet. The segment routing header of the service packet also contains a routing type field. The routing type field is used to specify the format of the segment routing header. The format of the segment routing header corresponds to the format of the compressed segment identifier, and the ways of changing the SL determined by the different formats of the segment routing header are different. The following describes in more detail the ways in which the SL can be modified by various segment routing header formats.

[0059] According to the segment routing header compression method presented by the embodiments of the present invention, each node in the segment routing path is configured using a compressed segment identifier or an uncompressed segment identifier, and a compressed segment identifier is further configured for the critical node having a function of performing identifier type conversion a segment for segment IDs specified by the SL set, wherein the critical node is a node configured using a compressed segment ID, of two adjacent nodes configured using different types of segment IDs; generating a list of segments containing configured compressed segment identifiers and uncompressed segment identifiers; generating a segment routing header of the service packet, wherein the segment routing header of the service packet contains a list of segments and a routing type field for specifying the format of the segment routing header, wherein the format of the segment routing header corresponds to the compressed segment identifier format. According to an embodiment of the present invention, by performing segment ID type conversion and determining the segment routing header format corresponding to the compressed segment ID format, hybrid networking and hybrid programming of nodes configured using compressed segment IDs and nodes configured using uncompressed segment IDs can be achieved. , making SRv6 routing applicable to more complex networking environments, facilitating rapid deployment of SRv6 capabilities in an existing network.

[0060] According to some embodiments of the invention, a critical node is a node configured using a compressed segment identifier, and a next hop node is a node configured using an uncompressed segment identifier. For example, the segment routing path is formed as follows: node A-node B-node C, the transmission path of the service packet is the path A-B-C, while node A and node B are configured using compressed segment identifiers, node C is configured using uncompressed segment ID, and node B is the critical node. Accordingly, the function for performing segment ID type conversion for the segment ID specified by SL is the first conversion function for converting the type of segment ID specified by SL to uncompressed segment IDs.

[0061] According to some embodiments of the invention, a critical node is a node configured using a compressed segment identifier, and a prior hop node is a node already configured using an uncompressed segment identifier. For example, the segment routing path is formed as follows: Node A - Node B - Node C, the service packet transmission path is C-B-A, Node A and Node B are configured using compressed segment identifiers, Node C is configured using uncompressed segment ID, and node B is the critical node. Accordingly, the function for performing segment ID type conversion on the segment ID indicated by SL is the second conversion function for converting the type of segment ID indicated by SL to compressed segment IDs.

[0062] According to some embodiments of the invention, the segment routing header of the service packet may also contain a flag field (Flag) to indicate the type of segment identifier indicated by the SL. For example, if the value of the flag field is 1, this indicates that the segment ID indicated by the current SL is a compressed segment ID; if the value of the flag field is 0, this indicates that the segment ID indicated by the current SL is an uncompressed segment ID.

[0063] The first transform function includes changing the value of the flag field in the segment routing header of the received service packet to a value representing the uncompressed segment flag (ie, Flag=0). That is, the first conversion function is defined as the End.uzip function, which is used to implement processing for converting a compressed segment ID to an uncompressed segment ID, the processing being: changing a flag to change SL to indicate an uncompressed segment ID. It should be noted that End.uzip processing may also include an End operation of a compressed segment ID, with different compressed segment IDs corresponding to different schemes of the End operation, i.e., an embodiment of the present invention integrates compression schemes for different segment IDs.

[0064] The second transformation function includes changing the value of the flag field in the segment routing header of the received service packet to a value indicating a compressed segment identifier (ie, Flag=1). That is, the second conversion function is defined as the End.zip function, which is used to implement processing for converting an uncompressed segment ID to a compressed segment ID, the processing being: changing a flag to change SL to indicate a compressed segment ID. It should be noted that End.zip processing may also include an End operation of a compressed segment ID, where different compressed segment IDs have different End operation schemes, that is, an embodiment of the present invention integrates compression schemes for different segment IDs.

[0065] According to some embodiments of the invention, the value of the routing type field is the first predefined value, for example, Routing type = 6. Accordingly, the segment routing header of the service packet also contains an extension field (SRH_Ext), which is used to indicate the first format of the segment routing header, when this performs the following function: after the processing of the compressed segment identifier, decrease the value of SL by n, where n is the ratio of the length of the compressed segment identifier to the length of the shortest compressed segment identifier supported, with n being a positive integer; and upon completion of processing the uncompressed segment identifier, decrementing the value of SL by m, where m is the ratio of the length of the uncompressed segment identifier to the length of the shortest compressed segment identifier supported, with m being a positive integer.

[0066] That is, a new field defined as SRHExt can be used in the segment routing header of the service packet. The SRHExt field can support hybrid programming of compressed segment IDs and uncompressed segment IDs, even programming of compressed segment IDs with different lengths. In this case, the SL operation is redefined according to the shortest length of the compressed segment identifiers. For example, if the shortest compressed segment identifier supported is 16 bits long, then the SRH_Ext field defines the following functions:

[0067] after the processing of the 16-bit compressed segment identifier is completed, decrease SL by 1 in the End operation;

[0068] upon completion of processing the 32-bit compressed segment ID, decrease SL by 2 in the End operation;

[0069] upon completion of processing the 64-bit compressed segment identifier, decrease SL by 4 in the End operation; And

[0070] upon completion of the processing of the uncompressed segment identifier (uncompressed segment identifier 128 bits long), decrease SL by 8 in the End operation.

[0071] According to some embodiments of the invention, the value of the routing type field is the second predefined value, for example, Routing type = 4. In this case, the segment routing header continues to use the current routing type field, however, it is required to redefine the function of the routing type field to ensure compatibility with both compressed and uncompressed segment identifiers. More specifically, the routing type field is used to indicate a second segment routing header format that contains p compressed segment identifiers occupying bits of length t of the uncompressed segment identifiers, where t is a positive integer, p is a value obtained by rounding the ratio of the length of the uncompressed segment identifier to the length of the compressed segment identifier. If the total length p of the compressed segment IDs is less than the total length t of the uncompressed segment IDs, use the reserved bytes to fill the remaining length. Accordingly, the routing type field is used to perform the following function: decrement SL by 1 upon completion of processing all compressed segment identifiers within the length of the uncompressed segment identifier. It should be noted that the routing type field may also perform the following function according to the existing definition: decrease the value of SL by 1 after processing the uncompressed segment identifier.

[0072] That is, if Routing type = 4, then SL still indicates the number of segment IDs within the length of one uncompressed segment ID (128 bits). If compressed segment identifiers are used in the segment routing header of the service packet, it is required to concatenate the plurality of compressed segment identifiers to occupy 128 bits. If an integer multiple of 128 bits (the integer is t and t is greater than or equal to 1) cannot be occupied, the reserved fields are filled to form an integer multiple of 128 bits. The compressed segment IDs are then processed, and only after all compressed segment IDs within 128 bits have been processed, SL is decremented by 1. After processing of the uncompressed segment ID is completed, SL is decremented by 1 in the End operation.

[0073] When processing compressed segment identifiers, it is necessary to determine whether to change the value of SL after evaluating that the processing of all compressed segment identifiers within 128 bits is completed.

[0074] In some embodiments of the invention, for example, the compressed segment identifier is compressed using the uSID (draft-fils-spring-net-pgm-extension-srv6-usid-02) method. Accordingly, the completion of processing all compressed segment IDs within the length of one uncompressed segment ID means that the bits after the currently processed segment ID in the segment list are zero.

[0075] In some embodiments of the invention, for example, the compressed segment identifier is compressed using the C-SID (draft-fils-spring-net-pgm-extension-srv6-usid-02) method. Accordingly, the service packet routing segment header or segment list may also be configured using a counter field (Sub_SL) to record the number of unprocessed compressed segment identifiers; whenever processing of the compressed segment ID is completed, the value of the counter field is decremented by 1, with the initial value of the counter field equal to p (where p is a value obtained by rounding off the ratio of the length of the uncompressed segment ID to the length of the compressed segment ID). Accordingly, the completion of processing all compressed segment identifiers within the length of one uncompressed segment identifier also means that the value of the counter field is zero.

[0076] According to an embodiment of the present invention, a service processing method is also provided. The method is applicable to segment routing path nodes, wherein each segment routing path node is configured using a compressed segment identifier or an uncompressed segment identifier, a critical node in the segment routing path is further configured using a compressed segment identifier having the function of performing segment identifier type conversion for the segment identifier, of the specified SL, and the critical node is a node configured using a compressed shard ID of two adjacent nodes configured using different types of shard IDs. As shown in FIG. 2, the service processing method includes the following steps:

[0077] S21: Obtaining a segment list and a routing type field to indicate the segment routing header format from the segment routing header of the received service packet, wherein the segment list contains configured compressed segment identifiers and configured uncompressed segment identifiers.

[0078] Before forwarding the service packet, the segment routing header compressor generates a segment list containing compressed segment IDs and uncompressed segment IDs, and carries the segment list in the segment routing header of the service packet. In this step, after receiving the service packet sent by the prior hop node, the node in the segment routing path obtains the list of segments from the segment routing header of the service packet, and also obtains a routing type field representing the format of the segment routing header.

[0079] S22: processing the current segment ID in the segment list and changing the SL according to the routing type field.

[0080] In this step, the service processing device processes the current segment ID in the segment list, where the segment ID is a compressed segment ID or an uncompressed segment ID. The way to change the SL determined by the different routing types after the segment ID processing is completed is different, so you need to determine the routing type and change the SL according to the routing type. Methods for changing the SL depending on various types of routing are described in more detail below with reference to FIG. 3.

[0081] S23: If the current node is a critical node, perform a type conversion of the segment ID for the segment ID specified by the SL.

[0082] The segment identifier type includes a compressed segment identifier and an uncompressed segment identifier. The segment ID type conversion includes converting a compressed segment ID to an uncompressed segment ID, or converting an uncompressed segment ID to a compressed segment ID.

[0083] It should be noted that if the node is not critical, the function specified by the segment ID (which may be a compressed segment ID or an uncompressed segment ID) configured in that node is executed without performing a segment ID type conversion for the segment ID specified by the SL.

[0084] S24: Forwarding the service packet to the next hop node, wherein the service packet carries the segment identifier type indicated by the SL.

[0085] In this step, the service processing device carries the converted segment ID type obtained in step S23 in the service packet, and forwards the service packet to the next hop.

[0086] According to the service processing method presented by embodiments of the present invention, a segment list and a routing type field for specifying a segment routing header format are extracted from a segment routing header of a received service packet, the segment list contains configured compressed segment IDs and configured uncompressed segment IDs; processing the current segment ID in the segment list and changing the SL according to the routing type field; if the current node is a critical node, performing a type conversion of the segment ID to the segment ID indicated by the SL; the service packet is forwarded to the next hop node, the service packet carrying the segment identifier type indicated by the SL. According to an embodiment of the present invention, by performing a type conversion of the segment ID specified by SL at the critical node and changing the SL according to the routing type field, hybrid networking and hybrid programming of nodes configured using compressed segment IDs and nodes configured with using uncompressed segment identifiers, making SRv6 routing applicable to more complex networking environments, facilitating rapid deployment of SRv6 facilities in an existing network.

[0087] According to some embodiments of the invention, a critical node is a node configured using a compressed segment identifier, and a next hop node is a node configured using an uncompressed segment identifier. Accordingly, performing a type conversion of the segment ID on the segment ID indicated by SL (ie, S23) includes changing the type of the segment ID indicated by SL to an uncompressed segment ID. That is, in the burst direction, the upstream node to the critical node is the node configured using the compressed segment ID, and the next hop node to the critical node is the node configured using the uncompressed segment ID.

[0088] According to some embodiments of the invention, a critical node is a node configured using a compressed segment identifier, and a prior hop node is a node configured using an uncompressed segment identifier. Accordingly, performing a type conversion of the segment ID on the segment ID indicated by SL (ie, step S23) includes changing the type of the segment ID indicated by SL to a compressed segment ID. That is, in the burst direction, the upstream node to the critical node is the node configured using the uncompressed segment ID, and the next hop node to the critical node is the node configured using the compressed segment ID.

[0089] According to some embodiments of the invention, a segment identifier type conversion function for a segment identifier indicated by SL may be implemented by setting the Flag field. More specifically, the segment routing header of the service packet also contains a Flag field to indicate the segment identifier type indicated by the SL, and the segment identifier type includes a compressed segment identifier and an uncompressed segment identifier. For example, Flag = 0 could be defined to indicate an uncompressed segment identifier, and Flag = 1 to indicate a compressed segment identifier.

[0090] Accordingly, in step S23, before performing segment ID type conversion for the segment ID indicated by SL, the method also includes obtaining a Flag field from the segment routing header of the service packet.

[0091] Accordingly, if the critical node is a node configured using a compressed segment identifier and the next hop node is a node configured using an uncompressed segment identifier, changing the type of segment identifiers indicated by UL to an uncompressed segment identifier includes changing the value of the Flag field to a value that points to the uncompressed segment ID, such as changing the value of the Flag field to 0.

[0092] Accordingly, if the critical node is a node configurable using a compressed segment identifier and the prior hop node is a node configured using an uncompressed segment identifier, changing the type of segment identifiers indicated by SL to an uncompressed segment identifier includes changing the value of the Flag field to a value that points to the compressed segment ID, such as changing the value of the Flag field to 1.

[0093] In the process of forwarding the service packet, upon completion of processing the segment identifier, it is required to change the SL. According to an embodiment of the present invention, the segment routing header format is defined in the routing type field, and ways of changing the SL depending on various segment routing headers are defined. Methods for changing the SL depending on various segment routing formats are described in more detail below with reference to FIG. 3.

[0094] According to some embodiments of the invention, as shown in FIG. 3, changing the SL according to the routing type field (that is, step S23) includes:

[0095] S231: determining the segment routing header format according to the routing type field, and performing step S232 if the segment routing header format is the first segment routing header format; performing step S233 if the segment routing header format is the second segment routing header format.

[0096] According to some embodiments of the present invention, the segment routing header format may be determined in accordance with the value of the routing type field. If the value of the routing type field is the first predetermined value, it is determined that the segment routing header format is the first segment routing header format; if the value of the routing type field is the second predetermined value, it is determined that the segment routing header format is the second segment routing header format. For example, the first preset value may be 6, and the second preset value may be 4. If the value of the routing type field is the first preset value, this indicates that the segment routing header of the service packet also contains an extension field (SRH_Ext) , and SL is changed in the manner specified by the SRH_Ext field. If the value of the routing type field is the second preset value, this indicates that the SL is still changed in the manner determined by the routing type field (it should be noted that the method of changing the SL determined by the routing type field according to the present invention is different from the method modification of the SL adopted in the prior art).

[0097] S232: after processing of the compressed segment identifier, decrease the value of SL by n, where n is the ratio of the length of the compressed segment identifier to the length of the shortest compressed segment identifier supported, with n being a positive integer; and upon completion of processing the uncompressed segment identifier, decrementing the value of SL by m, where m is the ratio of the length of the uncompressed segment identifier to the length of the shortest compressed segment identifier supported, with m being a positive integer.

[0098] In this step, if Routing type = 6, the SL processing is redefined according to the shortest length of the compressed segment identifier. For example, if the supported shortest compressed segment ID is 16 bits long, then SL is decremented by 1 (n=16/16=1) in an End operation after processing of the 16-bit compressed segment ID is completed; SL is reduced by 2 (n=32/16=2) when executing the End operation after processing of the 32-bit compressed segment identifier is completed; SL is reduced by 4 (n=64/16=4) when executing the End operation after the processing of the 64-bit compressed segment identifier is completed; and SL is decremented by 8 (m=128/16=8) when executing the End operation after processing of the 128-bit uncompressed segment ID is completed.

[0099] It should be noted that in order to ensure correct validation, respectively, in the Last Entry field of the segment routing header, it is determined that when performing the check, the SL field should also be calculated according to the set of supported shortest compressed segment lengths (for example, 16 bits).

[00100] In step S233, decrement SL by 1 after processing of all compressed segment IDs within the length of one uncompressed segment ID is completed.

[00101] In the second segment routing header format, p compressed segment identifiers occupy bits of length t of uncompressed segment identifiers, where t is a positive integer, p is a value obtained by rounding the ratio of the length of the uncompressed segment identifier to the length of the compressed segment identifier. If the total length p of the compressed segment IDs is less than the total length t of the uncompressed segment IDs, use the reserved bytes to fill the remaining length. That is, if Routing type = 4, then SL still specifies the number of segment IDs within the length of one uncompressed segment ID (128 bits). If compressed segment identifiers are used in the segment routing header of the service packet, it is necessary to concatenate a plurality of segment identifiers to occupy 128 bits. If an integer multiple of 128 bits (where the integer is t and t is greater than or equal to 1) cannot be occupied, the reserved fields are filled to form an integer multiple of 128 bits. Accordingly, after processing of compressed segment IDs is completed, SL is reduced by 1 if processing of all compressed segment IDs within 128 bits is completed.

[00102] It should be appreciated that in this step, the SL value is decremented by 1 after the processing of the uncompressed segment identifier is completed.

[00103] According to an embodiment of the present invention, when processing compressed segment identifiers, it is necessary to determine whether the value of SL should be changed after evaluating that the processing of all compressed segment identifiers within 128 bits has been completed.

[00104] In accordance with some embodiments of the invention, for example, for compressed segment identifiers compressed by the uSID method, determining that all compressed segment identifiers within 128 bits have been processed may be performed by evaluating the remaining bits. Accordingly, the completion of processing all compressed segment IDs within the length of one uncompressed segment ID means that the bits after the currently processed segment ID in the segment list are zero.

[00105] In accordance with some embodiments of the invention, for example, for compressed segment identifiers compressed by the C-SID method, determining that all compressed segment identifiers within 128 bits have been processed may be performed by using a counter. More specifically, in a service packet routing segment header or segment list, a counter field (Sub_SL) is provided to record the number of unprocessed compressed segment identifiers; whenever the processing of the compressed segment identifier is completed, the value of the Sub_SL field is decremented by 1, with the initial value of Sub_SL equal to p. Accordingly, the completion of processing all compressed segment identifiers within the length of one uncompressed segment identifier also means that the value of the counter field is zero.

[00106] It should be noted that the Sub_SL value and the SL value are not necessarily zero at the same time. When processing a compressed segment identifier, it is possible that the value of SL is already zero, but the value of Sub_SL is not yet zero. In this case, this means that the last 128 bits in the segment list have been reached during processing, but there are still unprocessed compressed segment identifiers that should not be processed as a last hop.

[00107] Below, to explain the solutions corresponding to the embodiments of the present invention, a more detailed description of these options is given using three specific examples.

[00108] Embodiment 1

[00109] A network topology according to Embodiment 1 of the invention is shown in FIG. 4. There is currently a VPN4 service. You want to create an A-B-D-F-M-Z SRv6 path that uses hybrid programming of nodes with compressed SIDs and uncompressed SIDs. Nodes A-G are configured using 32-bit compressed segment IDs that are compressed using the uSid compression scheme, the common prefix (uSID Block) of the compressed SIDs is 32 bits, and the length of each compressed segment ID is 32 bits. Thus, after removing the uSID Block of 128 bits, the compressed SIDs of three SRv6 nodes can be represented. Nodes M, N, and Z are configured using 128-bit uncompressed SIDs.

[00110] In the SRH compression process, the following determinations are made:

[00111] (1) Set the Flag = 1 field in the SRH to indicate that the SID is currently a compressed SID, and set the Flag = 0 field in the SRH to indicate that the SID is currently an uncompressed SID .

[00112] (2) The first conversion function End.uzip (encoded as 0x77) of the critical node between the compressed SID and the uncompressed SID is defined to perform the conversion of the segment identifier type indicated by the SL from the compressed SID to the uncompressed SID. The code looks like this:

[00113] If(SRH.Flag == 1)

[00114] Set SRH.Flag = 0

[00115] Decrease SL by 1

[00116] Update IPv6 DA using Segment_List[SL]

[00117] Forward packet over new DA;

[00118] (3) A second conversion function End.uzip (encoded as 0x78) of the critical node between the uncompressed SID and the compressed SID is defined to perform the conversion of the segment identifier type indicated by the SL from the uncompressed SID to the compressed SID. The code looks like this:

[00119] If(SRH.Flag == 0)

[00120] Set SRH.Flag = 1

[00121] Decrease SL by 1

[00122] Update IPv6 DA using Segment_List[SL]

[00123] Forward packet over new IPv6 DA;

[00124] FIG. 5 shows a block diagram of the SRH in the transmission direction A->Z of a service packet. Node A uses the SRH shown in FIG. 5 to represent the VPN4 service transmission path A-B-D-F-M-Z, where F:77 is used at the node F to indicate that an End.uzip operation is to be performed to convert the compressed SID to the uncompressed SID.

[00125] FIG. 6 is a block diagram of the SRH in the transmission direction Z->A of the service packet. Node Z uses the SRH shown in FIG. 6 to represent the Z-M-F-D-B-A transmission path of the VPN4 service, where node F is configured using a 128-bit uncompressed SID, and F:78 is used at this node to indicate that an End.uzip operation should be performed to convert the uncompressed SID to a compressed SID .

[00126] In this particular embodiment 1, Routing type = 4 indicates that the SRH format is the second segment routing header format, i.e. the routing type field in the SRH is compatible with the existing SRH. During the End operation of the compressed SID, the value of SL is reduced by 1 if processing of all 128-bit compressed SIDs (that is, SIDs compressed with the uSID method) is completed. The code looks like this:

[00127] IF (SRH.Flag == 1)

[00128] IF DA[64..95] !=0 //Still unprocessed uSIDs

[00129] Copy DA[64..127] to DAL32..95]

[00130] Set DA[96..127] to 0x0000

[00131] Forward packet over new IPv6 DA;

[00132] ELSE IF (DA[64..95]=0) and SL>0 //processing of all uSIDs in the current 128 bits is complete, and the compressed SIDs in the next 128 bits are taken for processing

[00133] Decrease SL by 1

[00134] Update IPv6 DAc using Segment_List[SL]

[00135] Forward packet over new IPv6 DA;

[00136] ELSE

[00137] Error message //if the next 128 bits are missing, service processing other than the End operation should be performed with an error message.

[00138] The service processing flow in the A->Z transmission direction of the service packet is shown in FIG. 7. The segment routing path is A-B-D-F-M-Z and the End.DX4 function is executed according to DA=20:02:Z:11::. The service processing flow in the Z->A direction of transmitting a service packet is shown in FIG. 8. The segment routing path is Z-M-F-D-B-A and the End.DX4 function is executed according to DA=20:02:A:11::.

[00139] Embodiment 2

[00140] A network topology according to Embodiment 2 of the invention is shown in FIG. 9. There is currently an L2VPN service. You want to create an A-B-D-F-M-Z SRv6 path that uses hybrid programming of nodes with compressed SIDs and uncompressed SIDs. Nodes A-G use 32-bit compressed SIDs, and nodes M, N, Z are configured with 128-bit uncompressed SIDs. According to this embodiment, SRH is the second segment routing header format, i.e. a new defined SRH_Ext field is used, i.e. Routing Type = 6, and SRH_Ext does not involve prior art SRH header compatibility processing.

[00141] In the SRH compression process, the following determinations are made:

[00142] (1) Set the Flag = 1 field in SRH_Ext to indicate that the SID is currently a compressed SID, and set the Flag = 0 field to indicate that the SID is currently an uncompressed SID.

[00143] (2) The first conversion function End.uzip (encoded as 0x77) of the critical node between the compressed SID and the uncompressed SID is defined to perform the conversion of the segment identifier type indicated by the SL from the compressed SID to the uncompressed SID. The code looks like this:

[00144] IF (SRH.Flag == 1)

[00145] Set SRH.Flag = 0

[00146] IF(SL>=10)

[00147] Decrease SL by 2 //Assuming that the shortest 16-bit compressed SID is supported, since in this case the compressed SID is 32 bits, SL should be reduced by 2

[00148] Update IPv6 DA using Segment_List[SL] //get next uncompressed SID

[00149] Forward packet over IPv6 DA;

[00150]ELSE

[00151] Error message //next hop is not an uncompressed SID, and an error message is output;

[00152] (3) A second conversion function End.uzip (encoded as 0x78) of the critical node between the uncompressed SID and the compressed SID is defined to perform a conversion of the segment identifier type indicated by the SL from the uncompressed SID to the compressed SID. The code looks like this:

[00153] If(SRH.Flag == 0)

[00154] Set SRH.Flag = 1

[00155] IF SL>10

[00156] Decrease SL by 8

[00157] Update IPv6 DA using Segment_List[SL] //get next compressed SID

[00158] Forward packet over new IPv6 DA;

[00159] FIG. 10 shows a block diagram of SRH_Ext in the transmission direction A->Z of a service packet. Node A uses the SRH_Ext field shown in FIG. 10 to represent the A-B-D-F-M-Z transmission path of the L2VPN service, where the node uses F:77 to indicate that an End.uzip operation is to be performed to convert the compressed SID to the uncompressed SID.

[00160] FIG. 11 shows a block diagram of SRH_Ext in the transmission direction Z->A of a service packet. Node Z uses the SRH_Ext field shown in FIG. 11 to represent the Z-M-F-D-B-A transmission path of the L2VPN service, where F:78 is used at the node F to indicate that an End.uzip operation is to be performed to convert the uncompressed SID to a compressed SID.

[00161] Since this particular Embodiment 2 uses a new Routing type (6), compatibility with the existing SRH processing method need not be taken into account. Assuming that SRH_Ext supports a compressed SID with a minimum length of 16 bits, since in this case the compressed SID occupies 32 bits, SL is decreased by 2 when an End operation is performed on a compressed SID, and SL is decreased by 8 when an End operation is performed on an uncompressed SID.

[00162] FIG. 12 shows the service processing flow in the direction A->Z of the transmission of the service packet. The segment routing path is A-B-D-F-M-Z and the End.DX2 function is executed according to DA=20:02:Z:15::. The service processing flow in the Z->A direction of transmitting a service packet is shown in FIG. 13. The segment routing path is Z-M-F-D-B-A, and the End.DX2 function is executed according to DA=20:02:A:15::.

[00163] Embodiment 3

[00164] The network topology according to Embodiment 3 of the invention is shown in FIG. 9. There is currently an L2VPN service. You want to create an A-B-D-F-M-Z SRv6 path that uses hybrid programming of nodes with compressed SIDs and uncompressed SIDs. Nodes A-G use 32-bit compressed SIDs, and nodes M, N, Z are configured with 128-bit uncompressed SIDs. The difference between Embodiment 3 and Embodiment 2 is that the SRH in this Embodiment is the second format of the Segment Routing Header, i.e., no extra extension field is added, and is compatible with normal SRH processing, namely: RoutingType = 4 .

[00165] In the SRH compression process, the following determinations are made:

[00166] (1) The Flag field is set to 1 in the SRH to indicate that the SIDs are currently a compressed SID, and the Flag field is set to 0 to indicate that the SID is currently an uncompressed SID. In this case, the Flag field visible in a node with an uncompressed SID (eg node M) is null, as in a normal SRH.

[00167] (2) The first conversion function End.uzip (encoded as 0x77) of the critical node between the compressed SID and the uncompressed SID is defined to perform the conversion of the segment identifier type indicated by the SL from the compressed SID to the uncompressed SID. The code looks like this:

[00168] IF (SRH.Flag == 1)

[00169] Set SRH.Flag = 0

[00170] IF(SL>0)

[00171] Decrease SL by 1

[00172] Update IPv6 DA using Segment_List[SL]

[00173] Forward packet over new DA

[00174]ELSE

[00175] Error message //last SID, conversion operation cannot be performed, and issue an error message;

[00176] (3) A second conversion function End.uzip (encoded as 0x78) of the critical node between the uncompressed SID and the compressed SID is defined to perform the conversion of the segment identifier type indicated by the SL from the uncompressed SID to the compressed SID. The code looks like this:

[00177] IF(SRH.Flag == 0)

[00178] Set SRH.Flag = 1

[00179] IF(SL>0)

[00180] Decrease SL by 1

[00181] Set Sub_SLc using Segment_List[SL] //by evaluating the length of the reserved byte at the end of 128 bits identifying the number of compressed SIDs contained there

[00182] Update IPv6 DAc using Segment_ListfSL]

[00183] Forward packet over new IPv6 DA;

[00184]ELSE

[00185] Error message //last SID, conversion operation could not be performed, and an error message is generated.

[00186] FIG. 14 is a block diagram of the SRH in the transmission direction A->Z of a service packet. Node A uses the SRH shown in FIG. 14 to represent the A-B-D-F-M-Z forwarding path of the L2VPN service, where F:77 is used at the node F to indicate that an End.uzip operation is to be performed to convert the compressed SID to the uncompressed SID.

[00187] FIG. 15 is a block diagram of the SRH in the transmission direction Z->A of the service packet. Node Z uses the SRH shown in FIG. 15 to represent the Z-M-F-D-B-A transmission path of the L2VPN service, where node F is encoded in 128 bits and uses F:78 to indicate that an End.uzip operation is to be performed to convert an uncompressed SID to a compressed SID.

[00188] Since this Embodiment 3 adopts a conventional SRH compatible scheme, that is, Routing type = 4, the compatibility-keeping processing method includes performing the following operations: SL still indicates the number of SIDs in 128 bits; if a compressed SID in SRH is used, the plurality of compressed SIDs are combined to occupy an integer multiple of 128 bits; if an integer multiple of bits is not reached after concatenating the plurality of compressed SIDs, the reserved bytes are filled to form an integer multiple of 128 bits. For example, as shown in FIG. 14, in the transmission direction A->Z of the service packet, there are only three compressed SIDs in the segment list. In this case, all zero codes must be added to fill 128 bits.

[00189] If an uncompressed SID is processed, then SL is reduced by 1 during the End operation. If a compressed SID is processed, then SL is reduced by 1 only after processing of all compressed SIDs in 128 bits is completed, while setting Sub_SL records the number of unprocessed compressed segment IDs within 128 bits. The code looks like this:

[00190] IF(SRH.Flag == 1)

[00191] IF Sub_SL>0 //there are still compressed raw SIDs in the current 128 bits

[00192] Update IPv6 DAc using Segment_List[SL]

[00193] Decrease Sub_SL by 1

[00194] Forward packet over new IPv6 DA;

[00195] ELSE IF (DA[64..95] == 0) and SL>0 //processing of all compressed SIDs in the current 128 bits is completed, and the compressed SIDs in the next 128 bits are taken for processing

[00196] Decrease SL by 1

[00197] Set Sub_SL via Segment_List[SL]

[00198] Update IPv6 DAc using Segment_List[SL]

[00199] Forward packet over new IPv6 DA;

[00200]ELSE

[00201] Error message //if the next 128 bits are missing, service processing other than the End operation should be performed with an error message.

[00202] It should be noted that when processing a compressed SID, it is possible that the value of SL is already zero, but the value of Sub_SL is not zero. In this case, this indicates that the last 128 bits in the segment list have been reached during processing, but there are still unprocessed compressed segment identifiers, which in this case should not be processed as a last hop.

[00203] FIG. 16 shows a service processing flow in the A->Z transmission direction of a service packet. The segment routing path is A-B-D-F-M-Z and the End.DX2 function is executed according to DA=20:02:Z:15::. The service processing flow in the Z->A direction of transmitting a service packet is shown in FIG. 17. The segment routing path is Z-M-F-D-B-A, and the End.DX2 function is executed according to DA=20:02:A:15::.

[00204] According to embodiments of the present invention, an SRH compression method is provided that simultaneously supports both the compressed SID format and the uncompressed SID format in an SRv6 SRH header, whereby an SRv6 forwarding path can contain nodes represented by compressed SIDs or nodes represented by uncompressed SIDs. , in connection with which scenarios for the use of SRv6 are expanding. A new flag field is defined to indicate whether the SID indicated by the SL in the SRH is a compressed SID or an uncompressed SID, and a new function is defined to perform the conversion of a compressed SID to an uncompressed SID and an uncompressed SID to a compressed SID in the SRv6 forwarding path.

[00205] Based on the same technical concept, an apparatus for compressing a segment routing header is also proposed within an embodiment of the present invention. As shown in FIG. 18, the segment routing header compression apparatus 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 ID or an uncompressed segment ID for each node in the segment routing path and configure, for a critical node in the segment routing path, the compressed segment ID, further having the function of performing segment ID type conversion for the segment ID specified by the field Segments Left (SL), wherein the critical node is a node configured using a compressed segment ID, of two adjacent nodes configured using different types of segment IDs.

[00206] The first generation module 102 is configured to generate a segment list containing a configured compressed segment identifier and a configured uncompressed segment identifier.

[00207] The second generation module 103 is configured to generate a segment routing header of the service packet, wherein the segment routing header of the service packet contains a list of segments and a routing type field for specifying a format of the segment routing header, wherein the format of the segment routing header corresponds to the compressed segment identifier format.

[00208] According to some embodiments of the invention, a critical node is a node configured using a compressed segment identifier, and a next hop node is configured using an uncompressed segment identifier. The function to perform a segment ID type conversion on the segment ID specified by the Segments Left (SL) field is the first conversion function to convert the segment ID type specified by SL to an uncompressed segment ID.

[00209] According to some embodiments of the invention, a critical node is a node configured using a compressed segment identifier, and a prior hop node is configured using an uncompressed segment identifier. The function to perform a segment identifier type conversion on the segment identifier indicated by the Segments Left (SL) field is a second conversion function for converting the type of segment identifier indicated by SL to a compressed segment identifier.

[00210] According to some embodiments of the invention, the segment routing header of the service packet also contains a flag field to indicate the segment identifier type for the segment identifier indicated by the SL; the first transformation function includes changing the value of a flag field in a segment routing header of the received service packet to a value indicating an uncompressed segment identifier; and/or the second transformation function includes changing the value of a flag field in the segment routing header of the received service packet to a value indicating a compressed segment identifier.

[00211] According to some embodiments of the invention, the segment routing header of the service packet also contains an extension field that is used to indicate the first format of the segment routing header, and perform the following functions after processing of the compressed segment identifier is completed: decrease the value of SL by n, where n is the length ratio compressed segment identifier to the length of the supported shortest compressed segment identifier, with n being a positive integer; and upon completion of processing the uncompressed segment identifier, decrementing the value of SL by m, where m is the ratio of the length of the uncompressed segment identifier to the length of the shortest compressed segment identifier supported, with m being a positive integer.

[00212] According to some embodiments of the invention, the routing type field is used to indicate a second segment routing header format, and the second segment routing header format contains p compressed segment identifiers occupying t bits of uncompressed segment identifiers, where t is a positive integer, p - a value obtained by rounding off the ratio of the length of the uncompressed segment ID to the length of the compressed segment ID. If the total length p of the compressed segment IDs is less than the total length t of the uncompressed segment IDs, use the reserved bytes to fill the remaining length.

[00213] The routing type field is used to perform the following function: decrement SL by 1 upon completion of processing all compressed segment identifiers within the length of the uncompressed segment identifier.

[00214] According to some embodiments of the invention, terminating the processing of all compressed segment identifiers within the length of the uncompressed segment identifier includes all bits after the currently processed segment identifier in the list of segments being zero.

[00215] According to some embodiments of the invention, the service packet's segment routing header or segment list also includes a counter field for recording the number of unprocessed compressed segment identifiers; and whenever the processing of the compressed segment identifier is completed, the value of the counter field is decremented by 1, while the initial value of the counter field is equal to p; and terminating processing of all compressed segment IDs within the length of the uncompressed segment ID includes that the value of the counter field is zero.

[00216] Based on the same technical concept, the present invention also provides a service processing apparatus applicable to segment routing path nodes, where each segment routing path node is configured using a compressed segment identifier or an uncompressed segment identifier, a critical node in the segment routing path is configured using the compressed segment ID, further having the function of performing segment ID type conversion for the segment ID indicated by the SL field, and the critical node is a node configured using the compressed segment ID, from two adjacent nodes configured using different types of segment IDs. As shown in FIG. 19, the service processing apparatus includes: a receiving module 201, a processing module 202, a conversion module 203, and a forwarding module 204, wherein the receiving module 201 is configured to obtain a segment list and a routing type field to indicate the segment routing header format from the received segment routing header. service packet, and the segment list contains a configured compressed segment identifier and a configured uncompressed segment identifier.

[00217] The processing module 202 is configured to process the current segment ID in the segment list and change the SL according to the routing type field.

[00218] The mapping module 203 is configured to convert the segment ID type to the segment ID indicated by the SL if the current node is a critical node.

[00219] The forwarding module 204 is configured to forward the service packet to the next hop node, with the service packet carrying the type of segment identifier indicated by the SL.

[00220] According to some embodiments of the invention, a critical node is a node configured using a compressed segment identifier, and a next hop node is configured using an uncompressed segment identifier; and the transform module 203 is configured to change the type of the segment ID indicated by SL to an uncompressed segment ID.

[00221] According to some embodiments of the invention, a critical node is a node configured using a compressed segment identifier, and a prior hop node is configured using an uncompressed segment identifier; and the conversion module 203 is configured to change the type of the segment ID indicated by the SL to the compressed segment ID.

[00222] According to some embodiments of the invention, the segment routing header of the service packet also includes a flag field to indicate the type of segment identifier indicated by the SL.

[00223] The receiving module 201 is also configured to obtain a flag field from the segment routing header of the service packet before the conversion module 203 converts the segment identifier type to the segment identifier indicated by the SL.

[00224] The processing module 202 is configured to change the value of the flag field to a value indicating the uncompressed segment identifier and/or to change the value of the flag field to a value indicating the compressed segment identifier.

[00225] According to some embodiments of the invention, the processing module 202 is configured to, if the segment routing header is the first segment routing header format, upon completion of processing the compressed segment identifier, reduce the value of SL by n, where n is the ratio of the length of the compressed segment identifier to the length of the supported the shortest compressed segment identifier, with n being a positive integer; and, upon completion of processing the uncompressed segment identifier, decrementing the value of SL by m, where m is the ratio of the length of the uncompressed segment identifier to the length of the shortest compressed segment identifier supported, m being a positive integer.

[00226] According to some embodiments of the invention, the processing module 202 is configured to, if the segment routing header is the second segment routing header format, upon completion of processing all compressed segment identifiers within the length of the uncompressed segment identifier, decrease SL by 1; wherein the p compressed segment IDs occupy bits of length t of the uncompressed segment IDs, where t is a positive integer, p is a value obtained by rounding off the ratio of the length of the uncompressed segment ID to the length of the compressed segment ID; and, if the total length p of the compressed segment identifiers is less than the total length t of the uncompressed segment identifiers, then the reserved bits are used to fill the remaining length.

[00227] According to some embodiments of the invention, terminating the processing of all compressed segment identifiers within the length of the uncompressed segment identifier includes all bits after the currently processed segment identifier in the segment list are zero.

[00228] According to some embodiments of the invention, the segment routing header of the service packet or the list of segments also contains a counter field for recording the number of unprocessed compressed segment identifiers; and whenever the processing of the compressed segment identifier is completed, the value of the counter field is decremented by 1, while the initial value of the counter field is equal to p; and terminating processing of all compressed segment IDs within the length of the uncompressed segment ID includes that the value of the counter field is zero.

[00229] In accordance with the present invention, there is also provided a computer device comprising one or more processors and a storage device in which one or more programs are stored, the execution of which by one or more processors causes the one or more processors to execute the segment routing header compression method represented by the above embodiments of the invention.

[00230] According to an embodiment of the present invention, there is provided a computer-readable medium that stores a computer program that executes the service processing method of the above embodiments.

[00231] Those skilled in the art can appreciate that all or some of the steps of the methods disclosed above and functional modules/blocks in a device may be implemented in software, firmware, hardware, or suitable combinations thereof. In the case of a hardware implementation, the division into functional modules/blocks above does not necessarily correspond to the division into physical components; for example, one physical component may perform several functions, or one function or step may be performed by several components together. Some or all of the physical components may be implemented as software executable by a processor, such as a central processing unit, digital signal processor, or microprocessor, or as hardware or an integrated circuit such as an ASIC. Such software may be distributed on a computer-readable medium, which may include a computer medium (or storage medium) and a communication medium (transient medium). As known to those skilled in the art, the term "computer-readable medium" includes volatile and non-volatile memory, removable and non-removable memory implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. Computer-readable media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technologies, CD-ROM, Digital Versatile Disk (DVD) or other optical storage device, magnetic cassette, magnetic tape, magnetic disk or other magnetic storage devices, or any other medium that can be used to store the required information and access it by a computer. In addition, as is well known to those skilled in the art, communication media typically comprise computer readable instructions, data structures, program modules, or other data carried by a modulated data signal, such as a carrier or other transmission mechanism, and may include any information delivery media. .

[00232] This description provides exemplary embodiments of the present invention. Although specific terms are used in this description, these terms are used and should be considered in a general descriptive sense only and should not limit the invention. Specialists in this field of technology it is obvious that, unless expressly stated otherwise, in some examples, features, characteristics and/or elements described in connection with a particular embodiment of the invention may be used alone or in combination with features, characteristics and/or elements, described in connection with other embodiments of the present invention. Accordingly, one skilled in the art will appreciate that various changes in the form and details of the invention may be made within the spirit of the invention as defined by the appended claims.

Claims (41)

1. Segment routing header compression method, including: configuring (S11) the compressed segment ID or the uncompressed segment ID for each node in the segment routing path, and configuring (S11), for the critical node in the segment routing path, the compressed segment ID further having the function of performing segment ID type conversion for the segment ID specified by the field Segments Left (SL), wherein the critical node is a node configured using a compressed segment ID, of two adjacent nodes configured using different types of segment IDs; generating (S12) a segment list containing a configured compressed segment identifier and a configured uncompressed segment identifier; generating (S13) a segment routing header of the service packet, wherein the segment routing header of the service packet contains a list of segments and a routing type field for specifying the format of the segment routing header, wherein the format of the segment routing header corresponds to the compressed segment identifier format. 2. The method of claim 1, wherein the critical node is a node configured using a compressed segment ID and the next hop node is configured using an uncompressed segment ID, the segment ID type conversion function for the segment ID specified by SL is the first conversion function, for converting the segment identifier type indicated by SL to an uncompressed segment identifier; and/or the critical node is a node configured using a compressed segment ID, and the prior hop node is configured using an uncompressed segment ID, the function to perform segment ID type conversion on the segment ID specified by SL is the second conversion function to convert the segment ID type specified by SL , to a compressed segment ID, preferably, the segment routing header of the service packet also contains a flag field for indicating the segment identifier type for the segment identifier indicated by the SL; And the first transformation function includes changing the value of a flag field in a segment routing header of the received service packet to a value indicating an uncompressed segment identifier; and/or the second transformation function includes changing the value of a flag field in the segment routing header of the received service packet to a value indicating a compressed segment identifier. 3. The method according to claim 1 or 2, wherein the segment routing header of the service packet also contains an extension field that is used to indicate the first format of the segment routing header; while performing the following function: after the processing of the compressed segment identifier is completed, decrementing the value of SL by n, where n is the ratio of the length of the compressed segment identifier to the length of the shortest compressed segment identifier supported, with n being a positive integer; and, upon completion of processing the uncompressed segment identifier, decrementing the value of SL by m, where m is the ratio of the length of the uncompressed segment identifier to the length of the shortest compressed segment identifier supported, with m being a positive integer. 4. The method of claim 1 or 2, wherein the routing type field is used to indicate a second segment routing header format, and the second segment routing header format comprises p compressed segment identifiers occupying t bits of uncompressed segment identifiers, where t is a positive integer , and p is a value obtained by rounding the ratio of the length of the uncompressed segment identifier to the length of the compressed segment identifier, and if the total length p of the compressed segment identifiers is less than the total length t of the uncompressed segment identifiers, use the reserved bytes to fill the remaining length; And the routing type field is used to perform the following function: decrement SL by 1 upon completion of processing all compressed segment identifiers within the length of the uncompressed segment identifier, preferably, completing processing of all compressed segment IDs within the length of the uncompressed segment ID includes that all bits after the currently processed segment ID in the segment list are zero; and/or the segment routing header of the service packet or segment list also contains a counter field for recording the number of unprocessed compressed segment identifiers; and whenever the processing of the compressed segment identifier is completed, the value of the counter field is decremented by 1, while the initial value of the counter field is equal to p; and terminating processing of all compressed segment IDs within the length of the uncompressed segment ID includes that the value of the counter field is zero. 5. A service processing method applicable to segment routing path nodes, wherein each segment routing path node is configured using a compressed segment identifier or an uncompressed segment identifier, a critical node in the segment routing path is configured using a compressed segment identifier further having a function to perform identifier type conversion segment ID for the segment ID specified by SL, and the critical node is a node configured using a compressed segment ID, of two adjacent nodes configured using different types of segment IDs, the method comprising: obtaining (S21) a segment list and a routing type field for indicating a segment routing header format from a segment routing header of the received service packet, the segment list including a configured compressed segment identifier and a configured uncompressed segment identifier; processing (S22) the current segment ID in the segment list and changing the SL according to the routing type field; if the current node is a critical node, performing (S23) a type conversion of the segment ID to the segment ID specified by the SL; And forwarding (S24) the service packet to the next hop node, the service packet carrying the segment identifier type indicated by the SL. 6. The method of claim 5, wherein the critical node is a node configured using a compressed segment ID and the next hop node is configured using an uncompressed segment ID; and performing a type conversion of the segment ID on the segment ID indicated by the SL, comprising changing the type of the segment ID indicated by the SL to an uncompressed segment ID; and/or the critical node is a node configured using the compressed segment ID, and the prior hop node is configured using the uncompressed segment ID; and performing a type conversion of the segment ID on the segment ID indicated by SL includes: changing the type of the segment ID indicated by SL to a compressed segment ID, preferably, the segment routing header of the service packet also contains a flag field to indicate the type of segment identifier indicated by the SL; before performing the segment ID type conversion for the segment ID specified by SL, the method also includes: obtaining a flag field from a segment routing header of the service packet; changing the segment identifier type indicated by SL to an uncompressed segment identifier includes changing the value of the flag field to a value indicating an uncompressed segment identifier; and/or changing the segment identifier type indicated by SL to a compressed segment identifier includes changing the value of the flag field to a value indicating the compressed segment identifier. 7. The method of claim 5 or 6, wherein changing the SL according to the routing type field includes: if the segment routing header is the first format of the segment routing header, after the processing of the compressed segment identifier is completed, decrease the value of SL by n, where n is the ratio of the length of the compressed segment identifier to the length of the shortest compressed segment identifier supported, with n being a positive integer; And after the processing of the uncompressed segment identifier is completed, decrease the value of SL by m, where m is the ratio of the length of the uncompressed segment identifier to the length of the shortest compressed segment identifier supported, with m being a positive integer. 8. The method of claim 5 or 6, wherein changing the SL according to the routing type field includes: if the segment routing header is the second segment routing header format, upon completion of processing all compressed segment identifiers within the length of the uncompressed segment identifier, decrease SL by 1; wherein the p compressed segment IDs occupy bits of length t of the uncompressed segment IDs, where t is a positive integer, p is a value obtained by rounding off the ratio of the length of the uncompressed segment ID to the length of the compressed segment ID; and, if the total length p of the compressed segment IDs is less than the total length t of the uncompressed segment IDs, use the reserved bytes to fill the remaining length, preferably, completing processing of all compressed segment IDs within the length of the uncompressed segment ID includes that all bits after the currently processed segment ID in the segment list are zero; and/or the segment routing header of the service packet or segment list also contains a counter field for recording the number of unprocessed compressed segment identifiers; and whenever the processing of the compressed segment identifier is completed, the value of the counter field is decremented by 1, while the initial value of the counter field is equal to p; and terminating processing of all compressed segment IDs within the length of the uncompressed segment ID includes that the value of the counter field is zero. 9. A device for compressing a segment routing header, comprising a configuration module (101), a first generation module (102) and a second generation module (103), wherein the configuration module (101) is configured to configure a compressed segment identifier or an uncompressed segment identifier for each node in the segment routing path and configuration, for a critical node in the segment routing path, a compressed segment identifier, additionally having the function of performing segment identifier type conversion for the segment identifier, indicated by the Segments Left (SL) field, wherein the critical node is a node configured using a compressed segment identifier, of two adjacent nodes configured using different types of segment identifiers; the first generation module (102) is configured to generate a list of segments containing a configured compressed segment identifier and a configured uncompressed segment identifier; And the second generation module (103) is configured to generate a segment routing header of the service packet, wherein the segment routing header of the service packet contains a list of segments and a routing type field to indicate the format of the segment routing header, while the format of the segment routing header corresponds to the compressed segment identifier format.

Images