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

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

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure is based on and claims the priority of Chinese patent application with application number 202310991642.1 and application date August 8, 2023. The entire content of the Chinese patent application is hereby incorporated into this disclosure as a reference. Technical Field

[0003] The present disclosure belongs to the field of communication technology, and particularly relates to an information configuration method, apparatus, communication equipment, and readable storage medium. Background Art

[0004] In the related art, two methods are defined for the in-band Operation Administration and Maintenance (OAM) header of flow detection: Method 1 is that the guide label (Flow ID indicator, FII) and the flow instruction header (Flow Instruction Header, FIH) are both Multi-Protocol Label Switching (MPLS) label headers; Method 2 is that the FII is the MPLS label header, and the FIH and the flow instruction extension header (Flow Instruction Extension Header, FIEH) are part of the data message. Method 2 can achieve more extended flow detection functions through extended messages. These two methods are distinguished by the S / R bit of the flow instruction header FIH. However, since general chips only identify 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 in-band OAM from the data message. Therefore, the above two methods are not interoperable, which may cause end-to-end incompatibility of flow detection.

[0005] Summary of the Invention

[0006] 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 interoperability in flow detection in related technologies.

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

[0008] In a first aspect, the present disclosure provides an information configuration method, which is performed by a first device, including: 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.

[0009] 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.

[0010] In a third aspect, the present disclosure provides an information configuration device, 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.

[0011] In a fourth aspect, the present disclosure provides an information configuration device, 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.

[0012] In a fifth aspect, the present disclosure provides a communication device comprising a processor, a memory, and a program or instruction stored on 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.

[0013] In a sixth aspect, the present disclosure provides a readable storage medium storing a program or instruction. When the program or instruction is executed by a processor, the method according to the first aspect or the method according to the second aspect is implemented.

[0014] 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.

[0015] In an embodiment of the present disclosure, a first device may receive first information sent by a second device, where the first information is used to configure a type of a guide tag or a flow ID tag for the first device. Thus, by configuring the type of a guide tag or a flow ID tag, the present disclosure can ensure that the types of guide tags or flow ID tags supported by end-to-end devices are consistent, thereby achieving end-to-end interoperability of follow-up detection. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a schematic diagram of an Inband OAM message header according to an embodiment of the present disclosure.

[0017] FIG2 is a flowchart of an information configuration method provided by an embodiment of the present disclosure.

[0018] FIG3 is a schematic diagram of the architecture of the management and control system in an embodiment of the present disclosure.

[0019] FIG4 is a flowchart of another information configuration method provided by an embodiment of the present disclosure.

[0020] FIG5 is a schematic structural diagram of an information configuration device provided by an embodiment of the present disclosure.

[0021] FIG6 is a schematic structural diagram of another information configuration device provided by an embodiment of the present disclosure.

[0022] FIG7 is a schematic structural diagram of a communication device provided by an embodiment of the present disclosure. DETAILED DESCRIPTION

[0023] The following will clearly and completely describe the technical solutions in the embodiments of the present disclosure in conjunction with the accompanying drawings. Obviously, the described embodiments are only part of the embodiments of the present disclosure, not all of them. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present disclosure without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0024] 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 under appropriate circumstances, 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 related to each other are in an "or" relationship.

[0025] To facilitate understanding of the embodiments of the present disclosure, the following contents are first described.

[0026] A key feature of carrier-grade transmission technology is OAM (Operation, Maintenance, and Management) capabilities, which provide alarms, performance monitoring, and other functions to ensure timely fault detection. In-stream OAM directly monitors service packets, such as connectivity, packet loss, and latency.

[0027] Optionally, in-situ Flow Information Telemetry (IFIT) can color the packets to divide them into different blocks, and then perform packet loss statistics based on the blocks. It can also achieve delay measurement through coloring. In network deployment, the controller enables the in-situ performance detection function for the services that need to be detected, and collects performance information from different nodes. The centralized controller then counts and calculates the corresponding packet loss rate and delay. Based on the principle of in-situ 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 accurately demarcate and troubleshoot.

[0028] Optionally, an inband OAM message header may be as shown in FIG1 .

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

[0030] The Flow Instruction Header (FIH) is preceded by a specific reserved label, followed by the FIH header content. The leading label is an MPLS reserved label (0-15), with a default value of "0xC" and configurable label values. To ensure maximum forward compatibility, the format complies with RFC 3032. The TC field, S field, and TTL field of the leading label (FII) must conform to the MPLS label definition.

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

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

[0033] a) Flow ID: bit 0-bit 19, used to uniquely identify a service flow. The Flow ID needs to be unique across the entire network within the detection domain. The SPN network element identifies the flow based on the Flow ID.

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

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

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

[0037] e) S / R: If the boot tag is at the bottom of the stack, it is reserved R and is set to 1 by default; if the boot tag is not at the bottom of the stack, it is S flag.

[0038] f) Type indication: Indicates the extended data type and whether to carry an extended header:

[0039] 0x00: reserved;

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

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

[0042] 0x03-0xFF: Reserved for extended use.

[0043] The information configuration method and apparatus, communication device, 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.

[0044] Please refer to Figure 2, which is a flowchart of an information configuration method provided in an embodiment of the present disclosure. The method 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. As shown in Figure 2, the method includes the following step 21.

[0045] In step 21 , the first device receives first information sent by the second device, where the first information is used to configure a type of a boot tag or a flow ID tag identifier for the first device.

[0046] Here, the second device is a control device or a control system. If the induction label (FII) and the flow ID label identify the same content, it means that the two can communicate with each other.

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

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

[0049] Therefore, by configuring the type of guide tag or flow ID tag identifier, the types of guide tags or flow ID tag identifiers supported by end-to-end devices can be made consistent, thereby achieving end-to-end interoperability of in-flow detection. In addition, when the end-to-end devices are from different manufacturers, in-flow detection can be interoperable between devices from different manufacturers, providing end-to-end service-level agreement (SLA) capabilities for services such as government and enterprise dedicated lines and vertical industry applications. For tens of thousands of deployed metropolitan area devices, efficient end-to-end interoperability of in-flow detection can be achieved without modification.

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

[0051] Optionally, the first information may include: a guide tag and a stack bottom identifier configuration of the guide 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 to 0, it may indicate that the corresponding guide tag is not at the stack bottom; if the stack bottom identifier is configured to 1, it may indicate that the corresponding guide tag is at the stack bottom. For another example, if the stack bottom identifier is configured to 1, it may indicate that the corresponding guide tag is not at the stack bottom; if the stack bottom identifier is configured to 0, it may indicate that the corresponding guide tag is at the stack bottom.

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

[0053] 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.

[0054] In some embodiments, the first information is 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 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.

[0055] Table 1

[0056] 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) based on the received first information. After receiving the first information sent by the second device, the information configuration method can also include:

[0057] The first device generates a first message header based on the first information; wherein, when the first information is a guide tag or a flow ID tag configured for the first device that identifies the type of the stack bottom, the first field in the first message header is a first value; or, when the first information is a guide tag or a flow ID tag configured for the first device that identifies the type of the stack non-bottom, the first field in the first message header is a second value.

[0058] Here, the first packet header is an Inband OAM packet header. The first field is, for example, an S field of the 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.

[0059] 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-bottom-stack label, the terminal device can generate an Inband OAM message 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 bottom-stack label, the terminal device can generate an Inband OAM message 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.

[0060] In an 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) in combination with flow coloring instance characteristic information. The information configuration method may also include: the first device receives second information sent by the second device, the second information is used to configure flow coloring instance characteristic information for the first device; the first device generates a second message header based on 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.

[0061] 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 enablement status, flow coloring flipping period, hop-by-hop detection status, and the like.

[0062] 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.

[0063] In some embodiments, the stream coloring instance feature information may include the following content as shown in Table 2:

[0064] Table 2

[0065] Please refer to Figure 4, which is a flowchart of an information configuration method provided by an embodiment of the present disclosure, the method is applied to a second device, such as a control device or a control system in an SPN. As shown in Figure 4, the method includes the following step 41.

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

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

[0068] Optionally, the type of the guide tag is any one of the following: bottom of stack, non-bottom of stack.

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

[0070] 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.

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

[0072] Optionally, the first information may include: a guide tag and a stack bottom identifier configuration of the guide 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 to 0, it may indicate that the corresponding guide tag is not at the stack bottom; if the stack bottom identifier is configured to 1, it may indicate that the corresponding guide tag is at the stack bottom. For another example, if the stack bottom identifier is configured to 1, it may indicate that the corresponding guide tag is not at the stack bottom; if the stack bottom identifier is configured to 0, it may indicate that the corresponding guide tag is at the stack bottom.

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

[0074] In an embodiment of the present disclosure, the second device can be configured based on the Inband OAM FII type supported by the metropolitan area device. Before sending the first information to the first device, the information configuration method further includes: the second device identifying the type of guide tag or flow ID tag supported by the third device, where the type is, for example, bottom of stack or non-bottom of stack. For example, the second device can identify the type of guide tag or flow ID tag supported by the third device based on preset information; and the second device generates the first information based on the type of guide tag or flow ID tag supported by the third device, i.e., determining the type of guide tag or flow ID tag to be configured for the first device.

[0075] 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 utilizes the Inband OAM method supported by the metropolitan area device for configuration, so that the types of guide tags or flow ID tags supported by relevant terminal devices and metropolitan area devices are consistent, thereby achieving end-to-end interoperability of follow-up detection.

[0076] Optionally, when the type of the boot tag or stream ID tag identified by the third device is bottom of stack, the first information indicates that the type of the boot tag or stream ID tag identified by the first device is bottom of stack.

[0077] Optionally, when the type of the boot tag or stream ID tag identified 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 identified by the first device is non-bottom of the stack.

[0078] 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.

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

[0080] Table 3

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

[0082] 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 packet header in combination with the flow coloring instance characteristic information.

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

[0084] It should be noted that the information configuration method provided in the embodiments of the present disclosure can be executed by an information configuration device or a control module in the information configuration device for executing the information configuration method. The embodiments of the present disclosure use an information configuration device executing the information configuration method as an example to illustrate the information configuration device provided in the embodiments of the present disclosure.

[0085] 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. 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 into 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, wherein the first information is used to configure the type of the boot tag or flow ID tag identification for the first device.

[0086] Optionally, the type of the guide tag is any one of the following: bottom of stack, non-bottom of stack.

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

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

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

[0090] 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 first device with a boot label or a flow ID label identifying a type of stack bottom, the first field in the first message header is a first value; or, when the first information configures the first device with a boot label or a flow ID label identifying a type of non-stack bottom, the first field in the first message header is a second value.

[0091] Optionally, the receiving module 51 is further configured to receive second information sent by a second device, where the second information is used to configure flow coloring instance characteristic information for the first device. The first generating module is further configured to generate a second message header based on the first information and the second information, wherein the type of the guide tag or flow ID tag identified in the second message header is determined based on the first information, and the in-flow detection characteristic information in the second message header is determined based on the flow coloring instance characteristic information.

[0092] Optionally, the flow coloring instance characteristic information includes at least one of the following: flow ID, in-flow detection enable status, flow coloring flipping 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.

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

[0094] 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. The device is applied to a second device, such as a control device or control system in an SPN. In some embodiments of the present disclosure, the information configuration device may include or be integrated into the second device. As shown in Figure 6, the information configuration device 60 includes: a sending module 61 for sending first information to a first device, wherein the first information is used to configure the type of the boot tag or flow ID tag identification for the first device.

[0095] Optionally, the type of the guide tag is any one of the following: bottom of stack, non-bottom of stack.

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

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

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

[0099] Optionally, the information configuration device 60 also includes: an identification module for identifying the type of boot tag or flow ID tag identification supported by the third device; and a second generation module for generating the first information according to the type of boot tag or flow ID tag identification supported by the third device.

[0100] Optionally, when the type of the boot tag or stream ID tag identified by the third device is bottom of stack, the first information indicates that the type of the boot tag or stream ID tag identified by the first device is bottom of stack.

[0101] Optionally, when the type of the boot tag or stream ID tag identified 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 identified by the first device is non-bottom of the stack.

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

[0103] 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.

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

[0105] Optionally, as shown in FIG7 , an 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, when executed by the processor 71, implements the various processes of the embodiment of the information configuration method shown in FIG2 above, and can achieve the same technical effect. When the communication device 70 is a second device, the program or instruction, when executed by the processor 71, implements the various processes of the embodiment of the information configuration method shown in FIG4 above, and can achieve the same technical effect. To avoid repetition, they are not described here.

[0106] 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.

[0107] The embodiments of the present disclosure also provide a computer program product on which programs or instructions are stored. When the programs or instructions are executed by a processor, the various processes of the above-mentioned information configuration method embodiments can be implemented and the same technical effects can be achieved. To avoid repetition, they will not be described here.

[0108] 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 technologies, compact disc read-only memory (CD-ROM), digital versatile disc (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 herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves. That is, computer-readable media herein refers to non-transitory computer-readable media.

[0109] It should be noted that, in this document, the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, article, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or elements inherent to such process, method, article, or apparatus. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or apparatus comprising the element.

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

[0111] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus the necessary general hardware platform, and of course 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 the present disclosure is essentially or the part that contributes to the existing technology 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), including a number of instructions for enabling a service classification device (which can be a mobile phone, computer, server, air conditioner, or network device, etc.) to execute the methods described in the various embodiments of the present disclosure.

[0112] 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 principles of the present disclosure. These improvements and modifications should also be regarded as within the scope of protection of the present disclosure.

Claims

1. 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.

2. 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.

3. The method according to claim 1, wherein The first information includes: A boot tag and a stack bottom identifier configuration of the boot tag; or The first information includes: a flow ID label identifier and a stack bottom bit of the flow ID label identifier.

4. 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 includes: 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.

5. 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.

6. 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.

7. 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.

8. 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.

9. The method according to claim 7, wherein The first information includes: A boot tag and a stack bottom identifier configuration of the boot tag; or The first information includes: a flow ID label identifier and a stack bottom bit of the flow ID label identifier.

10. The method according to claim 7, characterized in that Before sending the first information to the first device, the method further includes: 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.

11. 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 by 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.

12. 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.

13. 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.

14. 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.

15. 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 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.

16. A readable storage medium storing a program or an instruction, wherein the program or the 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.

17. 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.

Images