Information configuration method and apparatus, communication device, and readable storage medium

Abstract

The application discloses an information configuration method and device, a communication device and a readable storage medium, and belongs to the technical field of communication. The information configuration method in the embodiment of the application comprises the following steps: a first device receives first information sent by a second device, and the first information is used for configuring the type of a guide label or a flow ID label identification. Therefore, by means of the type of the guide label or the flow ID label identification, the types of the guide label or the flow ID label identification supported between end-to-end devices are consistent, and end-to-end intercommunication with flow detection is realized.

Description

Technical Field

[0001] This application belongs to the field of communication technology, specifically relating to an information configuration method, apparatus, communication equipment, and readable storage medium. Background Technology

[0002] In related technologies, two methods are defined for in-band Operation Administration and Maintenance (OAM) headers in flow-following detection: Method 1 uses both the Bootstrap Label (FII) and Flow Command Header (FIH) as Multi-Protocol Label Switching (MPLS) headers; Method 2 uses the MPLS header for the FII, with the FIH and FIEH being part of the data packet. Method 2 can implement more extended flow-following detection functions by extending the packet. These two methods are distinguished by the S / R bits of the Flow Command Header (FIH). However, since general-purpose chips only identify the MPLS header by recognizing the stack bottom, when the FII is identified as the stack bottom, the key in-band OAM information cannot be extracted from the data packet. Therefore, the two methods are not interoperable, which may cause end-to-end interoperability issues in flow-following detection. Summary of the Invention

[0003] The purpose of this application is to provide an information configuration method, apparatus, communication device, and readable storage medium to solve the problem of end-to-end non-interoperability in flow detection in related technologies.

[0004] To solve the above-mentioned technical problems, this application is implemented as follows:

[0005] Firstly, an information configuration method is provided, executed by a first device, comprising:

[0006] The first device receives first information sent by the second device, wherein the first information is used to configure the type of guide tag or flow ID tag identifier for the first device.

[0007] Secondly, an information configuration method is provided, executed by a second device, including:

[0008] The second device sends first information to the first device, wherein the first information is used to configure the first device with a type identified by a guide tag or a flow ID tag.

[0009] Thirdly, an information configuration device is provided, applied to a first device, comprising:

[0010] The receiving module is used to receive first information sent by the second device, wherein the first information is used to configure the type of the guide tag or stream ID tag identifier for the first device.

[0011] Fourthly, an information configuration device is provided, applied to a second device, comprising:

[0012] The sending module is used to send first information to the first device, wherein the first information is used to configure the type of the guide tag or flow ID tag identifier for the first device.

[0013] Fifthly, a communication device is provided, including a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein the program or instructions, when executed by the processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect.

[0014] In a sixth aspect, a readable storage medium is provided, on which a program or instructions are stored, which, when executed by a processor, implement the steps of the method described in the first aspect, or the steps of the method described in the second aspect.

[0015] In this embodiment, the first device can receive first information sent by the second device, the first information being used to configure the type of the bootstrap tag or flow ID tag identifier for the first device. Therefore, by configuring the type of the bootstrap tag or flow ID tag identifier, the types of bootstrap tags or flow ID tag identifiers supported by end-to-end devices can be made consistent, thereby achieving end-to-end interoperability for flow-following detection. Attached Figure Description

[0016] Figure 1 This is a schematic diagram of the Inband OAM message header in an embodiment of this application;

[0017] Figure 2 This is a flowchart of an information configuration method provided in an embodiment of this application;

[0018] Figure 3 This is a schematic diagram of the architecture of the control system in the embodiments of this application;

[0019] Figure 4 This is a flowchart of another information configuration method provided in an embodiment of this application;

[0020] Figure 5 This is a schematic diagram of the structure of an information configuration device provided in an embodiment of this application;

[0021] Figure 6 This is a schematic diagram of another information configuration device provided in an embodiment of this application;

[0022] Figure 7 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0023] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0024] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0025] To facilitate understanding of the embodiments of this application, the following will be described first.

[0026] A key feature of carrier-grade transmission technology is OAM capability, or Operation, Maintenance, and Management capability, which provides alarms, performance monitoring, and other functions to ensure timely fault detection. Stream-based OAM directly inspects service packets, such as performing connectivity, packet loss, and latency checks.

[0027] Optionally, flow-based performance testing (or flow-based detection) can divide packets into different blocks by coloring them, and then perform packet loss statistics based on the blocks. Coloring can also be used to measure latency. In network deployment, the controller enables flow-based performance testing for services requiring testing and collects performance information from different nodes. The central controller then calculates the corresponding packet loss rate and latency. Based on the principle of flow-based detection, actual service flows are characterized (e.g., colored), and packet loss and latency measurements are performed based on feature field recognition. This provides end-to-end and hop-by-hop performance testing capabilities for Secret Private Network (SPN) service flows, enabling rapid detection of network performance-related faults and precise delimitation and troubleshooting.

[0028] Optionally, an inband OAM header can be as follows: Figure 1 As shown.

[0029] 1) Flow ID tag (FII), also known as the flow ID tag identifier:

[0030] The Stream Instruction (FIH) header is guided by a specific reserved tag, followed by the FIH header content. The guide tag is an MPLS reserved tag (0-15), with a default value of "0xC," and configurable tag values ​​should be supported. For maximum forward compatibility, the format conforms to RFC 3032. The TC, S, and TTL fields of the guide tag FII must conform to the MPLS tag definition.

[0031] 2) Stream Instruction Header (FIH):

[0032] The flow instruction header carries basic information for in-band flow detection, including the flow ID, color indicator bit, type indicator, etc.

[0033] a) Flow ID: bit0-bit19, used to uniquely identify a service flow. The Flow ID needs to be unique across the entire network within the detection domain; SPN network elements identify flows based on the Flow ID.

[0034] b) L Flag: Loss Flag, a coloring marker for packet loss measurement.

[0035] c) D Flag: Delay Flag, a coloring mark for delay measurement. For example, 1 indicates that delay needs to be measured, and 0 indicates that delay does not need to be measured.

[0036] d)R: Reserved bit, intended for future expansion.

[0037] e) S / R: If the boot label is at the bottom of the stack, then R is reserved, and the default value is 1; if the boot label is not at the bottom of the stack, then S is selected.

[0038] f) Type indicator: Indicates the extended data type and whether an extended header is included.

[0039] 0x00: Reserved;

[0040] 0x01: Indicates that FIH is basic detection information and does not carry an extended header;

[0041] 0x02: Indicates that FIH is optional hop-by-hop detection information and does not carry an extended header;

[0042] 0x03-0xFF: Reserved for future expansion.

[0043] The information configuration method, apparatus, communication device, and readable storage medium provided in this application will be described in detail below with reference to the accompanying drawings and through specific embodiments and application scenarios.

[0044] Please see Figure 2 , Figure 2This is a flowchart illustrating an information configuration method provided in an embodiment of this application. The method is applied to a first device, such as an end device (e.g., a head node), edge device, or metropolitan area device in an SPN. Figure 2 As shown, the method includes the following steps:

[0045] Step 21: The first device receives first information sent by the second device, the first information being used to configure the type of guide tag or flow ID tag identifier for the first device.

[0046] Here, the second device is a control device or control system. The guidance tag (FII) and flow ID tag identify the same content and can communicate with each other.

[0047] Optionally, the type of the guide label is any of the following: stack bottom, non-stack bottom.

[0048] Optionally, the type identified by the stream ID tag is any of the following: stack bottom, non-stack bottom.

[0049] Therefore, by configuring the type of bootstrap label or flow ID label, the types of bootstrap labels or flow ID labels supported by end-to-end devices can be made consistent, thereby achieving end-to-end interoperability of flow detection. Furthermore, when the end-to-end devices are from different manufacturers, flow detection can be interoperable between devices from different manufacturers, providing end-to-end Service-Level Agreement (SLA) capabilities for government and enterprise leased lines, vertical industry applications, and other services. For the tens of thousands of metropolitan area network devices already deployed, efficient end-to-end interoperability of flow detection can be achieved without any modifications.

[0050] for example Figure 3 As shown, the control system can send the first information to the end devices and metropolitan area devices in the SPN respectively to configure the type of the guide tag or flow ID tag identifier, so that the types of guide tags or flow ID tags supported by the end devices and metropolitan area devices are consistent, achieving the effect of end-to-end interoperability of flow detection.

[0051] Optionally, the first information may include: a boot tag and a stack bottom identifier configuration for the boot tag. The stack bottom identifier configuration may also be referred to as a stack bottom bit (e.g., bottom of stack bit). For example, if the stack bottom identifier is configured as 0, it indicates that the corresponding boot tag is not at the bottom of the stack; or, if the stack bottom identifier is configured as 1, it indicates that the corresponding boot tag is at the bottom of the stack. Again, for example, if the stack bottom identifier is configured as 1, it indicates that the corresponding boot tag is not at the bottom of the stack; or, if the stack bottom identifier is configured as 0, it indicates that the corresponding boot tag is at the bottom of the stack.

[0052] Optionally, the first information may include: a stream ID tag identifier and the bottom of the stack bit of the stream ID tag identifier. For example, if the bottom of the stack bit is 0, it can indicate that the corresponding stream ID tag identifier is not at the bottom of the stack; or, if the bottom of the stack bit is 1, it can indicate that the corresponding stream ID tag identifier is at the bottom of the stack. Again, for example, if the bottom of the stack bit is 1, it can indicate that the corresponding stream ID tag identifier is not at the bottom of the stack; or, if the bottom of the stack bit is 0, it can indicate that the corresponding stream ID tag identifier is at the bottom of the stack.

[0053] It should be noted that in order to configure the type of the boot tag or stream ID tag identifier, the first device and the second device must support the configuration of the stack bottom identifier of the boot tag or stream ID tag identifier.

[0054] In some embodiments, the first information is Inband OAM global configuration feature information, as shown in Table 1 below. The newly added bootstrap label mode (FII-mode) corresponds to the bootstrap label stack bottom identifier configuration. When the configuration value is 0, it means that the FII is an MPLS non-stack bottom label; when the configuration value is 1, it means that the FII is an MPLS stack bottom label; the default value of the configuration value is 0.

[0055] Table 1

[0056]

[0057] In this embodiment of the application, when the first device is an end device (such as a head node), the first device can construct a message header (such as an Inband OAM message header) based on the received first information. After receiving the first information sent by the second device, the information configuration method may further include:

[0058] The first device generates a first header based on the first information; wherein, when the first information is a boot tag or flow ID tag configured by the first device of type stack bottom, the first field in the first header is a first value; or, when the first information is a boot tag or flow ID tag configured by the first device of type non-stack bottom, the first field in the first header is a second value.

[0059] Here, the first header is an Inband OAM header. The first field is, for example, the S field of FII. For example, the first value is equal to 0, and the second value is equal to 1; or, the first value is equal to 1, and the second value is equal to 0.

[0060] In some embodiments, if the bottom stack identifier of the boot tag configured by the control device is configured to be 0, indicating that the FII is an MPLS non-bottom stack tag, the end device can generate an Inband OAM header according to the bottom stack identifier, and set the bit value of the S field of the FII to 1, and set the S / R bit in the Flow Command Header FIH to the R identifier; or, if the bottom stack identifier of the boot tag configured by the control device is configured to be 1, indicating that the FII is an MPLS bottom stack tag, the end device can generate an Inband OAM header according to the bottom stack identifier, and set the bit value of the S field of the FII to 0, and set the S / R bit in the Flow Command Header FIH to the S identifier, and set the bit value to 1.

[0061] In this embodiment of the application, when the first device is an end device (such as a head node), the first device can construct a packet header (such as an Inband OAM packet header) by combining the stream coloring instance feature information. The information configuration method may further include:

[0062] The first device receives second information sent by the second device, the second information being used to configure stream staining instance feature information for the first device;

[0063] The first device generates a second header based on the first information and the second information; the type of the guide tag or flow ID tag in the second header is determined based on the first information, and the flow detection feature information in the second header is determined based on the flow staining instance feature information.

[0064] Here, the second header is an Inband OAM header. The flow detection feature information in the second header includes, for example, Flow ID, flow detection enable status, flow staining reversal period, and hop-by-hop detection status.

[0065] Optionally, the flow staining instance feature information includes, but is not limited to, at least one of the following:

[0066] Flow identifier (flow ID), flow detection enabled status, flow coloring inversion period, hop-by-hop detection status, source Medium Access Control (MAC) address, destination MAC address, Virtual Local Area Network (VLAN) identifier ID, inner VLAN ID, service flow priority, source Internet Protocol (IP) address, destination IP address, port number, interface number, instance name, protocol number, etc.

[0067] In some embodiments, the features of the above-mentioned flow staining instance may include the content shown in Table 2 below:

[0068] Table 2

[0069]

[0070]

[0071] Please see Figure 4 , Figure 4 This is a flowchart of an information configuration method provided in an embodiment of this application. The method is applied to a second device, such as a control device or control system in an SPN.

[0072] like Figure 4 As shown, the method includes the following steps:

[0073] Step 41: The second device sends first information to the first device, the first information being used to configure the first device with a type identified by a boot tag or a flow ID tag.

[0074] Here, the first device is, for example, an end device (such as a head node) or a metropolitan area network device in an SPN. The guiding tag (FII) and the flow ID tag identify the same content and can communicate with each other.

[0075] Optionally, the type of the guide label is any of the following: stack bottom, non-stack bottom.

[0076] Optionally, the type identified by the stream ID tag is any of the following: stack bottom, non-stack bottom.

[0077] Therefore, by configuring the type of boot tag or flow ID tag identifier, the types of boot tags or flow ID tags supported by end-to-end devices can be made consistent, thereby enabling end-to-end interoperability of flow detection.

[0078] for example Figure 3 As shown, the control system can send the first information to the end devices and metropolitan area devices in the SPN respectively to configure the type of the guide tag or flow ID tag identifier, so that the types of guide tags or flow ID tags supported by the end devices and metropolitan area devices are consistent, achieving the effect of end-to-end interoperability of flow detection.

[0079] Optionally, the first information may include: a boot tag and a stack bottom identifier configuration for the boot tag. The stack bottom identifier configuration may also be referred to as a stack bottom bit (e.g., bottom of stack bit). For example, if the stack bottom identifier is configured as 0, it indicates that the corresponding boot tag is not at the bottom of the stack; or, if the stack bottom identifier is configured as 1, it indicates that the corresponding boot tag is at the bottom of the stack. Again, for example, if the stack bottom identifier is configured as 1, it indicates that the corresponding boot tag is not at the bottom of the stack; or, if the stack bottom identifier is configured as 0, it indicates that the corresponding boot tag is at the bottom of the stack.

[0080] Optionally, the first information may include: a stream ID tag identifier and the bottom of the stack bit of the stream ID tag identifier. For example, if the bottom of the stack bit is 0, it can indicate that the corresponding stream ID tag identifier is not at the bottom of the stack; or, if the bottom of the stack bit is 1, it can indicate that the corresponding stream ID tag identifier is at the bottom of the stack. Again, for example, if the bottom of the stack bit is 1, it can indicate that the corresponding stream ID tag identifier is not at the bottom of the stack; or, if the bottom of the stack bit is 0, it can indicate that the corresponding stream ID tag identifier is at the bottom of the stack.

[0081] In this embodiment, the second device can be configured according to the Inband OAM FII type supported by the metropolitan area network device. Before sending the first information to the first device, the information configuration method further includes:

[0082] The second device identifies the type of boot tag or stream ID tag identifier supported by the third device; such type is, for example, stack bottom or non-stack bottom; for example, the second device can identify the type of boot tag or stream ID tag identifier supported by the third device based on preset information.

[0083] The second device generates first information based on the type of boot tag or stream ID tag identifier supported by the third device, that is, determines the type of boot tag or stream ID tag identifier configured for the first device.

[0084] Here, the third device is, for example, a metropolitan area network (MAN) device, and the first device is a device connected to the MAN device. By configuring using the Inband OAM method supported by the MAN device, the types of guide tags or flow ID tags supported by the relevant end devices and MAN devices can be made consistent, thereby achieving end-to-end interoperability of flow detection.

[0085] Optionally, when the type of the boot tag or stream ID tag identifier supported by the third device is stack bottom, the first information is that the type of the boot tag or stream ID tag identifier configured by the first device is stack bottom.

[0086] Optionally, when the type of the boot tag or stream ID tag identifier supported by the third device is not stack bottom, the first information is that the type of the boot tag or stream ID tag identifier configured by the first device is not stack bottom.

[0087] Optionally, when the type of boot tag or stream ID tag identifier supported by the third device includes stack bottom and non-stack bottom, that is, both types are supported, one type can be selected for configuration. For example, the type of boot tag or stream ID tag identifier configured by the first information for the first device is stack bottom, or the type of boot tag or stream ID tag identifier configured by the first information for the first device is non-stack bottom.

[0088] For example, device A supports the stack bottom type of FII, device B supports the non-stack bottom type of FII, and device C supports both stack bottom and non-stack bottom types of FII, as shown in Table 3 below:

[0089] Table 3

[0090]

[0091]

[0092] Based on Table 3 above, for devices connected to device A, the configured boot tag or flow ID tag is of type stack bottom; for devices connected to device B, the configured boot tag or flow ID tag is of type non-stack bottom; for devices connected to device C, the configured boot tag or flow ID tag is of type stack bottom, or the configured boot tag or flow ID tag is of type non-stack bottom.

[0093] Optionally, the information configuration method may further include:

[0094] The second device sends second information to the first device. The second information is used to configure the first device with stream staining instance feature information, and the first device combines the stream staining instance feature information to construct the message header.

[0095] Optionally, the flow staining instance feature information includes, but is not limited to, at least one of the following:

[0096] Flow identifier (flow ID), flow detection enabled status, flow coloring flip period, hop-by-hop detection status, source MAC address, destination MAC address, VLAN ID, inner VLAN ID, service flow priority, source IP address, destination IP address, port number, interface number, instance name, protocol number, etc.

[0097] It should be noted that the information configuration method provided in this application embodiment can be executed by an information configuration device or a control module within that information configuration device for executing the information configuration method. This application embodiment uses the execution of the information configuration method by an information configuration device as an example to illustrate the information configuration device provided in this application embodiment.

[0098] Please see Figure 5 , Figure 5 This is a schematic diagram of an information configuration device provided in an embodiment of this application. The device is applied to a first device, such as an end device (e.g., a head node), edge device, or metropolitan area device in an SPN. Figure 5 As shown, the information configuration device 50 includes:

[0099] The receiving module 51 is used to receive first information sent by the second device, the first information being used to configure the type of the guide tag or flow ID tag identifier for the first device.

[0100] Optionally, the type of the guide label is any of the following: stack bottom, non-stack bottom.

[0101] Optionally, the type identified by the stream ID tag is any of the following: stack bottom, non-stack bottom.

[0102] Optionally, the first information includes: the boot tag and the stack bottom identifier configuration of the boot tag.

[0103] Optionally, the first information includes: the stream ID tag identifier and the stack bottom bits of the stream ID tag identifier.

[0104] Optionally, the information configuration device 50 also includes:

[0105] The first generation module is configured to generate a first header based on the first information; when the first information is a boot tag or flow ID tag configured by the first device of type stack bottom, the first field in the first header is a first value; or, when the first information is a boot tag or flow ID tag configured by the first device of type non-stack bottom, the first field in the first header is a second value.

[0106] Optionally, the receiving module 51 is further configured to: receive second information sent by the second device, the second information being used to configure stream staining instance feature information for the first device;

[0107] The first generation module is further configured to: generate a second header based on the first information and the second information; the type of the guide tag or flow ID tag in the second header is determined based on the first information, and the flow detection feature information in the second header is determined based on the flow staining instance feature information.

[0108] Optionally, the flow staining instance feature information includes at least one of the following:

[0109] Flow identifier, flow detection enabled status, flow coloring flip period, hop-by-hop detection status, source MAC address, destination MAC address, VLAN ID, inner VLAN ID, service flow priority, source IP address, destination IP address, port number, interface number, instance name, and protocol number.

[0110] The information configuration device 50 of this application embodiment can achieve the above. Figure 2 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0111] Please see Figure 6 , Figure 6 This is a schematic diagram of an information configuration device provided in an embodiment of this application. This device is applied to a second device, such as a control device or control system in an SPN. Figure 6 As shown, the information configuration device 60 includes:

[0112] The sending module 61 is used to send first information to the first device, the first information being used to configure the type of the guide tag or flow ID tag identifier for the first device.

[0113] Optionally, the type of the guide label is any of the following: stack bottom, non-stack bottom.

[0114] Optionally, the type identified by the stream ID tag is any of the following: stack bottom, non-stack bottom.

[0115] Optionally, the first information includes: the boot tag and the stack bottom identifier configuration of the boot tag.

[0116] Optionally, the first information includes: the stream ID tag identifier and the stack bottom bits of the stream ID tag identifier.

[0117] Optionally, the information configuration device 60 also includes:

[0118] The identification module is used to identify the type of guide tag or stream ID tag identifier supported by the third device;

[0119] The second generation module is used to generate the first information based on the type of guide tag or stream ID tag identifier supported by the third device.

[0120] Optionally, when the type of the boot tag or stream ID tag identifier supported by the third device is stack bottom, the first information is that the type of the boot tag or stream ID tag identifier configured by the first device is stack bottom.

[0121] Optionally, when the type of the boot tag or stream ID tag identifier supported by the third device is not stack bottom, the first information is that the type of the boot tag or stream ID tag identifier configured by the first device is not stack bottom.

[0122] Optionally, when the type of boot tag or stream ID tag identifier supported by the third device includes stack bottom and non-stack bottom, the first information is that the type of boot tag or stream ID tag identifier configured by the first device is stack bottom, or the first information is that the type of boot tag or stream ID tag identifier configured by the first device is non-stack bottom.

[0123] Optionally, the sending module 61 is further configured to: send second information to the first device, the second information being used to configure stream staining instance feature information for the first device.

[0124] The information configuration device 60 of this application embodiment can achieve the above. Figure 4 The various processes of the method embodiments shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0125] Optional, such as Figure 7 As shown, this application embodiment also provides a communication device 70, including a processor 71, a memory 72, and a program or instructions stored in the memory 72 and executable on the processor 71. For example, when the communication device 70 is a first device, the program or instructions executed by the processor 71 implement the above-mentioned... Figure 2 The various processes of the information configuration method embodiment shown can achieve the same technical effect. When the communication device 70 is a second device, the above-described process is implemented when the program or instruction is executed by the processor 71. Figure 4 The various processes of the information configuration method embodiment shown can achieve the same technical effect, and will not be described again here to avoid repetition.

[0126] This application also provides a readable storage medium storing a program or instructions. When the program or instructions are executed by a processor, they can implement the various processes of the above-described information configuration method embodiments and achieve the same technical effects. To avoid repetition, they will not be described again here.

[0127] Computer-readable media include both permanent and non-permanent, removable and non-removable media, which can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0128] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

[0129] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0130] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a service classification device (which may be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0131] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. An information configuration method, characterized in that, include: The first device receives first information sent by the second device, wherein the first information is used to configure the type of the boot tag for the first device; the type of the boot tag is any one of the following: stack bottom, non-stack bottom; The first information includes: a guide tag and a stack bottom identifier configuration of the guide tag, wherein the stack bottom identifier configuration is used to characterize the type of the guide tag; the first information is generated based on the type of guide tag supported by the identified third device; the guide tag is the FII field in the flow detection scenario.

2. The method according to claim 1, characterized in that, After receiving the first information sent by the second device, the method further includes: The first device generates a first message header based on the first information; Wherein, when the type of the boot tag configured by the first information is stack bottom, the first field in the first message header is the first value; Alternatively, when the type of the boot tag configured for the first device is non-stack bottom, the first field in the first header is the second value.

3. The method according to claim 1, characterized in that, The method further includes: The first device receives second information sent by the second device, wherein the second information is used to configure stream staining instance feature information for the first device; The first device generates a second header based on the first information and the second information; wherein the type of the guide tag in the second header is determined based on the first information, and the flow detection feature information in the second header is determined based on the flow staining instance feature information.

4. The method according to claim 3, characterized in that, The flow staining instance feature information includes at least one of the following: Flow identifier, flow detection enabled status, flow coloring flip period, hop-by-hop detection status, source media access control MAC address, destination MAC address, virtual LAN identifier VLAN ID, inner VLAN ID, service flow priority, source IP address, destination IP address, port number, interface number, instance name, and protocol number.

5. An information configuration method, characterized in that, include: The second device sends first information to the first device, wherein the first information is used to configure the type of the boot tag for the first device; the type of the boot tag is any one of the following: stack bottom, non-stack bottom; The first information includes: a guide tag and a stack bottom identifier configuration for the guide tag, wherein the stack bottom identifier configuration is used to characterize the type of the guide tag; the guide tag is a FII field in the context of flow detection. Before sending the first information to the first device, the method further includes: The second device identifies the type of boot tag supported by the third device; The second device generates the first information based on the type of guide tag supported by the third device.

6. The method according to claim 5, characterized in that, When the type of boot tag supported by the third device is stack bottom, the first information is that the type of boot tag configured by the first device is stack bottom; or, When the type of boot tag supported by the third device is non-stack bottom, the first information is that the type of boot tag configured by the first device is non-stack bottom; or, When the type of boot tag supported by the third device includes stack bottom and non-stack bottom, the first information indicates that the type of boot tag configured by the first device is stack bottom, or the first information indicates that the type of boot tag configured by the first device is non-stack bottom.

7. The method according to claim 5, characterized in that, The method further includes: The second device sends second information to the first device, wherein the second information is used to configure stream staining instance feature information for the first device.

8. An information configuration device, characterized in that, include: The receiving module is configured to receive first information sent by the second device, wherein the first information is used to configure the type of the boot tag for the first device; the type of the boot tag is any one of the following: stack bottom, non-stack bottom; The first information includes: a guide tag and a stack bottom identifier configuration of the guide tag, wherein the stack bottom identifier configuration is used to characterize the type of the guide tag; the first information is generated based on the type of guide tag supported by the identified third device; the guide tag is the FII field in the flow detection scenario.

9. An information configuration device, characterized in that, include: A sending module is configured to send first information to a first device, wherein the first information is used to configure the type of a boot tag for the first device; the type of the boot tag is any one of the following: stack bottom, non-stack bottom; The first information includes: a guide tag and a stack bottom identifier configuration for the guide tag, wherein the stack bottom identifier configuration is used to characterize the type of the guide tag; the guide tag is a FII field in the context of flow detection. The information configuration device further includes: The identification module is used to identify the types of guide tags supported by the third device; The second generation module is used to generate the first information based on the type of guide tag supported by the third device.

10. A communication device, characterized in that, It includes a processor, a memory, and a program or instructions stored in the memory and executable on the processor, wherein when the program or instructions are executed by the processor, they implement the steps of the information configuration method as described in any one of claims 1 to 4, or implement the steps of the information configuration method as described in any one of claims 5 to 7.

11. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a processor, implement the steps of the information configuration method as described in any one of claims 1 to 4, or implement the steps of the information configuration method as described in any one of claims 5 to 7.

Images