Network configuration method, device and system

Abstract

The invention discloses a network configuration method, device and system, and belongs to the technical field of networks. The method comprises the following steps: a network node determines a forwarding node support service characteristic on a transmission path of a data stream; and the network node performs service configuration on the port of the forwarding node based on the service characteristics. According to the application, the network node performs service configuration on the forwarding node on the transmission path of the data stream, so that the service configuration process can be simplified, and the service configuration difficulty is reduced.

Description

Technical Field

[0001] The present application relates to the field of network technology, and in particular to a network configuration method, device and system. Background Art

[0002] In order to ensure the transmission performance of the data stream, it is necessary to perform service configuration on the forwarding node used for forwarding the data stream in the communication network, so that the forwarding node performs service operations on the data stream in the process of forwarding the data stream. For example, it is necessary to perform flow detection service configuration on the forwarding node used for forwarding the data stream in the communication network, so that the forwarding node performs flow detection operations on the data stream in the process of forwarding the data stream.

[0003] Currently, the forwarding node is usually manually configured for services, but manual configuration is difficult and the configuration process is complicated. Summary of the invention

[0004] The present application provides a network configuration method, device and system, in which a 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. The technical solution of the present application is as follows.

[0005] In a first aspect, a network configuration method is provided, the method comprising: a network node determines that a forwarding node on a transmission path of a data flow supports a service characteristic; the network node performs service configuration on a port of the forwarding node based on the service characteristic. After the network node performs service configuration on the port, the forwarding node can perform a service operation corresponding to the service characteristic on the port for the data flow during the process of forwarding the data flow.

[0006] The technical solution provided by the present application is that 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 flow. Compared with the current manual configuration solution, it can simplify the service configuration process and reduce the difficulty of service configuration.

[0007] Optionally, the network node performing service configuration on the port of the forwarding node based on the service characteristic includes: the network node acquiring configuration parameters of the port based on the service characteristic; and the network node performing the service configuration on the port using the configuration parameters.

[0008] Optionally, the network node adopting the configuration parameter to perform service configuration on the port includes: the network node sending a configuration message to the forwarding node, the configuration message including the configuration parameter. After the forwarding node receives the configuration message, the forwarding node adopts the configuration parameter included in the configuration message to perform service configuration on the port of the forwarding node.

[0009] The technical solution provided by the present application is that a network node sends a configuration message to a forwarding node on the transmission path of a data flow, which can facilitate the forwarding node to use the configuration parameters included in the configuration message to perform service configuration on the port of the forwarding node, thereby facilitating the forwarding node to perform corresponding service operations on the data flow at the port during the process of forwarding the data flow.

[0010] Optionally, the configuration message is a generic autonomic signaling protocol (GRASP) message, the GRASP message includes a configuration object key-value pair field, and the configuration object key-value pair field is used to carry the configuration parameters; or the configuration message is an extremely lean discovery protocol (XLDP) message, the XLDP message includes a packet data unit (PDU), the PDU includes a tag length value (TLV) field, and the TLV field is used to carry the configuration parameters. That is, the network node sends configuration information to the forwarding node through GRASP or XLDP. Among them, GRASP and XLDP are both trusted protocols.

[0011] The technical solution provided by the present application is that a network node sends configuration information to a forwarding node on a data flow transmission path through GRASP or XLDP, which can ensure the reliability and security of the transmission of the configuration information between the network node and the forwarding node.

[0012] Optionally, the configuration parameter includes enabling indication information and an identifier of the port, and the enabling indication information is used to indicate enabling a service function corresponding to a service characteristic of the port.

[0013] The technical solution provided by the present application is that the configuration parameters of the port of the forwarding node include enabling indication information and the identifier of the port. Therefore, the forwarding node can enable the service function corresponding to the service characteristic of the port according to the enabling indication information, so that the forwarding node can perform the service operation corresponding to the service characteristic on the data flow at the port during the process of forwarding the data flow through the port.

[0014] Optionally, before the network node performs service configuration on the port of the forwarding node based on the service characteristics, the method further includes: the network node receives path information sent by the forwarding node, the path information includes an identifier of the port; the network node obtains the port on the transmission path based on the path information (that is, the network node identifies the port on the transmission path based on the path information). The path information is obtained based on a message of the data flow (such as a data message or a detection message) in the process of the forwarding node forwarding the data flow.

[0015] The technical solution provided by the present application is that a forwarding node on the transmission path of a data flow obtains path information of the data flow based on the message of the data flow during the process of forwarding the data flow, and sends the path information to a network node, so that the network node can determine the port in the forwarding node located on the transmission path based on the path information, and then perform service configuration on the port.

[0016] Optionally, the port is a port in the forwarding node for receiving or sending the data flow, and the path information further includes at least one of the following: indication information of the data flow; flow direction of the data flow in the forwarding node, the flow direction being the direction from the port in the forwarding node for receiving the data flow to the port in the forwarding node for sending the data flow. The indication information of the data flow may be an Internet Protocol version 6 (IPv6) flow label, an application-aware networking (APN) identification (ID), a quintuple, a triplet, a binary, or other information that can be used to indicate the data flow.

[0017] In the technical solution provided by the present application, the path information sent by the forwarding node to the network node includes the indication information of the data flow, so the network node can determine the data flow corresponding to the path information according to the indication information of the data flow (that is, determine that the path information is the path information of the data flow). Since the path information sent by the forwarding node to the network node includes the flow direction of the data flow in the forwarding node, it is convenient for the network node to restore the transmission path of the data flow in scenarios such as multi-path load balancing, inconsistent round-trip paths, and dynamic path switching. That is, in the scenario where the data flow has multiple load sharing paths, inconsistent round-trip paths, or dynamic switching of transmission paths, the network node can 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.

[0018] Optionally, the path information also includes indication information of the forwarding node, and the method also includes: the network node obtains the forwarding node on the transmission path based on the path information (that is, the network node identifies the forwarding node on the transmission path based on the path information), and the network node performs service configuration on the forwarding node based on the service characteristics.

[0019] The technical solution provided by the present application is that a forwarding node on the transmission path of a data flow obtains path information of the data flow based on the message of the data flow during the process of forwarding the data flow, and sends the path information to a network node, so that the network node can determine the forwarding node on the transmission path based on the path information, and then perform service configuration on the forwarding node on the transmission path.

[0020] Optionally, the method further includes: the network node determining the transmission path according to path information sent by a forwarding node on the transmission path; and the network node presenting the transmission path.

[0021] The technical solution provided by the present application enables a network node to present a transmission path of a data stream, thereby realizing visualization of the transmission path of the data stream, and facilitating a user to analyze the transmission path of the data stream and the transmission status of the data stream.

[0022] Optionally, the network node determining that the forwarding node on the transmission path of the data flow supports the service feature includes: the network node determining that the forwarding node supports the service feature by sending a detection message, that is, the network node determines that the forwarding node supports the service feature by detection.

[0023] The technical solution provided by the present application enables a network node to determine the service characteristics supported by a forwarding node on a transmission path of a data stream through network detection, so that the network node can perform service configuration on the forwarding node based on the service characteristics supported by the forwarding node on the transmission path.

[0024] Optionally, the detection message is an Internet Control Message Protocol (ICMP) message, the ICMP message includes a type field and a code field, the type field and the code field are used to indicate whether the forwarding node supports the service feature; or the detection 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 to indicate whether the forwarding node supports the service feature; or the detection message is an XLDP message, the XLDP message includes a PDU, the PDU includes a TLV field, the TLV field is used to indicate whether the forwarding node supports the service feature. The ICMP message can be an ICMP message based on Internet Protocol version 4 (IPv4) or an ICMP message based on IPv6, the ICMP message based on IPv4 is also called an ICMPv4 message, and the ICMP message based on IPv6 is also called an ICMPv6 message.

[0025] The technical solution provided by the present application is that the network node detects the service characteristics supported by the forwarding node on the transmission path of the data flow through ICMP, GRASP or XLDP, which can facilitate the network node to learn the service characteristics supported by the forwarding node. In addition, since GRASP and XLDP are both trusted protocols, the network node detects the service characteristics supported by the forwarding node on the transmission path of the data flow through GRASP and XLDP, which can ensure the reliability and security of the communication between the network node and the forwarding node on the transmission path.

[0026] Optionally, the type of service feature supported by the previous hop node or the next hop node of the forwarding node is different from the type of the service feature supported by the forwarding node, and the configuration parameter also includes feature conversion information, which is used to indicate the type conversion of the service feature.

[0027] The technical solution provided by the present application is that since the configuration parameters of the port of the forwarding node include characteristic conversion information, after the forwarding node uses the configuration parameters to perform service configuration on the port, during the process of the forwarding node forwarding the data stream through the port, the type conversion of the service characteristics can be performed on the data stream based on the characteristic conversion information, so that the services corresponding to different types of the service characteristics are opened up (or called splicing, connected) in the forwarding node.

[0028] Optionally, the network node is a control node or a head node of the transmission path. That is, in the present application, the control node or the head node of the transmission path of the data stream may perform service configuration on the forwarding node on the transmission path.

[0029] The technical solution provided by the present application is a distributed configuration solution in which the head node of the data flow transmission path performs service configuration on the forwarding node on the transmission path. The distributed configuration solution is applicable to network scenarios without control nodes, cross-domain network scenarios, large-scale network scenarios, etc. The solution in which the control node performs service configuration on the forwarding node on the data flow transmission path is a centralized configuration solution. The centralized configuration solution is applicable to centralized management scenarios with control nodes.

[0030] Optionally, the above service characteristics are end-to-end service characteristics. Therefore, the technical solution provided by this application supports end-to-end service configuration.

[0031] Optionally, the service feature includes any one of a flow detection feature and a slicing feature. Therefore, the technical solution of the present application is applicable to flow detection service scenarios and slicing service scenarios. In both flow detection service scenarios and slicing service scenarios, the network node can perform service configuration on the forwarding node, which simplifies the configuration process of flow detection services, slicing services, etc. and reduces the configuration difficulty.

[0032] Optionally, the in-situ flow detection feature includes an in-situ flow information telemetry (IFIT) feature and a packet conservation algorithm for internet (IPCA) feature; the slicing feature includes a slicing feature based on flexible Ethernet (FlexE), a slicing feature based on a channelized sub-interface, and a slicing feature based on a flexible channel (FlexChannel).

[0033] In a second aspect, a network configuration device is provided, the network configuration device comprising modules for executing the method provided in the first aspect or any optional manner of the first aspect. The modules in the network configuration device can be implemented based on software, hardware, or a combination of software and hardware, and the modules can be arbitrarily combined or divided based on specific implementations.

[0034] In a third aspect, a network configuration device is provided, which includes a memory and a processor; the memory is used to store computer programs; the processor is used to execute the computer programs stored in the memory so that the network configuration device performs the method provided in the first aspect or any optional manner of the first aspect.

[0035] In a fourth aspect, a network configuration device is provided, which includes a main control board and an interface board, and the main control board and the interface board are used to implement the method provided in the first aspect or any optional manner of the first aspect.

[0036] In a fifth aspect, a network configuration system is provided, which includes a network node and a forwarding node; the network node includes a network configuration device as provided in the second aspect or the third aspect above, and the network node is used to perform service configuration on the forwarding node.

[0037] In a sixth aspect, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed, the method provided in the first aspect or any optional manner of the first aspect is implemented.

[0038] In a seventh aspect, a computer program product is provided, which includes a program or code, and when the program or code is executed, it implements the method provided in the first aspect or any optional manner of the first aspect.

[0039] In an eighth aspect, a chip is provided, which includes a programmable logic circuit and / or program instructions, and when the chip is running, it is used to implement the method provided in the first aspect or any optional manner of the first aspect.

[0040] The technical effects of the second to eighth aspects mentioned above can refer to the first aspect or any optional implementation method of the first aspect, and will not be elaborated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 It is a network scene graph;

[0042] Figure 2 is a schematic diagram of a communication network provided in an embodiment of the present application;

[0043] Figure 3 is a schematic diagram of another communication network provided in an embodiment of the present application;

[0044] Figure 4 is a schematic diagram of another communication network provided in an embodiment of the present application;

[0045] Figure 5 is a flow chart of a network configuration method provided by an embodiment of the present application;

[0046] Figure 6 It is a schematic diagram of an ICMPv4 message provided in an embodiment of the present application;

[0047] Figure 7 It is a schematic diagram of an ICMPv6 message provided in an embodiment of the present application;

[0048] Figure 8 It is a schematic diagram of a GRASP message provided in an embodiment of the present application;

[0049] Fig. 9 It is a schematic diagram of an XLDP message provided in an embodiment of the present application;

[0050] Fig.10 is a schematic diagram of a network configuration device provided in an embodiment of the present application;

[0051] Fig.11 is a schematic diagram of another network configuration device provided in an embodiment of the present application;

[0052] Fig.12 It is a schematic diagram of another network configuration device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The implementation methods of the present application will be further described below in conjunction with the accompanying drawings.

[0054] In order to ensure the transmission performance of the data stream, it is necessary to perform service configuration on the forwarding nodes (such as head nodes, intermediate nodes and tail nodes) used to forward the data stream in the communication network, so that the forwarding nodes can perform service operations on the data stream in the process of forwarding the data stream. For example, in order to provide service level agreement (SLA) visibility for the data stream, it is necessary to perform flow detection service configuration on the forwarding nodes used to forward the data stream in the communication network, so that the forwarding nodes can perform flow detection on the data stream in the process of forwarding the data stream. For another example, in order to ensure the deterministic quality of the data stream, it is necessary to perform slice service configuration on the forwarding nodes used to forward the data stream in the communication network, so that the forwarding nodes can forward the data stream through the corresponding network slices.

[0055] The current automated configuration solution cannot perform service configuration, and the service configuration of the forwarding nodes used to forward data flows is performed manually. For example, the forwarding nodes that the data flow passes through are manually identified and the service configuration is performed on these forwarding nodes. However, manual configuration is difficult, the configuration process is complicated, and the workload is large. Especially in scenarios such as end-to-end (E2E) cross-campus networks, cross-operator networks, multi-path, multi-branch interconnection, and cloud services, the networking through which the data flow passes is relatively complex, and the difficulty and workload of manually identifying the forwarding nodes that the data flow passes through and performing service configuration on these forwarding nodes are both large. For example, in Figure 1 In the network scenario shown, the data flow transmitted between campus network 1 and campus network 2 needs to pass through the forwarding nodes in campus network 1, the forwarding nodes in the Internet / private network / WAN (that is, the Internet or private network or WAN), and the forwarding nodes in campus network 2. The data flow transmitted between campus network 1 and the cloud network needs to pass through the forwarding nodes in campus network 1, the forwarding nodes in the Internet / private network / WAN, and the forwarding nodes in the cloud network. The data flow transmitted between campus network 2 and the cloud network needs to pass through the forwarding nodes in campus network 2, the forwarding nodes in the Internet / private network / WAN, and the forwarding nodes in the cloud network. The networking through which these data flows pass is relatively complex. Manually identifying the forwarding nodes through which these data flows pass and manually configuring services for these forwarding nodes are both difficult and labor-intensive, and may even be difficult to implement.

[0056] An embodiment of the present application provides a network configuration scheme, in which a control node or a head node of a data flow transmission path performs service configuration on a forwarding node on the transmission path, so that the forwarding node performs corresponding service operations on the data flow during the process of forwarding the data flow, thereby simplifying the service configuration process and reducing the difficulty of service configuration.

[0057] The technical solution of the present application is introduced below, and the application scenario of the present application is first introduced.

[0058] The application scenario of the embodiment of the present application provides a communication network, which is a network domain or the communication network includes 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), etc. The communication network includes a plurality of network nodes, and the plurality of network nodes are communicatively connected. In one embodiment, the plurality of network nodes are forwarding nodes for message forwarding. In another embodiment, the plurality of network nodes include a control node and a forwarding node for message forwarding, and the control node is used to manage and control the forwarding node.

[0059] Among them, the forwarding node can 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, for example, the forwarding nodes in the communication network are all switches or routers, or some forwarding nodes are switches and the other forwarding nodes are routers. According to the deployment location, the forwarding nodes in the communication network include edge nodes and non-edge nodes. The edge nodes are located at the edge of the communication network, and the non-edge nodes are connected between different edge nodes. Among them, the control node can be a functional module deployed in a server, or a server, or a server cluster composed of several servers, or a cloud computing service center. The control node integrates functions such as network management, business control and network analysis. The control node is also called a control device, a network management node, a network management device, a network manager, a network controller, etc.

[0060] In an embodiment of the present application, the communication network includes a transmission path for transmitting a data stream, and the forwarding nodes on the transmission path include a head node, an end node, and an intermediate node (transit node) located between the head node and the end node. The head node and the end node may both be edge nodes in the communication network, and the intermediate node is a non-edge node in the communication network. The number of intermediate nodes on the transmission path may be one or more. In some embodiments, the transmission path may only include a head node and an end node, but not an intermediate node. The names of network nodes, forwarding nodes, transmission paths, head nodes, intermediate nodes, end nodes, etc. in the present application are merely exemplary. Network nodes may also be referred to as network devices, network element devices, network elements, etc. Forwarding nodes may also be referred to as forwarding devices, gateway nodes, gateway devices, routing nodes, routing devices, etc. Transmission paths may also be referred to as forwarding paths, communication paths, communication tunnels, etc. Head nodes may also be referred to as head node devices, head nodes, head node devices, etc. Intermediate nodes may also be referred to as intermediate devices, transit nodes, transit devices, etc. End nodes may also be referred to as end node devices.

[0061] In an embodiment of the present application, the control node or the head node of the transmission path of the data flow performs service configuration on the forwarding node on the transmission path, so that the forwarding node on the transmission path performs corresponding service operations on the data flow in the process of forwarding the data flow. For example, the forwarding node on the transmission path generates path information in the process of forwarding the data flow, and sends the path information to the control node or the head node. The control node or the head node determines the port on the transmission path (for example, determines the forwarding node on the transmission path and the port in the forwarding node used to forward the data flow) 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 flow passes. The services of the embodiment of the present application include slicing services, flow detection services, etc., and the corresponding service operations include forwarding operations based on network slicing, flow detection operations, etc. Among them, the flow detection service includes flow information telemetry (in-situ flow information telemetry, IFIT) service, network packet conservation algorithm (packet conservation algorithm for internet, IPCA) service, etc. Slicing services include slicing services based on flexible Ethernet (FlexE), slicing services based on channelized sub-interfaces (channelized sub-interfaces), slicing services based on flexible channels (FlexChannels), etc. For the sake of ease of description, slicing services based on FlexE are referred to as FlexE services, slicing services based on channelized sub-interfaces are referred to as channelized sub-interface services, and slicing services based on FlexChannels are referred to as FlexChannel services.

[0062] Please refer to Figure 2, which shows a schematic diagram of a communication network provided in an embodiment of the present application. The communication network includes forwarding nodes 101-109, and 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, and 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 data stream 1, forwarding node 101 is the head node of transmission path S1, forwarding node 105 is the tail node of transmission path S1, and forwarding nodes 102-104 are intermediate nodes on transmission path S1. For example, forwarding nodes 102 to 105 generate path information in the process of forwarding messages of data stream 1 (for example, during a period of time when data stream 1 starts to be transmitted on transmission path S1, forwarding nodes 102 to 105 generate path information based on the messages of data stream 1 forwarded during the period of time), and send the path information to forwarding node 101. Forwarding node 101 determines the ports of forwarding nodes 102 to 105 located on transmission path S1 based on the path information sent by forwarding nodes 102 to 105 (for example, forwarding nodes 101 to 105 on transmission path S1 and ports of forwarding nodes 101 to 105 used to forward data stream 1 are determined). As a result, forwarding node 101 identifies the ports through which data stream 1 passes, and then forwarding node 101 performs service configuration on the ports through which data stream 1 passes.

[0063] In some embodiments, the communication network includes multiple transmission paths for transmitting data stream 1, and the multiple transmission paths are used to load share the data stream 1. The head nodes of the multiple transmission paths are the same. The head node identifies the port through which the data stream 1 passes according to the path information sent by the forwarding nodes on the multiple transmission paths, and then performs service configuration on the port through which the data stream 1 passes. In this embodiment, the port through which the data stream 1 passes is on the multiple transmission paths. Optionally, the tail nodes of the multiple transmission paths are the same. Please refer to Figure 3 , which shows a schematic diagram of another communication network provided in an embodiment of the present application, the architecture of the communication network is similar to Figure 2 The architecture of the communication networks shown is the same, with the following differences: Figure 3The communication network shown includes a transmission path S1 and a transmission path S2 for transmitting 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, and forwarding nodes 102, 107-109 are intermediate nodes on the transmission path S2. For example, in the process of forwarding messages of data stream 1 being forwarded by the forwarding nodes 102-105, 107-109 (for example, during a period of time when data stream 1 starts to be transmitted on the transmission path S1 and the transmission path S2, the forwarding nodes 102-105, 107-109 generate path information based on the messages of data stream 1 forwarded during the period of time), and send the path information to the forwarding node 101, and the forwarding node 101 determines the port on the transmission path S1 according to the path information sent by the forwarding nodes 102-105, 107-109. (for example, determining the forwarding nodes 101-105 on the transmission path S1 and the ports in the forwarding nodes 101-105 used to forward the data stream 1) and the ports on the transmission path S2 (for example, determining the forwarding nodes 101-102, 107-109, 105 on the transmission path S2 and the ports in the forwarding nodes 101-102, 107-109, 105 used to forward the data stream 1), thereby, the forwarding node 101 identifies the port through which the data stream 1 passes, and then the forwarding node 101 performs service configuration on the port through which the data stream 1 passes.

[0064] Figure 2 and Figure 3 The application scenario shown takes the head node performing service configuration on the port through which data flow 1 passes as an example. In the case where the communication network includes a control node, the control node can perform service configuration on the port through which data flow 1 passes. For examples, please refer to Figure 4, which shows a schematic diagram of another communication network provided by an embodiment of the present application. The communication network includes a control node 100 and forwarding nodes 101-109, the control node 100 is in communication connection with the forwarding nodes 101-109, and the control node 100 is used to manage and control the forwarding nodes 101-109. The communication network includes a transmission path S1 and a transmission path S2 for transmitting data stream 1, the forwarding node 101 is the head node of the transmission path S1 and the transmission path S2, the forwarding node 105 is the tail node of the transmission path S1 and the transmission path S2, the forwarding nodes 102-104 are intermediate nodes on the transmission path S1, and the forwarding nodes 102, 107-109 are intermediate nodes on the transmission path S2. For example, during the process of forwarding the message of data stream 1 by the forwarding nodes 101-105, 107-109 (for example, during a period of time when data stream 1 starts to be transmitted on transmission path S1 and transmission path S2, the forwarding nodes 102-105, 107-109 generate path information based on the message of data stream 1 forwarded during the period of time), the path information is generated and sent to the control node 100. The control node 100 determines the port on the transmission path S1 according to the path information sent by the forwarding nodes 101-105, 107-109. (e.g., determining the forwarding nodes 101-105 on the transmission path S1 and the ports in the forwarding nodes 101-105 used to forward the data stream 1) and the ports on the transmission path S2 (e.g., determining the forwarding nodes 101-102, 107-109, 105 on the transmission path S2 and the ports in the forwarding nodes 101-102, 107-109, 105 used to forward the data stream 1), thereby the control node 100 identifies the ports through which the data stream 1 passes, and then the control node 100 performs service configuration on the ports through which the data stream 1 passes. It should be noted that Figure 4 For simplicity, only the connection lines between the control node 100 and the forwarding nodes 101-104 are shown. In actual applications, the control node 100 and the forwarding nodes 101-109 are all in communication connection. In addition, this section takes the control node 100 performing service configuration on the port through which the data flow 1 passes as an example. Figure 4 In the network scenario shown, the forwarding node 101 may also identify the port through which the data flow 1 passes and perform service configuration on the port through which the data flow 1 passes, which is not limited in the embodiment of the present application.

[0065] In the embodiment of the present application, the scheme for business configuration by the head node is a distributed configuration scheme, and the scheme for business configuration by the control node is a centralized configuration scheme. In the distributed configuration scheme, the head node performs business configuration on the port on the transmission path of the data stream based on protocols such as the Generic Autonomic Signaling Protocol (GRASP) and the Extremely Lean Discovery Protocol (XLDP). In the centralized configuration scheme, the control node performs business configuration on the port on the transmission path of the data stream based on protocols such as the Simple Network Management Protocol (SNMP) and the Network Configuration Protocol (NETCONF). Compared with the centralized configuration scheme, the distributed configuration scheme is suitable for network scenarios without control nodes, cross-domain network scenarios, large-scale network scenarios, etc. For example, there is no control node in about 95% of soho network scenarios. Since the information transmission of protocols such as GRASP and XLDP is fast, usually in seconds or milliseconds, the distributed configuration scheme is suitable for large-scale network scenarios. Among them, soho means small office or home office in English, and small office or home office in Chinese.

[0066] The above description of the application scenario of the present application is only for example and is not intended to limit the technical solution of the present application. In the implementation process, the number of network nodes in the application scenario and the relationship between these network nodes can be configured as needed, and the embodiments of the present application do not limit this.

[0067] The above is an introduction to the application scenarios of the present application. The following is an introduction to the method implementation examples of the present application.

[0068] Please refer to Figure 5 , which shows a flow chart of a network configuration method provided by an embodiment of the present application. The network configuration method is executed 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 Figures 2 to 4 The network node 101 in the communication network shown is either Figure 4 The control node 100 in the communication network shown. For the convenience of description, the network node for executing the network configuration method is described as "network node A" and the data flow is described as "data flow A" hereinafter. Figure 5 The method includes the following steps S501 to S502.

[0069] S501. Network node A determines that forwarding node A on the transmission path of data stream A supports service feature A.

[0070] Among them, forwarding node A is any forwarding node on the transmission path of data stream A, for example, forwarding node A is an intermediate node on the transmission path. Service characteristic A can be an end-to-end service characteristic, service characteristic A corresponds to end-to-end service, and service characteristic A is suitable for hop-by-hop processing of end-to-end service. Optionally, service characteristic A includes at least one of a flow detection characteristic and a slice characteristic, and the flow detection characteristic includes 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 service 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. Among them, the flow detection characteristic corresponds to the flow detection service, and the slice characteristic corresponds to the slice service. For example, the IPCA feature corresponds to the IPCA service, the IFIT feature corresponds to the IFIT service, the FlexE-based slice feature corresponds to the FlexE-based slice service, the channelized sub-interface-based slice feature corresponds to the channelized sub-interface-based slice service, and the FlexChannel-based slice feature corresponds to the FlexChannel-based slice service. For the sake of ease of description, the FlexE-based slice feature is referred to as the FlexE feature, the channelized sub-interface-based slice feature is referred to as the channelized sub-interface feature, the FlexChannel-based slice feature is referred to as the FlexChannel feature, the FlexE-based slice service is referred to as the FlexE service, the channelized sub-interface-based slice service is referred to as the channelized sub-interface service, and the FlexChannel-based slice service is referred to as the FlexChannel service.

[0071] In an optional embodiment, network node A determines that forwarding node A supports service feature A by sending a detection message. For example, network node A sends a detection message to forwarding node A to detect whether forwarding node A supports service feature A, and network node A determines that forwarding node A supports service feature A based on the detection result. In one embodiment, network node A is a control node, and network node A sends a detection message to forwarding node A based on a first protocol, and the detection message is a message based on the first protocol (referred to as a first protocol message). In another embodiment, network node A is the head node of the transmission path of data stream A, and network node A sends a detection message to forwarding node A based on a second protocol, and the detection message is a message based on the second protocol (referred to as a second protocol message). In this other embodiment, network node A sends a detection message to forwarding node A based on a command line input by a user; or, network node A sends a detection message to forwarding node A according to the instruction of the control node. Among them, the first protocol includes but is not limited to a simple network management protocol (SNMP) and a network configuration protocol (NETCONF), and correspondingly, the first protocol message includes but is not limited to an SNMP message and a NETCONF message. The second protocol includes but is not limited to the Internet Control Message Protocol (ICMP), the Generic Autonomic Signaling Protocol (GRASP), and the Extremely Lean Discovery Protocol (XLDP). Correspondingly, the second protocol message includes but is not limited to the ICMP message, the GRASP message, and the XLDP message.

[0072] Taking the detection message being an ICMP message, a GRASP message or an XLDP message as an example, the following describes the implementation method of network node A detecting whether forwarding node A supports service feature A in three embodiments.

[0073] First embodiment: the detection message is an ICMP message, and the ICMP message (i.e., the detection message) includes a type field and a code field, and the type field and the code field are used to indicate whether the detection forwarding node A supports service feature A. For example, the type field and the code field are used to carry detection indication information to indicate whether the detection forwarding node A supports service feature A.

[0074] The ICMP message may be an ICMPv4 message or an ICMPv6 message. Figure 6 As shown in the figure, the ICMPv6 message is as follows Figure 7 See Figure 6 The ICMPv4 message includes ICMP data and an ICMP header and an IPv4 header encapsulated outside the ICMP data in sequence. The length of the IPv4 header is generally 20 to 60 bytes, the length of the ICMP header is generally 4 bytes, and the value of the protocol field in the IPv4 header is "1" to indicate that the next header of the IPv4 header is an ICMP header. Figure 7 The ICMPv6 message includes ICMP data and an ICMP header, an IPv6 extension header, and an IPv6 header encapsulated outside the ICMP data in sequence. The length of the IPv6 header is generally 40 bytes. The length of the IPv6 extension header is variable. The length of the ICMP header is generally 4 bytes. 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. Figure 6 and Figure 7 In the ICMPv4 message and the ICMPv6 message, the ICMP data includes a type field, a code field, a checksum field, a length field for ICMPv6 (the length field is retained in the ICMPv4 message), a length field for ICMPv4 (the length field is retained in the ICMPv6 message), various fields, an ICMP payload, an ICMP extension header, and n objects, where n is a positive integer. The ICMP extension header includes a version field, a reserved 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 detection indication information to indicate the detection service characteristics, for example, to indicate whether the detection forwarding node A supports service characteristic A. The meanings of other fields and message headers in the ICMP message can be referred to relevant technical documents, which will not be repeated here. Figure 6 and Figure 7 Taking the example that the ICMP data includes n objects, the ICMP data may not include objects, and this application does not limit this.

[0075] According to the above description, the service characteristic A is an IFIT characteristic, an IPCA characteristic, a FlexE characteristic, a channelized sub-interface characteristic or a FlexChannel characteristic. According to the different service characteristics A, the detection indication information used to detect whether the forwarding node A supports the service characteristic A is different. For example, when the detection message is an ICMP message, the detection indication information (the value of the type field and the value of the code field) carried by the detection message for detecting the IPCA characteristic, the IFIT characteristic, the FlexE characteristic, the channelized sub-interface characteristic, and the FlexChannel characteristic are respectively shown in the following Table 1.

[0076] Table 1

[0077]

[0078] Referring to Table 1, the value of the type field is "200 / 201 / 205" (i.e., 200 or 201 or 205), and the value of the code field is "1", "2", "3", "4" or "5". When 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 to indicate the detection of the IPCA feature, and the value of the type field "200 / 201 / 205" and the value of the code field "1" are detection indication information for indicating the detection of the IPCA feature. When the forwarding node A receives the ICMP message including the detection indication information, the forwarding node A determines whether the forwarding node A supports the IPCA feature according to the detection indication information, and feeds back to the network node A a detection response message indicating whether the forwarding node A supports the IPCA feature. When 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 to indicate the detection of the IFIT characteristic. The value "200 / 201 / 205" of the type field and the value "2" of the code field are detection indication information for indicating the detection of the IFIT characteristic. When forwarding node A receives an ICMP message including the detection indication information, forwarding node A determines whether forwarding node A supports the IFIT characteristic based on the detection indication information, and feeds back to network node A a detection response message indicating whether forwarding node A supports the IFIT characteristic. When 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 to indicate the detection of the FlexE feature, and the value of the type field "200 / 201 / 205" and the value of the code field "3" are detection indication information used to indicate the detection of the FlexE feature. When the forwarding node A receives the ICMP message including the detection indication information, the forwarding node A determines whether the forwarding node A supports the FlexE feature according to the detection indication information, and feeds back to the network node A a detection response message indicating whether the forwarding node A supports the FlexE feature. And so on.

[0079] In the first embodiment, the probe response message may be an ICMP message, such as Figure 6 and Figure 7As shown, the type field and the code field can be used to carry the detection indication information for indicating the detection service characteristics (for example, service characteristic A), and the reserved field in the ICMP message can be used to carry the detection result. Among them, 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. For example, the value of the reserved field in the detection response message is a first value (for example, 1), indicating that the detection result is that the forwarding node A supports the corresponding service characteristics; the value of the reserved field in the detection response message is a second value (for example, 0), indicating that the detection result is that the forwarding node A does not support the corresponding service characteristics.

[0080] It should be noted that, in the case where network node A is the head node of the transmission path of data stream A, the user can trigger network node A through a command line to detect whether forwarding node A supports service feature A. In addition, network node A and forwarding node A can be the same node or different nodes (for example, forwarding node A is a remote node of network node A), that is, network node A can detect whether the local node supports service feature A, and can also detect whether the remote node supports service feature A. For example, the command line for detecting whether the local node supports service feature A is "display capacity [primary feature] [secondary function] [submodule function or / RFC]", and the command line for detecting whether the remote node supports service feature A is "display IPv4 / IPv6 address capacity [primary feature] [secondary function] [submodule function or / RFC]", where the IPv4 / IPv6 address is the IPv4 address or IPv6 address of the remote node. Based on the command line for detecting whether the remote node supports service feature A, network node A sends the following command to the remote node: Figure 6 or Figure 7The detection message (i.e., ICMP message) shown is used to detect whether the remote node supports service feature A. In one example, the user enters the command line "display Geneveslice FlexChannel" to network node A, and network node A detects whether the node supports the FlexChannel feature according to the command line. In another example, the user enters the command line "display IFIT" to network node A, and network node A detects whether the node supports the IFIT feature according to the command line. In another example, the user enters the command line "display IPCA" to network node A, and network node A detects whether the node supports the IPCA feature according to the command line. In yet another example, the user enters the command line "display XX.XX.XX.XX Geneve slice FlexChannel" to network node A, and network node A detects whether the remote node with the address "XX.XX.XX.XX" supports the FlexChannel feature according to the command line. In another example, the user inputs the command line "display YY:::YY IFIT" to network node A, and network node A detects whether the remote node with the address "YY:::YY" supports the IFIT feature according to the command line. In another example, the user inputs the command line "display XX.XX.XX.XX IPCA" to network node A, and network node A detects whether the remote node with the address "XX.XX.XX.XX" supports the IPCA feature according to the command line.

[0081] Second embodiment: The detection message is a GRASP message, and the GRASP message (also known as the detection message) includes a configuration object key-value pair field, and the configuration object key-value pair field is used to indicate whether the detection forwarding node A supports service feature A. For example, the configuration object key-value pair field is used to carry detection indication information to indicate whether the detection forwarding node A supports service feature A.

[0082] For example, the GRASP message (ie, the detection message) is as follows: Figure 8As shown. The GRASP message includes a signaling protocol message and a user datagram protocol (UDP) header, an Internet protocol (IP) header, and an Ethernet (ETH) header that are sequentially encapsulated outside the signaling protocol message. The signaling protocol message includes a message type (Msg type) field, a session identifier (session ID) field, a configuration object name (Obj name) field, a length (Len) field, and n configuration object key-value pair fields, where n is a positive integer. Each of the n configuration object key-value 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 field in 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 to carry the message type. In the embodiment of the present application, the message type is a request message (such as a probe message) or a response message (such as a response message), that is, the probe message used to detect whether the forwarding node supports the service characteristics and the probe response message corresponding to the probe message can both be GRASP messages, and the message type field is used to distinguish between the probe message and the probe response message. The session identification field is used to carry the 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-value pair fields in the GRASP message (i.e., n). Each of the n configuration object key-value pair fields is used to carry a configuration object key-value pair, and the configuration object key subfield in each configuration object key-value pair field is used to carry the key of the configuration object key-value pair, and the configuration object value subfield in each configuration object key-value pair field is used to carry the value of the configuration object key-value pair. In an embodiment of the present application, at least one configuration object key-value pair field in the n configuration object key-value pair fields is used to carry detection indication information to indicate detection service characteristics, such as indicating whether the detection forwarding node A supports service characteristic A. Among them, the structure and meaning of the UDP header, IP header, and ETH header in the GRASP message can refer to the relevant technical documents, which will not be repeated here.

[0083] In the example, service characteristic A is any one of IFIT characteristics, IPCA characteristics, FlexE characteristics, channelized sub-interface characteristics, and FlexChannel characteristics. When the detection message is a GRASP message, the detection indication information carried by the detection message (that is, the GRASP message) for detecting IPCA characteristics, IFIT characteristics, FlexE characteristics, channelized sub-interface characteristics, and FlexChannel characteristics are shown in Table 2 below.

[0084] Table 2

[0085]

[0086] Referring to Table 2, the value "A1" of the message type field indicates that the type of the GRASP message is a detection message, and the value of the configuration object name field is "detection of flow detection characteristics" or "detection of slice characteristics". When the value of the configuration object name field is "detection of flow detection characteristics", the value of the configuration object key subfield is "X1" or "X2", "X1" is the detection indication information used to indicate the detection of IPCA characteristics, and "X2" is the detection indication information used to indicate the detection of IFIT characteristics. When the value of the configuration object name field is "detection of slice characteristics", the value of the configuration object key subfield is "X3", "X4" or "X5", "X3" is the detection indication information used to indicate the detection of FlexE characteristics, "X4" is the detection indication information used to indicate the detection of channelized sub-interface characteristics, and "X5" is the detection indication information used to indicate the detection of FlexChannel characteristics. For example, when forwarding node A receives a GRASP message whose message type field value is "A1" and whose configuration object key subfield value is "X1", forwarding node A determines whether forwarding node A supports the IPCA feature based on the GRASP message, and feeds back a detection response message to network node A to indicate whether forwarding node A supports the IPCA feature. When forwarding node A receives a GRASP message whose message type field value is "A1" and whose configuration object key subfield value is "X2", forwarding node A determines whether forwarding node A supports the IFIT feature based on the GRASP message, and feeds back a detection response message to network node A to indicate whether forwarding node A supports the IFIT feature. When forwarding node A receives a GRASP message whose message type field value is "A1" and whose configuration object key subfield value is "X3", forwarding node A determines whether forwarding node A supports the FlexE feature based on the GRASP message, and feeds back a detection response message to network node A to indicate whether forwarding node A supports the FlexE feature. And so on. In this embodiment, the configuration object value subfield in the detection message is an empty field and does not carry any information. In other embodiments, the configuration object value subfield may carry information, which is not limited in this embodiment of the present application.

[0087] In the second embodiment, the probe response message may be a GRASP message, and the configuration object value subfield in the configuration object key-value pair field may be used to carry the detection result. For example, the detection result may be added to the configuration object value subfield of the detection message to obtain the 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 detection response message is a GRASP message, the detection indication information for detecting IPCA characteristics, IFIT characteristics, FlexE characteristics, channelized sub-interface characteristics, and FlexChannel characteristics carried by the detection response message and the corresponding detection results are shown in Table 3 below.

[0088] Table 3

[0089]

[0090] Referring to Table 3, the value "A2" of the message type field indicates that the type of the GRASP message is a response message (a detection response message in this embodiment), the value of the configuration object name field is "detection flow detection characteristics" or "detection slice characteristics", 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 detection indication information for detecting service characteristics, the value of the configuration object key subfield is the detection result of the service characteristics, the value of the configuration object value subfield "1" is used to indicate that forwarding node A supports the corresponding service characteristics, and the value of the configuration object value subfield "0" is used to indicate that 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): when the value of the configuration object key subfield in the configuration object key-value pair field is "X1" and the value of the configuration object value subfield in the configuration object key-value pair field is "1", the probe response message is used to indicate that forwarding node A supports the IPCA feature; when the value of the configuration object key subfield in the configuration object key-value pair field is "X1" and the value of the configuration object value subfield in the configuration object key-value pair field is "0", the probe response message is used to indicate that forwarding node A does not support the IPCA feature; when the value of the configuration object key subfield in the configuration object key-value pair field is "X2" and the value of the configuration object value subfield in the configuration object key-value pair field is "1", the probe response message is used to indicate that forwarding node A supports the IFIT feature; when the value of the configuration object key subfield in the configuration object key-value pair field is "X2" and the value of the configuration object value subfield in the configuration object key-value pair field is "0", the probe response message is used to indicate that forwarding node A does not support the IFIT feature. And so on. In the second embodiment, the value of the configuration object value subfield is "1" or "0" for exemplary purposes only. In other embodiments, other values ​​(e.g., 2 to k) are used to indicate whether the detected node supports the corresponding service feature. Based on the description of the second embodiment, it can be seen that a GRASP message can detect multiple service features. For example, detection indication information for detecting different service features is carried in different configuration object key-value pair fields of a GRASP message to detect multiple different service features.

[0091] Third embodiment: the detection message is an XLDP message, the XLDP message includes a PDU, and the TLV field in the PDU is used to indicate whether the detection forwarding node A supports service feature A. For example, the TLV field in the PDU is used to carry detection indication information to indicate whether the detection forwarding node A supports service feature A.

[0092] For example, the XLDP message (ie, the detection message) is as follows: Fig. 9As shown. The XLDP message includes a destination address (DA) field, a source address (SA) field, an Ethernet type (ETH type) field, a version (version) field, a message type (Msg type) field, an XLDP PDU and a frame check sequence (FCS) field. The XLDP PDU includes at least one level 1 (L1) TLV field and at least one level 2 (L2) TLV field. The L2TLV field is a subfield in the L1 TLV field. An L1 TLV field may include multiple L2 TLV fields. Among them, 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 the XLDP PDU is variable. In the XLDP PDU, the L1 TLV field and the L2 TLV field each include a type subfield, a length subfield and a value subfield, the length of the type subfield is 7 bits, the length of the length subfield is 9 bits, and the length of the value subfield is 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 Ethernet type field is used to carry the Ethernet type, and the value of the Ethernet type field is "0x88DD". The version field is used to carry version information, and the value of the version field can be "0x1". The message type field is used to carry the message type, and 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), "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, and 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 the FCS. Optionally, at least one L1 TLV field in the XLDP PDU is used to carry the probe indication information to indicate the characteristics of the probe service, such as indicating whether the probe forwarding node A supports service characteristic A.

[0093] In the example, service characteristic A is any one of IFIT characteristic, IPCA characteristic, FlexE characteristic, channelized sub-interface characteristic, and FlexChannel characteristic. When the detection message is an XLDP message, the detection indication information carried by the detection message for detecting IPCA characteristic, IFIT characteristic, FlexE characteristic, channelized sub-interface characteristic, and FlexChannel characteristic are respectively shown in Table 4 below.

[0094] Table 4

[0095]

[0096] The L2 TLV field described in Table 4 is a subfield in the L1 TLV field described in Table 4. Referring to Table 4, the value "A1" of the message type field indicates that the type of the XLDP message is a detection message (i.e., a channel message), and the value of the L1 TLV type field is "B1", "B2", "B3", "B4", or "B5". When the value of the L1 TLV type field is "B1", the L1 TLV field is used to indicate the detection of the IPCA feature, and the value "B1" of the L1 TLV type field is the detection indication information for indicating the detection of the IPCA feature. When the forwarding node A receives the XLDP message including the detection indication information, the forwarding node A determines whether the forwarding node A supports the IPCA feature according to the detection indication information, and feeds back to the network node A a detection response message indicating whether the forwarding node A supports the IPCA feature. When the value of the L1 TLV type field is "B2", the L1 TLV field is used to indicate the detection of the IFIT feature, and the value "B2" of the L1 TLV type field is the detection indication information used to indicate the detection of the IFIT feature. When the forwarding node A receives the XLDP message including the detection indication information, the forwarding node A determines whether the forwarding node A supports the IFIT feature according to the detection indication information, and feeds back to the network node A a detection response message indicating whether the forwarding node A supports the IFIT feature. When the value of the L1 TLV type field is "B3", the L1 TLV field is used to indicate the detection of the FlexE feature, and the value "B3" of the L1 TLV type field is the detection indication information used to indicate the detection of the FlexE feature. When the forwarding node A receives the XLDP message including the detection indication information, the forwarding node A determines whether the forwarding node A supports the FlexE feature according to the detection indication information, and feeds back to the network node A a detection response message indicating whether the forwarding node A supports the FlexE feature. And so on. In this embodiment, the L2 TLV field in the detection message (i.e., the XLDP message) is an empty field. In some embodiments, the L2 TLV field may carry information, or the detection message does not include the L2 TLV field, which is not limited in the embodiments of the present application.

[0097] In the third embodiment, the probe response message may be an XLDP message, and the L2 TLV field may be used to carry the detection result. For example, the detection result of the service characteristic carried in the L2 TLV field under the L1 TLV field in the probe message for indicating the detection of a certain service characteristic can obtain the probe response message corresponding to the probe message. For example, in the case where the probe response message is an XLDP message, the detection indication information carried by the probe response message for detecting IPCA characteristics, IFIT characteristics, FlexE characteristics, channelized sub-interface characteristics, and FlexChannel characteristics and the corresponding detection results are shown in Table 5 below.

[0098] Table 5

[0099]

[0100] Referring to Table 5, the value "A2" of the message type field indicates that the type of the XLDP message is a response message (a detection response message in this embodiment), the value of the L1 TLV type field is "B1", "B2", "B3", "B4" or "B5", the corresponding value of the L2 TLV type field is "B11", "B21", "B31", "B41" or "B51", the value of the L2 TLV value field is "1" or "0", the value of the L1 TLV type field is detection indication information of the detected service 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 the detection result of the service characteristics, the value "1" of the L2 TLV value field is used to indicate that the detected node (for example, forwarding node A) supports the corresponding service 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 service characteristics. For example, for a certain L1TLV field in the probe response message (i.e., the XLDP message): when the value of the type subfield (i.e., the L1 TLV type field) 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 "1", the probe response message is used to indicate that the forwarding node A supports the IPCA feature; when 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", the probe response message is used to indicate that the forwarding node A does not support the IPCA feature; when the value of the type subfield in the L1 TLV field is "B2", the value of the type subfield in a certain L2 TLV field under the L1 TLV field is "B21", and the value of the value subfield in the L2 TLV field is "0", the probe response message is used to indicate that the forwarding node A does not support the IPCA feature; When the value of the value subfield in the TLV field is "1", the detection response message is used to indicate that the forwarding node A supports the IFIT feature; when the value of the type subfield in the L1 TLV field is "B2", the value of the type subfield in a certain L2 TLV field under the L1 TLV field is "B21" and the value of the value subfield in the L2 TLV field is "0", the detection response message is used to indicate that the forwarding node A does not support the IFIT feature. And so on. In the third embodiment, the value of the L2 TLV value field is "1" or "0" is only exemplary. In other embodiments, other values ​​(for example, 2 to k) are used to indicate whether the detected node supports the service feature. Based on the description of the third embodiment, it can be known that an XLDP message can detect multiple service features. For example, different level TLV fields in a GRASP message carry detection indication information for detecting different service features to detect multiple different service features.

[0101] S502. Network node A performs service configuration on port P1 of forwarding node A based on service characteristic A.

[0102] Among them, the port P1 of the forwarding node A is on the transmission path of the data stream A. In an optional embodiment, the network node A obtains the configuration parameters of the port P1 based on the service characteristic A, and the network node A uses the configuration parameters 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 stream A and the service 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 service configuration on the port P1 of the forwarding node A according to the configuration parameters of the port P1.

[0103] In one embodiment, the configuration parameters of port P1 include enabling indication information and an identifier of port P1 (e.g., a port number), and the enabling indication information is used to indicate that a service function corresponding to service characteristic A is enabled for port P1, and forwarding node A enables the service function corresponding to service characteristic A for port P1 according to the enabling indication information. For example, service characteristic A is an IPCA characteristic, an IFIT characteristic, a FlexE characteristic, a channelized sub-interface characteristic, or a FlexChannel characteristic, and correspondingly, the enabling indication information is used to indicate that an IPCA function, an IFIT function, a FlexE function, a channelized sub-interface function, or a FlexChannel function is enabled for port P1, and forwarding node A enables an IPCA function, an IFIT function, a FlexE function, a channelized sub-interface function, or a FlexChannel function for port P1 according to the enabling indication information. Among them, 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, network node A queries whether port P1 of forwarding node A enables the service function corresponding to service characteristic A. If port P1 of forwarding node A does not enable the service function corresponding to service characteristic A, network node A generates the configuration parameter including the enabling indication information and the identifier of port P1.

[0104] In another embodiment, service characteristic A has at least two types, service characteristic A corresponds to at least two types of services, the type of service characteristic A supported by the previous hop node or the next hop node of forwarding node A on the transmission path of data stream A is different from the type of service characteristic A supported by forwarding node A, the configuration parameters of port P1 include characteristic conversion information, the characteristic conversion information is used to indicate the type conversion of service characteristic A, and forwarding node A performs type conversion configuration of service characteristic A on port P1 according to the characteristic conversion information. In this embodiment, the configuration parameters of port P1 also include an identifier of port P1 to indicate port P1. After forwarding node A performs type conversion configuration of service characteristic A on port P1, in the process of forwarding data stream A, forwarding node A performs type conversion of service characteristic A on data stream A at port P1. For example, the characteristic conversion information is the type conversion relationship of service characteristic A, and forwarding node A configures the type conversion relationship at port P1. Optionally, the previous hop node or the next hop node of the forwarding node A supports the first type of service characteristic A, and the forwarding node A supports the 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. After the forwarding node A configures the conversion relationship at port P1, the first type of service characteristic A is converted into the second type of service characteristic A for data stream A at port P1 according to the conversion relationship during the process of forwarding data stream A by the forwarding node A. For example, the service characteristic A corresponds to service A, the first type of service characteristic A corresponds to the first type of service A, and the second type of service characteristic A corresponds to the second type of service A. During the process of forwarding data stream A by the forwarding node A, the first type of service A is converted into the second type of service A for data stream A at port P1 according to the conversion relationship. In an example, service feature A is a flow detection feature, service A is a flow detection service, IPCA feature and IFIT feature are two types of flow detection features, IPCA service and IFIT service are the two types of flow detection services, the previous hop node of forwarding node A supports the IPCA feature, forwarding node A supports the IFIT feature, the feature conversion information is the conversion relationship between the IPCA feature and the IFIT feature, after forwarding node A configures the conversion relationship on port P1, in the process of forwarding data flow A by forwarding node A, the IPCA feature is converted into the IFIT feature for data flow A at port P1, for example, forwarding node A performs IPCA decapsulation on the message of data flow A and performs IFIT encapsulation on the message of data flow A to convert the IPCA feature into the IFIT feature.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, the previous hop node of forwarding node A supports FlexE characteristic, forwarding node A supports FlexChannel characteristic, the characteristic conversion information is the conversion relationship between FlexE characteristic and FlexChannel characteristic, after forwarding node A configures the conversion relationship at port P1, in the process of forwarding data stream A, forwarding node A converts FlexE characteristic to FlexChannel characteristic at port P1 for data stream A. For example, the conversion relationship is the correspondence relationship between FlexE slice identifier and FlexChannel slice identifier, in the process of forwarding data stream A, forwarding node A replaces the FlexE slice identifier in the message of data stream A with the FlexChannel slice identifier at port P1 according to the correspondence, and forwards the message of data stream A through the network slice indicated by the FlexChannel slice identifier. In this embodiment, network node A can detect whether the type of service characteristic A supported by the previous hop node or the next hop node of forwarding node A is the same as the type of service characteristic A supported by forwarding node A. If the type of service characteristic A supported by the previous hop node or the next hop node is different from the type of service characteristic A supported by forwarding node A, network node A generates configuration parameters of port P1 according to the type of service characteristic A supported by the previous hop node or the next hop node and the type of service characteristic A supported by forwarding node A, and the configuration parameters include the characteristic conversion information.

[0105] In an optional embodiment, the configuration parameters of port P1 also include indication information of data stream A, and the configuration parameters are used to indicate that the service configuration of port P1 is performed for data stream A based on service characteristic A (the service configuration performed on port P1 based on service characteristic A is valid for data stream A, and invalid for other data streams), and forwarding node A performs the service configuration on port P1 for data stream A according to the configuration parameters. The indication information of data stream A may be information that can be used to indicate data stream A, such as an IPv6 flow label, an APN ID, a five-tuple, a triplet, a two-tuple, etc. Optionally, the message of data stream A includes the indication information of data stream A, and network node A obtains the indication information of data stream A from the message of data stream A, and generates the configuration parameters of port P1 based on the indication information of data stream A, and the configuration parameters include the indication information of data stream A.

[0106] In an optional embodiment, forwarding node A is the head node of the transmission path of data stream A, the configuration parameters of port P1 include encapsulation configuration parameters corresponding to service characteristic A, forwarding node A performs encapsulation configuration of service characteristic A on port P1 according to the encapsulation configuration parameters, and subsequently encapsulates the message of data stream A at port P1 in the process of forwarding data stream A by forwarding node A. In one example, service characteristic A is a flow detection characteristic (such as IFIT characteristic), the encapsulation configuration parameters include enabling indication information of packet loss function, delay function, etc., flow detection encapsulation information, etc., forwarding node A performs flow detection configuration on port P1 according to the encapsulation configuration parameters, and subsequently performs IFIT encapsulation on the message of data stream A in the process of forwarding data stream A by forwarding node A, and enables packet loss function, delay function, etc. in the IFIT header. In another example, service characteristic A is a slicing characteristic (e.g., a FlexE characteristic), and the encapsulation configuration parameters include a slicing identifier, slicing encapsulation information, etc. Forwarding node A performs slicing configuration on port P1 according to the encapsulation configuration parameters, and subsequently, when forwarding node A forwards data stream A, it performs slicing encapsulation on the message of data stream A at port P1, for example, adding a slicing identifier to the message of data stream A. Optionally, network node A determines the encapsulation configuration parameters corresponding to service characteristic A according to the configuration information input by the user. When network node A is the head node of the transmission path of data stream A, network node A can also determine the encapsulation configuration parameters corresponding to service characteristic A according to the configuration information sent by the control node. The configuration information input by the user may include characteristic requirements of data stream A (e.g., the need to detect delay, packet loss, etc.), etc.

[0107] In an optional embodiment, forwarding node A is the tail node of the transmission path of data stream A, and the configuration parameters of port P1 include decapsulation configuration parameters corresponding to service characteristic A. Forwarding node A performs decapsulation configuration of service characteristic A on port P1 according to the decapsulation configuration parameters. For example, forwarding node A performs decapsulation of service characteristic A on the message of data stream A at port P1 according to the decapsulation configuration parameters, and subsequently, in the process of forwarding data stream A being forwarded by forwarding node A, decapsulation of service characteristic A on the message of data stream A at port P1 is performed. In one example, service characteristic A is a flow detection characteristic (such as an IFIT characteristic), and forwarding node A performs flow detection decapsulation configuration on port P1 according to the decapsulation configuration parameters, and subsequently, in the process of forwarding node A being forwarded by data stream A, the IFIT header in the message of data stream A is stripped off at port P1. In another example, service characteristic A is a slicing characteristic, and forwarding node A performs slicing and decapsulation configuration on port P1 according to the decapsulation configuration parameter. In the subsequent process of forwarding data stream A by forwarding node A, the message of data stream A is sliced ​​and decapsulated at port P1, for example, the slicing identifier in the message of data stream A is deleted. Optionally, network node A determines the decapsulation configuration parameter corresponding to service characteristic A according to the configuration information input by the user. In the case where network node A is the head node of the transmission path of data stream A, network node A can also determine the decapsulation configuration parameter corresponding to service characteristic A according to the configuration information sent by the control node.

[0108] In an optional embodiment, service characteristic A is a slice characteristic, and the configuration parameters of port P1 include slice resource allocation corresponding to service characteristic A, and forwarding node A configures slice resources of the slice service corresponding to service characteristic A according to the slice resource allocation. For example, the slice resource allocation includes the size of the bandwidth resource corresponding to the slice service, and 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, network node A determines the slice resource allocation corresponding to service characteristic A according to the configuration information input by the user, and the configuration information input by the user may include quality requirements of data stream A, such as delay requirements, packet loss requirements, etc.

[0109] In an optional embodiment, the forwarding node A includes multiple egress ports (for example, m egress ports, where m is an integer greater than 1) for forwarding data stream A, and the m egress ports are used to load share data stream A, and the m egress ports include port P1, and the configuration parameters of port P1 also include the sharing ratio of port P1 to data stream A. For example, the m egress ports load share data stream A according to the load balancing sharing strategy, and the sharing ratio of port P1 to data stream A is 1 / m. For another example, the m egress ports load share data stream A according to a fixed ratio, and the sharing ratio of port P1 to data stream A is the fixed ratio corresponding to port P1. In one embodiment, the network node A determines the sharing ratio of port P1 to data stream A according to the configuration information input by the user, and the configuration information input by the user includes the sharing ratio of port P1 to data stream A; or, the configuration information input by the user includes the load sharing strategy of the m egress ports, and the network node A determines the sharing ratio of port P1 to data stream A according to the load sharing strategy. In another embodiment, network node A counts the carrying conditions of the m egress ports for data stream A in a historical time period, and network node A determines the share ratio of port P1 for data stream A according to the carrying conditions of the m egress ports for data stream A in the historical time period. For example, network node A counts the carrying conditions of the m egress ports for data stream A in a historical time period and finds that 60% of the messages of data stream A are forwarded through port P1 in the historical time period, so network node A determines that the share ratio of port P1 for data stream A is 60%. Network node A can also determine the share ratio of port P1 for data stream A in other common ways.

[0110] In an optional embodiment, the configuration parameters of port P1 include configuration parameters of dependent characteristics of service characteristic A, and forwarding node A configures the dependent characteristics of port P1 according to the configuration parameters of the dependent characteristics of service characteristic A. For example, the flow detection characteristic depends on clock synchronization, and forwarding node A configures the clock characteristics at port P1 according to the configuration parameters of the dependent characteristics of the flow detection characteristic. For example, the clock characteristics can be clock characteristics based on the Institute of Electrical and Electronics Engineers (IEEE) 1588 protocol, the International Telecommunication Union Telecommunication Standardization Sector (ITU-T for ITU Telecommunication Standardization Sector, ITU-T) G.8275.1 protocol, the network time protocol (NTP) or other clock protocols, for example, clock characteristics based on IEEE1588 version 2 (version 2, V2) or NTP. Optionally, network node A determines the dependent characteristics of service characteristic A, and network node A generates the configuration parameters of the dependent characteristics according to the dependent characteristics of service characteristic A. Alternatively, network node A generates the configuration parameters of the dependent characteristics of service characteristic A according to the configuration information input by the user. In the case where network node A is the head node of the transmission path of data stream A, network node A may also generate configuration parameters of dependent characteristics of service characteristic A according to the configuration information sent by the control node.

[0111] Based on the above, it can be seen that in the process of network node A determining the configuration parameters of port P1, factors such as the service function of port P1, the type of service feature A supported by the previous hop node and next hop node of forwarding node A, the load sharing of the port (multi-path situation), the dependency characteristics of service feature A, and the configuration information input by the user are considered. Therefore, the reliability of the configuration parameters determined by network node A is relatively high.

[0112] The above content of S502 introduces the content of the configuration parameters of port P1 and the implementation process of network node A determining the configuration parameters of port P1. The following introduces the implementation process of network node A using the configuration parameters of port P1 to configure the service of port P1.

[0113] As described above, network node A performs service configuration on port P1 by sending configuration parameters of port P1 to forwarding node A. Optionally, network node A sends a configuration message to forwarding node A, the configuration message including configuration parameters of port P1, and forwarding node A performs service configuration on port P1 according to the configuration parameters included in the configuration message. For ease of description, the configuration message used to perform service configuration on port P1 is referred to as a port configuration message. In one embodiment, network node A is a control node, and the port configuration message is a first protocol message, including but not limited to SNMP messages and NETCONF messages. In another embodiment, network node A is the head node of the transmission path of data stream A, and the port configuration message is a second protocol message, including but not limited to GRASP messages or XLDP messages. Taking the example that the port configuration messages are GRASP messages and XLDP messages respectively, the implementation method of network node A performing service configuration on port P1 is introduced in two embodiments.

[0114] First embodiment: the port configuration message is a GRASP message, which includes a configuration object key-value pair field, and the configuration object key-value pair field is used to carry configuration parameters of port P1. Forwarding node A performs service configuration on port P1 according to the GRASP message.

[0115] For example, the GRASP message (ie, the port configuration message) is as follows: Figure 8 As shown. At least one configuration object key-value pair field in the GRASP message is used to carry the configuration parameters of port P1 to indicate the service configuration of port P1. Taking the example that the configuration parameters of port P1 include the identifier and enable indication information of port P1, the identifier of port P1 and the enable indication information are respectively located in a configuration object key-value pair field. In one example, the n configuration object key-value pair fields in the GRASP message include a first configuration object key-value pair field (e.g., configuration object key-value pair field 1) and a second configuration object key-value pair field (e.g., configuration object key-value pair field 2), the identifier "P1" of port P1 is located in the first configuration object key-value pair field, and the enable indication information is located in the second configuration object key-value pair field. The identifier and enable indication information of port P1 carried by the GRASP message as a port configuration message are respectively shown in Table 6 below.

[0116] Table 6

[0117]

[0118]

[0119] 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 in-flow detection service" or "configure slice service". The value of the configuration object key subfield (that is, configuration object key subfield 1) in the first configuration object key-value pair field is "port identifier", and the value of the configuration object value subfield (that is, configuration object value subfield 1) in the first configuration object key-value pair field is the identifier "P1" of port P1. When the value of the configuration object name field is "configure in-flow detection service", the value of the configuration object key subfield (that is, 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 (that is, configuration object value subfield 2) in the second configuration object key-value pair field is "1" or "0". When the value of the configuration object name field is "Configure 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 enable indication information. For example, for a port configuration message (i.e., a GRASP message): when the value of the configuration object key subfield 1 is "port identifier", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Y1", and the value of the configuration object value subfield 2 is "1", the port configuration message is used to indicate that the IPCA function is enabled for port P1, and forwarding node A enables the IPCA function for port P1 according to the port configuration message, and feeds back a configuration response message including the enabling result to network node A; when the value of the configuration object key subfield 1 is "port identifier", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Y1", and the value of the configuration object value subfield 2 is "0", the port configuration message is used to indicate that the IPCA function is disabled for port P1, and forwarding node A disables the IPCA function for port P1 according to the port configuration message, and feeds back a configuration response message including the enabling result to network node A.Similarly, when the value of the configuration object key subfield 1 is "port identifier", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Y2", and the value of the configuration object value subfield 2 is "1", the port configuration message is used to indicate that the IFIT function is enabled for port P1, and forwarding node A enables the IFIT function for port P1 according to the port configuration message, and feeds back a configuration response message including the enabling result to network node A; when the value of the configuration object key subfield 1 is "port identifier", the value of the configuration object value subfield 1 is "P1", the value of the configuration object key subfield 2 is "Y2", and the value of the configuration object value subfield 2 is "0", the port configuration message is used to indicate that the IFIT function is disabled for port P1, and forwarding node A disables the IFIT function for port P1 according to the port configuration message, and feeds back a configuration response message including the disabling result to network node A. And so on.

[0120] In the first embodiment, the configuration response message is a GRASP message, and at least one configuration object key-value pair field may be used to carry the configuration result (eg, enabling result). For example, the configuration result carried by the configuration response message is shown in Table 7 below.

[0121] Table 7

[0122]

[0123] The configuration object key-value pair field described in Table 7 and the second configuration object key-value pair field described in Table 6 may be the same configuration object key-value pair field. Referring to Table 7, the value "A2" of the message type field indicates that the type of the GRASP message is a response message (a configuration response message in this embodiment), 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 is "Y1", "Y2", "Y3", "Y4" or "Y5", the value of the configuration object value subfield is the configuration result, the configuration result is 0 or an error code, and the configuration result "0" is used to indicate successful configuration. For example, for the configuration response message (i.e., GRASP message): when the value of the configuration object key subfield is "Y1", the configuration object value subfield carries the configuration result of the IPCA service; when the value of the configuration object key subfield is "Y2", the configuration object value subfield carries the configuration result of the IFIT service; when the value of the configuration object key subfield is "Y3", the configuration object value subfield carries the configuration result of the FlexE service. And so on.

[0124] Second embodiment: The port configuration message is an XLDP message, which includes a PDU. The TLV field in the PDU is used to carry the configuration parameters of the port P1. The forwarding node A performs service configuration on the port P1 according to the XLDP message. For example, the XLDP message (that is, the port configuration message) is as follows: Fig. 9 As shown, the configuration parameters of port P1 are carried in the same L1 TLV field. Taking the example that the configuration parameters of port P1 include the identifier and enable indication information of port P1, the identifier of port P1 and the enable indication information can be respectively located in an L2TLV field, and the L2 TLV field used to carry the identifier of port P1 and the L2 TLV field used to carry the enable 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 "P1" of port P1 is located in the first TLV field, and the enable indication information is located in the second TLV field. The identifier and enable indication information of port P1 carried by the XLDP message as the port configuration message are shown in Table 8 below.

[0125] Table 8

[0126]

[0127] Referring to Table 8, the value "A1" of the message type field indicates that the type of the XLDP message is a configuration message (a channel message, a port configuration message in this embodiment), 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 identifier", and the value of the value subfield in the first TLV field is the identifier "P1" of port P1. The value of the type subfield in the second TLV field is "C11", "C21", "C31", "C41" or "C51", and 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, for the port configuration message (i.e., XLDP message): when 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 identifier", 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 L1 When the value of the type subfield in the TLV field is "C1", the value of the type subfield in the first TLV field is "port identifier", 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 port P1. Forwarding node A disables the IPCA function for port P1 according to the port configuration message, and feeds back a configuration response message including the disabling result to 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 identifier", 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 "1", the port configuration message is used to indicate that the IFIT function (that is, the service function of the IFIT service) is enabled for port P1, and the forwarding node A enables the IFIT function for 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 L1 When the value of the type subfield in the TLV field is "C2", the value of the type subfield in the first TLV field is "port identifier", 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 port configuration message is used to indicate that the IFIT function of port P1 is disabled, and forwarding node A disables the IFIT function of port P1 according to the port configuration message, and feeds back a configuration response message including the disablement result to network node A. And so on.

[0128] In the second embodiment, the configuration response message is an XLDP message, and the L2 TLV field is used to carry the configuration result (eg, enabling result). For example, the configuration result carried by the configuration response message is shown in Table 9 below.

[0129] Table 9

[0130]

[0131] Referring to Table 9, the value "A2" of the message type field indicates that the type of the XLDP message is a response message (a configuration response message in this embodiment), 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 the configuration result, the configuration result is 0 or an error code, and the configuration result "0" is used to indicate successful configuration. For example, for the configuration response message (i.e., XLDP message): when the value of the type subfield in the L1 TLV field is "C1" and the value of the type 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; when the value of the type subfield in the L1 TLV field is "C2" and the value of the type 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; when the value of the type subfield in the L1 TLV field is "C3" and the value of the type 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.

[0132] After network node A performs service configuration corresponding to service characteristic A on port P1 of forwarding node A, in the process of forwarding node A forwarding data stream A through port P1, service operations corresponding to the service can be performed on data stream A at port P1.

[0133] In one embodiment, service characteristic A is a flow detection characteristic, and the service corresponding to service characteristic A is a flow detection service. After network node A configures the flow detection service on port P1 of forwarding node A, forwarding node A performs a flow detection operation on data stream A at port P1 during the process of forwarding data stream A through port P1. For example, forwarding node A is the head node of the transmission path of data stream A, and port P1 is the egress port of data stream A in forwarding node A. Forwarding node A performs flow detection encapsulation and flow detection on the message whose egress port in data stream A is port P1, for example, forwarding node A collects packet loss information of the message of data stream A at port P1 (for example, counting the number of messages of data stream A sent from port P1), delay information (for example, collecting the timestamp of the message of data stream A sent from port P1), etc. For another example, forwarding node A is an intermediate node on the transmission path of data stream A. Forwarding node A performs in-flow detection on the message of data stream A at port P1 according to the in-flow detection encapsulation information carried by the message of data stream A. For example, forwarding node A collects packet loss information and delay information of the message of data stream A at port P1. For another example, forwarding node A is a tail node of the transmission path of data stream A, and port P1 is an egress port of data stream A in forwarding node A. Forwarding node A performs in-flow detection and decapsulation on the message of data stream A and performs in-flow detection. For example, forwarding node A collects packet loss information and delay information of the message of data stream A at port P1. Optionally, forwarding node A includes a port chip (also called an interface chip, interface board, etc.). When forwarding node A is a head node, the port chip performs in-flow detection and encapsulation on the message of data stream A. When forwarding node A is a tail node, the port chip performs in-flow detection and decapsulation on the message of data stream A. In addition, the port chip performs flow detection on the message of data stream A, and the port chip can add the collected packet loss information, delay information, etc. to the message of data stream A, which is not limited in the embodiments of the present application. In one example, service characteristic A is an IPCA characteristic, and the service corresponding to service characteristic A is an IPCA service. After network node A configures the IPCA service for port P1, forwarding node A performs IPCA detection on data stream A at port P1 during the process of forwarding data stream A through port P1. In another example, service characteristic A is an IFIT characteristic, and the service corresponding to service characteristic A is an IFIT service. After network node A configures the IFIT service for port P1, forwarding node A performs IFIT detection on data stream A at port P1 during the process of forwarding data stream A through port P1.

[0134] In another embodiment, service characteristic A is a slice characteristic, and the service corresponding to service characteristic A is a slice service. After network node A configures the port P1 of forwarding node A for the slice service, forwarding node A performs a slice service operation on data stream A at port P1 during the process of forwarding data stream A through port P1. For example, forwarding node A is the head node of the transmission path of data stream A, and forwarding node A performs a slice encapsulation corresponding to the slice service on the message whose egress port in data stream A is port P1, and forwards the message of data stream A through the network slice corresponding to the slice service. For example, forwarding node A adds a slice identifier corresponding to the slice service to the message whose egress port in data stream A is port P1, determines the slice port corresponding to the slice service in port P1 according to the slice identifier, and forwards the message of data stream A through the slice port. For another example, forwarding node A is an intermediate node on the transmission path of data stream A, and forwarding node A determines the slice port corresponding to the slice service in port P1 according to the slice identifier in the message whose egress port in data stream A is port P1, and forwards the message of data stream A through the slice port. For another example, forwarding node A is the tail node of the transmission path of data stream A, and forwarding node A deletes the slice identifier in the message whose egress port is port P1 in data stream A. Optionally, forwarding node A includes a port chip, and the port chip performs a slice service operation on data stream A at port P1, wherein the slice service is a FlexE service, a channelized sub-interface service, or a FlexChannel service, and the network slice corresponding to the slice service is a network slice based on a FlexE interface, a network slice based on a channelized sub-interface, or a network slice based on a FlexChannel.

[0135] In summary, in the network configuration scheme provided by the embodiment of the present application, 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 characteristics, and then performs service configuration on the port of the forwarding node based on the service characteristics, so that the service operation corresponding to the service characteristics is performed on the data stream at the port during the process of the forwarding node forwarding the data stream. In the embodiment of the present application, the control node or the head node performs service configuration on the port on the transmission path of the data stream, which simplifies the service configuration process and reduces the difficulty of service configuration.

[0136] For the convenience of description, the service corresponding to service characteristic A is referred to as service A hereinafter.

[0137] In an optional embodiment, before network node A performs service configuration on port P1 of forwarding node A based on service characteristic A (i.e., before S502), network node A queries whether port P1 has been configured with service A (e.g., whether port P1 has been configured with service A for data stream 1). In the case that port P1 is not configured with service A, network node A performs service A configuration on port P1 (i.e., executes S502). In the case that port P1 has been configured with service A, network node A does not perform service A configuration on port P1.

[0138] For example, network node A sends a query message to forwarding node A, the query message includes port query information, the port query information is used to indicate whether the query port P1 has been configured with service A, and forwarding node A determines whether port P1 has been configured with service A according to the query message and sends a query response message including the query result to network node A. Among them, the port query information includes the identifier of port P1 and the query indication information. For the convenience of description, the query message used to query whether port P1 has been configured with service A is referred to as a port query message. In one embodiment, network node A is a control node, and the port query message is a first protocol message, such as an SNMP message or a NETCONF message. In another embodiment, network node A is the head node of the transmission path of data stream A, and the port query message is a second protocol message, and the second protocol message includes a GRASP message or an XLDP message. Taking the port query messages as GRASP messages and XLDP messages as examples, the implementation method of network node A querying whether port P1 has been configured with service A is introduced in two embodiments.

[0139] First embodiment: The port query message is a GRASP message, which includes a configuration object key-value pair field, and the configuration object key-value pair field is used to carry port query information. Forwarding node A queries whether port P1 is configured with service A according to the port query information, and sends a query response message including the query result to network node A. For example, the GRASP message (i.e., the port query message) is as follows: Figure 8As shown, at least one configuration object key-value pair field in the GRASP message is used to carry port query information to query whether port P1 is configured with service A. Taking the port query information including the identifier of port P1 and the query indication information as an example, the identifier of port P1 and the query indication information are respectively located in a configuration object key-value pair field. In one example, the n configuration object key-value pair fields in the GRASP message include a first configuration object key-value pair field (e.g., configuration object key-value pair field 1) and a second configuration object key-value pair field (e.g., configuration object key-value pair field 2), the identifier "P1" of port P1 is located in the first configuration object key-value pair field, and the query indication information is located in the second configuration object key-value pair field. The identifier and query indication information of port P1 carried by the GRASP message as a port query message are respectively shown in Table 10 below.

[0140] Table 10

[0141]

[0142] 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, in this embodiment, the query message is a port query message), and the value of the configuration object name field is "query with-flow 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 identifier", 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 identifier "P1" of port P1. When the value of the configuration object name field is "query with-flow detection service configuration", 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 "Z1" or "Z2", and when 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 the query indication information. For example, for the port query message (i.e., GRASP message): when the value of the configuration object key subfield 1 is "port identifier", the value of the configuration object value subfield 1 is "P1", and the value of the configuration object key subfield 2 is "Z1", the port query message is used to indicate whether the query port P1 is configured with IPCA service, and the forwarding node A determines whether the port P1 is configured with IPCA service according to the port query message, and feeds back a query response message including the query result to the network node A; when the value of the configuration object key subfield 1 is "port identifier", the value of the configuration object value subfield 1 is "P1", and the value of the configuration object key subfield 2 is "Z2", the port query message is used to indicate whether the query port P1 is configured with IFIT service, and the forwarding node A determines whether the port P1 is configured with IFIT service according to the port query message, and feeds back a query response message including the query result to the network node A. And so on. In the first embodiment, the configuration object value subfield 2 is an empty field. In other embodiments, the configuration object value subfield 2 can also carry information, and the embodiment of the present application does not limit this.

[0143] In the first embodiment, the query response message is a GRASP message, and the query result can be carried by using at least one configuration object key value. For example, the query response message can be obtained by adding the query result to the configuration object value subfield in the second configuration object key value pair field of the port query message. For example, the query result carried by the GRASP message as the query response message is shown in Table 11 below.

[0144] Table 11

[0145]

[0146]

[0147] The first configuration object key-value pair field described in Table 11 and the first configuration object key-value pair field described in Table 10 may be the same configuration object key-value pair field, and the second configuration object key-value pair field described in Table 11 and the second configuration object key-value pair field described in Table 10 may be the same configuration object key-value pair field. Referring to Table 11, the value "A2" of the message type field indicates that the type of the GRASP message is a response message (a query response message in this embodiment), and the value of the configuration object name field is "query for in-flow detection service configuration" or "query for 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 identifier", 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 identifier "P1" of port P1. When the value of the configuration object name field is "query flow detection service configuration", the value of the configuration object key subfield (that is, configuration object key subfield 2) in the second configuration object key-value pair field is "Z1" or "Z2", and when 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 (that is, configuration object value subfield 2) in the second configuration object key-value pair field is "1" or "0", and 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 to indicate that the port P1 has been configured with the corresponding service, and the value "0" of the configuration object value subfield 2 is used to indicate that the port P1 has not been configured with the corresponding service. For example, for the query response message (i.e., GRASP message): when the value of the configuration object key subfield 1 is "port identifier", 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 to indicate that the port P1 has been configured with the IPCA service; when the value of the configuration object key subfield 1 is "port identifier", 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 to indicate that the port P1 has been configured with the IPCA service. Port P1 is not configured with IPCA service; when the value of configuration object key subfield 1 is "port identifier", the value of configuration object value subfield 1 is "P1", the value of configuration object key subfield 2 is "Z2" and the value of configuration object value subfield 2 is "1", the query response message is used to indicate that port P1 is configured with IFIT service; when the value of configuration object key subfield 1 is "port identifier", the value of configuration object value subfield 1 is "P1", the value of configuration object key subfield 2 is "Z2" and the value of configuration object value subfield 2 is "0", the query response message is used to indicate that port P1 is not configured with IFIT service. And so on.

[0148] Second embodiment: The port query message is an XLDP message, which includes a PDU. The TLV field in the PDU is used to carry port query information. The forwarding node A queries whether the port P1 is configured with service A according to the port query information, and sends a query response message including the query result to the network node A. For example, the XLDP message (i.e., the port query message) is as follows: Fig. 9 As shown, the port query information is carried in the same L1 TLV field. Taking the example that the port query information includes the identifier of port P1 and the query indication information, the identifier of port P1 and the query indication information can be respectively located in an L2 TLV field, and the L2 TLV field used to carry the identifier of port P1 and the L2 TLV field used to carry 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 L2TLV fields in the same L1 TLV field, the identifier of port P1 is "P1" located in the first TLV field, and the query indication information is located in the second TLV field. The identifier and query indication information of port P1 carried by the XLDP message as the port query message are shown in Table 12 below.

[0149] Table 12

[0150]

[0151]

[0152] Referring to Table 12, the value "A1" of the message type field indicates that the type of the XLDP message is a query message (a channel message, in this embodiment, the query message is a port query message), 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 identifier", and the value of the value subfield in the first TLV field is the identifier "P1" of port P1. The value of the type subfield in the second TLV field is "D11", "D21", "D31", "D41" or "D51". For example, for the port query message (i.e., XLDP message): when 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 identifier", the value of the value subfield in the first TLV field is "P1", and the value of the type subfield in the second TLV field is "D11", the port query message is used to indicate whether the port P1 is configured with the IPCA service, and 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 the query result to the network node A; when 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 identifier", the value of the value subfield in the first TLV field is "P1", and the value of the type subfield in the second TLV field is "D21", the port query message is used to indicate 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 a query response message including the query result to the network node A. And so on. In the second embodiment, the value subfield in the second TLV field is an empty field and does not carry any information. In other embodiments, the value subfield in the second TLV field may also carry information, which is not limited in the embodiment of the present application.

[0153] In the second embodiment, the query response message is an XLDP message, and the query result can be carried using the L2 TLV field. For example, the query response message can be obtained by adding the query result to the value subfield in the second TLV field of the port query message. For example, the query result carried by the XLDP message as the query response message is shown in Table 13 below.

[0154] Table 13

[0155]

[0156] Referring to Table 13, the value "A2" of the message type field indicates that the type of the XLDP message is a response message (a response message, in this embodiment, the response message is a query response message), 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 identifier", and the value of the value subfield in the first TLV field is the identifier "P1" of port P1. The value of the type subfield in the second TLV field is "D11", "D21", "D31", "D41" or "D51", and 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 been configured with the corresponding service, and the value "0" of the value subfield in the second TLV field is used to indicate that the port P1 has not been configured with the corresponding service. For example, for the query response message (i.e., XLDP message): when 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 identifier", 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 the port P1 has been configured with the IPCA service; when 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 identifier", 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 "0", the port query message is used to indicate that the port P1 is not configured with the IPCA service; in the case of the L1 When the value of the type subfield in the TLV field is "D2", the value of the type subfield in the first TLV field is "port identifier", 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", and the value of the value subfield in the second TLV field is "1", the port query message is used to indicate that the port P1 is configured with the IFIT service; when the value of the type subfield in the L1TLV field is "D2", the value of the type subfield in the first TLV field is "port identifier", 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", and the value of the value subfield in the second TLV field is "0", the port query message is used to indicate that the port P1 is not configured with the IFIT service. And so on.

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

[0158] In one embodiment, network node A is a control node, and the node configuration message is a first protocol message, such as an SNMP message or a NETCONF message. In another embodiment, network node A is a head node of a transmission path of data stream A, and the node configuration message is a second protocol message, and the second protocol message includes a GRASP message or an XLDP message. The following takes the case where the node configuration messages are GRASP messages and XLDP messages as examples, and introduces the implementation method of network node A performing service configuration on forwarding node A in two embodiments.

[0159] First embodiment: The node configuration message is a GRASP message, which includes a configuration object key-value pair field, and the configuration object key-value pair field is used to carry node configuration parameters. Forwarding node A uses the node configuration parameters to perform service configuration on forwarding node A, and sends a configuration response message including the configuration result to network node A. For example, the GRASP message is as follows Figure 8 As shown, at least one configuration object key-value pair field in the GRASP message is used to carry node configuration parameters to perform service configuration on forwarding node A. Taking the node configuration parameters including enabling indication information as an example, the node configuration parameters carried by the GRASP message as the node configuration message are shown in Table 14 below.

[0160] Table 14

[0161]

[0162] 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, in this embodiment, the configuration message is a node configuration message), and the value of the configuration object name field is "Configure In-Flow Detection Service" or "Configure Slice Service". When the value of the configuration object name field is "Configure In-Flow Detection Service", the value of the configuration object key subfield in the configuration object key-value pair field is "G1" or "G2", and when 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", and the value of the configuration object value subfield is enable indication information. The value "1" of the configuration object value subfield is used to indicate enabling the corresponding service function, and the value "0" of the configuration object value subfield is used to indicate disabling the corresponding service function. For example, for the node configuration message (i.e., the GRASP message): when the value of the configuration object key subfield is "G1" and the value of the configuration object value subfield is "1", the node configuration message is used to indicate that the IPCA function is enabled for forwarding node A, and forwarding node A enables the IPCA function for forwarding node A according to the node configuration message, and feeds back a configuration response message including the enabling result to network node A; when the value of the configuration object key subfield is "G1" and the value of the configuration object value subfield is "0", the node configuration message is used to indicate that the IPCA function is disabled for forwarding node A, and forwarding node A disables the IPCA function for forwarding node A according to the node configuration message, and feeds back a packet to network node A. In the case where the value of the configuration object key subfield is "G2" and the value of the configuration object value subfield is "1", the node configuration message is used to indicate that the IFIT function is enabled for forwarding node A, and forwarding node A enables the IFIT function for forwarding node A according to the node configuration message, and feeds back a configuration response message including the enabling result to network node A; in the case where the value of the configuration object key subfield is "G2" and the value of the configuration object value subfield is "0", the node configuration message is used to indicate that the IFIT function is disabled for forwarding node A, and forwarding node A disables the IFIT function for forwarding node A according to the node configuration message, and feeds back a configuration response message including the enabling result to network node A. And so on. In the first embodiment, the node configuration message also includes the identifier of forwarding node A, and the identifier of forwarding node A is carried in a configuration object key-value pair field or carried in other locations of the node configuration message, such as carried in the destination address field.

[0163] In this first embodiment, the configuration response message is a GRASP message, and the configuration object key-value pair field can be used to carry the configuration result. The configuration result carried by the configuration response message is similar to Table 7 and is not described here (the difference from Table 7 is that the value of the configuration object key subfield in this embodiment is "G1", "G2", "G3", "G4" or "G5").

[0164] Second embodiment: the node configuration message is an XLDP message, the XLDP message includes a PDU, the TLV field in the PDU is used to carry node configuration parameters, forwarding node A performs service configuration on forwarding node A according to the node configuration parameters, and sends a configuration response message including the configuration result to network node A. For example, the XLDP message (i.e., the node configuration message) is as follows Fig. 9 As shown, the node configuration parameters are carried in the same L1 TLV field. Taking the node configuration parameters including the enabling indication information as an example, the enabling indication information is located in the L2 TLV field in the L1 TLV field. The node configuration parameters carried by the XLDP message as the node configuration message are shown in Table 15 below.

[0165] Table 15

[0166]

[0167] Referring to Table 15, the value "A1" of the message type field indicates that the type of the XLDP message is a configuration message (a channel message, in this embodiment, the configuration message is a node configuration message), and the value of the L1 TLV type field is "E1", "E2", "E3", "E4" or "E5". The value of the type subfield in an L2 TLV field under the L1 TLV field is "E11", "E21", "E31", "E41" or "E51", and the value of the value subfield in the L2 TLV field is "1" or "0". 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, for the node configuration message (i.e., the XLDP message): when 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 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; when 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 "0", the node configuration message is used to indicate that the IPCA function is disabled for the forwarding node A, and 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; when the value of the type subfield in the L1 TLV field is "E2", the L2 When the value of the type subfield in the TLV field is "E21" and the value of the value subfield in the L2 TLV field is "1", the node configuration message is used to indicate that the IFIT function is enabled for forwarding node A, and forwarding node A enables the IFIT function for forwarding node A according to the node configuration message, and feeds back a configuration response message including the enabling result to network node A; when 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", and the value of the value subfield in the L2 TLV field is "0", the node configuration message is used to indicate that the IFIT function is disabled for forwarding node A, and forwarding node A disables the IFIT function for forwarding node A according to the node configuration message, and feeds back a configuration response message including the enabling result to network node A. And so on. The node configuration message also includes an identifier of forwarding node A, and the identifier of forwarding node A is carried in an L2 TLV field or carried in other locations in the node configuration message.

[0168] In the second embodiment, the configuration response message is an XLDP message, and the configuration result can be carried by using the L2 TLV field. In this embodiment, the configuration result carried by the configuration response message is similar to that in Table 9 above, and is not described here in detail (different from Table 9 above, 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 in the L2 TLV field is "E11", "E21", "E31", "E41" or "E51").

[0169] In an optional embodiment, before network node A performs service configuration on forwarding node A based on service characteristic A, network node A queries whether forwarding node A has been configured with service A (e.g., queries whether forwarding node A has been globally configured with service A, e.g., queries whether forwarding node A has been configured with service A for data stream 1). If forwarding node A is not configured with service A, network node A performs service A configuration on forwarding node A. If forwarding node A has been configured with service A, network node A does not perform service A configuration on forwarding node A.

[0170] For example, network node A sends a query message to forwarding node A, the query message includes node query information, the node query information is used to indicate whether forwarding node A has been configured with service A, forwarding node A determines whether forwarding node A has been configured with service A according to the query message and sends a query response message including the query result to network node A. For the convenience of description, the query message used to query whether forwarding node A has been configured with 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.

[0171] In one embodiment, network node A is a control node, and the node query message is an SNMP1 message or a NETCONF message. In another embodiment, network node A is a head node of a transmission path of data stream A, and the node query message is a GRASP message or an XLDP message. The following uses the example that the node query messages are GRASP messages and XLDP messages, respectively, to introduce the implementation method of network node A querying whether forwarding node A has been configured with service A in two embodiments.

[0172] First embodiment: The node query message is a GRASP message, which includes a configuration object key-value pair field, and the configuration object key-value pair field is used to carry node query information. Forwarding node A queries whether forwarding node A is configured with service A according to the node query information, and sends a query response message including the query result to network node A. For example, the GRASP message (i.e., the node query message) is as follows: Figure 8As shown, at least one configuration object key-value pair field in the GRASP message is used to carry node query information to query whether forwarding node A is configured with service A. Taking the node query information including query indication information as an example, the query indication information carried by the GRASP message as the node query message is shown in Table 16 below.

[0173] Table 16

[0174]

[0175] 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, in this embodiment, the query message is a node query message), and the value of the configuration object name field is "query with-flow detection service configuration" or "query slice service configuration". When the value of the configuration object name field is "query with-flow detection service configuration", the value of the configuration object key subfield in the configuration object key-value pair field is "F1" or "F2", and when 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, for the node query message (i.e., GRASP message): when the value of the configuration object key subfield is "F1", the node query message is used to indicate whether the forwarding node A is configured with the IPCA service, and the forwarding node A determines whether the forwarding node A is configured with the IPCA service based on the node query message, and feeds back a query response message including the query result to the network node A; when the value of the configuration object key subfield is "F2", the node query message is used to indicate whether the forwarding node A is configured with the IFIT service, and the forwarding node A determines whether the forwarding node A is configured with the IFIT service based on the node query message, and feeds back a query response message including the query result to the network node A. And so on. In this first embodiment, the configuration object value subfield is an empty field. In other embodiments, the configuration object value subfield may also carry information, which is not limited in the embodiments of the present application. The node query message also includes the identifier of the forwarding node A, and the identifier of the forwarding node A is carried in a configuration object key-value pair field or carried in other locations of the node configuration message.

[0176] In the first embodiment, the query response message is a GRASP message, and the query result can be carried by using at least one configuration object key value. For example, the query response message can be obtained by adding the query result to the configuration object value subfield of the node query message. For example, the query result carried by the GRASP message as the query response message is shown in Table 17 below.

[0177] Table 17

[0178]

[0179] The configuration object key-value pair field described in Table 17 and the configuration object key-value pair field described in Table 16 may be the same configuration object key-value pair field. Referring to Table 17, the value "A2" of the message type field indicates that the type of the GRASP message is a response message (a query response message in this embodiment), and the value of the configuration object name field is "query with-flow detection service configuration" or "query slice service configuration". In the case where the value of the configuration object name field is "query with-flow 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", and the value of the configuration object value subfield is the query result. The value "1" of the configuration object value subfield is used to indicate that forwarding node A has configured the corresponding service, and the value "0" of the configuration object value subfield is used to indicate that forwarding node A has not configured the corresponding service. For example, for the query response message (i.e., GRASP message): when 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 the forwarding node A has been configured with the IPCA service; when the value of the configuration object key subfield is "F1" and the value of the configuration object value subfield is "0", the query response message is used to indicate that the forwarding node A has not been configured with the IPCA service; when the value of the configuration object key subfield is "F2" and the value of the configuration object value subfield is "1", the query response message is used to indicate that the forwarding node A has been configured with the IFIT service; when the value of the configuration object key subfield is "F2" and the value of the configuration object value subfield is "0", the query response message is used to indicate that the forwarding node A has not been configured with the IFIT service. And so on.

[0180] Second embodiment: the node query message is an XLDP message, the XLDP message includes a PDU, the TLV field in the PDU is used to carry node query information, forwarding node A queries whether forwarding node A is configured with service A according to the node query information, and sends a query response message including the query result to network node A. For example, the XLDP message (i.e., the node query message) is as follows Fig. 9 As shown, the node query information is carried in the same L1 TLV field. Taking the node query information including the query indication information as an example, the query indication information is located in an L2 TLV field. In an example, the query indication information carried by the XLDP message as the node query message is shown in Table 18 below.

[0181] Table 18

[0182]

[0183] Referring to Table 18, the value "A1" of the message type field indicates that the type of the XLDP message is a query message (a channel message, and in this embodiment, the query message is a node query message), 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 an L2 TLV field under the L1 TLV field is "R11", "R21", "R31", "R41" or "R51". For example, for the node query message (i.e., XLDP message): when the value of the type subfield in the L1 TLV field is "R1" and the value of the type subfield in the L2 TLV field is "R11", the node query message is used to indicate whether the forwarding node A is configured with the IPCA service. The forwarding node A determines whether the forwarding node A is configured with the IPCA service based on the node query message and feeds back a query response message including the query result to the network node A; when the value of the type subfield in the L1TLV field is "R2" and the value of the type subfield in the L2 TLV field is "R21", the node query message is used to indicate whether the forwarding node A is configured with the IFIT service. The forwarding node A determines whether the forwarding node A is configured with the IFIT service based on the node query message and feeds back a query response message including the query result to the network node A; when the value of the type subfield in the L1 TLV field is "R3" and the value of the type subfield in the L2 TLV field is "R4". When the value of the type subfield in the TLV field is "R31", the node query message is used to indicate whether the forwarding node A is configured with the FlexE service. The forwarding node A determines whether the forwarding node A is configured with the FlexE service based on the node query message and feeds back a query response message including the query result to the network node A. In this second embodiment, the value subfield in the L2 TLV field is an empty field and does not carry any information. In other embodiments, the value subfield in the L2 TLV field may carry information, which is not limited in the embodiments of the present application. The node query message also includes an identifier of the forwarding node A, which is carried in an L2 TLV or carried in other locations in the node configuration message.

[0184] In the second embodiment, the query response message is an XLDP message, and the query result can be carried using the L2 TLV field. For example, the query response message can be obtained by adding the query result to the value subfield in the L2 TLV field of the node query message. For example, the query result carried by the XLDP message as the query response message is shown in Table 19 below.

[0185] Table 19

[0186]

[0187] Referring to Table 19, the value "A2" of the message type field indicates that the type of the XLDP message is a response message (a channel message, and in this embodiment, the response message is a query response message), 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 an L2 TLV field 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 "1" of the value subfield in the L2 TLV field is used to indicate that the forwarding node A has been configured with the corresponding service, and the value "0" of the value subfield in the L2 TLV field is used to indicate that the forwarding node A has not been configured with the corresponding service. For example, for the query response message (i.e., XLDP message): when 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", and the value of the value subfield in the L2 TLV field is "1", the node query message is used to indicate that the forwarding node A has been configured with the IPCA service; when 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", and the value of the value subfield in the L2 TLV field is "0", the node query message is used to indicate that the forwarding node A is not configured with the IPCA service; when 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", and the value subfield in the L2 TLV field is "1", the node query message is used to indicate that the forwarding node A has been configured with the IFIT service; when the value of the type subfield in the L1 TLV field is "R2", the value of the L2 TLV field is "R21", and the value subfield in the L2 TLV field is "1", the node query message is used to indicate that the forwarding node A has been configured with the IFIT service; When the value of the type subfield in the TLV field is "R11" and the value of the value subfield in the L2 TLV field is "0", the node query message is used to indicate that the forwarding node A is not configured with the IFIT service.

[0188] In an optional embodiment, before S502, network node A obtains (or identifies) port P1 on the transmission path of data stream A, that is, identifies port P1 in forwarding node A located on the transmission path. For example, network node A receives path information sent by forwarding node A, and the path information includes an identifier of port P1, and network node A obtains port P1 on the transmission path according to the path information. The path information is obtained based on the message of data stream A during the process of forwarding the message of data stream A by forwarding node A. For example, the path information is obtained by forwarding node A based on the data message or detection message of data stream A, and the detection message of data stream A is generated by the head node of the transmission path of data stream A based on the data message of data stream A, and the detection message is used to detect 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 through SNMP, NETCONF, etc. In another example, network node A is the head node of the transmission path of data stream A, and forwarding node A sends path information to network node A through GRASP, XLDP, etc.

[0189] In the embodiment of the present application, port P1 is a port in forwarding node A for receiving or sending data stream A (that is, an ingress port or egress port of data stream A in forwarding node A), and the above-mentioned path information obtained by forwarding node A based on the message of data stream A may also include at least one of the following: indication information of data stream A; flow direction of data stream A in forwarding node A. The flow direction is the direction from the port in forwarding node A for receiving data stream A (that is, the ingress port) to the port in forwarding node A for sending data stream A (that is, the egress port). The indication information of data stream A may be information that can be used to indicate data stream A, such as an IPv6 flow label, APN ID, a five-tuple, a triplet, a two-tuple, etc. Optionally, the above-mentioned path information obtained by forwarding node A based on the message of data stream A includes indication information "A" of data stream A, flow direction of data stream A in forwarding node A, identifier of the ingress port of data stream A in forwarding node A, and identifier of the egress port.

[0190] In an example, the path information obtained by forwarding node A based on the message of data flow A is shown in Table 20 below.

[0191] Table 20

[0192] Indication information of data stream A Flow direction Ingress Port Outgoing port A 1 Port 1 (for example, Eth0 / 0 / 1) Port 2 (for example, Eth0 / 0 / 2)

[0193] Referring to Table 20, the path information obtained by forwarding node A based on the message of data flow A includes indication information "A" of data flow A, flow direction "1" of data flow A in forwarding node A, identifier of the ingress port (e.g., Eth0 / 0 / 1) and the egress port (e.g., Eth0 / 0 / 2) of data flow A in forwarding node A. Based on Table 20, it can be seen 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 that the flow direction of data flow A in forwarding node A is from port 1 to port 2.

[0194] In another example, the path information obtained by forwarding node A based on the message of data flow A is shown in Table 21 below.

[0195] Table 21

[0196] Indication information of data stream A Flow direction Ingress Port Outgoing port A 1 Port 1 (for example, Eth0 / 0 / 1) Port 2 (for example, Eth0 / 0 / 2) A 2 Port 2 (for example, Eth0 / 0 / 2) Port 1 (for example, Eth0 / 0 / 1)

[0197] Referring to Table 21, it can be seen that forwarding node A obtains two sets of path information based on the message of data flow A, and the two sets of path information respectively include the indication information "A" of data flow A, the flow direction of data flow A in forwarding node A, and the identifier of the input port and the identifier of the output port of data flow A in forwarding node A. Based on the first set of path information (the path information recorded in the second row of Table 21), it can be seen that the input port of data flow A in forwarding node A is port 1, the output 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 (the path information recorded in the third row of Table 21), it can be seen that the input port of data flow A in forwarding node A is port 2, the output port is port 1, and the flow direction "2" is used for the direction from port 2 to port 1. Data flow A has two opposite flow directions in forwarding node A.

[0198] In another example, the path information obtained by forwarding node A based on the message of data flow A is shown in Table 22 below.

[0199] Table 22

[0200] Indication information of data stream A Flow direction Ingress Port Outgoing port A 1 Port 1 (for example, Eth0 / 0 / 1) Port 2 (for example, Eth0 / 0 / 2) A 3 Port 1 (for example, Eth0 / 0 / 1) Port 3 (for example, Eth0 / 0 / 3)

[0201] As shown in Table 22, forwarding node A obtains two sets of path information based on the message of data flow A, and the two sets of path information respectively include the indication information "A" of data flow A, the flow direction of data flow A in forwarding node A, the identifier of the inlet port of data flow A in forwarding node A, and the identifier of the outlet port of data flow A in forwarding node A. Based on the first set of path information (the path information recorded in the second row of Table 22), it can be seen that the inlet port of data flow A in forwarding node A is port 1, the outlet 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 (the path information recorded in the third row of Table 22), it can be seen that the inlet port of data flow A in forwarding node A is port 1, the outlet port is port 3, and the flow direction "3" is used for the direction from port 1 to port 3. It can be seen that data flow A has two flow directions in forwarding node A, and the two flow directions are from the same input port to different output ports. Based on this, it can be determined that data flow A has at least two transmission paths, and the at least two transmission paths can be load sharing paths. The at least two transmission paths perform load sharing on data flow A.

[0202] In the embodiment of the present application, the port P1 of the forwarding node A may be any port recorded in Tables 20 to 22 above. In addition to the information listed in Tables 20 to 22 above, the path information may also include other information. For example, the path information sent by the forwarding node A to the network node A may also include the identifier of the forwarding node A, and the network node A identifies the forwarding node A on the transmission path of the data stream A according to the path information.

[0203] In the embodiment of the present application, an example is taken in which network node A identifies forwarding node A on the transmission path of data stream A and port P1 in forwarding node A located on the transmission path based on path information sent by forwarding node A. In actual applications, each forwarding node on the transmission path of data stream A can obtain path information based on the message of data stream A and send the path information to network node A. Network node A can identify each forwarding node and the port in each forwarding node located on the transmission path based on the path information sent by each forwarding node on the transmission path. The implementation process of network node A identifying each forwarding node on the transmission path of data stream A and the port in each forwarding node located on the transmission path can refer to the implementation process of network node A identifying forwarding node A and port P1, which will not be repeated herein.

[0204] The embodiment of the present application takes the example of network node A performing service configuration on forwarding node A and port P1 based on service characteristic A as an example. Network node A can perform service configuration on each forwarding node supporting service characteristic A on the transmission path of data stream A and the ports in these forwarding nodes located on the transmission path based on service characteristic A. The configuration process of network node A on the forwarding nodes on the transmission path and the ports in these forwarding nodes can refer to the process of network node A configuring the service of forwarding node A and port P1, which will not be described in detail herein. In addition, in the process of network node A obtaining the configuration parameters of the forwarding nodes on the transmission path and the configuration parameters of the ports of these forwarding nodes, the path information sent by these forwarding nodes as shown in Tables 20 to 22 above can also be considered. For example, network node A determines the load sharing of these forwarding nodes for data stream A, the round-trip path of data stream A, etc. based on the path information sent by these forwarding nodes, and derives the configuration parameters of these forwarding nodes and the configuration parameters of the ports in these forwarding nodes located on the transmission path of data stream A based on service characteristic A combined with the load sharing of these forwarding nodes for data stream A, the round-trip path of data stream A, etc. based on the configuration parameters of these forwarding nodes and the configuration parameters of the ports in these forwarding nodes located on the transmission path of data stream A, which is not limited in the embodiment of the present application.

[0205] In the embodiment of the present application, after network node A receives the path information sent by the forwarding nodes on the transmission path of data stream A, it can also determine the transmission path according to the path information sent by these forwarding nodes and present the transmission path. Thus, the transmission path of data stream A can be visualized, which is convenient for users to analyze the transmission path of data stream A and the transmission status of data stream A.

[0206] In an embodiment of the present application, in the process of forwarding the data stream by the forwarding node on the transmission path of the data stream, the path information is obtained based on the message of the data stream, and the path information is sent 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 in the forwarding node located on the transmission path (that is, identifies the forwarding node and port through which the data stream passes) according to the path information sent by the forwarding node on the transmission path, and then performs business configuration on the forwarding node and port through which the data stream passes based on the business characteristics supported by the forwarding node through which the data stream passes. Thus, the present application can realize real-time perception of the forwarding node and port through which the data stream passes, and dynamically configure the business of the forwarding node and port through which the data stream passes according to the change of the transmission path, and dynamically cancel the business configuration of the forwarding node and port on the transmission path before the change after the transmission path changes. For example, the slicing configuration, flow detection configuration, etc. of the forwarding node and port on the transmission path before the change are dynamically canceled, so that these forwarding nodes release network bandwidth resources, forwarding resources, etc., avoid waste of network bandwidth, forwarding resources, etc., avoid data streams from not obtaining relevant reserved resources, and help to ensure the transmission performance of data streams.

[0207] GRASP and XLDP involved in the embodiments of the present application are both trusted protocols. These trusted protocols can provide trusted bearer pipes. The head node of the transmission path of the data stream sends configuration information and query messages to other forwarding nodes on the transmission path based on GRASP, XLDP, etc., which can ensure the reliability and security of the communication between the head node and these other forwarding nodes. It should be noted that in the process of describing GRASP messages (such as detection messages, configuration messages, query messages, response messages) and XLDP messages (such as detection messages, configuration messages, query messages, response messages) in the above embodiments, the values ​​of the relevant fields involved are only abstract descriptions and do not represent the actual values ​​of these fields. The actual values ​​of these fields need to be defined in combination with relevant standards. For example, the values ​​"A1" and "A2" of the message type field described in Table 2 and Table 3, the values ​​of the configuration object name field "detection flow detection characteristics" or "detection slice characteristics", and the values ​​of the configuration object key subfields "X1", "X2", "X3", "X4", "X5", etc. are abstract descriptions for distinguishing different business characteristic detections, and are not the actual values ​​of these fields. For another example, the values ​​"A1", "A2" of the message type field described in Table 4 and Table 5, 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 Table 5 are all abstract descriptions for distinguishing different service feature detections, and are not the actual values ​​of these fields. For example, for an XLDP message, the actual value of the message type field can be 0xFF, 0x03, etc., and "A1" and "A2" are used here for abstract representation.

[0208] The above is an introduction to the method embodiment of the present application. The following is an introduction to the device embodiment of the present application. The device of the present application can be used to execute the method of the present application. For details not disclosed in the device embodiment of the present application, please refer to the method embodiment.

[0209] Please refer to Fig.10 , which shows a schematic diagram of a network configuration device 1000 provided in an embodiment of the present 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 Figures 2 to 4 The network node 101 in, or Figure 4 The control node 100 in the network configuration device 1000 is used to perform Figure 5 The method provided in the embodiment shown. Fig.10 As shown, the network configuration device 1000 includes a determination module 1001 and a configuration module 1002 .

[0210] The determination module 1001 is used to determine whether the forwarding node on the transmission path of the data flow supports the service characteristics; the configuration module 1002 is used to perform service configuration on the port of the forwarding node based on the service characteristics. For the functional implementation of the determination module 1001, please refer to the relevant description in S501 above, and for the functional implementation of the configuration module 1002, please refer to the relevant description in S502 above.

[0211] Optionally, the configuration module 1002 is used to obtain configuration parameters of the port based on the service characteristics; and use the configuration parameters to perform service configuration on the port.

[0212] Optionally, the configuration module 1002 is used to send a configuration message to the forwarding node, where the configuration message includes the configuration parameters.

[0213] Optionally, the configuration message is a GRASP message, the GRASP message includes a configuration object key-value pair field, and the configuration object key-value pair field is used to carry the configuration parameters; or the configuration message is an XLDP message, the XLDP message includes a PDU, the PDU includes a TLV field, and the TLV field is used to carry the configuration parameters.

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

[0215] Optional, please continue to refer to Fig.10 , the network configuration device 1000 further includes:

[0216] The receiving module 1003 is used to receive the path information sent by the forwarding node, where the path information includes the identifier of the port;

[0217] The acquisition module 1004 is configured to acquire the port on the transmission path based on the path information.

[0218] Optionally, the port is a port in the forwarding node used to receive or send the data flow, and the path information also includes at least one of the following: indication information of the data flow; the flow direction of the data flow in the forwarding node, which flow direction is the direction from the port in the forwarding node used to receive the data flow to the port in the forwarding node used to send the data flow.

[0219] Optionally, the path information also includes indication information of the forwarding node. The acquisition module 1004 is further used to acquire the forwarding node on the transmission path based on the path information. The configuration module 1002 is further used to perform service configuration on the forwarding node based on the service characteristics.

[0220] Optionally, the determination module 1001 is further configured to determine the transmission path according to the path information sent by the forwarding node on the transmission path; please continue to refer to Fig.10 The network configuration device 1000 also includes: a presentation module 1005, used to present the transmission path.

[0221] Optionally, the determination module 1001 is configured to determine whether the forwarding node supports a service feature by sending a detection message.

[0222] Optionally, the detection message is an ICMP message, the ICMP message includes a type field and a code field, the type field and the code field are used to indicate whether the forwarding node supports the service feature; or the detection 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 to indicate whether the forwarding node supports the service feature; or the detection message is an XLDP message, the XLDP message includes a PDU, the PDU includes a TLV field, and the TLV field is used to indicate whether the forwarding node supports the service feature.

[0223] 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 also includes characteristic conversion information, which is used to indicate the type conversion of the service characteristic.

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

[0225] Optionally, the service feature is an end-to-end service feature.

[0226] Optionally, the service feature includes any one of a flow detection feature and a slicing feature.

[0227] Optionally, the flow detection feature includes an IFIT feature and an IPCA feature; the slicing feature includes a FlexE-based slicing feature, a channelized sub-interface-based slicing feature, and a FlexChannel-based slicing feature.

[0228] To summarize, in the network configuration scheme provided by the embodiment of the present application, after the network node determines that the forwarding node on the transmission path of the data flow supports the service characteristics, the port of the forwarding node is configured for service based on the service characteristics, so that during the process of the forwarding node forwarding the data flow, the service operation corresponding to the service characteristic is performed on the data flow at the port. Compared with the current manual configuration scheme, the embodiment of the present application can simplify the service configuration process and reduce the difficulty of service configuration.

[0229] The network configuration device provided in the embodiment of the present application can also be implemented using an application-specific integrated circuit (ASIC) or a programmable logic device (PLD). The above-mentioned PLD can be a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL) or any combination thereof. The method provided in the above-mentioned method embodiment can also be implemented by software. When the method provided in the above-mentioned method embodiment is implemented by software, each module in the above-mentioned network configuration device can also be a software module.

[0230] An embodiment of the present application provides a network configuration device, including a memory and a processor; the memory is used to store a computer program; the processor is used to execute the computer program stored in the memory so that the network configuration device performs all or part of the steps of the network configuration method provided in the above method embodiment.

[0231] As an example, see Fig.11 , which shows a schematic diagram of another network configuration device 1100 provided in an embodiment of the present application. The network configuration device 1100 is a network node or a functional component in a network node. For example, the network node is Figures 2 to 4 The network node 101 in Figure 4 The control node 100 in the network configuration device 1100 is used to perform Figure 5 The network configuration method embodiment is shown. Fig.11 As shown, the network configuration device 1100 includes a main control board 1110, an interface board 1130 and an interface board 1140. In the case of multiple interface boards, a switching network board ( Fig.11 The switching network board is used to complete data exchange between the interface boards (the interface board is also called a line card or a service board).

[0232] The main control board 1110 is used to perform system management, equipment maintenance, protocol processing and other functions. The interface board 1130 and the interface board 1140 are used to provide various business interfaces (for example, POS interface, GE interface, ATM interface, etc.) and realize message forwarding. There are mainly three types of functional units on the main control board 1110: system management control unit, system clock unit and system maintenance unit. The main control board 1110, the interface board 1130 and the interface board 1140 are connected to the system backplane through the system bus to achieve intercommunication. The interface board 1130 includes one or more processors 1131. The processor 1131 is used to control and manage the interface board 1130 and communicate with the central processing unit 1112 on the main control board 1110. The memory 1132 on the interface board 1130 is used to store the configuration parameters in the above-mentioned embodiments, etc. As Fig.11 As shown, 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, etc., which is not limited in this embodiment of the present application.

[0233] The interface board 1130 includes one or more network interfaces 1133 for receiving and sending messages, and the processor 1131 can process the messages received by the network interface 1133. The specific implementation process is not described one by one here. Among them, the network interface 1133 can be the port described in the above embodiment, also called a network port.

[0234] It is understandable that Fig.11 As shown, this embodiment includes multiple interface boards and adopts a distributed forwarding mechanism. Under this mechanism, the operation on the interface board 1140 is basically similar to the operation on the interface board 1130, and for the sake of brevity, it will not be repeated. In addition, it can be understood that Fig.11 The processor 1131 in the interface board 1130 and / or the processor 1141 in the interface board 1140 may be dedicated hardware or chips, such as a network processor or a dedicated integrated circuit to implement the above functions. This implementation is what is commonly referred to as a forwarding plane using dedicated hardware or chip processing. In another embodiment, the processor 1131 in the interface board 1130 and / or the processor 1141 in the interface board 1140 may also be a general-purpose processor, such as a general-purpose central processing unit (CPU) to implement the above-described functions.

[0235] It should be noted that there may be one or more main control boards, and when there are multiple boards, they may include a main main control board and a standby main control board. There may be one or more interface boards. The stronger the data processing capability of the network node, the more interface boards are provided. In the case of multiple interface boards, the multiple interface boards can communicate with each other through one or more switching network boards, and when there are multiple boards, they can jointly realize load sharing and redundant backup. In a centralized forwarding architecture, the network node may not need a switching network board, and the interface board is responsible for the processing function of the service data of the entire system. In a distributed forwarding architecture, the network node includes multiple interface boards, and data exchange between multiple interface boards can be realized through the switching network board, providing large-capacity data exchange and processing capabilities. Therefore, the data access and processing capabilities of the network nodes of the distributed architecture are greater than those of the nodes of the centralized architecture. Which architecture to adopt depends on the networking deployment scenario, and no limitation is made here.

[0236] In an optional embodiment, the memory 1132 may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, an optical disc storage (including a compressed optical disc, a laser disc, an optical disc, a digital versatile disc, a Blu-ray disc, etc.), a magnetic disk or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 1132 may exist independently and be connected to the processor 1131 via a communication bus. The memory 1132 may also be integrated with the processor 1131.

[0237] The memory 1132 is used to store program codes, and the processor 1131 controls the execution to execute some or all steps of the network configuration method provided in the above embodiment. The processor 1131 is used to execute the program codes stored in the memory 1132. The program codes may include one or more software modules. The one or more software modules may be the above Fig.10 The memory 1114 may also be used to store program codes, and the central processor 1112 controls the execution to execute part or all of the steps of the network configuration method provided in the above embodiment.

[0238] In an optional embodiment, the network interface 1133 can be a device such as a transceiver for communicating with other nodes or communication networks, such as Ethernet, radio access network (RAN), wireless local area networks (WLAN), etc.

[0239] As another example, see Fig.12 , which shows a schematic diagram of another network configuration device 1200 provided in an embodiment of the present application. The network configuration device 1200 may be a control node or a functional component in a control node. The network configuration device 1200 is used to perform the above Figure 5 The network configuration method embodiment shown in FIG. Fig.12 As shown, the network configuration device 1200 includes:

[0240] Processor 1201 and memory 1202 , memory 1201 and memory 1202 are connected via bus 1203 . Fig.12 The processor 1201 and the memory 1202 are described as being independent of each other. Optionally, the processor 1201 and the memory 1202 are integrated together.

[0241] The memory 1202 is used to store computer programs, including operating systems and program codes. The memory 1202 is a storage medium of various types, such as RAM, ROM, non-volatile random access memory (NVRAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM), flash memory, register, optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), disk or other magnetic storage device.

[0242] Among them, processor 1201 is a general processor or a special processor. A general processor is a processor that performs specific steps and / or operations by reading and executing a computer program stored in a memory (e.g., memory 1202). The general processor may use a computer program stored in a memory (e.g., memory 1202) in the process of performing the above steps and / or operations. The computer program is executed, for example, to implement the related functions of the aforementioned determination module 1001, configuration module 1002, and acquisition module 1004. A general processor is, for example, but not limited to, a CPU. A special processor is a processor specially designed to perform specific steps and / or operations, and a special processor is, for example, but not limited to, a digital signal processor (DSP), 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. Processor 1201 includes at least one circuit to perform all or part of the steps of the method provided in the above embodiment.

[0243] Optionally, the network configuration device 1200 further includes a network interface 1204, which is connected to the processor 1201 and the memory 1202 via the bus 1203. The network interface 1204 enables the network configuration device 700 to communicate with other devices. The network interface 1204 may be the port described in the above embodiment, also referred to as a network port.

[0244] Optionally, the network configuration device 1200 further includes an input / output (I / O) interface 1205, which is connected to the processor 1201 and the memory 1202 via the bus 1203. The processor 1201 can receive input commands or data, etc. via the I / O interface 1205. The I / O interface 1205 is used for the network configuration device 1200 to connect input devices, such as a keyboard, a mouse, etc.

[0245] Optionally, the network configuration device 1200 further includes a display 1206, which is connected to the processor 1201 and the memory 1202 via the bus 1203. The display 1206 can be used to display the intermediate results and / or final results generated by the processor 1201 executing the above-mentioned network configuration method. For example, the display 1206 is used to display the transmission path described in the above-mentioned embodiment. In a possible implementation, the display 1206 is a touch display screen to provide a human-computer interaction interface. The display 1206 can implement the related functions of the aforementioned presentation module 1005.

[0246] Optionally, in some possible scenarios, the network interface 1204 and the I / O interface 1205 are collectively referred to as a communication interface. In addition, the communication interface also includes a transceiver for information transmission and reception, which is not limited in the embodiments of the present application.

[0247] The bus 1203 is any type of communication bus for interconnecting the internal devices of the network configuration device 1200. For example, a system bus. The embodiment of the present application takes the interconnection of the above-mentioned devices in the network configuration device 1200 through the bus 1203 as an example. Optionally, the above-mentioned devices in the network configuration device 1200 are connected to each other in a communication manner other than the bus 1203, for example, the above-mentioned devices in the network configuration device 1200 are interconnected through a logical interface in the network configuration device 1200.

[0248] The above devices may be arranged on independent chips, or at least partially or completely on the same chip. Whether to arrange each device independently on different chips or to integrate them on one or more chips often depends on the needs of product design. The embodiments of the present application do not limit the specific implementation form of the above devices.

[0249] Fig.12 The network configuration device 1200 shown is merely exemplary. During implementation, the network configuration device 1200 includes other components, which are not listed one by one in this document. Fig.12 The network configuration device 1200 shown can perform service configuration on the forwarding nodes on the transmission path of the data flow by executing all or part of the steps of the network configuration method provided in the above embodiment.

[0250] The embodiment of the present application provides a network configuration system, which includes a network node and a forwarding node. The network node includes: Figures 10 to 12 In any of the network configuration devices shown, the network node is used to perform service configuration on the forwarding node. For example, the network configuration system is as follows Figures 2 to 4 Any of the communication networks shown.

[0251] An embodiment of the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed (for example, executed by a control node, a head node, a processor, etc.), all or part of the steps of the method provided in the above method embodiment are implemented.

[0252] An embodiment of the present application provides a computer program product, which includes a program or code. When the program or code is executed (for example, executed by a control node, a head node, a processor, etc.), it implements all or part of the steps of the method provided in the above method embodiment.

[0253] An embodiment of the present application provides a chip, which includes a programmable logic circuit and / or program instructions. When the chip is running, it is used to implement all or part of the steps of the method provided in the above method embodiment.

[0254] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product, and the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a computer network, or other programmable device. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium, or a semiconductor medium (e.g., a solid-state hard disk), etc.

[0255] The term "at least one" in this application refers to one or more, and "multiple" refers to two or more. The term "and / or" in this application is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, in order to facilitate clear description, in this application, the words "first", "second", "third" and the like are used to distinguish between identical or similar items with substantially the same functions and effects. Those skilled in the art will understand that the words "first", "second", "third" and the like do not limit the quantity and execution order.

[0256] The different types of embodiments such as the method embodiment and the device embodiment provided in the embodiment of the present application can refer to each other, and the embodiment of the present application does not limit this. The order of the operation of the method embodiment provided in the embodiment of the present application can be appropriately adjusted, and the operation can also be increased or decreased in response to the situation. Any technician familiar with the technical field can easily think of the method of change within the technical scope disclosed in the present application, which should be covered within the protection scope of the present application, so it will not be repeated. In the corresponding embodiments provided in the present application, it should be understood that the disclosed device, etc. can be implemented by other configuration methods. For example, the device embodiment described above is only schematic, for example, the division of the module is only a logical function division, and there may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. The module described as a separate component may or may not be physically separated, and the component described as a module may or may not be a physical module, which may be located in one place or distributed on multiple devices. Some or all of the modules can be selected according to actual needs to achieve the purpose of the scheme of this embodiment.

[0257] The above is only an exemplary embodiment of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A network configuration method, characterized in that: The method comprises: The network node determines that the forwarding node on the transmission path of the data flow supports the service characteristics; The network node performs service configuration on the port of the forwarding node based on the service characteristics.

2. The method according to claim 1, characterized in that The network node performing service configuration on the port of the forwarding node based on the service characteristics includes: The network node acquires configuration parameters of the port based on the service characteristics; The network node performs the service configuration on the port using the configuration parameters.

3. The method according to claim 2, characterized in that The network node adopting the configuration parameters to perform the service configuration on the port includes: the network node sending a configuration message to the forwarding node, the configuration message including the configuration parameters.

4. The method according to claim 3, characterized in that The configuration message is a General Autonomous Signaling Protocol GRASP message, the GRASP message includes a configuration object key-value pair field, and the configuration object key-value pair field is used to carry the configuration parameters; or The configuration message is a Minimal 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 parameters.

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

6. The method according to any one of claims 1 to 5, characterized in that: The method further comprises: The network node receives the path information sent by the forwarding node, where the path information includes an identifier of the port; The network node acquires the port on the transmission path based on the path information.

7. The method according to any one of claims 1 to 6, characterized in that: The network node determining that a forwarding node on a transmission path of the data flow supports a service characteristic includes: the network node determining that the forwarding node supports the service characteristic by sending a detection message.

8. The method according to claim 7, characterized in that The detection message is an Internet Control Message Protocol (ICMP) message, and the ICMP message includes a type field and a code field, and the type field and the code field are used to indicate whether the forwarding node supports the service feature; or The detection message is a General Autonomous Signaling Protocol GRASP message, the GRASP message includes a configuration object key-value pair field, and the configuration object key-value pair field is used to indicate whether the forwarding node supports the service feature; or The detection message is a Minimal 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 feature.

9. The method according to any one of claims 2 to 5, characterized in that: The type of 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 includes characteristic conversion information, and the characteristic conversion information is used to indicate the type conversion of the service characteristic.

10. The method according to any one of claims 1 to 9, characterized in that: The network node is a control node or a head node of the transmission path.

11. A network configuration device, characterized in that: Applied to a network node, the device comprises: A determination module, used to determine whether a forwarding node on a transmission path of a data stream supports a service characteristic; A configuration module is used to perform service configuration on the port of the forwarding node based on the service characteristics.

12. The device according to claim 11, characterized in that The configuration module is used to: obtain configuration parameters of the port based on the service characteristics; and perform the service configuration on the port using the configuration parameters.

13. The device according to claim 12, characterized in that The configuration module is used to send a configuration message to the forwarding node, where the configuration message includes the configuration parameters.

14. The device according to claim 13, characterized in that The configuration message is a General Autonomous Signaling Protocol GRASP message, the GRASP message includes a configuration object key-value pair field, and the configuration object key-value pair field is used to carry the configuration parameters; or The configuration message is a Minimal 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 parameters.

15. The device according to any one of claims 12 to 14, characterized in that The configuration parameter includes enabling indication information and an identifier of the port, and the enabling indication information is used to indicate enabling a service function corresponding to the service characteristic for the port.

16. The device according to any one of claims 11 to 15, characterized in that The device also includes: A receiving module, configured to receive path information sent by the forwarding node, wherein the path information includes an identifier of the port; An acquisition module is used to acquire the port on the transmission path based on the path information.

17. The device according to any one of claims 11 to 16, characterized in that The determining module is used to determine that the forwarding node supports the service characteristics by sending a detection message.

18. The device according to claim 17, characterized in that The detection message is an Internet Control Message Protocol (ICMP) message, and the ICMP message includes a type field and a code field, and the type field and the code field are used to indicate whether the forwarding node supports the service feature; or The detection message is a General Autonomous Signaling Protocol GRASP message, the GRASP message includes a configuration object key-value pair field, and the configuration object key-value pair field is used to indicate whether the forwarding node supports the service feature; or The detection message is a Minimal 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 feature.

19. The device according to any one of claims 12 to 15, characterized in that The type of service characteristics supported by the previous hop node or the next hop node of the forwarding node is different from the type of the service characteristics supported by the forwarding node, and the configuration parameters further include characteristic conversion information, and the characteristic conversion information is used to indicate the type conversion of the service characteristics.

20. The device according to any one of claims 11 to 19, characterized in that The network node is a control node or a head node of the transmission path.

Images