CN115473840A

CN115473840A - Message issuing method, forwarding path processing method and device

Info

Publication number: CN115473840A
Application number: CN202110656186.6A
Authority: CN
Inventors: 徐国其; 胡志波; 刘国权; 郑娟
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-06-11
Filing date: 2021-06-11
Publication date: 2022-12-13
Also published as: WO2022257854A1

Abstract

The embodiment of the application discloses a message issuing method, a forwarding path processing method and a forwarding path processing device, which are used for saving network resources and improving processing efficiency. The message issuing method comprises the following steps: the method comprises the steps that a first network device obtains state information of a network interface; responding to the change of the state information of the network interface, the first network equipment generates a first message, wherein the first message carries the identifier of the network interface, the changed state information and the slice identifier of a first network slice, and the changed state information indicates the changed state of the network interface belonging to the first network slice; and the first network equipment issues the first message.

Description

Message issuing method, forwarding path processing method and device

Technical Field

The present application relates to the field of communications, and in particular, to a method for issuing a packet, a method for processing a forwarding path, and an apparatus for processing a forwarding path.

Background

A network slicing (network slicing) essentially divides a physical network of an operator into a plurality of virtual networks, and each virtual network is divided according to different service requirements, such as time delay, bandwidth, security, reliability, and the like, so as to flexibly cope with different network application scenarios. The network interface of the network equipment in the network topology is configured with the corresponding network slice, the forwarding path of the virtual network is generated according to the network slice, and the message is forwarded by using the forwarding path, so that the service requirement of the service on the network slice is met.

In the conventional technology, a network device periodically sends information of a network slice configured by its network interface to other devices, so that the other devices know the information and perform corresponding processing. But this approach is more resource consuming and less efficient for the network.

Disclosure of Invention

The embodiment of the application provides a message issuing method, a forwarding path processing method and a forwarding path processing device, which are used for saving network resources and improving processing efficiency.

In a first aspect, a method for issuing a packet is provided, where the method is applied to a first network device, and the method includes the following steps: the first network device obtains status information of the network interface, for example, whether the network interface is configured with a corresponding network slice, whether the network interface fails, and the like. And in response to the change of the state information of the network interface, the first network device generates a first message, wherein the first message carries the identifier of the network interface, the changed state information and the slice identifier of the first network slice. Wherein the changed state information indicates a changed state of the network interface belonging to the first network slice. And the first network equipment issues the first message. Compared with the scheme of periodically releasing the network interface and the configured information of the network slice in the traditional technology, the embodiment of the application only releases the first message carrying the changed state information of the network interface, the identifier of the network interface and the corresponding slice identifier of the first network slice when the state information of the network interface of the first network equipment changes, thereby reducing the number of message releases, avoiding the need of releasing when the periodic timing is finished, saving the release time and improving the processing efficiency of the equipment receiving the first message on the first message.

The change of the state information of the network interface may have the following four possible implementation manners, and the following description is given to the step of generating the first packet by the first network device in combination with the four possible implementation manners.

The implementation mode is as follows: and responding to the network interface newly added configuration of the first network slice, and the first network equipment generates a first message.

The implementation mode two is as follows: and in response to the network interface deleting the configuration of the first network slice, the first network equipment generates a first message.

The implementation mode is three: and responding to the change of the network interface from the normal state to the fault state, the first network equipment acquires the slice identifier of the first network slice, and generates a first message according to the slice identifier of the first network slice.

The implementation mode is four: and responding to the network interface from the fault state to the normal state, the first network equipment acquires the slice identifier of the first network slice, and generates a first message according to the slice identifier of the first network slice.

The above four possible implementations do not constitute a limitation to the technical solution of the present application, and a person skilled in the art can design the implementation according to specific situations.

As a possible design, the First packet is an Intermediate System to Intermediate System (ISIS) packet, an Open Shortest Path First (OSPF) packet, or a Border Gateway Protocol (BGP) packet.

As a possible design, the changed state information and the slice identifier of the first network slice are carried in a Type Length Value (TLV) field of a two-layer Bundle Member attribute (L2 Bundle members Attributes) of the ISIS packet or the OSPF packet.

As a possible design, the L2Bundle Member Attributes TLV field of the ISIS packet includes a two-layer binding Attribute description (L2 Bundle Attribute Descriptors) field, and the changed state information and the slice identifier of the first network slice are carried in the L2Bundle Attribute Descriptors field.

As a possible design, the L2Bundle Member Attributes TLV field of the OSPF packet includes a Member Link attribute (Member Link attribute) subtype length value (sub-TLV) field, and the changed state information and the slice identifier of the first network slice are carried in the Member Link attribute sub-TLV field.

As a possible design, the changed State Information and the slice identifier of the first Network slice are carried in a Network Layer availability Information (NLRI) field of a Link-State (Link-State) of the BGP message.

As a possible design, the Link-State NLRI field includes a Link descriptor (Link Descriptors) field, and the changed State information and the slice identifier of the first network slice are carried in the Link Descriptors field.

As a possible design, the first packet is used to process the forwarding path according to the changed state information of the network interface, so as to achieve the purpose of transmitting the packet according to the correct forwarding path. Wherein the forwarding path is a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice.

As a possible design, the issuing, by the first network device, the first packet includes: and the first network equipment issues the first message to the control equipment or the second network equipment so that the control equipment or the second network equipment with the route calculation capability processes the forwarding path according to the first message. Certainly, the second network device may also be a network device without a routing capability, so as to achieve the purpose of flooding the first packet in the network topology.

In a second aspect, a forwarding path processing method is provided, which is applied to a target device, where the target device may be a control device or a second network device. The method comprises the following steps: the target device receives a first message from a first network device, where the first message carries an identifier of the network interface, changed state information of the network interface, and a slice identifier of a first network slice, and the changed state information indicates a changed state of the network interface belonging to the first network slice. And the target equipment processes a forwarding path according to the changed state information, wherein the forwarding path is a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice. Because the first message is sent when the state information of the network interface changes, compared with the traditional technology, the message sending amount is reduced, and the message is not required to be sent when the period is finished like the traditional technology, so that the processing efficiency of the target device on the forwarding path is improved. The target device can process the forwarding path in time according to the changed state information, so that the possibility of transmitting the message according to the wrong forwarding path is reduced, and the reliability of the network is ensured.

The target device processes the forwarding path according to the changed state information, and the processing modes according to the state information are different:

as a possible implementation manner, in response to that the changed state information indicates that the network interface deletes configuration of the first network slice, or in response to that the changed state information indicates that the network interface changes from a normal state to a fault state, the target device searches for path information of a forwarding path corresponding to an identifier of the network interface and a slice identifier of the first network slice. And the target device deletes the path information of the forwarding path or sets the path information of the forwarding path as invalid, thereby avoiding continuously using the wrong forwarding path. Or the target device recalculates the forwarding path corresponding to the slice identifier of the first network slice according to other network interfaces, except the network interface, belonging to the first network slice, so as to ensure that the correct forwarding path is adopted for message transmission.

As another possible implementation manner, in response to that the changed state information indicates that the network interface newly configures the first network slice, the target device generates a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice, so as to transmit a packet corresponding to the first network slice through the forwarding path. And the target device stores the corresponding relationship between the identifier of the network interface, the slice identifier of the first network slice, and the path information of the forwarding path, so that the subsequent target device performs corresponding processing according to the corresponding relationship, for example, the corresponding relationship is issued to the first network device, so that the first network device generates a routing table and a forwarding table for forwarding the packet according to the path information of the forwarding path.

As another possible implementation manner, if the target device deletes the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice when the network interface is in the fault state, the target device generates a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice in response to the changed state information indicating that the network interface is restored from the fault state to the normal state, or the target device sets the forwarding information of the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice as valid, so as to transmit the packet corresponding to the first network slice through the forwarding path. And the target device stores the corresponding relation among the identifier of the network interface, the slice identifier of the first network slice and the path information of the forwarding path.

For the type of the first packet, the changed state information, and the position of the slice identifier of the first network slice carried in the first packet, please refer to the above, which is not described herein again.

In a third aspect, a packet issuing apparatus is provided, which is applied to a first network device, and the apparatus includes: the processing unit is used for acquiring the state information of the network interface; the processing unit is further configured to generate a first message in response to a change of state information of the network interface, where the first message carries an identifier of the network interface, changed state information, and a slice identifier of a first network slice, and the changed state information indicates a changed state of the network interface belonging to the first network slice; and the sending unit is used for issuing the first message.

As a possible design, in response to a change in the state information of the network interface, the processing unit generates a first packet, including: responding to the network interface deleting and configuring the first network slice, and generating a first message by the processing unit; or, in response to the network interface newly configuring the first network slice, the processing unit generates a first packet.

As a possible design, in response to a change in the state information of the network interface, the processing unit generates a first packet, including: and responding to the change of the network interface from a normal state to a fault state, the processing unit acquires the slice identifier of the first network slice, and generates a first message according to the slice identifier of the first network slice.

As a possible design, in response to a change in the state information of the network interface, the processing unit generates a first packet, including: and responding to the network interface from the fault state to the normal state, the processing unit acquires the slice identifier of the first network slice, and generates a first message according to the slice identifier of the first network slice.

As a possible design, the first packet is used to process a forwarding path according to the changed state information of the network interface, where the forwarding path is a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice.

As a possible design, the sending unit is configured to issue the first packet to a control device or a second network device.

In a fourth aspect, a forwarding path processing apparatus is provided, which is applied to a target device, and the apparatus includes: a receiving unit, configured to receive a first packet from a first network device, where the first packet carries an identifier of the network interface, changed state information of the network interface, and a slice identifier of a first network slice, and the changed state information indicates a changed state of the network interface belonging to the first network slice; and the processing unit is used for processing a forwarding path according to the changed state information, wherein the forwarding path is a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice.

As a possible design, the processing unit is configured to, in response to the changed state information indicating that the network interface deletes configuration of the first network slice, or in response to the changed state information indicating that the network interface changes from a normal state to a failure state, search path information of a forwarding path corresponding to an identifier of the network interface and a slice identifier of the first network slice; the processing unit is further configured to delete the path information of the forwarding path or set the path information of the forwarding path as invalid; or, recalculating the forwarding path corresponding to the slice identifier of the first network slice according to other network interfaces except the network interface belonging to the first network slice.

As a possible design, the processing unit is configured to, in response to the changed state information indicating that the network interface newly configures the first network slice, generate a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice, and store a correspondence between the identifier of the network interface, the slice identifier of the first network slice, and the path information of the forwarding path.

As a possible design, the processing unit is configured to, in response to that the changed state information indicates that the network interface is restored from a fault state to a normal state, generate a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice, and store a correspondence between the identifier of the network interface, the slice identifier of the first network slice, and the path information of the forwarding path; or, setting the forwarding information of the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice as valid.

As a possible design, the target device is a control device or a second network device.

In a fifth aspect, a network device is provided, which includes a processor chip and a memory, wherein the memory is used for storing instructions or program codes, and the processor chip is used for calling and running the instructions or program codes from the memory to execute the message issuing method according to the first aspect.

In a sixth aspect, there is provided an apparatus comprising a processor chip and a memory, the memory being configured to store instructions or program code, the processor chip being configured to call and execute the instructions or program code from the memory to perform the forwarding path processing method according to the second aspect.

A seventh aspect provides a computer-readable storage medium comprising instructions, a program or code which, when executed on a computer, causes the computer to execute the packet issuing method according to the first aspect or the forwarding path processing method according to the second aspect.

Drawings

Fig. 1 is a schematic structural diagram of a network system according to an embodiment of the present application;

fig. 2 is a flowchart of a forwarding path processing method according to an embodiment of the present application;

fig. 3 is a schematic format diagram of a TLV field or a sub-TLV field provided in an embodiment of the present application;

fig. 4 is a schematic format diagram of an L2Bundle Attribute Descriptors field of an ISIS message provided in the embodiment of the present application;

fig. 5 is a schematic format diagram of an L2Bundle Member Attributes TLV field of an OSPF packet provided in the embodiment of the present application;

fig. 6 is a schematic format diagram of a Link-State NLRI field of a BGP message provided in the embodiment of the present application;

fig. 7 is a schematic structural diagram of a message issuing apparatus 700 according to an embodiment of the present application;

fig. 8 is a schematic structural diagram of a forwarding path processing apparatus 800 according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of an apparatus 900 provided in an embodiment of the present application;

fig. 10 is a schematic structural diagram of an apparatus 1000 according to an embodiment of the present application.

Detailed Description

In the conventional technology, a network device periodically sends information of a network slice configured by a network interface of the network device to other devices. Specifically, the network device periodically sends a message to other devices, where the message carries an identifier of each network interface in one or more network interfaces of the network device, and an identifier of a network slice configured for the network interface. If a certain network interface of the network device is not configured with a network slice, the message does not include the identifier of the network slice corresponding to the network interface. If a certain network interface fails, the message does not include the identifier of the network interface and the identifier of the corresponding network slice.

For example, network device a includes network interface 1, network interface 2, and network interface 3, where network interface 1 is configured with network slice 1, network interface 2 is configured with network slice 2, and network interface 3 is not configured with network slice. Then network device a includes the identity of network interface 1, the identity of network slice 1, the identity of network interface 2, the identity of network slice 2, and the identity of network interface 3 in messages sent to other devices. If the network interface 1 fails, the network device a includes the identifier of the network interface 2, the identifier of the network slice 2, and the identifier of the network interface 3 in a message sent to another device.

When the information of the network interface and the corresponding network slice does not change in a period of time, the periodic reporting of the information causes a waste of transmission resources on one hand, and causes a waste of processing resources due to the processing of the packet by other devices on the other hand. Moreover, when the state of the network interface changes in a reporting period, the message also needs to be reported when the timing of the period is finished, which affects the efficiency of other devices for acquiring and processing the information in the message.

In order to overcome the above technical problems, embodiments of the present application provide a forwarding path processing method and device, which are used to save network resources and improve processing efficiency.

The forwarding path processing method provided in the embodiment of the present application may be applied to the network system shown in fig. 1, for example. In the figure, the network system includes a network device 101, a network device 102, a network device 103, a network device 104, and a control device 201. The network device 101 is connected to the network device 102 and the network device 103, the network device 102 and the network device 103 are connected to the network device 104, and the control device 201 is connected to the network device 101, the network device 102, the network device 103, and the network device 104.

Network device 101, network device 102, network device 103, and network device 104 may be, for example, physical devices such as a router (router) and a switch (switch) that support a routing function, or may be servers that deploy virtual routers or virtual switches. The network device 101, the network device 102, the network device 103, and the network device 104 may establish a neighbor relationship based on an Interior Gateway Protocol (IGP).

The Control device 201 may be, for example, a Network Control Element (NCE) or the like. The control device 201, the network device 101, and the network device 104 may establish a neighbor relationship through a Border Gateway Protocol (BGP).

Referring to fig. 2, this figure is a flowchart of a forwarding path processing method according to an embodiment of the present application.

The forwarding path processing method comprises the following steps:

s201: the first network device obtains status information of the network interface.

In the embodiment of the present application, the first network device may be, for example, network device 101, network device 102, network device 103, or network device 104 in fig. 1.

In this embodiment, the first network device may have one or more network interfaces, which may be physical interfaces or virtual interfaces (also referred to as sub-interfaces).

The first network device obtains status information of the network interface, wherein the status information indicates the status of the network interface. For example, whether a network interface is configured with a corresponding network slice, whether a network interface fails, etc. Wherein a network interface may be configured with one or more network slices. The network interface failure may be a failure at the physical level or a failure at the protocol level. No matter which layer fails, the network interface cannot receive or send the message.

S202: and responding to the state information of the network interface to change, and the first network equipment generates a first message.

In this embodiment, when the first network device determines that the state information of the network interface changes, the first network device may generate a first packet according to the identifier of the network interface, the changed state information, and the slice identifier of the first network slice, where the changed state information indicates a changed state of the network interface belonging to the first network slice.

The change of the state information of the network interface may have several scenes, and the following different scenes are combined to introduce the information carried by the first message.

Scene one: and the network interface newly configures a first network slice.

Before the network interface newly configures the first network slice, the state information of the network interface acquired by the first network device is that the first network slice is not configured for the network interface (please refer to the following text for the process of checking that the network slice is not configured, which is not described herein again). The action of the network interface newly adding the configuration first network slice may trigger the generation of the first packet. The first message carries the identifier of the network interface, the slice identifier of the first network slice, and the changed state information of the network interface, wherein the changed state information indicates that the first network slice is a newly configured network slice of the network interface.

If the network interface is configured with other network slices before the first network slice is newly configured, the first message may only carry the identifier of the first network slice, and does not need to carry the identifiers of other network slices, so as to save network resources.

Scene two: the network interface deletes the configuration first network slice.

Before the network interface deletes the configuration of the first network slice, the state information of the network interface acquired by the first network device configures the first network slice for the network interface. The act of the network device deleting the configuration first network slice may trigger generation of the first packet. The first message carries the identifier of the network interface, the slice identifier of the first network slice, and the changed state information of the network interface, wherein the changed state information indicates that the network interface deletes the configuration of the first network slice.

Scene three: the network interface changes from a normal state to a fault state.

Before the network interface fails, the state information of the network interface acquired by the first network device is that the network interface is in a normal state, that is, the first network device can receive a message or send a message. When the network interface fails, the first network device acquires a slice identifier of a first network slice configured for the network interface, and triggers generation of a first message. The first message carries the identifier of the network interface, the slice identifier of the first network slice, and the changed state information of the network interface, wherein the changed state information indicates that the network interface fails.

If the network interface is configured with other network slices besides the first network slice, the first message may also carry identifiers of other network slices to inform the device receiving the first message that the message corresponding to the network slices cannot be transmitted due to the failure of the network interface.

Scene four: and the network interface is recovered to a normal state from a fault state.

Before the network interface recovers to the normal state, the state information of the network interface acquired by the first network device is that the network interface is in the fault state. When the network interface returns to a normal state, the first network device obtains a slice identifier of a first network slice configured for the network interface before, and triggers generation of a first message. The first message carries the identifier of the network interface, the slice identifier of the first network slice, and the changed state information of the network interface, wherein the changed state information indicates that the network interface is restored to a normal state.

If the network interface is configured with other network slices besides the first network slice, the first message may also carry identifiers of other network slices to inform the device receiving the first message that the network interface is restored to a normal state, so that the message corresponding to the network slices can be transmitted.

The four scenarios are not limited to the technical solution of the present application, and can be designed by a person skilled in the art according to actual situations.

It should be noted that, when the state information of the multiple network interfaces of the first network device changes, the first message may carry an interface identifier of each network interface of the multiple network interfaces, changed state information corresponding to the interface identifier, and a slice identifier of the first network slice corresponding to the interface identifier.

S203: and the first network equipment issues the first message.

In this embodiment, the first network device may issue the first packet to the target device. The target device may be a second network device or a control device. For example, when the first network device is network device 102, the target device may be network device 101 or network device 104. When the first network device is the network device 101, the target device may be the control device 201.

In this embodiment of the application, the changed state information of the network interface of the first network device and the slice identifier of the first network slice may be carried in the first message in a form of a Type Length Value (TLV) field or a sub-TLV (sub-TLV). The two pieces of information may be carried in the same TLV field or the same sub-TLV field, or may be carried in different TLV fields or different sub-TLV fields.

Referring to fig. 3, the diagram is a schematic format diagram of the state information and the slice identifier of the first network slice carried in the same TLV field or the same sub-TLV field after the network interface is changed. The TLV field or sub-TLV field includes: a Type field, a Length field, a state field, a Reserved field, and a virtual transport network identifier (vtn-id) field. Wherein, the value of the Type field is used to indicate that the TLV field or the sub-TLV field is a field used to carry the state information after the network interface is changed and the slice identifier of the first network slice. The Length field has a value of the Length of the TLV field or sub-TLV field. The state field is used for carrying state information after the network interface is changed. The vtn-id field is used to carry the slice identification of the first network slice, which may occupy 4octets. The Reserved field is used to carry other information.

In this embodiment of the present application, the identifier of the network interface of the first network device may be carried in the same TLV field or the same sub-TLV field as the changed state information and the slice identifier of the first network slice, or may be carried in other fields, which is not specifically limited in this application.

When the target device is a second network device, the First network device may issue a First packet to the second network device based on IGP, where the First packet may be, for example, an Intermediate System to Intermediate System (ISIS) packet or an Open Shortest Path First (OSPF) packet. When the target device is a control device, the first network device may issue a first packet to the control device based on BGP, where the first packet may be, for example, a BGP packet.

When the first packet is an ISIS packet or an OSPF packet, the changed state information of the network interface and the slice identifier of the first network slice are carried in a Type Length Value (TLV) field of a two-layer (Lay 2, L2) binding Member attribute (Bundle Member Attributes) of the ISIS packet or the OSPF packet.

Specifically, the L2Bundle Member Attributes TLV field of the ISIS packet includes a two-layer binding Attribute descriptor (L2 Bundle Attribute Descriptors) field, and the changed state information and the slice identifier of the first network slice may be carried in the L2Bundle Attribute Descriptors field.

Referring to FIG. 4, the format of the L2Bundle Attribute Descriptors field is shown. Based on rfc8668, the L2Bundle Attribute Descriptors field includes: a length (len) field, a descriptor (Desc) field, a Link local Identifier Bundle Member #1 field, and a Link local Identifier Bundle Member #2 field. Wherein, the len field has a value of 25, the Desc field has a value of 2, the Link local Identifier Bundle member #1 field has a value of 0x11111111, and the Link local Identifier Bundle member #2 field has a value of 0x11112222. In addition to the above fields, the L2Bundle Attribute Descriptors field may further include a sub-TLV field shown in fig. 3, so as to carry the state information after the network interface change and the slice identifier of the first network slice.

In addition, the L2Bundle Member Attributes TLV field of the ISIS packet may also carry an identifier of a network interface. The identification of the network interface may be embodied as an Internet Protocol (IP) address or index of the network interface.

For example, the L2Bundle Member Attributes TLV field includes an Internet Protocol fourth version (Internet Protocol version 4, IPv 4) interface address sub-TLV field or an Internet Protocol sixth version (Internet Protocol version 6, IPv 6) interface address sub-TLV field, where the IPv4 interface address sub-TLV field is used to carry an IPv4 address of the network interface and the IPv6 interface address sub-TLV field is used to carry an IPv6 address of the network interface.

The L2Bundle Member Attributes TLV field may further include a Link local Identifier (Link Identifier) field of the network interface, and is used to carry an index of the network interface. For example, network device 101 includes two network interfaces indexed 01 and 02, respectively.

Referring to fig. 5, the figure is a schematic format diagram of an L2Bundle Member Attributes TLV field of an OSPF packet. In this figure, the L2Bundle members Attributes TLV field includes: a Type field, a Length field, an L2Bundle Member Descriptor field, and a Member Link attribute (Member Link attribute) subtype Length value (sub-TLV) field. The changed state information and the slice identifier of the first network slice may be in a sub-TLV format as shown in fig. 3, and the like, as one sub-TLV in the Member Link attribute sub-TLV field.

In addition, the number Link attribute sub-TLV field can also carry the identification of the network interface. For example, the Member Link attribute sub-TLV field includes a local interface ID sub-TLV field, which is used to carry an index of the network interface. The Member Link attribute sub-TLV field can also carry a local interface IPv6 address field for carrying the IPv6 address of the network interface.

When the first message is a BGP message, the changed State Information and the slice identifier of the first Network slice are carried in a Network Layer availability Information (NLRI) field of a Link-State (Link-State) of the BGP message. Referring to fig. 6, the format of the Link-State NLRI field is shown. In the figure, the Link-State NLRI field includes a protocol-number (protocol-ID) field, an identification field (Identifier) field (64 bits), a Local Node descriptor (Local Node Descriptors) field, a Remote Node descriptor (Remote Node Descriptors) field, and a Link descriptor (Link Descriptors) field. Wherein the Local Node Descriptors field, remote Node Descriptors field, and Link Descriptors field are optional (variable).

The Link Descriptors field comprises a Link Local Identifier field and is used for carrying the Identifier of the network interface. In this embodiment of the application, the Link Descriptors field may further include a sub-TLV field shown in fig. 3, which is used to carry the changed state information of the network interface and the slice identifier of the first network slice.

S204: the target device receives a first message from the first network device.

S205: and the target equipment processes the forwarding path according to the changed state information of the network interface.

In this embodiment of the present application, when a target device has a capability of processing a forwarding path, for example, the target device is a control device or an edge network device with a path calculation capability, the target device may process the forwarding path according to changed state information of a network interface carried in a first packet, where the forwarding path is a forwarding path corresponding to an identifier of the network interface and a slice identifier of a first network slice.

In the embodiment of the present application, the content indicated by the changed state information is different, and the manner in which the target device processes the forwarding path is also different.

When the changed state information indicates that the network interface deletes configuration of the first network slice, or the changed state information indicates that the network interface changes from a normal state to a fault state, the target device may search path information of a forwarding path corresponding to an identifier of the network interface and a slice identifier of the first network slice, which is stored in advance, and delete the path information of the forwarding path or set the path information of the forwarding path as invalid. Moreover, after deleting the path information of the forwarding path or setting the path information of the forwarding path as invalid, the target device needs to notify other network devices except the first network device that the forwarding path passes through, so as to avoid a problem of message loss caused by forwarding a message through the forwarding path.

Or after the target device finds the path information of the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice, the target device recalculates the forwarding path corresponding to the slice identifier of the first network slice according to other network interfaces, except the network interface, belonging to the first network slice. And the target device can issue the re-calculated forwarding information of the forwarding path to the network device on the forwarding path, so as to achieve the purpose of forwarding the message of the first network slice through the normal forwarding path.

When the changed state information indicates that the network interface is newly configured with the first network slice, the target device generates a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice, and stores a corresponding relationship between the identifier of the network interface, the slice identifier of the first network slice and path information of the forwarding path. The target device may also issue forwarding information of the forwarding path to the network device on the forwarding path, so as to forward the packet of the first network slice through the forwarding path.

If the target device deletes the path information of the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice when the network interface is in the fault state, the target device may regenerate the forwarding path when the changed state information indicates that the network interface is restored from the fault state to the normal state, and store the correspondence between the identifier of the network interface, the slice identifier of the first network slice, and the path information of the forwarding path. If the target device sets the path information of the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice to be invalid when the network interface is in the fault state, the target device may set the path information of the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice to be valid when the changed state information indicates that the network interface is restored from the fault state to the normal state. After the forwarding path is regenerated or the path information is set to be valid, the target device may notify the network device on the forwarding path, so that the forwarding path can forward the packet of the first network slice.

When the first network device and the target device are not directly connected, that is, other network devices are connected between the first network device and the target device, the network devices may forward the first packet, so that the target device can receive the first packet and perform subsequent steps.

Compared with the scheme of periodically releasing the network interface and the configured information of the network slice in the prior art, the embodiment of the application releases the first message carrying the changed state information of the network interface, the identifier of the network interface and the corresponding slice identifier of the first network slice to the target device only when the state information of the network interface of the first network device changes, so that the number of message releases is reduced, the message does not need to be released when the periodic timing is finished, the release time is saved, and the processing efficiency of the target device is improved.

The following describes how to check that a network slice corresponding to a network interface is not configured, and how to generate a forwarding path corresponding to an identification of the network interface and a slice identification of a first network slice, by taking fig. 1 as an example.

In this embodiment, the control device 201 may issue, to the network device 101, the network device 102, the network device 103, and the network device 104 which communicate with the control device, corresponding slice instance information respectively, where the slice instance information includes a correspondence between an Identification (ID) of a Flexible Algorithm (FA) and a slice identifier of a network slice. Wherein the FA ID is used to identify algorithm constraints of the flexible algorithm. The slice instance information may further include an algorithm constraint condition corresponding to the FA ID, so that the network device in communication with the control device 201 acquires and stores the information. In some examples, the algorithm constraint condition may also be directly configured in the network device, that is, the control device 201 only issues the correspondence between the FA ID and the slice identifier, and does not issue the algorithm constraint condition corresponding to the FA ID.

The algorithm constraint conditions of the flexible algorithm include, for example, a metric type (metric type), a calculation type (calculation type), a link attribute, and the like.

The metric value types include three types: metric type =0 denotes the IGP metric value; metric type =1 denotes the minimum individual link delay (link delay), see specifically RFC7810 protocol; the metric type =2 represents the traffic engineering metric value, and please refer to RFC5305 protocol specifically.

The calculation types include two types: calculation type =0 denotes Shortest Path First (SPF); calculation type =1 denotes strict shortest path first (strict SPF).

The link attributes are represented by color (color), and different link attributes correspond to different colors. The network devices with the same link attribute form a network topology structure, and the corresponding forwarding path is calculated based on the network topology structure.

The constraints may further include:

exclusion management Group (exception Admin Group): the designated link management group cannot contain any referenced affinity attribute name, and unsatisfied links will be excluded from participating in the calculation.

Including Any one of the administrative groups (Included-Any Admin Group): a given link management group can participate in calculating a way as long as it contains a referenced affinity attribute name.

Including the complete administration Group (Included-All Admin Group): if the specified link management group is to contain all referenced affinity attribute names, links that are not satisfied are excluded from participating in the calculation.

For example, the control device 201 transmits the correspondence relationship of the FA ID 128 and the slice identifier of network slice 1, and the correspondence relationship of the FA ID 129 and the slice identifier of network slice 2 to the network device 101, the network device 102, the network device 103, and the network device 104, respectively.

Assuming that a network slice 1 is used for transmitting a message of a high-bandwidth service, the corresponding algorithm constraint conditions are as follows:

metric type：IGP Metric；

calculation type：SPF；

exclude Admin Group: and (3) red.

The network slice 2 is used for transmitting a message of a low-delay service, and the corresponding algorithm constraint conditions are as follows:

metric type：IGP Metric；

calculation type：SPF；

Included-Any Admin Group: and blue.

If the slice instance information sent by the control device 201 includes an algorithm constraint condition, and different slice IDs correspond to a plurality of algorithm constraint conditions, the network device may select one algorithm constraint condition corresponding to the slice ID according to the priority of the algorithm constraint condition.

The control device 201 also issues the corresponding relationship between the corresponding interface set and the slice identifier of the network slice to the network device 104 communicating with the control device.

For example, the control device 201 sends, to the network device 101, a correspondence between the slice identifications of the interface set a and the network slice 1, and a correspondence between the slice identifications of the interface set B and the network slice 2, where the interface set a and the interface set B respectively include one or more network interfaces of the network device 101.

And the network equipment determines an interface set meeting the algorithm constraint condition according to the algorithm constraint condition corresponding to the network slice.

For example, the network device 101 determines, according to the algorithm constraint condition corresponding to the network slice 1, that the interface set meeting the algorithm constraint condition is an interface set a'. The network device 101 determines the interface set meeting the algorithm constraint condition to be an interface set B' according to the algorithm constraint condition corresponding to the network slice 2.

The network device compares the interface set corresponding to the network slice issued by the control device 201 and the interface set determined according to the algorithm constraint condition of the network slice, and if one or more interfaces in the interface set determined according to the algorithm constraint condition are not in the issued interface set, it indicates that the one or more interfaces are not configured with the network slice.

For example, it is assumed that the interface set a 'corresponding to the network slice 1 and determined by the network device 101 includes a sub-interface a of the interface 1 and a sub-interface b of the interface 2, the interface set a corresponding to the network slice 1 and issued by the control device 201 includes the sub-interface a of the interface 1 and the sub-interface b of the interface 2, and it can be seen that the interface set a' is completely included in the interface set a, which indicates that the sub-interface a of the interface 1 and the sub-interface b of the interface 2 are both configured with the network slice 1.

Assuming that the interface set B ' corresponding to the network slice 2 determined by the network device 101 includes the sub-interface c of the interface 1 and the sub-interface d of the interface 2, and the interface set B corresponding to the network slice 2 issued by the control device 201 includes the sub-interface c of the interface 1, since the sub-interface c of the interface 1 in the interface set B ' is included in the interface set B and the sub-interface d of the interface 2 in the interface set B ' is not included in the interface set B, it is described that the sub-interface c of the interface 1 is configured with the network slice 2, and the sub-interface d of the interface 2 is not configured with the network slice 2.

Based on the above description, when a certain network interface of the network device changes from configured network slice to unconfigured network slice, the first packet may be issued.

For example, when the subinterface d of the interface 2 of the network device 101 is configured with the network slice 2 from the previous configuration to the deletion of the configuration of the network slice 2 for various reasons, a first message may be issued, where the first message may carry an identifier of the subinterface d of the interface 2, a slice identifier of the network slice 2, and changed state information, where the changed state information is used to indicate that the subinterface d deletes the configuration of the network slice 2.

After knowing which corresponding network slices are configured for the network interfaces of each network device, the control device 201 may calculate a forwarding path configured with the same network slice, and store a correspondence between path information of the forwarding path, an identifier of the network interface, and an identifier of the network slice. And, the control device 201 may issue the path information to the corresponding network device, so as to achieve the purpose of forwarding the packet belonging to the network slice through the forwarding path. Specifically, the control device 201 may issue a Segment Routing (policy) policy or an IPv6 Segment Routing (IPv 6, SRv) policy, where the policy carries path information, and the path information may be embodied as a Segment Identifier (SID) list (list).

For example, if the forwarding path calculated by the control device 201 and corresponding to network slice 1 is network device 101, network device 102, and network device 104, the control device 201 may store the correspondence between SID list of the forwarding path, sub-interface a of the network device 101, and network slice 1, and send the SID list to the network device 101, so that the network device 101 generates a corresponding forwarding table according to the SID list, where an output interface of the forwarding table is the sub-interface a. Based on the forwarding table, network device 101 may forward the packet to network device 102 through sub-interface a.

Referring to fig. 7, an embodiment of the present application further provides a message issuing apparatus 700, where the message issuing apparatus 700 may implement the function of the first network device in the embodiment shown in fig. 2. The message distribution apparatus 700 includes a processing unit 701 and a transmitting unit 702. Wherein, the processing unit 701 is configured to implement S201 and S202 in the embodiment shown in fig. 2; the sending unit 702 is configured to implement S203 in the embodiment shown in fig. 2.

Specifically, the processing unit 701 is configured to obtain state information of a network interface, and generate a first message in response to a change of the state information of the network interface, where the first message carries an identifier of the network interface, changed state information, and a slice identifier of a first network slice, and the changed state information indicates a changed state of the network interface belonging to the first network slice.

A sending unit 702, configured to issue the first packet.

For a specific execution process, reference is made to the detailed description of the corresponding steps in the embodiment shown in fig. 2, which is not repeated here.

Referring to fig. 8, an embodiment of the present application further provides a forwarding path processing apparatus 800, where the forwarding path processing apparatus 800 may implement the function of the target device in the embodiment shown in fig. 2. The forwarding path processing apparatus 800 includes a receiving unit 801 and a processing unit 802. Wherein, the receiving unit 801 is configured to implement S204 in the embodiment shown in fig. 2; the processing unit 802 is configured to implement S205 in the embodiment shown in fig. 2.

Specifically, the receiving unit 801 is configured to receive a first packet from a first network device, where the first packet carries an identifier of the network interface, changed state information of the network interface, and a slice identifier of a first network slice, and the changed state information indicates a changed state of the network interface belonging to the first network slice.

A processing unit 802, configured to process a forwarding path according to the changed state information, where the forwarding path is a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice.

It should be noted that the division of the unit in the embodiment of the present application is schematic, and is only a logic function division, and there may be another division manner in actual implementation. Each functional unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. For example, in the above embodiment, the acquiring unit and the processing unit may be the same unit or different units. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

Fig. 9 is a schematic structural diagram of an apparatus 900 according to an embodiment of the present application. The message issuing apparatus 700 or the forwarding path processing apparatus 800 in the foregoing may be implemented by the device shown in fig. 9. Referring to fig. 9, the device 900 comprises at least one processor 901, a communication bus 902 and at least one network interface 904, optionally the device 900 may further comprise a memory 903.

The processor 901 may be a Central Processing Unit (CPU), a Network Processor (NP), or a combination of a CPU and an NP. In one implementation, the processor 901 may also be a Traffic Management (TM) chip or hardware integrating NP and TM chips, and the TM chip or the hardware integrating NP and TM chips may execute the method for scheduling queues in the TM chip according to the embodiment of the present application. The processor 1010 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a Programmable Logic Device (PLD), or a combination thereof. The PLD may be a Complex Programmable Logic Device (CPLD), a field-programmable gate array (FPGA), a General Array Logic (GAL), or any combination thereof. The processor may be configured to update or check the data packet, so as to implement the packet transmission method provided in the embodiment of the present application.

For example, when the first network device in fig. 2 is implemented by the device shown in fig. 9, the processor may be configured to: acquiring the state information of a network interface, responding to the change of the state information of the network interface, generating a first message, and issuing the first message. When the target device in fig. 2 is implemented by the device shown in fig. 9, the processor may be configured to: and receiving a first message from the first network equipment, and processing the forwarding path according to the changed state information.

The communication bus 902 is used to transfer information between the processor 901, the network interface 904, and the memory 903. The bus system 902 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus system 902 may be divided into an address bus, a data bus, a control bus, etc., which is indicated in fig. 9 by only one thick line, but does not indicate that there is only one bus or one type of bus.

The Memory 903 may be a read-only Memory (ROM) or other type of static storage device that may store static information and instructions, and the Memory 903 may also be a Random Access Memory (RAM) or other type of dynamic storage device that may store information and instructions, a compact disk read-only Memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these. The memory 903 may be separate and coupled to the processor 901 via a communication bus 902. The memory 903 may also be integrated with the processor 901.

Optionally, the memory 903 is used for storing program codes or instructions for executing the scheme of the present application, and is controlled by the processor 901 to execute. The processor 901 is configured to execute program code or instructions stored in the memory 903. One or more software modules may be included in the program code. Alternatively, the processor 901 may also store program code or instructions for performing aspects of the present application, in which case the processor 901 need not read the program code or instructions into the memory 903.

Network interface 904 may be a transceiver or the like for communicating with other devices or a communication network, such as an ethernet, a Radio Access Network (RAN), or a Wireless Local Area Network (WLAN). In this embodiment, the network interface 904 may be configured to receive a packet sent by another node in the segment routing network, and may also send a packet to another node in the segment routing network. The network interface 904 may be an ethernet (ethernet) interface, a Fast Ethernet (FE) interface, or a Gigabit Ethernet (GE) interface.

In particular implementations, device 900 may include multiple processors, such as processor 901 and processor 905 shown in FIG. 9, for one embodiment. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

Fig. 10 is a schematic structural diagram of an apparatus 1000 according to an embodiment of the present disclosure. Any one or more of the first network device and the target device in fig. 2 may be implemented by the device shown in fig. 10.

Referring to the schematic diagram of the device structure shown in fig. 10, the device 1000 includes a main control board and one or more interface boards. The main control board is in communication connection with the interface board. The main control board is also called a Main Processing Unit (MPU) or a route processor card (route processor card), and includes a CPU and a memory, and is responsible for controlling and managing each component in the device 1000, including routing calculation, device management, and maintenance functions. An interface board is also called a Line Processing Unit (LPU) or a line card (line card) and is used for receiving and transmitting messages. In some embodiments, the master control board communicates with the interface board or the interface board communicates with the interface board through a bus. In some embodiments, the interface boards communicate with each other through a switch board, in which case the device 1000 also includes a switch board, the switch board is communicatively connected to the main control board and the interface boards, the switch board is used to forward data between the interface boards, and the switch board may also be referred to as a Switch Fabric Unit (SFU). The interface board includes a CPU, memory, a forwarding engine, and Interface Cards (ICs), which may include one or more network interfaces. The network interface can be an Ethernet interface, an FE interface or a GE interface. The CPU is in communication connection with the memory, the forwarding engine and the interface card respectively. The memory is used for storing a forwarding table. The forwarding engine is configured to forward the received packet based on a forwarding table stored in the memory, and if a destination address of the received packet is an IP address of the device 700, send the packet to a CPU of the main control board or the interface board for processing; if the destination address of the received message is not the IP address of the device 1000, the forwarding table is searched according to the destination, and if the next hop and egress interface corresponding to the destination address are found from the forwarding table, the message is forwarded to the egress interface corresponding to the destination address. The forwarding engine may be a Network Processor (NP). The interface card is also called a daughter card and can be installed on an interface board and is responsible for converting photoelectric signals into data frames, and forwarding the data frames to a forwarding engine for processing or an interface board CPU after validity check is carried out on the data frames. In some embodiments, the CPU may also perform the functions of a forwarding engine, such as implementing soft forwarding based on a general purpose CPU, so that no forwarding engine is needed in the interface board. In some embodiments, the forwarding engine may be implemented by an ASIC or a Field Programmable Gate Array (FPGA). In some embodiments, the memory storing the forwarding table may also be integrated into the forwarding engine as part of the forwarding engine.

An embodiment of the present application further provides a chip system, including: a processor coupled to a memory, the memory being configured to store a program or instructions, which when executed by the processor, causes the system-on-chip to implement the message transmission method provided in the embodiment shown in fig. 2.

Optionally, the system on a chip may have one or more processors. The processor may be implemented by hardware or by software. When implemented in hardware, the processor may be a logic circuit, an integrated circuit, or the like. When implemented in software, the processor may be a general-purpose processor implemented by reading software code stored in a memory. Optionally, the memory in the system-on-chip may also be one or more. The memory may be integrated with the processor or may be separate from the processor, which is not limited in this application. For example, the memory may be a non-transitory processor, such as a read only memory ROM, which may be integrated with the processor on the same chip or separately disposed on different chips, and the type of the memory and the arrangement of the memory and the processor are not particularly limited in this application.

The system on chip may be, for example, an FPGA, an ASIC, a system on chip (SoC), a CPU, an NP, a digital signal processing circuit (DSP), a Micro Controller Unit (MCU), a Programmable Logic Device (PLD) or other integrated chips.

It will be appreciated that the steps of the above described method embodiments may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The steps of the method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor.

The embodiment of the present application further provides a computer-readable storage medium, which includes instructions, and when the computer-readable storage medium runs on a computer, the computer is enabled to execute the packet issuing method executed by the first network device or the forwarding path processing method executed by the target device, which are provided in the above method embodiment.

Embodiments of the present application further provide a computer program product including instructions, which when run on a computer, cause the computer to execute the packet issuing method executed by the first network device or the forwarding path processing method executed by the target device, which are provided in the above method embodiments.

The terms "first," "second," "third," "fourth," and the like in the description and claims of this application and in the above-described drawings, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one type of logical module division, and other division manners may be available in actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be obtained according to actual needs to achieve the purpose of the solution of the present embodiment.

In addition, each module unit in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a hardware form, and can also be realized in a software module unit form.

The integrated unit, if implemented as a software module unit and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above-described embodiments are intended to explain the objects, aspects and advantages of the present invention in further detail, and it should be understood that the above-described embodiments are merely exemplary embodiments of the present invention.

The above embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; and the modifications or the substitutions do not make the essence of the corresponding technical solutions depart from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for issuing a message, the method comprising:

the method comprises the steps that a first network device obtains state information of a network interface;

responding to the change of the state information of the network interface, the first network equipment generates a first message, wherein the first message carries the identifier of the network interface, the changed state information and the slice identifier of a first network slice, and the changed state information indicates the changed state of the network interface belonging to the first network slice;

and the first network equipment issues the first message.

2. The method of claim 1, wherein in response to a change in the state information of the network interface, the first network device generates a first packet comprising:

responding to the network interface deleting and configuring the first network slice, and generating a first message by the first network equipment; or the like, or, alternatively,

and responding to the network interface newly added and configured with the first network slice, and the first network equipment generates a first message.

3. The method of claim 1, wherein in response to a change in the state information of the network interface, the first network device generates a first packet comprising:

and responding to the change of the network interface from the normal state to the fault state, the first network equipment acquires the slice identifier of the first network slice, and generates a first message according to the slice identifier of the first network slice.

4. The method of claim 1, wherein in response to a change in the state information of the network interface, the first network device generates a first packet comprising:

and responding to the network interface from the fault state to the normal state, the first network equipment acquires the slice identifier of the first network slice, and generates a first message according to the slice identifier of the first network slice.

5. The method of any of claims 1-4, wherein the first packet is an intermediate system to intermediate system ISIS packet, an Open Shortest Path First (OSPF) packet, or a Border Gateway Protocol (BGP) packet.

6. The method of claim 5, wherein the changed state information and the slice identifier of the first network slice are carried in a two-layer Bundle Member attribute L2Bundle Member Attributes Type Length Value (TLV) field of the ISIS packet or the OSPF packet.

7. The method according to claim 6, wherein the L2Bundle number Attributes TLV field of the ISIS message comprises a two-layer binding Attribute description L2Bundle Attribute Descriptors field, and wherein the changed state information and the slice identifier of the first network slice are carried in the L2Bundle Attribute Descriptors field.

8. The method according to claim 6, wherein the L2Bundle Member Attributes TLV field of the OSPF packet includes a Member Link Attribute subtype Length value sub-TLV field, and wherein the changed state information and the slice identifier of the first network slice are carried in the Member Link Attribute sub-TLV field.

9. The method of claim 6, wherein the changed State information and the slice identifier of the first network slice are carried in a Link-State Network Layer Reachability Information (NLRI) field of the BGP packet.

10. The method of claim 9, wherein the Link-State NLRI field comprises a Link descriptor links Descriptors field, and wherein the changed State information and a slice identifier of the first network slice are carried in the Link Descriptors field.

11. The method according to any of claims 1-10, wherein the first packet is used to process a forwarding path according to the changed state information of the network interface, and the forwarding path is a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice.

12. The method according to any of claims 1-11, wherein the first network device issuing the first packet comprises:

and the first network equipment issues the first message to control equipment or second network equipment.

13. A forwarding path processing method, the method comprising:

the method comprises the steps that target equipment receives a first message from first network equipment, wherein the first message carries an identifier of a network interface, changed state information of the network interface and a slice identifier of a first network slice, and the changed state information indicates the changed state of the network interface belonging to the first network slice;

and the target equipment processes a forwarding path according to the changed state information, wherein the forwarding path is a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice.

14. The method of claim 13, wherein the target device processing the forwarding path according to the changed state information comprises:

responding to the changed state information to indicate that the network interface deletes the configuration of the first network slice, or responding to the changed state information to indicate that the network interface changes from a normal state to a fault state, and searching path information of a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice by the target device;

the target device deletes the path information of the forwarding path or sets the path information of the forwarding path as invalid; or the target device recalculates the forwarding path corresponding to the slice identifier of the first network slice according to other network interfaces except the network interface belonging to the first network slice.

15. The method of claim 13, wherein the target device processing the forwarding path according to the status information of the network interface comprises:

and responding to the changed state information to indicate the network interface to newly configure the first network slice, generating a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice by the target device, and storing the corresponding relation between the identifier of the network interface, the slice identifier of the first network slice and the path information of the forwarding path.

16. The method of claim 13, wherein the target device processing the forwarding path according to the status information of the network interface comprises:

responding to the changed state information to indicate that the network interface is restored to a normal state from a fault state, generating a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice by the target device, and storing the corresponding relation among the identifier of the network interface, the slice identifier of the first network slice and the path information of the forwarding path; or, the target device sets the forwarding information of the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice to be valid.

17. The method of any of claims 13-16, wherein the first packet is an intermediate system to intermediate system ISIS packet, an open shortest path first OSPF packet, or a border gateway protocol BGP packet.

18. The method of claim 17, wherein the changed state information and the slice identifier of the first network slice are carried in a two-layer Bundle Member attribute L2Bundle Member Attributes length value TLV field of the ISIS packet or the OSPF packet.

19. The method of claim 18, wherein an L2Bundle Member Attributes TLV field of the ISIS packet includes a two-layer Bundle Attribute description L2Bundle Attribute Descriptors field, and wherein the changed state information and the slice identifier of the first network slice are carried in the L2Bundle Attribute Descriptors field.

20. The method according to claim 18, wherein the L2Bundle Member Attributes TLV field of the OSPF packet includes a Member Link attribute sub-type length value sub-TLV field, and the changed state information and the slice identifier of the first network slice are carried in the Member Link attribute sub-TLV field.

21. The method of claim 18, wherein the changed State information and the slice identifier of the first network slice are carried in a Link-State Network Layer Reachability Information (NLRI) field of the BGP packet.

22. The method of claim 21, wherein the Link-State NLRI field comprises a Link descriptor links Descriptors field, and wherein the changed State information and a slice identifier of the first network slice are carried in the Link Descriptors field.

23. The method according to any of claims 13-22, wherein the target device is a control device or a second network device.

24. A message distribution apparatus, applied to a first network device, the apparatus comprising:

the processing unit is used for acquiring the state information of the network interface;

the processing unit is further configured to generate a first message in response to a change of state information of the network interface, where the first message carries an identifier of the network interface, changed state information, and a slice identifier of a first network slice, and the changed state information indicates a changed state of the network interface belonging to the first network slice;

and the sending unit is used for issuing the first message.

25. The apparatus of claim 24, wherein in response to a change in the state information of the network interface, the processing unit generates a first packet comprising:

responding to the network interface deleting and configuring the first network slice, and generating a first message by the processing unit; or the like, or, alternatively,

and responding to the network interface newly added and configured with the first network slice, and the processing unit generates a first message.

26. The apparatus of claim 24, wherein in response to a change in the state information of the network interface, the processing unit generates a first packet comprising:

and responding to the change of the network interface from the normal state to the fault state, the processing unit acquires the slice identifier of the first network slice, and generates a first message according to the slice identifier of the first network slice.

27. The apparatus of claim 24, wherein in response to a change in the state information of the network interface, the processing unit generates a first packet comprising:

and responding to the network interface from the fault state to the normal state, the processing unit acquires the slice identifier of the first network slice, and generates a first message according to the slice identifier of the first network slice.

28. The apparatus of any of claims 24-27, wherein the first packet is an intermediate system to intermediate system ISIS packet, an open shortest path first OSPF packet, or a border gateway protocol BGP packet.

29. The apparatus of claim 28, wherein the changed state information and the slice identifier of the first network slice are carried in a two-layer Bundle Member attribute L2Bundle Member Attributes length value TLV field of the ISIS packet or the OSPF packet.

30. The apparatus of claim 29, wherein an L2Bundle Member Attributes TLV field of the ISIS packet includes a two-layer Bundle Attribute description L2Bundle Attribute Descriptors field, and wherein the changed state information and the slice identifier of the first network slice are carried in the L2Bundle Attribute Descriptors field.

31. The apparatus of claim 29, wherein an L2Bundle Member Attributes TLV field of the OSPF packet comprises a Member Link attribute subtype length value sub-TLV field, and wherein the changed state information and the slice identifier of the first network slice are carried in the Member Link attribute sub-TLV field.

32. The apparatus of claim 29, wherein the changed State information and the slice identifier of the first network slice are carried in a Link-State Network Layer Reachability Information (NLRI) field of the BGP packet.

33. The apparatus of claim 32, wherein the Link-State NLRI field comprises a Link descriptor links Descriptors field, and wherein the changed State information and a slice identification of the first network slice are carried in the Link Descriptors field.

34. The apparatus according to any of claims 24-33, wherein the first packet is configured to process a forwarding path according to the changed state information of the network interface, and the forwarding path is a forwarding path corresponding to an identifier of the network interface and a slice identifier of the first network slice.

35. The apparatus of any one of claims 24-34,

the sending unit is configured to issue the first packet to a control device or a second network device.

36. A forwarding path processing apparatus, applied to a target device, the apparatus comprising:

a receiving unit, configured to receive a first packet from a first network device, where the first packet carries an identifier of the network interface, changed state information of the network interface, and a slice identifier of a first network slice, and the changed state information indicates a changed state of the network interface belonging to the first network slice;

and the processing unit is used for processing a forwarding path according to the changed state information, wherein the forwarding path is a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice.

37. The apparatus of claim 36,

the processing unit is configured to, in response to the changed state information indicating that the network interface deletes the configuration of the first network slice, or in response to the changed state information indicating that the network interface changes from a normal state to a fault state, search for path information of a forwarding path corresponding to an identifier of the network interface and a slice identifier of the first network slice;

the processing unit is further configured to delete the path information of the forwarding path or set the path information of the forwarding path as invalid; or, recalculating the forwarding path corresponding to the slice identifier of the first network slice according to other network interfaces except the network interface belonging to the first network slice.

38. The apparatus of claim 36,

the processing unit is configured to respond to the changed state information indicating that the network interface newly configures the first network slice, generate a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice, and store a correspondence between the identifier of the network interface, the slice identifier of the first network slice, and the path information of the forwarding path.

39. The apparatus of claim 36,

the processing unit is configured to generate a forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice in response to the changed state information indicating that the network interface is restored from the fault state to the normal state, and store a corresponding relationship between the identifier of the network interface, the slice identifier of the first network slice, and the path information of the forwarding path; or, setting the forwarding information of the forwarding path corresponding to the identifier of the network interface and the slice identifier of the first network slice as valid.

40. The apparatus of any of claims 36-39, wherein the first packet is an intermediate system to intermediate system ISIS packet, an Open Shortest Path First (OSPF) packet, or a Border Gateway Protocol (BGP) packet.

41. The apparatus of claim 40, wherein the changed state information and the slice identifier of the first network slice are carried in a two-layer Bundle Member attribute L2Bundle Member Attributes Type Length Value (TLV) field of the ISIS packet or the OSPF packet.

42. The apparatus of claim 41, wherein an L2Bundle number entries TLV field of the ISIS message comprises a two-layer Bundle Attribute description L2Bundle Attribute Descriptors field, and wherein the changed state information and the slice identifier of the first network slice are carried in the L2Bundle Attribute Descriptors field.

43. The apparatus according to claim 41, wherein the L2Bundle number Attributes TLV field of the OSPF packet includes a Member Link attribute Link attribute subtype Length value sub-TLV field, and the changed state information and the slice identifier of the first network slice are carried in the Member Link attribute sub-TLV field.

44. The apparatus of claim 41, wherein the changed State information and the slice identifier of the first network slice are carried in a Link-State Network Layer Reachability Information (NLRI) field of the BGP message.

45. The apparatus of claim 44, wherein the Link-State NLRI field comprises a Link descriptor Link Descriptors field, and wherein the changed State information and a slice identification of the first network slice are carried in the Link Descriptors field.

46. The apparatus of any of claims 36-45, wherein the target device is a control device or a second network device.

47. A network device, characterized in that it comprises a processor chip and a memory for storing instructions or program code, the processor chip being adapted to call up and run said instructions or program code from the memory to execute the message issuing method according to any one of claims 1 to 12.

48. An apparatus, comprising a processor chip and a memory for storing instructions or program code, the processor chip being configured to retrieve from the memory and execute the instructions or program code to perform the forwarding path processing method of any of claims 13-23.

49. A computer-readable storage medium comprising instructions, program or code which, when executed on a computer, causes the computer to perform the message distribution method of any one of claims 1-12 or the forwarding path processing method of any one of claims 13-23.