CN115865770A

CN115865770A - SRv6 mixed editing and compressing method, node equipment and network system

Info

Publication number: CN115865770A
Application number: CN202211162659.8A
Authority: CN
Inventors: 许文祥; 褚丹丹; 郑涛
Original assignee: New H3C Technologies Co Ltd
Current assignee: New H3C Technologies Co Ltd
Priority date: 2022-09-23
Filing date: 2022-09-23
Publication date: 2023-03-28

Abstract

The present specification provides a SRv6 hybrid compression method, which includes: and the target node equipment sends a first message carrying a first identifier to downstream node equipment so that the downstream equipment performs SRv6 mixed editing compression or does not perform SRv6 mixed editing compression according to the first identifier. By the method, jump compression of SRv6 hybrid coding can be realized, and the compression capacity is improved.

Description

SRv6 mixed editing and compressing method, node equipment and network system

Technical Field

The present disclosure relates to the field of communications technologies, and in particular, to a method, a node device, and a network system for SRv6 hybrid coding compression.

Background

The standard SRv6 SID (Segment Routing IPv6, IPv6 Segment Routing) adopts a 128-bit IPv6 address format, has routable attribute, supports programmable capability, simplifies domain path creation, can quickly establish an end-to-end path in an IPv6 network, flexibly meets various services and network requirements, and meets the requirements of network service development.

SRv6 has a packet extension header encapsulation length =40B (IPv 6 header) +8B (SRH fixed header) +16 × nb (Segment List). While SRv6 has many advantages, there are two major difficulties faced in practical deployment: firstly, with the increase of SID (Segment Identifier), SRv6 extension header overhead will increase, and network bandwidth utilization ratio will decrease; secondly, the processing of the SRv6 message has higher requirements on the chip, the existing network equipment is difficult to support for the copying and operation of the SRH head with large depth, and the current SID length of 128 bits can reduce the processing efficiency of the chip.

Disclosure of Invention

The embodiment of the disclosure provides a method, node equipment and a network system for SRv6 hybrid coding compression, and by the method, jump compression of SRv6 hybrid coding can be realized, and compression capacity is improved.

The embodiment of the disclosure provides a method for SRv6 hybrid coding compression, which comprises the following steps:

and the target node equipment sends a first message carrying a first identifier to downstream node equipment so that the downstream equipment performs SRv6 mixed editing compression or does not perform SRv6 mixed editing compression according to the first identifier.

Before the target node device sends the first packet carrying the first identifier to the downstream node device, the method further includes:

the target node equipment receives a second message sent by each downstream node equipment, wherein the second message carries a second identifier indicating whether the target node equipment supports SRv6 mixed coding compression capability or not;

and the target node equipment determines whether each downstream node equipment supports SRv6 hybrid compression or not according to the second identifier.

The sending, by the target node device, a first packet carrying a first identifier to a downstream node device includes:

the target node equipment acquires target downstream node equipment which does not support SRv6 mixed coding compression according to the second message sent by each downstream node equipment, and generates a first identifier according to the acquired hop count from the target node equipment to the target downstream node equipment;

and sending a first message carrying the first identifier to downstream node equipment.

the target node equipment acquires target downstream node equipment which does not support SRv6 mixed editing compression in each downstream node equipment from a controller, and generates a first identifier according to the acquired hop count from the target node equipment to the target downstream node equipment;

the controller determines whether each downstream node device supports SRv6 hybrid compression or not through a second identifier in a second message sent by each downstream node device, and provides a target downstream node device which does not support SRv6 hybrid compression for the target node device.

It can be seen from the foregoing embodiments that the node device may obtain, through the second identifier, that the downstream node devices do not support SRv6 hybrid coding compression, and add the first identifier in the first message, where the first identifier carries hop count, so that the downstream node devices perform SRv6 hybrid coding compression according to the hop count.

The embodiment of the disclosure also provides a method for SRv6 hybrid encoding and compressing, which comprises the following steps:

the target node equipment determines target downstream node equipment which does not support SRv6 mixed coding compression in each downstream node equipment according to a second identifier in a second message sent from each downstream node equipment, and obtains the hop count of the target downstream node equipment;

generating a first identifier according to the hop count, and sending a first message carrying the first identifier to downstream node equipment of a next hop;

and the downstream node equipment receiving the first message acquires the first identifier, if the hop count carried in the first identifier is 0, the downstream node equipment receiving the first message executes SRv6 mixed compilation compression, and if the hop count carried in the first identifier is A and A is not 0, the downstream node equipment skipping A downstream node equipment executes SRv6 mixed compilation compression.

The disclosed embodiment provides a node device, which includes:

a sending module, configured to send a first packet carrying a first identifier to a downstream node device, so that the downstream device performs SRv6 hybrid coding compression or does not perform SRv6 hybrid coding compression according to the first identifier.

Wherein the node device further comprises:

a receiving module, configured to receive a second packet sent by each downstream node device, where the second packet carries a second identifier indicating whether the second packet supports SRv6 hybrid compression capability;

and the identification module is used for determining whether the downstream node equipment supports SRv6 hybrid compression or not according to the second identifier.

The sending module is specifically configured to obtain, according to the second packet sent by each downstream node device, a target downstream node device that does not support SRv6 hybrid compression, generate a first identifier according to the obtained hop count from the sending module to the target downstream node device, and send, to the downstream node device, the first packet carrying the first identifier.

Wherein the node device further comprises:

the receiving module is used for acquiring target downstream node equipment which does not support SRv6 mixed encoding compression in each downstream node equipment from the controller, and generating a first identifier according to the acquired hop count from the receiving module to the target downstream node equipment;

the controller determines whether each downstream node device supports SRv6 hybrid compression or not through a second identifier in a second message sent by each downstream node device, and provides target downstream node devices which do not support SRv6 hybrid compression for the node devices.

The embodiment of the present disclosure further provides a network system, where the network system includes: target node device and downstream node device:

the target node equipment generates a first identifier according to the hop count, and sends a first message carrying the first identifier to downstream node equipment of the next hop;

the downstream node device receiving the first message acquires the first identifier, if the hop count carried in the first identifier is 0, the downstream node device receiving the first message executes SRv6 hybrid coding compression, and if the hop count carried in the first identifier is a and a is not 0, the downstream node device skipping a number of downstream node devices executes SRv6 hybrid coding compression.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with this specification and, together with the description, serve to explain the principles of the specification.

Fig. 1 is a structural diagram of an SRv6 SID format supporting compression according to an embodiment of the present disclosure.

Fig. 2 is an example of encoding in which 128bit SRv6 SID and 32bit G-SID are mixed and coded in G-SRH according to the embodiment of the present disclosure.

Fig. 3 is a schematic diagram of a network architecture according to an embodiment of the present disclosure.

Fig. 4 is a schematic diagram of a network architecture according to an embodiment of the present disclosure.

Fig. 5 is a schematic flowchart of a method for SRv6 hybrid encoding and compressing according to an embodiment of the present disclosure.

Detailed Description

Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the specification, as detailed in the claims that follow.

The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the description. As used in this specification and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.

It should be understood that although the terms first, second, third, etc. may be used herein to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, the first information may also be referred to as second information, and similarly, the second information may also be referred to as first information, without departing from the scope of the present specification. The word "if," as used herein, may be interpreted as "at \8230; \8230when" or "when 8230; \823030when" or "in response to a determination," depending on the context.

Currently, the G-SRv6 (Generalized SRv 6) scheme is used to compress the length of the SID node encapsulated in the SRH header. In general, the same Common Prefix (Common Prefix) is allocated to the SID in one SRv6 domain, and the Common Prefix of the SID in the SID List can be removed, and only the changed compressed SID is carried, thereby reducing the overhead of the SRv6 header; when the destination address is replaced, the G-SID replaces the G-SID in the IPv6 address to form a new SID, and the forwarding of the data packet is completed based on the table lookup of the new SID.

Under a multi-domain scene, SIDs of multiple domains cannot be guaranteed to have the same common prefix, and establishment of an SRv6 path across multiple domains can be conveniently realized through mixed compilation: SRv6 SID and G-SID are arranged in G-SID mixed arrangement in G-SRv6, thereby supporting mixed programming of compression nodes and common SRv6 nodes, realizing stock evolution and smooth upgrading.

When the scheme is used for arranging an SRv6 SID path, in a mixed-arrangement scene, the premise that a next-hop SID needs to be compressed is that a previous-hop SID carries a SID marked by COC, that is, if one device does not support compression, even if the next device supports compression, the SID of the device supporting compression cannot be compressed. Thereby affecting the compression performance of the SRv6 path.

As shown in FIG. 1, a SRv6 SID format supporting compression, full SID = B (Block, i.e., common Prefix) + N (node ID) + F (Function) + A (Args) (optional) + Padding (optional), G-SID = N + F (Function)

Thus, G-SID + Block + F + a (optional) + Padding (optional) = complete SID. As shown in FIG. 2, the scheme of the encoding example of the hybrid encoding of the 128bit SRv6 SID and the 32bit G-SID in the G-SRH is to update the next 32bits G-SID to the destination address through COC _ Flaver SID indication. The SRv6 compression subpath starts with a 128bit SRv6 SID (carrying COC Flovor) bootstrap supporting compression (this SID carries the complete SID information, including Common Prefix, etc., which can be used to recover the complete next SID with the subsequent G-SID), and consists of the following multiple G-SIDs. At the end of the G-SID List, it ends with 128 bits as a boundary. The start and end of the compression path are identified using the COC flag. When the SID in the DA carries COC Flavor, the next 32bit G-SID needs to be updated to the destination address. And when the SID in the DA does not carry the COC _ Flavor SID, the SL- - -is indicated, and the next 128-bit SID is updated to the destination address.

As shown in fig. 3, in a network architecture, if the node B does not support compression, since the current scheme compression subpath needs to be guided by a 128bit SRv6 SID (carrying COC flag) that supports compression, the node B cannot be used as a guided SID, so the SID of the node C cannot be compressed, and only the SID of the node C is used as the guided SID, and the node D can start compression. That is, if one node in the middle does not support compression, even if its next SID supports compression, the SID cannot be compressed, which affects the compression performance in the shuffle mode.

In order to solve the foregoing technical problem, an embodiment of the present disclosure provides a method for SRv6 hybrid coding compression, where the method includes:

the target node equipment sends a first message carrying a first identifier to downstream node equipment so that the downstream equipment performs SRv6 mixed editing compression or does not perform SRv6 mixed editing compression according to the first identifier.

In this embodiment, the target node device may be a head node device, or may be any upstream node device in the network relative to a downstream node device.

In this embodiment, the first identifier in the first message sent by the target node device to the downstream node device may be a value of an HOP flag, and when the value of the HOP flag is 1, it indicates that one node device is skipped and then SRv6 hybrid coding compression is performed, as shown in fig. 3, when the first message sent by the target node device a carries the HOP flag =1, and after the downstream node device B receives the first message, it identifies that the HOP flag =1, that is, it is not 0, then the downstream node device B does not perform compression, and when the first message is subsequently sent to the downstream node device C, then the downstream node device C performs compression, and then the HOP flag = 0. At this time, the guide SID of the G-SID is also the SID of the node A, and the complete information of the G-SID is recovered by using the SID of the COC Flavor carried by the node A.

In one embodiment, the start of a segment of the compressed SRv6 path is indicated by a 128-bit COC _ Flaver SID and HOP _ Flaver SID, which contains the COC _ Flaver G-SID and the HOP Value. The SID carries complete SID information, including Common Prefix information, which can be used to recover the complete next SID from the subsequent G-SID skipping the HOP Value 128-bit SID.

The G-SIDs in the compression path each carry COC and HOP's G-SIDs, indicating that the SID skipping the HOP Value number is a 32-bit G-SID.

The last G-SID of the compression path may be a 32-bit G-SID without COC _ Flavor to indicate the end of the compression path. The SRv6 SIDs that it assembles into in the DA are processed according to the processing rules of 128-bit SIDs.

In this embodiment, when the target node device is used as a guiding device to send the first packet, it is necessary to acquire which downstream node devices in each downstream node device do not support compression (that is, it is necessary to hop those downstream node devices).

In one mode, a target node device receives a second message sent by each downstream node device, wherein the second message carries a second identifier indicating whether the second message supports SRv6 hybrid compression capability;

In this embodiment, the target node device may calculate the number of hops to reach a downstream node device when knowing that a certain downstream node device does not support the SRv6 hybrid compression capability after receiving the notification message, thereby obtaining the first identifier.

In another embodiment, when a controller exists in a network, a target node device acquires, from the controller, a target downstream node device that does not support SRv6 hybrid compression in each downstream node device, and generates a first identifier according to the acquired hop count from the target downstream node device to the target downstream node device;

In this embodiment, an SRv6 compression scheme is deployed, address planning needs to be performed, and the control plane and the data plane need to be upgraded to support SRv6 compression. After IGP and BGP are configured, the capability of supporting node compression needs to be released, so protocols such as ISIS, BGP-LS, BGP-Policy and the like need to be expanded, and the expansion condition of the HOP Flavor in a control plane is mainly described in the section.

After SRv6 SID deployment is completed, SRv6 SID planning and configuration are required to be completed, a node generates a local SID table according to the configuration, and then SID is issued to a network through an IGP protocol. Therefore, it is necessary to extend an 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:

expanding SRv6Capabilities sub-TLV, adding H-Flag, and enabling the advertising node to support the capability of skipping a plurality of unsupported nodes to compress the next node, namely the capability of skipping the transmission of COC (code of control) Flag compression information

The method comprises the steps that an O-flag is defined in draft-ietf-lsr-is-SRv 6-extensions-17, a C-flag is defined in SRv6 compression capacity of a mark node, an H-flag is defined in the invention (bit of index 3 is used as H-flag), and when the H-flag is set to be 1, the mark node is used for marking the SRv6 jump compression capacity of the mark node, wherein the current node has the capacity of jumping and transmitting COC flag compression information. When the H-Flag is set, the C-Flag must be set, and only the message with the H-Flag set and the C-Flag unset needs to ignore the H-Flag.

An SDN controller or node that does not support skip compression should ignore the H-Flag when it receives the SRv6Capabilities sub-TLV of the extended H-Flag.

The SRv6 hop compression capability of a node may be reported to the SDN controller via BGP-LS. When calculating the SRv6 TE path, the SDN controller arranges the SID list according to the hop compression capability of the node. The H-Flag may also be used when a node computes a way.

If the head node does not report SRv6 hop compression capability, then the SDN controller should not issue a SRv6 Policy containing H-G-SID to the head node. If indeed it is to be delivered, it can only contain SIDs without HOP Flavor.

And the SRv6 END SID sub-TLV, the SRv6 end.X SID sub-TLV and the SRv6 LAN end.X SID sub-TLV are expanded to increase an H-flag identification SID to support jump compression.

The premise of setting the H-flag is that the C-flag must be set, and when the H-flag is set, SRv6 SID Structure Sub-Sub-TLVs need to be carried. Length is used to indicate how many nodes need to be skipped and then compressed (considering the actual networking specification). The name is H.value, and the value range of the current H.value is 0-2 ^4.

When the H-Flag is set, the C-Flag must be set, and only the message with the H-Flag set and the C-Flag not set needs to omit the H-Flag. If H-flag =1 and carries SRv6 SID Structure Sub-TLV, the SID in SRv6 End Sub-TLV is considered as a skip compression SID; if only the H-flag is set but the SRv6 SID Structure Sub-TLV is not carried, omitting the H-flag and the C-flag, and determining the SID as a non-compressed SID; if the Behavior of the SID is the Behavior carrying the HOP flag, the H-flag must be set, the SRv6 SID Structure Sub-TLV must be carried, otherwise, the SID is determined to be an illegal SID and needs to be discarded; if only C-flag is carried and H-flag is not carried, the SID is determined to be a compressed SID without skip compression capability. When a node which does not support HOP compression receives an unsupported Endpoint bearer, such as the SID of an HOP bearer, the TLV associated with the SID is directly ignored, but still distributed to other nodes.

Firstly, in the process of issuing the IGP capability, the node identifies that the node supports the jump compression capability by setting an extension H-flag of an SRv6Capabilities TLV.

To support SRv6 compression requires that the corresponding SID be instantiated and published into the network or uploaded to the controller via IGP or like protocols. When the node instantiates the SID, a corresponding SID forwarding table entry is generated.

When the SID is issued, H-flag in TLV (such as SRv6 End SID sub-TLV, SRv6 end.x SID sub-TLV, SRv6 LAN end.x SID sub-TLV) corresponding to the SID needs to be set to identify that the format of the SID supports jump compression.

The issued SID has a HOP flag, and identifies the H-SID or the compressed H-G-SID skips over the SIDs of H.value SIDs for compression.

The BGP-LS protocol may be used for the SRv6 related information [ draft-ietf-idr-bgpls-SRv6-ext-08] described above. The method is used for supporting the report of the SRv6 optimized SID state based on draft-ietf-idr-bgpls-SRv6-ext-08 document extension.

In order to realize the TE path calculation, the controller needs to know the topology information of the whole network, TE attribute and SR attribute of the topology. The controller may collect network topology information via the BGP-LS protocol. To support SRv6 jump compression, three types of information need to be extended.

And (3) expanding the SRv6Capabilities TLV, adding an H-flag, and enabling the advertising node to support the jump compression capability. When the H-Flag is set, the C-Flag must be set, and only the message with the H-Flag set and the C-Flag unset needs to ignore the H-Flag. When the H-flag is set to 1, it indicates that "the current node has SRv6 skip compression capability", and is used to flag the SRv6 skip compression capability of the node. When an SDN controller or a node which does not support jump compression receives the SRv6Capabilities TLV of the extended H-flag, the H-flag is omitted. The SRv6 compression capacity of the node is reported to the SDN controller through BGP-LS, and the SDN controller can program SID list according to the compression capacity of the node when calculating the SRv6 TE path.

And expanding the SRv6 end.X SID TLV under the SRv6 Link Attributes, and adding an H-flag identification SID to support jump compression.

And expanding an End Behavior sub-TLV corresponding to the Node SID, adding an H-flag, and identifying and supporting jump compression. BGP-LS information comes from IGP, where the H-flag extension logic is extended from IGP.

When BGP-LS connection is established, if the node supports SRv6 jump compression, the H-flag in the SRv6Capabilities TLV needs to be set. Nodes can upload SID information supporting hop compression to the controller via BGP-LS. When sending the SIDs, the H-flag needs to be set in the SRv6 end.X TLV, the SRv6 LAN end.X SID TLV and the SRv6 Endpoint Behavior TLV corresponding to the SIDs, so as to completely describe the SIDs. SRv6 SID Structure TLV needs to be carried when H-flag is set, where h.vlaue is used to describe the number of hops for a hop.

Through the above embodiments, when some nodes in the middle cannot be compressed, only the current node is not compressed, and the compression state of the next node is not affected, that is, if the next node is a SID supporting compression, compression may also be performed, that is, jump compression may be supported.

As shown in fig. 4, with the scheme in the present disclosure, a, C, and D are all nodes supporting compression, and B1 and B2 do not support compression, according to the conventional compression scheme, the previous hop B2 of the device C does not support compression, i.e. the SID of the node cannot carry COC marker, so that the SID of the node C cannot be compressed either. After the invention is adopted, the node A can carry the HOP flag to indicate that the H.value jump is skipped and then the compression is carried out, namely, the node C can utilize the information in the COC flag of the node A to carry out the compression, thereby improving the compression efficiency under the mixed editing mode.

As shown in fig. 5, an embodiment of the present disclosure further provides a method for SRv6 hybrid compression, where the method includes:

s501, the target node equipment determines target downstream node equipment which does not support SRv6 mixed coding compression in each downstream node equipment according to a second identifier in a second message sent from each downstream node equipment, and obtains the hop count of the target downstream node equipment when the target node equipment reaches the target downstream node equipment;

s502, generating a first identifier according to the hop count, and sending a first message carrying the first identifier to downstream node equipment of a next hop;

s503, the downstream node device receiving the first packet obtains the first identifier, if the hop count carried in the first identifier is 0, the downstream node device receiving the first packet executes SRv6 hybrid coding compression, and if the hop count carried in the first identifier is a and a is not 0, it indicates that the SRv6 hybrid coding compression is executed after skipping a number of downstream node devices.

By the method, when a certain node can not be compressed, only the current node is not compressed, and the compression state of the next node can not be influenced, namely if the next node is the SID supporting compression, the next node can also be compressed. Thereby improving the compression performance in the hybrid mode.

Based on the foregoing method embodiments, an embodiment of the present disclosure further provides a node device, where the node device includes:

a sending module, configured to send a first packet carrying a first identifier to a downstream node device, so that the downstream node device performs SRv6 hybrid coding compression or does not perform the SRv6 hybrid coding compression according to the first identifier.

Wherein the node device further comprises:

the receiving module is used for receiving a second message sent by each downstream node device, wherein the second message carries a second identifier indicating whether the second message supports SRv6 mixed coding compression capability or not;

The sending module is specifically configured to obtain, according to the second packet sent by each downstream node device, a target downstream node device that does not support SRv6 hybrid compression, generate a first identifier according to the obtained hop count from the sending module to the target downstream node device, and send, to the downstream node device, a first packet carrying the first identifier.

Wherein the node device further comprises:

the receiving module is used for acquiring target downstream node equipment which does not support SRv6 hybrid coding compression in each downstream node equipment from the controller, and generating a first identifier according to the acquired hop count from the receiving module to the target downstream node equipment;

An embodiment of the present disclosure further provides a network system, where the network system includes: target node device and downstream node device:

The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.

Other embodiments of the present description will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.

It will be understood that the present description is not limited to the precise arrangements described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

The above description is only a preferred embodiment of the present disclosure, and should not be taken as limiting the present disclosure, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present disclosure should be included in the protection scope of the present disclosure.

Claims

1. A method of SRv6 hybrid compression, the method comprising:

2. The method according to claim 1, wherein before the target node device sends the first packet carrying the first identifier to the downstream node device, the method further comprises:

3. The method according to claim 2, wherein the sending, by the target node device, the first packet carrying the first identifier to the downstream node device includes:

the target node equipment acquires target downstream node equipment which does not support SRv6 mixed coding compression according to the second message sent by each downstream node equipment, and generates a first identifier according to the hop count from the target node equipment to the target downstream node equipment;

4. The method according to claim 1, wherein before the target node device sends the first packet carrying the first identifier to the downstream node device, the method further comprises:

5. A method for SRv6 hybrid compression, the method comprising:

the target node equipment determines target downstream node equipment which does not support SRv6 mixed coding compression in each downstream node equipment according to a second identifier in a second message sent from each downstream node equipment, and obtains hop count of the target downstream node equipment;

and the downstream node equipment receiving the first message acquires the first identifier, if the hop count carried in the first identifier is 0, the downstream node equipment receiving the first message executes SRv6 mixed encoding compression, and if the hop count carried in the first identifier is A and A is not 0, the downstream node equipment skipping A downstream node equipment executes SRv6 mixed encoding compression.

6. A node apparatus, characterized in that the node apparatus comprises:

7. The node device of claim 6, wherein the node device further comprises:

and the identification module is used for determining whether each piece of downstream node equipment supports SRv6 hybrid coding compression or not according to the second identifier.

8. The node apparatus of claim 7,

9. The node device of claim 6, wherein the node device further comprises:

10. A network system, characterized in that the network system comprises: target node device and downstream node device:

the target node equipment determines target downstream node equipment which does not support SRv6 mixed coding compression in each downstream node equipment according to a second identifier in a second message sent from each downstream node equipment, and obtains the hop count of the target downstream node equipment when the target node equipment reaches the target downstream node equipment;

and the downstream node equipment which receives the first message acquires the first identifier, if the hop count carried in the first identifier is 0, the downstream node equipment which receives the first message executes SRv6 mixed coding compression, and if the hop count carried in the first identifier is A and A is not 0, the downstream node equipment skips A downstream node equipment and then executes SRv6 mixed coding compression.