Message processing method and device, readable storage medium and computer program product

Abstract

The invention relates to a message processing method and device, a readable storage medium and a computer program product. The message processing method is used for a message packaging node in a message forwarding path, and comprises the following steps: packaging an indication field for a forwarded flow message, and sending the flow message packaged with the indication field, the indication field comprising an IOAM trace type field, a packet loss measurement field and a time delay measurement field; wherein the IOAM trace type field is used for indicating a node in a message forwarding path to report IOAM data to a receiving entity according to the indication of the IOAM trace type field; the packet loss measurement field is used for indicating the node in the message forwarding path to carry out packet loss measurement according to the indication of the packet loss measurement field; the time delay measurement field is used for indicating the node in the message forwarding path to carry out time delay measurement according to the indication of the time delay measurement field. By adopting the method, the network performance can be measured, and the message processing flexibility can be improved.

Description

Technical Field

[0001] The present application relates to the field of data communication technology, and in particular to a message processing method, device, readable storage medium and computer program product. Background Art

[0002] IOAM (In-band Operation Administration and Maintenance) technology collects OAM information including node ID (Identification), inbound interface ID, outbound interface ID, timestamp, etc. in the message forwarding path of the traffic message to implement IOAM trace monitoring.

[0003] Currently, the RFC (Request for Comments) standard also specifies some IOAM methods, taking the passport method as an example. In the passport method, each hop in the message forwarding path needs to collect and carry OAM metadata.

[0004] However, the passport method cannot monitor packet loss and packet loss location, nor can it perform periodic packet loss, delay and other performance measurements. In addition, the above IOAM method has the problem of low flexibility in flow message processing. Summary of the invention

[0005] Embodiments of the present application provide a message processing method, device, readable storage medium, and computer program product, which can measure network performance and improve message processing flexibility.

[0006] In a first aspect, an embodiment of the present application provides a message processing method. The message processing method is used in a message encapsulation node in a message forwarding path, and the method includes:

[0007] Encapsulate an indication field for the forwarded traffic message, and send the traffic message encapsulated with the indication field, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein:

[0008] The IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to the receiving entity according to the instruction of the IOAM trace type field;

[0009] The packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the instruction of the packet loss measurement field;

[0010] The delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the instruction of the delay measurement field.

[0011] In one of the embodiments, the indication field further includes an extension flag field, and the extension flag field is used to indicate a flow identifier and a message sequence identifier in the message forwarding path.

[0012] In one of the embodiments, the extended flag field includes a plurality of bits; when the 0th bit of the plurality of bits is set to a first value, an optional stream identification field exists in the indication field;

[0013] When the first bit among the multiple bits is set to a first value, an optional message sequence identification field exists in the indication field.

[0014] In one of the embodiments, the optional flow identification field includes 32 bits.

[0015] In one of the embodiments, the optional sequence identification field includes 32 bits.

[0016] In one of the embodiments, the extended flag field includes 8 bits.

[0017] In one of the embodiments, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and different bit values ​​are used to indicate whether a node in the message forwarding path reports the IOAM data to the receiving entity.

[0018] In one of the embodiments, the IOAM trace type field includes 24 bits.

[0019] In one of the embodiments, the field value of the packet loss measurement field of the traffic packets belonging to the same packet batch is the same.

[0020] In one of the embodiments, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

[0021] In one of the embodiments, the field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

[0022] In one of the embodiments, the packet loss measurement field is specifically used to instruct the nodes in the message forwarding path to determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field, and report the message count value corresponding to the message batch to the receiving entity.

[0023] In one of the embodiments, the packet loss measurement field includes 1 bit.

[0024] In one embodiment, the forwarded traffic message encapsulation indication field includes:

[0025] During the encapsulation process of the delay measurement field, determining a target flow message from each of the message batches;

[0026] The delay measurement field of the target traffic message is set to a first value, and the delay measurement field of other traffic messages in the message batch except the target traffic message is set to a second value, and the first value and the second value are different.

[0027] In one of the embodiments, the delay measurement field set to the first value is specifically used to instruct the node in the message forwarding path to report the message timestamp of the target traffic message to the receiving entity;

[0028] The delay measurement field set to the second value is specifically used to instruct the nodes in the message forwarding path to prohibit reporting the message timestamp of the other traffic message to the receiving entity.

[0029] In one of the embodiments, the delay measurement field includes 1 bit.

[0030] In one of the embodiments, the indication field also includes a namespace identification field, a flag field, and a reserved field.

[0031] In one embodiment, the namespace identification field includes 16 bits.

[0032] In one embodiment, the flag field includes 8 bits.

[0033] In one embodiment, the reserved field includes 6 bits.

[0034] In one embodiment, the forwarded traffic message encapsulation indication field includes:

[0035] Encapsulating the indication field in the first message header in the traffic message to instruct the nodes in the message forwarding path to perform hop-by-hop IOAM data reporting;

[0036] Alternatively, the indication field is encapsulated in a second message header in the traffic message to instruct the nodes in the message forwarding path to perform end-to-end IOAM data reporting.

[0037] In one embodiment, the method further comprises:

[0038] The IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, the packet loss measurement is performed according to the indication of the packet loss measurement field, and the delay measurement is performed according to the indication of the delay measurement field.

[0039] In a second aspect, an embodiment of the present application provides a message processing method. The message processing method is used for a message receiving node in a message forwarding path, and the method includes:

[0040] receiving a traffic message encapsulated with an indication field and sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field;

[0041] The IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, the packet loss measurement is performed according to the indication of the packet loss measurement field, and the delay measurement is performed according to the indication of the delay measurement field.

[0042] In one of the embodiments, the indication field further includes an extension flag field, and the method further includes:

[0043] According to the indication of the extended flag field, the flow identifier and the message sequence identifier in the message forwarding path are reported to the receiving entity.

[0044] In one embodiment, the extended flag field includes multiple bits, and reporting the flow identifier and the message sequence identifier in the message forwarding path to the receiving entity according to the indication of the extended flag field includes:

[0045] If the 0th bit among the multiple bits is set to a first value, reporting the flow identifier to the receiving entity;

[0046] If the first bit among the multiple bits is set to a first value, the message sequence identifier is reported to the receiving entity.

[0047] In one embodiment, the IOAM trace type field includes a plurality of bits, and different bits correspond to different IOAM data types. The reporting of IOAM data to a receiving entity according to an indication of the IOAM trace type field includes:

[0048] Determining, according to the value of each bit in the IOAM trace type field, the type of IOAM data that needs to be reported to the receiving entity;

[0049] Reporting IOAM data corresponding to the IOAM data type to the receiving entity.

[0050] In one of the embodiments, performing packet loss measurement according to the instruction of the packet loss measurement field includes:

[0051] Determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field;

[0052] Reporting, according to the message batches, the message count values ​​corresponding to each message batch to the receiving entity;

[0053] The field value of the packet loss measurement field of a plurality of continuous flow messages belonging to the same message batch is the same, and the field value of the packet loss measurement field of flow messages belonging to different message batches is different.

[0054] In one of the embodiments, performing delay measurement according to an indication of the delay measurement field includes:

[0055] Determine, from the message batch, a target traffic message in which the delay measurement field is set to a first value;

[0056] Reporting the message timestamp of the target traffic message to the receiving entity, and prohibiting reporting the message timestamps of other traffic messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

[0057] In a third aspect, an embodiment of the present application provides a message processing device. The message processing device is arranged at a message encapsulation node in a message forwarding path, and the device comprises:

[0058] A processing module, used for encapsulating an indication field for a forwarded traffic message, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein: the IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to a receiving entity according to the indication of the IOAM trace type field; the packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the indication of the packet loss measurement field; the delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the indication of the delay measurement field;

[0059] The sending module is used to send the traffic message encapsulated with the indication field.

[0060] In a fourth aspect, an embodiment of the present application provides a message processing device. The message processing device is arranged at a message receiving node in a message forwarding path, and the device comprises:

[0061] A receiving module, configured to receive a traffic message encapsulated with an indication field and sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field;

[0062] The sending module is used to report IOAM data to a receiving entity according to the indication of the IOAM trace type field, perform packet loss measurement according to the indication of the packet loss measurement field, and perform delay measurement according to the indication of the delay measurement field.

[0063] In a fifth aspect, an embodiment of the present application provides a communication device. The communication device includes: a processor and a transmitter;

[0064] The processor is used to encapsulate an indication field for a forwarded traffic message, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein: the IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to a receiving entity according to the indication of the IOAM trace type field; the packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the indication of the packet loss measurement field; the delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the indication of the delay measurement field;

[0065] The transmitter is used to send the traffic message encapsulated with the indication field.

[0066] In a sixth aspect, an embodiment of the present application provides a communication device. The communication device includes: a receiver and a transmitter;

[0067] The receiver is used to receive a traffic message encapsulated with an indication field and sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field;

[0068] The transmitter is used to report IOAM data to a receiving entity according to the indication of the IOAM trace type field, perform packet loss measurement according to the indication of the packet loss measurement field, and perform delay measurement according to the indication of the delay measurement field.

[0069] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, and when the computer program is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0070] In an eighth aspect, an embodiment of the present application provides a chip, wherein the chip includes a programmable logic circuit and / or program instructions, and when the chip is running, the steps of the method described in the first aspect or the second aspect are implemented.

[0071] In a ninth aspect, an embodiment of the present application provides a computer program product. The computer program product includes a computer program, and when the computer program is executed by a processor, the steps of the method described in the first aspect or the second aspect are implemented.

[0072] In the above-mentioned message processing method, device, readable storage medium and computer program product, the message encapsulation node encapsulates the indication field for the forwarded traffic message and sends the traffic message encapsulated with the indication field, and the indication field includes an IOAM trace type field, a packet loss measurement field and a delay measurement field; wherein: the IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to the receiving entity according to the indication of the IOAM trace type field; the packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the indication of the packet loss measurement field; the delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the indication of the delay measurement field; thus, the embodiment of the present application defines the indication field, The IOAM trace type field in the indication field is used to indicate that the nodes in the message forwarding path report IOAM data to the receiving entity. In this way, the nodes can directly report IOAM data to the receiving entity, thereby avoiding the problem that in traditional technology, the nodes collect IOAM data and carry it in the message for downward transmission. Once a message is lost, the IOAM trace monitoring will be interrupted, resulting in low flexibility in traffic message processing. The embodiment of the present application improves the flexibility of traffic message processing. In addition, the indication field of the embodiment of the present application also includes a packet loss measurement field and a delay measurement field. Based on the packet loss measurement field and the delay measurement field, the nodes in the message forwarding path can perform packet loss measurement, delay measurement, etc., thereby integrating network performance measurement into the IOAM method. BRIEF DESCRIPTION OF THE DRAWINGS

[0073] Figure 1 A diagram of an implementation environment of a message processing method in an embodiment;

[0074] Figure 2 A schematic diagram of a flow chart of a message processing method in an embodiment;

[0075] Figure 3 is a schematic diagram exemplarily indicating fields;

[0076] Figure 4 A schematic diagram of an exemplary message count value reported by a node in a message forwarding path;

[0077] Figure 5 It is a schematic diagram of the field value of the packet loss measurement field in the indication field of each traffic message in an exemplary service flow;

[0078] Figure 6 A schematic diagram of an exemplary message timestamp of a target traffic message reported by a node in a message forwarding path;

[0079] Figure 7 Schematic diagram of field values ​​of a packet loss measurement field L and a delay measurement field D in an indication field of each traffic message in an exemplary service flow;

[0080] Figure 8 is another schematic diagram for exemplarily indicating fields;

[0081] Fig. 9 A schematic diagram of a flow chart of a message processing method in another embodiment;

[0082] Fig.10 A schematic diagram of a flow chart of a message processing method in another embodiment;

[0083] Fig.11 is a structural block diagram of a message processing device in an embodiment;

[0084] Fig.12 is a structural block diagram of a message processing device in another embodiment;

[0085] Fig.13 is a schematic diagram of the structure of a communication device in one embodiment;

[0086] Fig.14 Schematic diagram of the structure of a chip in one embodiment. DETAILED DESCRIPTION

[0087] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0088] Figure 1 A schematic diagram of an implementation environment of a message processing method provided in an embodiment of the present application.

[0089] The message forwarding path includes multiple nodes: Figure 1 The message encapsulation node and penetration node shown in Figure 1 Two penetration nodes) and a message decapsulation node are shown as examples. The message encapsulation node and the penetration node connected thereto communicate through the network, the mutually connected penetration nodes communicate through the network, the message decapsulation node and the penetration node connected thereto can also communicate through the network, and the message encapsulation node, the message decapsulation node and the penetration node communicate with the receiving entity through the network respectively.

[0090] Of course, in other possible implementations, the message forwarding path may also only include a message encapsulation node and a message decapsulation node, and the message encapsulation node and the message decapsulation node communicate through a network.

[0091] The message encapsulation node, the penetration node, the message decapsulation node and the receiving entity may be servers respectively, and the server may be a single server or a server cluster composed of multiple servers.

[0092] In traditional technology, taking the passport method as an example, in the passport method, each hop in the message forwarding path needs to collect and carry OAM metadata in the traffic message, and then pass the traffic message carrying OAM metadata to the next node. The next node continues to collect OAM metadata and continues to pass it down after carrying the OAM metadata in the received traffic message. However, the problem with this method is that the node collects IOAM data and carries it in the message and passes it down. Once a message is lost, the IOAM trace monitoring will be interrupted, resulting in low flexibility in traffic message processing. In addition, the passport method cannot monitor packet loss and packet loss location, nor can it perform periodic performance measurements such as packet loss and latency.

[0093] Based on the above-mentioned traditional technology, an embodiment of the present application provides a message processing method. By defining an indication field, the IOAM trace type field in the indication field indicates that the nodes in the message forwarding path report IOAM data to the receiving entity. In this way, the node can directly report IOAM data to the receiving entity, avoiding the problem that the nodes in the traditional technology collect IOAM data and carry it in the message for downward transmission. Once a message is lost, it will cause the IOAM trace monitoring to be interrupted and cause low flexibility in traffic message processing. The embodiment of the present application improves the flexibility of traffic message processing; in addition, the indication field of the embodiment of the present application also includes a packet loss measurement field and a delay measurement field. Based on the packet loss measurement field and the delay measurement field, the nodes in the message forwarding path can perform packet loss measurement, delay measurement, etc., thereby integrating network performance measurement into the IOAM method.

[0094] It should be noted that the beneficial effects brought about by the embodiments of the present application or the technical problems solved are not limited to this one, but may also include other implicit or related problems. For details, please refer to the description of the following embodiments.

[0095] In one embodiment, if Figure 2 As shown, a message processing method is provided, which is applied to Figure 1 Taking the packet encapsulation node in the packet forwarding path as an example, the following steps are included:

[0096] Step 201: The message encapsulation node encapsulates an indication field for the forwarded traffic message.

[0097] Please combine Figure 1During the transmission of a service flow, each flow message in the service flow first reaches a message encapsulation node in a message forwarding path, and then, for each flow message, the message encapsulation node needs to encapsulate the flow message. For example, the message encapsulation node needs to encapsulate a message header for the flow message.

[0098] For example, in an IPv6 (Internet Protocol Version 6) network environment, a message encapsulation node needs to encapsulate an IPv6 message header for each traffic message; in an IPv4 (Internet Protocol Version 4) network environment, a message encapsulation node needs to encapsulate an IPv4 message header for each traffic message.

[0099] In an embodiment of the present application, when it is necessary to simultaneously perform network performance measurement and IOAM trace monitoring on a certain service flow forwarded by a message encapsulation node, the message encapsulation node must insert an indication field corresponding to each flow message in each flow message in the service flow. That is, in the process of encapsulating each flow message in the service flow by the message encapsulation node, the indication field corresponding to each flow message is encapsulated together with the flow message. Exemplarily, the message encapsulation node can encapsulate the indication field corresponding to the flow message in the message header of the flow message.

[0100] Among them, determining whether a business flow needs to perform network performance measurement and IOAM trace monitoring at the same time can be determined by the controller, and then the controller sends the flow identifier of the business flow that needs to perform network performance measurement and IOAM trace monitoring at the same time to the message encapsulation node, and the message encapsulation node can determine the business flow based on the flow identifier; of course, the message encapsulation node can also determine whether a business flow needs to perform network performance measurement and IOAM trace monitoring at the same time, and treat the business flow that requires network performance measurement and IOAM trace monitoring at the same time as the business flow.

[0101] Step 202: The message encapsulation node sends a traffic message encapsulated with an indication field.

[0102] After the message encapsulation node encapsulates the indication field for each flow message, the message encapsulation node sends the flow message encapsulated with the indication field to a next-level node connected to the message encapsulation node in the message forwarding path.

[0103] As mentioned above, the next level node connected to the message encapsulation node can be Figure 1 The penetration node shown, of course, in the case where the message forwarding path only includes the message encapsulation node and the message decapsulation node, the next level node connected to the message encapsulation node can also be the message decapsulation node, and no specific limitation is made here.

[0104] The indication fields include an IOAM trace type field, a packet loss measurement field, and a delay measurement field.

[0105] In other possible implementations, the indication field also includes an extension flag field, a namespace identification field, a flag field, and a reserved field.

[0106] See also Figure 3 , Figure 3 FIG. 1 is a schematic diagram for exemplarily indicating fields. Figure 3 As shown, the IOAM-Trace-Type field is the IOAM trace type field, the L field is the packet loss measurement field, the D field is the delay measurement field, the Extension-Flags field is the extension flag field, the Namespace-ID field is the namespace identification field, Flags is the flag field, and Reserved is the reserved field.

[0107] Each field included in the indication field has a corresponding meaning and function. The meaning and function of each field in the indication field are introduced below.

[0108] 1) The IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to the receiving entity according to the instructions of the IOAM trace type field.

[0109] First, the "nodes in the message forwarding path" mentioned here are introduced. In the embodiments of the present application, the meaning of the nodes in the message forwarding path is different based on different measurement modes. For example, in the hop-by-hop measurement mode, the nodes in the message forwarding path refer to all nodes in the message forwarding path, such as Figure 1 The message encapsulation node, penetration node and message decapsulation node shown; in the end-to-end measurement mode, the nodes in the message forwarding path refer to the first node (ie, the message encapsulation node) and the tail node (ie, the message decapsulation node) in the message forwarding path.

[0110] The determination of the above two measurement modes will be introduced in the following embodiments and will not be described in detail here. Here, the IOAM trace type field is further described.

[0111] In the embodiment of the present application, the IOAM data includes, for example, one or more of a node ID, an input interface ID of the message in the node, an output interface ID, and a timestamp.

[0112] In this way, after the message receiving node in the message forwarding path (i.e., the node other than the message encapsulation node in the message forwarding path, of course, it can be understood that the steps performed by the message receiving node in the embodiment of the present application can also be performed by the message encapsulation node) receives the traffic message encapsulated with the indication field sent by the message encapsulation node, it reports the IOAM data to the receiving entity according to the indication of the IOAM trace type field in the message. For example, the message receiving node reports the node ID, the inbound interface ID of the message in the node, and the outbound interface ID.

[0113] As an implementation, the IOAM trace type field includes multiple bits. Exemplarily, the IOAM trace type field includes 24 bits, different bits correspond to different IOAM data types, and different bit values ​​are used to indicate whether a node in a message forwarding path reports IOAM data to a receiving entity.

[0114] For example, for a traffic message, the message encapsulation node sets the second highest bit (bit 1, the highest bit is bit 0) in the encapsulated IOAM trace type field to "1", indicating that the node in the message forwarding path needs to output the IOAM data of the node's input interface ID and output interface ID to the receiving entity, and so on.

[0115] In a possible implementation, for IOAM trace monitoring, all traffic packets in the business flow need to be subject to IOAM trace monitoring. Thus, for each traffic packet in the business flow, when the message encapsulation node encapsulates the indication field, it needs to mark the bit of the corresponding IOAM data type in the IOAM trace type field as a first value, for example, a mark of "1", and mark the other bits in the IOAM trace type field as a second value of "0".

[0116] In another possible implementation, for IOAM trace monitoring, the IOAM encapsulation node only needs to select a subset of the forwarded traffic messages, that is, only some of the traffic messages in the service flow may need to be monitored by IOAM trace. The message encapsulation node selects some traffic messages from the traffic messages of the service flow through a preset message selection strategy, and then, for each selected traffic message, when the message encapsulation node encapsulates the indication field, it needs to mark the corresponding IOAM data type bit in the IOAM trace type field as "1" and mark the remaining bits as "0"; and for the unselected traffic messages in the service flow, when the message encapsulation node encapsulates the indication field for each unselected traffic message, it needs to mark all 24 bits in the IOAM trace type field as "0", so that the nodes in the message forwarding path do not need to generate IOAM data of the traffic message and output it to the receiving entity.

[0117] In this way, when the receiving node reports IOAM data to the receiving entity according to the indication of the IOAM trace type field, for each flow message, it can first determine the IOAM data type that needs to be reported to the receiving entity according to the value of each bit in the IOAM trace type field. If a certain bit is marked as "1", it indicates that the IOAM data of the IOAM data type corresponding to the bit of the flow message needs to be reported. If a certain bit is marked as "0", it indicates that the IOAM data of the IOAM data type corresponding to the bit of the flow message does not need to be reported. If all bits in the IOAM trace type field of a flow message are marked as "0", it indicates that no IOAM data of the flow message does not need to be reported. Then, the receiving node reports the IOAM data corresponding to the IOAM data type to the receiving entity.

[0118] In traditional technology, an IOAM method is also defined: the postcard method. In the postcard method, each hop in the message forwarding path needs to generate an OAM metadata for each message and report it to the centralized acquisition controller, and the OAM metadata generated by each hop node is not attached to the traffic message.

[0119] However, in this IOAM mode, each hop node in the message forwarding path must generate an independent OAM message for each message in the monitored service flow. For example, if there are 1,000 messages in the monitored service flow, then for this service flow, each hop node needs to generate 1,000 OAM messages and report them to the centralized acquisition controller, thus generating a large amount of OAM data and consuming the resources of the network and the centralized acquisition controller.

[0120] In an embodiment of the present application, as a possible implementation method described above, for IOAM trace monitoring, the IOAM encapsulation node only needs to select a subset of forwarding traffic messages, that is, only some traffic messages in the business flow may need to be monitored by IOAM trace, thereby greatly reducing the number of messages for IOAM trace monitoring, reducing the amount of IOAM data, and saving network resources of the network and centralized acquisition and control device.

[0121] 2) The packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the instructions of the packet loss measurement field.

[0122] For network performance measurement, the IOAM encapsulation node must mark the packet loss measurement field in the indication field of each message.

[0123] In the embodiment of the present application, the packet loss measurement field includes 1 bit. In combination with the value of the bit of the packet loss measurement field of each traffic message, the node in the message forwarding path can also determine the measurement period and perform packet loss measurement according to the measurement period.

[0124] Exemplarily, the field value of the packet loss measurement field of the traffic packets belonging to the same message batch in the business flow is the same, and the traffic packets belonging to the same message batch are multiple continuous traffic packets. In addition, the field value of the packet loss measurement field of the traffic packets belonging to different message batches in the business flow is different; the packet loss measurement field is specifically used to instruct the nodes in the message forwarding path to determine the message batch to which the message belongs according to the field value of the packet loss measurement field, and report the message count value corresponding to the message batch to the receiving entity.

[0125] For example, see Figure 4 , Figure 4 The diagram is a schematic diagram of an exemplary node in a message forwarding path reporting a message count value, wherein a message batch can be used as a measurement period, and a node in the message forwarding path reports a message count value corresponding to the message batch in each batch (ie, each measurement period).

[0126] Combination Figure 5 , Figure 5 The packet loss measurement field (eg, Figure 3 Schematic diagram of the field value of the L field shown in FIG. 1 . In the process of the message encapsulation node encapsulating the indication field of each flow message in the service flow, the flow messages are grouped according to batches (Batch) to obtain multiple message batches: Batch1, Batch2, Batch3, etc., each message batch includes multiple flow messages, and then, the field value of the packet loss measurement field of multiple consecutive flow messages belonging to the same message batch is marked as the same value, and the field value of the packet loss measurement field of the flow messages of different message batches alternates between a first value (for example, 1) and a second value (for example, 0).

[0127] The message encapsulation node can divide the traffic messages into multiple message batches according to a fixed message quantity or a fixed timer method. The fixed message quantity, for example, 1000 consecutive traffic messages are considered as a message batch, and the fixed timer method, for example, multiple consecutive traffic messages within 10s are considered as a message batch.

[0128] In this way, when the receiving node performs packet loss measurement according to the indication of the packet loss measurement field, for each traffic message in the service flow, the receiving node determines the message batch to which the traffic message belongs according to the field value of the packet loss measurement field. For example, if the field value of the first 1000 consecutive traffic messages is 1, and the field value of the 1001st traffic message is 0, then the first 1000 traffic messages are determined to be batch 1 (Batch 1); if the field value of the 1001st to 2000th consecutive traffic messages is 0, and the field value of the 2001st traffic message is 1, then the 1001st to 2000th are determined to be batch 2 (Batch 2), and so on. Then, according to the message batch, the message count value corresponding to the traffic message batch is reported to the receiving entity, that is, for batch 1, the receiving node will report the number of messages it received as 1000, and for batch 2, the receiving node will report the number of messages it received as 1000, and so on.

[0129] The receiving entity can measure the message loss occurring between any nodes in each cycle and realize the packet loss measurement of the service flow by periodically comparing the message count values ​​reported by different nodes in the message forwarding path for each message batch.

[0130] It should be noted that compared with the postcard method in traditional technology, each hop in the message forwarding path needs to generate an OAM metadata for each message and report it to the centralized acquisition and control device. The centralized acquisition and control device analyzes the OAM metadata of each traffic message to perform packet loss measurement. This leads to the problem of large amount of data in the packet loss measurement process and excessive consumption of network resources.

[0131] However, in the delay measurement process of the embodiment of the present application, for a batch, the node only reports the message count value of the batch for packet loss measurement, thereby greatly reducing the amount of data in the delay measurement process and reducing the consumption of network resources.

[0132] As an implementation method, the nodes in the above-mentioned message forwarding path report IOAM data to the receiving entity, and may also report according to the above-mentioned message batches, that is, for a message batch, the nodes in the message forwarding path report not only the message count value in the message batch, but also the IOAM data of all or part of the traffic messages in the message batch, and support network performance measurement and IOAM trace monitoring at the same time.

[0133] 3) The delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the instructions of the delay measurement field.

[0134] For network performance measurement, the IOAM encapsulation node needs to mark the delay measurement field in the indication field of a single flow message in each message batch. As an implementation method, a message in the middle of each message batch can be selected as the single message.

[0135] As an implementation method, the delay measurement field includes 1 bit. When the message encapsulation node encapsulates the flow message indication field in the service flow corresponding to the message forwarding path, during the encapsulation process of the delay measurement field, the message encapsulation node determines the target flow message from each message batch, as described above, for example, selects the flow message in the middle position in each message batch as the single target flow message, and then, the message encapsulation node sets 1 bit position of the delay measurement field of the target flow message to a first value (for example, 1), and sets 1 bit position of the delay measurement field of other flow messages in the message batch except the target flow message to a second value (for example, 0), and the first value and the second value are different.

[0136] For example, see Figure 6 , Figure 6 The schematic diagram is an exemplary diagram of a node in a message forwarding path reporting a message timestamp of a target flow message. Among them, a message batch can be used as a measurement period, and a node in the message forwarding path reports a message timestamp of a target flow message in each batch (i.e., each measurement period).

[0137] Combined with the packet loss measurement process, Figure 5 Based on Figure 7 , Figure 7 The present invention is a schematic diagram of the field values ​​of the packet loss measurement field L and the delay measurement field D in the indication field of the traffic message in an exemplary service flow. In the process of encapsulating the indication field of each node in the service flow by the message encapsulation node, the traffic messages are grouped according to batches (Batch) to obtain multiple message batches: Batch1, Batch2, Batch3, etc., each message batch includes multiple traffic messages, and then the field values ​​of the packet loss measurement field of multiple continuous traffic messages belonging to the same message batch are marked as the same value, and the field values ​​of the packet loss measurement field of traffic messages of different message batches alternate between 1 and 0; then, the message encapsulation node determines the target traffic message from each message batch, and then, the message encapsulation node sets one bit of the delay measurement field of the target traffic message to 1, and sets one bit of the delay measurement field of other traffic messages in the message batch except the target traffic message to 0.

[0138] Among them, the delay measurement field set to the first value is specifically used to instruct the nodes in the message forwarding path to report the message timestamp of the target traffic message to the receiving entity; the delay measurement field set to the second value is specifically used to instruct the nodes in the message forwarding path to prohibit reporting the message timestamp of other messages to the receiving entity.

[0139] In this way, during the process of the message receiving node performing delay measurement according to the indication of the delay measurement field, for each message batch, the target traffic message whose delay measurement field is set to the first value can be determined from the various traffic messages in the message batch, and the message timestamp (i.e., the receiving timestamp) of the target traffic message can be recorded. The message receiving node reports the message timestamp of the target traffic message to the receiving entity, and is prohibited from reporting the message timestamps of other messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

[0140] The receiving entity can measure the delay value of the traffic message between any nodes by periodically comparing, that is, for each message batch, comparing the message timestamps belonging to the same traffic message reported by different nodes in the message forwarding path.

[0141] In the traditional postcard method, the centralized collector collects the OAM metadata reported by each node and performs correlation analysis on the OAM data reported by all nodes to monitor packet loss and its location. However, this IOAM method cannot periodically monitor key performance indicators of service flows such as packet loss, latency, and jitter.

[0142] The embodiment of the present application defines an indication field in the above manner to support the periodic measurement function of IOAM on indicators such as packet loss and delay.

[0143] 4) The extended flag field includes multiple bits, and the extended flag field is used to indicate the flow identifier and the message sequence identifier in the message forwarding path. Exemplarily, the extended flag field includes 8 bits, and when each bit of the extended flag field is set to "1", it indicates that there is a corresponding optional 4-byte field in the indication field.

[0144] Exemplarily, when the 0th bit among the multiple bits is set to the first value, it indicates that there is an optional flow identification field Flow ID (Optional) in the indication field, that is, the optional 4-byte field is the flow identification field, the optional flow identification field is used to encapsulate the flow identification, and the optional flow identification field includes 32 bits. Among them, the 0th bit is used to indicate the flow identification of the service flow in the message forwarding path.

[0145] For example, see Figure 8 , Figure 8 A schematic diagram exemplarily indicating fields.

[0146] It can be understood that, when the 0th bit of the extended flag field is set to the first value, for each flow message in the service flow, the field value of the optional flow identifier field in the indication field is the same, that is, the flow identifier is the flow identifier of the service flow. When the message receiving node parses the indication field of each flow message, if the 0th bit of the extended flag field is set to the first value, the message receiving node uploads the flow identifier of the service flow when reporting IOAM data, message count value and message timestamp, so that the receiving entity can perform IOAM trace monitoring and network performance measurement for the flow identifier.

[0147] When the first bit among the multiple bits is set to the first value, it indicates that there is an optional message sequence identification field Sequence Number (Optional) in the indication field, that is, the optional 4-byte field is a sequence identification field, and the optional sequence identification field is used to encapsulate the message sequence identification belonging to the same service flow, and the optional sequence identification field includes 32 bits. Among them, the first bit is used to indicate that the node in the message forwarding path reports the message sequence identification of the message in the service flow to the receiving entity.

[0148] In addition, in the indication field of the embodiment of the present application, the namespace identification field includes 16 bits, the flag field includes 8 bits, and the reserved field includes 6 bits.

[0149] In one embodiment, based on Figure 2 The embodiment shown, see Fig. 9 This embodiment relates to an exemplary implementation of a message encapsulation node for a flow message encapsulation indication field in a service flow corresponding to a message forwarding path. Fig. 9 As shown, step 201 includes:

[0150] Step 901: The message encapsulation node encapsulates the indication field in the first message header in the traffic message to instruct the nodes in the message forwarding path to perform hop-by-hop IOAM data reporting; or, the message encapsulation node encapsulates the indication field in the second message header in the traffic message to instruct the nodes in the message forwarding path to perform end-to-end IOAM data reporting for the traffic message.

[0151] As described above, based on different measurement modes, the meaning of the nodes in the message forwarding path in the embodiment of the present application is different. For example, in the hop-by-hop measurement mode, the nodes in the message forwarding path refer to all nodes in the message forwarding path, such as Figure 1 The message encapsulation node, penetration node and message decapsulation node shown; in the end-to-end measurement mode, the nodes in the message forwarding path refer to the first node (ie, the message encapsulation node) and the tail node (ie, the message decapsulation node) in the message forwarding path.

[0152] In an embodiment of the present application, if the message encapsulation node determines that the current measurement mode is a hop-by-hop measurement mode, then when encapsulating the traffic message in the service flow, the indication field is respectively encapsulated in the first message header in the traffic message. In this way, the node in the message forwarding path recognizes that the indication field is encapsulated in the first message header, and it is determined that it is a hop-by-hop measurement mode, so that each node in the message forwarding path needs to report IOAM data and measure network performance based on the indication of the indication field.

[0153] If the message encapsulation node determines that the current measurement mode is the end-to-end measurement mode, then when encapsulating the traffic message in the business flow, the indication field is respectively encapsulated in the second message header in the traffic message. In this way, the node in the message forwarding path recognizes that the indication field is encapsulated in the second message header, and it is determined that it is the end-to-end measurement mode. Therefore, the intermediate penetration node in the message forwarding path does not need to report IOAM data and measure network performance based on the indication of the indication field, and only the message encapsulation node and the message decapsulation node need to report IOAM data and measure network performance based on the indication of the indication field.

[0154] Among them, the process of reporting IOAM data and measuring network performance based on the indication of the indication field can be referred to the description of the above embodiment, which will not be repeated here.

[0155] In one embodiment, based on Figure 2 The embodiment shown in the figure relates to an exemplary process in which a message encapsulation node reports IOAM data and measures network performance according to an indication field in a flow message encapsulated with an indication field. The process includes the following steps A1:

[0156] Step A1: The message encapsulation node reports IOAM data to the receiving entity according to the instruction of the IOAM trace type field, performs packet loss measurement according to the instruction of the packet loss measurement field, and performs delay measurement according to the instruction of the delay measurement field.

[0157] The process of the above-mentioned message receiving node reporting IOAM data and measuring network performance according to the indication field in the traffic message encapsulated with the indication field can be referred to the process of the receiving node reporting IOAM data and measuring network performance according to the indication field in the traffic message encapsulated with the indication field in the above-mentioned text, which will not be repeated here.

[0158] In one embodiment, see Fig.10 , provides a message processing method for a message receiving node in a message forwarding path, as described above, the message receiving node refers to other nodes in the message forwarding path except the message encapsulation node, in the hop-by-hop measurement mode, other nodes in the message forwarding path except the message encapsulation node can be Figure 1The traversal nodes and message decapsulation nodes shown are as follows; in the end-to-end measurement mode, other nodes in the message forwarding path except the message encapsulation node can be message decapsulation nodes.

[0159] Of course, the method used in the embodiment of the present application for a message receiving node in a message forwarding path can also be used for a message encapsulation node, which will not be repeated here.

[0160] The message processing method includes:

[0161] Step 1001: A message receiving node receives a traffic message encapsulated with an indication field and sent by a message encapsulation node in a message forwarding path.

[0162] The indication fields include an IOAM trace type field, a packet loss measurement field, and a delay measurement field.

[0163] Step 1002: The message receiving node reports IOAM data to the receiving entity according to the instruction of the IOAM trace type field, performs packet loss measurement according to the instruction of the packet loss measurement field, and performs delay measurement according to the instruction of the delay measurement field.

[0164] In one of the embodiments, the indication field also includes an extension flag field. The message processing method of this embodiment also includes: the message receiving node reports the flow identifier and the message sequence identifier in the message forwarding path to the receiving entity according to the indication of the extension flag field.

[0165] In one embodiment, the extended flag field includes multiple bits, and according to the indication of the extended flag field, the flow identifier and the message sequence identifier in the message forwarding path are reported to the receiving entity, including: if the 0th bit among the multiple bits is set to the first value, the message receiving node reports the flow identifier to the receiving entity; if the 1st bit among the multiple bits is set to the first value, the message receiving node reports the message sequence identifier to the receiving entity.

[0166] In one of the embodiments, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and the IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, including: the message receiving node determines the IOAM data type that needs to be reported to the receiving entity according to the value of each bit in the IOAM trace type field; the message receiving node reports the IOAM data corresponding to the IOAM data type to the receiving entity.

[0167] In one of the embodiments, packet loss measurement is performed according to the indication of the packet loss measurement field, including: a message receiving node determines the message batch to which the traffic message belongs according to the field value of the packet loss measurement field; the message receiving node reports the message count value corresponding to each message batch to the receiving entity according to the message batch; wherein the field value of the packet loss measurement field of multiple consecutive traffic messages belonging to the same message batch is the same, and the field value of the packet loss measurement field of traffic messages belonging to different message batches is different.

[0168] In one of the embodiments, delay measurement is performed according to the indication of the delay measurement field, including: the message receiving node determines the target flow message whose delay measurement field is set to the first value from the message batch; the message receiving node reports the message timestamp of the target flow message to the receiving entity, and prohibits reporting the message timestamp of other flow messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

[0169] The implementation manner and beneficial effects of the above-mentioned message processing method for a message receiving node in a message forwarding path can be found in the relevant description of the implementation manner of the message processing method for a message encapsulation node above, and will not be repeated here.

[0170] The following is an example to illustrate the process of packet loss measurement and delay measurement in the embodiment of the present application.

[0171] 1) Packet loss measurement process

[0172] In an IPv6 network environment, based on different measurement modes, during the process in which the message encapsulation node encapsulates each traffic message of a service flow, the indication field defined in the embodiment of the present application can be carried in a Hop-by-Hop option header or a Destination option header.

[0173] Among them, if it is a hop-by-hop measurement mode, the Hop-by-Hop option header is used, so that each hop node in the message forwarding path needs to perform corresponding processing on the indication field; if it is an end-to-end measurement mode, the Destination option header is used, so that only the message encapsulation node and the message decapsulation node in the message forwarding path need to perform corresponding processing on the indication field.

[0174] Next, during the encapsulation process of the indication field, a Flow ID is assigned to the service flow. Exemplarily, the message encapsulation node can randomly assign the Flow ID or the centralized controller can uniformly assign the Flow ID. The random assignment of the Flow ID may cause a situation where the Flow ID is repeated and conflicted, and the centralized controller is preferably used for uniform assignment.

[0175] While the message encapsulation node records the Flow ID field of the service flow, for each flow message in the service flow, according to the fixed message number or fixed timer method, the bit value of the "L" field of each flow message is exchanged between 0 and 1.

[0176] In this way, the receiving node only reads the encapsulated tag value to identify which batch the flow message belongs to. All nodes in the message forwarding path count the messages in each batch and report the message count value of each batch to the receiving entity, and carry the Flow ID of the business flow. The receiving entity can measure the message loss occurring between any nodes by comparing the message count values ​​reported by different nodes in the message forwarding path.

[0177] Please combine Figure 5 , assuming that in a certain measurement period, each flow message of a batch of measured business flow (the measured business is the business flow, assuming its Flow ID = 100) is counted, the message count values ​​reported by the message encapsulation node and the first penetration node are the same, both are 1000, but the message count reported by the second penetration node is 980, and the message count value reported by the message decapsulation node is 970. Then, the message count values ​​reported by all nodes in the message forwarding path associated with the Flow ID of 100 by the receiving entity can accurately calculate the packet loss rate of the measurement period: (1000-970) / 1000=3%, and it can be determined that 20 messages are lost at the second penetration node and 10 messages are lost at the message decapsulation node.

[0178] 2) Delay measurement (or jitter measurement) process

[0179] As described above, the message encapsulation node uses the "L" bit to mark the generation of alternating batches of messages, and then uses the "D" bit to generate the measured delay of a single message in the batch. For each message batch, the message encapsulation node determines the target flow message from each message batch, and then the message encapsulation node sets one bit of the delay measurement field of the target flow message to 1, and sets one bit of the delay measurement field of other messages in the message batch except the target flow message to 0.

[0180] The receiving node identifies the target traffic message with the D bit set in each batch, and records the timestamp of the target traffic message reception as the message timestamp. The receiving node reports the message timestamp of each batch of messages with the D bit set to "1" to the receiving entity, and carries the Flow ID information of the business flow; the receiving entity compares the message timestamps of the same message reported by different nodes on the message forwarding path, and can measure the message delay value between any nodes.

[0181] It should be noted that delay measurement requires that each node in the message forwarding path maintain time synchronization. Figure 7 , assuming that in a certain measurement period, the packet encapsulation node is testing a batch of business flows (the business under test is the business flow, assuming that its Flow For a message with FlowID = 100, the D bit of a message is set to "1" in the packet. The message timestamp recorded when the message encapsulation node reports the message to the receiving entity is: 8:30:10:5 (hour: minute: second: millisecond). The message timestamp recorded when the intermediate penetration node reports the receipt of the message with the D bit set to "1" is: 8:30:10:7.5 (hour: minute: second: millisecond). The message timestamp recorded when the message decapsulation node reports the receipt of the message with the D bit set to "1" is: 8:30:10:13.8 (hour: minute: second: millisecond). The receiving entity associates the message timestamps reported by all nodes in the message forwarding path with FlowID 100. The end-to-end delay of the measurement period can be accurately calculated to be: 13.8-5=8.8 milliseconds, and the delay from the message encapsulation node to the penetration node is: 7.5-5=2.5 milliseconds.

[0182] It should be understood that, although the various steps in the above flowchart are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps is not strictly limited in order, and these steps can be executed in other orders. Moreover, at least a part of the steps in the above flowchart may include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0183] In one embodiment, Fig.11 As shown, a message processing device is provided, which is arranged in a message encapsulation node in a message forwarding path, and includes:

[0184] The processing module 1101 is used to encapsulate an indication field for a forwarded traffic message, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein: the IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to a receiving entity according to the indication of the IOAM trace type field; the packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the indication of the packet loss measurement field; the delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the indication of the delay measurement field;

[0185] The sending module 1102 is used to send the traffic message encapsulated with the indication field.

[0186] In one of the embodiments, the indication field further includes an extension flag field, and the extension flag field is used to indicate a flow identifier and a message sequence identifier in the message forwarding path.

[0187] In one of the embodiments, the extended flag field includes a plurality of bits; when the 0th bit of the plurality of bits is set to a first value, an optional stream identification field exists in the indication field;

[0188] When the first bit among the multiple bits is set to a first value, an optional message sequence identification field exists in the indication field.

[0189] In one of the embodiments, the optional flow identification field includes 32 bits.

[0190] In one of the embodiments, the optional sequence identification field includes 32 bits.

[0191] In one of the embodiments, the extended flag field includes 8 bits.

[0192] In one of the embodiments, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and different bit values ​​are used to indicate whether a node in the message forwarding path reports the IOAM data to the receiving entity.

[0193] In one of the embodiments, the IOAM trace type field includes 24 bits.

[0194] In one of the embodiments, the field value of the packet loss measurement field of the traffic packets belonging to the same packet batch is the same.

[0195] In one of the embodiments, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

[0196] In one of the embodiments, the field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

[0197] In one of the embodiments, the packet loss measurement field is specifically used to instruct the nodes in the message forwarding path to determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field, and report the message count value corresponding to the message batch to the receiving entity.

[0198] In one of the embodiments, the packet loss measurement field includes 1 bit.

[0199] In one of the embodiments, the processing module 1101 is specifically used to determine the target traffic message from each of the message batches during the encapsulation process of the delay measurement field; set the delay measurement field of the target traffic message to a first value, and set the delay measurement field of other traffic messages in the message batch except the target traffic message to a second value, and the first value and the second value are different.

[0200] In one of the embodiments, the delay measurement field set to the first value is specifically used to instruct the node in the message forwarding path to report the message timestamp of the target traffic message to the receiving entity;

[0201] The delay measurement field set to the second value is specifically used to instruct the nodes in the message forwarding path to prohibit reporting the message timestamp of the other traffic message to the receiving entity.

[0202] In one of the embodiments, the delay measurement field includes 1 bit.

[0203] In one of the embodiments, the indication field also includes a namespace identification field, a flag field, and a reserved field.

[0204] In one embodiment, the namespace identification field includes 16 bits.

[0205] In one embodiment, the flag field includes 8 bits.

[0206] In one embodiment, the reserved field includes 6 bits.

[0207] In one of the embodiments, the processing module 1101 is specifically used to encapsulate the indication field in the first message header in the traffic message to instruct the nodes in the message forwarding path to perform hop-by-hop IOAM data reporting; or, to encapsulate the indication field in the second message header in the traffic message to instruct the nodes in the message forwarding path to perform end-to-end IOAM data reporting.

[0208] In one of the embodiments, the sending module 1102 is further used to report IOAM data to a receiving entity according to the indication of the IOAM trace type field, perform packet loss measurement according to the indication of the packet loss measurement field, and perform delay measurement according to the indication of the delay measurement field.

[0209] For the specific definition of the message processing device in the message encapsulation node set in the message forwarding path, please refer to the definition of the message processing method in the message encapsulation node in the message forwarding path in the above text, which will not be repeated here. Each module in the above message processing device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above modules can be embedded in or independent of the processor in the message encapsulation node in the form of hardware, or can be stored in the memory in the message encapsulation node in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0210] In one embodiment, Fig.12 As shown, a message processing device is provided, which is arranged at a message receiving node in a message forwarding path, and includes:

[0211] The receiving module 1201 is used to receive a traffic message encapsulated with an indication field and sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field;

[0212] The sending module 1202 is used to report IOAM data to a receiving entity according to the indication of the IOAM trace type field, perform packet loss measurement according to the indication of the packet loss measurement field, and perform delay measurement according to the indication of the delay measurement field.

[0213] In one of the embodiments, the indication field further includes an extension flag field, and the sending module 1202 is further configured to report a flow identifier and a message sequence identifier in the message forwarding path to the receiving entity according to an indication of the extension flag field.

[0214] In one embodiment, the extended flag field includes multiple bits, and the sending module 1202 is specifically used to report the flow identifier to the receiving entity if the 0th bit among the multiple bits is set to the first value; if the 1st bit among the multiple bits is set to the first value, report the message sequence identifier to the receiving entity.

[0215] In one of the embodiments, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and the sending module 1202 is specifically used to determine the IOAM data type that needs to be reported to the receiving entity according to the value of each bit in the IOAM trace type field; and report the IOAM data corresponding to the IOAM data type to the receiving entity.

[0216] In one of the embodiments, the sending module 1202 is specifically used to determine the message batch to which the traffic message belongs based on the field value of the packet loss measurement field; and report the message count value corresponding to each message batch to the receiving entity according to the message batch; wherein the field value of the packet loss measurement field of multiple consecutive traffic messages belonging to the same message batch is the same, and the field value of the packet loss measurement field of traffic messages belonging to different message batches is different.

[0217] In one of the embodiments, the sending module 1202 is specifically used to determine the target traffic message in the message batch whose delay measurement field is set to the first value; report the message timestamp of the target traffic message to the receiving entity, and prohibit reporting the message timestamp of other traffic messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

[0218] For the specific definition of the message processing device in the receiving node in the message forwarding path, please refer to the definition of the message processing method in the receiving node in the message forwarding path in the above text, which will not be repeated here. Each module in the above message processing device can be implemented in whole or in part by software, hardware and a combination thereof. Each of the above modules can be embedded in or independent of the processor in the receiving node in the form of hardware, or can be stored in the memory in the receiving node in the form of software, so that the processor can call and execute the operations corresponding to each of the above modules.

[0219] Fig.13 A schematic diagram of the structure of a communication device provided for an embodiment of the present application. The communication device may be a message encapsulation node in a message forwarding path, and the communication device may include a receiver 31, a memory 32, a processor 33, at least one communication bus 34 and a transmitter 35. The communication bus 34 is used to realize the communication connection between components. The memory 32 may include a high-speed RAM memory, and may also include a non-volatile storage NVM, such as at least one disk memory. Various programs may be stored in the memory 32 for completing various processing functions and implementing the method steps of this embodiment. In this embodiment, the transmitter 35 may be a radio frequency processing module or a baseband processing module in the communication device, and the receiver 31 may also be a radio frequency processing module or a baseband processing module in the communication device. The transmitter 35 and the receiver 31 may be integrated together to realize a transceiver, and the transmitter 35 and the receiver 31 may be coupled to the processor 33, which can realize the action of receiving or sending under the instruction or control of the processor 33.

[0220] In this embodiment, the processor 33 is used to encapsulate an indication field for the forwarded traffic message, and the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein: the IOAM trace type field is used to instruct the node in the message forwarding path to report IOAM data to the receiving entity according to the indication of the IOAM trace type field; the packet loss measurement field is used to instruct the node in the message forwarding path to perform packet loss measurement according to the indication of the packet loss measurement field; the delay measurement field is used to instruct the node in the message forwarding path to perform delay measurement according to the indication of the delay measurement field;

[0221] The transmitter 35 is used to send the traffic message encapsulated with the indication field.

[0222] In one of the embodiments, the indication field further includes an extension flag field, and the extension flag field is used to indicate a flow identifier and a message sequence identifier in the message forwarding path.

[0223] In one of the embodiments, the extended flag field includes a plurality of bits; when the 0th bit of the plurality of bits is set to a first value, an optional stream identification field exists in the indication field;

[0224] When the first bit among the multiple bits is set to a first value, an optional message sequence identification field exists in the indication field.

[0225] In one of the embodiments, the optional flow identification field includes 32 bits.

[0226] In one of the embodiments, the optional sequence identification field includes 32 bits.

[0227] In one of the embodiments, the extended flag field includes 8 bits.

[0228] In one of the embodiments, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and different bit values ​​are used to indicate whether a node in the message forwarding path reports the IOAM data to the receiving entity.

[0229] In one of the embodiments, the IOAM trace type field includes 24 bits.

[0230] In one of the embodiments, the field value of the packet loss measurement field of the traffic packets belonging to the same packet batch is the same.

[0231] In one of the embodiments, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

[0232] In one of the embodiments, the field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

[0233] In one of the embodiments, the packet loss measurement field is specifically used to instruct the nodes in the message forwarding path to determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field, and report the message count value corresponding to the message batch to the receiving entity.

[0234] In one of the embodiments, the packet loss measurement field includes 1 bit.

[0235] In one of the embodiments, the processor 33 is specifically used to determine the target traffic message from each of the message batches during the encapsulation process of the delay measurement field; set the delay measurement field of the target traffic message to a first value, and set the delay measurement field of other traffic messages in the message batch except the target traffic message to a second value, and the first value and the second value are different.

[0236] In one of the embodiments, the delay measurement field set to the first value is specifically used to instruct the node in the message forwarding path to report the message timestamp of the target traffic message to the receiving entity;

[0237] The delay measurement field set to the second value is specifically used to instruct the nodes in the message forwarding path to prohibit reporting the message timestamp of the other traffic message to the receiving entity.

[0238] In one of the embodiments, the delay measurement field includes 1 bit.

[0239] In one of the embodiments, the indication field also includes a namespace identification field, a flag field, and a reserved field.

[0240] In one embodiment, the namespace identification field includes 16 bits.

[0241] In one embodiment, the flag field includes 8 bits.

[0242] In one embodiment, the reserved field includes 6 bits.

[0243] In one of the embodiments, the processor 33 is specifically used to encapsulate the indication field in the first message header in the traffic message to instruct the nodes in the message forwarding path to perform hop-by-hop IOAM data reporting; or, to encapsulate the indication field in the second message header in the traffic message to instruct the nodes in the message forwarding path to perform end-to-end IOAM data reporting.

[0244] In one of the embodiments, the transmitter 35 is further used to report IOAM data to a receiving entity according to an indication of the IOAM trace type field, perform packet loss measurement according to an indication of the packet loss measurement field, and perform delay measurement according to an indication of the delay measurement field.

[0245] Fig.13 The communication device shown may also be a receiving node in a message forwarding path (such as a message encapsulation node, a penetration node, or a message decapsulation node in the message forwarding path), wherein:

[0246] The receiver 31 is used to receive a traffic message encapsulated with an indication field sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field;

[0247] The transmitter 35 is configured to report IOAM data to a receiving entity according to the indication of the IOAM trace type field, perform packet loss measurement according to the indication of the packet loss measurement field, and perform delay measurement according to the indication of the delay measurement field.

[0248] In one of the embodiments, the indication field further includes an extension flag field, and the transmitter 35 is further configured to report a flow identifier and a message sequence identifier in the message forwarding path to the receiving entity according to an indication of the extension flag field.

[0249] In one embodiment, the extended flag field includes multiple bits, and the transmitter 35 is specifically used to report the flow identifier to the receiving entity if the 0th bit among the multiple bits is set to the first value; if the 1st bit among the multiple bits is set to the first value, report the message sequence identifier to the receiving entity.

[0250] In one of the embodiments, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and the transmitter 35 is specifically used to determine the IOAM data type that needs to be reported to the receiving entity according to the value of each bit in the IOAM trace type field; and report the IOAM data corresponding to the IOAM data type to the receiving entity.

[0251] In one of the embodiments, the transmitter 35 is specifically used to determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field; and report the message count value corresponding to each message batch to the receiving entity according to the message batch; wherein the field value of the packet loss measurement field of multiple consecutive traffic messages belonging to the same message batch is the same, and the field value of the packet loss measurement field of traffic messages belonging to different message batches is different.

[0252] In one of the embodiments, the transmitter 35 is specifically used to determine the target traffic message in the message batch whose delay measurement field is set to the first value; report the message timestamp of the target traffic message to the receiving entity, and prohibit reporting the message timestamp of other traffic messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

[0253] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0254] Encapsulate an indication field for the forwarded traffic message, and send the traffic message encapsulated with the indication field, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein:

[0255] The IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to the receiving entity according to the instruction of the IOAM trace type field;

[0256] The packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the instruction of the packet loss measurement field;

[0257] The delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the instruction of the delay measurement field.

[0258] In one of the embodiments, the indication field further includes an extension flag field, and the extension flag field is used to indicate a flow identifier and a message sequence identifier in the message forwarding path.

[0259] In one of the embodiments, the extended flag field includes a plurality of bits; when the 0th bit of the plurality of bits is set to a first value, an optional stream identification field exists in the indication field;

[0260] When the first bit among the multiple bits is set to a first value, an optional message sequence identification field exists in the indication field.

[0261] In one of the embodiments, the optional flow identification field includes 32 bits.

[0262] In one of the embodiments, the optional sequence identification field includes 32 bits.

[0263] In one of the embodiments, the extended flag field includes 8 bits.

[0264] In one of the embodiments, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and different bit values ​​are used to indicate whether a node in the message forwarding path reports the IOAM data to the receiving entity.

[0265] In one of the embodiments, the IOAM trace type field includes 24 bits.

[0266] In one of the embodiments, the field value of the packet loss measurement field of the traffic packets belonging to the same packet batch is the same.

[0267] In one of the embodiments, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

[0268] In one of the embodiments, the field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

[0269] In one of the embodiments, the packet loss measurement field is specifically used to instruct the nodes in the message forwarding path to determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field, and report the message count value corresponding to the message batch to the receiving entity.

[0270] In one of the embodiments, the packet loss measurement field includes 1 bit.

[0271] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0272] During the encapsulation process of the delay measurement field, determining a target flow message from each of the message batches;

[0273] The delay measurement field of the target traffic message is set to a first value, and the delay measurement field of other traffic messages in the message batch except the target traffic message is set to a second value, and the first value and the second value are different.

[0274] In one of the embodiments, the delay measurement field set to the first value is specifically used to instruct the node in the message forwarding path to report the message timestamp of the target traffic message to the receiving entity;

[0275] The delay measurement field set to the second value is specifically used to instruct the nodes in the message forwarding path to prohibit reporting the message timestamp of the other traffic message to the receiving entity.

[0276] In one of the embodiments, the delay measurement field includes 1 bit.

[0277] In one of the embodiments, the indication field also includes a namespace identification field, a flag field, and a reserved field.

[0278] In one embodiment, the namespace identification field includes 16 bits.

[0279] In one embodiment, the flag field includes 8 bits.

[0280] In one embodiment, the reserved field includes 6 bits.

[0281] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0282] Encapsulating the indication field in the first message header in the traffic message to instruct the nodes in the message forwarding path to perform hop-by-hop IOAM data reporting;

[0283] Alternatively, the indication field is encapsulated in a second message header in the traffic message to instruct the nodes in the message forwarding path to perform end-to-end IOAM data reporting.

[0284] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0285] The IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, the packet loss measurement is performed according to the indication of the packet loss measurement field, and the delay measurement is performed according to the indication of the delay measurement field.

[0286] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:

[0287] receiving a traffic message encapsulated with an indication field and sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field;

[0288] The IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, the packet loss measurement is performed according to the indication of the packet loss measurement field, and the delay measurement is performed according to the indication of the delay measurement field.

[0289] In one embodiment, the indication field further includes an extension flag field, and when the computer program is executed by the processor, the following steps are specifically implemented:

[0290] According to the indication of the extended flag field, the flow identifier and the message sequence identifier in the message forwarding path are reported to the receiving entity.

[0291] In one embodiment, the extended flag field includes a plurality of bits, and when the computer program is executed by a processor, the following steps are specifically implemented:

[0292] If the 0th bit among the multiple bits is set to a first value, reporting the flow identifier to the receiving entity;

[0293] If the first bit among the multiple bits is set to a first value, the message sequence identifier is reported to the receiving entity.

[0294] In one embodiment, the IOAM trace type field includes a plurality of bits, different bits correspond to different IOAM data types, and when the computer program is executed by the processor, the following steps are specifically implemented:

[0295] Determining, according to the value of each bit in the IOAM trace type field, the type of IOAM data that needs to be reported to the receiving entity;

[0296] Reporting IOAM data corresponding to the IOAM data type to the receiving entity.

[0297] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0298] Determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field;

[0299] Reporting, according to the message batches, the message count values ​​corresponding to each message batch to the receiving entity;

[0300] The field value of the packet loss measurement field of a plurality of continuous flow messages belonging to the same message batch is the same, and the field value of the packet loss measurement field of flow messages belonging to different message batches is different.

[0301] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0302] Determine, from the message batch, a target traffic message in which the delay measurement field is set to a first value;

[0303] Reporting the message timestamp of the target traffic message to the receiving entity, and prohibiting reporting the message timestamps of other traffic messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

[0304] Fig.14 It is a schematic structural diagram of the chip of an embodiment of the present application. Fig.14The chip 1200 shown includes a processor 1210, which can call and run a computer program from a memory to implement the method in the embodiment of the present application.

[0305] Alternatively, if Fig.14 As shown, the chip 1200 may further include a memory 1220. The processor 1210 may call and run a computer program from the memory 1220 to implement the method in the embodiment of the present application.

[0306] The memory 1220 may be a separate device independent of the processor 1210 , or may be integrated into the processor 1210 .

[0307] Optionally, the chip 1200 may further include an input interface 1230. The processor 1210 may control the input interface 1230 to communicate with other devices or chips, and specifically, may obtain information or data sent by other devices or chips.

[0308] Optionally, the chip 1200 may further include an output interface 1240. The processor 1210 may control the output interface 1240 to communicate with other devices or chips, and specifically, may output information or data to other devices or chips.

[0309] Optionally, the chip 1200 can be applied to the network element device in the embodiment of the present application, and the chip 1200 can implement the corresponding processes implemented in the various methods in the embodiment of the present application, which will not be described here for the sake of brevity.

[0310] It should be understood that the chip 1200 mentioned in the embodiment of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0311] The present application also provides a computer program product including instructions, and when the computer program is executed by a processor, the following steps are implemented:

[0312] Encapsulate an indication field for the forwarded traffic message, and send the traffic message encapsulated with the indication field, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein:

[0313] The IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to the receiving entity according to the instruction of the IOAM trace type field;

[0314] The packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the instruction of the packet loss measurement field;

[0315] The delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the instruction of the delay measurement field.

[0316] In one of the embodiments, the indication field further includes an extension flag field, and the extension flag field is used to indicate a flow identifier and a message sequence identifier in the message forwarding path.

[0317] In one of the embodiments, the extended flag field includes a plurality of bits; when the 0th bit of the plurality of bits is set to a first value, an optional stream identification field exists in the indication field;

[0318] When the first bit among the multiple bits is set to a first value, an optional message sequence identification field exists in the indication field.

[0319] In one of the embodiments, the optional flow identification field includes 32 bits.

[0320] In one of the embodiments, the optional sequence identification field includes 32 bits.

[0321] In one of the embodiments, the extended flag field includes 8 bits.

[0322] In one of the embodiments, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and different bit values ​​are used to indicate whether a node in the message forwarding path reports the IOAM data to the receiving entity.

[0323] In one of the embodiments, the IOAM trace type field includes 24 bits.

[0324] In one of the embodiments, the field value of the packet loss measurement field of the traffic packets belonging to the same packet batch is the same.

[0325] In one of the embodiments, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

[0326] In one of the embodiments, the field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

[0327] In one of the embodiments, the packet loss measurement field is specifically used to instruct the nodes in the message forwarding path to determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field, and report the message count value corresponding to the message batch to the receiving entity.

[0328] In one of the embodiments, the packet loss measurement field includes 1 bit.

[0329] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0330] During the encapsulation process of the delay measurement field, determining a target flow message from each of the message batches;

[0331] The delay measurement field of the target traffic message is set to a first value, and the delay measurement field of other traffic messages in the message batch except the target traffic message is set to a second value, and the first value and the second value are different.

[0332] In one of the embodiments, the delay measurement field set to the first value is specifically used to instruct the node in the message forwarding path to report the message timestamp of the target traffic message to the receiving entity;

[0333] The delay measurement field set to the second value is specifically used to instruct the nodes in the message forwarding path to prohibit reporting the message timestamp of the other traffic message to the receiving entity.

[0334] In one of the embodiments, the delay measurement field includes 1 bit.

[0335] In one of the embodiments, the indication field also includes a namespace identification field, a flag field, and a reserved field.

[0336] In one embodiment, the namespace identification field includes 16 bits.

[0337] In one embodiment, the flag field includes 8 bits.

[0338] In one embodiment, the reserved field includes 6 bits.

[0339] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0340] Encapsulating the indication field in the first message header in the traffic message to instruct the nodes in the message forwarding path to perform hop-by-hop IOAM data reporting;

[0341] Alternatively, the indication field is encapsulated in a second message header in the traffic message to instruct the nodes in the message forwarding path to perform end-to-end IOAM data reporting.

[0342] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0343] The IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, the packet loss measurement is performed according to the indication of the packet loss measurement field, and the delay measurement is performed according to the indication of the delay measurement field.

[0344] In one embodiment, the present application also provides a computer program product including instructions, and when the computer program is executed by a processor, the following steps are implemented:

[0345] receiving a traffic message encapsulated with an indication field and sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field;

[0346] The IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, the packet loss measurement is performed according to the indication of the packet loss measurement field, and the delay measurement is performed according to the indication of the delay measurement field.

[0347] In one embodiment, the indication field further includes an extension flag field, and when the computer program is executed by the processor, the following steps are specifically implemented:

[0348] According to the indication of the extended flag field, the flow identifier and the message sequence identifier in the message forwarding path are reported to the receiving entity.

[0349] In one embodiment, the extended flag field includes a plurality of bits, and when the computer program is executed by a processor, the following steps are specifically implemented:

[0350] If the 0th bit among the multiple bits is set to a first value, reporting the flow identifier to the receiving entity;

[0351] If the first bit among the multiple bits is set to a first value, the message sequence identifier is reported to the receiving entity.

[0352] In one embodiment, the IOAM trace type field includes a plurality of bits, different bits correspond to different IOAM data types, and when the computer program is executed by the processor, the following steps are specifically implemented:

[0353] Determining, according to the value of each bit in the IOAM trace type field, the type of IOAM data that needs to be reported to the receiving entity;

[0354] Reporting IOAM data corresponding to the IOAM data type to the receiving entity.

[0355] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0356] Determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field;

[0357] Reporting, according to the message batches, the message count values ​​corresponding to each message batch to the receiving entity;

[0358] The field value of the packet loss measurement field of a plurality of continuous flow messages belonging to the same message batch is the same, and the field value of the packet loss measurement field of flow messages belonging to different message batches is different.

[0359] In one embodiment, when the computer program is executed by a processor, the following steps are specifically implemented:

[0360] Determine, from the message batch, a target traffic message in which the delay measurement field is set to a first value;

[0361] Reporting the message timestamp of the target traffic message to the receiving entity, and prohibiting reporting the message timestamps of other traffic messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

[0362] Those of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0363] The technical features of the above embodiments may be arbitrarily combined. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0364] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.

Claims

1. A message processing method, characterized in that: A message encapsulation node used in a message forwarding path, the method comprising: Encapsulate an indication field for the forwarded traffic message, and send the traffic message encapsulated with the indication field, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein: The IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to the receiving entity according to the instruction of the IOAM trace type field; The packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the instruction of the packet loss measurement field; The delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the instruction of the delay measurement field.

2. The method according to claim 1, characterized in that The indication field also includes an extension flag field, and the extension flag field is used to indicate a flow identifier and a message sequence identifier in the message forwarding path.

3. The method according to claim 2, characterized in that The extended flag field includes a plurality of bits; when the 0th bit among the plurality of bits is set to a first value, an optional stream identification field exists in the indication field; When the first bit among the multiple bits is set to a first value, an optional message sequence identification field exists in the indication field.

4. The method according to claim 3, characterized in that The optional flow identification field includes 32 bits.

5. The method according to claim 3, characterized in that: The optional sequence identification field includes 32 bits.

6. The method according to any one of claims 2 to 5, characterized in that: The extended flag field includes 8 bits.

7. The method according to claim 1, characterized in that The IOAM trace type field includes a plurality of bits, different bits correspond to different IOAM data types, and different bit values ​​are used to indicate whether a node in the message forwarding path reports the IOAM data to the receiving entity.

8. The method according to claim 1 or 7, characterized in that: The IOAM trace type field includes 24 bits.

9. The method according to claim 1, characterized in that: The field value of the packet loss measurement field of the traffic packets belonging to the same packet batch is the same 。 10. The method according to claim 9, characterized in that The flow messages belonging to the same message batch are multiple continuous flow messages.

11. The method according to claim 9, characterized in that The field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

12. The method according to any one of claims 1-5, 7, 9-11, characterized in that: The packet loss measurement field is specifically used to instruct the nodes in the message forwarding path to determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field, and report the message count value corresponding to the message batch to the receiving entity.

13. The method according to claim 1, characterized in that The packet loss measurement field includes 1 bit.

14. The method according to claim 12, characterized in that The forwarded traffic message encapsulation indication field includes: During the encapsulation process of the delay measurement field, determining a target flow message from each of the message batches; The delay measurement field of the target traffic message is set to a first value, and the delay measurement field of other traffic messages in the message batch except the target traffic message is set to a second value, and the first value and the second value are different.

15. The method according to claim 14, characterized in that The delay measurement field set to the first value is specifically used to instruct the node in the message forwarding path to report the message timestamp of the target traffic message to the receiving entity; The delay measurement field set to the second value is specifically used to instruct the nodes in the message forwarding path to prohibit reporting the message timestamp of the other traffic message to the receiving entity.

16. The method according to claim 1, characterized in that The delay measurement field includes 1 bit.

17. The method according to claim 1, characterized in that The indication field also includes a namespace identification field, a flag field and a reserved field.

18. The method according to claim 17, characterized in that The namespace identification field includes 16 bits.

19. The method according to claim 17, characterized in that The flag field includes 8 bits.

20. The method according to claim 17, characterized in that The reserved field includes 6 bits.

21. The method according to claim 1, characterized in that The forwarded traffic message encapsulation indication field includes: Encapsulating the indication field in the first message header in the traffic message to instruct the nodes in the message forwarding path to perform hop-by-hop IOAM data reporting; Alternatively, the indication field is encapsulated in a second message header in the traffic message to instruct the nodes in the message forwarding path to perform end-to-end IOAM data reporting.

22. The method according to claim 1, characterized in that The method further comprises: The IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, the packet loss measurement is performed according to the indication of the packet loss measurement field, and the delay measurement is performed according to the indication of the delay measurement field.

23. A message processing method, characterized in that: For a message receiving node in a message forwarding path, the method comprises: receiving a traffic message encapsulated with an indication field and sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; The IOAM data is reported to the receiving entity according to the indication of the IOAM trace type field, the packet loss measurement is performed according to the indication of the packet loss measurement field, and the delay measurement is performed according to the indication of the delay measurement field.

24. The method according to claim 23, characterized in that The indication field further includes an extension flag field, and the method further includes: According to the indication of the extended flag field, the flow identifier and the message sequence identifier in the message forwarding path are reported to the receiving entity.

25. The method according to claim 24, characterized in that The extended flag field includes a plurality of bits, and the reporting, according to an instruction of the extended flag field, a flow identifier and a message sequence identifier in the message forwarding path to the receiving entity includes: If the 0th bit among the multiple bits is set to a first value, reporting the flow identifier to the receiving entity; If the first bit among the multiple bits is set to a first value, the message sequence identifier is reported to the receiving entity.

26. The method according to claim 23, characterized in that The IOAM trace type field includes a plurality of bits, and different bits correspond to different IOAM data types. The reporting of IOAM data to a receiving entity according to an indication of the IOAM trace type field includes: Determining, according to the value of each bit in the IOAM trace type field, the type of IOAM data that needs to be reported to the receiving entity; Reporting IOAM data corresponding to the IOAM data type to the receiving entity.

27. The method according to claim 23, characterized in that The performing packet loss measurement according to the instruction of the packet loss measurement field includes: Determine the message batch to which the traffic message belongs according to the field value of the packet loss measurement field; Reporting, according to the message batches, the message count values ​​corresponding to each message batch to the receiving entity; The field value of the packet loss measurement field of a plurality of continuous flow messages belonging to the same message batch is the same, and the field value of the packet loss measurement field of flow messages belonging to different message batches is different.

28. The method according to claim 27, characterized in that The performing delay measurement according to the indication of the delay measurement field includes: Determine, from the message batch, a target traffic message in which the delay measurement field is set to a first value; Reporting the message timestamp of the target traffic message to the receiving entity, and prohibiting reporting the message timestamps of other traffic messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

29. A message processing device, characterized in that: A message encapsulation node arranged in a message forwarding path, the device comprising: A processing module, used for encapsulating an indication field for a forwarded traffic message, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein: the IOAM trace type field is used to instruct the nodes in the message forwarding path to report IOAM data to a receiving entity according to the indication of the IOAM trace type field; the packet loss measurement field is used to instruct the nodes in the message forwarding path to perform packet loss measurement according to the indication of the packet loss measurement field; the delay measurement field is used to instruct the nodes in the message forwarding path to perform delay measurement according to the indication of the delay measurement field; The sending module is used to send the traffic message encapsulated with the indication field.

30. A message processing device, characterized in that: A message receiving node arranged in a message forwarding path, the device comprising: A receiving module, configured to receive a traffic message encapsulated with an indication field and sent by a message encapsulation node in the message forwarding path, wherein the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field; The sending module is used to report IOAM data to a receiving entity according to the indication of the IOAM trace type field, perform packet loss measurement according to the indication of the packet loss measurement field, and perform delay measurement according to the indication of the delay measurement field.

31. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 28 are implemented.

32. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 28 are implemented.

Images