CN119276697A

CN119276697A - Network configuration method, device and system

Info

Publication number: CN119276697A
Application number: CN202310835243.6A
Authority: CN
Inventors: 张大胜; 盛成; 杨平安; 丁兆坤
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2023-07-07
Filing date: 2023-07-07
Publication date: 2025-01-07

Abstract

A network configuration method, device and system belong to the field of network technology. The method includes: a network node determines that a forwarding node on a transmission path of a data stream supports a service characteristic; the network node performs service configuration on a port of the forwarding node based on the service characteristic. In the present application, the network node performs service configuration on a forwarding node on a transmission path of a data stream, which can simplify the service configuration process and reduce the difficulty of service configuration.

Description

Network configuration method, device and system

Technical Field

The present application relates to the field of network technologies, and in particular, to a network configuration method, device, and system.

Background

In order to ensure the transmission performance of the data stream, service configuration needs to be performed on a forwarding node for forwarding the data stream in the communication network, so that the forwarding node performs service operation on the data stream in the process of forwarding the data stream. For example, it is necessary to configure a forwarding node for forwarding a data flow in a communication network with a flow detection service, so that the forwarding node performs a flow detection operation on the data flow during forwarding of the data flow.

Currently, forwarding nodes are typically manually configured for traffic. However, manual configuration is difficult and the configuration process is complex.

Disclosure of Invention

The application provides a network configuration method, a device and a system, wherein a network node performs service configuration on a forwarding node on a transmission path of a data stream, so that the service configuration process can be simplified, and the service configuration difficulty can be reduced. The technical scheme of the application is as follows.

In a first aspect, a network configuration method is provided, the method comprising the steps that a network node determines that a forwarding node on a transmission path of a data stream supports service characteristics, and the network node performs service configuration on a port of the forwarding node based on the service characteristics. After the network node performs service configuration on the port, the forwarding node may perform service operation corresponding to the service characteristic on the port for the data stream in a process of forwarding the data stream.

According to the technical scheme provided by the application, the network node performs service configuration on the port of the forwarding node based on the service characteristics supported by the forwarding node on the transmission path of the data stream, and compared with the existing manual configuration scheme, the service configuration process can be simplified, and the service configuration difficulty is reduced.

Optionally, the network node performing service configuration on the port of the forwarding node based on the service characteristic includes the network node acquiring a configuration parameter of the port based on the service characteristic, and the network node performing the service configuration on the port by using the configuration parameter.

Optionally, the network node performing service configuration on the port by using the configuration parameter includes that the network node sends a configuration message to the forwarding node, where the configuration message includes the configuration parameter. After the forwarding node receives the configuration message, the forwarding node adopts the configuration parameters included in the configuration message to carry out service configuration on the port of the forwarding node.

According to the technical scheme provided by the application, the network node sends the configuration message to the forwarding node on the transmission path of the data stream, so that the forwarding node can conveniently carry out service configuration on the port of the forwarding node by adopting the configuration parameters included in the configuration message, and corresponding service operation on the data stream is carried out on the port in the process of forwarding the data stream by the forwarding node.

Optionally, the configuration message is a generic autonomous signaling protocol (generic autonomic signaling protocol, GRASP) message, which includes a configuration object key pair field for carrying the configuration parameter, or a very simple discovery protocol (extremely lean discovery protocol, XLDP) message, which XLDP message includes a packet data unit (PACKET DATA unit, PDU) including a type length value (TAG LENGTH value, TLV) field for carrying the configuration parameter. That is, the network node sends configuration information to the forwarding node through the GRASP or XLDP. Wherein GRASP and XLDP are both trusted protocols.

According to the technical scheme provided by the application, the network node sends the configuration information to the forwarding node on the transmission path of the data stream through the GRASP or XLDP, so that the reliability and the safety of the transmission of the configuration information between the network node and the forwarding node can be ensured.

Optionally, the configuration parameter includes enabling indication information and an identifier of the port, where the enabling indication information is used to indicate a service function corresponding to the service feature enabled for the port.

According to the technical scheme provided by the application, the configuration parameters of the port of the forwarding node comprise the enabling indication information and the identification of the port, so that the forwarding node can enable the service function corresponding to the service characteristic for the port according to the enabling indication information, and the forwarding node can perform the service operation corresponding to the service characteristic for the data stream in the process of forwarding the data stream through the port.

Optionally, before the network node performs service configuration on the port of the forwarding node based on the service characteristic, the method further includes the network node receiving path information sent by the forwarding node, where the path information includes an identifier of the port, and the network node obtaining the port on the transmission path based on the path information (i.e., the network node identifies the port on the transmission path based on the path information). Wherein the path information is obtained based on a message (e.g., a data message or a detection message) of the data stream in the process of forwarding the data stream by the forwarding node.

According to the technical scheme provided by the application, the forwarding node on the transmission path of the data stream acquires the path information of the data stream based on the message of the data stream in the process of forwarding the data stream, and sends the path information to the network node, so that the network node can determine the port on the transmission path in the forwarding node according to the path information, and further carry out service configuration on the port.

Optionally, the port is a port in the forwarding node for receiving or transmitting the data flow, and the path information further comprises at least one of an indication information of the data flow, a flow direction of the data flow in the forwarding node, the flow direction being a direction from the port in the forwarding node for receiving the data flow to the port in the forwarding node for transmitting the data flow. The indication information of the data flow may be information that an internet protocol version 6 (internet protocol version, ipv 6) flow label (flow lable), an application-aware network (APN) Identifier (ID), a quintuple, a triplet, a tuple, or the like can be used to indicate the data flow.

According to the technical scheme provided by the application, the path information sent by the forwarding node to the network node comprises the indication information of the data flow, so that the network node can determine the data flow corresponding to the path information according to the indication information of the data flow (namely, determine that the path information is the path information of the data flow). Because the path information sent by the forwarding node to the network node includes the flow direction of the data stream in the forwarding node, the network node can restore the transmission path of the data stream in the scenes of multipath load balancing, inconsistent round trip paths, dynamic path switching and the like. That is, in a scenario where the data flow has multiple load sharing paths, inconsistent round trip paths, or dynamically switched transmission paths, the network node may restore the transmission path of the data flow based on the path information including the flow direction sent by the forwarding node on the transmission path of the data flow.

Optionally, the path information further includes indication information of the forwarding node, and the method further includes the network node acquiring the forwarding node on the transmission path based on the path information (i.e., the network node identifies the forwarding node on the transmission path based on the path information), and the network node performing service configuration on the forwarding node based on the service characteristic.

According to the technical scheme provided by the application, the forwarding node on the transmission path of the data stream acquires the path information of the data stream based on the message of the data stream in the process of forwarding the data stream, and sends the path information to the network node, so that the network node can determine the forwarding node on the transmission path according to the path information, and further perform service configuration on the forwarding node on the transmission path.

Optionally, the method further comprises the step that the network node determines the transmission path according to the path information sent by the forwarding node on the transmission path, and the step that the network node presents the transmission path.

According to the technical scheme provided by the application, the network node presents the transmission path of the data stream, so that the visualization of the transmission path of the data stream can be realized, and the user can analyze the transmission path of the data stream, the transmission condition of the data stream and the like conveniently.

Optionally, the network node determining that the forwarding node on the transmission path of the data stream supports the service characteristic includes the network node determining that the forwarding node supports the service characteristic by sending a probe message. I.e. the network node determines by probing that the forwarding node supports the traffic characteristics.

According to the technical scheme provided by the application, the network node determines the service characteristics supported by the forwarding node on the transmission path of the data stream through network detection, so that the network node can conveniently perform service configuration on the forwarding node based on the service characteristics supported by the forwarding node on the transmission path.

Optionally, the probe packet is an internet control packet protocol (internet control message protocol, ICMP) packet, where the ICMP packet includes a type field and a code field, where the type field and the code field are used to indicate whether the forwarding node supports the service characteristic, or the probe packet is a GRASP packet, where the GRASP packet includes a configuration object key value pair field, where the configuration object key value pair field is used to indicate whether the forwarding node supports the service characteristic, or the probe packet is a XLDP packet, where the XLDP packet includes a PDU, where the PDU includes a TLV field, and where the TLV field is used to indicate whether the forwarding node supports the service characteristic. The ICMP message may be an ICMP message based on internet protocol 4 th edition (internet protocol version, IPv 4) or an ICMP message based on IPv6, where the ICMP message based on IPv4 is also referred to as ICMPv4 message, and the ICMP message based on IPv6 is also referred to as ICMPv6 message.

According to the technical scheme provided by the application, the network node detects the service characteristics supported by the forwarding node on the transmission path of the data stream through ICMP, GRASP or XLDP, so that the network node can conveniently acquire the service characteristics supported by the forwarding node. In addition, since the GRASP and XLDP are both trusted protocols, the network node can ensure the reliability and safety of the communication between the network node and the forwarding node on the transmission path by detecting the service characteristics supported by the forwarding node on the transmission path of the data stream through the GRASP and the XLDP.

Optionally, the type of the service characteristic supported by the previous hop node or the next hop node of the forwarding node is different from the type of the service characteristic supported by the forwarding node, and the configuration parameter further includes characteristic conversion information, where the characteristic conversion information is used to indicate a type conversion of the service characteristic.

According to the technical scheme provided by the application, as the configuration parameters of the port of the forwarding node comprise the characteristic conversion information, after the forwarding node adopts the configuration parameters to carry out service configuration on the port, the forwarding node can carry out type conversion of the service characteristics on the data stream based on the characteristic conversion information in the process of forwarding the data stream through the port, so that services corresponding to the service characteristics of different types are opened (or called splicing and communication) in the forwarding node.

Optionally, the network node is a control node or a head node of the transmission path. That is, in the present application, the forwarding node on the transmission path of the data stream may be configured for traffic by the control node or the head node of the transmission path.

The technical scheme provided by the application is that the scheme of carrying out service configuration on the forwarding nodes on the transmission path by the head node of the transmission path of the data stream is a distributed configuration scheme, and the distributed configuration scheme is suitable for network scenes without control nodes, cross-domain network scenes, large-scale network scenes and the like. The scheme of carrying out service configuration on the forwarding nodes on the transmission path of the data stream by the control node is a centralized configuration scheme, and the centralized configuration scheme is suitable for a centralized management scene with the control node.

Optionally, the service characteristic is an end-to-end service characteristic. Therefore, the technical scheme provided by the application supports end-to-end service configuration.

Optionally, the traffic characteristics include any one of a flow-following detection characteristic and a slice characteristic. Therefore, the technical scheme of the application is suitable for the stream-following detection service scene and the slice service scene, and the network node can carry out service configuration on the forwarding node in the stream-following detection service scene and the slice service scene, thereby simplifying the configuration process of the stream-following detection service, the slice service and the like and reducing the configuration difficulty.

Optionally, the on-stream detection characteristics include on-stream information telemetry (in-situ flow information telemetry, IFIT) characteristics, network Bao Shouheng algorithm (packet conservation algorithm for internet, IPCA) characteristics, and the slice characteristics include flexible ethernet (flexible ethernet, flexE) based slice characteristics, channelized sub-interface (channelized sub-interface) based slice characteristics, flexible channel (FlexChannel) based slice characteristics.

In a second aspect, there is provided a network configuration apparatus comprising means for performing the method as provided in the first aspect or any of the alternatives of the first aspect. The modules in the network configuration device may be implemented based on software, hardware, or a combination of software and hardware, and the modules may be arbitrarily combined or divided based on the specific implementation.

In a third aspect, there is provided a network configuration device comprising a memory for storing a computer program and a processor for executing the computer program stored in the memory to cause the network configuration device to perform a method as provided in the first aspect or any of the alternatives of the first aspect.

In a fourth aspect, there is provided a network configuration device comprising a main control board and an interface board for implementing the method as provided in the first aspect or any of the alternatives of the first aspect.

In a fifth aspect, a network configuration system is provided, the network configuration system comprising a network node and a forwarding node, the network node comprising the network configuration device as provided in the second or third aspect above, the network node being configured to perform service configuration on the forwarding node.

In a sixth aspect, there is provided a computer readable storage medium having stored therein a computer program which when executed implements a method as provided in the above first aspect or any of the alternatives of the first aspect.

In a seventh aspect, there is provided a computer program product comprising a program or code which when executed implements a method as provided in the first aspect or any of the alternatives of the first aspect.

In an eighth aspect, there is provided a chip comprising programmable logic circuitry and/or program instructions, the chip being operable to implement a method as provided in the first aspect or any of the alternatives of the first aspect.

The technical effects of the second to eighth aspects may refer to the first aspect or any optional implementation manner of the first aspect, which is not described herein.

Drawings

FIG. 1 is a network scenario diagram;

FIG. 2 is a schematic diagram of a communication network provided by an embodiment of the present application;

FIG. 3 is a schematic diagram of another communication network provided by an embodiment of the present application;

FIG. 4 is a schematic diagram of yet another communication network provided by an embodiment of the present application;

fig. 5 is a flowchart of a network configuration method according to an embodiment of the present application;

Fig. 6 is a schematic diagram of an ICMPv4 packet according to an embodiment of the present application;

fig. 7 is a schematic diagram of an ICMPv6 packet according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a GRASP message according to an embodiment of the present application;

FIG. 9 is a schematic diagram of XLDP messages provided in an embodiment of the present application;

fig. 10 is a schematic diagram of a network configuration device according to an embodiment of the present application;

fig. 11 is a schematic diagram of another network configuration device according to an embodiment of the present application;

fig. 12 is a schematic diagram of still another network configuration device according to an embodiment of the present application.

Detailed Description

Embodiments of the present application will be further described below with reference to the accompanying drawings.

In order to ensure the transmission performance of the data stream, service configuration needs to be performed on forwarding nodes (such as a head node, an intermediate node and a tail node) for forwarding the data stream in the communication network, so that the forwarding nodes perform service operation on the data stream in the process of forwarding the data stream. For example, in order to provide service-level agreements (SLAs) -LEVEL AGREEMENT for a data flow with visibility, a forwarding node in a communication network for forwarding the data flow needs to be configured with a flow detection service, so that the forwarding node performs flow detection on the data flow during forwarding of the data flow by the forwarding node. For another example, in order to guarantee deterministic quality of a data flow, a forwarding node in a communication network for forwarding the data flow needs to be configured with a slice service, so that the forwarding node forwards the data flow through a corresponding network slice.

The current automatic configuration scheme cannot perform service configuration, but the forwarding node for forwarding the data stream is manually configured. For example, forwarding nodes through which the data flow passes are manually identified and traffic configuration is performed on these forwarding nodes. However, the difficulty of manual configuration is relatively high, the configuration process is complex, the workload is relatively high, and particularly in the scenes of business end-to-end (E2E) cross-park network, cross-operator network, multi-path, multi-branch interconnection, business cloud, and the like, the networking of the data flow is relatively complex, and the difficulty and the workload of manually identifying forwarding nodes of the data flow and performing business configuration on the forwarding nodes are relatively high. For example, in the network scenario shown in fig. 1, the data flows transmitted between the campus network 1 and the campus network 2 need to pass through the forwarding nodes in the campus network 1, the forwarding nodes in the internet/private network/WAN (i.e., the internet or private network or WAN), and the forwarding nodes in the campus network 2, the data flows transmitted between the campus network 1 and the cloud network need to pass through the forwarding nodes in the campus network 1, the forwarding nodes in the internet/private network/WAN, and the forwarding nodes in the cloud network, the data flows transmitted between the campus network 2 and the cloud network need to pass through the forwarding nodes in the campus network 2, the forwarding nodes in the internet/private network/WAN, and the forwarding nodes in the cloud network, and the networking through which the data flows pass is complex, and the difficulty and the workload of manually identifying the forwarding nodes and manually configuring the services are large, and even difficult to implement.

The embodiment of the application provides a network configuration scheme, in which a control node or a head node of a transmission path of a data stream carries out service configuration on a forwarding node on the transmission path, so that the forwarding node carries out corresponding service operation on the data stream in the process of forwarding the data stream, thereby simplifying the service configuration process and reducing the service configuration difficulty.

The technical scheme of the application is described below, and the application scene of the application is described first.

An application scenario of an embodiment of the present application provides a communication network, which is a network domain or which comprises at least two network domains. For example, the communication network includes a metropolitan area network, a wide area network (wide area network, WAN), a campus network, a cloud network, the internet, a private network, a data center network (DATA CENTER network, DCN), and the like. The communication network includes a plurality of network nodes, which are communicatively coupled. In one embodiment, the plurality of network nodes are forwarding nodes for forwarding messages. In another embodiment, the plurality of network nodes includes a control node and a forwarding node for forwarding the message, where the control node is configured to manage and control the forwarding node.

The forwarding node may be a physical switch, a physical router, a virtual switch created in a physical device, a virtual router, etc. The types of forwarding nodes in the communication network are the same or different, e.g. the forwarding nodes in the communication network are all switches or routers, or part of the forwarding nodes are switches and part of the forwarding nodes are routers. The forwarding nodes in the communication network comprise edge nodes located at edges of the communication network and non-edge nodes connected between different edge nodes, according to the deployment location. The control node can be a functional module deployed in a server, or a server cluster formed by a plurality of servers, or a cloud computing service center, and integrates functions of network management, service control, network analysis and the like. The control node is also called a control device, a network management node, a network management device, a network manager, a network controller, etc.

In an embodiment of the application, the communication network comprises a transmission path for transmitting a data stream, and the forwarding nodes on the transmission path comprise a head node (head node), a tail node (end node) and an intermediate node (transit node) between the head node and the tail node. The head node and the tail node may each be edge nodes in the communication network, the intermediate nodes are non-edge nodes in the communication network, the number of intermediate nodes on the transmission path may be one or more, and in some embodiments the transmission path may include only the head node and the tail node, and no intermediate nodes. The designations of network nodes, forwarding nodes, transmission paths, head nodes, intermediate nodes, tail nodes, etc. are merely exemplary. A network node may also be referred to as a network device, a network element, etc. Forwarding nodes may also be referred to as forwarding devices, gateway nodes, gateway devices, routing nodes, routing devices, etc. The transmission path may also be referred to as a forwarding path, a communication tunnel, etc. The head node may also be referred to as a head node device, a head node device, etc. Intermediate nodes may also be referred to as intermediaries, transit nodes, transit devices, etc. The tail node may also be referred to as a tail node device.

In the embodiment of the application, the control node or the head node of the transmission path of the data stream carries out service configuration on the forwarding node on the transmission path, so that the forwarding node on the transmission path carries out corresponding service operation on the data stream in the process of forwarding the data stream. For example, the forwarding node on the transmission path generates path information in the process of forwarding the data stream, and sends the path information to the control node or the head node, and the control node or the head node determines a port on the transmission path (for example, determines the forwarding node on the transmission path and a port in the forwarding node for forwarding the data stream) according to the path information sent by the forwarding node on the transmission path, and the control node or the head node performs service configuration on the port through which the data stream passes. The services of the embodiment of the application comprise slicing services, stream following detection services and the like, and the corresponding service operations comprise forwarding operations based on network slicing, stream following detection operations and the like. The stream detection service comprises stream information telemetry (in-situ flow information telemetry, IFIT) service, network Bao Shouheng algorithm (packet conservation algorithm for internet, IPCA) service and the like. Slice traffic includes flexible ethernet (flexible ethernet, flexE) based slice traffic, channelized sub-interface (channelized sub-interface) based slice traffic, flexible channel (FlexChannel) based slice traffic, and the like. For convenience of description, the FlexE-based slice service is hereinafter referred to as FlexE service, the channelized sub-interface-based slice service is hereinafter referred to as channelized sub-interface service, and the FlexChannel-based slice service is hereinafter referred to as FlexChannel service.

Referring to fig. 2, a schematic diagram of a communication network according to an embodiment of the application is shown. The communication network comprises forwarding nodes 101-109, wherein the forwarding nodes 101-109 are in the same network domain or the forwarding nodes 101-109 are in different network domains. Forwarding nodes 101, 105, 106 are edge nodes in the communication network and forwarding nodes 102-104, 107-109 are non-edge nodes in the communication network. The communication network includes a transmission path S1 for transmitting the data stream 1, a forwarding node 101 is a head node of the transmission path S1, a forwarding node 105 is a tail node of the transmission path S1, and forwarding nodes 102 to 104 are intermediate nodes on the transmission path S1. For example, the forwarding nodes 102 to 105 generate path information in the process of forwarding the packet of the data stream 1 (for example, the forwarding nodes 102 to 105 generate path information based on the packet of the data stream 1 forwarded in a period of time when the data stream 1 starts to be transmitted in the transmission path S1), and send the path information to the forwarding node 101, and the forwarding node 101 determines, according to the path information sent by the forwarding nodes 102 to 105, a port located on the transmission path S1 in the forwarding nodes 102 to 105 (for example, determines the forwarding nodes 101 to 105 on the transmission path S1 and a port used for forwarding the data stream 1 in the forwarding nodes 101 to 105), so that the forwarding node 101 identifies a port through which the data stream 1 passes, and further the forwarding node 101 performs service configuration on the port through which the data stream 1 passes.

In some embodiments, the communication network includes a plurality of transmission paths for transmitting the data stream 1, where the plurality of transmission paths are used for carrying out load sharing on the data stream 1, head nodes of the plurality of transmission paths are identical, and the head nodes identify a port through which the data stream 1 passes according to path information sent by forwarding nodes on the plurality of transmission paths, so as to carry out service configuration on the port through which the data stream 1 passes. In this embodiment, the ports through which data stream 1 passes are on the multiple transmission paths. Optionally, the tail nodes of the plurality of transmission paths are identical. Referring to fig. 3, a schematic diagram of another communication network provided by the embodiment of the present application is shown, and the architecture of the communication network is the same as that of the communication network shown in fig. 2, wherein the communication network shown in fig. 3 includes a transmission path S1 and a transmission path S2 for transmitting a data stream 1, a forwarding node 101 is a head node of the transmission path S1 and the transmission path S2, a forwarding node 105 is a tail node of the transmission path S1 and the transmission path S2, forwarding nodes 102, 107-109 are intermediate nodes on the transmission path S2, and forwarding nodes 102, 107-109 are intermediate nodes on the transmission path S2. In an example, in a process of forwarding a packet of the data stream 1 by the forwarding nodes 102 to 105 and 107 to 109 (for example, in a period of time when the data stream 1 starts to be transmitted on the transmission path S1 and the transmission path S2, the forwarding nodes 102 to 105 and 107 to 109 generate path information based on the packet of the data stream 1 forwarded in the period of time), and send the path information to the forwarding node 101, the forwarding node 101 determines a port on the transmission path S1 (for example, determines a port on the transmission path S1 for forwarding the data stream 1 from the forwarding nodes 101 to 105 and a port on the transmission path 101 to 105 for forwarding the data stream 1 from the forwarding nodes 101 to 105) and a port on the transmission path S2 (for example, determines a port on the transmission path S2 for forwarding the data stream 1 from the forwarding nodes 101 to 102, 107 to 109 and 105), so that the forwarding node 101 identifies a port on which the data stream 1 passes, and the forwarding node 101 performs service configuration on a port on which the data stream 1 passes.

The application scenario shown in fig. 2 and fig. 3 is illustrated by taking the service configuration of the port through which the data stream 1 passes by the head node as an example, and in the case that the communication network includes the control node, the control node may perform the service configuration of the port through which the data stream 1 passes. For example, please refer to fig. 4, which illustrates a schematic diagram of still another communication network according to an embodiment of the present application. The communication network comprises a control node 100 and forwarding nodes 101-109, wherein the control node 100 is in communication connection with the forwarding nodes 101-109, and the control node 100 is used for managing and controlling the forwarding nodes 101-109. The communication network includes a transmission path S1 and a transmission path S2 for transmitting a data stream 1, a forwarding node 101 is a head node of the transmission path S1 and the transmission path S2, a forwarding node 105 is a tail node of the transmission path S1 and the transmission path S2, forwarding nodes 102 to 104 are intermediate nodes on the transmission path S1, and forwarding nodes 102 and 107 to 109 are intermediate nodes on the transmission path S2. In an example, in a process of forwarding a packet of the data stream 1 by the forwarding nodes 101 to 105 and 107 to 109 (for example, in a period of time when the data stream 1 starts to be transmitted on the transmission path S1 and the transmission path S2, the forwarding nodes 102 to 105 and 107 to 109 generate path information based on the packet of the data stream 1 forwarded in the period of time), and send the path information to the control node 100, the control node 100 determines a port on the transmission path S1 (for example, determines a port on the transmission path S1 for forwarding the data stream 1 from the forwarding nodes 101 to 105 and a port on the transmission path 101 to 105 for forwarding the data stream 1 from the forwarding nodes 101 to 105) and a port on the transmission path S2 (for example, determines a port on the transmission path S2 for forwarding the data stream 1 from the forwarding nodes 101 to 102, 107 to 109 and 105), so that the control node 100 identifies a port through which the data stream 1 passes, and further controls the node 100 to perform service configuration on the port through which the data stream 1 passes. In fig. 4, for brevity, only the connection lines between the control node 100 and the forwarding nodes 101 to 104 are shown, and in practical application, the control node 100 and the forwarding nodes 101 to 109 are all in communication connection. In addition, this paragraph describes the control node 100 as an example of traffic configuration for the port through which the data stream 1 passes, and in the network scenario shown in fig. 4, the forwarding node 101 may also identify the port through which the data stream 1 passes and perform traffic configuration for the port through which the data stream 1 passes, which is not limited in the embodiment of the present application.

In the embodiment of the application, the scheme of carrying out service configuration by the head node is a distributed configuration scheme, and the scheme of carrying out service configuration by the control node is a centralized configuration scheme. In the distributed configuration scheme, the head node performs service configuration on ports on a transmission path of a data stream based on a general autonomous signal protocol (generic autonomic signaling protocol, GRASP), a very simple discovery protocol (extremely lean discovery protocol, XLDP), and the like. In the centralized configuration scheme, the control node performs service configuration on ports on a transmission path of a data stream based on protocols such as a simple network management protocol (simple network management protocol, SNMP), a network configuration protocol (network configuration protocol, netcon), and the like. Compared with a centralized configuration scheme, the distributed configuration scheme is suitable for a network scene without control nodes, a cross-domain network scene, a large-scale network scene and the like. For example, about 95% of soho network scenes have no control nodes. Because the information of the GRASP, the XLDP and other protocols is transferred quickly, and is usually in the second level or the millisecond level, the distributed configuration scheme is suitable for a large-scale network scene. Wherein soho English is small office or home office, and Chinese is small office or home office.

The above description about the application scenario of the present application is only used as an example, and is not used to limit the technical solution of the present application. In the implementation process, the number of network nodes and the relationship between the network nodes in the application scenario can be configured according to the need, which is not limited by the embodiment of the present application.

The above description is about the application scenario of the present application, and the following description is made of the method embodiment of the present application.

Fig. 5 is a flowchart of a network configuration method according to an embodiment of the present application. The network configuration method is performed by a network node, which is a control node or a head node of a transmission path of a data stream. For example, the network node is a network node 101 in the communication network shown in fig. 2 to 4 or a control node 100 in the communication network shown in fig. 4. For convenience of description, the network node for performing the network configuration method will be hereinafter described as "network node a", and the data flow will be described as "data flow a". Referring to fig. 5, the method includes the following steps S501 to S502.

S501, the network node A determines that the forwarding node A on the transmission path of the data stream A supports the service characteristic A.

Wherein the forwarding node a is any forwarding node on the transmission path of the data stream a, e.g. forwarding node a is an intermediate node on the transmission path. The service characteristic a may be an end-to-end service characteristic, where the service characteristic a corresponds to an end-to-end service, and the service characteristic a is applicable to hop-by-hop processing of the end-to-end service. Optionally, the traffic characteristic a includes at least one of a stream-following detection characteristic including at least one of an IPCA characteristic and an IFIT characteristic, and the slice characteristic includes at least one of a FlexE-based slice characteristic, a channelized sub-interface-based slice characteristic, and a FlexChannel-based slice characteristic, so the traffic characteristic a is any one of an IPCA characteristic, an IFIT characteristic, a FlexE-based slice characteristic, a channelized sub-interface-based slice characteristic, and a FlexChannel-based slice characteristic. Wherein the stream-following detection characteristic corresponds to the stream-following detection service, and the slice characteristic corresponds to the slice service. For example, IPCA characteristics correspond to IPCA traffic, IFIT characteristics correspond to IFIT traffic, flexE-based slice characteristics correspond to FlexE-based slice traffic, channelized sub-interface-based slice characteristics correspond to channelized sub-interface-based slice traffic, flexChannel-based slice characteristics correspond to FlexChannel-based slice traffic. For convenience of description, hereinafter, the slice characteristic based on FlexE will be referred to as FlexE characteristic, the slice characteristic based on the channelization sub-interface will be referred to as channelization sub-interface characteristic, the slice characteristic based on FlexChannel will be referred to as FlexChannel characteristic, the slice traffic based on FlexE will be referred to as FlexE traffic, the slice traffic based on the channelization sub-interface will be referred to as channelization sub-interface traffic, and the slice traffic based on FlexChannel will be referred to as FlexChannel traffic.

In an alternative embodiment, the network node a determines that the forwarding node a supports the service characteristic a by sending a probe message. For example, the network node a sends a detection message to the forwarding node a to detect whether the forwarding node a supports the service characteristic a, and the network node a determines that the forwarding node a supports the service characteristic a according to the detection result. In one embodiment, the network node a is a control node, and the network node a sends a probe packet to the forwarding node a based on the first protocol, where the probe packet is a packet based on the first protocol (abbreviated as a first protocol packet). In another embodiment, the network node a is a head node of a transmission path of the data flow a, and the network node a sends a probe packet to the forwarding node a based on the second protocol, where the probe packet is a packet based on the second protocol (referred to as a second protocol packet for short). In this other embodiment, the network node a sends the probe message to the forwarding node a based on the command line input by the user, or the network node a sends the probe message to the forwarding node a according to the instruction of the control node. The first protocol includes, but is not limited to, simple network management protocol (simple network management protocol, SNMP), network configuration protocol (network configuration protocol, netcon), and the corresponding first protocol message includes, but is not limited to, SNMP message, netcon message. The second protocol includes, but is not limited to, an internet control message protocol (internet control message protocol, ICMP), a generic autonomous signaling protocol (generic autonomic signaling protocol, GRASP), a very simple discovery protocol (extremely lean discovery protocol, XLDP), and the corresponding second protocol message is not limited to ICMP message, GRASP message, XLDP message.

The implementation manner of the network node a to detect whether the forwarding node a supports the service characteristic a is described in three embodiments below by taking the ICMP message, the GRASP message, or the XLDP message as an example.

In a first embodiment, the probe message is an ICMP message, and the ICMP message (i.e., the probe message) includes a type field and a code field, where the type field and the code field are used to indicate whether the probing forwarding node a supports the service characteristic a. For example, the type field and the code field are used to carry probe indication information to indicate whether the probe forwarding node a supports the traffic characteristics a.

The ICMP message may be an ICMPv4 message or an ICMPv6 message. The ICMPv4 message is shown in fig. 6, and the ICMPv6 message is shown in fig. 7. Referring to fig. 6, the ICMPv4 packet includes ICMP data, and an ICMP header and an IPv4 header sequentially encapsulated outside the ICMP data, where the length of the IPv4 header is typically 20-60 bytes, the length of the ICMP header is typically 4 bytes, and the value of a protocol field in the IPv4 header is "1" to indicate that the next header of the IPv4 header is an ICMP header. Referring to fig. 7, the ICMPv6 packet includes ICMP data, and an ICMP header, an IPv6 extension header, and an IPv6 header sequentially encapsulated outside the ICMP data, the length of the IPv6 header is typically 40 bytes, the length of the IPv6 extension header is variable, the length of the ICMP header is typically 4 bytes, and the value of the next header field in the IPv6 extension header is "58" to indicate that the next header of the IPv6 extension header is an ICMP header. Referring to fig. 6 and 7, in the ICMPv4 packet and the ICMPv6 packet, ICMP data includes a type field, a code field, a checksum field, a length field for ICMPv6 (the length field is reserved in the ICMPv4 packet), a length field for ICMPv4 (the length field is reserved in the ICMPv6 packet), various fields, an ICMP payload, an ICMP extension header, and n objects, n being a positive integer. The ICMP extension header includes a version field, a reserved (reseved) field, and a checksum field. Each of the n objects includes an object header and object data, the length of the object header is fixed, and the length of the object data is variable. In this embodiment, the type field and the code field are used to carry probe indication information to indicate probing of traffic characteristics, for example, whether probing forwarding node a supports traffic characteristics a. The meaning of other fields and headers in the ICMP message may refer to related art documents, and will not be described herein. Fig. 6 and 7 illustrate that ICMP data includes n objects, and ICMP data may not include objects, which is not limited in the present application.

As can be seen from the foregoing description, the traffic characteristic a is an IFIT characteristic, an IPCA characteristic, a FlexE characteristic, a channelized sub-interface characteristic, or a FlexChannel characteristic, and the probe indication information for probing whether the forwarding node a supports the traffic characteristic a is different according to the traffic characteristic a. For example, in the case where the probe packet is an ICMP packet, probe indication information (a value of a type field and a value of a code field) carried by the probe packet for probing the IPCA characteristic, the IFIT characteristic, the FlexE characteristic, the channelized sub-interface characteristic, and the FlexChannel characteristic are shown in table 1 below, respectively.

TABLE 1

Referring to table 1, the type field has a value of "200/201/205" (i.e., 200 or 201 or 205), and the code field has a value of "1", "2", "3", "4" or "5". In the case that the value of the type field is "200/201/205" and the value of the code field is "1", the type field and the code field are used for indicating that the IPCA characteristic is detected, the value of the type field "200/201/205" and the value of the code field "1" are detection indication information for indicating that the IPCA characteristic is detected, and in the case that the forwarding node a receives an ICMP message including the detection indication information, the forwarding node a determines whether the forwarding node a supports the IPCA characteristic according to the detection indication information, and feeds back to the network node a whether the forwarding node a supports the detection response message of the IPCA characteristic. In the case that the value of the type field is '200/201/205' and the value of the code field is '2', the type field and the code field are used for indicating that the IFIT characteristic is detected, the value '200/201/205' of the type field and the value '2' of the code field are detection indication information for indicating that the IFIT characteristic is detected, and in the case that the forwarding node a receives an ICMP message including the detection indication information, the forwarding node a determines whether the forwarding node a supports the IFIT characteristic according to the detection indication information and feeds back to the network node a whether the forwarding node a supports the detection response message of the IFIT characteristic. In the case that the value of the type field is "200/201/205" and the value of the code field is "3", the type field and the code field are used for indicating the probe FlexE characteristic, the value of the type field "200/201/205" and the value of the code field "3" are probe indication information for indicating the probe FlexE characteristic, and in the case that the forwarding node a receives an ICMP message including the probe indication information, the forwarding node a determines whether the forwarding node a supports the FlexE characteristic according to the probe indication information, and feeds back to the network node a whether the forwarding node a supports the probe response message of the FlexE characteristic. And so on.

In this first embodiment, the probe response message may be an ICMP message, as shown in fig. 6 and fig. 7, where the type field and the code field may be used to carry probe indication information for indicating a probe service characteristic (e.g., service characteristic a), and the reserved field in the ICMP message may be used to carry a probe result. The detection indication information carried by the detection response message is the same as the detection indication information carried by the corresponding detection message, for example, the value of the type field in the detection response message is the same as the value of the type field of the corresponding detection message, and the value of the code field in the detection response message is the same as the value of the code field of the corresponding detection message. The value of the reserved field in the probe response message is a first value (e.g., 1), which indicates that the probe result supports the corresponding service characteristic for the forwarding node a, and the value of the reserved field in the probe response message is a second value (e.g., 0), which indicates that the probe result does not support the corresponding service characteristic for the forwarding node a.

It should be noted that, in the case where the network node a is the head node of the transmission path of the data stream a, the user may trigger the network node a through the command line to detect whether the forwarding node a supports the service characteristic a. Moreover, the network node a and the forwarding node a may be the same node or different nodes (e.g., the forwarding node a is a remote node of the network node a), that is, the network node a may detect whether the node supports the service characteristic a or not, and may also detect whether the remote node supports the service characteristic a or not. For example, the command behavior "DISPLAY CAPACILITY [ primary feature ] [ secondary function ] [ submodule function or/RFC ]", which is used to detect whether the node supports the traffic feature a, is used to detect whether the remote node supports the traffic feature a, the command behavior "DISPLAY IPV/IPv 6 address capacility [ primary feature ] [ secondary function ] [ submodule function or/RFC ]", which is the IPv4/IPv6 address of the remote node, and the network node a sends a detection message (i.e., ICMP message) as shown in fig. 6 or fig. 7 to the remote node based on the command line, which is used to detect whether the remote node supports the traffic feature a, to detect whether the remote node supports the traffic feature a. In one example, a user inputs a command line "DISPLAY GENEVE SLICE FlexChannel" to network node a, which probes whether the node supports FlexChannel features based on the command line. In another example, the user inputs a command line "DISPLAY IFIT" to network node a, from which network node a detects whether the node supports the IFIT feature. In yet another example, the user inputs a command line "DISPLAY IPCA" to network node a, from which network node a detects whether the node supports IPCA features. In yet another example, a user inputs a command line "display xx.xx.xx.xx GENEVE SLICE FlexChannel" to network node a, which detects from the command line whether a remote node addressed "xx.xx.xx.xx" supports FlexChannel features. In yet another example, the user inputs the command line "DISPLAY YY:: YY IFIT" to network node a, which detects from the command line whether the far-end node with address "YY:: YY" supports the IFIT feature. In yet another example, a user inputs a command line "display xx.xx.xx.xx IPCA" to network node a, which detects from the command line whether a remote node addressed "xx.xx.xx.xx" supports IPCA features.

In a second embodiment, the probe message is a GRASP message, and the GRASP message (i.e. the probe message) includes a configuration object key pair field, where the configuration object key pair field is used to indicate whether the probe forwarding node a supports the service characteristic a, for example, the configuration object key pair field is used to carry probe indication information to indicate whether the probe forwarding node a supports the service characteristic a.

The GRASP message (i.e., probe message) is illustrated in fig. 8, for example. The GRASP message includes a signaling protocol message, a user datagram protocol (user datagram protocol, UDP) header, an Internet protocol (internet protocol, IP) header and an Ethernet (ETH) header which are sequentially encapsulated outside the signaling protocol message. The signaling protocol message includes a message type (MESSAGE TYPE, msg type) field, a session identifier (session identifier, session ID) field, a configuration object name (Obj name) field, a length (Len) field, and n configuration object key pair fields, where n is a positive integer. Each of the n configuration object key pair fields includes a configuration object key (Obj key) subfield and a configuration object value (Obj value) subfield. The length of the message type field is 1 byte, the length of the session identification field is 2 bytes, the length of the configuration object name field is 16 bytes, the length of the length field is 1 byte, the length of each configuration object key value pair field is 48 bytes, and the length of the configuration object key subfield and the length of the configuration object value subfield are 24 bytes, respectively. The type of the value of the session identification field is UINT16 (16-bit unsigned integer), and the type of each of the message type field, the configuration object name field, the length field, the configuration object key subfield, and the configuration object value subfield is UINT8 (8-bit unsigned integer). The message type field is used for carrying a message type, and in this embodiment of the present application, the message type is a request message (for example, a probe message) or a response message (for example, a response message), that is, a probe message used for detecting whether the forwarding node supports a service characteristic, and a probe response message corresponding to the probe message may be a GRASP message, and the probe message and the probe response message are distinguished by using the message type field. The session identification field is used to carry a session identification. The configuration object name field is used to carry the name of the configuration object. The length field is used to carry the number of configuration object key pair fields (i.e., n) in the GRASP message. Each of the n configuration object key value pair fields is configured to carry a configuration object key value pair, the configuration object key sub-fields in each of the configuration object key value pair fields are configured to carry keys of the configuration object key value pair, and the configuration object value sub-fields in each of the configuration object key value pair fields are configured to carry values of the configuration object key value pair. In the embodiment of the present application, at least one of the n configuration object key pair fields is used to carry probe indication information to indicate a probe service characteristic, for example, to indicate whether the probe forwarding node a supports the service characteristic a. the structures and meanings of the UDP header, the IP header, and the ETH header in the GRASP message may refer to related technical documents, which are not described herein.

For example, the service characteristic a is any one of the IFIT characteristic, the IPCA characteristic, the FlexE characteristic, the channelized sub-interface characteristic, and the FlexChannel characteristic, and in the case that the probe packet is a GRASP packet, the probe packet (i.e., the GRASP packet) carries probe instruction information for probing the IPCA characteristic, the IFIT characteristic, the FlexE characteristic, the channelized sub-interface characteristic, and the FlexChannel characteristic, as shown in table 2 below.

TABLE 2

Referring to table 2, a value "A1" of the message type field indicates that the type of the GRASP message is a probe message, and a value of the configuration object name field is "probe-follow-flow detection characteristic" or "probe slice characteristic". In the case where the value of the configuration object name field is "detect with stream detection characteristic", the value of the configuration object key subfield is "X1" or "X2", and "X1" is detection instruction information for instructing to detect IPCA characteristic and "X2" is detection instruction information for instructing to detect IFIT characteristic. In the case where the value of the configuration object name field is "probe slice characteristic", the value of the configuration object key subfield is "X3", "X4", or "X5", "X3" is probe instruction information for instructing the probe FlexE characteristic, "X4" is probe instruction information for instructing the probe channelized sub-interface characteristic, and "X5" is probe instruction information for instructing the probe FlexChannel characteristic. For example, when the forwarding node a receives a GRASP message with a message type field having a value of "A1" and a configuration object key subfield having a value of "X1", the forwarding node a determines whether the forwarding node a supports the IPCA feature according to the GRASP message, and feeds back to the network node a probe response message indicating whether the forwarding node a supports the IPCA feature. Under the condition that the forwarding node A receives the GRASP message with the value of the message type field of 'A1' and the value of the configuration object key subfield of 'X2', the forwarding node A determines whether the forwarding node A supports the IFIT characteristic or not according to the GRASP message and feeds back a detection response message whether the forwarding node A supports the IFIT characteristic or not to the network node A. When the forwarding node a receives a GRASP message with the value "A1" of the message type field and the value "X3" of the configuration object key subfield, the forwarding node a determines whether the forwarding node a supports FlexE features according to the GRASP message, and feeds back to the network node a whether the forwarding node a supports the probe response message with FlexE features. And so on. In this embodiment, the configuration object value subfield in the probe packet is an empty field, and does not carry any information, and in other embodiments, the configuration object value subfield may carry information, which is not limited in the embodiment of the present application.

In the second embodiment, the probe response message may be a GRASP message, and the configuration object key value subfield in the configuration object key value pair field may be used to carry the probe result. For example, a detection result is added to a configuration object value subfield of the detection message to obtain a detection response message corresponding to the detection message. The detection result and the detection indication information for indicating the detection service characteristics are located in the same configuration object key value pair field. For example, in the case where the probe response message is a GRASP message, the probe indication information for probing the IPCA characteristic, the IFIT characteristic, the FlexE characteristic, the channelized subinterface characteristic, and the FlexChannel characteristic carried by the probe response message and the corresponding probe result are shown in the following table 3 respectively.

TABLE 3 Table 3

Referring to table 3, the value "A2" of the message type field indicates that the type of the GRASP message is a response message (in this embodiment, a probe response message), the value of the configuration object name field is "probe follow-up detection characteristic" or "probe slice characteristic", the value of the configuration object key subfield is "X1", "X2", "X3", "X4" or "X5", the value of the configuration object value subfield is "1" or "0", the value of the configuration object key subfield is probe indication information for probing service characteristics, the value of the configuration object key subfield is a probe result of service characteristics, the value of the configuration object value subfield is "1" for indicating that the forwarding node a supports the corresponding service characteristics, and the value of the configuration object value subfield is "0" for indicating that the forwarding node a does not support the corresponding service characteristics. For example, for a certain configuration object key value pair field in a probe response message (i.e. a GRASP message), the probe response message is used for indicating that the forwarding node a supports the IPCA feature when the value of a configuration object key subfield in the configuration object key value pair field is "X1" and the value of a configuration object key subfield in the configuration object key value pair field is "1", the probe response message is used for indicating that the forwarding node a does not support the IPCA feature when the value of a configuration object key subfield in the configuration object key value pair field is "0", and is used for indicating that the forwarding node a supports the IFIT feature when the value of a configuration object key subfield in the configuration object key value pair field is "X2" and the value of a configuration object value subfield in the configuration object key value pair field is "1", and the probe response message is used for indicating that the forwarding node a does not support the IFIT feature when the value of a configuration object key subfield in the configuration object key value pair field is "X2". And so on. In this second embodiment, a value of the configuration object value subfield of "1" or "0" is merely exemplary, and in other embodiments, other values (e.g., 2~k) are employed to indicate whether the probed node supports the corresponding traffic characteristics. Based on the description of the second embodiment, a GRASP message can detect various service characteristics. For example, detection indication information for detecting different service characteristics is carried in different configuration object key value pair fields of one GRASP message to detect a plurality of different service characteristics.

In a third embodiment, the probe message is XLDP messages, and the XLDP messages include a PDU, where a TLV field in the PDU is used to indicate whether the probing forwarding node a supports the service characteristic a. For example, a TLV field in the PDU is used to carry probe indication information to indicate whether the probe forwarding node a supports the traffic feature a.

The XLDP message (i.e., probe message) is illustrated in fig. 9, for example. The XLDP packet includes a destination address (destination address, DA) field, a Source Address (SA) field, an ethernet type (ETH type) field, a version field, a message type (MESSAGE TYPE, msg type) field, XLDP PDU, and a frame check sequence (FRAME CHECK sequence, FCS) field. The XLDP PDU includes at least one level1 (L1) TLV field and at least one level2 (L2) TLV field, the L2TLV field being a sub-field in the L1 TLV field, and one L1 TLV field may include a plurality of L2TLV fields therein. Wherein, the length of the DA field and the length of the SA field are both 6 bytes, the length of the Ethernet type field is 2 bytes, the length of the version field and the length of the message type field are both 1 byte, the length of the FCS field is 4 bytes, and the length of XLDP PDU is variable. In XLDP PDU, the L1 TLV field and the L2TLV field each include a type subfield having a length of 7 bits, a length subfield having a length of 9 bits, and a value subfield having a length of 0 to 511 bytes. The DA field is used to carry the Destination Media Access Control (DMAC) address of the XLDP message. The SA field is used to carry the Source MEDIA ACCESS Control (SMAC) address of the XLDP message. The ethertype field is used to carry an ethertype, and the value of the ethertype field is "0x88DD". The version field is used to carry version information, and the value of the version field may be "0x1". The message type field is used to carry a message type, where the value of the message type field is "0x01", "0x03", or "0xFF", "0x01" is used to indicate that the message type is a heartbeat message (e.g. a heartbeat message), and "0xFF" is used to indicate that the message type is a channel message (e.g. a request message), and "0x03" is used to indicate that the message type is a response message (e.g. a response message), in this embodiment, the type of the probe message is a channel message, the value of the message type field of the probe message is "0xFF", the type of the probe response message is a response message, and the value of the message type field of the probe response message is "0x03". The FCS field is used to carry FCS. Optionally, at least one L1 TLV field in XLDP PDU is used to carry probe indication information to indicate a probe traffic characteristic, for example, to indicate whether probe forwarding node a supports traffic characteristic a.

For example, the service characteristic a is any one of the IFIT characteristic, the IPCA characteristic, the FlexE characteristic, the channelized sub-interface characteristic, and the FlexChannel characteristic, and in the case that the probe packet is a XLDP packet, the probe packet carries probe instruction information for probing the IPCA characteristic, the IFIT characteristic, the FlexE characteristic, the channelized sub-interface characteristic, and the FlexChannel characteristic, which are shown in table 4 below.

TABLE 4 Table 4

The L2 TLV field described in table 4 is a sub-field in the L1 TLV field described in table 4. Referring to table 4, the value "A1" of the message type field indicates XLDP that the type of message is a probe message (i.e., a channel message), and the value of the L1 TLV type field is "B1", "B2", "B3", "B4", or "B5". In the case that the value of the L1 TLV type field is "B1", the L1 TLV field is used to indicate that the IPCA characteristic is detected, the value "B1" of the L1 TLV type field is detection indication information used to indicate that the IPCA characteristic is detected, and in the case that the forwarding node a receives XLDP messages including the detection indication information, the forwarding node a determines whether the forwarding node a supports the IPCA characteristic according to the detection indication information, and feeds back to the network node a whether the forwarding node a supports the probe response message of the IPCA characteristic. In the case that the value of the L1 TLV type field is "B2", the L1 TLV field is used to indicate the probe IFIT characteristic, the value "B2" of the L1 TLV type field is probe indication information used to indicate the probe IFIT characteristic, and in the case that the forwarding node a receives XLDP packet including the probe indication information, the forwarding node a determines whether the forwarding node a supports the IFIT characteristic according to the probe indication information, and feeds back to the network node a whether the forwarding node a supports the probe response packet of the IFIT characteristic. In the case that the value of the L1 TLV type field is "B3", the L1 TLV field is used to indicate the probe FlexE characteristic, the value "B3" of the L1 TLV type field is probe indication information used to indicate the probe FlexE characteristic, and in the case that the forwarding node a receives a XLDP packet including the probe indication information, the forwarding node a determines whether the forwarding node a supports FlexE characteristic according to the probe indication information, and feeds back to the network node a whether the forwarding node a supports the probe response packet of FlexE characteristic. And so on. In this embodiment, the L2 TLV field in the probe message (i.e., XLDP message) is a null field. In some embodiments, the L2 TLV field may carry information, or the probe message does not include the L2 TLV field, which is not limited by embodiments of the present application.

In this third embodiment, the probe response packet may be XLDP packets, and the L2 TLV field may be used to carry the probe result. For example, the detection result of the service characteristic is carried in an L2 TLV field under an L1 TLV field used for indicating detection of the service characteristic in the detection message, so as to obtain a detection response message corresponding to the detection message. For example, in the case that the probe response message is XLDP, the probe indication information for probing the IPCA characteristic, the IFIT characteristic, the FlexE characteristic, the channelized sub-interface characteristic, and the FlexChannel characteristic carried by the probe response message and the corresponding probe result are shown in the following table 5.

TABLE 5

Referring to table 5, the value "A2" of the message type field indicates XLDP that the type of the message is a response message (in this embodiment, a probe response message), the value of the L1 TLV type field is "B1", "B2", "B3", "B4", or "B5", the value of the corresponding L2 TLV type field is "B11", "B21", "B31", "B41", or "B51", the values of the L2 TLV value fields are each "1" or "0", the value of the L1 TLV type field is probe indication information for the probed traffic characteristics, the value of the L2 TLV type field is used to indicate the type of the L2 TLV field, the value of the L2 TLV value field is a probe result of the traffic characteristics, the value "1" of the L2 TLV value field is used to indicate that the probed node (e.g., forwarding node a) supports the corresponding traffic characteristics, and the value "0" of the L2 TLV value field is used to indicate that the forwarding node a does not support the corresponding traffic characteristics. For example, for a certain L1 TLV field in the probe response message (i.e. XLDP message), in the case that the value of the type subfield in the L1 TLV field (i.e. the L1 TLV type field) is "B1", the value of the type subfield in a certain L2 TLV field under the L1 TLV field is "B11" and the value of the value subfield in the L2 TLV field is "1", the probe response message is used to indicate that the forwarding node A supports IPCA feature; the probe response message is used to indicate that forwarding node a does not support the IFIT feature if the value of the type subfield in the L1 TLV field is "B1", the value of the type subfield in a certain L2 TLV field under the L1 TLV field is "B11", and the value of the value subfield in the L2 TLV field is "0", and the probe response message is used to indicate that forwarding node a supports the IFIT feature if the value of the type subfield in a certain L2 TLV field under the L1 TLV field is "B2", and the value of the value subfield in the L2 TLV field is "1", and the value of the type subfield in the L2 TLV field is "B21", and the value of the value subfield in the L2 TLV field is "0". And so on. In this third embodiment, the value of the L2 TLV value field is "1" or "0" is merely exemplary, and in other embodiments, other values (e.g., 2~k) are employed to indicate whether the probed node supports traffic characteristics. Based on the description of the third embodiment, a XLDP packet can detect multiple service characteristics. For example, detection indication information for detecting different service characteristics is carried in different primary TLV fields of one GRASP message to detect a plurality of different service characteristics.

S502, the network node A carries out service configuration on the port P1 of the forwarding node A based on the service characteristic A.

Wherein the port P1 of the forwarding node a is on the transmission path of the data stream a. In an alternative embodiment, the network node a obtains the configuration parameter of the port P1 based on the service characteristic a, and the network node a uses the configuration parameter to perform service configuration on the port P1. For example, the network node a determines the configuration parameters of the port P1 through parameter derivation based on the data flow a and the traffic characteristic a, the network node a sends the configuration parameters of the port P1 to the forwarding node a, and the forwarding node a performs traffic configuration on the port P1 of the forwarding node a according to the configuration parameters of the port P1.

In one embodiment, the configuration parameter of the port P1 includes enabling indication information and an identification (for example, a port number) of the port P1, where the enabling indication information is used to indicate a service function corresponding to the enabling service characteristic a of the port P1, and the forwarding node a enables the service function corresponding to the service characteristic a of the port P1 according to the enabling indication information. For example, the traffic characteristic a is an IPCA characteristic, an IFIT characteristic, flexE characteristic, a channelized sub-interface characteristic, or FlexChannel characteristic, and the enabling indication information is used to indicate that the IPCA function, the IFIT function, the FlexE function, the channelized sub-interface function, or the FlexChannel function is enabled for the port P1, and the forwarding node a enables the IPCA function, the IFIT function, the FlexE function, the channelized sub-interface function, or the FlexChannel function according to the enabling indication information. The IPCA function is a service function corresponding to the IPCA characteristic, the IFIT function is a service function corresponding to the IFIT characteristic, the FlexE function is a service function corresponding to the FlexE characteristic, the channelized sub-interface function is a service function corresponding to the channelized sub-interface characteristic, and the FlexChannel function is a service function corresponding to the FlexChannel characteristic. Optionally, the network node a queries whether the port P1 of the forwarding node a enables the service function corresponding to the service characteristic a, and if the port P1 of the forwarding node a does not enable the service function corresponding to the service characteristic a, the network node a generates the configuration parameter including the enabling indication information and the identifier of the port P1.

In another embodiment, the service characteristics a have at least two types, the service characteristics a correspond to the at least two types of services, the type of the service characteristics a supported by a previous hop node or a next hop node of the forwarding node a on the transmission path of the data flow a is different from the type of the service characteristics a supported by the forwarding node a, the configuration parameters of the port P1 include characteristic conversion information, the characteristic conversion information is used for indicating the type conversion of the service characteristics a, and the forwarding node a performs the type conversion configuration of the service characteristics a on the port P1 according to the characteristic conversion information. In this embodiment, the configuration parameters of port P1 also include an identification of port P1 to indicate port P1. After the forwarding node a performs the type conversion configuration of the service characteristic a on the port P1, the forwarding node a performs the type conversion of the service characteristic a on the port P1 for the data flow a in the process of forwarding the data flow a. The characteristic conversion information is, for example, a type conversion relationship of the service characteristic a, and the forwarding node a configures the type conversion relationship at the port P1. Optionally, the last hop node or the next hop node of the forwarding node a supports a first type of service characteristic a, the forwarding node a supports a second type of service characteristic a, the characteristic conversion information is a conversion relationship between the first type of service characteristic a and the second type of service characteristic a, and after the port P1 configures the conversion relationship, the forwarding node a converts the first type of service characteristic a into the second type of service characteristic a for the data stream a at the port P1 according to the conversion relationship in the process of forwarding the data stream a by the forwarding node a. For example, the service characteristic a corresponds to the service a, the first type of service characteristic a corresponds to the first type of service a, the second type of service characteristic a corresponds to the second type of service a, and the forwarding node a converts the first type of service a into the second type of service a for the data flow a at the port P1 according to the conversion relationship in the process of forwarding the data flow a. In one example, the service characteristic a is a flow-following detection characteristic, the service a is a flow-following detection service, the IPCA characteristic and the IFIT characteristic are two types of flow-following detection characteristics, the IPCA service and the IFIT service are the two types of flow-following detection services, a last hop node of the forwarding node a supports the IPCA characteristic, the forwarding node a supports the IFIT characteristic, the characteristic conversion information is a conversion relationship between the IPCA characteristic and the IFIT characteristic, and the forwarding node a converts the IPCA characteristic into the IFIT characteristic for the data flow a at the port P1 in the process of forwarding the data flow a by the forwarding node a after the port P1 configures the conversion relationship, for example, the forwarding node a decapsulates a message of the data flow a and encapsulates the message of the data flow a with the IFIT to convert the IPCA characteristic into the IFIT characteristic. In another example, service characteristic a is a slice characteristic, service a is a slice service, flexE characteristic, channelized sub-interface characteristic and FlexChannel characteristic are three types of slice characteristics, flexE service, channelized sub-interface service and FlexChannel service are the three types of slice services, a last hop node of forwarding node a supports FlexE characteristic, forwarding node a supports FlexChannel characteristic, the characteristic conversion information is a conversion relationship between FlexE characteristic and FlexChannel characteristic, and forwarding node a converts FlexE characteristic to FlexChannel characteristic for data stream a at port P1 in the process of forwarding data stream a after port P1 configures the conversion relationship. For example, the conversion relationship is a correspondence between FlexE slice identifiers and FlexChannel slice identifiers, and in the process of forwarding the data flow a by the forwarding node a, the FlexE slice identifier in the packet of the data flow a is replaced by the FlexChannel slice identifier at the port P1 according to the correspondence, and the packet of the data flow a is forwarded by the network slice indicated by the FlexChannel slice identifier. In this embodiment, the network node a may detect whether the type of the service characteristic a supported by the previous hop node or the next hop node of the forwarding node a is the same as the type of the service characteristic a supported by the forwarding node a, and if the type of the service characteristic a supported by the previous hop node or the next hop node is different from the type of the service characteristic a supported by the forwarding node a, the network node a generates a configuration parameter of the port P1 according to the type of the service characteristic a supported by the previous hop node or the next hop node and the type of the service characteristic a supported by the forwarding node a, where the configuration parameter includes the characteristic conversion information.

In an alternative embodiment, the configuration parameter of the port P1 further includes information indicating the data flow a, where the configuration parameter is used to indicate that the port P1 is configured for the data flow a based on the service characteristic a (the service configuration made for the port P1 based on the service characteristic a is valid for the data flow a and invalid for other data flows), and the forwarding node a performs the service configuration for the port P1 for the data flow a according to the configuration parameter. The indication information of the data flow a may be information that can be used to indicate the data flow a, such as an IPv6 flow tag, an APN ID, a quintuple, a triplet, and a tuple. Optionally, the packet of the data flow a includes indication information of the data flow a, and the network node a obtains the indication information of the data flow a from the packet of the data flow a, and generates the configuration parameter of the port P1 based on the indication information of the data flow a, where the configuration parameter includes the indication information of the data flow a.

In an alternative embodiment, the forwarding node a is a head node of the transmission path of the data flow a, the configuration parameters of the port P1 include an encapsulation configuration parameter corresponding to the service characteristic a, the forwarding node a performs encapsulation configuration of the service characteristic a on the port P1 according to the encapsulation configuration parameter, and the packet of the data flow a is encapsulated at the port P1 in the process of forwarding the data flow a by the subsequent forwarding node a. In one example, the service characteristic a is an on-flow detection characteristic (for example, an IFIT characteristic), the encapsulation configuration parameter includes enabling indication information of a packet loss function, a delay function, and the like, on-flow detection encapsulation information, and the like, the forwarding node a performs on-flow detection configuration on the port P1 according to the encapsulation configuration parameter, performs IFIT encapsulation on a packet of the data flow a in a process that the forwarding node a forwards the data flow a, and enables the packet loss function, the delay function, and the like in an IFIT header. In another example, the service characteristic a is a slice characteristic (e.g., flexE characteristic), the encapsulation configuration parameter includes a slice identifier, slice encapsulation information, and the like, and the forwarding node a performs slice configuration on the port P1 according to the encapsulation configuration parameter, and performs slice encapsulation on the packet of the data flow a at the port P1 in the process of forwarding the data flow a by the forwarding node a, for example, adding the slice identifier and the like to the packet of the data flow a. Optionally, the network node a determines, according to configuration information input by a user, an encapsulation configuration parameter corresponding to the service characteristic a, and in the case that the network node a is a head node of a transmission path of the data flow a, the network node a may further determine, according to configuration information issued by the control node, the encapsulation configuration parameter corresponding to the service characteristic a. The configuration information input by the user may include a characteristic requirement (such as detection delay, packet loss, etc.) of the data stream a.

In an alternative embodiment, the forwarding node a is a tail node of the transmission path of the data flow a, the configuration parameters of the port P1 include a decapsulation configuration parameter corresponding to the service characteristic a, and the forwarding node a performs the decapsulation configuration of the service characteristic a on the port P1 according to the decapsulation configuration parameter. For example, the forwarding node a performs decapsulation of the service characteristic a on the packet of the data flow a at the port P1 according to the decapsulation configuration parameter, and performs decapsulation of the service characteristic a on the packet of the data flow a at the port P1 in the process of forwarding the data flow a by the subsequent forwarding node a. In one example, the traffic characteristic a is an on-flow detection characteristic (e.g., an IFIT characteristic), and the forwarding node a performs on-flow detection decapsulation configuration on the port P1 according to the decapsulation configuration parameter, and the subsequent forwarding node a strips the IFIT header in the packet of the data flow a from the port P1 during forwarding of the data flow a. In another example, the service characteristic a is a slice characteristic, the forwarding node a performs slice decapsulation configuration on the port P1 according to the decapsulation configuration parameter, and the forwarding node a performs slice decapsulation on the packet of the data flow a at the port P1 in the process of forwarding the data flow a by the forwarding node a, for example, deletes a slice identifier in the packet of the data flow a. Optionally, the network node a determines the decapsulation configuration parameters corresponding to the service characteristics a according to the configuration information input by the user, and in the case that the network node a is the head node of the transmission path of the data flow a, the network node a may further determine the decapsulation configuration parameters corresponding to the service characteristics a according to the configuration information issued by the control node.

In an alternative embodiment, the service characteristic a is a slice characteristic, the configuration parameter of the port P1 includes a slice resource allocation situation corresponding to the service characteristic a, and the forwarding node a configures slice resources of the slice service corresponding to the service characteristic a according to the slice resource allocation situation. For example, the slice resource allocation situation includes the size of the bandwidth resource corresponding to the slice service, and the forwarding node a configures the bandwidth resource of the slice service according to the size of the bandwidth resource corresponding to the slice service. Optionally, the network node a determines the slice resource allocation situation corresponding to the service characteristic a according to the configuration information input by the user, where the configuration information input by the user may include quality requirements, such as delay requirements, packet loss requirements, and the like, of the data stream a.

In an alternative embodiment, the forwarding node a includes a plurality of egress ports (for example, m egress ports, where m is an integer greater than 1) for forwarding the data flow a, where the m egress ports are used for load sharing of the data flow a, the m egress ports include a port P1, and the configuration parameter of the port P1 further includes a sharing ratio of the port P1 to the data flow a. For example, the m output ports perform load sharing on the data stream a according to a load balancing sharing policy, and the sharing ratio of the port P1 to the data stream a is 1/m. For another example, the m output ports load-share the data stream a according to a fixed ratio, and the ratio of sharing the data stream a by the port P1 is the fixed ratio corresponding to the port P1. In one embodiment, the network node a determines the sharing ratio of the port P1 to the data stream a according to the configuration information input by the user, where the configuration information input by the user includes the sharing ratio of the port P1 to the data stream a, or the configuration information input by the user includes the load sharing policies of the m output ports, and the network node a determines the sharing ratio of the port P1 to the data stream a according to the load sharing policies. In another embodiment, the network node a counts the bearing conditions of the m output ports on the data flow a in the historical period, and the network node a determines the sharing ratio of the port P1 to the data flow a according to the bearing conditions of the m output ports on the data flow a in the historical period. For example, the network node a counts the load situation of the m output ports on the data stream a in the historical period, and 60% of the packets of the data stream a are forwarded through the port P1 in the historical period, so that the network node a determines that the sharing ratio of the port P1 to the data stream a is 60%. The network node a may also determine the sharing ratio of the port P1 to the data flow a in other general ways.

In an alternative embodiment, the configuration parameters of the port P1 include configuration parameters of the dependency of the service characteristic a, and the forwarding node a configures the dependency of the service characteristic a for the port P1 according to the configuration parameters of the dependency of the service characteristic a. For example, the on-stream detection characteristic depends on clock synchronization, and the forwarding node a performs configuration of the clock characteristic at the port P1 according to the configuration parameter of the on-stream detection characteristic dependent characteristic. By way of example, the clock characteristic may be a clock characteristic based on the Institute of Electrical and Electronics Engineers (IEEE) 1588 protocol, the international telecommunications union telecommunication standardization sector (ITU-T for ITU Telecommunication Standardization Sector, ITU-T) g.8275.1 protocol, the network time protocol (network time protocol, NTP) or other clock protocols, for example, based on IEEE1588 version2 (version 2, V2) or NTP. Optionally, the network node a determines a dependency characteristic of the service characteristic a, and the network node a generates a configuration parameter of the dependency characteristic according to the dependency characteristic of the service characteristic a. Or the network node A generates the configuration parameters of the dependence characteristics of the service characteristic A according to the configuration information input by the user. In case that the network node a is a head node of the transmission path of the data flow a, the network node a may also generate configuration parameters of the dependency of the traffic characteristic a according to the configuration information issued by the control node.

Based on the above, in the process of determining the configuration parameters of the port P1 by the network node a, factors such as the service function of the port P1, the type of the service characteristic a supported by the previous hop node, the next hop node, and the like of the forwarding node a, the load sharing condition (multipath condition) of the port, the dependence characteristic of the service characteristic a, and the configuration information input by the user are considered, so that the reliability of the configuration parameters determined by the network node a is higher.

The above description of S502 describes the content of the configuration parameters of the port P1 and the implementation process of the network node a determining the configuration parameters of the port P1, and the following description describes the implementation process of the network node a performing service configuration on the port P1 by using the configuration parameters of the port P1.

As described above, the network node a performs service configuration on the port P1 by sending the configuration parameters of the port P1 to the forwarding node a. Optionally, the network node a sends a configuration message to the forwarding node a, where the configuration message includes a configuration parameter of the port P1, and the forwarding node a performs service configuration on the port P1 according to the configuration parameter included in the configuration message. For convenience of description, a configuration message for performing service configuration on the port P1 will be referred to as a port configuration message. In one embodiment, the network node a is a control node, and the port configuration message is a first protocol message, including but not limited to an SNMP message, a netcon message. In another embodiment, the network node a is a head node of a transmission path of the data stream a, and the port configuration message is a second protocol message, including but not limited to a GRASP message or XLDP message. The implementation manner of the service configuration of the port P1 by the network node a will be described in two embodiments by taking the port configuration message as an example, where the port configuration message is a GRASP message or XLDP message, respectively.

In the first embodiment, the port configuration message is a GRASP message, the GRASP message includes a configuration object key value pair field, the configuration object key value pair field is used for carrying configuration parameters of the port P1, and the forwarding node A performs service configuration on the port P1 according to the GRASP message.

The GRASP message (i.e., port configuration message) is illustrated in fig. 8, for example. At least one configuration object key pair field in the GRASP message is used to carry configuration parameters of the port P1 to indicate to perform service configuration on the port P1. Taking the configuration parameter of the port P1 as an example, the configuration parameter includes the identifier and the enabling indication information of the port P1, where the identifier and the enabling indication information of the port P1 are located in a configuration object key value pair field, respectively. In one example, the n configuration object key pair fields in the GRASP message include a first configuration object key pair field (for example, configuration object key pair field 1) and a second configuration object key pair field (for example, configuration object key pair field 2), the identifier "P1" of the port P1 is located in the first configuration object key pair field, the enabling indication information is located in the second configuration object key pair field, and the identifier and the enabling indication information of the port P1 carried in the GRASP message as the port configuration message are shown in the following table 6, respectively.

TABLE 6

Referring to table 6, the value "A1" of the message type field indicates that the type of the GRASP message is a configuration message (a request message, in this embodiment, a port configuration message), and the value of the configuration object name field is "configure flow detection service" or "configure slice service". The value of the configuration object key subfield (i.e., configuration object key subfield 1) in the first configuration object key value pair field is "port identification", and the value of the configuration object value subfield (i.e., configuration object value subfield 1) in the first configuration object key value pair field is the identification "P1" of port P1. In the case where the value of the configuration object name field is "configure stream detection service", the value of the configuration object key subfield (i.e., configuration object key subfield 2) in the second configuration object key value pair field is "Y1" or "Y2", and the value of the configuration object value subfield (i.e., configuration object value subfield 2) in the second configuration object key value pair field is "1" or "0". In the case where the value of the configuration object name field is "configuration slice service", the value of the configuration object key subfield 2 is "Y3", "Y4", or "Y5", and the value of the configuration object value subfield 2 is "1" or "0". The value of the configuration object value subfield 2 is the enable indication information. For example, in the case that the value of the configuration object key subfield 1 is "port identification", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Y1", the port configuration message is used for indicating that the IPCA function is enabled for the port P1, the forwarding node a enables the IPCA function for the port P1 according to the port configuration message and feeds back a configuration response message including an enabling result to the network node a, and in the case that the value of the configuration object key subfield 1 is "port identification", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Y1", the value of the configuration object value subfield 2 is "0", the port configuration message is used for indicating that the IPCA function is disabled for the port P1, and the forwarding node a disables the a function for the port P1 according to the port configuration message and feeds back a configuration response message including a disabling result to the network node a. Similarly, when the value of the configuration object key subfield 1 is "port identification", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Y2", the value of the configuration object value subfield 2 is "1", the port configuration message is used for indicating that the IFIT function is enabled for the port P1, the forwarding node a enables the IFIT function for the port P1 according to the port configuration message and feeds back a configuration response message including an enabling result to the network node a, and when the value of the configuration object key subfield 1 is "port identification", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Y2", the value of the configuration object value subfield 2 is "0", the port configuration message is used for indicating that the IFIT function is disabled for the port P1, and the forwarding node a disables the IFIT function for the port P1 according to the port configuration message and feeds back a configuration response message including a disabling result to the network node a. And so on.

In this first embodiment, the configuration response message is a GRASP message, and the configuration result (e.g., the enable result) may be carried by at least one configuration object key pair field. For example, the configuration result carried by the configuration response message is shown in table 7 below.

TABLE 7

The configuration object key pair field described in table 7 may be the same configuration object key pair field as the second configuration object key pair field described in table 6. Referring to table 7, the value "A2" of the message type field indicates that the type of the GRASP message is a response message (in this embodiment, a configuration response message), the value of the configuration object name field is "configuration stream-associated detection service" or "configuration slice service", the value of the configuration object key subfield is "Y1", "Y2", "Y3", "Y4" or "Y5", the value of the configuration object value subfield is a configuration result, the configuration result is 0 or an error code, and the configuration result "0" is used to indicate that the configuration is successful. For example, for the configuration response message (i.e., the GRASP message), the configuration object value subfield carries the configuration result of the IPCA service when the value of the configuration object key subfield is "Y1", the configuration object value subfield carries the configuration result of the IFIT service when the value of the configuration object key subfield is "Y2", and the configuration object value subfield carries the configuration result of the FlexE service when the value of the configuration object key subfield is "Y3". And so on.

In the second embodiment, the port configuration message is XLDP messages, the XLDP messages include PDUs, TLV fields in the PDUs are used for carrying configuration parameters of the port P1, and the forwarding node A performs service configuration on the port P1 according to the XLDP messages. For example, as shown in fig. 9, the XLDP packet (i.e., the port configuration packet) carries the configuration parameters of the port P1 in the same L1 TLV field. Taking the configuration parameter of the port P1 including the identification and the enabling indication information of the port P1 as an example, the identification and the enabling indication information of the port P1 may be located in one L2TLV field, and the L2TLV field for carrying the identification of the port P1 and the L2TLV field for carrying the enabling indication information may be in the same L1 TLV field. In one example, the first TLV field and the second TLV field are two L2TLV fields in the same L1 TLV field, the identifier "P1" of the port P1 is located in the first TLV field, and the enabling indication information is located in the second TLV field, and the identifier and the enabling indication information of the port P1 carried in the XLDP packet as the port configuration packet are shown in table 8 below.

TABLE 8

Referring to table 8, the value "A1" of the message type field indicates XLDP that the type of message is a configuration message (a channel message, in this embodiment, a port configuration message), and the value of the L1 TLV type field is "C1", "C2", "C3", "C4", or "C5". The value of the type subfield in the first TLV field is "port identification", and the value of the value subfield in the first TLV field is the identification "P1" of the port P1. The value of the type subfield in the second TLV field is "C11", "C21", "C31", "C41" or "C51", the value of the value subfield in the second TLV field is "1" or "0", the value "1" of the value subfield in the second TLV field is used to indicate that the service function of the corresponding service is enabled, and the value "0" of the value subfield in the second TLV field is used to indicate that the service function of the corresponding service is disabled. For example, in the case that the value of the type subfield in the L1 TLV field is "C1", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "C11", and the value of the value subfield in the second TLV field is "1", the port configuration message is used to indicate that the IPCA function (i.e., the service function of the IPCA service) is enabled for the port P1, and the forwarding node a enables the IPCA function for the port P1 according to the port configuration message and feeds back a configuration response message including the enabling result to the network node a; in the case that the value of the type subfield in the L1 TLV field is "C1", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "C11", and the value of the value subfield in the second TLV field is "0", the port configuration message is used to indicate that the IPCA function is disabled for the port P1, and the forwarding node a disables the IPCA function for the port P1 according to the port configuration message and feeds back a configuration response message including the disable result to the network node a. Similarly, when the value of the type subfield in the L1 TLV field is "C2", the value of the type subfield in the first TLV field is "port identification", the value of the type subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "C21", the value of the type subfield in the second TLV field is "1", the port configuration message is used to indicate that the IFIT function is enabled for the port P1 (i.e., the service function of the IFIT service) according to the port configuration message, the forwarding node a enables the IFIT function for the port P1 and feeds back a configuration response message including the enabling result to the network node a, when the value of the type subfield in the L1 TLV field is "C2", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "C21", and the value of the value subfield in the second TLV field is "0", the forwarding node a enables the port configuration message for enabling the port configuration response message to the port P1 according to the port configuration message including the enabling the port configuration result to the port configuration message. And so on.

In this second embodiment, the configuration response message is XLDP messages, and the configuration result (e.g., enable result) is carried by using the L2 TLV field. For example, the configuration result carried by the configuration response message is shown in table 9 below.

TABLE 9

Referring to table 9, the value "A2" of the message type field indicates XLDP that the type of the message is a response message (in this embodiment, a configuration response message), the value of the L1 TLV type field is "C1", "C2", "C3", "C4", or "C5", the value of the type subfield in the L2 TLV field is "C11", "C21", "C31", "C41", or "C51", the value of the value subfield in the L2 TLV field is a configuration result, the configuration result is 0 or an error code, and the configuration result "0" is used to indicate that the configuration is successful. For example, for the configuration response message (i.e., XLDP message), in the case where the value of the type subfield in the L1 TLV field is "C1", the value of the value subfield in the L2 TLV field is "C11", the value of the value subfield in the L2 TLV field is the configuration result of the IPCA service, in the case where the value of the type subfield in the L1 TLV field is "C2", the value of the value subfield in the L2 TLV field is "C21", the value of the value subfield in the L2 TLV field is the configuration result of the IFIT service, in the case where the value of the type subfield in the L1 TLV field is "C3", the value of the value subfield in the L2 TLV field is "C31", the value of the value subfield in the L2 TLV field is the configuration result of the FlexE service. And so on.

After the network node a performs service configuration corresponding to the service characteristic a on the port P1 of the forwarding node a, in the process that the forwarding node a forwards the data stream a through the port P1, the port P1 may perform service operation corresponding to the service for the data stream a.

In one embodiment, the service characteristic a is a flow-following detection characteristic, the service corresponding to the service characteristic a is a flow-following detection service, and after the network node a performs flow-following detection service configuration on the port P1 of the forwarding node a, the forwarding node a performs flow-following detection operation on the data flow a at the port P1 in the process of forwarding the data flow a through the port P1. For example, the forwarding node a is a head node of a transmission path of the data stream a, and the port P1 is an outgoing port of the data stream a in the forwarding node a, and the forwarding node a performs flow-following detection encapsulation and flow-following detection on a packet with the outgoing port being the port P1 in the data stream a, for example, the forwarding node a collects packet loss information (for example, counts the number of packets of the data stream a sent by the port P1) of the packet of the data stream a at the port P1, and delay information (for example, a timestamp of collecting the packet of the data stream a sent by the port P1) and the like. For another example, the forwarding node a is an intermediate node on the transmission path of the data flow a, and the forwarding node a performs the flow following detection on the packet of the data flow a at the port P1 according to the flow following detection encapsulation information carried by the packet of the data flow a, for example, the forwarding node a collects packet loss information, delay information and the like of the packet of the data flow a at the port P1. For another example, the forwarding node a is a tail node of the transmission path of the data stream a, and the port P1 is an output port of the data stream a in the forwarding node a, where the forwarding node a performs flow-following detection and decapsulation on the packet of the data stream a and performs flow-following detection, for example, the forwarding node a collects packet loss information, delay information and the like of the packet of the data stream a at the port P1. Optionally, the forwarding node a includes a port chip (also referred to as an interface chip, an interface board, etc.), where in the case that the forwarding node a is a head node, the port chip encapsulates the packet of the data flow a with flow detection, and in the case that the forwarding node a is a tail node, the port chip decapsulates the packet of the data flow a with flow detection. In addition, the port chip performs flow following detection on the message of the data flow a, and the port chip may add acquired packet loss information, delay information and the like in the message of the data flow a, which is not limited in the embodiment of the present application. In one example, the service characteristic a is an IPCA characteristic, and the service corresponding to the service characteristic a is an IPCA service, and after the network node a performs IPCA service configuration on the port P1, the forwarding node a performs IPCA detection on the data flow a at the port P1 in a process of forwarding the data flow a through the port P1. In another example, the service characteristic a is an IFIT characteristic, the service corresponding to the service characteristic a is an IFIT service, and after the network node a performs IFIT service configuration on the port P1, the forwarding node a performs IFIT detection on the data flow a at the port P1 in the process of forwarding the data flow a through the port P1.

In another embodiment, the service characteristic a is a slicing characteristic, the service corresponding to the service characteristic a is a slicing service, and after the network node a performs slicing service configuration on the port P1 of the forwarding node a, the forwarding node a performs slicing service operation on the data stream a at the port P1 in the process of forwarding the data stream a through the port P1. For example, the forwarding node a is a head node of a transmission path of the data flow a, and performs slice encapsulation corresponding to the slice service on a packet with an output port being the port P1 in the data flow a and forwards the packet of the data flow a through a network slice corresponding to the slice service, and for example, the forwarding node a adds a slice identifier corresponding to the slice service in the packet with the output port being the port P1 in the data flow a, determines a slice port corresponding to the slice service in the port P1 according to the slice identifier, and forwards the packet of the data flow a through the slice port. For another example, the forwarding node a is an intermediate node on the transmission path of the data flow a, and the forwarding node a determines a slice port corresponding to the slice service in the port P1 according to the slice identifier in the packet with the port P1 in the data flow a, and forwards the packet of the data flow a through the slice port. For another example, the forwarding node a is a tail node of the transmission path of the data stream a, and the forwarding node a deletes the slice identifier in the packet with the output port being the port P1 in the data stream a. Optionally, the forwarding node a includes a port chip, and the port chip performs a slice service operation on the data flow a at the port P1, where the slice service is FlexE service, channelized sub-interface service or FlexChannel service, and the network slice corresponding to the slice service is a network slice based on the FlexE interface, a network slice based on the channelized sub-interface, or a network slice based on FlexChannel.

In summary, according to the network configuration scheme provided by the embodiment of the present application, after the control node or the head node of the transmission path of the data stream determines that the forwarding node on the transmission path of the data stream supports the service characteristic, the port of the forwarding node is configured with the service based on the service characteristic, so that the port performs the service operation corresponding to the service characteristic for the data stream in the process of forwarding the data stream by the forwarding node. In the embodiment of the application, the control node or the head node carries out service configuration on the port on the transmission path of the data stream, thereby simplifying the service configuration process and reducing the service configuration difficulty.

For convenience of description, a service corresponding to the service characteristic a will be hereinafter referred to as a service a.

In an alternative embodiment, before the network node a performs service configuration on the port P1 of the forwarding node a based on the service characteristic a (i.e. before S502), the network node a queries whether the port P1 has configured the service a (e.g. whether the port P1 has configured the service a for the data flow 1). In case the port P1 is not configured with the service a, the network node a configures the port P1 with the service a (i.e. performs S502). In case port P1 has been configured with traffic a, network node a does not configure port P1 with traffic a.

For example, the network node a sends a query message to the forwarding node a, where the query message includes port query information, where the port query information is used to indicate whether the query port P1 has configured the service a, and the forwarding node a determines, according to the query message, whether the port P1 has configured the service a and sends a query response message including a query result to the network node a. The port query information includes identification and query indication information of the port P1. For convenience of description, the query message for querying whether the port P1 has configured the service a is referred to as a port query message. In one embodiment, the network node a is a control node, and the port query message is a first protocol message, for example, an SNMP message or a netcon message. In another embodiment, the network node a is a head node of a transmission path of the data stream a, and the port query message is a second protocol message, where the second protocol message includes a GRASP message or XLDP messages. The implementation of the network node a to query whether the port P1 has been configured with the service a will be described in two embodiments below by taking the port query message as an example, which is a GRASP message or XLDP message, respectively.

In the first embodiment, the port query message is a GRASP message, the GRASP message includes a configuration object key pair field, the configuration object key pair field is used for carrying port query information, and the forwarding node A queries whether the port P1 configures the service A according to the port query information and sends a query response message including a query result to the network node A. For example, as shown in fig. 8, the GRASP message (i.e., a port query message) includes at least one configuration object key pair field in the GRASP message for carrying port query information to query whether the port P1 configures the service a. Taking port query information including identification and query indication information of the port P1 as an example, the identification and query indication information of the port P1 are respectively located in a configuration object key value pair field. In one example, the n configuration object key pair fields in the GRASP message include a first configuration object key pair field (for example, configuration object key pair field 1) and a second configuration object key pair field (for example, configuration object key pair field 2), the identifier "P1" of the port P1 is located in the first configuration object key pair field, the query instruction information is located in the second configuration object key pair field, and the identifier and the query instruction information of the port P1 carried in the GRASP message as the port query message are shown in the following table 10, respectively.

Table 10

Referring to table 10, the value "A1" of the message type field indicates that the type of the GRASP message is a query message (a request message, which is a port query message in this embodiment), and the value of the configuration object name field is "query stream detection service configuration" or "query slice service configuration". The value of the configuration object key subfield (i.e., configuration object key subfield 1) in the first configuration object key value pair field is "port identification", and the value of the configuration object value subfield (i.e., configuration object value subfield 1) in the first configuration object key value pair field is the identification "P1" of port P1. In the case that the value of the configuration object name field is "query stream detection service configuration", the value of the configuration object key subfield (i.e., the configuration object key subfield 2) in the second configuration object key value pair field is "Z1" or "Z2", and in the case that the value of the configuration object name field is "query slice service configuration", the value of the configuration object key subfield 2 is "Z3", "Z4" or "Z5". The value of the configuration object key subfield 2 is query indication information. For example, in the case that the value of the configuration object key subfield 1 is "port identification", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Z1", the port query message is used for indicating whether the port P1 is configured with the IPCA service, the forwarding node a determines whether the port P1 is configured with the IPCA service according to the port query message and feeds back a query response message including a query result to the network node a, and in the case that the value of the configuration object key subfield 1 is "port identification", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Z2", the port query message is used for indicating whether the port P1 is configured with the IFIT service, and the forwarding node a determines whether the port P1 is configured with the IFIT service according to the port query message and feeds back the query response message including the query result to the network node a. And so on. In this first embodiment, the configuration object value subfield 2 is a null field, and in other embodiments, information may also be carried in the configuration object value subfield 2, which is not limited in this embodiment of the present application.

In the first embodiment, the query response message is a GRASP message, and the query result may be carried by using at least one configuration object key value. For example, the query result is added to the configuration object value subfield in the second configuration object key value pair field of the port query message to obtain the query response message. Illustratively, the query results carried by the GRASP message as a query response message are shown in Table 11 below.

TABLE 11

The first configuration object key pair field described in table 11 may be the same configuration object key pair field as the first configuration object key pair field described in table 10, and the second configuration object key pair field described in table 11 may be the same configuration object key pair field as the second configuration object key pair field described in table 10. Referring to table 11, the value "A2" of the message type field indicates that the type of the GRASP message is a response message (in this embodiment, a query response message), and the value of the configuration object name field is "query stream detection service configuration" or "query slice service configuration". The value of the configuration object key subfield (configuration object key subfield 1) in the first configuration object key value pair field is "port identification", and the value of the configuration object value subfield (configuration object value subfield 1) in the first configuration object key value pair field is the identification "P1" of the port P1. In the case that the value of the configuration object name field is "query stream detection service configuration", the value of the configuration object key subfield (i.e., the configuration object key subfield 2) in the second configuration object key value pair field is "Z1" or "Z2", and in the case that the value of the configuration object name field is "query slice service configuration", the value of the configuration object key subfield 2 is "Z3", "Z4" or "Z5". The value of the configuration object value subfield (i.e., the configuration object value subfield 2) in the second configuration object key value pair field is "1" or "0", the value of the configuration object value subfield 2 is the query result, the value "1" of the configuration object value subfield 2 is used for indicating that the port P1 has configured the corresponding service, and the value "0" of the configuration object value subfield 2 is used for indicating that the port P1 has not configured the corresponding service. For example, in the case that the value of the configuration object key subfield 1 is "port identification", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Z1" and the value of the configuration object value subfield 2 is "1", the query response message is used for indicating that the port P1 has been configured with the IPCA service, in the case that the value of the configuration object key subfield 1 is "port identification", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Z1" and the value of the configuration object value subfield 2 is "0", the query response message is used for indicating that the port P1 has not been configured with the IPCA service, in the case that the value of the configuration object key subfield 1 is "P1", the value of the configuration object value subfield 2 is "Z2" and the value of the configuration object value subfield 2 is "1", the query response message is used for indicating that the port P1 has not been configured with the value of the port identification ", and the value of the configuration object value subfield 2 is" Z2 "1". And so on.

In the second embodiment, the port query message is XLDP messages, the XLDP messages include PDUs, TLV fields in the PDUs are used for carrying port query information, the forwarding node A queries whether the port P1 configures the service A according to the port query information, and transmits query response messages including query results to the network node A. For example, as shown in fig. 9, the XLDP packet (i.e., the port query packet) carries port query information in the same L1 TLV field. Taking the port query information including the identification of the port P1 and the query indication information as an example, the identification of the port P1 and the query indication information may be located in one L2 TLV field, where the L2 TLV field for carrying the identification of the port P1 and the L2 TLV field for carrying the query indication information are in the same L1 TLV field. In one example, the first TLV field and the second TLV field are two L2 TLV fields in the same L1 TLV field, the identifier of the port P1 is "P1" located in the first TLV field, the query indication information is located in the second TLV field, and the identifier of the port P1 and the query indication information carried in the XLDP packet as the port query packet are shown in table 12 below.

Table 12

Referring to table 12, the value "A1" of the message type field indicates XLDP that the type of message is a query message (a channel message, which is a port query message in this embodiment), and the value of the L1 TLV type field is "D1", "D2", "D3", "D4" or "D5". The value of the type subfield in the first TLV field is "port identification", and the value of the value subfield in the first TLV field is the identification "P1" of the port P1. The value of the type subfield in the second TLV field is "D11", "D21", "D31", "D41" or "D51". For example, in the case that the value of the type subfield in the L1 TLV field is "D1", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "D11", the port query message is used for indicating whether the query port P1 configures IPCA service, the forwarding node a determines whether the port P1 configures IPCA service according to the port query message and feeds back a query response message including a query result to the network node a, in the case that the value of the type subfield in the L1 TLV field is "D2", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "D21", the port query message is used for indicating whether the query port P1 configures IFIT service, and the forwarding node a determines whether the port P1 configures ifa service according to the port query response message and feeds back the query result to the network node a. And so on. In this second embodiment, the value subfield in the second TLV field is a null field, where no information is carried, and in other embodiments, the value subfield in the second TLV field may also carry information, which is not limited by the embodiment of the present application.

In this second embodiment, the query response message is XLDP messages, and the L2 TLV field may be used to carry the query result. For example, the query result is added to the value subfield in the second TLV field of the port query message, so as to obtain the query response message. Illustratively, the query results carried by the XLDP message, which is a query response message, are shown in Table 13 below.

TABLE 13

Referring to table 13, the value "A2" of the message type field indicates XLDP that the type of message is a response message (a response message, which is a query response message in this embodiment), and the value of the L1 TLV type field is "D1", "D2", "D3", "D4" or "D5". The values of the type subfields in the first TLV field are all "port identifications", and the values of the value subfields in the first TLV field are all identifications "P1" of port P1. The value of the type subfield in the second TLV field is "D11", "D21", "D31", "D41" or "D51", the value of the value subfield in the second TLV field is "1" or "0", the value "1" of the value subfield in the second TLV field is used to indicate that the port P1 has configured the corresponding traffic, and the value "0" of the value subfield in the second TLV field is used to indicate that the port P1 has not configured the corresponding traffic. For example, for the query response message (i.e., XLDP message), where the value of the type subfield in the L1 TLV field is "D1", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "D11", and the value of the value subfield in the second TLV field is "1", the port query message is used to indicate that port P1 has configured IPCA traffic; in case the value of the type subfield in the L1 TLV field is "D1", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "D11", the value of the value subfield in the second TLV field is "0", the port query message is used to indicate that port P1 does not configure IPCA traffic, in case the value of the type subfield in the L1 TLV field is "D2", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "P1", the value of the type subfield in the second TLV field is "D21", the value of the value subfield in the second TLV field is "1", the port query message is used to indicate that port P1 has configured IFIT traffic, the value of the type subfield in the first TLV field is "D2", the value of the type subfield in the first TLV field is "port identification", the value of the value subfield in the first TLV field is "D21", the value of the second TLV field is "D1", the port query message is used for indicating that the port P1 is not configured with the IFIT service. And so on.

In an alternative embodiment, after determining that the forwarding node a supports the service characteristic a, the network node a performs service configuration on the forwarding node a based on the service characteristic a. For example, before the network node a performs service configuration on the port P1 of the forwarding node a based on the service characteristic a, the network node a sends a node configuration message to the forwarding node a, where the node configuration message includes node configuration information, and the forwarding node a performs service configuration on the forwarding node a according to the node configuration message, and sends a configuration response message including a configuration result to the network node a. The node configuration message and the port configuration message may be the same message or different messages.

In one embodiment, the network node a is a control node, and the node configuration message is a first protocol message, for example, an SNMP message or a netcon message. In another embodiment, the network node a is a head node of a transmission path of the data stream a, and the node configuration message is a second protocol message, where the second protocol message includes a GRASP message or XLDP messages. The implementation manner of the service configuration of the forwarding node a by the network node a is described in two embodiments below by taking the node configuration message as an example, which is a GRASP message and a XLDP message respectively.

In a first embodiment, the node configuration message is a GRASP message, where the GRASP message includes a configuration object key pair field, where the configuration object key pair field is used to carry a node configuration parameter, and the forwarding node a uses the node configuration parameter to perform service configuration on the forwarding node a, and sends a configuration response message including a configuration result to the network node a. For example, as shown in fig. 8, at least one configuration object key pair field in the GRASP message is used to carry a node configuration parameter to perform service configuration on the forwarding node a. Taking the example that the node configuration parameters include the enabling indication information as an example, the node configuration parameters carried by the GRASP message as the node configuration message are shown in the following table 14.

TABLE 14

Referring to table 14, the value "A1" of the message type field indicates that the type of the GRASP message is a configuration message (a request message, which is a node configuration message in this embodiment), and the value of the configuration object name field is "configure flow detection service" or "configure slice service". In the case where the value of the configuration object name field is "configure stream detection service", the value of the configuration object key subfield in the configuration object key value pair field is "G1" or "G2", and in the case where the value of the configuration object name field is "configure slice service", the value of the configuration object key subfield in the configuration object key value pair field is "G3", "G4" or "G5". The value of the configuration object value subfield in the configuration object key value pair field is '1' or '0', the value of the configuration object value subfield is the enabling indication information, the value '1' of the configuration object value subfield is used for indicating that the corresponding service function is enabled, and the value '0' of the configuration object value subfield is used for indicating that the corresponding service function is disabled. For example, for the node configuration message (i.e., GRASP message), when the value of the configuration object key subfield is "G1", the node configuration message is used for indicating that the IPCA function is enabled for the forwarding node A, the forwarding node A enables the IPCA function for the forwarding node A according to the node configuration message, and feeds back a configuration response message including an enabling result to the network node A, when the value of the configuration object key subfield is "G1", the value of the configuration object value subfield is "0", the node configuration message is used for indicating that the IPCA function is disabled for the forwarding node A according to the node configuration message, and feeds back a configuration response message including an enabling result to the network node A, when the value of the configuration object key subfield is "G2", the node configuration message is used for indicating that the IFA is enabled for the forwarding node A according to the configuration object value, and the IFA is enabled for the network node A according to the configuration value, and the IFA is enabled for the network node A is fed back to the configuration response message including the enabling result. And so on. In this first embodiment, the node configuration message further includes an identifier of the forwarding node a, where the identifier of the forwarding node a is carried in a configuration object key pair field or in another location of the node configuration message, for example, in a destination address field.

In this first embodiment, the configuration response message is a GRASP message, and the configuration result carried by the configuration object key value pair field is similar to table 7, and is not described herein (unlike table 7, the values of the configuration object key subfields in this embodiment are "G1", "G2", "G3", "G4", or "G5").

In the second embodiment, the node configuration message is XLDP messages, the XLDP messages comprise PDU (protocol data unit), TLV (type-value) fields in the PDU are used for carrying node configuration parameters, the forwarding node A carries out service configuration on the forwarding node A according to the node configuration parameters, and a configuration response message comprising a configuration result is sent to the network node A. For example, as shown in fig. 9, the XLDP packet (i.e., the node configuration packet) carries the node configuration parameters in the same L1 TLV field. Taking the example in which the node configuration parameters include the enable indication information, the enable indication information is located in an L2TLV field in the L1 TLV field. The node configuration parameters carried by XLDP messages, which are node configuration messages, are shown in table 15 below.

TABLE 15

Referring to table 15, the value "A1" of the message type field indicates XLDP that the type of message is a configuration message (a channel message, which is a node configuration message in this embodiment), and the value of the L1 TLV type field is "E1", "E2", "E3", "E4", or "E5". The value "E11", "E21", "E31", "E41" or "E51" of the type subfield in one of the L2 TLV fields under the L1 TLV field, the value "1" of the value subfield in the L2 TLV field is used to indicate that the service function of the corresponding service is enabled, and the value "0" of the value subfield in the L2 TLV field is used to indicate that the service function of the corresponding service is disabled. For example, in the case that the value of the type subfield in the L1 TLV field is "E1", the value of the type subfield in the L2 TLV field is "E11", and the value of the value subfield in the L2 TLV field is "1", the node configuration message (i.e., XLDP message) is used to indicate that the IPCA function is enabled for the forwarding node a, and the forwarding node a enables the IPCA function for the forwarding node a according to the node configuration message and feeds back a configuration response message including the enabling result to the network node a; in case that the value of the type subfield in the L1 TLV field is "E1", the value of the type subfield in the L2 TLV field is "E11", the value of the value subfield in the L2 TLV field is "0", the node configuration message is used for indicating that the IFIT function is enabled for the forwarding node a, the forwarding node a disables the IPCA function for the forwarding node a according to the node configuration message and feeds back a configuration response message including the enabling result to the network node a, in case that the value of the type subfield in the L1 TLV field is "E2", the value of the type subfield in the L2 TLV field is "E21", the value of the value subfield in the L2 TLV field is "1", the node configuration message is used for indicating that the IFIT function is enabled for the forwarding node a, the forwarding node a enables the IFIT function for the forwarding node a according to the node configuration message and feeds back a configuration response message including the enabling result to the network node a, in case that the value of the type subfield in the L1 field is "E2", the value of the type subfield in the L2 TLV field is "E21" value of the type subfield in the L2 TLV field is "E2", the forwarding node A disables the IFIT function for the forwarding node A according to the node configuration message, and feeds back a configuration response message comprising an enabling result to the network node A. And so on. The node configuration message also includes an identifier of the forwarding node a, where the identifier of the forwarding node a is carried in an L2 TLV field or in another location of the node configuration message.

In this second embodiment, the configuration response message is XLDP messages, and the L2 TLV field may be used to carry the configuration result. In this embodiment, the configuration result carried by the configuration response packet is similar to the configuration result carried in the above table 9, and is not described herein (unlike the above table 9, in this embodiment, the value of the L1TLV type field is "E1", "E2", "E3", "E4" or "E5", and the corresponding value of the type subfield "E11", "E21", "E31", "E41" or "E51" in the L2 TLV field).

In an alternative embodiment, before the network node a performs service configuration on the forwarding node a based on the service characteristic a, the network node a queries whether the forwarding node a has configured the service a (e.g., queries whether the forwarding node a has globally configured the service a, e.g., queries whether the forwarding node a has configured the service a for the data flow 1). And in the case that the forwarding node A is not configured with the service A, the network node A configures the service A for the forwarding node A. In case that the forwarding node a has configured the service a, the network node a does not configure the forwarding node a for the service a.

For example, the network node a sends a query message to the forwarding node a, where the query message includes node query information, where the node query information is used to indicate whether the forwarding node a has configured the service a, and the forwarding node a determines, according to the query message, whether the forwarding node a has configured the service a and sends a query response message including a query result to the network node a. For convenience of description, a query message for querying whether the forwarding node a has configured the service a is referred to as a node query message. The node query message and the port query message are the same message or different messages.

In one embodiment, the network node a is a control node, and the node query message is an SNMP1 message or a netcon message. In another embodiment, the network node a is a head node of a transmission path of the data stream a, and the node query message is a GRASP message or XLDP messages. The implementation of the network node a to query whether the forwarding node a has configured the service a is described in two embodiments below by taking the node query message as an example, which is a GRASP message and XLDP message respectively.

In the first embodiment, the node query message is a GRASP message, the GRASP message comprises a configuration object key value pair field, the configuration object key value pair field is used for carrying node query information, the forwarding node A queries whether the forwarding node A configures the service A according to the node query information, and sends a query response message comprising a query result to the network node A. For example, as shown in fig. 8, the GRASP message (i.e., the node query message) includes at least one configuration object key pair field in the GRASP message for carrying node query information to query whether the forwarding node a configures the service a. Taking the node query information including query indication information as an example, query indication information carried by the GRASP message as the node query message is shown in the following table 16, respectively.

Table 16

Referring to table 16, the value "A1" of the message type field indicates that the type of the GRASP message is a query message (a request message, which is a node query message in this embodiment), and the value of the configuration object name field is "query stream detection service configuration" or "query slice service configuration". In the case where the value of the configuration object name field is "query stream detection service configuration", the value of the configuration object key subfield in the configuration object key value pair field is "F1" or "F2", and in the case where the value of the configuration object name field is "query slice service configuration", the value of the configuration object key subfield in the configuration object key value pair field is "F3", "F4" or "F5". The value of the configuration object key subfield is query indication information. For example, in the case that the value of the configuration object key subfield is "F1", the node query message is used for indicating whether the forwarding node a configures the IPCA service, the forwarding node a determines whether the forwarding node a configures the IPCA service according to the node query message and feeds back a query response message including a query result to the network node a, and in the case that the value of the configuration object key subfield is "F2", the node query message is used for indicating whether the forwarding node a configures the IFIT service, and the forwarding node a determines whether the forwarding node a configures the IFIT service according to the node query message and feeds back a query response message including a query result to the network node a. And so on. In this first embodiment, the configuration object value subfield is a null field, and in other embodiments, information may also be carried in the configuration object value subfield, which is not limited in this embodiment of the present application. The node query message also includes an identifier of the forwarding node a, where the identifier of the forwarding node a is carried in a configuration object key pair field or in another location of the node configuration message.

In the first embodiment, the query response message is a GRASP message, and the query result may be carried by using at least one configuration object key value. For example, a query result is added to a configuration object value subfield of the node query message to obtain a query response message. Illustratively, the query results carried by the GRASP message as a query response message are shown in Table 17 below.

TABLE 17

The configuration object key pair field described in table 17 may be the same configuration object key pair field as the configuration object key pair field described in table 16. Referring to table 17, the value "A2" of the message type field indicates that the type of the GRASP message is a response message (in this embodiment, a query response message), and the value of the configuration object name field is "query stream detection service configuration" or "query slice service configuration". In the case where the value of the configuration object name field is "query stream detection service configuration", the value of the configuration object key subfield in the configuration object key value pair field is "F1" or "F2", and in the case where the value of the configuration object name field is "query slice service configuration", the value of the configuration object key subfield is "F3", "F4" or "F5". The value of the configuration object value subfield in the configuration object key value pair field is "1" or "0", the value of the configuration object value subfield is a query result, the value of the configuration object value subfield is "1" used for indicating that the forwarding node a has configured the corresponding service, and the value of the configuration object value subfield is "0" used for indicating that the forwarding node a has not configured the corresponding service. For example, for the query response message (i.e., GRASP message), the query response message is used to indicate that forwarding node A has configured IPCA traffic if the value of the configuration object key subfield is "F1" and the value of the configuration object value subfield is "1", the query response message is used to indicate that forwarding node A has not configured IPCA traffic if the value of the configuration object key subfield is "F1" and the value of the configuration object value subfield is "0", and the query response message is used to indicate that forwarding node A has configured IFIT traffic if the value of the configuration object key subfield is "F2" and the value of the configuration object value subfield is "1", and the query response message is used to indicate that forwarding node A has not configured IFIT traffic if the value of the configuration object key subfield is "F2" and the value of the configuration object value subfield is "0". And so on.

In the second embodiment, the node query message is XLDP messages, the XLDP messages comprise PDU, TLV fields in the PDU are used for carrying node query information, the forwarding node A queries whether the forwarding node A configures the service A according to the node query information, and transmits a query response message comprising a query result to the network node A. For example, as shown in fig. 9, the XLDP packet (i.e., the node query packet) carries node query information in the same L1 TLV field. Taking as an example that the node query information includes query indication information, the query indication information is located in one L2TLV field. In one example, the query indication information carried by XLDP messages, which are node query messages, are shown in table 18 below, respectively.

TABLE 18

Referring to table 18, the value "A1" of the message type field indicates XLDP that the type of message is a query message (a channel message, which is a node query message in this embodiment), the value of the type subfield in the L1 TLV field is "R1", "R2", "R3", "R4" or "R5", and the value of the type subfield in one L2 TLV field under the L1 TLV field is "R11", "R21", "R31", "R41" or "R51". For example, in the case that the value of the type subfield in the L1 TLV field is "R1", the value of the type subfield in the L2 TLV field is "R11", the node query message is used to indicate whether to query the forwarding node a to configure the IPCA service, the forwarding node a determines whether to configure the IPCA service and feed back a query response message including a query result to the network node a according to the node query message, in the case that the value of the type subfield in the L1 TLV field is "R2", the value of the type subfield in the L2 TLV field is "R21", the node query message is used to indicate whether to query the forwarding node a to configure the IFIT service, the forwarding node a determines whether to configure the IFIT service according to the node query message and feeds back a query response message including a query result to the network node a, the forwarding node a determines whether to configure the forwarding node a query result to the network node FlexE according to the node query result, and the type subfield in the L1 TLV field is "R3". In the second embodiment, the value subfield in the L2 TLV field is a null field, where no information is carried, and in other embodiments, the value subfield in the L2 TLV field may carry information, which is not limited by the embodiments of the present application. The node query message also includes an identifier of the forwarding node a, where the identifier of the forwarding node a is carried in an L2 TLV or in another location of the node configuration message.

In this second embodiment, the query response message is XLDP messages, and the L2 TLV field may be used to carry the query result. For example, a query result is added to a value subfield in an L2 TLV field of the node query message, so as to obtain a query response message. Illustratively, the query results carried by the XLDP message, which is a query response message, are shown in Table 19 below.

TABLE 19

Referring to table 19, the value "A2" of the message type field indicates XLDP that the type of message is a response message (a channel message, which is a query response message in this embodiment), the value of the type subfield in the L1 TLV field is "R1", "R2", "R3", "R4" or "R5", the value of the type subfield in one of the L2 TLV fields under the L1 TLV field is "R11", "R21", "R31", "R41" or "R51", the value of the value subfield in the L2 TLV field is "1" or "0", the value of the value subfield "1" in the L2 TLV field is used to indicate that the forwarding node a has configured the corresponding traffic, and the value of the value subfield "0" in the L2 TLV field is used to indicate that the forwarding node a has not configured the corresponding traffic. For this query response message (i.e., XLDP message) the example is that in case the value of the type subfield in the L1 TLV field is "R1", the value of the type subfield in the L2 TLV field is "R11", the value of the value subfield in the L2 TLV field is "1", the node query message is used to indicate that forwarding node a has configured IPCA traffic in case the value of the type subfield in the L1 TLV field is "R1", the value of the type subfield in the L2 TLV field is "R11", the node query message is used to indicate that forwarding node a has not configured IPCA traffic in case the value of the value subfield in the L2 TLV field is "0", the value of the type subfield in the L2 TLV field is "R2", the value of the value subfield in the L2 TLV field is "R21", the value of the value subfield in the L2 field is "1", the node query message is used to indicate that forwarding node a has configured ifa traffic in case the value of the type subfield in the L1 is "R2", the value of the value subfield in the L2 is "it 2". And so on.

In an alternative embodiment, the network node a acquires (or refers to identifying) the port P1 on the transmission path of the data flow a before S502, i.e. identifies the port P1 in the forwarding node a located on the transmission path. For example, the network node a receives path information sent by the forwarding node a, where the path information includes an identifier of the port P1, and the network node a obtains the port P1 on the transmission path according to the path information. The path information is obtained based on the message of the data flow A in the process of forwarding the message of the data flow A by the forwarding node A. For example, the path information is obtained by the forwarding node a based on the data packet of the data stream a or the detection packet, where the detection packet of the data stream a is generated by the head node of the transmission path of the data stream a based on the data packet of the data stream a, and the detection packet is used for detecting the port on the transmission path. In one example, network node a is a control node, and forwarding node a sends path information to network node a via SNMP, netcon f, etc. In another example, network node a is a head node of a transmission path of data flow a, and forwarding node a sends path information to network node a through GRASP, XLDP, or the like.

In the embodiment of the present application, the port P1 is a port in the forwarding node a for receiving or sending the data flow a (i.e., an ingress port or an egress port of the data flow a in the forwarding node a), and the path information acquired by the forwarding node a based on the packet of the data flow a may further include at least one of indication information of the data flow a and a flow direction of the data flow a in the forwarding node a. Wherein the flow direction is the direction from the port in forwarding node a for receiving data flow a (i.e. the ingress port) to the port in forwarding node a for transmitting data flow a (i.e. the egress port). The indication information of the data flow a may be information that can be used to indicate the data flow a, such as an IPv6 flow tag, an APN ID, a quintuple, a triplet, and a tuple. Optionally, the path information acquired by the forwarding node a based on the packet of the data flow a includes indication information "a" of the data flow a, a flow direction of the data flow a in the forwarding node a, an identifier of an ingress port of the data flow a in the forwarding node a, and an identifier of an egress port of the data flow a.

In one example, the path information obtained by forwarding node a based on the packets of data flow a is shown in table 20 below.

Table 20

Indication information of data stream a	Flow direction	Inlet port	Outlet port
				A	1	Port 1 (e.g., eth 0/0/1)	Port 2 (e.g. Eth 0/0/2)

Referring to table 20, the path information acquired by the forwarding node a based on the packet of the data flow a includes indication information "a" of the data flow a, flow direction "1" of the data flow a in the forwarding node a, identification of an ingress port (e.g., eth 0/0/1) and identification of an egress port (e.g., eth 0/0/2) of the data flow a in the forwarding node a. Based on table 20, it can be seen that the ingress port of the data flow a in the forwarding node a is port 1, the egress port is port 2, and the flow direction "1" is used to indicate that the flow direction of the data flow a in the forwarding node a is the direction from port 1 to port 2.

In another example, the path information obtained by forwarding node a based on the packet of data flow a is shown in table 21 below.

Table 21

Indication information of data stream a	Flow direction	Inlet port	Outlet port
				A	1	Port 1 (e.g., eth 0/0/1)	Port 2 (e.g. Eth 0/0/2)
A	2	Port 2 (e.g. Eth 0/0/2)	Port 1 (e.g., eth 0/0/1)

Referring to table 21, the forwarding node a obtains two sets of path information based on the packet of the data flow a, where the two sets of path information include the indication information "a" of the data flow a, the flow direction of the data flow a in the forwarding node a, and the identification of the ingress port and the identification of the egress port of the data flow a in the forwarding node a. Based on the first set of path information (path information recorded in row 2 of table 21), it is known that the ingress port of the data flow a in the forwarding node a is port 1, the egress port is port 2, and the flow direction "1" is used to indicate the direction from port 1 to port 2. Based on the second set of path information (path information recorded in row 3 of table 21), it is known that the ingress port of the data flow a in the forwarding node a is port 2, the egress port is port 1, and the flow direction "2" is for the direction from port 2 to port 1. The data flow a has two opposite flows in the forwarding node a.

In yet another example, path information obtained by forwarding node a based on the packets of data flow a is shown in table 22 below.

Table 22

Indication information of data stream a	Flow direction	Inlet port	Outlet port
				A	1	Port 1 (e.g., eth 0/0/1)	Port 2 (e.g. Eth 0/0/2)
A	3	Port 1 (e.g., eth 0/0/1)	Port 3 (e.g. Eth 0/0/3)

Referring to table 22, the forwarding node a obtains two sets of path information based on the packet of the data flow a, where the two sets of path information include the indication information "a" of the data flow a, the flow direction of the data flow a in the forwarding node a, the identification of the ingress port of the data flow a in the forwarding node a, and the identification of the egress port of the data flow a in the forwarding node a, respectively. Based on the first set of path information (path information recorded in row 2 of table 22), it is known that the ingress port of data flow a in forwarding node a is port 1, the egress port is port 2, and the flow direction "1" is used to indicate the direction from port 1 to port 2. Based on the second set of path information (path information recorded in row 3 of table 22), it is known that the ingress port of data flow a in forwarding node a is port 1, the egress port is port 3, and the flow direction "3" is for the direction from port 1 to port 3. It can be seen that the data stream a has two flow directions in the forwarding node a, which are directions from the same ingress port to different egress ports, based on which it can be determined that the data stream a has at least two transmission paths, which may be load sharing paths, which load share the data stream a.

In the embodiment of the present application, the port P1 of the forwarding node a may be any of the ports recorded in the above tables 20 to 22. In addition to the information listed in tables 20 through 22 above, other information may be included in the path information. The path information transmitted by the forwarding node a to the network node a may also comprise, for example, an identification of the forwarding node a, from which the network node a identifies the forwarding node a on the transmission path of the data flow a.

In the embodiment of the present application, the network node a identifies, based on the path information sent by the forwarding node a, the forwarding node a on the transmission path of the data flow a and the port P1 located on the transmission path in the forwarding node a, and in practical application, each forwarding node on the transmission path of the data flow a may acquire the path information based on the packet of the data flow a and send the path information to the network node a, the network node a may identify each forwarding node and the port located on the transmission path in each forwarding node based on the path information sent by each forwarding node on the transmission path, and the implementation process of each forwarding node on the transmission path of the data flow a and the port located on the transmission path in each forwarding node may refer to the implementation process of the network node a to identify the forwarding node a and the port P1, which is not described herein.

In the embodiment of the present application, the service configuration of the forwarding node a and the port P1 based on the service characteristic a by the network node a is taken as an example, the network node a may perform service configuration on each forwarding node supporting the service characteristic a on the transmission path of the data flow a and the ports located on the transmission path in the forwarding nodes based on the service characteristic a, and the configuration process of the network node a on the forwarding nodes on the transmission path and the ports in the forwarding nodes may refer to the service configuration process of the network node a on the forwarding node a and the ports P1, which is not described herein. In addition, the network node a may also consider the path information as shown in the above tables 20 to 22 sent by the forwarding nodes in the process of obtaining the configuration parameters of the forwarding nodes on the transmission path and the configuration parameters of the ports of the forwarding nodes. For example, the network node a determines the load sharing situation of the forwarding nodes on the data stream a, the round trip path situation of the data stream a, and the like according to the path information sent by the forwarding nodes, and derives the configuration parameters of the forwarding nodes and the configuration parameters of the ports located on the transmission path of the data stream a in combination with the load sharing situation of the forwarding nodes on the data stream a, the round trip path situation of the data stream a, and the like based on the service characteristic a.

In the embodiment of the present application, after receiving the path information sent by the forwarding nodes on the transmission path of the data stream a, the network node a may further determine the transmission path according to the path information sent by the forwarding nodes, and present the transmission path. Therefore, the visualization of the transmission path of the data stream A can be realized, and the user can conveniently analyze the transmission path of the data stream A, the transmission condition of the data stream A and the like.

In the embodiment of the application, the forwarding node on the transmission path of the data stream acquires path information based on the message of the data stream in the process of forwarding the data stream, and transmits the path information to the control node or the head node of the transmission path, the control node or the head node identifies the forwarding node on the transmission path and the port (namely, identifies the forwarding node and the port through which the data stream passes) on the transmission path according to the path information transmitted by the forwarding node on the transmission path, and further performs service configuration on the forwarding node and the port through which the data stream passes based on the service characteristics supported by the forwarding node through which the data stream passes. For example, the slice configuration, the stream following detection configuration and the like of forwarding nodes and ports on the transmission path before the change are dynamically canceled, so that the forwarding nodes release network bandwidth resources, forwarding resources and the like, waste of the network bandwidth, the forwarding resources and the like is avoided, the situation that the data stream cannot obtain relevant reserved resources is avoided, and the transmission performance of the data stream is guaranteed.

The GRASP and the XLDP related to the embodiment of the application are both trusted protocols, the trusted protocols can provide a trusted bearing pipeline, the head node of the transmission path of the data flow sends configuration information, inquiry messages and the like to other forwarding nodes on the transmission path based on the GRASP, the XLDP and the like, and the reliability and the security of the communication between the head node and the other forwarding nodes can be ensured. It should be noted that, in the foregoing description of the GRASP messages (such as a probe message, a configuration message, a query message, and a response message) and XLDP messages (such as a probe message, a configuration message, a query message, and a response message), the values of related fields are only abstract descriptions, and do not represent the actual values of the fields, and the actual values of the fields need to be defined in combination with related standards. For example, the values "A1", "A2" of the message type field, the value "probe stream detection characteristic" or "probe slice characteristic" of the configuration object name field, the values "X1", "X2", "X3", "X4", "X5" of the configuration object key subfield, etc. described in table 2, table 3 are abstract descriptions for distinguishing between different service characteristic probes, and are not actual values of these fields. For another example, the values "A1", "A2" of the message type field, the values "B1", "B2", "B3", "B4", "B5" of the L1 TLV type field, and the values "B11", "B21", "B31", "B41", "B51" of the L2 TLV type field described in tables 4 and 5 are all abstract descriptions for distinguishing different service characteristic probes, and are not actual values of these fields. For example, for XLDP messages, the actual value of the message type field may be 0xFF, 0x03, etc., where "A1", "A2" abstractions are employed.

The foregoing is an introduction to the method embodiments of the present application and the following description of the apparatus embodiments of the present application. The apparatus of the present application may be used to perform the method of the present application. For details not disclosed in the device embodiments of the present application, please refer to the method embodiments.

Fig. 10 is a schematic diagram of a network configuration device 1000 according to an embodiment of the application. The network configuration device 1000 is applied to a network node, which is a control node or a head node of a transmission path of a data stream. For example, the network node is the network node 101 in fig. 2 to 4 or the control node 100 in fig. 4. The network configuration device 1000 is configured to perform the method provided by the embodiment shown in fig. 5. As shown in fig. 10, the network configuration apparatus 1000 includes a determination module 1001 and a configuration module 1002.

A determining module 1001, configured to determine that a forwarding node on a transmission path of a data stream supports a service characteristic, and a configuring module 1002, configured to configure a service of a port of the forwarding node based on the service characteristic. The function implementation of the determining module 1001 is referred to the related description in S501, and the function implementation of the configuring module 1002 is referred to the related description in S502.

Optionally, a configuration module 1002 is configured to obtain a configuration parameter of the port based on the service characteristic, and configure the service for the port using the configuration parameter.

Optionally, a configuration module 1002 is configured to send a configuration packet to the forwarding node, where the configuration packet includes the configuration parameter.

Optionally, the configuration message is a GRASP message, the GRASP message includes a configuration object key value pair field, the configuration object key value pair field is used for carrying the configuration parameter, or the configuration message is a XLDP message, the XLDP message includes a PDU, the PDU includes a TLV field, and the TLV field is used for carrying the configuration parameter.

Optionally, the configuration parameter includes enabling indication information and an identifier of the port, where the enabling indication information is used to indicate that the service function corresponding to the service characteristic is enabled for the port.

Optionally, please continue to refer to fig. 10, the network configuration apparatus 1000 further includes:

a receiving module 1003, configured to receive path information sent by the forwarding node, where the path information includes an identifier of the port;

an acquiring module 1004 is configured to acquire the port on the transmission path based on the path information.

Optionally, the port is a port in the forwarding node for receiving or transmitting the data flow, and the path information further comprises at least one of an indication information of the data flow, a flow direction of the data flow in the forwarding node, the flow direction being a direction from the port in the forwarding node for receiving the data flow to the port in the forwarding node for transmitting the data flow.

Optionally, the path information further includes indication information of the forwarding node, the obtaining module 1004 is further configured to obtain the forwarding node on the transmission path based on the path information, and the configuring module 1002 is further configured to perform service configuration on the forwarding node based on the service characteristic.

Optionally, the determining module 1001 is further configured to determine the transmission path according to the path information sent by the forwarding node on the transmission path, and please continue to refer to fig. 10, the network configuration apparatus 1000 further includes a presenting module 1005 configured to present the transmission path.

Optionally, the determining module 1001 is configured to determine that the forwarding node supports service characteristics by sending a probe packet.

Optionally, the probing message is an ICMP message, where the ICMP message includes a type field and a code field, where the type field and the code field are used to indicate whether the forwarding node supports the service characteristic, or the probing message is a GRASP message, where the GRASP message includes a configuration object key pair field, where the configuration object key pair field is used to indicate whether the forwarding node supports the service characteristic, or the probing message is a XLDP message, where the XLDP message includes a PDU, where the PDU includes a TLV field, and where the TLV field is used to indicate whether the forwarding node supports the service characteristic.

Optionally, the network node is a control node or a head node of the transmission path.

Optionally, the service characteristic is an end-to-end service characteristic.

Optionally, the traffic characteristics include any one of a flow-following detection characteristic and a slice characteristic.

Optionally, the on-stream detection characteristics include IFIT characteristics, IPCA characteristics, and the slice characteristics include FlexE-based slice characteristics, channelization subinterface-based slice characteristics, flexChannel-based slice characteristics.

In summary, according to the network configuration scheme provided by the embodiment of the present application, after determining that the forwarding node on the transmission path of the data stream supports the service characteristic, the network node performs service configuration on the port of the forwarding node based on the service characteristic, so that in the process of forwarding the data stream by the forwarding node, the port performs the service operation corresponding to the service characteristic for the data stream.

The network configuration device provided by the embodiment of the application can also be implemented by an application-specific integrated circuit (ASIC) or a programmable logic device (programmable logic device, PLD). The PLD may be a complex program logic device (complex programmable logical device, CPLD), a field-programmable gate array (FPGA) GATE ARRAY, general-purpose array logic (GENERIC ARRAY logic, GAL), or any combination thereof. The method provided by the method embodiment may also be implemented by software, and when the method provided by the method embodiment is implemented by software, each module in the network configuration device may also be a software module.

The embodiment of the application provides a network configuration device which comprises a memory and a processor, wherein the memory is used for storing a computer program, and the processor is used for executing the computer program stored in the memory to enable the network configuration device to execute all or part of steps of a network configuration method provided by the embodiment of the method.

As an example, please refer to fig. 11, which illustrates a schematic diagram of another network configuration device 1100 provided by an embodiment of the present application. The network configuration means 1100 is a network node or a functional component in a network node, for example the network node 101 in fig. 2 to 4 or the control node 100 in fig. 4. The network configuration apparatus 1100 is used to perform the network configuration method embodiment shown in fig. 5. As shown in fig. 11, the network configuration apparatus 1100 includes a main control board 1110, an interface board 1130, and an interface board 1140. The plurality of interface boards may in case comprise a switching network board (not shown in fig. 11) for performing data exchange between the interface boards (interface boards also called line cards or service boards).

The main control board 1110 is used for performing functions such as system management, device maintenance, and protocol processing. Interface boards 1130 and 1140 are used to provide various service interfaces (e.g., POS interface, GE interface, ATM interface, etc.) and to implement message forwarding. The main control board 1110 mainly includes 3 kinds of functional units, namely a system management control unit, a system clock unit and a system maintenance unit. The main control board 1110, the interface board 1130 and the interface board 1140 are connected with the system backboard through a system bus to realize intercommunication. The interface board 1130 includes one or more processors 1131 thereon. Processor 1131 is used to control and manage interface board 1130 and communicate with central processor 1112 on main control board 1110. The memory 1132 on the interface board 1130 is used to store configuration parameters and the like in the above-described embodiments. As shown in fig. 11, the main control board 1110 may include a memory 1114, and the memory 1114 on the main control board 1110 may also be used to store configuration parameters and the like, which is not limited by the embodiment of the present application.

The interface board 1130 includes one or more network interfaces 1133 for receiving and sending messages, and the processor 1131 may process the messages received by the network interfaces 1133, and specific implementation processes will not be described herein one by one. The network interface 1133 may be a port described in the above embodiments, which is also referred to as a network port.

It will be appreciated that, as shown in fig. 11, the present embodiment includes a plurality of interface boards, and a distributed forwarding mechanism is adopted, under which operations on the interface board 1140 are substantially similar to those of the interface board 1130, and for brevity, a description is omitted. Furthermore, it is understood that the processor 1131 in the interface board 1130 and/or the processor 1141 in the interface board 1140 in fig. 11 may be dedicated hardware or chips, such as network processors or application-specific integrated circuits, to implement the above-described functions, which is a so-called forwarding plane that uses dedicated hardware or chip processing. In other embodiments, the processor 1131 in the interface board 1130 and/or the processor 1141 in the interface board 1140 may also employ a general-purpose processor, such as a general-purpose central processing unit (central processing unit, CPU), to perform the functions described above.

It should be noted that the main control board may have one or more blocks, and the main control board and the standby main control board may be included when there are multiple blocks. The interface boards may have one or more blocks, the more data processing capabilities the network nodes are, the more interface boards are provided. Under the condition of a plurality of interface boards, the interface boards can communicate through one or a plurality of exchange network boards, and load sharing redundancy backup can be realized jointly when a plurality of interface boards exist. Under the centralized forwarding architecture, the network node does not need a switching network board, and the interface board bears the processing function of the service data of the whole system. Under the distributed forwarding architecture, the network node comprises a plurality of interface boards, and data exchange among the plurality of interface boards can be realized through a switching network board, so that high-capacity data exchange and processing capacity are provided. Therefore, the data access and processing power of the network nodes of the distributed architecture is greater than that of the nodes of the centralized architecture. Which architecture is specifically adopted depends on the networking deployment scenario, and no limitation is made here.

In alternative embodiments, memory 1132 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that may store information and instructions, or an electrically erasable programmable read-only memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-only memory, EEPROM), a compact disc read-only memory (CD-ROM) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk 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. The memory 1132 may be self-contained and coupled to the processor 1131 via a communications bus. Memory 1132 may also be integrated with processor 1131.

The memory 1132 is used for storing program codes and is controlled to be executed by the processor 1131 to perform part or all of the steps of the network configuration method provided in the above embodiment. The processor 1131 is configured to execute program code stored in the memory 1132. One or more software modules may be included in the program code. The one or more software modules may be the functional modules provided in the embodiment shown in fig. 10 described above. The memory 1114 may also be used for storing program codes and be controlled to be executed by the central processor 1112 to perform part or all of the steps of the network configuration method provided in the above embodiment.

In alternative embodiments, the network interface 1133 may be a device using any type of transceiver for communicating with other nodes or communication networks, such as Ethernet, radio Access network (radio access network, RAN), wireless local area network (wireless local area networks, WLAN), and the like.

As another example, please refer to fig. 12, which illustrates a schematic diagram of another network configuration apparatus 1200 provided by an embodiment of the present application, the network configuration apparatus 1200 may be a control node or a functional component in the control node. The network configuration apparatus 1200 is configured to perform the network configuration method embodiment shown in fig. 5 described above. As shown in fig. 12, the network configuration apparatus 1200 includes:

A processor 1201 and a memory 1202, the memory 1201 and the memory 1202 being connected by a bus 1203. Fig. 12 illustrates the processor 1201 and the memory 1202 separately from each other. Optionally, the processor 1201 and the memory 1202 are integrated.

The memory 1202 is used to store a computer program, including an operating system and program code. The Memory 1202 is a variety of types of storage media, such as, for example, RAM, ROM, nonvolatile random access Memory (NVRAM), programmable read only Memory (programmable read-only Memory, PROM), erasable Programmable Read Only Memory (EPROM), electrically erasable programmable read only Memory (ELECTRICALLY ERASABLE PROGRAMMABLE READ-only Memory, EEPROM), compact disc read only Memory (compact disc read-only Memory, CD-ROM), flash Memory, registers, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk, or other magnetic storage device.

Wherein the processor 1201 is a general purpose processor or a special purpose processor. A general-purpose processor is a processor that performs certain steps and/or operations by reading and executing computer programs stored in a memory (e.g., memory 1202), which may be used in the execution of the steps and/or operations described above (e.g., memory 1202). The computer programs are executed, for example, to implement the relevant functions of the aforementioned determination module 1001, configuration module 1002 and acquisition module 1004. A general purpose processor such as, but not limited to, a CPU. A special purpose processor is a specially designed processor for performing certain steps and/or operations, such as, but not limited to, a digital signal processor (DIGITAL SIGNAL processor), ASIC, CPLD, FPGA, GAL, or any combination thereof. Processor 1201 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor 1201 includes at least one circuit to perform all or part of the steps of the method provided by the embodiments described above.

Optionally, the network configuration device 1200 further comprises a network interface 1204, the network interface 1204 being connected to the processor 1201 and the memory 1202 by a bus 1203. The network interface 1204 enables the network configuration apparatus 700 to communicate with other devices. The network interface 1204 may be a port described in the above embodiments, also referred to as a network port.

Optionally, the network configuration device 1200 further comprises an input/output (I/O) interface 1205, the I/O interface 1205 being connected to the processor 1201 and the memory 1202 via a bus 1203. The processor 1201 can receive an input command or data or the like through the I/O interface 1205. The I/O interface 1205 is used to connect input devices such as a keyboard, a mouse, and the like to the network configuration apparatus 1200.

Optionally, the network configuration device 1200 further comprises a display 1206, the display 1206 being connected to the processor 1201 and the memory 1202 by a bus 1203. The display 1206 can be used to display intermediate and/or final results, etc., produced by the processor 1201 performing the network configuration methods described above. For example, the display 1206 is used to display the transmission path described in the above embodiment. In a possible implementation, the display 1206 is a touch screen to provide a human-machine interaction interface. The display 1206 can implement the functionality associated with the presentation module 1005 described previously.

Alternatively, in some possible scenarios, the above-described network interface 1204 and I/O interface 1205 are collectively referred to as a communication interface. In addition, the communication interface further includes a transceiver for receiving and transmitting information, which is not limited in the embodiment of the present application.

Wherein the bus 1203 is any type of communication bus used to interconnect the internal devices of the network configuration apparatus 1200. Such as a system bus. The embodiment of the present application is described by taking the case that the above-mentioned devices inside the network configuration apparatus 1200 are interconnected through the bus 1203 as an example, alternatively, the above-mentioned devices inside the network configuration apparatus 1200 are communicatively connected to each other by a connection means other than the bus 1203, for example, the above-mentioned devices inside the network configuration apparatus 1200 are interconnected through a logic interface inside the network configuration apparatus 1200.

The above devices may be provided on separate chips, or may be provided at least partially or entirely on the same chip. Whether the individual devices are independently disposed on different chips or integrally disposed on one or more chips is often dependent on the needs of the product design. The embodiment of the application does not limit the specific implementation form of the device.

The network configuration apparatus 1200 shown in fig. 12 is merely exemplary, and in implementation, the network configuration apparatus 1200 includes other components, which are not listed herein. The network configuration apparatus 1200 shown in fig. 12 can perform traffic configuration for forwarding nodes on a transmission path of a data stream by performing all or part of the steps of the network configuration method provided by the above-described embodiments.

The embodiment of the application provides a network configuration system, which comprises a network node and a forwarding node, wherein the network node comprises a network configuration device as shown in any one of figures 10 to 12, and the network node is used for carrying out service configuration on the forwarding node. The network configuration system is, for example, a communication network as shown in any one of fig. 2 to 4.

Embodiments of the present application provide a computer readable storage medium having stored therein a computer program which, when executed (e.g. by a control node, head node, processor, etc.), implements all or part of the steps of a method as provided by the method embodiments described above.

The present application provides a computer program product comprising a program or code which, when executed (e.g. by a control node, head node, processor, etc.), implements all or part of the steps of a method as provided by the method embodiments described above.

Embodiments of the present application provide a chip comprising programmable logic circuits and/or program instructions, which when executed is adapted to carry out all or part of the steps of the method as provided by the method embodiments described above.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be embodied in whole or in part in the form of a computer program product comprising one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a network of computers, or other programmable devices. The computer instructions may be stored in or transmitted from one computer readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means from one website, computer, server, or data center. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device including one or more servers, data centers, etc. that can be integrated with the available medium. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium, or a semiconductor medium (e.g., solid state disk), etc.

The term "at least one" in the present application means one or more, and "a plurality" means two or more. The term "and/or" in the present application is merely an association relation describing the association object, and means that three kinds of relations may exist, for example, a and/or B, and that three kinds of cases, i.e., a alone, a and B together, and B alone, exist. In addition, for the purpose of clarity of description, the words "first," "second," "third," and the like are used herein to distinguish between identical or similar items that have substantially the same function and effect. Those skilled in the art will appreciate that the words "first," "second," "third," etc. do not limit the number and order of execution.

Different types of embodiments, such as a method embodiment and a device embodiment, provided by the embodiment of the present application may be referred to each other, and the embodiment of the present application is not limited to this. The sequence of the operations of the method embodiment provided by the embodiment of the application can be properly adjusted, the operations can also be increased or decreased according to the situation, and any method which is easily conceivable to be changed by a person skilled in the art within the technical scope of the disclosure of the application is covered in the protection scope of the application, so that the description is omitted. In the corresponding embodiments provided in the present application, it should be understood that the disclosed apparatus and the like may be implemented by other structural means. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules is merely a logical division of functionality, and there may be additional divisions of actual implementation, e.g., multiple modules or components may be combined or integrated into another system, or some features may be omitted, or not performed. The modules illustrated as separate components may or may not be physically separate, and the components described as modules may or may not be physical modules, may be located in one place, or may be distributed over a plurality of devices. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

While the application has been described with reference to exemplary embodiments, it will be understood by those skilled in the art that various changes and substitutions of equivalents may be made without departing from the spirit and scope of the application. Therefore, the protection scope of the application is subject to the protection scope of the claims.

Claims

1. A method of network configuration, the method comprising:

The network node determines that a forwarding node on a transmission path of the data stream supports service characteristics;

and the network node performs service configuration on the port of the forwarding node based on the service characteristics.

2. The method of claim 1, wherein the network node configuring traffic for the port of the forwarding node based on the traffic characteristics comprises:

the network node obtains configuration parameters of the port based on the service characteristics;

and the network node adopts the configuration parameters to carry out the service configuration on the port.

3. The method of claim 2, wherein the network node configuring the traffic for the port using the configuration parameters comprises the network node sending a configuration message to the forwarding node, the configuration message including the configuration parameters.

4. The method of claim 3, wherein the configuration message is a generic autonomous signaling protocol GRASP message, the GRASP message including a configuration object key pair field for carrying the configuration parameter, or

The configuration message is a very simple discovery protocol XLDP message, the XLDP message includes a packet data unit PDU, the PDU includes a type length value TLV field, and the TLV field is used to carry the configuration parameter.

5. The method according to any one of claims 2 to 4, wherein the configuration parameter includes enabling indication information and an identification of the port, the enabling indication information being used to indicate that a service function corresponding to the service characteristic is enabled for the port.

6. The method according to any one of claims 1 to 5, further comprising:

The network node receives path information sent by the forwarding node, wherein the path information comprises the identification of the port;

the network node obtains the port on the transmission path based on the path information.

7. The method according to any of claims 1 to 6, wherein the network node determining that a forwarding node on a transmission path of a data flow supports a traffic characteristic comprises the network node determining that the forwarding node supports the traffic characteristic by sending a probe message.

8. The method of claim 7, wherein the probe message is an Internet control message protocol ICMP message, the ICMP message including a type field and a code field, the type field and the code field being used to indicate whether probing the forwarding node supports the traffic characteristics, or

The detection message is a general autonomous signal protocol GRASP message, and the GRASP message comprises a configuration object key value pair field, wherein the configuration object key value pair field is used for indicating whether the forwarding node supports the service characteristic or not

The probe message is a very simple discovery protocol XLDP message, the XLDP message includes a packet data unit PDU, the PDU includes a type length value TLV field, and the TLV field is used to indicate whether the forwarding node supports the service characteristic.

9. The method according to any one of claims 2 to 5, wherein the type of traffic characteristics supported by a previous hop node or a next hop node of the forwarding node is different from the type of traffic characteristics supported by the forwarding node, and wherein the configuration parameters include characteristic conversion information for indicating a type conversion of the traffic characteristics.

10. The method according to any of claims 1 to 9, wherein the network node is a control node or a head node of the transmission path.

11. A network configuration apparatus for use with a network node, the apparatus comprising:

a determining module, configured to determine that a forwarding node on a transmission path of a data stream supports a service characteristic;

And the configuration module is used for carrying out service configuration on the port of the forwarding node based on the service characteristics.

12. The apparatus of claim 11, wherein the configuration module is configured to obtain configuration parameters for the port based on the traffic characteristics and configure the traffic for the port using the configuration parameters.

13. The apparatus of claim 12, wherein the configuration module is configured to send a configuration message to the forwarding node, the configuration message including the configuration parameter.

14. The apparatus of claim 13, wherein the configuration message is a generic autonomous signaling protocol GRASP message, the GRASP message including a configuration object key pair field for carrying the configuration parameter, or

15. The apparatus according to any one of claims 12 to 14, wherein the configuration parameter includes enabling indication information and an identification of the port, the enabling indication information being used to indicate that a service function corresponding to the service characteristic is enabled for the port.

16. The apparatus according to any one of claims 11 to 15, further comprising:

The receiving module is used for receiving path information sent by the forwarding node, wherein the path information comprises the identification of the port;

and the acquisition module is used for acquiring the port on the transmission path based on the path information.

17. The apparatus according to any of claims 11 to 16, wherein the determining module is configured to determine that the forwarding node supports the service characteristic by sending a probe message.

18. The apparatus of claim 17, wherein the probe message is an Internet control message protocol ICMP message, the ICMP message including a type field and a code field, the type field and the code field being used to indicate whether probing the forwarding node supports the traffic characteristics or not

19. The apparatus according to any one of claims 12 to 15, wherein a type of traffic characteristics supported by a previous hop node or a next hop node of the forwarding node is different from the type of traffic characteristics supported by the forwarding node, the configuration parameters further comprising characteristic conversion information indicating a type conversion of the traffic characteristics.

20. The apparatus according to any of claims 11 to 19, wherein the network node is a control node or a head node of the transmission path.