WO2025031363A1 - Information configuration method and apparatus, and communication device and readable storage medium - Google Patents

Abstract

The present disclosure belongs to the technical field of communications. Provided are an information configuration method and apparatus, and a communication device and a readable storage medium. The method comprises: a first device receiving first information sent by a second device, wherein the first information is used for configuring the type of a guide label or flow ID indicator for the first device. Thus, by means of configuring the types of guide labels or flow ID indicators, the disclosure can make the types of guide labels or flow ID indicators supported between end-to-end devices consistent, thereby implementing end-to-end intercommunication by means of in-situ flow information telemetry.

Description

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

CROSS-REFERENCE TO RELATED APPLICATIONS

The present disclosure is based on the Chinese patent application with application number 202310991642.1 and application date August 8, 2023, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into the present disclosure as a reference.

Technical Field

The present disclosure belongs to the field of communication technology, and specifically relates to an information configuration method, device, communication equipment and readable storage medium.

Background Art

In the related art, two methods are defined for the in-band operation, administration and maintenance (OAM) header of the flow detection: the first method is that the guide label (Flow ID indicator, FII) and the flow instruction header (Flow Instruction Header, FIH) are both multi-protocol label switching (Multi-Protocol Label Switching, MPLS) label headers, and the second method is that FII is the MPLS label header, and FIH and the flow instruction extension header (Flow Instruction Extension Header, FIEH) are part of the data message. The second method can realize more extended flow detection functions through extended messages. The two methods are distinguished by the S/R bit of the flow instruction header FIH. However, since the general chip only identifies the MPLS label header by identifying the bottom of the stack, when the FII is identified as the bottom of the stack, it is no longer possible to extract the key information of the in-band OAM from the data message. Therefore, the above two methods are not interoperable, which may cause the end-to-end incompatibility of the flow detection.

Summary of the invention

The purpose of the embodiments of the present disclosure is to provide an information configuration method and apparatus, a communication device, and a readable storage medium to solve the problem of end-to-end non-interoperability in flow detection in the related art.

In order to solve the above technical problems, the present disclosure is implemented as follows.

In a first aspect, the present disclosure provides an information configuration method, which is performed by a first device, and includes: the first device receives first information sent by a second device, wherein the first information is used to configure a type of a boot tag or a flow ID tag identifier for the first device.

In a second aspect, the present disclosure provides an information configuration method, which is performed by a second device, including: the second device sends first information to a first device, wherein the first information is used to configure a type of a boot tag or a flow ID tag identifier for the first device.

In a third aspect, the present disclosure provides an information configuration apparatus, applied to a first device, comprising: a receiving module, configured to receive first information sent by a second device, wherein the first information is used to configure a type of a boot tag or a flow ID tag identifier for the first device.

In a fourth aspect, the present disclosure provides an information configuration apparatus, applied to a second device, comprising: a sending module, configured to send first information to a first device, wherein the first information is used to configure a type of a boot tag or a flow ID tag identifier for the first device.

In a fifth aspect, the present disclosure provides a communication device, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method described in the first aspect or the method described in the second aspect.

In a sixth aspect, the present disclosure provides a readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the method described in the first aspect or the method described in the second aspect.

In a seventh aspect, the present disclosure provides a computer program product comprising instructions, which, when executed by a processor, implement the method according to the first aspect or the method according to the second aspect.

In an embodiment of the present disclosure, a first device may receive first information sent by a second device, wherein the first information is used to configure a type of a guide tag or a stream ID tag for the first device. Thus, by configuring the type of a guide tag or a stream ID tag, the present disclosure can make the types of guide tags or stream ID tags supported by end-to-end devices consistent, thereby achieving end-to-end interoperability of follow-up detection.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a schematic diagram of the Inband OAM message header in the embodiment of the present disclosure.

FIG. 2 is a flow chart of an information configuration method provided by an embodiment of the present disclosure.

FIG. 3 is a schematic diagram of the architecture of the management and control system in an embodiment of the present disclosure.

FIG. 4 is a flow chart of another information configuration method provided by an embodiment of the present disclosure.

FIG5 is a schematic diagram of the structure of an information configuration device provided in an embodiment of the present disclosure.

FIG. 6 is a schematic diagram of the structure of another information configuration device provided in an embodiment of the present disclosure.

FIG. 7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present disclosure.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are part of the embodiments of the present disclosure, rather than all of the embodiments. Based on the embodiments in the present disclosure, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present disclosure.

The terms "first", "second", etc. in the specification and claims of the present disclosure are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable when appropriate, so that the embodiments of the present disclosure can be implemented in an order other than those illustrated or described herein, and the objects distinguished by "first", "second", etc. are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and/or" in the specification and claims represents at least one of the connected objects, and the character "/" generally indicates that the objects associated with each other are in an "or" relationship.

In order to facilitate understanding of the embodiments of the present disclosure, the following contents are first described.

An important feature of carrier-grade transmission technology is OAM capability, which is used to provide alarms, performance testing, etc. to ensure that faults can be discovered in a timely manner. Follow-the-flow OAM directly tests service packets, such as connectivity, packet loss, and latency.

Optionally, flow-based performance detection (or in-situ flow information telemetry, IFIT) can divide the message into different blocks by coloring the message, and then perform packet loss statistics based on the block. It can also achieve delay measurement through coloring. In network deployment, the controller enables the flow-based performance detection function for the services that need to be detected, and collects performance information from different nodes. The centralized controller counts and calculates the corresponding packet loss rate and delay. Based on the principle of flow-based detection, the actual service flow is marked with features (such as coloring), and packet loss and delay measurements are performed based on the feature fields that have not yet been identified. It can provide end-to-end and hop-by-hop performance detection capabilities for secret private network (SPN) service flows, quickly perceive network performance-related faults, and perform accurate demarcation and troubleshooting.

Optionally, an inband OAM message header may be as shown in Figure 1.

1) Guide label (FII), also known as flow ID label identification:

The flow instruction header FIH is guided by a specific reserved label, and the FIH header content is after the guide label. The guide label is an MPLS reserved label (0-15), the default value is "0xC", and the label value should be configurable. To support maximum forward compatibility, the format complies with the RFC 3032 standard. The TC field, S field, and TTL field of the guide label FII are required to comply with the definition of MPLS labels.

2) Flow Instruction Header (FIH):

The flow instruction header carries basic information for in-band flow detection, including flow ID, color indication bit, type indication, etc.:

a) Flow ID: bit0-bit19, used to uniquely identify a service flow. The Flow ID needs to be unique throughout the detection domain. The SPN network element identifies the flow based on the Flow ID.

b)L Flag: Loss Flag, packet loss measurement coloring mark.

c)D Flag: Delay Flag, delay measurement color mark, for example: 1 means delay measurement is required, 0 means delay measurement is not required.

d)R: Reserved bit, reserved for future expansion.

e) S/R: If the boot tag is at the bottom of the stack, it is reserved R, which is set to 1 by default; if the boot tag is not at the bottom of the stack, it is marked S.

f) Type indication Type: indicates the extended data type and whether to carry an extended header:

0x00: reserved;

0x01: Indicates that FIH is basic detection information and does not carry an extension header;

0x02: indicates that FIH is optional hop-by-hop detection information and does not carry an extension header;

0x03-0xFF: Reserved for extended use.

The information configuration method and apparatus, communication equipment, and readable storage medium provided by the embodiments of the present disclosure are described in detail below with reference to the accompanying drawings through specific embodiments and their application scenarios.

Please refer to Figure 2, which is a flowchart of an information configuration method provided by an embodiment of the present disclosure, and the method is applied to a first device, and the first device is, for example, an end device (such as a head node), an edge device or a metropolitan area device in an SPN. As shown in Figure 2, the method includes the following step 21.

In step 21, 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 or stream ID tag identification for the first device.

Here, the second device is a control device or a control system. The guide label (FII) and the flow ID label identify the same content, indicating that the two can communicate with each other.

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

Optionally, the type of the flow ID label identifier is any one of the following: bottom of stack, non-bottom of stack.

Therefore, by configuring the type of guide tag or flow ID tag identification, the types of guide tags or flow ID tag identification supported by end-to-end devices can be made consistent, thereby achieving end-to-end interoperability of follow-up detection. In addition, when the end-to-end devices are from different manufacturers, follow-up detection can be interoperable between devices from different manufacturers, providing end-to-end service levels for services such as government and enterprise dedicated lines and vertical industry applications. Service-Level Agreement (SLA) capability. For tens of thousands of deployed metropolitan area devices, end-to-end interoperability of in-flight detection can be efficiently achieved without modification.

For example, as shown in Figure 3, the management and control system can send the first information to the terminal device and the metropolitan area device in the SPN respectively to configure the type of the guide label or the flow ID label identifier, so that the types of the guide label or the flow ID label identifier supported by the terminal device and the metropolitan area device are consistent, thereby achieving the effect of end-to-end interoperability of flow detection.

Optionally, the first information may include: a guide tag and a stack bottom identification configuration of the guide tag. The stack bottom identification configuration may also be referred to as a stack bottom bit (such as bottom of stack bit). For example, if the stack bottom identification configuration is 0, it may indicate that the corresponding guide tag is not at the stack bottom; if the stack bottom identification configuration is 1, it may indicate that the corresponding guide tag is at the stack bottom. For another example, if the stack bottom identification configuration is 1, it may indicate that the corresponding guide tag is not at the stack bottom; if the stack bottom identification configuration is 0, it may indicate that the corresponding guide tag is at the stack bottom.

Optionally, the first information may include: a flow ID tag identifier and a stack bottom bit (such as bottom of stack bit) of the flow ID tag identifier. For example, if the stack bottom bit is 0, it can represent that the corresponding flow ID tag identifier is not the stack bottom; if the stack bottom bit is 1, it can represent that the corresponding flow ID tag identifier is the stack bottom. For another example, if the stack bottom bit is 1, it can represent that the corresponding flow ID tag identifier is not the stack bottom; if the stack bottom bit is 0, it can represent that the corresponding flow ID tag identifier is the stack bottom.

It should be noted that in order to implement the configuration of the type of the boot tag or the flow ID tag identifier, the first device and the second device need to support the stack bottom identifier configuration of the boot tag or the flow ID tag identifier.

In some embodiments, the first information is the Inband OAM global configuration feature information, as shown in Table 1 below, wherein a new guide label mode (FII-mode) is added, which corresponds to the stack bottom identifier configuration of the guide label, and when the value of the stack bottom identifier configuration is 0, it indicates that the FII is an MPLS non-stack bottom label; when the value of the stack bottom identifier configuration is 1, it indicates that the FII is an MPLS stack bottom label; the default value of the stack bottom identifier configuration value is 0.

Table 1

In the embodiment of the present disclosure, 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) according to the received first information. After receiving the first information sent by the second device, the information configuration method may also include:

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

Here, the first message header is an Inband OAM message header. The first field is, for example, an 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.

In some embodiments, if the stack bottom flag of the guide label configured by the control device is configured as 0, indicating that the FII is an MPLS non-stack bottom label, the terminal device can generate an Inband OAM header according to the stack bottom flag configuration, and set the bit value of the S field of the FII therein to 1, and set the S/R bit in the flow instruction header FIH to the R flag. If the stack bottom flag of the guide label configured by the control device is configured as 1, indicating that the FII is an MPLS stack bottom label, the terminal device can generate an Inband OAM header according to the stack bottom flag configuration, and set the bit value of the S field of the FII therein to 0, and set the S/R bit in the flow instruction header FIH to the S flag, and the bit value is set to 1.

In the disclosed embodiment, 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) in combination with the flow coloring instance characteristic information. The information configuration method may also include: the first device receives the second information sent by the second device, the second information is used to configure the flow coloring instance characteristic information for the first device; the first device generates a second message header according to the first information and the second information; the type of the guide label or flow ID label identification in the second message header is determined based on the first information, and the flow detection characteristic information in the second message header is determined based on the flow coloring instance characteristic information.

Here, the second message header is an Inband OAM message header. The in-band detection feature information in the second message header includes, for example, FlowID, in-band detection enable status, flow coloring flip cycle, hop-by-hop detection status, etc.

Optionally, the flow coloring instance characteristic information includes but is not limited to at least one of the following: flow identification (flow ID), flow detection enable status, flow coloring flipping period, hop-by-hop detection status, source media access control (MAC) address, destination MAC address, virtual local area network (VLAN) identification ID, inner VLAN ID, service flow priority, source Internet Protocol (IP) address, destination IP address, port number, interface number, instance name, protocol number, etc.

In some embodiments, the content of the above-mentioned flow coloring instance feature information may be as shown in the following Table 2:

Table 2

Please refer to Figure 4, which is a flow chart of an information configuration method provided by an embodiment of the present disclosure, the method is applied to a second device, the second device being, for example, a control device or a control system in an SPN. As shown in Figure 4, the method includes the following step 41.

In step 41, the second device sends first information to the first device, where the first information is a type of a boot tag or a stream ID tag identifier configured for the first device.

Here, the first device is, for example, a terminal device (such as a head node) or a metropolitan area device in an SPN. If the guide label (FII) and the flow ID label identify the same content, it means that the two can communicate with each other.

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

Optionally, the type of the flow ID label identifier is any one of the following: bottom of stack, non-bottom of stack.

Therefore, the present disclosure can make the types of guide tags or flow ID tags supported by end-to-end devices consistent by configuring the types of guide tags or flow ID tags, thereby achieving end-to-end interoperability of flow detection.

For example, as shown in Figure 3, the management and control system can send the first information to the terminal device and the metropolitan area device in the SPN respectively to configure the type of the guide label or the flow ID label identifier, so that the types of the guide label or the flow ID label identifier supported by the terminal device and the metropolitan area device are consistent, thereby achieving the effect of end-to-end interoperability of flow detection.

Optionally, the first information may include: a guide tag and a stack bottom identification configuration of the guide tag. The stack bottom identification configuration may also be referred to as a stack bottom bit (such as bottom of stack bit). For example, if the stack bottom identification configuration is 0, it may indicate that the corresponding guide tag is not at the stack bottom; if the stack bottom identification configuration is 1, it may indicate that the corresponding guide tag is at the stack bottom. For another example, if the stack bottom identification configuration is 1, it may indicate that the corresponding guide tag is not at the stack bottom; if the stack bottom identification configuration is 0, it may indicate that the corresponding guide tag is at the stack bottom.

Optionally, the first information may include: a flow ID label identifier and a stack bottom bit (such as bottom of stack bit) of the flow ID label identifier. For example, if the stack bottom bit is 0, it may indicate that the corresponding flow ID label identifier is not the stack bottom; if the stack bottom bit is 1, it may indicate that the corresponding flow ID label identifier is the stack bottom. For another example, if the stack bottom bit is 1, it may indicate that the corresponding flow ID label identifier is not the stack bottom. Bottom of the stack. If the bottom bit is 0, the corresponding flow ID label is at the bottom of the stack.

In the disclosed embodiment, the second device can be configured according to the Inband OAM FII type supported by the metropolitan area device. Before sending the first information to the first device, the information configuration method also includes: the second device identifies the type of the guide tag or flow ID tag identification supported by the third device, where the type is, for example, the bottom of the stack or the non-bottom of the stack. For example, the second device can identify the type of the guide tag or flow ID tag identification supported by the third device according to the preset information; the second device generates the first information according to the type of the guide tag or flow ID tag identification supported by the third device, that is, determines the type of the guide tag or flow ID tag identification configured for the first device.

Here, the third device is, for example, a metropolitan area device, and the first device is a device connected to the metropolitan area device. The present disclosure uses the Inband OAM method supported by the metropolitan area device for configuration, so that the types of guide labels or flow ID label identifications supported by relevant terminal devices, metropolitan area devices, etc. can be consistent, thereby achieving end-to-end interoperability of flow detection.

Optionally, when the type of the boot tag or stream ID tag identification supported by the third device is the bottom of the stack, the first information indicates that the type of the boot tag or stream ID tag identification configured for the first device is the bottom of the stack.

Optionally, when the type of the boot tag or stream ID tag identification supported by the third device is non-bottom of the stack, the first information indicates that the type of the boot tag or stream ID tag identification configured for the first device is non-bottom of the stack.

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

In an example of the present disclosure, the FII type supported by device A is the bottom of the stack, the FII type supported by device B is the non-bottom of the stack, and the FII type supported by device C includes the bottom of the stack and the non-bottom of the stack, as shown in Table 3 below:

Table 3

Based on the above Table 3, for the device connected to device A, the types of the configured boot tags or flow ID tags are all bottom of the stack; for the device connected to device B, the types of the configured boot tags or flow ID tags are all non-bottom of the stack; for the device connected to device C, the types of the configured boot tags or flow ID tags are all bottom of the stack, or the types of the configured boot tags or flow ID tags are all non-bottom of the stack.

Optionally, the information configuration method may also include: the second device sends second information to the first device, and the second information is used to configure flow coloring instance characteristic information for the first device, so that the first device constructs a message header in combination with the flow coloring instance characteristic information.

Optionally, the flow coloring instance characteristic information includes but is not limited to at least one of the following: flow identification (flow ID), flow detection enable status, flow coloring flipping cycle, 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.

It should be noted that the information configuration method provided in the embodiment of the present disclosure may be executed by an information configuration device or a control module in the information configuration device for executing the information configuration method. In the embodiment of the present disclosure, the information configuration device provided in the embodiment of the present disclosure is described by taking the information configuration device executing the information configuration method as an example.

Please refer to Figure 5, which is a schematic diagram of the structure of an information configuration device provided in an embodiment of the present disclosure, and the device is applied to a first device, such as an end device (such as a head node), an edge device or a metropolitan area device in an SPN. In some embodiments of the present disclosure, the information configuration device may include or be integrated in the first device. As shown in Figure 5, the information configuration device 50 includes: a receiving module 51, which is used to receive first information sent by a second device, and the first information is used to configure the type of a boot label or a flow ID label identification for the first device.

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

Optionally, the type of the flow ID label identifier is any one of the following: bottom of stack, non-bottom of stack.

Optionally, the first information includes: a guide tag and a stack bottom identifier configuration of the guide tag.

Optionally, the first information includes: a flow ID label identifier and a stack bottom bit of the flow ID label identifier.

Optionally, the information configuration device 50 also includes: a first generation module, used for the first device to generate a first message header based on the first information; when the first information configures the boot label or flow ID label type of the first device as the bottom of the stack, the first field in the first message header is a first value; or, when the first information configures the boot label or flow ID label type of the first device as non-bottom of the stack, the first field in the first message header is a second value.

Optionally, the receiving module 51 is further used to: receive second information sent by a second device, the second information being used to configure flow coloring instance characteristic information for the first device. The first generating module is further used to: generate a second message header according to the first information and the second information, wherein the type of the guide label or flow ID label identification in the second message header is determined based on the first information, and the flow detection characteristic information in the second message header is determined based on the flow coloring instance characteristic information.

Optionally, the flow coloring instance feature information includes at least one of the following: flow identifier, flow detection enable status, flow coloring flip cycle, 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.

The information configuration device 50 of the embodiment of the present disclosure can implement each process of the method embodiment shown in FIG. 2 and can achieve the same technical effect. To avoid repetition, it will not be described again here.

Please refer to Figure 6, which is a schematic diagram of the structure of an information configuration device provided in an embodiment of the present disclosure, and the device is applied to a second device, such as a control device or a control system in an SPN. In some embodiments of the present disclosure, the information configuration device may include or be integrated in the second device. As shown in Figure 6, the information configuration device 60 includes: a sending module 61, which is used to send first information to a first device, and the first information is used to configure the type of a boot tag or a flow ID tag identifier for the first device.

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

Optionally, the type of the flow ID label identifier is any one of the following: bottom of stack, non-bottom of stack.

Optionally, the first information includes: a guide tag and a stack bottom identifier configuration of the guide tag.

Optionally, the first information includes: a flow ID label identifier and a stack bottom bit of the flow ID label identifier.

Optionally, the information configuration device 60 also includes: an identification module, used to identify the type of boot tag or flow ID tag identification supported by the third device; and a second generation module, used to generate the first information according to the type of boot tag or flow ID tag identification supported by the third device.

Optionally, when the type of the boot tag or stream ID tag identification supported by the third device is the bottom of the stack, the first information indicates that the type of the boot tag or stream ID tag identification configured for the first device is the bottom of the stack.

Optionally, when the type of the boot tag or stream ID tag identification supported by the third device is non-bottom of the stack, the first information indicates that the type of the boot tag or stream ID tag identification configured for the first device is non-bottom of the stack.

Optionally, when the types of boot tags or stream ID tag identifiers supported by the third device include bottom of stack and non-bottom of stack, the first information is that the type of boot tag or stream ID tag identifier configured for the first device is bottom of stack, or, the first information is that the type of boot tag or stream ID tag identifier configured for the first device is non-bottom of stack.

Optionally, the sending module 61 is further used to: send second information to the first device, where the second information is used to configure flow coloring instance feature information for the first device.

The information configuration device 60 of the embodiment of the present disclosure can implement each process of the method embodiment shown in FIG. 4 and can achieve the same technical effect. To avoid repetition, it will not be described again here.

Optionally, as shown in FIG7 , the embodiment of the present disclosure further provides a communication device 70, including a processor 71, a memory 72, and a program or instruction 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 instruction is executed by the processor 71 to implement the various processes of the information configuration method embodiment shown in FIG2 above, and the same technical effect can be achieved. When the communication device 70 is a second device, the program or instruction is executed by the processor 71 to implement the various processes of the information configuration method embodiment shown in FIG4 above, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The embodiment of the present disclosure also provides a readable storage medium on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information configuration method embodiment can be implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

The embodiments of the present disclosure also provide a computer program product on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned information configuration method embodiment can be implemented and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

Computer readable media include permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules 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 technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves. That is, computer readable media in this article refers to non-transitory computer readable media.

It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

The serial numbers of the above-mentioned embodiments of the present disclosure are only for description and do not represent the advantages or disadvantages of the embodiments.

Through the description of the above implementation methods, those skilled in the art can clearly understand that the above embodiment methods can be implemented by means of software plus a necessary general hardware platform, or by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present disclosure, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), and includes a number of instructions for enabling a computer The service classification device (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) executes the methods described in the various embodiments of the present disclosure.

The above is only a preferred embodiment of the present disclosure. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principle of the present disclosure. These improvements and modifications should also be regarded as the scope of protection of the present disclosure.

Claims (17)

An information configuration method, comprising: The first device receives first information sent by the second device, wherein the first information is used to configure a type of a boot tag or a flow ID tag identification for the first device. The method according to claim 1, wherein The type of the guide tag is any one of the following: bottom of stack, non-bottom of stack; or The type of the flow ID label identification is any one of the following: bottom of stack, non-bottom of stack. The method according to claim 1, wherein The first information includes: a guide tag and a stack bottom identifier configuration of the guide tag; or The first information includes: a flow ID label identifier and a stack bottom bit of the flow ID label identifier. The method according to any one of claims 1 to 3, wherein after receiving the first information sent by the second device, the method further comprises: The first device generates a first message header according to the first information; When the first information is a guide tag or a flow ID tag type identified by the first device configuration as a stack bottom, the first field in the first message header is a first value; or When the first information indicates that the type of the guide label or flow ID label configured for the first device is non-bottom of stack, the first field in the first message header is a second value. The method according to claim 1, further comprising: The first device receives second information sent by the second device, wherein the second information is used to configure flow coloring instance feature information for the first device; The first device generates a second packet header based on the first information and the second information, wherein the type of the guide label or flow ID label identification in the second packet header is determined based on the first information, and the flow detection feature information in the second packet header is determined based on the flow coloring instance feature information. The method according to claim 5, wherein the flow coloring instance feature information includes at least one of the following: Flow ID, flow detection enable status, flow coloring flip cycle, hop-by-hop detection status, source media access control MAC address, destination MAC address, virtual LAN ID VLAN ID, inner VLAN ID, service flow priority, source IP address, destination IP address, port number, interface number, instance name, and protocol number. An information configuration method, comprising: The second device sends first information to the first device, wherein the first information is a type of a boot tag or a stream ID tag identifier configured for the first device. The method according to claim 7, wherein The type of the guide tag is any one of the following: bottom of stack, non-bottom of stack; or The type of the flow ID label identification is any one of the following: bottom of stack, non-bottom of stack. The method according to claim 7, wherein The first information includes: a guide tag and a stack bottom identifier configuration of the guide tag; or The first information includes: a flow ID label identifier and a stack bottom bit of the flow ID label identifier. The method according to claim 7, characterized in that before sending the first information to the first device, the method further comprises: The second device identifies the type of boot tag or stream ID tag identification supported by the third device; and The second device generates the first information according to a type of a boot tag or a stream ID tag identification supported by the third device. The method according to claim 10, wherein When the type of the boot tag or stream ID tag identification supported by the third device is the bottom of the stack, the first information indicates that the type of the boot tag or stream ID tag identification configured for the first device is the bottom of the stack; or When the type of the boot tag or stream ID tag identification supported by the third device is non-bottom of the stack, the first information indicates that the type of the boot tag or stream ID tag identification configured for the first device is non-bottom of the stack; or When the types of boot labels or stream ID label identifiers supported by the third device include bottom of stack and non-bottom of stack, the type of boot label or stream ID label identifier configured for the first device by the first information is bottom of stack, or the type of boot label or stream ID label identifier configured for the first device by the first information is non-bottom of stack. The method according to claim 7, further comprising: The second device sends second information to the first device, wherein the second information is used to configure flow coloring instance feature information for the first device. An information configuration device, comprising: The receiving module is used to receive first information sent by the second device, wherein the first information is used to configure a type of a boot tag or a flow ID tag identification for the first device. An information configuration device, comprising: The sending module is used to send first information to the first device, wherein the first information is used to configure a type of a boot tag or a flow ID tag identifier for the first device. A communication device comprises a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the information configuration method as described in any one of claims 1 to 6, or implements the information configuration method as described in any one of claims 7 to 12. A readable storage medium storing a program or instruction, wherein the program or instruction, when executed by a processor, implements the information configuration method according to any one of claims 1 to 6, or implements the information configuration method according to any one of claims 7 to 12. A computer program product comprising instructions, wherein when the instructions are executed by a processor, the processor executes the information configuration method according to any one of claims 1 to 6, or implements the information configuration method according to any one of claims 7 to 12.