A method, node device and network system for SRv6 hybrid compression
By generating an SRv6 hybrid encoding method carrying hop count identifiers, the problems of reduced network bandwidth utilization and chip processing efficiency caused by the increase in SRv6 SID length are solved, achieving efficient SRv6 hybrid encoding compression and improving network performance.
Patent Information
- Application Number
- CN202211162659.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-09-23
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2042-09-23
AI Technical Summary
The increased SID length in SRv6 leads to reduced network bandwidth utilization, making it difficult for existing network devices to support deep SRH header operations, thus affecting chip processing efficiency.
By acquiring the SRv6 hybrid compression capability of downstream node devices from the target node device, generating an identifier carrying the hop count, and guiding the downstream node device to perform SRv6 hybrid compression or skip nodes that do not support compression, skip compression is achieved.
It improves the efficiency of SRv6 mixed compression, increases network bandwidth utilization, and reduces the processing requirements of the chip.
Smart Images

Figure CN115865770B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of communication technology, and in particular to a method, node device and network system for SRv6 hybrid compression. Background Technology
[0002] The standard SRv6 SID (Segment Routing IPv6) uses a 128-bit IPv6 address format, has routable attributes, supports programmability, simplifies domain path creation, and can quickly establish end-to-end paths in IPv6 networks, flexibly meeting various business and network needs and adapting to the needs of network service development.
[0003] The SRv6 packet extension header encapsulation length = 40B (IPv6 header) + 8B (SRH fixed header) + 16*NB (SegmentList). Although SRv6 has many advantages, it faces two main difficulties in actual deployment: First, as the SID (Segment Identifier) increases, the overhead of the SRv6 extension header increases, reducing network bandwidth utilization; second, SRv6 packet processing places high demands on the chip, and existing network equipment struggles to support the copying and manipulation of deep SRH headers, while the current 128-bit SID length reduces chip processing efficiency. Summary of the Invention
[0004] This disclosure provides a method, node device, and network system for SRv6 hybrid compression. This method enables skip compression of SRv6 hybrid code, thereby improving compression capabilities.
[0005] This disclosure provides a method for SRv6 hybrid compression, the method comprising:
[0006] The target node device sends a first message carrying a first identifier to the downstream node device, so that the downstream device may perform SRv6 mixed compression or not perform SRv6 mixed compression based on the first identifier.
[0007] The method further includes the following steps before the target node device sends the first message carrying the first identifier to the downstream node device:
[0008] The target node device receives a second message sent by each downstream node device. The second message carries a second identifier indicating whether it supports SRv6 mixed compression capability.
[0009] The target node device determines whether each downstream node device supports SRv6 mixed compression based on the second identifier.
[0010] The target node device sends a first message carrying a first identifier to the downstream node device, including:
[0011] The target node device obtains the target downstream node device that does not support SRv6 mixed compression based on the second message sent by each downstream node device, and generates a first identifier based on the number of hops from itself to the target downstream node device.
[0012] Send a first message carrying the first identifier to downstream node devices.
[0013] The method further includes the following steps before the target node device sends the first message carrying the first identifier to the downstream node device:
[0014] The target node device obtains the target downstream node devices that do not support SRv6 mixed compression from the controller, and generates a first identifier based on the number of hops from itself to the target downstream node device.
[0015] The controller determines whether each downstream node device supports SRv6 mixed compression by using the second identifier in the second message sent by each downstream node device, and provides the target node device with target downstream node devices that do not support SRv6 mixed compression.
[0016] As can be seen from the above embodiments, the node device can obtain which downstream node devices do not support SRv6 mixed compression through the second identifier, and add the first identifier to the first message. The first identifier carries the hop count, so that the downstream node device can perform SRv6 mixed compression according to the hop count.
[0017] This disclosure also provides a method for SRv6 hybrid compression, the method comprising:
[0018] The target node device determines the target downstream node device that does not support SRv6 mixed compression among the downstream node devices based on the second identifier in the second message sent from each downstream node device, and obtains the number of hops from itself to each target downstream node device.
[0019] A first identifier is generated based on the number of hops, and a first message carrying the first identifier is sent to the downstream node device of the next hop;
[0020] The downstream node device receiving the first message obtains the first identifier. If the hop count carried in the first identifier is 0, the downstream node device receiving the first message performs SRv6 mixed compression. If the hop count carried in the first identifier is A, and A is not 0, it means that SRv6 mixed compression is performed after skipping A downstream node devices.
[0021] This disclosure provides a node device, which includes:
[0022] The sending module is used to send a first message carrying a first identifier to a downstream node device, so that the downstream device may perform SRv6 mixed encoding and compression or not perform SRv6 mixed encoding and compression according to the first identifier.
[0023] The node device further includes:
[0024] The receiving module is used to receive the second message sent by each downstream node device. The second message carries a second identifier indicating whether it supports SRv6 mixed compression capability.
[0025] The identification module is used to determine whether each downstream node device supports SRv6 mixed compression based on the second identifier.
[0026] Specifically, the sending module is used to obtain the target downstream node device that does not support SRv6 mixed compression based on the second message sent by each downstream node device, generate a first identifier based on the number of hops from itself to the target downstream node device, and send a first message carrying the first identifier to the downstream node device.
[0027] The node device further includes:
[0028] The receiving module is used to obtain the target downstream node devices that do not support SRv6 mixed compression from the controller, and generate a first identifier based on the number of hops from itself to the target downstream node device.
[0029] The controller determines whether each downstream node device supports SRv6 mixed compression by using the second identifier in the second message sent by each downstream node device, and provides the node device with target downstream node devices that do not support SRv6 mixed compression.
[0030] This disclosure also provides a network system comprising: a target node device and a downstream node device.
[0031] The target node device determines the target downstream node device that does not support SRv6 mixed compression among the downstream node devices based on the second identifier in the second message sent from each downstream node device, and obtains the number of hops it has made to reach each target downstream node device.
[0032] The target node device generates a first identifier based on the number of hops, and sends a first message carrying the first identifier to the downstream node device of the next hop;
[0033] The downstream node device that receives the first message obtains the first identifier. If the number of hops carried in the first identifier is 0, the downstream node device that receives the first message performs SRv6 mixed compression. If the number of hops carried in the first identifier is A, and A is not 0, it means that SRv6 mixed compression is performed after skipping A downstream node devices. Attached Figure Description
[0034] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this specification and, together with the description, serve to explain the principles of this specification.
[0035] Figure 1 This is a structural diagram of an SRv6 SID format that supports compression, provided as an embodiment of the present disclosure.
[0036] Figure 2 An encoding example of mixing 128-bit SRv6 SID and 32-bit G-SID in G-SRH is provided for embodiments of this disclosure.
[0037] Figure 3 This is a schematic diagram of a network architecture provided in an embodiment of the present disclosure.
[0038] Figure 4 This is a schematic diagram of a network architecture provided in an embodiment of the present disclosure.
[0039] Figure 5 This is a flowchart illustrating an SRv6 hybrid compression method provided in an embodiment of this disclosure. Detailed Implementation
[0040] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this specification. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this specification as detailed in the appended claims.
[0041] The terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to be limiting of this specification. The singular forms “a,” “the,” and “the” as used in this specification and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items.
[0042] It should be understood that although the terms first, second, third, etc., may be used in this specification to describe various information, this information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of this specification, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to determination."
[0043] Currently, the G-SRv6 (Generalized SRv6) scheme is used to compress the length of the SID node encapsulated in the SRH header. Typically, SIDs within an SRv6 field are assigned the same common prefix. The common prefix of SIDs in the SIDList can be removed, carrying only the changed, compressed SID, thus reducing the overhead of the SRv6 header. When changing the destination address, the G-SID in the IPv6 address is replaced with the new G-SID, forming a new SID. Packet forwarding is then completed by looking up the table based on this new SID.
[0044] In multi-domain scenarios, it is not possible to guarantee that the SIDs of multiple domains have the same common prefix. Cross-domain SRv6 paths can be easily established through mixed programming: SRv6 SIDs and G-SIDs are mixed and orchestrated in G-SRv6, thereby supporting the mixed programming of compressed nodes and ordinary SRv6 nodes, realizing the evolution of existing resources and smooth upgrades.
[0045] When orchestrating SRv6 SID paths, this scheme requires that the next-hop SID be compressed in a mixed-path scenario, provided that the previous-hop SID carries a COC (Copyright Authentication Code) tag. This means that if one device does not support compression, even if the next device does support compression, the SID of that device cannot be compressed. This negatively impacts the compression performance of the SRv6 path.
[0046] like Figure 1 As shown, an SRv6 SID format that supports compression is defined as follows: Complete SID = B (Block, i.e., CommonPrefix) + N (Node ID) + F (Function) + A (Args) (optional) + Padding (optional); G-SID = N + F (Function).
[0047] Therefore, G-SID + Block + F + A (optional) + Padding (optional) = Complete SID. Figure 2This example illustrates an encoding scheme where 128-bit SRv6 SIDs and 32-bit G-SIDs are mixed within a G-SRH. This scheme uses the COC FlavorSID to indicate the update of the next 32-bit G-SID to the destination address. The SRv6 compressed subpath begins with a 128-bit SRv6 SID that supports compression (carrying a COC Flavor). This SID carries complete SID information, including the Common Prefix, which can be used to reconstruct the next complete SID from subsequent G-SIDs, and is composed of multiple subsequent G-SIDs. The G-SID list ends with a 128-bit delimiter. The COC Flavor is used to identify the start and end of the compressed path. When a SID in the DA carries a COC Flavor, the next 32-bit G-SID needs to be updated to the destination address. When a SID in the DA does not carry a COC FlavorSID, it indicates that SL-- is used, and the next 128-bit SID is updated to the destination address.
[0048] like Figure 3 In one network architecture shown, if node B does not support compression, the current implementation requires a compressed sub-path to begin with a 128-bit SRv6 SID (carrying COC Flavor) that supports compression. Since node B cannot be used as the bootstrap SID, node C's SID also cannot be compressed. Only node C's SID can serve as the bootstrap SID for node D to begin compression. In other words, if any intermediate node does not support compression, even if its next SID supports compression, that SID cannot be compressed, which affects compression performance in mixed-mode programming.
[0049] To address the aforementioned technical problems, this disclosure provides an SRv6 hybrid compression method, which includes:
[0050] The target node device sends a first message carrying a first identifier to the downstream node device, so that the downstream device may perform SRv6 mixed compression or not perform SRv6 mixed compression based on the first identifier.
[0051] In this embodiment, the target node device can be a head node device or any upstream node device in the network relative to the downstream node device.
[0052] In this embodiment, the first identifier in the first message sent by the target node device to the downstream node device can be represented by the value of HOP Flavor. When the value of HOP Flavor is 1, it indicates that SRv6 mixed compression is performed after skipping one node device. Figure 3As shown, when target node device A sends a first message carrying HOP Flavor=1, downstream node device B receives it and recognizes that HOP Flavor=1 (i.e., not 0). Therefore, downstream node device B does not perform compression. When the message is subsequently transmitted to downstream node device C, HOP Flavor=0, so downstream node device C performs compression. At this point, its G-SID's bootstrap SID is still node A's SID. The complete G-SID information is then recovered using the SID of the COC Flavor carried by node A.
[0053] In one embodiment, the start of a compressed SRv6 path is indicated by a 128-bit COC Flavor SID and HOP Flavor SID, which contains the COC Flavor G-SID and Hop Value. This SID carries complete SID information, including information such as the Common Prefix, and can be used to recover the complete next SID from subsequent G-SIDs that skip the HOP Value and the 128-bit SID.
[0054] The G-SIDs in the compression path all carry the G-SIDs of COC and HOP, indicating that the SID of the skipped HOP Value is a 32-bit G-SID.
[0055] The last G-SID in the compression path can be a 32-bit G-SID without COC Flavor, used to indicate the end of the compression path. Its combination into an SRv6 SID in the DA is processed according to the rules for 128-bit SIDs.
[0056] In this embodiment, when the target node device sends the first message as the guiding device, it needs to obtain which downstream node devices do not support compression (i.e., which downstream node devices need to be skipped).
[0057] In one approach, the target node device receives a second message sent by each downstream node device, the second message carrying a second identifier indicating whether it supports SRv6 mixed compression capability.
[0058] The target node device determines whether each downstream node device supports SRv6 mixed compression based on the second identifier.
[0059] When establishing a network, each node device sends an announcement message (second message) to inform the other party of its location information. In this embodiment, the announcement message can carry a second identifier of whether it supports SRv6 mixed compression capability. After receiving the announcement message, the target node device can calculate the number of hops to reach the downstream node device and obtain the first identifier when it learns that a certain downstream node device does not support SRv6 mixed compression capability.
[0060] In another embodiment, when a controller is present in the network, the target node device obtains the target downstream node devices that do not support SRv6 mixed compression from the controller, and generates a first identifier based on the number of hops from itself to the target downstream node device.
[0061] The controller determines whether each downstream node device supports SRv6 mixed compression by using the second identifier in the second message sent by each downstream node device, and provides the target node device with target downstream node devices that do not support SRv6 mixed compression.
[0062] In this embodiment, deploying the SRv6 compression scheme requires address planning and upgrading the control plane and data plane to support SRv6 compression. After the node's IGP and BGP are configured, it is necessary to publish the capability to support node compression. Therefore, it is necessary to extend protocols such as ISIS, BGP-LS, and BGP-Policy. This section focuses on describing the extension of HOP Flavor in the control plane.
[0063] After completing the SRv6 SID deployment, it is necessary to complete SRv6 SID planning and configuration. Nodes generate local SID tables based on the configuration and then publish the SIDs to the network via the IGP protocol. Therefore, it is necessary to extend the IGP protocol, such as the ISIS protocol. Taking the ISIS protocol [draft-ietf-lsr-isis-srv6-extensions-17] as an example, the protocol extension is as follows:
[0064] Extending SRv6 Capabilities sub-TLV, adding H-Flag, and announcing the ability of nodes to skip several nodes that do not support compression for the next node, i.e., the ability to skip and pass COC Flavor compression information.
[0065] The O-flag is defined in draft-ietf-lsr-isis-srv6-extensions-17, the C-flag indicates the node's SRv6 compression capability, and the H-flag is defined in this invention (using the 3rd bit as the H-flag). When the H-flag is set to 1, it means "the current node has the ability to hop and transmit COC Flavor compression information," indicating the node's SRv6 hop compression capability. The C-flag must be set when the H-flag is set. Packets with only a set H-flag and an unset C-flag should have their H-flag ignored.
[0066] SDN controllers or nodes that do not support skip compression should ignore the H-flag when they receive an SRv6Capabilitiessub-TLV with an extended H-flag.
[0067] A node's SRv6 hop compression capability can be reported to the SDN controller via BGP-LS. When calculating SRv6 TE paths, the SDN controller organizes the SID list based on the node's hop compression capability. H-Flag can also be used during node routing.
[0068] If the head node does not report SRv6 hop compression capability, the SDN controller should not issue an SRv6 policy containing the HG-SID to that head node. If it must be issued, it can only contain SIDs without HOP flavor.
[0069] Extended SRv6 END SID sub-TLV, SRv6 End.X SID sub-TLV, and SRv6 LAN End.X SID sub-TLV add H-flag identifier SID to support skip compression.
[0070] Setting the H-flag requires that the C-flag be set. When the H-flag is set, the sub-sub-TLVs need to carry the SRv6 SID Structure Sub-sub-TLV. Four bits from Arg.Length (considering the actual network topology) are used to indicate how many nodes need to be skipped before compression. This value is named H.value, and its current range is 0 to 2^4.
[0071] When H-flag is set, C-flag must also be set. Packets with H-flag set but C-flag not set should have their H-flag ignored. If H-flag = 1 and carries the SRv6 SID Structure Sub-sub-TLV, the SID in the SRv6 EndSub-TLV is considered a hop-compressed SID. If only H-flag is set but the SRv6 SIDStructure Sub-sub-TLV is not carried, H-flag and C-flag are ignored, and the SID is considered uncompressed. If the SID's Behavior carries HOP Flavor, H-flag must be set, and the SRv6 SID Structure Sub-sub-TLV must be carried; otherwise, it is considered an invalid SID and must be discarded. If only C-flag is carried but H-flag is not, the SID is considered a compressed SID without hop-compressed capability. When a node that does not support jump compression receives an unsupported Endpoint Behavior, such as the SID of HOP Flavor, it will directly ignore the TLV associated with that SID, but will still continue to distribute it to other nodes.
[0072] First, during the IGP capability release process, nodes identify that they support skip compression capabilities by setting the extended H-flag of the SRv6 Capabilities TLV.
[0073] To support SRv6 compression, a corresponding SID needs to be instantiated and published to the network or sent to the controller via protocols such as IGP. When a node instantiates a SID, a corresponding SID forwarding table entry will be generated.
[0074] When publishing a SID, you need to set the H-flag in the corresponding TLV (such as SRv6 End SID sub-TLV, SRv6End.X SID sub-TLV, SRv6 LAN End.X SID sub-TLV) to indicate that the format of this SID supports skip compression.
[0075] The published SID has HOP Flavor, which identifies the H-SID or compressed HG-SID as being compressed after skipping H.value SIDs.
[0076] The BGP-LS protocol can be used for the aforementioned SRv6-related information [draft-ietf-idr-bgpls-srv6-ext-08]. This invention extends the draft-ietf-idr-bgpls-srv6-ext-08 document to support reporting SRv6 optimized SID status.
[0077] To calculate TE paths, the controller needs to understand the entire network topology, including TE and SR attributes. The controller can collect network topology information via the BGP-LS protocol. To support SRv6 hop compression, three types of information need to be extended.
[0078] Extend the SRv6 Capabilities TLV by adding an H-flag to announce node support for hop compression capabilities. When the H-flag is set, the C-flag must also be set. Packets with only a set H-flag and no set C-flag should ignore the H-flag. When the H-flag is set to 1, it indicates that "the current node has SRv6 hop compression capability," used to identify the node's SRv6 hop compression capability. SDN controllers or nodes that do not support hop compression should ignore the H-flag when receiving an SRv6 Capabilities TLV with an extended H-flag. The node's SRv6 compression capability is reported to the SDN controller via BGP-LS. When calculating SRv6 TE paths, the SDN controller can arrange the SID list based on the node's compression capability.
[0079] Extend the SRv6 End.X SID TLV under SRv6 Link Attributes to add H-flag identifier SID support for skip compression.
[0080] Extend the End Behavior sub-TLV corresponding to the Node SID by adding an H-flag to indicate support for skip compression. The BGP-LS information comes from IGP, and the H-flag extension logic here is the same as the IGP extension.
[0081] When establishing a BGP-LS connection, if the node supports SRv6 hop compression, the H-flag in the SRv6Capabilities TLV needs to be set. The node can upload SID information that supports hop compression to the controller via BGP-LS. When uploading these SIDs, the H-flag needs to be set in the corresponding SRv6 End.X TLV, SRv6 LAN End.X SID TLV, and SRv6 EndpointBehavior TLV to fully describe the SID. When the H-flag is set, the SRv6 SID Structure TLV needs to be carried, where H.vlaue is used to describe the number of hops.
[0082] Through the above embodiments, when some intermediate nodes cannot be compressed, only the current node is not compressed, and it will not affect the compression status of the next node. That is, if the next node is a SID that supports compression, it can also be compressed, which means that skip compression can be supported.
[0083] like Figure 4 As shown in the scheme of this disclosure, nodes A, C, and D all support compression, while nodes B1 and B2 do not. According to traditional compression schemes, the upstream node B2 of device C does not support compression, meaning that the SID of this node cannot carry the COC tag, thus preventing compression of node C's SID. With this invention, a HOP Flavor tag can be carried on node A, indicating that compression should be performed after skipping the H.value hop. This allows node C to utilize the information in node A's COC Flavor for compression, improving compression efficiency in mixed-mode programming.
[0084] like Figure 5 As shown in the embodiments of this disclosure, a method for SRv6 mixed compression is also provided, the method comprising:
[0085] The S501 target node device determines the target downstream node device that does not support SRv6 mixed compression among the downstream node devices based on the second identifier in the second message sent from each downstream node device, and obtains the number of hops from itself to each target downstream node device.
[0086] S502 generates a first identifier based on the number of hops and sends a first message carrying the first identifier to the downstream node device of the next hop;
[0087] S503 The downstream node device receiving the first message obtains the first identifier. If the hop count carried in the first identifier is 0, the downstream node device receiving the first message performs SRv6 mixed compression. If the hop count carried in the first identifier is A, and A is not 0, it means that SRv6 mixed compression is performed after skipping A downstream node devices.
[0088] This method allows for compression only on the current node when compression is not possible, without affecting the compression status of the next node. In other words, if the next node has a compressible SID, compression can still be performed. This improves compression performance in mixed-mode programming.
[0089] Based on the above method embodiments, this disclosure also provides a node device, the node device comprising:
[0090] The sending module is used to send a first message carrying a first identifier to a downstream node device, so that the downstream device may perform SRv6 mixed encoding and compression or not perform SRv6 mixed encoding and compression according to the first identifier.
[0091] The node device further includes:
[0092] The receiving module is used to receive the second message sent by each downstream node device. The second message carries a second identifier indicating whether it supports SRv6 mixed compression capability.
[0093] The identification module is used to determine whether each downstream node device supports SRv6 mixed compression based on the second identifier.
[0094] Specifically, the sending module is used to obtain the target downstream node device that does not support SRv6 mixed compression based on the second message sent by each downstream node device, generate a first identifier based on the number of hops from itself to the target downstream node device, and send a first message carrying the first identifier to the downstream node device.
[0095] The node device further includes:
[0096] The receiving module is used to obtain the target downstream node devices that do not support SRv6 mixed compression from the controller, and generate a first identifier based on the number of hops from itself to the target downstream node device.
[0097] The controller determines whether each downstream node device supports SRv6 mixed compression by using the second identifier in the second message sent by each downstream node device, and provides the node device with target downstream node devices that do not support SRv6 mixed compression.
[0098] This disclosure also provides a network system, the network system comprising: a target node device and a downstream node device:
[0099] The target node device determines the target downstream node device that does not support SRv6 mixed compression among the downstream node devices based on the second identifier in the second message sent from each downstream node device, and obtains the number of hops it has made to reach each target downstream node device.
[0100] The target node device generates a first identifier based on the number of hops, and sends a first message carrying the first identifier to the downstream node device of the next hop;
[0101] The downstream node device that receives the first message obtains the first identifier. If the number of hops carried in the first identifier is 0, the downstream node device that receives the first message performs SRv6 mixed compression. If the number of hops carried in the first identifier is A, and A is not 0, it means that SRv6 mixed compression is performed after skipping A downstream node devices.
[0102] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.
[0103] Other embodiments of this specification will readily occur to those skilled in the art upon consideration of the specification and practice of the invention claimed herein. This specification is intended to cover any variations, uses, or adaptations that follow the general principles of this specification and include common knowledge or customary techniques in the art not claimed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this specification are indicated by the following claims.
[0104] It should be understood that this specification is not limited to the precise structures described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this specification is limited only by the appended claims.
[0105] The above description is merely a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this specification should be included within the scope of protection of this specification.
Claims
1. A method for SRv6 hybrid compression, characterized in that, The method includes: The target node device sends a first message carrying a first identifier to the downstream node device, so that the downstream node device may perform SRv6 mixed encoding and compression or not perform SRv6 mixed encoding and compression according to the first identifier. The target node device sends a first message carrying a first identifier to the downstream node device, including: The target node device obtains the target downstream node device that does not support SRv6 mixed compression based on the second message sent by each downstream node device, and generates a first identifier based on the number of hops from itself to the target downstream node device. Send a first message carrying the first identifier to downstream node devices.
2. The method according to claim 1, characterized in that, Before the target node device sends the first message carrying the first identifier to the downstream node device, the method further includes: The target node device receives a second message sent by each downstream node device. The second message carries a second identifier indicating whether it supports SRv6 mixed compression capability. The target node device determines whether each downstream node device supports SRv6 mixed compression based on the second identifier.
3. The method according to claim 1, characterized in that, Before the target node device sends the first message carrying the first identifier to the downstream node device, the method further includes: The target node device obtains the target downstream node devices that do not support SRv6 mixed compression from the controller, and generates a first identifier based on the number of hops from itself to the target downstream node device. The controller determines whether each downstream node device supports SRv6 mixed compression by using the second identifier in the second message sent by each downstream node device, and provides the target node device with target downstream node devices that do not support SRv6 mixed compression.
4. A method for SRv6 hybrid compression, characterized in that, The method includes: The target node device determines the target downstream node device that does not support SRv6 mixed compression among the downstream node devices based on the second identifier in the second message sent from each downstream node device, and obtains the number of hops from itself to each target downstream node device. A first identifier is generated based on the number of hops, and a first message carrying the first identifier is sent to the downstream node device of the next hop; The downstream node device receiving the first message obtains the first identifier. If the hop count carried in the first identifier is 0, the downstream node device receiving the first message performs SRv6 mixed compression. If the hop count carried in the first identifier is A, and A is not 0, it means that SRv6 mixed compression is performed after skipping A downstream node devices.
5. A node device, characterized in that, The node device includes: The sending module is used to send a first message carrying a first identifier to a downstream node device, so that the downstream node device may perform SRv6 mixed encoding and compression or not perform SRv6 mixed encoding and compression according to the first identifier. Specifically, the sending module is used to obtain the target downstream node device that does not support SRv6 mixed compression based on the second message sent by each downstream node device, generate a first identifier based on the number of hops from itself to the target downstream node device, and send a first message carrying the first identifier to the downstream node device.
6. The node device according to claim 5, characterized in that, The node device also includes: The receiving module is used to receive the second message sent by each downstream node device. The second message carries a second identifier indicating whether it supports SRv6 mixed compression capability. The identification module is used to determine whether each downstream node device supports SRv6 mixed compression based on the second identifier.
7. The node device according to claim 5, characterized in that, The node device also includes: The receiving module is used to obtain the target downstream node devices that do not support SRv6 mixed compression from the controller, and generate a first identifier based on the number of hops from itself to the target downstream node device. The controller determines whether each downstream node device supports SRv6 mixed compression by using the second identifier in the second message sent by each downstream node device, and provides the node device with target downstream node devices that do not support SRv6 mixed compression.
8. A network system, characterized in that, The network system includes: target node devices and downstream node devices. The target node device determines the target downstream node device that does not support SRv6 mixed compression among the downstream node devices based on the second identifier in the second message sent from each downstream node device, and obtains the number of hops it has made to reach each target downstream node device. The target node device generates a first identifier based on the number of hops, and sends a first message carrying the first identifier to the downstream node device of the next hop; The downstream node device that receives the first message obtains the first identifier. If the number of hops carried in the first identifier is 0, the downstream node device that receives the first message performs SRv6 mixed compression. If the number of hops carried in the first identifier is A, and A is not 0, it means that SRv6 mixed compression is performed after skipping A downstream node devices.
Citation Information
Patent Citations
Data packet processing method and device
CN113556284A
