Communication method, electronic device, and apparatus

Abstract

Embodiments of the present application provide a communication method, an electronic device, and an apparatus. The communication method is applied to a first device that is an electronic device that supports SRv6 in a network, and the method comprises: acquiring an SRv6 Locator of the first device; and sending a first LLDP packet to a second device, wherein the first LLDP packet comprises the SRv6 Locator of the first device, so that, on the basis of the SRv6 Locator of the first device, the second device generates a Locator route to the first device. By applying the embodiments of the present application, SRv6 information advertisement can be performed by means of a simple routing protocol.

Description

A communication method, electronic device and apparatus TECHNICAL FIELD

[0001] The present application relates to the technical field of communication, and in particular to a communication method, electronic device and apparatus. BACKGROUND

[0002] When communication is performed based on SRv6 (Segment Routing Internet Protocol Version 6) technology, SRv6 Locators (Locator) of electronic devices need to be pre-announced between electronic devices in a network. In related technologies, SRv6 Locator can be announced based on IS-IS (Intermediate System to Intermediate System) or OSPFv3 (Open Shortest Path First version 3).

[0003] However, since the protocols of IS-IS and OSPFv3 are relatively complex, electronic devices that do not support complex dynamic routing protocol functions, such as hosts, etc., are difficult to perform SRv6 Locator announcement through the above related technologies. This makes it difficult for such electronic devices to complete SRv6 Locator announcement, and further makes it difficult to perform subsequent SRv6 communication.

[0004] SUMMARY

[0005] Embodiments of the present application aim to provide a communication method, electronic device and apparatus to perform SRv6 Locator announcement through a simple routing protocol. The specific technical solutions are as follows:

[0006] In a first aspect, the embodiments of the present application provide a communication method applied to a first device, the first device being an electronic device supporting SRv6 (Segment Routing Internet Protocol Version 6) in a network, and the method comprising:

[0007] obtaining an SRv6 Locator (Locator) of the first device;

[0008] sending a first LLDP (Link Layer Discovery Protocol) message to a second device, the first LLDP message comprising the SRv6 Locator of the first device, so that the second device generates a Locator route to the first device according to the SRv6 Locator of the first device.

[0009] In an embodiment of the present application, the method further comprises:

[0010] receiving a second LLDP packet sent by a third device, the second LLDP packet comprising an SRv6 Locator of the third device;

[0011] generating, according to the SRv6 Locator of the third device, a Locator route to the third device;

[0012] sending, to a dynamic routing protocol neighbor of the first device, a route advertisement packet based on a dynamic routing protocol, the route advertisement packet comprising the Locator route to the third device.

[0013] In an embodiment of the present application, the second LLDP packet further comprises an SRv6 capability Capbility, and the method further comprises:

[0014] determining, according to the SRv6 capability, a maximum Segment Identifier (SID) stack depth supported by the third device.

[0015] In an embodiment of the present application, the first LLDP packet further comprises an SRv6 capability, and the SRv6 capability is used to enable the second device to determine an SRv6 capability of the first device, the SRv6 capability representing a maximum SID stack depth supported by the first device.

[0016] In an embodiment of the present application, each LLDP packet comprises an SRv6 Locator TLV structure, and the SRv6 Locator TLV structure is used to carry an SRv6 Locator of a device.

[0017] In an embodiment of the present application, the SRv6 Locator TLV structure comprises a value Value field, and the value field comprises a Locator field used to carry an SRv6 Locator of a device.

[0018] The value field further comprises a multi-topology identifier (MTID) field, an expense field, an algorithm field, a Locator length field, and a sub-TLV field.

[0019] The MTID field carries an MTID, the expense field represents a path expense of the SRv6 Locator, the algorithm field represents a path calculation algorithm used by a device, and the Locator length field represents a length of the SRv6 Locator.

[0020] The sub-TLV includes a first sub-TLV and / or a second sub-TLV, the first sub-TLV carries an End SID, the End SID is: a SID pre-allocated by the device under the SRv6 Locator; and the second sub-TLV carries a management label.

[0021] In an embodiment of the present application, each LLDP packet further includes an SRv6 Capbility TLV structure, the SRv6 Capbility TLV structure is used to carry the SRv6 capability.

[0022] In an embodiment of the present application, the SRv6 Capbility TLV structure includes a value field, the value field includes an optional sub-TLV,

[0023] The optional sub-TLV includes a type field and a length field, the type field carries the type of the maximum label stack depth MSD supported by the device, and the length field carries the MSD value, the MSD value represents the maximum number of SIDs allowed to be carried in the packet generated by the device.

[0024] In a second aspect, embodiments of the present application provide an electronic device, the electronic device is a device supporting Internet Protocol version 6 segment routing SRv6 in a network, and the electronic device includes:

[0025] a processor;

[0026] a transceiver;

[0027] a machine readable storage medium, the machine readable storage medium stores machine executable instructions capable of being executed by the processor; the machine executable instructions cause the processor to perform the following steps:

[0028] obtain an SRv6 Locator of the first device;

[0029] send a first link layer discovery protocol LLDP packet to a second device, the first LLDP packet includes the SRv6 Locator of the first device, so that the second device generates a Locator route to the first device according to the SRv6 Locator of the first device.

[0030] In an embodiment of the present application, the machine executable instructions further cause the processor to perform the following steps:

[0031] receive a second LLDP packet sent by a third device, the second LLDP packet includes an SRv6 Locator of the third device;

[0032] generating, according to the SRv6 Locator of the third device, a Locator route to the third device;

[0033] sending, based on a dynamic routing protocol, a route advertisement packet to a dynamic routing protocol neighbor of the first device, the route advertisement packet including the Locator route to the third device.

[0034] In an embodiment of the present application, the second LLDP packet further includes an SRv6 capability Capbility, and the machine executable instructions further cause the processor to perform the following steps:

[0035] determining, according to the SRv6 capability, a maximum Segment Identifier (SID) stack depth supported by the third device.

[0036] In an embodiment of the present application, the first LLDP packet further includes an SRv6 capability, and the SRv6 capability is used to cause the second device to determine an SRv6 capability of the first device, the SRv6 capability indicating a maximum SID stack depth supported by the first device.

[0037] In an embodiment of the present application, each LLDP packet includes an SRv6 Locator TLV structure, and the SRv6 Locator TLV structure is used to carry an SRv6 Locator of a device.

[0038] In an embodiment of the present application, the SRv6 Locator TLV structure includes a value Value field, and the Value field includes a Locator field used to carry an SRv6 Locator of a device;

[0039] The Value field further includes a multi-topology identifier (MTID) field, an expense field, an algorithm field, a Locator length field, and a sub-TLV field.

[0040] The MTID field carries an MTID, the expense field indicates a path expense of the SRv6 Locator, the algorithm field indicates a path calculation algorithm used by a device, and the Locator length field indicates a length of the SRv6 Locator.

[0041] The sub-TLV includes a first sub-TLV and / or a second sub-TLV, the first sub-TLV carries an end SID, and the end SID is a SID pre-allocated by the device under the SRv6 Locator; and the second sub-TLV carries a management label.

[0042] In an embodiment of the present application, each of the LLDP packets further comprises an SRv6 Capbility TLV structure, which is used to carry the SRv6 capability.

[0043] In an embodiment of the present application, the SRv6 Capbility TLV structure comprises a value field, which comprises an optional sub-TLV,

[0044] The optional sub-TLV comprises a type field and a length field, the type field carries the type of the maximum label stack depth MSD supported by the device, and the length field carries the MSD value, which represents the maximum number of SIDs allowed to be carried in the packet generated by the device.

[0045] In a third aspect, embodiments of the present application provide a communication apparatus applied to a first device, the first device being an electronic device supporting Segment Routing version 6 (SRv6) in a network, and the apparatus comprising:

[0046] a Locator obtaining module configured to obtain an SRv6 Locator of the first device;

[0047] a first packet sending module configured to send a first Link Layer Discovery Protocol (LLDP) packet to a second device, the first LLDP packet comprising the SRv6 Locator of the first device, so that the second device generates a Locator route to the first device according to the SRv6 Locator of the first device.

[0048] In an embodiment of the present application, the apparatus further comprises:

[0049] a packet receiving module configured to receive a second LLDP packet sent by a third device, the second LLDP packet comprising an SRv6 Locator of the third device;

[0050] a route generating module configured to generate a Locator route to the third device according to the SRv6 Locator of the third device;

[0051] a second packet sending module configured to send a route advertisement packet to a dynamic routing protocol neighbor of the first device based on a dynamic routing protocol, the route advertisement packet comprising the Locator route to the third device.

[0052] In an embodiment of the present application, the second LLDP packet further comprises an SRv6 Capbility, and the apparatus further comprises:

[0053] A maximum SID determination module is configured to determine, according to the SRv6 capability, a maximum Segment Identifier (SID) stack depth supported by the third device.

[0054] In an embodiment of the present application, the first LLDP packet further comprises an SRv6 capability, and the SRv6 capability is used to enable the second device to determine the SRv6 capability of the first device, and the SRv6 capability represents the maximum SID stack depth supported by the first device.

[0055] In an embodiment of the present application, each LLDP packet comprises an SRv6 Locator TLV structure, and the SRv6 Locator TLV structure is used to carry the SRv6 Locator of a device.

[0056] In an embodiment of the present application, the SRv6 Locator TLV structure comprises a value field, and the value field comprises a Locator field used to carry the SRv6 Locator of a device.

[0057] The value field further comprises a multi-topology identifier (MTID) field, an overhead field, an algorithm field, a Locator length field, and a sub-TLV field.

[0058] The MTID field carries an MTID, the overhead field represents the path overhead of the SRv6 Locator, the algorithm field represents the path calculation algorithm used by a device, and the Locator length field represents the length of the SRv6 Locator.

[0059] The sub-TLV comprises a first sub-TLV and / or a second sub-TLV, the first sub-TLV carries an end SID, and the end SID is a SID pre-allocated by the device under the SRv6 Locator, and the second sub-TLV carries a management label.

[0060] In an embodiment of the present application, each LLDP packet further comprises an SRv6 Capbility TLV structure, and the SRv6 Capbility TLV structure is used to carry the SRv6 capability.

[0061] In an embodiment of the present application, the SRv6 Capbility TLV structure comprises a value field, and the value field comprises an optional sub-TLV,

[0062] The optional sub-TLV includes a type field and a length field, the type field carries a type of a maximum label stack depth MSD supported by a device, and the length field carries an MSD value, the MSD value represents a maximum number of SIDs allowed to be carried in a packet generated by the device.

[0063] In a fourth aspect, an embodiment of the present application provides a machine readable storage medium, which stores machine executable instructions, when the machine executable instructions are invoked and executed by a processor, the machine executable instructions cause the processor to implement the method in any of the first aspect.

[0064] In a fifth aspect, an embodiment of the present application provides a computer program product, which causes a processor to implement the method in any of the first aspect.

[0065] The embodiment of the present application has the following beneficial effects:

[0066] In the embodiment of the present application, the first device advertises the SRv6 Locator to the second device through the first LLDP packet, so that the second device generates a Locator route to the first device according to the SRv6 Locator of the first device. Since the first LLDP packet is a packet sent based on the LLDP protocol, the complexity of the LLDP protocol is low. Most electronic devices, even electronic devices that do not support the function of a complex dynamic routing protocol, have configured the LLDP protocol and can send the LLDP packet based on the LLDP protocol. Therefore, the scheme provided in the embodiment of the present application can complete the advertisement of the SRv6 Locator through the LLDP packet, and then enable the first device to perform SRv6 communication after the SRv6 Locator is advertised. BRIEF DESCRIPTION OF DRAWINGS

[0067] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other embodiments can also be obtained from these drawings without creative labor.

[0068] FIG. 1 is a schematic diagram of an application scenario provided by an embodiment of the present application;

[0069] FIG. 2 is a flowchart of a first communication method provided by an embodiment of the present application;

[0070] FIG. 3 is a flowchart of a second communication method provided by an embodiment of the present application;

[0071] FIG. 4 is a flowchart of a third communication method provided by an embodiment of the present application;

[0072] FIG. 5 is a schematic diagram of an SRv6 Locator TLV provided by an embodiment of the present application;

[0073] FIG. 6 is a schematic diagram of a second sub-TLV provided by an embodiment of the present application;

[0074] FIG. 7 is a schematic diagram of an SRv6 Capbility TLV provided by an embodiment of the present application;

[0075] FIG. 8 is a schematic diagram of a third sub-TLV provided by an embodiment of the present application;

[0076] FIG. 9 is a schematic diagram of an LLDP packet provided by an embodiment of the present application;

[0077] FIG. 10 is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application;

[0078] FIG. 11 is a schematic diagram of the structure of a communication apparatus provided by an embodiment of the present application. DETAILED DESCRIPTION

[0079] The technical solutions in the embodiments of the present application will be described clearly and completely below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only some of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of the present application.

[0080] In order to describe the problems in the related art, first, an application scenario of an embodiment of the present application is described.

[0081] Referring to FIG. 1, it is a schematic diagram of an application scenario provided by an embodiment of the present application.

[0082] The diagram includes host 1, host 2, leaf node, spine node, and core device. The leaf node and the spine node in the diagram form a Spine-Leaf network structure.

[0083] If the host 1 and the host 2 in the diagram use the dynamic routing protocol such as IGP (Interior Gateway Protocol) or BGP (Border Gateway Protocol) in the related art to advertise the SRv6 Locator, the IGP or BGP needs to be configured on the host 1 and the host 2. However, the dynamic routing protocol such as IGP and BGP is relatively complex, the host 1 and the host 2 do not support the SRv6 Locator advertisement based on the dynamic routing protocol, which further causes the host 1 and the host 2 to be difficult to perform subsequent SRv6 communication.

[0084] In addition to the host 1 and the host 2, other devices can support complex dynamic routing protocols, and thus the other devices can advertise SRv6 Locator based on IGP or BGP.

[0085] However, it should be noted that since electronic devices capable of supporting complex dynamic routing protocols can theoretically support simple routing protocols, theoretically, various electronic devices (such as all electronic devices in FIG. 1) can advertise SRv6 Locator by using the scheme provided in the embodiments of the present application.

[0086] In addition, in a network, all devices can uniformly use the scheme provided in the embodiments of the present application to advertise SRv6 Locator. For example, all devices in FIG. 1 can use the scheme provided in the embodiments of the present application to advertise SRv6 Locator. Alternatively, only part of the devices use the scheme provided in the embodiments of the present application to advertise SRv6 Locator, and other devices advertise SRv6 Locator by other means. For example, the host 1 and the host 2 in FIG. 1 use the scheme provided in the embodiments of the present application to advertise SRv6 Locator, and other devices advertise SRv6 Locator by using dynamic routing protocols such as IGP or BGP.

[0087] Furthermore, the embodiments of the present application are applicable to electronic devices in various network structures. The network structures include ring network topology, Spine-Leaf network structure shown in FIG. 1, and the like.

[0088] The communication method provided in the embodiments of the present application is described below.

[0089] Referring to FIG. 2, it is a flowchart of a first communication method provided in the embodiments of the present application, which is applied to a first device, and the first device is an electronic device supporting SRv6 in a network, and includes the following steps S201-S202. Before performing the steps S201-S202, the first device first enables LLDP, so that the first device can send LLDP packets in the future.

[0090] S201: Obtain the SRv6 Locator of the first device.

[0091] S202: Send a first LLDP packet to a second device, and the first LLDP packet includes the SRv6 Locator of the first device, so that the second device generates a Locator route to the first device according to the SRv6 Locator of the first device.

[0092] Since the first LLDP packet contains the SRv6 Locator of the first device, the second device can learn the SRv6 Locator of the first device.

[0093] As can be seen from the above, in the embodiment of the application, the first device advertises the SRv6 Locator to the second device through the first LLDP packet, so that the second device generates the Locator route to the first device according to the SRv6 Locator of the first device. Since the first LLDP packet is a packet sent based on the LLDP protocol, the complexity of the LLDP protocol is low. Most electronic devices, even those that do not support the function of complex dynamic routing protocol, have configured the LLDP protocol and can send the LLDP packet based on the LLDP protocol. Therefore, the scheme provided in the embodiment of the application can complete the advertisement of the SRv6 Locator through the LLDP packet, and then the first device can perform SRv6 communication after advertising the SRv6 Locator.

[0094] Referring to FIG. 3, a flowchart of a second communication method provided in the embodiment of the application includes the following steps S301-S303.

[0095] S301: receiving a second LLDP packet sent by a third device.

[0096] The second LLDP packet includes the SRv6 Locator of the third device.

[0097] S302: generating a Locator route to the third device according to the SRv6 Locator of the third device.

[0098] Specifically, in addition to performing the foregoing steps S201-S202, the first device will also receive the second LLDP packet sent by the third device and generate the Locator route to the third device.

[0099] S303: sending a route advertisement packet to a dynamic routing protocol neighbor of the first device based on the dynamic routing protocol.

[0100] The route advertisement packet includes the Locator route to the third device.

[0101] Specifically, if the first device supports the dynamic routing protocol, after generating the Locator route to the third device, step S303 can be performed to send the route advertisement packet to the dynamic routing protocol neighbor of the first device, so that the dynamic routing protocol neighbor can also generate the Locator route to the third device. The dynamic routing protocol neighbor also supports the dynamic routing protocol.

[0102] Taking the network structure shown in FIG. 1 as an example, if the first device is a spine node and the third device is a core device. The spine node receives the second LLDP packet sent by the core device, generates the Locator route to the core device, and then sends the route advertisement packet to the leaf node as the dynamic routing protocol neighbor.

[0103] Alternatively, if the first device is a leaf node and the third device is a host 1 or a host 2 (hereinafter collectively referred to as a host). The leaf node receives the second LLDP packet sent by the host, generates the Locator route to the host, and then sends the route advertisement packet to the spine node as the dynamic routing protocol neighbor.

[0104] In addition, if the first device does not support the dynamic routing protocol, step S303 can not be performed, and the Locator route learned by the first device to the third device can be announced to other devices through the LLDP packet provided by the embodiment of the present application.

[0105] As can be seen from the above, in the scheme provided by the embodiment of the present application, the first device can not only announce its SRv6 Locator to the second device through the first LLDP packet, but also receive the second LLDP packet sent by the third device to generate the Locator route to the third device. That is, the first device can complete the bidirectional SRv6 Locator interaction between the LLDP packet and other devices.

[0106] Referring to FIG. 4, it is a flowchart of a third communication method provided by the embodiment of the present application. Compared with the embodiment shown in FIG. 2, the second LLDP packet further includes an SRv6 Capbility (capability), which is used to inform the receiving end of the maximum SID stack depth of the sending end. The above method further includes the following step S203.

[0107] S203: Determine the maximum SID stack depth supported by the third device according to the SRv6 Capbility.

[0108] Specifically, the SRv6 Capbility includes the maximum SID stack depth supported by the third device. In addition, other information indicating the SRv6 packet capability of the third device can also be included. For details, please refer to the definition of SRv6 Capbility in related technologies, which will not be described here.

[0109] In addition, it should be noted that the third device can synchronously send the SRv6 Capbility and the SRv6 Locator in the second LLDP packet, or send the SRv6 Capbility to the first device through a third LLDP packet different from the second LLDP packet.

[0110] As can be seen from the above, in the scheme provided by the embodiments of the present application, the second LLDP packet sent by the third device to the first device can further contain the SRv6 Capbility, so that the first device can determine the maximum SID stack depth supported by the third device. That is, in the electronic device of the embodiments of the present application, not only can the SRv6 Locator be transmitted through the simple LLDP packet, but also the transmission of the SRv6 Capbility can be realized.

[0111] In one example, in the application scenario shown in FIG. 1, the host 1 sends the first LLDP packet to the leaf node by using the scheme provided by the embodiments of the present application, the leaf node generates the Locator route to the host 1. The leaf node sends the route advertisement packet to the spine node, and the spine node generates the Locator route to the host 1. Then, the spine node can further send the route advertisement packet to the core device, and the core device generates the Locator route to the host 1.

[0112] On this basis, the host 1 sends the SRv6 Locator FC00:0:11:: / 48 to the leaf node through the LLDP packet, and advertises the SRv6 Capbility.

[0113] The host 2 sends the SRv6 Locator FC00:0:12:: / 48 to the leaf node through the LLDP packet, and advertises the SRv6 Capbility.

[0114] The leaf node generates the Locator route FC00:0:11:: / 48 to the host 1 and the Locator route FC00:0:12:: / 48 to the host 2 through the LLDP, and determines the maximum SID stack depth of the host 1 and the host 2.

[0115] The leaf node sends the Locator route of the host 1 and the host 2 generated through the LLDP, and the maximum SID stack depth of the host 1 and the host 2 to the spine node through the IGP or the BGP.

[0116] The spine node generates the Locator route to the host 1 and the host 2 through the IGP or the BGP, and determines the maximum SID stack depth to the host 1 and the host 2.

[0117] The spine node sends the Locator route of the host 1 and the host 2 generated through the IGP or the BGP, and the maximum SID stack depth of the host 1 and the host 2 to the core device through the IGP or the BGP.

[0118] The core device generates Locator routes to host 1 and host 2 through IGP or BGP, and determines the maximum SID stack depth to host 1 and host 2.

[0119] This process is only a one-way route generation process for host 1 and host 2 to the core device, and the route generation process of the core device to host 1 and host 2 will not be described.

[0120] In an embodiment of the present application, the first LLDP packet further includes SRv6 Capbility, and the SRv6 Capbility is used to determine the SRv6 capability of the first device by the second device, and the SRv6 capability represents the maximum SID stack depth supported by the first device.

[0121] Similar to the SRv6 Capbility carried in the second LLDP packet, the first LLDP packet sent by the first device to the second device can also carry the SRv6 Capbility. In addition, the SRv6 Capbility sent by the first device to the second device can be included in the first LLDP packet together with the SRv6 Locator, or can be included in the fourth LLDP packet separately.

[0122] In an embodiment of the present application, each LLDP packet includes an SRv6 Locator TLV (Type Length Value) structure, and the SRv6 Locator TLV structure is used to carry the SRv6 Locator of the device.

[0123] In another embodiment of the present application, the SRv6 Locator TLV structure includes a Value field, and the Value field includes a Locator field, and the Locator field is used to carry the SRv6 Locator of the device.

[0124] The Value field further includes an MTID (Multi-Topology Identifier) field, a Metric field, an Algorithm field, a Loc Size field, and a sub-TLV field.

[0125] The MTID field carries an MTID, which is used to identify different topologies. In a point-to-point network, two electronic devices on a link can form an adjacency relationship only if they have the same MTID.

[0126] The sub-TLV includes a first sub-TLV and / or a second sub-TLV. The first sub-TLV carries an End SID, which is a SID pre-assigned to the device under the SRv6 Locator. The second sub-TLV carries an administrative tag.

[0127] In addition, the length of the Type field in the SRv6 Locator TLV structure can be a preset fixed length, such as 8 bits, 16 bits, etc.

[0128] The length of the Length field in the SRv6 Locator TLV structure can be a preset fixed length, such as 8 bits, 16 bits, etc.

[0129] The SRv6 Locator TLV structure can further include an R field, which is a reserved field.

[0130] The length of the MTID field can be a preset fixed length, such as 12 bits, 16 bits, etc.

[0131] The length of the cost field can be a preset fixed length, such as 32 bits, 48 bits, etc.

[0132] The length of the algorithm field can be a preset fixed length, such as 8 bits, 16 bits, etc. Different values of the algorithm field correspond to different algorithms. For example, a value of 0 indicates that the path calculation algorithm is a shortest path algorithm (Shortest Path First), a value of 1 indicates that the path calculation algorithm is a strict shortest path algorithm (Strict Shortest Path First), etc.

[0133] The length of the Locator length field can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0134] The Locator field is of variable length.

[0135] The sub-TLV field is of variable length.

[0136] In addition, the Value field of the SRv6 Locator TLV structure can further include at least one of the following fields: an R field, which is a reserved idle field.

[0137] a Flags field. The Flags field can be a reserved field, and the length of the Flags field can be a preset fixed length, such as 8 bits, 12 bits, or the like.

[0138] a sub-TLV len field. The sub-TLV len field records the length of the sub-TLV. The length of the sub-TLV len field can be a preset fixed length, such as 8 bits, 12 bits, or the like.

[0139] Referring to FIG. 5, it is a schematic diagram of an SRv6 Locator TLV structure provided by an embodiment of the present application.

[0140] Each rectangle in the figure represents a field, and the detailed description of each field can be referred to the above, which will not be repeated here.

[0141] In addition, the length of the first sub-TLV can be a preset fixed length, such as 32 bits, 48 bits, or the like. The Value field in the first sub-TLV records an End SID (Segment Identification).

[0142] The length of the second sub-TLV can be a preset fixed length, such as 32 bits, 48 bits, or the like. The Value field in the second sub-TLV records a management label.

[0143] Different management labels are used for different routes, and in the process of introducing cross-domain Locator routes to each other, the management label is set for the Locator route, and then the management label is matched in the routing policy, and the Locator route with repeated management labels is filtered, which can prevent the problem of routing loop.

[0144] In another embodiment of the present application, the second sub-TLV further includes a Type field and a Length field.

[0145] The length of the Type field can be a preset fixed length, such as 8 bits, 12 bits, or the like.

[0146] The length of the Length field can be a preset fixed length, such as 8 bits, 12 bits, or the like.

[0147] Referring to FIG. 6, it is a schematic diagram of a second sub-TLV provided by an example of the present application.

[0148] Each rectangle in the figure represents a field, and detailed descriptions of the fields can be found above and will not be repeated here.

[0149] In one embodiment of the present application, each LLDP packet further comprises an SRv6 Capbility TLV structure, and the SRv6 Capbility TLV structure is used to carry the SRv6 Capbility.

[0150] In one embodiment of the present application, the SRv6 Capbility TLV structure comprises a Value field, and the Value field comprises an optional sub-TLV.

[0151] In addition, the length of the Type field in the SRv6 Capbility TLV structure can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0152] The length of the Length field in the SRv6 Capbility TLV structure can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0153] In addition, the SRv6 Capbility TLV structure can further comprise a reserved Flags field. In one embodiment, the length of the Flags field can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0154] Referring to FIG. 7, it is a schematic diagram of an SRv6 Capbility TLV provided in an embodiment of the present application.

[0155] Each rectangle in the figure represents a field, and detailed descriptions of the fields can be found above and will not be repeated here.

[0156] The optional sub-TLV comprises a Type field and a Length field, the Type field carries the MSD-Type (Maximum SID Depth-Type) supported by the device, the Length field carries the MSD Value, and the MSD Value represents the maximum number of SIDs allowed to be carried in the packet generated by the device.

[0157] The MSD-Type comprises:

[0158] Maximum Segments Left MSD Type (MSD type of maximum remaining segments), indicating the maximum value of the SL (Segment Left) field in the SRH (Segment Routing Header) of the received packet before the SRv6 Endpoint Function instruction associated with the SID is applied.

[0159] Maximum End Pop MSD Type (MSD type of maximum end pop): The maximum number of SIDs that a device supporting PSP (Penultimate Segment Pop of the SRH) or USP (Ultimate Segment Pop of the SRH) can pop.

[0160] Maximum H.Insert MSD Type (MSD type of maximum insertion): When performing the "H.Insert (packet header insertion)" operation to insert SRH information, the maximum number of SIDs allowed to be inserted. If the value is 0, the device cannot perform the "H.Insert" operation.

[0161] Maximum H.Encaps MSD Type (MSD type of maximum encapsulation): The maximum number of SIDs that can be encapsulated into the packet.

[0162] Maximum End D MSD Type (MSD type of maximum end decapsulation): The maximum number of SIDs that the device can decapsulate.

[0163] In the case where multiple MSD types exist, each MSD type corresponds to an MSD value, indicating the value of the MSD of that type.

[0164] The length of the type field can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0165] The length of the length field can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0166] Referring to FIG. 8, an optional sub-TLV provided by an embodiment of the present application is shown.

[0167] Each rectangle in the figure represents a field, and detailed descriptions of the fields can be found in the foregoing, which will not be repeated here. Since the number of MSD types is not fixed, the number of MSD Values and MSD-Types is not fixed, so it is represented by an ellipsis in the figure.

[0168] In another embodiment of the present application, each LLDP packet further comprises a Type field, a Length field, an OUI (Organizationally Unique Identifier) field, and a Subtype field.

[0169] The Type field records the type of the LLDP packet, and the length of the Type field can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0170] The Length field records the length of the LLDP packet, and the length of the Length field can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0171] The OUI field records the OUI of the electronic device sending the LLDP packet.

[0172] The Subtype field indicates the subtype of the LLDP packet, and the length of the Subtype field can be a preset fixed length, such as 8 bits, 12 bits, etc.

[0173] Referring to FIG. 9, it is a schematic diagram of an LLDP packet provided by an embodiment of the present application.

[0174] The OUI and the OUI Continued together constitute a complete OUI field, and the SRv6 Locator TLV and the SRv6 Locator TLV Continued together constitute a complete SRv6 Locator TLV structure. The detailed description of each field in the figure can be referred to the above, and will not be repeated here.

[0175] Corresponding to the foregoing communication method, an embodiment of the present application further provides an electronic device, and the above-mentioned electronic device is a device supporting SRv6 in a network. As shown in FIG. 10, the electronic device comprises:

[0176] a processor 1001;

[0177] a transceiver 1004;

[0178] a machine readable storage medium 1002, which stores machine executable instructions capable of being executed by the processor 1001; the machine executable instructions cause the processor 1001 to execute the following steps:

[0179] obtain an SRv6 locator Locator of the first device;

[0180] The first link layer discovery protocol (LLDP) message is sent to a second device, the first LLDP message including an SRv6 Locator of the first device, such that the second device generates a Locator route to the first device based on the SRv6 Locator of the first device.

[0181] As shown in FIG. 10, the network device can further include a communication bus 1003. The processor 1001, the machine readable storage medium 1002, and the transceiver 1004 can communicate with each other through the communication bus 1003. The communication bus 1003 can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus 1003 can be divided into an address bus, a data bus, a control bus, etc.

[0182] The transceiver 1004 can be a wireless communication module. The transceiver 1004 can interact with other devices to exchange data under the control of the processor 1001.

[0183] The machine readable storage medium 1002 can include a Random Access Memory (RAM) and can further include a Non-Volatile Memory (NVM), such as at least one disk storage. In addition, the machine readable storage medium 1002 can be at least one storage device located remotely from the aforementioned processor.

[0184] The processor 1001 can be a general-purpose processor, including a Central Processing Unit (CPU), a Network Processor (NP), etc. The processor 1001 can also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field-Programmable Gate Array (FPGA), or other programmable logic device, a discrete gate or transistor logic component, a discrete hardware component.

[0185] As can be seen from the above, in the embodiment of the application, the first device advertises the SRv6 Locator to the second device through the first LLDP packet, so that the second device generates the Locator route to the first device according to the SRv6 Locator of the first device. Since the first LLDP packet is a packet sent based on the LLDP protocol, the complexity of the LLDP protocol is low. Most electronic devices, even those that do not support the function of a complex dynamic routing protocol, have configured the LLDP protocol and can send the LLDP packet based on the LLDP protocol. Therefore, the scheme provided in the embodiment of the application can complete the advertisement of the SRv6 Locator through the LLDP packet, and then the first device can perform SRv6 communication after advertising the SRv6 Locator.

[0186] In an embodiment of the application, the machine executable instructions further cause the processor to perform the following steps:

[0187] receiving a second LLDP packet sent by a third device, the second LLDP packet comprising an SRv6 Locator of the third device;

[0188] generating a Locator route to the third device according to the SRv6 Locator of the third device;

[0189] sending a route advertisement packet to a dynamic routing protocol neighbor of the first device based on the dynamic routing protocol, the route advertisement packet comprising the Locator route to the third device.

[0190] As can be seen from the above, in the scheme provided in the embodiment of the application, the first device not only can advertise its own SRv6 Locator to the second device through the first LLDP packet, but also can receive the second LLDP packet sent by the third device and generate the Locator route to the third device. That is, the first device can complete the bidirectional SRv6 Locator interaction with other devices through the LLDP packet.

[0191] In an embodiment of the application, the second LLDP packet further comprises an SRv6 Capbility, and the machine executable instructions further cause the processor to perform the following steps:

[0192] determining a maximum Segment Identifier (SID) stack depth supported by the third device according to the SRv6 Capbility.

[0193] As can be seen from the above, in the scheme provided by the embodiment of the application, the second LLDP packet sent by the third device to the first device can further include the SRv6 Capbility, so that the first device can determine the maximum SID stack depth supported by the third device. That is, in the electronic device of the embodiment of the application, not only can the SRv6 Locator be transmitted through the simple LLDP packet, but also the transmission of the SRv6 Capbility can be realized.

[0194] In an embodiment of the application, the first LLDP packet further includes an SRv6 Capbility, and the SRv6 Capbility is used to enable the second device to determine the SRv6 capability of the first device, the SRv6 capability indicating the maximum SID stack depth supported by the first device.

[0195] In an embodiment of the application, each LLDP packet includes an SRv6 Locator TLV structure, and the SRv6 Locator TLV structure is used to carry the SRv6 Locator of the device.

[0196] In an embodiment of the application, the SRv6 Locator TLV structure includes a value Value field, and the Value field includes a Locator field used to carry the SRv6 Locator of the device.

[0197] The Value field further includes a multi-topology identifier (MTID) field, an overhead field, an algorithm field, a Locator length field, and a sub-TLV field.

[0198] The MTID field carries the MTID, the overhead field indicates the path overhead of the SRv6 Locator, the algorithm field indicates the path calculation algorithm used by the device, and the Locator length field indicates the length of the SRv6 Locator.

[0199] The sub-TLV includes a first sub-TLV and / or a second sub-TLV, the first sub-TLV carries an end SID (End SID), and the End SID is a SID pre-allocated by the device under the SRv6 Locator, and the second sub-TLV carries a management label.

[0200] In an embodiment of the application, each LLDP packet further includes an SRv6 Capbility TLV structure, and the SRv6 Capbility TLV structure is used to carry the SRv6 Capbility.

[0201] In an embodiment of the present application, the SRv6 Capbility TLV structure includes a Value field, and the Value field includes an optional sub-TLV,

[0202] The optional sub-TLV includes a type field and a length field, the type field carries the type of the maximum label stack depth MSD supported by the device, and the length field carries an MSD value, and the MSD value represents the maximum number of SIDs allowed to be carried in a packet generated by the device.

[0203] Corresponding to the foregoing communication method, an embodiment of the present application further provides a communication device.

[0204] Referring to FIG. 11, a structural schematic diagram of a communication device provided by an embodiment of the present application is shown, which is applied to a first device, and the first device is an electronic device supporting SRv6 in a network, and the device includes:

[0205] A Locator obtaining module 1101 is configured to obtain an SRv6 locator Locator of the first device;

[0206] A first packet sending module 1102 is configured to send a first link layer discovery protocol LLDP packet to a second device, and the first LLDP packet includes the SRv6 Locator of the first device, so that the second device generates a Locator route reaching the first device according to the SRv6 Locator of the first device.

[0207] As can be seen from the above, in an embodiment of the present application, the first device advertises the SRv6 Locator to the second device through the first LLDP packet, so that the second device generates the Locator route reaching the first device according to the SRv6 Locator of the first device. Since the first LLDP packet is a packet sent based on the LLDP protocol, the complexity of the LLDP protocol is relatively low. Most electronic devices, even those not supporting the function of a complex dynamic routing protocol, are configured to perform the LLDP protocol and can send the LLDP packet based on the LLDP protocol. Therefore, the scheme provided by the embodiment of the present application can complete the advertisement of the SRv6 Locator through the LLDP packet, and further enable the first device to perform SRv6 communication after advertising the SRv6 Locator.

[0208] In an embodiment of the present application, the device further includes:

[0209] A packet receiving module is configured to receive a second LLDP packet sent by a third device, and the second LLDP packet includes an SRv6 Locator of the third device;

[0210] The route generating module is configured to generate a Locator route to the third device according to the SRv6 Locator of the third device.

[0211] The second packet sending module is configured to send a route advertisement packet to a dynamic routing protocol neighbor of the first device based on a dynamic routing protocol, the route advertisement packet including the Locator route to the third device.

[0212] As can be seen from the above, in the scheme provided by the embodiments of the present application, the first device can not only advertise its SRv6 Locator to the second device through the first LLDP packet, but also receive the second LLDP packet sent by the third device to generate a Locator route to the third device. That is, the first device can complete bidirectional SRv6 Locator interaction with other devices through LLDP packets.

[0213] In an embodiment of the present application, the second LLDP packet further includes an SRv6 Capbility, and the device further includes:

[0214] The maximum SID determining module is configured to determine a maximum segment identifier (SID) stack depth supported by the third device according to the SRv6 Capbility.

[0215] As can be seen from the above, in the scheme provided by the embodiments of the present application, the second LLDP packet sent by the third device to the first device can further include an SRv6 Capbility, so that the first device can determine the maximum SID stack depth supported by the third device. That is, in the embodiments of the present application, the electronic device can not only transmit an SRv6 Locator through a simple LLDP packet, but also implement transmission of an SRv6 Capbility.

[0216] In an embodiment of the present application, the first LLDP packet further includes an SRv6 Capbility, and the SRv6 Capbility is used to make the second device determine an SRv6 capability of the first device, the SRv6 capability representing a maximum SID stack depth supported by the first device.

[0217] In an embodiment of the present application, each LLDP packet includes an SRv6 Locator TLV structure, and the SRv6 Locator TLV structure is used to carry an SRv6 Locator of a device.

[0218] In an embodiment of the present application, the SRv6 Locator TLV structure includes a Value field, and the Value field includes a Locator field used to carry an SRv6 Locator of a device.

[0219] The Value field further includes a multi-topology identification (MTID) field, an overhead field, an algorithm field, a Locator length field, and a sub-TLV field.

[0220] The MTID field carries an MTID, the overhead field represents a path overhead of the SRv6 Locator, the algorithm field represents a path calculation algorithm used by the device, and the Locator length field represents a length of the SRv6 Locator.

[0221] The sub-TLV includes a first sub-TLV and / or a second sub-TLV, the first sub-TLV carries an end SID (End SID), and the End SID is a SID pre-allocated by the device under the SRv6 Locator, and the second sub-TLV carries a management label.

[0222] In an embodiment of the present application, each LLDP packet further includes an SRv6 Capbility TLV structure used to carry the SRv6 Capbility.

[0223] In an embodiment of the present application, the SRv6 Capbility TLV structure includes a Value field, and the Value field includes an optional sub-TLV,

[0224] The optional sub-TLV includes a type field and a length field, the type field carries a type of a maximum label stack depth (MSD) supported by the device, and the length field carries an MSD value, and the MSD value represents a maximum number of SIDs allowed to be carried in a packet generated by the device.

[0225] Based on the same inventive concept, according to the communication method provided in the above embodiments of the present application, a machine-readable storage medium storing machine-executable instructions, when invoked and executed by a processor, causes the processor to implement the steps of any of the communication methods.

[0226] In yet another embodiment provided in the present application, a computer program product including instructions is provided, which, when executed on a computer, causes the computer to perform the steps of any of the communication methods in the above embodiments.

[0227] In the embodiments described above, all or some of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or some of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded into and executed by a computer, all or some of the processes or functions according to the embodiments described in the specification are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media. The available media can be a magnetic medium (for example, floppy disk, hard disk, magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, solid state disk (SSD)) and the like.

[0228] It should be noted that, in this document, the terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between the entities or operations. Moreover, the terms "include", "contain" or any other variants thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed or inherent to such process, method, article or device. Without more limitations, the element defined by the statement "including a" does not exclude the presence of other identical elements in the process, method, article or device including the element.

[0229] Each of the embodiments in the specification is described in a related manner, and the same or similar parts between each of the embodiments can be referred to each other. Each of the embodiments focuses on the difference from other embodiments. In particular, for electronic device, apparatus, computer readable storage medium and computer program product embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the part of the method embodiment.

[0230] The above merely provides the preferred embodiment of the present application, and not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A communication method characterized by comprising: The method is applied to a first device, which is an electronic device supporting Internet Protocol version 6 Segment Routing (SRv6) in a network, and the method comprises: obtaining an SRv6 Locator of the first device; sending a first Link Layer Discovery Protocol (LLDP) packet to a second device, wherein the first LLDP packet comprises the SRv6 Locator of the first device, so that the second device generates a Locator route to the first device according to the SRv6 Locator of the first device.

2. The method of claim 1, wherein, The method further comprises: receiving a second LLDP packet sent by a third device, wherein the second LLDP packet comprises an SRv6 Locator of the third device; generating a Locator route to the third device according to the SRv6 Locator of the third device; sending a route advertisement packet to a dynamic routing protocol neighbor of the first device based on a dynamic routing protocol, wherein the route advertisement packet comprises the Locator route to the third device.

3. The method of claim 2, wherein, The second LLDP packet further comprises an SRv6 Capbility, and the method further comprises: determining a maximum Segment Identifier (SID) stack depth supported by the third device according to the SRv6 Capbility.

4. The method of claim 3, wherein, The first LLDP packet further comprises an SRv6 Capbility, which is used to enable the second device to determine the SRv6 Capbility of the first device, wherein the SRv6 Capbility represents a maximum SID stack depth supported by the first device.

5. The method of claim 2, wherein, Each LLDP packet comprises an SRv6 Locator TLV structure, which is used to carry the SRv6 Locator of a device.

6. The method of claim 5, wherein, The SRv6 Locator TLV structure comprises a Value field, which comprises a Locator field used to carry the SRv6 Locator of the device; The Value field further comprises a Multi-Topology Identifier (MTID) field, an expense field, an algorithm field, a Locator length field, and a sub-TLV field. The MTID field carries an MTID, the expense field represents a path expense of the SRv6 Locator, the algorithm field represents a path calculation algorithm used by the device, and the Locator length field represents a length of the SRv6 Locator; The sub-TLV comprises a first sub-TLV and / or a second sub-TLV, the first sub-TLV carries an End SID, which is a SID pre-allocated by the device under the SRv6 Locator, and the second sub-TLV carries a management label.

7. The method of claim 4, wherein, Each LLDP packet further comprises an SRv6 Capbility TLV structure, which is used to carry the SRv6 Capbility.

8. The method of claim 7, wherein, The SRv6 Capbility TLV structure comprises a Value field, which comprises an optional sub-TLV, The optional sub-TLV includes a type field and a length field, the type field carries the type of a maximum label stack depth MSD supported by a device, and the length field carries an MSD value, the MSD value represents a maximum number of SIDs allowed to be carried in a packet generated by the device.

9. An electronic device, comprising: The electronic device is a device supporting Internet Protocol version 6 segment routing SRv6 in a network, and the electronic device includes: a processor; a transceiver; a machine-readable storage medium storing machine-executable instructions executable by the processor; the machine-executable instructions cause the processor to perform the following steps: obtain an SRv6 locator of the first device; send a first link layer discovery protocol LLDP packet to a second device, the first LLDP packet including the SRv6 locator of the first device, so that the second device generates a Locator route to the first device according to the SRv6 locator of the first device.

10. The electronic device of claim 9, wherein, The machine-executable instructions also cause the processor to perform the following steps: receive a second LLDP packet sent by a third device, the second LLDP packet including an SRv6 locator of the third device; generate a Locator route to the third device according to the SRv6 locator of the third device; send a route advertisement packet to a dynamic routing protocol neighbor of the first device based on a dynamic routing protocol, the route advertisement packet including the Locator route to the third device.

11. The electronic device of claim 10, wherein, The second LLDP packet also includes an SRv6 capability, and the machine-executable instructions also cause the processor to perform the following steps: determine a maximum segment identifier SID stack depth supported by the third device according to the SRv6 capability.

12. The electronic device of claim 11, wherein, The first LLDP packet also includes an SRv6 capability, which is used to enable the second device to determine the SRv6 capability of the first device, the SRv6 capability representing a maximum SID stack depth supported by the first device.

13. The electronic device of claim 10, wherein, Each LLDP packet includes an SRv6 Locator TLV structure for carrying the SRv6 Locator of a device.

14. The electronic device of claim 13, wherein, The SRv6 Locator TLV structure includes a value field, the value field includes a Locator field for carrying the SRv6 Locator of a device; The value field also includes a multi-topology identifier MTID field, an overhead field, an algorithm field, a Locator length field, and a sub-TLV field; The MTID field carries an MTID, the overhead field represents the path overhead of the SRv6 Locator, the algorithm field represents the path calculation algorithm used by the device, and the Locator length field represents the length of the SRv6 Locator; The sub-TLV includes a first sub-TLV and / or a second sub-TLV, the first sub-TLV carries an End SID, the End SID is: a SID pre-allocated by the device under the SRv6 Locator; the second sub-TLV carries a management label.

15. The electronic device of claim 12, wherein, Each LLDP packet further includes an SRv6 Capbility TLV structure, which is used to carry the SRv6 capability.

16. The electronic device of claim 15, wherein, The SRv6 Capbility TLV structure includes a value field, and the value field includes an optional sub-TLV, The optional sub-TLV includes a type field and a length field, the type field carries the type of the maximum label stack depth MSD supported by the device, and the length field carries an MSD value, the MSD value represents the maximum number of SIDs allowed to be carried in the packet generated by the device.

17. A communications device, characterized by The device is applied to a first device, the first device is an electronic device supporting Internet Protocol version 6 segment routing SRv6 in a network, and the device includes: A Locator obtaining module is configured to obtain an SRv6 locator Locator of the first device. A first packet sending module is configured to send a first link layer discovery protocol LLDP packet to a second device, the first LLDP packet includes the SRv6 Locator of the first device, so that the second device generates a Locator route to the first device according to the SRv6 Locator of the first device.

18. The apparatus of claim 17, wherein, The device further includes: A packet receiving module is configured to receive a second LLDP packet sent by a third device, the second LLDP packet includes an SRv6 Locator of the third device. A route generating module is configured to generate a Locator route to the third device according to the SRv6 Locator of the third device. A second packet sending module is configured to send a route advertisement packet to a dynamic routing protocol neighbor of the first device based on a dynamic routing protocol, the route advertisement packet includes the Locator route to the third device.

19. The apparatus of claim 18, wherein, The second LLDP packet further includes an SRv6 capability Capbility, and the device further includes: A maximum SID determining module is configured to determine a maximum segment identifier SID stack depth supported by the third device according to the SRv6 capability.

20. The apparatus of claim 19, wherein, The first LLDP packet further includes an SRv6 capability, which is used to enable the second device to determine the SRv6 capability of the first device, and the SRv6 capability represents the maximum SID stack depth supported by the first device.

21. The apparatus of claim 18, wherein, Each LLDP packet includes an SRv6 Locator TLV structure, which is used to carry the SRv6 Locator of the device.

22. The apparatus of claim 21, wherein, The SRv6 Locator TLV structure includes a value field, and the value field includes a Locator field used for carrying an SRv6 Locator of a device; The value field further includes a multi-topology identifier (MTID) field, an overhead field, an algorithm field, a Locator length field, and a sub-TLV field; The MTID field carries an MTID, the overhead field represents a path overhead of the SRv6 Locator, the algorithm field represents a path calculation algorithm used by the device, and the Locator length field represents a length of the SRv6 Locator; The sub-TLV includes a first sub-TLV and / or a second sub-TLV, the first sub-TLV carries an end SID (End SID), and the End SID is a SID pre-assigned to the device under the SRv6 Locator, and the second sub-TLV carries a management label.

23. The apparatus of claim 20, wherein, Each LLDP packet further includes an SRv6 Capbility TLV structure used for carrying the SRv6 capability.

24. The apparatus of claim 23, wherein, The SRv6 Capbility TLV structure includes a value field, and the value field includes an optional sub-TLV, The optional sub-TLV includes a type field and a length field, the type field carries a type of a maximum label stack depth (MSD) supported by the device, and the length field carries an MSD value representing a maximum number of SIDs allowed to be carried in a packet generated by the device.

25. A machine-readable storage medium, characterized in that, Machine executable instructions are stored, and when called and executed by a processor, the machine executable instructions cause the processor to implement the method of any one of claims 1-8.

26. A computer program product, characterised in that, The computer program product causes the processor to implement the method of any one of claims 1-8.

Images