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

By introducing IOAM trace type, packet loss measurement and delay measurement fields in the message forwarding path, the problem of packet loss and delay cannot be monitored in the prior art is solved, and the flexibility of traffic packet processing and network performance measurement is improved. ability.

WO2025011201A1PCT designated stage expired Publication Date: 2025-01-16CHINA TELECOM CORP LTD TECHNOLOGY INNOVATION CENTER +1

Patent Information

Application Number
PCT/CN2024/094458
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-07-07
Filing Date
2024-05-21
Publication Date
2025-01-16

AI Technical Summary

Technical Problem

The existing IOAM technology cannot monitor packet loss and packet loss location, cannot perform periodic performance measurements such as packet loss and delay, and has low flexibility in processing traffic packets.

Method used

Introduce IOAM trace type field, packet loss measurement field and delay measurement field in the message forwarding path, and instruct nodes to conduct IOAM data reporting, packet loss measurement and delay measurement to improve the flexibility of message processing.

Benefits of technology

It realizes the flexibility of measuring network performance and message processing, avoids the problem of IOAM trace monitoring interruption in traditional technology, and enhances the ability to measure network performance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024094458_16012025_PF_FP_ABST
    Figure CN2024094458_16012025_PF_FP_ABST
Patent Text Reader

Abstract

The present application relates to a message processing method, an apparatus, a readable storage medium and a computer program product. The message processing method is applied to a message packaging node in a message forwarding path. The method comprises: packaging an instruction field for a forwarded traffic message, and sending the traffic message packaged with the instruction field, the instruction field comprising an IOAM trace type field, a packet loss measurement field and a delay measurement field, the IOAM trace type field being used for instructing a node in the message forwarding path to report, according to an instruction of the IOAM trace type field, IOAM data to a reception entity, the packet loss measurement field being used for instructing the node in the packet forwarding path to perform, according to an instruction of the packet loss measurement field, packet loss measurement, and the delay measurement field being used for instructing the node in the message forwarding path to perform, according to an instruction of the delay measurement field, delay measurement. The method allows for network performance measurement, and improves message processing flexibility.
Need to check novelty before this filing date? Find Prior Art

Description

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

[0001] Related applications

[0002] This application claims priority to Chinese patent application number 202310836265.4, filed on July 7, 2023, entitled “Message processing method, device, readable storage medium and computer program product,” the entire text of which is hereby incorporated by reference. Technical Field

[0003] 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

[0004] In-band Operation Administration and Maintenance (IOAM) technology collects OAM information, including node identification (ID), inbound interface ID, outbound interface ID, and timestamp, along the packet forwarding path of traffic packets to implement IOAM trace monitoring.

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

[0006] However, the passport method cannot monitor packet loss and packet loss location, nor can it perform periodic performance measurements such as packet loss and latency. In addition, the above IOAM method also has the problem of low flexibility in traffic message processing.

[0007] Summary of the Invention

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

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

[0010] 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,

[0011] 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;

[0012] 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;

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

[0014] In one embodiment, 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.

[0015] In one embodiment, the extended flag field includes multiple bits; when the 0th bit in the multiple bits is set to a first value, the optional flow identification field exists in the indication field;

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

[0017] In one embodiment, the optional flow identification field includes 32 bits.

[0018] In one embodiment, the optional sequence identification field includes 32 bits.

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

[0020] In one embodiment, 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 the node in the message forwarding path reports the IOAM data to the receiving entity.

[0021] In one embodiment, the IOAM trace type field includes 24 bits.

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

[0023] In one embodiment, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

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

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

[0026] In one embodiment, the packet loss measurement field includes 1 bit.

[0027] In one embodiment, the forwarded traffic message encapsulation indication field, the method further includes:

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

[0029] 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, where the first value and the second value are different.

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

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

[0032] In one embodiment, the delay measurement field includes 1 bit.

[0033] In one embodiment, the indication field further includes a namespace identification field, a flag field, and a reserved field.

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

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

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

[0037] In one embodiment, the forwarded traffic message encapsulation indication field, the method further includes:

[0038] 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; or

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

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

[0041] Report IOAM data to a receiving entity according to the instruction of the IOAM trace type field, perform packet loss measurement according to the instruction of the packet loss measurement field, and perform delay measurement according to the instruction of the delay measurement field.

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

[0043] 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;

[0044] IOAM data is reported to a receiving entity according to an instruction of the IOAM trace type field, packet loss measurement is performed according to an instruction of the packet loss measurement field, and delay measurement is performed according to an instruction of the delay measurement field.

[0045] In one embodiment, the indication field further includes an extension flag field, and the method further includes:

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

[0047] 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 an instruction of the extended flag field includes:

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

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

[0050] In one embodiment, the IOAM trace type field includes multiple bits, different bits correspond to different IOAM data types, and reporting the IOAM data to the receiving entity according to an indication of the IOAM trace type field includes:

[0051] 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;

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

[0053] In one embodiment, performing packet loss measurement according to an instruction of the packet loss measurement field includes:

[0054] Determining the packet batch to which the traffic packet belongs according to the field value of the packet loss measurement field;

[0055] Reporting the message count value corresponding to each message batch to the receiving entity according to the message batch;

[0056] The field value of the packet loss measurement field of a plurality of consecutive traffic packets belonging to the same packet batch is the same, and the field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

[0057] In one embodiment, performing delay measurement according to an instruction of the delay measurement field includes:

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

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

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

[0061] a processing module, configured to encapsulate an indication field for a forwarded traffic message, the indication field including an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein the IOAM trace type field is configured to instruct a node in the message forwarding path to report IOAM data to a receiving entity according to an indication of the IOAM trace type field; the packet loss measurement field is configured to instruct a node in the message forwarding path to perform packet loss measurement according to an indication of the packet loss measurement field; and the delay measurement field is configured to instruct a node in the message forwarding path to perform delay measurement according to an indication of the delay measurement field;

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

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

[0064] 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;

[0065] The sending module is configured to report IOAM data to a receiving entity according to an instruction of the IOAM trace type field, perform packet loss measurement according to an instruction of the packet loss measurement field, and perform delay measurement according to an instruction of the delay measurement field.

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

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

[0068] The transmitter is configured to send the traffic message encapsulated with the indication field.

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

[0070] The receiver is 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;

[0071] The transmitter is configured 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.

[0072] In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the method described in the first or second aspect above.

[0073] 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 executed, the steps of the method described in the first aspect or the second aspect are implemented.

[0074] 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 or second aspect are implemented.

[0075] 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, 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 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; and 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. In this way, the embodiment of the present application defines an indication field, and instructs the nodes in the message forwarding path to report IOAM data to the receiving entity through the IOAM trace type field in the indication field, so that the node can directly report IOAM data to the receiving entity, avoiding the problem in traditional technology that the node collects IOAM data and carries it in the message for transmission downward, and once a message is lost, it will cause the IOAM trace monitoring to be interrupted, resulting in low flexibility in traffic message processing. The embodiments of the present application enhance the flexibility of traffic message processing. Furthermore, the indication field in the embodiments of the present application also includes a packet loss measurement field and a delay measurement field. Based on these packet loss measurement fields and delay measurement fields, 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

[0076] To more clearly illustrate the technical solutions in the embodiments of this application or related technologies, the following briefly introduces the drawings required for use in the embodiments or related technology descriptions. Obviously, the drawings described below are only some embodiments of this application. For those of ordinary skill in the art, other drawings can be derived from these drawings without inventive effort.

[0077] FIG1 is a diagram showing an application environment of a message processing method in an embodiment of the present application.

[0078] FIG2 is a flow chart of a message processing method in an embodiment of the present application.

[0079] FIG3 is a schematic diagram of an exemplary indication field of the present application.

[0080] FIG4 is a schematic diagram of an exemplary message counting value reported by a node in a message forwarding path of the present application.

[0081] FIG5 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 of the present application.

[0082] FIG6 is a schematic diagram of an exemplary message timestamp of a target traffic message reported by a node in a message forwarding path of the present application.

[0083] FIG7 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 each traffic message in an exemplary service flow of the present application.

[0084] FIG8 is a schematic diagram of another exemplary indication field of the present application.

[0085] FIG9 is a flow chart of a message processing method in another embodiment of the present application.

[0086] FIG10 is a flow chart of a message processing method in another embodiment of the present application.

[0087] FIG11 is a structural block diagram of a message processing device in an embodiment of the present application.

[0088] FIG12 is a structural block diagram of a message processing device in another embodiment of the present application.

[0089] FIG13 is a schematic structural diagram of a communication device in an embodiment of the present application.

[0090] FIG14 is a schematic structural diagram of a chip in one embodiment of the present application. DETAILED DESCRIPTION

[0091] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0092] FIG1 is a schematic diagram of an application environment of a message processing method provided in an embodiment of the present application.

[0093] The message forwarding path includes multiple nodes, such as the message encapsulation node, the penetration node (Figure 1 shows two penetration nodes by way of example), and the message decapsulation node, as shown in Figure 1. The message encapsulation node communicates with the penetration node connected to it through a network, the interconnected penetration nodes communicate with each other through a network, and the message decapsulation node communicates with the penetration node connected to it through a network. Furthermore, the message encapsulation node, the message decapsulation node, and the penetration node each communicate with the receiving entity through a network.

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

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

[0096] In traditional technologies, such as 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 the OAM metadata to the next node. The next node continues to collect OAM metadata and carries the OAM metadata in the received traffic message and continues to pass it down. However, a problem with this method is that the node collects IOAM data and carries it in the message before passing it down. If 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.

[0097] Based on the above-mentioned traditional technology, the embodiment of the present application provides a message processing method. By defining an indication field and an IOAM trace type field in the indication field, the node in the message forwarding path is instructed to 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 node collects IOAM data and carries it in the message and transmits it downward in the traditional technology. 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.

[0098] It should be noted that the beneficial effects or technical problems solved by the embodiments of the present application 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.

[0099] In one embodiment, as shown in FIG2 , a message processing method is provided, which is described by taking the method applied to a message encapsulation node in the message forwarding path in FIG1 as an example, and includes the following steps S201 to S202 .

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

[0101] Referring to Figure 1, during the transmission of a service flow, each traffic message in the service flow first reaches a message encapsulation node in the message forwarding path. Then, for each traffic message, the message encapsulation node needs to encapsulate the traffic message. For example, the message encapsulation node needs to encapsulate the traffic message with a message header.

[0102] For example, in an Internet Protocol Version 6 (IPV6) network environment, the packet encapsulation node needs to encapsulate an IPv6 header for each traffic packet. In an Internet Protocol Version 4 (IPV4) network environment, the packet encapsulation node needs to encapsulate an IPv4 header for each traffic packet.

[0103] In an embodiment of the present application, when it is necessary to simultaneously perform network performance measurement and IOAM trace monitoring on a service flow forwarded by a message encapsulation node, the message encapsulation node must insert an indication field corresponding to each flow packet into each flow packet in the service flow. Specifically, during the process of encapsulating each flow packet in the service flow, the message encapsulation node encapsulates the indication field corresponding to each flow packet along with the flow packet. For example, the message encapsulation node may encapsulate the indication field corresponding to the flow packet in the flow packet header.

[0104] The controller can determine whether a service flow requires both network performance measurement and IOAM trace monitoring. The controller then sends the flow identifier of the service flow requiring both network performance measurement and IOAM trace monitoring to the message encapsulation node, which then identifies the service flow based on the flow identifier. Alternatively, the message encapsulation node can independently determine whether a service flow requires both network performance measurement and IOAM trace monitoring and designate the service flow requiring both as a service flow.

[0105] Step S202: Sending a traffic message encapsulated with an indication field through a message encapsulation node.

[0106] 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 the next-level node connected to the message encapsulation node in the message forwarding path.

[0107] As mentioned above, the next-level node connected to the message encapsulation node can be the penetration node shown in Figure 1. Of course, when 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 restrictions are made here.

[0108] The indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field.

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

[0110] See Figure 3, which is a schematic diagram illustrating exemplary fields. As shown in Figure 3, the IOAM-Trace-Type field represents the IOAM trace type field, the L field represents the packet loss measurement field, the D field represents the latency measurement field, the Extension-Flags field represents the extension flag field, the Namespace-ID field represents the namespace identifier field, the Flags field represents the flag field, and the Reserved field represents the reserved field.

[0111] Each field in the indication field has a corresponding meaning and function. The following describes the meaning and function of each field in the indication field.

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

[0113] First, let's introduce the "nodes in the message forwarding path" mentioned here. In the embodiments of the present application, the meanings of the nodes in the message forwarding path are 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 the message encapsulation node, penetration node, and message decapsulation node shown in Figure 1. In the end-to-end measurement mode, the nodes in the message forwarding path refer to the first node (i.e., the message encapsulation node) and the tail node (i.e., the message decapsulation node) in the message forwarding path.

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

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

[0116] Thus, after a message receiving node in the message forwarding path (i.e., a node other than the message encapsulation node in the message forwarding path; of course, it is 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 a traffic message encapsulated with an indication field sent by the message encapsulation node, it reports IOAM data to the receiving entity based on the indication of the IOAM trace type field in the message. For example, the message receiving node reports the node ID, the message's inbound interface ID, and the outbound interface ID in the node.

[0117] As an embodiment, 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 the nodes in the message forwarding path report IOAM data to the receiving entity.

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

[0119] In one possible implementation, for IOAM trace monitoring, all traffic packets in the service flow need to be monitored for IOAM trace. Thus, for each traffic packet in the service flow, when the packet 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, for example, a mark of "0".

[0120] In another possible implementation, for IOAM trace monitoring, the IOAM encapsulation node only needs to select a subset of forwarded traffic packets, that is, only some traffic packets in the service flow may need to be monitored for IOAM trace. The message encapsulation node selects some traffic packets from the traffic packets of the service flow through a preset message selection strategy. Then, for each selected traffic packet, 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 "1" and mark the remaining bits as "0". For traffic packets not selected in the service flow, when the message encapsulation node encapsulates the indication field for each unselected traffic packet, 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 for the traffic packet and output it to the receiving entity.

[0121] 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 traffic message, it can first determine the IOAM data type that needs to be reported to the receiving entity based on the value of each bit in the IOAM trace type field. If a bit is marked as "1", it indicates that the IOAM data of the IOAM data type corresponding to the bit in the traffic message needs to be reported. If a bit is marked as "0", it indicates that the IOAM data of the IOAM data type corresponding to the bit in the traffic message does not need to be reported. If all bits in the IOAM trace type field of a traffic message are marked as "0", it indicates that no IOAM data of the traffic 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.

[0122] Traditionally, a postcard IOAM approach has been defined. In this approach, each hop in the packet forwarding path generates OAM metadata for each packet and reports it to a centralized controller. The OAM metadata generated by each hop is not included in the traffic packet.

[0123] However, in this IOAM approach, each hop in the message forwarding path must generate a separate OAM message for each message in the monitored service flow. For example, if the monitored service flow contains 1,000 messages, each hop will need to generate 1,000 OAM messages for this service flow and report them to the centralized control center. This generates a large amount of OAM data, consuming network and centralized control center resources.

[0124] In an embodiment of the present application, as described above in one possible implementation, 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 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.

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

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

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

[0128] For example, the packet loss measurement field value of traffic packets belonging to the same packet batch in a service flow is the same, and the traffic packets belonging to the same packet batch are multiple consecutive traffic packets. Furthermore, the packet loss measurement field value of traffic packets belonging to different packet batches in a service flow is different. The packet loss measurement field is specifically used to instruct nodes in the message forwarding path to determine the message batch to which a message belongs based on the field value of the packet loss measurement field, and to report the message count value corresponding to the message batch to the receiving entity.

[0129] For example, see Figure 4, which is a schematic diagram of an exemplary embodiment of a node in a message forwarding path reporting a message count value. A message batch can serve 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 (i.e., each measurement period).

[0130] In conjunction with Figure 5, Figure 5 is a schematic diagram of the field values ​​of the packet loss measurement field (the L field shown in Figure 3) in the indication field of a traffic message in an exemplary service flow. During the process of encapsulating the indication field of each traffic message in the service flow by the message encapsulation node, the traffic messages are grouped according to batches (Batch), resulting in multiple message batches: Batch 1, Batch 2, Batch 3, ..., Batch n, etc., each message batch including multiple traffic messages; then, the field value of the packet loss measurement field of multiple consecutive traffic messages belonging to the same message batch is marked as the same value, and the field value of the packet loss measurement field of traffic messages in different message batches alternates between a first value (e.g., 1) and a second value (e.g., 0).

[0131] The packet encapsulation node can divide traffic packets into multiple packet batches based on a fixed packet number or a fixed timer. For example, a fixed packet number can be 1000 consecutive traffic packets as a packet batch, or a fixed timer can be 10 seconds or more consecutive traffic packets as a packet batch.

[0132] 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 based on 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.

[0133] The receiving entity compares the message counts reported by different nodes in the message forwarding path for each message batch periodically, and can measure the amount of message loss occurring between any nodes in each cycle, thereby realizing packet loss measurement of the service flow.

[0134] 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 data volume in the packet loss measurement process and excessive consumption of network resources.

[0135] However, in the embodiment of the present application, during the delay measurement process, 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.

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

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

[0138] 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, the message in the middle of each message batch can be selected as the single message.

[0139] As an embodiment, the delay measurement field includes one bit. When a message encapsulation node encapsulates the traffic message indication field in the service flow corresponding to the message forwarding path, during the encapsulation of the delay measurement field, the message encapsulation node determines a target traffic message from each message batch. As described above, for example, the middle traffic message in each message batch is selected as the single target traffic message. The message encapsulation node then sets one bit of the delay measurement field of the target traffic message to a first value (e.g., 1) and sets one bit of the delay measurement field of the other traffic messages in the message batch other than the target traffic message to a second value (e.g., 0), where the first value and the second value are different.

[0140] For example, see Figure 6, which is a schematic diagram of an exemplary message timestamp reported by a node in a message forwarding path for a target flow message. A message batch can be used as a measurement period, and a node in the message forwarding path reports the message timestamp of the target flow message in each batch (i.e., each measurement period).

[0141] In conjunction with the packet loss measurement process, referring to FIG5 , FIG7 is a schematic diagram illustrating the field values ​​of the packet loss measurement field L and the delay measurement field D in the indication field of a traffic packet in a service flow. During the process of encapsulating the indication field for each node in the service flow, the packet encapsulation node groups the traffic packets into batches, resulting in multiple batches: Batch 1, Batch 2, Batch 3, ..., Batch n, etc. Each batch includes multiple traffic packets. The packet loss measurement field values ​​of multiple consecutive traffic packets belonging to the same batch are then marked with the same value, while the packet loss measurement field values ​​of traffic packets in different batches alternate between 1 and 0. Next, the packet encapsulation node determines a target traffic packet from each batch and then sets one bit of the delay measurement field of the target traffic packet to a first value of 1, and sets one bit of the delay measurement field of all traffic packets in the batch other than the target traffic packet to a second value of 0.

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

[0143] In this way, when the message receiving node performs delay measurement according to the indication of the delay measurement field, for each message batch, the target flow message whose delay measurement field is set to the first value can be determined from the various flow messages in the message batch, and the message timestamp (i.e., the receiving timestamp) of the target flow message is recorded. The message receiving node reports the message timestamp of the target flow message to the receiving entity, and prohibits 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.

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

[0145] In the traditional postcard method, a centralized collector collects OAM metadata reported by each node and performs correlation analysis on the OAM metadata reported by all nodes, thereby monitoring 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.

[0146] In the above-mentioned manner, the embodiment of the present application defines an indication field to support the periodic measurement function of IOAM on indicators such as packet loss and latency.

[0147] 4) The Extended Flags field includes multiple bits and is used to indicate the flow identifier and message sequence identifier in the packet forwarding path. Exemplarily, the Extended Flags field includes 8 bits. When each bit of the Extended Flags field is set to "1", it indicates the presence of a corresponding optional 4-byte field in the Indicator field.

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

[0149] For example, see FIG8 , which is a schematic diagram of an exemplary indication field.

[0150] It is understood that when bit 0 of the Extended Flags field is set to the first value, the field value of the optional flow identifier field in the indication field of each traffic packet in the service flow 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 traffic packet, if bit 0 of the Extended Flags field is set to the first value, the message receiving node will upload 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 based on this flow identifier.

[0151] When the first bit among the multiple bits is set to the first value, it indicates that the optional message sequence identification field (Optional) Sequence Number is present in the indication field, that is, the optional 4-byte field is the sequence identification field, which is used to encapsulate the sequence identification of messages belonging to the same service flow. The optional sequence identification field includes 32 bits, of which the first bit is used to instruct a node in the message forwarding path to report the message sequence identification of the message in the service flow to the receiving entity.

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

[0153] In one embodiment, based on the embodiment shown in FIG2 , referring to FIG9 , this embodiment relates to an exemplary implementation of a packet encapsulation node encapsulating a flow packet indication field in a service flow corresponding to a packet forwarding path. As shown in FIG9 , step S201 further includes step S901.

[0154] Step S901: 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.

[0155] As described above, the meaning of the nodes in the message forwarding path in the embodiments of the present application varies depending on the measurement mode. For example, in hop-by-hop measurement mode, the nodes in the message forwarding path refer to all nodes in the message forwarding path, such as the message encapsulation node, traversal node, and message decapsulation node shown in Figure 1; in end-to-end measurement mode, the nodes in the message forwarding path refer to the first node (i.e., the message encapsulation node) and the last node (i.e., the message decapsulation node) in the message forwarding path.

[0156] 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 determines 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.

[0157] 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 determines 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. 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.

[0158] The process of reporting IOAM data and measuring network performance based on the indication of the indication field can be described in the above embodiment and will not be repeated here.

[0159] In one embodiment, in conjunction with the embodiment shown in FIG2 , this embodiment relates to an exemplary process in which a packet encapsulation node reports IOAM data and performs network performance measurement based on an indication field in a traffic packet encapsulated with an indication field. The process includes the following steps A1:

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

[0161] The above-mentioned message receiving node reports IOAM data and measures network performance according to the indication field in the traffic message encapsulated with the indication field. 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 can be referred to the above-mentioned process, which will not be repeated here.

[0162] In one embodiment, referring to FIG10 , a packet processing method is provided for a packet receiving node in a packet forwarding path. As described above, a packet receiving node refers to any node in the packet forwarding path other than the packet encapsulating node. In hop-by-hop measurement mode, any node in the packet forwarding path other than the packet encapsulating node may be a traversal node or a packet decapsulating node as shown in FIG1 . In end-to-end measurement mode, any node in the packet forwarding path other than the packet encapsulating node may be a packet decapsulating node.

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

[0164] The message processing method includes steps S1001 to S1002.

[0165] Step S1001: 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.

[0166] The indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field.

[0167] Step S1002: 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.

[0168] In one embodiment, the indication field further includes an extension flag field. The message processing method of this embodiment further 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.

[0169] In one embodiment, the extended flag field includes multiple bits. The step of reporting a flow identifier and a message sequence identifier in a message forwarding path to a receiving entity according to an indication of the extended flag field may include: if bit 0 among the multiple bits is set to a first value, the message receiving node reporting the flow identifier to the receiving entity; if bit 1 among the multiple bits is set to the first value, the message receiving node reporting the message sequence identifier to the receiving entity.

[0170] In one embodiment, the IOAM trace type field includes multiple bits, where different bits correspond to different IOAM data types. The step of reporting IOAM data to a receiving entity according to an indication of the IOAM trace type field may include: the message receiving node determining the IOAM data type to be reported to the receiving entity based on the value of each bit in the IOAM trace type field; and the message receiving node reporting the IOAM data corresponding to the IOAM data type to the receiving entity.

[0171] In one embodiment, the step of performing packet loss measurement according to the indication of the packet loss measurement field may include: the message receiving node determines the message batch to which the traffic message belongs based on 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.

[0172] In one embodiment, the step of performing delay measurement according to the indication of the delay measurement field may include: the message receiving node determines the target traffic 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 traffic message to the receiving entity, and prohibits 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.

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

[0174] The following describes the packet loss measurement and delay measurement processes of the embodiments of the present application through examples.

[0175] 1) Packet loss measurement process

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

[0177] In hop-by-hop measurement mode, the Hop-by-Hop option header is used. In this way, each hop node in the packet forwarding path needs to process the indication field accordingly. In end-to-end measurement mode, the Destination option header is used. In this way, only the packet encapsulation node and the packet decapsulation node in the packet forwarding path need to process the indication field accordingly.

[0178] Next, during the encapsulation of the indicator field, a Flow ID is assigned to the service flow. For example, the packet encapsulation node can randomly assign Flow IDs, or a centralized controller can uniformly assign Flow IDs. Randomly assigning Flow IDs can result in duplicate Flow ID conflicts, so a centralized controller is preferred.

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

[0180] In this way, the receiving node only reads the encapsulated tag value to identify the batch to which the flow message belongs. All nodes in the message forwarding path count the messages in each batch and report the message count value for each batch to the receiving entity, along with the service flow's Flow ID. By comparing the message count values ​​reported by different nodes in the message forwarding path, the receiving entity can measure the message loss occurring between any nodes.

[0181] Please refer to Figure 5. Assume 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, and the message count values ​​reported by the message encapsulation node and the first penetration node are the same, both 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 with the associated Flow ID of 100 of the receiving entity can be accurately calculated to obtain the packet loss rate of the measurement period: (1000-970) / 1000=3%, and it can be determined that 20 messages were lost at the second penetration node and 10 messages were lost at the message decapsulation node.

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

[0183] As described above, the packet encapsulation node uses the "L" bit to generate alternating batches of packets and then uses the "D" bit to generate the measured delay for each packet in the batch. For each packet batch, the packet encapsulation node identifies the target flow packet from each batch. The packet encapsulation node then sets one bit of the delay measurement field of the target flow packet to 1 and sets one bit of the delay measurement field of all packets in the batch except the target flow packet to 0.

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

[0185] It should be noted that the measurement of delay requires that each node in the message forwarding path maintain time synchronization. Please refer to Figure 7, assuming that in a certain measurement period, the message encapsulation node sets the D bit of a message in a batch of measured business flows (the measured business is the business flow, assuming its Flow ID = 100) to "1", and the message timestamp recorded when the message encapsulation node reports the message to the receiving entity is: 8:30:10:5 (hours: minutes: seconds: milliseconds), the middle penetration node reports the message timestamp recorded when receiving the message with the D bit set to "1": 8:30:10:7.5 (hours: minutes: seconds: milliseconds), the message decapsulation node reports the message timestamp recorded when receiving the message with the D bit set to "1": 8:30:10:13.8 (hours: minutes: seconds: milliseconds), the receiving entity associates Flow The message timestamps reported by all nodes in the forwarding path of the message with ID 100 can be used to accurately calculate the end-to-end delay of the measurement period: 13.8-5 = 8.8 milliseconds, and the delay from the message encapsulation node to the penetration node: 7.5-5 = 2.5 milliseconds.

[0186] It should be understood that, although the various steps in the above flow chart are shown in sequence as indicated by the arrows, these steps are not necessarily performed in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the above flow chart may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times. The execution order of these steps or stages is not necessarily to be performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0187] In one embodiment, as shown in FIG11 , a message processing device is provided, which is provided at a message encapsulation node in a message forwarding path, and includes:

[0188] Processing module 1101 is configured to encapsulate an indication field for a forwarded traffic message, the indication field including an IOAM trace type field, a packet loss measurement field, and a delay measurement field; wherein the IOAM trace type field is configured to instruct a node in the message forwarding path to report IOAM data to a receiving entity according to an indication of the IOAM trace type field; the packet loss measurement field is configured to instruct a node in the message forwarding path to perform packet loss measurement according to an indication of the packet loss measurement field; and the delay measurement field is configured to instruct a node in the message forwarding path to perform delay measurement according to an indication of the delay measurement field.

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

[0190] In one embodiment, 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.

[0191] In one embodiment, the extended flag field includes multiple bits; when the 0th bit among the multiple bits is set to the first value, an optional flow identification field exists in the indication field; when the 1st bit among the multiple bits is set to the first value, an optional message sequence identification field exists in the indication field.

[0192] In one embodiment, the optional flow identification field includes 32 bits.

[0193] In one embodiment, the optional sequence identification field includes 32 bits.

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

[0195] In one embodiment, 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 the node in the message forwarding path reports the IOAM data to the receiving entity.

[0196] In one embodiment, the IOAM trace type field includes 24 bits.

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

[0198] In one embodiment, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

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

[0200] In one embodiment, 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.

[0201] In one embodiment, the packet loss measurement field includes 1 bit.

[0202] In one embodiment, 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.

[0203] In one embodiment, 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 the other traffic messages to the receiving entity.

[0204] In one embodiment, the delay measurement field includes 1 bit.

[0205] In one embodiment, the indication field further includes a namespace identification field, a flag field, and a reserved field.

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

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

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

[0209] In one embodiment, 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.

[0210] In one embodiment, the sending module 1102 is further 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.

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

[0212] In one embodiment, as shown in FIG12 , a message processing device is provided, which is provided at a message receiving node in a message forwarding path, and includes:

[0213] The receiving module 1201 is 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;

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

[0215] In one embodiment, the indication field further includes an extension flag field, and the sending module 1202 is further configured to report 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.

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

[0217] In one embodiment, 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 based on 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.

[0218] In one embodiment, 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.

[0219] In one embodiment, 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 timestamps of other traffic messages in the message batch whose delay measurement field is set to the second value to the receiving entity.

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

[0221] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device can be a message encapsulation node in a message forwarding path. 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 implement communication connections 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 storage. Various programs can be stored in the memory 32 to perform various processing functions and implement the method steps of this embodiment. In this embodiment, the transmitter 35 can be a radio frequency processing module or a baseband processing module in the communication device, and the receiver 31 can also be a radio frequency processing module or a baseband processing module in the communication device. The transmitter 35 and the receiver 31 can be integrated together to form a transceiver. The transmitter 35 and the receiver 31 can both be coupled to the processor 33, and can perform receiving or transmitting actions under the instruction or control of the processor 33.

[0222] In this embodiment, the processor 33 is configured to encapsulate an indication field for a forwarded traffic message, where the indication field includes an IOAM trace type field, a packet loss measurement field, and a delay measurement field. The IOAM trace type field is configured to instruct nodes in the message forwarding path to report IOAM data to a receiving entity according to an indication of the IOAM trace type field. The packet loss measurement field is configured to instruct nodes in the message forwarding path to perform packet loss measurement according to an indication of the packet loss measurement field. The delay measurement field is configured to instruct nodes in the message forwarding path to perform delay measurement according to an indication of the delay measurement field.

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

[0224] In one embodiment, 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.

[0225] In one embodiment, the extended flag field includes multiple bits; when the 0th bit among the multiple bits is set to the first value, an optional flow identification field exists in the indication field; when the 1st bit among the multiple bits is set to the first value, an optional message sequence identification field exists in the indication field.

[0226] In one embodiment, the optional flow identification field includes 32 bits.

[0227] In one embodiment, the optional sequence identification field includes 32 bits.

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

[0229] In one embodiment, 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 the node in the message forwarding path reports the IOAM data to the receiving entity.

[0230] In one embodiment, the IOAM trace type field includes 24 bits.

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

[0232] In one embodiment, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

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

[0234] In one embodiment, 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.

[0235] In one embodiment, the packet loss measurement field includes 1 bit.

[0236] In one embodiment, 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.

[0237] In one embodiment, 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 the other traffic messages to the receiving entity.

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

[0239] In one embodiment, the indication field further 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 embodiment, 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 embodiment, the transmitter 35 is further 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.

[0245] The communication device shown in FIG13 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 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;

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

[0248] In one embodiment, the indication field further includes an extension flag field, and the transmitter 35 is further configured to report 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.

[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 embodiment, 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 based on 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 embodiment, the transmitter 35 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.

[0252] In one embodiment, 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 timestamps 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. 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 embodiment, 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 embodiment, the extended flag field includes a plurality of bits; when the 0th bit among the plurality of bits is set to a first value, the optional flow identification field is present in the indication field;

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

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

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

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

[0264] In one embodiment, 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 the node in the message forwarding path reports the IOAM data to the receiving entity.

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

[0266] In one embodiment, 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 embodiment, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

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

[0269] In one embodiment, 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 embodiment, 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, where the first value and the second value are different.

[0274] In one embodiment, 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 the other traffic messages to the receiving entity.

[0275] In one embodiment, the delay measurement field includes 1 bit.

[0276] In one embodiment, the indication field further includes a namespace identification field, a flag field, and a reserved field.

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

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

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

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

[0281] The indication field is encapsulated 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 indication field is encapsulated 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.

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

[0283] IOAM data is reported to a receiving entity according to an instruction of the IOAM trace type field, packet loss measurement is performed according to an instruction of the packet loss measurement field, and delay measurement is performed according to an instruction of the delay measurement field.

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

[0285] 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;

[0286] IOAM data is reported to a receiving entity according to an instruction of the IOAM trace type field, packet loss measurement is performed according to an instruction of the packet loss measurement field, and delay measurement is performed according to an instruction of the delay measurement field.

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

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

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

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

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

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

[0293] 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;

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

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

[0296] Determining the packet batch to which the traffic packet belongs according to the field value of the packet loss measurement field;

[0297] Reporting the message count value corresponding to each message batch to the receiving entity according to the message batch;

[0298] The field value of the packet loss measurement field of multiple consecutive traffic packets belonging to the same packet batch is the same, and the field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

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

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

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

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

[0303] Optionally, as shown in FIG14 , the chip 1200 may further include a memory 1220. The processor 1210 may call and execute a computer program from the memory 1220 to implement the method in the embodiment of the present application.

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

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

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

[0307] 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. For the sake of brevity, they will not be repeated here.

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

[0309] The present application also provides a computer program product comprising instructions, which, when executed by a processor, implements the following steps:

[0310] 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:

[0311] 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;

[0312] 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;

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

[0314] In one embodiment, 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.

[0315] In one embodiment, the extended flag field includes multiple bits; when the 0th bit among the multiple bits is set to the first value, an optional flow identification field exists in the indication field; when the 1st bit among the multiple bits is set to the first value, an optional message sequence identification field exists in the indication field.

[0316] In one embodiment, the optional flow identification field includes 32 bits.

[0317] In one embodiment, the optional sequence identification field includes 32 bits.

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

[0319] In one embodiment, 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 the node in the message forwarding path reports the IOAM data to the receiving entity.

[0320] In one embodiment, the IOAM trace type field includes 24 bits.

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

[0322] In one embodiment, the traffic messages belonging to the same message batch are multiple continuous traffic messages.

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

[0324] In one embodiment, 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.

[0325] In one embodiment, the packet loss measurement field includes 1 bit.

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

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

[0328] 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, where the first value and the second value are different.

[0329] In one embodiment, 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 the other traffic messages to the receiving entity.

[0330] In one embodiment, the delay measurement field includes 1 bit.

[0331] In one embodiment, the indication field further includes a namespace identification field, a flag field, and a reserved field.

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

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

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

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

[0336] The indication field is encapsulated 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 indication field is encapsulated 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.

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

[0338] Report IOAM data to a receiving entity according to the instruction of the IOAM trace type field, perform packet loss measurement according to the instruction of the packet loss measurement field, and perform delay measurement according to the instruction of the delay measurement field.

[0339] In one embodiment, the present application further provides a computer program product comprising instructions, which, when executed by a processor, implements the following steps:

[0340] 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;

[0341] Report IOAM data to a receiving entity according to the instruction of the IOAM trace type field, perform packet loss measurement according to the instruction of the packet loss measurement field, and perform delay measurement according to the instruction of the delay measurement field.

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

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

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

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

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

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

[0348] 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;

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

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

[0351] Determining the packet batch to which the traffic packet belongs according to the field value of the packet loss measurement field;

[0352] Reporting the message count value corresponding to each message batch to the receiving entity according to the message batch;

[0353] The field value of the packet loss measurement field of a plurality of consecutive traffic packets belonging to the same packet batch is the same, and the field value of the packet loss measurement field of traffic packets belonging to different packet batches is different.

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

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

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

[0357] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented 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 may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may 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).

[0358] The technical features of the above embodiments can be combined arbitrarily. 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.

[0359] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

1. A message processing method, applied to a message encapsulation node 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, wherein the indication field further comprises 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, wherein the extended flag field comprises a plurality of bits; when the 0th bit in 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. The method according to claim 3 , wherein the optional flow identification field comprises 32 bits. The method of claim 3 , wherein the optional sequence identification field comprises 32 bits.

6. The method according to any one of claims 2 to 5, wherein the extended flag field comprises 8 bits.

7. The method according to claim 1, wherein 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 the nodes in the message forwarding path report the IOAM data to the receiving entity.

8. The method according to claim 1 or 7, wherein the IOAM trace type field comprises 24 bits.

9. The method according to claim 1, wherein 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, wherein the traffic messages belonging to the same message batch are multiple continuous traffic messages.

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

12. A method according to any one of claims 1-5, 7, 9-11, wherein the packet loss measurement field is used to instruct the nodes in the packet 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 of claim 1, wherein the packet loss measurement field comprises 1 bit.

14. The method according to claim 12, wherein the encapsulation indication field for the forwarded traffic message comprises: 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, wherein the delay measurement field set to the first value is 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 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 of claim 1, wherein the latency measurement field comprises 1 bit.

17. The method according to claim 1, wherein the indication field further comprises a namespace identification field, a flag field, and a reserved field. The method of claim 17 , wherein the namespace identification field comprises 16 bits. The method of claim 17 , wherein the flag field comprises 8 bits.

20. The method of claim 17, wherein the reserved field comprises 6 bits.

21. The method according to claim 1, wherein the encapsulation indication field for the forwarded traffic message comprises: 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; or 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 of claim 1, wherein the method further comprises: The IOAM data is reported to a 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, applied to a message receiving node in a message forwarding path, the method comprising: 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 a 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, wherein the indication field further comprises an extension flag field, the method further comprising: 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, wherein the extended flag field includes a plurality of 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 comprises: 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, wherein the IOAM trace type field includes a plurality of bits, and different bits correspond to different IOAM data types, and reporting the IOAM data to the receiving entity according to an indication of the IOAM trace type field comprises: 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, wherein performing packet loss measurement according to the instruction of the packet loss measurement field comprises: 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, wherein performing delay measurement according to the indication of the delay measurement field comprises: 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, arranged at a message encapsulation node in a message forwarding path, the device comprising: A processing module, configured to encapsulate an indication field for the forwarded traffic message, wherein the indication field includes an IOAM trace type. field, packet loss measurement field, and 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; The sending module is used to send the traffic message encapsulated with the indication field.

30. A message processing device, arranged at a message receiving node 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, wherein the computer program, when executed by a processor, implements the steps of the method according to any one of claims 1 to 28.

32. A computer program product, comprising a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 28.

Citation Information

Patent Citations

  • Active stream following detection method, network equipment and communication system

    CN113079091A

  • Network performance measurement method, device and system, equipment and storage medium

    CN113765732A

  • Communication method and device

    CN114745302A

  • Stream detection method and electronic equipment

    CN115280745A

  • Scalable network path tracing

    US20210144082A1

Cited By

  • Service data packet processing system and method based on link simulation node

    CN119892730A