Packet transmission method, electronic device, and computer readable storage medium

Abstract

The present application provides a packet transmission method, an electronic device, and a computer readable storage medium. The method comprises: a first communication node sends an in-band OAM packet, wherein the in-band OAM packet comprises a data area and a data header, the data header comprises a packet specific serial number and a functional entity detection identifier, and the functional entity detection identifier is used for instructing a functional entity node on a forwarding path of the in-band OAM packet to add a functional entity data entry into the data area.

Description

Message transmission method, electronic device, and computer-readable storage medium

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is based on the Chinese patent application with application number 2023106995544 and application date of June 13, 2023, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this application as a reference. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a message transmission method, an electronic device, and a computer-readable storage medium. Background Art

[0004] A deterministic network (DetNet) is a network that can provide deterministic SLA (service-level agreement) guarantees for packet forwarding, including low upper bounds on packet loss rate, latency, and jitter. The data plane architecture of DetNet consists of a forwarding sublayer and a service sublayer. The forwarding sublayer is dedicated to traffic forwarding, while the service sublayer is dedicated to service protection. The service sublayer has currently proposed using a packet replication function (PRF), a packet elimination function (PEF), and a packet ordering function (POF) to provide service protection for deterministic service traffic. The above three functions are collectively referred to as packet replication, elimination, and ordering functions (PREOF). In the DetNet service sublayer that implements PREOF, how to collect, manage, and maintain (Operations, Administration, and Management, OAM) the location, configuration, and status information of PRF, PEP, and POF nodes is a technical problem that needs to be solved.

[0005] Summary of the Invention

[0006] Embodiments of the present application provide a message transmission method, an electronic device, and a computer-readable storage medium, which are intended to implement OAM detection of PREOF in a deterministic network.

[0007] In a first aspect, an embodiment of the present application provides a message transmission method, applied to a source node, the method comprising:

[0008] Send an associated OAM message, wherein the associated OAM message includes a data area and a data header, the data header includes a message-specific sequence number and a functional entity detection identifier, and the functional entity detection identifier is used to instruct a functional entity node on a forwarding path of the associated OAM message to add a functional entity data strip to the data area.

[0009] In a second aspect, an embodiment of the present application provides a message transmission method, applied to a functional entity node, the method comprising:

[0010] Receiving an associated OAM message, wherein the associated OAM message includes a data area and a data header, and the data header includes a message-specific sequence number and a functional entity detection identifier;

[0011] adding a functional entity data strip to the data area of ​​the associated OAM message according to the functional entity detection identifier;

[0012] The associated OAM message with the added functional entity data strip is sent to the next hop node.

[0013] In a third aspect, an embodiment of the present application provides a message transmission method, applied to a second communication node, the method comprising:

[0014] Receiving an associated OAM message, wherein the associated OAM message includes a data area and a data header, and the data header includes a message-specific sequence number and a functional entity detection identifier;

[0015] A first detection feedback message is sent, wherein the first detection feedback message includes: a flow identifier, a node identifier, a message-specific sequence number corresponding to the associated OAM message, and all functional entity data strips in the data area of ​​the associated OAM message received by the second communication node.

[0016] In a fourth aspect, an embodiment of the present application provides an electronic device, including:

[0017] one or more processors;

[0018] A memory having one or more programs stored thereon, wherein when the one or more programs are executed by the one or more processors, the one or more processors implement the message transmission method as described in the first aspect, the second aspect or the third aspect above.

[0019] In a fifth 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 message transmission method as described in the first aspect, the second aspect, or the third aspect above.

[0020] In an embodiment of the present application, an associated OAM message is sent through a first communication node. The associated OAM message includes a data area and a data header, wherein the data header includes a message-specific sequence number and a functional entity detection identifier, so that after a functional entity node in a deterministic network receives the associated OAM message, it copies, eliminates, or sorts the message according to the functional entity attributes of the node and the message-specific sequence number, and at the same time triggers the functional entity detection identifier in the message, records the relevant information of the executed function in the functional entity data strip, and adds the functional entity data strip to the data area of ​​the associated OAM message. In this way, during the end-to-end transmission of the associated OAM message, relevant functional entity data of the functional entity nodes passing along the way are collected to implement OAM detection of the PREOF of the deterministic network. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] FIG1 is a schematic diagram of an encapsulation format of a DetNet service message based on MPLS;

[0022] FIG2 is an exemplary topology diagram of a DetNet service performing PREOF protection at the service sublayer;

[0023] FIG3 is a flow chart of a message transmission method provided in an embodiment of the present application;

[0024] FIG4 is a schematic diagram of an encapsulation format of an associated OAM message provided in an embodiment of the present application;

[0025] FIG5 is a schematic diagram of an encapsulation format of a data header of a PREOF-TRACE message provided in an embodiment of the present application;

[0026] FIG6 is a flow chart of a message transmission method provided in an embodiment of the present application;

[0027] FIG7 is a flow chart of a message transmission method provided in an embodiment of the present application;

[0028] FIG8 is a schematic diagram of an application scenario of a message transmission method provided in an embodiment of the present application;

[0029] FIG9 a is a schematic diagram of PREOF-TRACE message ① in FIG8 ;

[0030] FIG9 b is a schematic diagram of PREOF-TRACE message ② in FIG8 ;

[0031] FIG9 c is a schematic diagram of PREOF-TRACE message ③ in FIG8 ;

[0032] FIG9 d is a schematic diagram of PREOF-TRACE message ④ in FIG8 ;

[0033] FIG9e is a schematic diagram of PREOF-TRACE message ⑤ in FIG8 ;

[0034] FIG9 f is a schematic diagram of PREOF-TRACE message ⑥ in FIG8 ;

[0035] FIG10 is a schematic structural diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] In order to enable those skilled in the art to better understand the technical solution of the present application, the message transmission method, electronic device and computer-readable storage medium provided in the present application are described in detail below with reference to the accompanying drawings.

[0037] Hereinafter, example embodiments will be described more fully in conjunction with the accompanying drawings, but the described example embodiments may be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Rather, these examples are provided so that this application will be thorough and complete and will fully enable those skilled in the art to understand the scope of this application.

[0038] As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items.

[0039] The terms used herein are used only to describe specific embodiments and are not intended to limit this application. As used herein, the singular forms "a," "an," and "the" are intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that when the terms "comprising" and / or "made of" are used in this specification, they specify the presence of features, wholes, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or groups thereof.

[0040] In the description of the embodiments of the present application, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it can be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments, and may be combined with each other without conflict.

[0041] In the description of the embodiments of this application, any embodiment or design scheme using "exemplary," "for example," or "for example" should not be understood as being more preferred or advantageous than other embodiments or designs. Rather, the use of words such as "exemplary," "for example," or "for example" is intended to present the relevant concepts in a concrete manner.

[0042] Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly identifying the technical features being referred to. Thus, features specified as "first" or "second" may explicitly or implicitly include one or more of such features. The terms "include," "comprising," "having," and their variations all mean "including but not limited to," unless otherwise specifically emphasized.

[0043] To facilitate understanding of the solutions of the embodiments of the present application and to provide a clear and concise description of the following embodiments, a brief introduction to the relevant technologies is first given:

[0044] (1) Deterministic Network (Detnet): A deterministic network is a network built using network resources to provide high bandwidth, low latency, low jitter, and deterministic services to meet the needs of different industries. It is mainly aimed at vertical industries such as industry, energy, and the Internet of Vehicles, which have extremely high requirements for low network latency, reliability, and stability. It is a deterministic network with differentiated services built according to the business level. Determinism is mainly reflected in the precise guarantee of network transmission indicators (bandwidth, latency, jitter, and packet loss). The quantification of these indicators can be determined based on the actual needs of the industry scenario, and determinism can be achieved by selecting appropriate deterministic network technologies based on the quantification of indicators.

[0045] (2) DetNet's data plane architecture: DetNet's data plane consists of a forwarding sublayer and a service sublayer. The forwarding sublayer is dedicated to traffic forwarding, while the service sublayer is dedicated to service protection. Deterministic network domain intermediate nodes other than terminal systems and edge nodes can be divided into relay nodes and ordinary forwarding nodes based on whether they have a service sublayer. Relay nodes have a service sublayer, while ordinary forwarding nodes do not.

[0046] (3) DetNet message encapsulation: See Figure 1, which is a schematic diagram of the encapsulation format of an MPLS-based DetNet service message. As shown in Figure 1, the MPLS-based DetNet service message includes the following fields: physical layer, data link layer, forwarding label, service label, DetNet service message control word, and DetNet service message payload.

[0047] (4) Message Replication, Elimination, and Ordering Function (PREOF): The service sublayer has proposed to use the message replication function (PRF), the message duplicate elimination function (PEF), and the out-of-order message ordering function (POF) to provide service protection for deterministic service traffic. The above three functions are collectively referred to as PREOF.

[0048] See Figure 2, which is an exemplary topology diagram of a DetNet service providing PREOF protection at the service sublayer in the related art, wherein R represents a message replication node, E represents a message copy elimination node, O represents a message sorting node, P represents a forwarding sublayer path, and G represents a service sublayer path.

[0049] At the routing node that provides the PRF functional entity for the service flow, the protected flow is copied and forwarded to different interfaces through message replication, forming a redundant flow with 1+1 (copying 1 flow) protection, or a redundant flow with 1+N (copying N flows) protection. After the message is replicated, the original flow and all redundant flows are combined into a logical composite flow, and the original flow and each redundant flow are specific member flows within the composite flow. The original flow and the redundant flow converge at the routing node that provides the PEF functional entity, but due to the different delays of different member flows, there is a sequence in the time when the message copies arrive at the PEF node. The PEF node only retains the first copy of the same message and discards the copies that arrive subsequently, thus restoring it to a single data flow. At the POF node, the disordered messages introduced by the redundant path are cached and reordered.

[0050] (5) Operation, Administration, and Maintenance (OAM): Network OAM is used for connection verification, performance measurement, fault management, performance analysis, configuration updates, and other tasks. In order to ensure deterministic transmission of services, it is necessary to establish a set of OAM mechanisms for DetNet. Its main function is to effectively improve the network's operation, management, and maintenance capabilities and ensure the stable operation of the network. Currently, DetNet can use existing IP OAM tools and MPLS OAM tools in the forwarding sublayer, but lacks available OAM tools in the service sublayer. The basic OAM requirement of the DetNet service sublayer is to locate and detect the PREOF function of the network.

[0051] The present invention provides a message transmission method, electronic device, and computer-readable storage medium, designed to implement OAM detection of PREOF in a deterministic network. Because PREOF operates on a per-flow basis, OAM messages must strictly follow the actual path of the deterministic service flow and must be able to traverse every branch of the PREOF mesh path. The present invention utilizes a path-dependent approach to collect, manage, and maintain the location, configuration, and status information of PRF, PEP, and POF nodes.

[0052] See Figure 3, which is a flow chart of a message transmission method provided in an embodiment of the present application. As shown in Figure 3, the method includes the following steps:

[0053] Step S100: The first communication node sends a channel-associated OAM message.

[0054] The associated OAM message includes a data area and a data header. The data header includes a message-specific sequence number and a functional entity detection identifier. The functional entity detection identifier is used to instruct the functional entity node on the forwarding path of the associated OAM message to add a functional entity data item to the data area.

[0055] It should be noted that the first communication node described in the embodiment of the present application may specifically be a source node that sends an associated OAM message.

[0056] It should be noted that the functional entity node described in the embodiment of the present application includes at least one of a PRF node, a PEF node or a POF node.

[0057] It should be noted that, since the associated OAM message provided in the embodiment of the present application is used for OAM detection of network PREOF, in some descriptions of the embodiment of the present application, the associated OAM message used for OAM detection of PREOF is called a PREOF-TRACE message.

[0058] In an embodiment of the present application, an encapsulation format of an associated OAM message applied to a DetNet service sublayer is provided. The encapsulation format of the associated OAM message includes the following fields: an outer encapsulation, a data header, and a data area.

[0059] It should be noted that the objects of the functions performed by the PRF, PEF, and POF functional entities are flows. Therefore, the OAM objects of the associated OAM messages in the embodiments of the present application are also flows. In the message encapsulation, the associated OAM messages need to have a flow identifier that is consistent with the format of the DetNet service message. For example, for the MPLS data plane, the associated OAM message has an S-label that is consistent with the format of the DetNet service message; for another example, for the IP data plane, the associated OAM message has the same six-tuple as the DetNet service message; when the port information cannot be obtained, a triple or a double tuple can also be used. Furthermore, in order to ensure that the associated OAM message can be treated the same as the DetNet message in the forwarding sublayer of the DetNet network node and enjoy the same routing rules, the outer encapsulation of the associated OAM message is the same as the outer encapsulation format of the DetNet service flow message. For example, on the MPLS data plane, the associated OAM message has the same physical layer, data link layer, forwarding label, and service label as the DetNet service message encapsulation format.

[0060] See Figure 4, which is a schematic diagram of the encapsulation format of an associated OAM message provided in an embodiment of the present application. As shown in Figure 4, the associated OAM message includes the following fields: physical layer, data link layer, forwarding label, service label, data header, and data area. The data header and data area replace the DetNet service message control word and DetNet service message payload in the DetNet service message shown in Figure 1.

[0061] See Figure 5, which is a schematic diagram of the encapsulation format of a data header of a PREOF-TRACE message provided in an embodiment of the present application. As shown in Figure 5, the data header includes the following fields:

[0062] (1) OAM identification code, 4 bits in length, used to distinguish OAM messages from service messages;

[0063] (2) Version, 4 bits in length, used to indicate the version number of the deterministic network ACH header;

[0064] (3) Message-specific sequence number, 8 bits long, used to indicate the sequence number. The node needs to increase the sequence number by 1 when forwarding each OAM message.

[0065] (4) Announcement type, 8 bits in length, used to indicate the type of the deterministic network association channel;

[0066] (5) Node identifier, 20 bits in length, used to identify the network node that generates the OAM message;

[0067] (6) Level, 3 bits in length, used to indicate the characteristics of dynamic path forwarding, such as the level of the OAM domain;

[0068] (7) Functional entity detection identifier (T), 1 bit in length, used to identify the PREOF-TRACE message and instruct the functional entity node on the forwarding path of the associated OAM message to add a functional entity data entry to the data area;

[0069] (8) Session, 4 bits in length, used to identify the OAM session and distinguish OAM sessions generated by the same node;

[0070] (9) OAM domain name, 20 bits in length, records the unique identifier of the OAM domain;

[0071] (10) Fragmentation, 4 bits in length, used when the PREOF-TRACE message length exceeds the forwarding plane reserved resources and must be fragmented. 1 bit for fragment identification and 3 bits for fragment sequence number.

[0072] (11) Data field length, 8 bits long, used to indicate the length of the data field of the PREOF-TRACE message;

[0073] (12) Detection option, 20 bits in length, used to define the format of the PREOF-TRACE message;

[0074] (13) Reserved for other purposes.

[0075] It should be noted that the encapsulation format of the data header of the PREOF-TRACE message shown in Figure 5 is only exemplary. In specific implementation, other fields can be added to the data header, or some non-core fields can be deleted. The order of arrangement of each field and the number of bits occupied can also be adjusted according to actual conditions.

[0076] In some examples, the data header of the associated OAM message (PREOF-TRACE message) involved in the embodiments of the present application includes an OAM identification code. The OAM identification code is a combination of several bits used to distinguish OAM messages from service messages. For example, for OAM messages, the OAM identification code combination is 0001; while for DetNet service messages, the value of the four bits of the OAM identification code field is 0000. In this way, after receiving the message, the network node can determine whether the currently received message is an OAM message or a service message based on the value of the OAM identification code field in the data header.

[0077] In some examples, the data header of the associated OAM message (PREOF-TRACE message) involved in the embodiments of the present application includes a functional entity detection identifier. The functional entity detection identifier can be a combination of several bits, which identifies the message as a PREOF-TRACE message by taking a specific bit value, and then instructs the functional entity node on the forwarding path of the associated OAM message to add a functional entity data strip to the data area. The T field in the example of Figure 5 is the functional entity detection identifier, which contains 1 bit and identifies the PREOF-TRACE message by setting the value of the T bit. For example, when the value of the T field in the message is 1, it indicates that the message is a PREOF-TRACE message; when the value of the T field in the message is 0, it indicates that the message is a message other than PREOF-TRACE. In this way, after receiving the message, the network node can determine whether the currently received message is a PREOF-TRACE message based on the value of the T field in the data header. According to an embodiment of the present application, for a PRF node, a PEF node or a POF node, when the received message is a PREOF-TRACE message, while executing the PREOF function corresponding to this node, it is also necessary to add a functional entity data strip to the data area of ​​the message.

[0078] In some examples, the data header of the associated OAM message (PREOF-TRACE message) involved in the embodiments of the present application includes a detection option field, which is used to indicate the information items that the functional entity data strip added to the data area by the functional entity node must include through a value.

[0079] In some examples, the information items included in the functional entity data strip include at least one of the following:

[0080] (1) The functional entity identifier, which is used to indicate the functional entity node of the adding subject of the functional entity data strip. Each functional entity node has a unique functional entity identifier;

[0081] (2) Attributes of a functional entity, which are used to indicate the attributes of a functional entity node. The attributes of a functional entity node include: PRF, PEF, or POF attributes;

[0082] (3) The identifier of the router node where the functional entity is located. Each router node has a unique routing node identifier;

[0083] (4) The timestamp when the functional entity processes the message, for example, the timestamp when the PRF functional node copies the message, the timestamp when the PEF executes the message deletion operation, and the timestamp when the POF node adds the message to the dedicated reordering buffer queue;

[0084] (5) The number of copies of the message, indicating the number of copies of the message made by the PRF function node;

[0085] (6) The length of the dedicated reordering buffer queue, which indicates the length of the dedicated reordering buffer queue in the POF node after adding the current message;

[0086] (7) Interface identifier of the node where the message flows in, indicating the interface of the routing node that receives the current message. It can be identified by a physical interface address, a sub-interface address, or a virtual interface address.

[0087] (8) The interface identifier of the message outflow node, which indicates the physical interface address of the routing node pointing to the next hop of the message. It can be identified by the physical interface address, sub-interface address, or virtual interface address;

[0088] (9) The time slot number or cycle number of the node from which the message leaves. When the routing node forwards messages by time slot or by cycle at the interface, the time slot number or cycle number assigned to the message during scheduling and forwarding.

[0089] (10) The queue number of the node where the message flows out. When a multi-queue forwarding mechanism is used for the message, the number of the sending queue assigned by the routing node when scheduling the forwarding of the current message.

[0090] In some examples, the detection option field can be a combination of several bits, where each bit corresponds to an information item, and the value of the bit indicates the information item that the functional entity data strip needs to include. For example, if the value of the information item corresponding to the x-th bit in the detection option field is 1, it means that the functional entity data strip needs to include the information item corresponding to the bit. In the encapsulation format of the data header of the PREOF-TRACE message shown in Figure 5, the detection option field contains 20 bits, and the meaning of each bit is as follows:

[0091] bit0: The functional entity data strip records the identifier of the PREOF functional entity;

[0092] bit1: The functional entity data strip records the attributes of the PREOF functional entity (PRF / PEF / POF);

[0093] bit2: The functional entity data entry records the identifier of the router node where the PREOF functional entity is located;

[0094] Bit3: The functional entity data strip records the timestamp of the PRF / PEF / POF processing performed by the service sublayer functional entity on the message;

[0095] Bit4: The functional entity data entry records the number of times the PRF functional entity copies the message;

[0096] Bit 5: The functional entity data strip records the length of the OAM message buffer queue at the time it enters the dedicated reordering buffer;

[0097] Bit 6: The functional entity data entry records the interface identifier of the node into which the message flows;

[0098] bit7: The functional entity data entry records the interface identifier of the node where the message flows out;

[0099] bit8: The functional entity data strip records the timeslot number or cycle number of the node where the message flows out;

[0100] bit9: The functional entity data entry records the queue number of the node where the message flows out;

[0101] Bit 10 to bit 19: Reserved and can be expanded as needed.

[0102] In some examples, the first communication node obtains a message-specific sequence number of a previous PREOF-TRACE message, adds 1 to the message-specific sequence number of the previous PREOF-TRACE message, and obtains a message-specific sequence number of a current PREOF-TRACE message.

[0103] In some examples, the message-specific sequence number has the following functions: (1) For PRF and PEF nodes, the number of message copies is determined based on the message-specific sequence number; (2) For POF nodes, the messages are reordered based on the message-specific sequence number.

[0104] In some examples, the data header of the associated OAM message (PREOF-TRACE message) involved in the embodiments of the present application includes a message-specific sequence number including a domain code and a sequence code. The domain code is used to identify the OAM domain from which the associated OAM message originates, and the sequence code has a unique corresponding relationship with the associated OAM message within the OAM domain.

[0105] In some examples, the message transmission method of the embodiment of the present application further includes the following steps:

[0106] S110, the first communication node receives a first detection feedback message sent by the second communication node, wherein the first detection feedback message includes: a flow identifier, a node identifier, a message-specific sequence number corresponding to the associated OAM message, and all functional entity data strips in the data area of ​​the associated OAM message received by the second communication node.

[0107] It should be noted that the second communication node described in the embodiment of the present application may specifically be a destination node of the associated OAM message, and the destination node includes a destination relay node or an OAM domain tail node.

[0108] In some examples, when a PREOF-TRACE message arrives at a destination relay node or an OAM domain tail node (herein, the destination relay node or the OAM domain tail node may be referred to as a second communication node), the second communication node generates a first detection feedback message including PREOF function entity data collected along the PREOF-TRACE message, and sends the first detection feedback message to the first communication node. Because the first detection feedback message feeds back PREOF function entity data, in some descriptions of the embodiments of the present application, the first detection feedback message is referred to as a first PREOF-RESPONCE message.

[0109] In some examples, the first PREOF-RESPONCE message carries the following data: (1) the same flow identifier, node identifier, and message-specific sequence number as the PREOF-TRACE message; and (2) all functional entity data items in the PREOF-TRACE message data area.

[0110] In some examples, the first PREOF-RESPONCE message may be sent to the first communication node out-of-band.

[0111] In some examples, the message transmission method of the embodiment of the present application further includes the following steps:

[0112] S120, the first communication node receives a second detection feedback message sent by a message elimination function PEF node in a forwarding path of the associated OAM message, wherein the second detection feedback message includes: a flow identifier, a node identifier, a message-specific sequence number of the associated OAM message, all functional entity data strips in a data area of ​​the associated OAM message received by the PEF node, and the number of copies of the associated OAM message received by the PEF node.

[0113] In some examples, when a PREOF-TRACE message arrives at a PEF node, and the PEF node has previously received a PREOF-TRACE message with the same message-specific sequence number as the current PREOF-TRACE message and then performs an operation to eliminate redundant message copies, the PEF node further generates a second detection feedback message including PREOF functional entity data collected along the way by the current PREOF-TRACE message, and sends the second detection feedback message to the first communication node. Because the second detection feedback message feeds back PREOF functional entity data, in some descriptions of the embodiments of the present application, the second detection feedback message is referred to as a second PREOF-RESPONCE message.

[0114] In some examples, the second PREOF-RESPONCE message carries the following data: (1) the same flow identifier, node identifier, and message-specific sequence number as the PREOF-TRACE message; (2) all functional entity data items in the PREOF-TRACE message data area; and (3) the number of PREOF-TRACE message copies received by the PEF node.

[0115] In some examples, the second PREOF-RESPONCE message may be sent to the first communication node out-of-band.

[0116] Please refer to Figure 6, which is a flow chart of a message transmission method provided in an embodiment of the present application. As shown in Figure 6, the message transmission method includes the following steps:

[0117] S210, the functional entity node receives an associated OAM message, wherein the associated OAM message includes a data area and a data header, and the data header includes a message-specific sequence number and a functional entity detection identifier;

[0118] S220, the functional entity node adds a functional entity data entry to the data area of ​​the associated OAM message according to the functional entity detection identifier;

[0119] S230, the functional entity node sends the associated OAM message with the functional entity data strip added thereto to the next hop node.

[0120] In some examples, the functional entity data strip includes at least one of the following information items: the identifier of the functional entity, the attributes of the functional entity, the identifier of the router node where the functional entity is located, the timestamp of the functional entity processing the message, the number of copies of the message, the length of the reordering dedicated cache queue, the interface identifier of the message flowing into the node, the interface identifier of the message flowing out of the node, the time slot number or cycle number of the message flowing out of the node, or the queue number of the message flowing out of the node.

[0121] In some examples, the data header of the associated OAM message further includes a detection option field, and the information items included in the functional entity data strip are determined by the value of the detection option field.

[0122] In some examples, the message-specific sequence number includes a domain code and a sequence code. The domain code is used to identify the OAM domain from which the associated OAM message originates, and the sequence code has a unique corresponding relationship with the associated OAM message within the OAM domain.

[0123] In an exemplary embodiment of the present application, the functional entity node is a message replication function (PRF) node, and the associated OAM message has multiple corresponding next-hop nodes in the PRF node.

[0124] When the functional entity node is a message replication function (PRF) node, in step S220, adding a functional entity data entry to the data area of ​​the associated OAM message specifically includes the following steps:

[0125] S310, the PRF node copies the associated OAM message to obtain multiple associated OAM message copies, where each associated OAM message copy corresponds to a next hop node;

[0126] S320: The PRF node adds a corresponding PRF function entity data entry in the data area of ​​each associated OAM message copy.

[0127] When the functional entity node is a message replication function (PRF) node, in step S230, the associated OAM message with the functional entity data strip added thereto is sent to the next hop node, which specifically includes the following steps:

[0128] S330: Send each associated OAM message copy after adding the PRF function entity data strip to the corresponding next hop node.

[0129] In some examples, when an associated OAM message (PREOF-TRACE message) arrives at a PRF node, the PREOF-TRACE message has N (N>1) next-hop nodes corresponding to different forwarding paths. Therefore, the PRF node needs to copy the PREOF-TRACE message to obtain N PREOF-TRACE message copies, and then forward each PREOF-TRACE message copy to the corresponding next-hop node.

[0130] In an embodiment of the present application, before each PREOF-TRACE message copy is forwarded to the corresponding next-hop node, a corresponding PRF function entity data strip is first added to the data area of ​​each PREOF-TRACE message copy. In some examples, the PRF function entity data strip added by the PRF node to the PREOF-TRACE message copy includes at least one of the following information items: a functional entity identifier of the PRF node, a PRF attribute identifier, a node identifier of the PRF node, a timestamp of the PRF node processing the message, the number of message copies, an interface identifier of the message flowing into the PRF node, an interface identifier of the message flowing out of the PRF node, a time slot number or cycle number of the message flowing out of the PRF node, and a queue number of the message flowing out of the PRF node.

[0131] In some examples, the data header of an associated OAM message received by a PRF node also includes a detection option field, and the information items included in the PRF function entity data strip are determined by the value of the detection option field. Continuing with the previous example, the detection option field in the data header of the associated OAM message includes multiple bits, each bit corresponding to one information item. The PRF node determines whether the PRF function entity data strip needs to include the corresponding information item based on the value of each bit.

[0132] In an exemplary embodiment of the present application, the functional entity node is a message elimination function (PEF) node. When the functional entity node is a PEF node, in step S220, adding a functional entity data strip to the data area of ​​the associated OAM message specifically includes the following steps:

[0133] S410: The PEF node counts the number of received copies of the same associated OAM message according to the message-specific sequence number.

[0134] S420 , when the number of copies is equal to 1, the PEF node adds a PEF function entity data entry to the data area of ​​the associated OAM message.

[0135] When the functional entity node is a PEF node, in step S230, the associated OAM message with the functional entity data strip added thereto is sent to the next hop node, including:

[0136] S430: The PEF node sends the associated OAM message with the PEF function entity data strip added thereto to the next hop node.

[0137] In some examples, each time a PEF node receives an associated OAM message (PREOF-TRACE message), it counts the PREOF-TRACE messages according to the message-specific sequence number to record the number of PREOF-TRACE messages received by the node with the same message-specific sequence number.

[0138] The number of PREOF-TRACE messages (i.e., the number of copies). If the count value of the currently received PREOF-TRACE message by the PEF node is 1, it means that no message with the same message-specific sequence number as the currently received PREOF-TRACE message has been received before. In this case, the PEF node adds a PEF functional entity data item to the data area of ​​the PREOF-TRACE message.

[0139] In some examples, the PEF functional entity data strip includes at least one of the following information items: a functional entity identifier of the PEF node, a PEF attribute identifier, a node identifier of the PEF node, a timestamp of the PEF node processing the message, an interface identifier of the message flowing into the PEF node, an interface identifier of the message flowing out of the PEF node, a time slot number or cycle number of the message flowing out of the PEF node, and a queue number of the message flowing out of the PEF node.

[0140] When the functional entity node is a PEF node, the message transmission method in the embodiment of the present application further includes the following steps:

[0141] S440, when the number of copies is greater than 1, the PEF node sends a second detection feedback message to the first communication node; wherein the second detection feedback message includes: the flow identifier of the associated OAM message, the node identifier, the message-specific sequence number, all functional entity data strips in the data area of ​​the associated OAM message received by the PEF node, and the number of copies of the associated OAM message received by the PEF node.

[0142] In some examples, when the number of copies is greater than 1, the message transmission method of the embodiment of the present application further includes the following steps:

[0143] S450: The PEF node deletes the currently received channel-associated OAM message.

[0144] When the PREOF-TRACE message arrives at the PEF node, and the PEF node has previously received a PREOF-TRACE message with the same message-specific sequence number as the current PREOF-TRACE message, the PEF node needs to eliminate the redundant message copies. In addition, the PEF node also generates a second detection feedback message (second PREOF-RESPONCE message) containing the PREOF functional entity data collected along the way of the current PREOF-TRACE message, and sends the second detection feedback message to the first communication node.

[0145] In some examples, the second PREOF-RESPONCE message carries the following data: (1) the same flow identifier, node identifier, and message-specific sequence number as the PREOF-TRACE message; (2) all functional entity data items in the PREOF-TRACE message data area; and (3) the number of PREOF-TRACE message copies received by the PEF node.

[0146] In some examples, the PEF node may send the second PREOF-RESPONCE message to the first communication node in an out-of-band manner.

[0147] In an exemplary embodiment of the present application, the functional entity node is a message sorting function POF node. When the functional entity node is a POF node, in step S220, adding a functional entity data strip to the data area of ​​the associated OAM message specifically includes the following steps:

[0148] S510, adding a POF function entity data strip to the data area of ​​the associated OAM message;

[0149] S520: Send the associated OAM message with the POF function entity data strip added thereto to the next hop node.

[0150] In some examples, when the functional entity node is a POF node, the message transmission method of the embodiment of the present application further includes the following steps:

[0151] S530, adding the currently received associated OAM message to the reordering dedicated buffer queue;

[0152] S540 , sort the associated OAM messages in the dedicated reordering buffer queue according to the message-specific sequence numbers in the associated OAM messages.

[0153] When the associated OAM message (PREOF-TRACE message) arrives at the POF node, the POF node adds the PREOF-TRACE message to the reordering dedicated cache queue. Each message in the reordering dedicated cache queue has its own corresponding message-specific sequence number. Therefore, the POF node determines the sorting position of the current PREOF-TRACE message in the reordering dedicated cache queue based on the message-specific sequence number in the data header of the current PREOF-TRACE message, and caches the current PREOF-TRACE message at the corresponding sorting position waiting to be dequeued.

[0154] The POF node records the relevant information for sorting the current PREOF-TRACE message in the POF functional entity data strip. Specifically, the POF functional entity data strip includes at least one of the following information items: the functional entity identifier of the POF node, the POF attribute identifier, the node identifier of the POF node, the timestamp of the POF node processing the message, the queue length when the message enters the reordering dedicated buffer queue, the interface identifier of the message flowing into the POF node, the interface identifier of the message flowing out of the POF node, the time slot number or cycle number of the message flowing out of the POF node, and the queue number of the message flowing out of the POF node.

[0155] Please refer to Figure 7, which is a flow chart of a message transmission method provided in an embodiment of the present application. As shown in Figure 7, the message transmission method includes the following steps:

[0156] S610, the second communication node receives an associated OAM message, wherein the associated OAM message includes a data area and a data header, and the data header includes a message-specific sequence number and a functional entity detection identifier;

[0157] S620, the second communication node sends a first detection feedback message, wherein the first detection feedback message includes: the flow identifier, node identifier, message-specific sequence number corresponding to the associated OAM message, and all functional entity data strips in the data area of ​​the associated OAM message received by the second communication node.

[0158] In some examples, the second communication node is a destination node that receives the associated OAM message.

[0159] In some examples, the data area includes at least one functional entity data stripe, each functional entity data stripe is one of the following: a message copy function PRF functional entity data stripe, a message deletion function PEF functional entity data stripe, or a message sorting function POF functional entity data stripe.

[0160] In some examples, the data header of the associated OAM message further includes a detection option field, and the detection option field is used to indicate, by taking a value, information items that the functional entity data strip needs to include.

[0161] In some examples, the information items include at least one of the following: an identifier of the functional entity, an attribute of the functional entity, an identifier of the router node where the functional entity is located, a timestamp of the functional entity processing the message, the number of message copies, the length of the reordering dedicated cache queue, the interface identifier of the message inflow node, the interface identifier of the message outflow node, the time slot number or cycle number of the message outflow node, or the queue number of the message outflow node.

[0162] In some examples, the message-specific sequence number includes a domain code and a sequence code. The domain code is used to identify the OAM domain from which the associated OAM message originates, and the sequence code has a unique corresponding relationship with the associated OAM message within the OAM domain.

[0163] In some examples, the second communication node includes a destination relay node or an OAM domain tail node. When the PREOF-TRACE message arrives at the destination relay node or the OAM domain tail node, the destination relay node or the OAM domain tail node generates a message containing

[0164] The first detection feedback message (first PREOF-RESPONCE message) of the PREOF function entity data collected along the PREOF-TRACE message is sent to the first communication node. Since the first detection feedback message feeds back the PREOF function entity data,

[0165] In some examples, the first PREOF-RESPONCE message carries the following data: (1) the same flow identifier, node identifier, and message-specific sequence number as the PREOF-TRACE message; and (2) all functional entity data items in the PREOF-TRACE message data area.

[0166] In some examples, the second communication node may send the first PREOF-RESPONCE message to the first communication node out-of-band.

[0167] It should be noted that in the above embodiments, the description of each embodiment has its own focus. For parts that are not detailed or recorded in a certain embodiment, reference can be made to the relevant description of other embodiments.

[0168] Please refer to Figure 8, which is a schematic diagram of an application scenario of a message transmission method provided in an embodiment of the present application. The scenario shown in Figure 8 is a DetNet MPLS network, which includes the following nodes: a source node (R1) of an edge node, a destination node (R6) of an edge node, relay nodes (R2-R5) that run both the DetNet service sublayer and the forwarding sublayer, and ordinary relay nodes (P1-P8) that only run the DetNet forwarding sublayer. For service flow A that requires deterministic forwarding provided by DetNet, this method is used to perform OAM on the PREOF function at the service sublayer, enter the MPLS network from the R1 node, and reach the R6 node.

[0169] The following describes in detail the message transmission method provided in the embodiment of the present application in conjunction with the scenario shown in FIG8 .

[0170] (1) Source node R1 sends a PREOF-TRACE message ①, which is transplanted from the real message of the service flow, so that the forwarding behavior of the DetNet forwarding sublayer for the PREOF-TRACE message is equivalent to the real service message. As shown in Figure 8, the PREOF-TRACE message ① includes the following fields: forwarding label (F-label), service label (S-label), data header (PREOF-TRACE header), wherein the PREOF-TRACE header specifically includes the following fields: OAM identification code, message-specific sequence number, node identifier, functional entity detection identifier (T), and detection option (TRACE option). The information content corresponding to each of the above fields is shown in Figure 9a.

[0171] It should be noted that the PREOF-TRACE message ① also carries a data area, which is to be filled with relevant functional entity data strips by subsequent functional entity nodes.

[0172] (2) The relay node R2 is a PRF node with a service sublayer. The corresponding functional entity identifier is PRF-A-1, the functional entity attribute is PRF, and the router node identifier is R2.

[0173] Node PRF-A-1 (i.e., node R2) receives PREOF-TRACE message ① from source node R1. Based on the OAM identifier in the data header (PREOF-TRACE header), it determines that the message is an OAM message. Based on the functional entity detection identifier (T) in the PREOF-TRACE header, it also determines that the message is a PREOF-TRACE message. Based on the destination address of PREOF-TRACE message ①, node R2 determines that PREOF-TRACE message ① has two next-hop nodes, P1 and P2, at its local node. It then replicates PREOF-TRACE message ①, obtaining two copies of the PREOF-TRACE message for next-hop nodes P1 and P2, which are recorded as PREOF-TRACE message ② and PREOF-TRACE message ③, respectively.

[0174] As shown in Figure 9b, for PREOF-TRACE message ②, the PRF-A-1 node replaces its forwarding label (F-lable) with "toP1", indicating that it is forwarded to the P1 node; the service label remains unchanged; a PRF-A-1 functional entity data strip is added to the data area, and the PRF-A-1 node determines which information items need to be recorded in the PRF-A-1 functional entity data strip according to the value of the TRACE option in the PREOF-TRACE header, and then adds the corresponding information item content to the PRF-A-1 functional entity data strip. As shown in Figure 8, the PRF-A-1 functional entity data strip of PREOF-TRACE message ② includes the following information items: the identifier of the functional entity (PRF-A-1), the attribute of the functional entity (PRF), the identifier of the router node where the functional entity is located (R2), the timestamp of the functional entity processing the message (PRF processing timestamp), the number of copies of the message (2), the length of the reordering dedicated cache queue (Null), and the interface identifier of the node where the message flows into (ingress-int of R2 from R1), the interface identifier of the message's egress node (egress-int of R2 to P1), the timeslot ID of the message's egress node (timeslot id of egress-int), and the queue ID of the message's egress node (queue id in ingress-int). It should be noted that if the PREOF-TRACE message header has a data length field, the value of the data length field must also be updated.

[0175] As shown in Figure 9c, for PREOF-TRACE message ③, the PRF-A-1 node replaces its forwarding label (F-lable) with "toP2", indicating that it is forwarded to the P2 node; the service label remains unchanged; a PRF-A-1 functional entity data strip is added to the data area, and the PRF-A-1 node determines which information items need to be recorded in the PRF-A-1 functional entity data strip according to the value of the TRACE option in the PREOF-TRACE header, and then adds the corresponding information item content to the PRF-A-1 functional entity data strip. As shown in Figure 9c, the PRF-A-1 functional entity data strip of PREOF-TRACE message ③ includes the following information items: the identifier of the functional entity (PRF-A-1), the attribute of the functional entity (PRF), the identifier of the router node where the functional entity is located (R2), the timestamp of the functional entity processing the message (PRF processing timestamp), the number of copies of the message (2), the length of the reordering dedicated cache queue (Null), and the interface identifier of the node into which the message flows (ingress-int of R2 from R1), the interface identifier of the message's egress node (egress-int of R2 to P2), the timeslot ID of the message's egress node (timeslot id of egress-int), and the queue ID of the message's egress node (queue id in ingress-int). If the PREOF-TRACE message header has a data length field, the value of the data length field must also be updated.

[0176] (3) The relay node R3 is a PEF node with a service sublayer. The corresponding functional entity identifier is PEF-A-1, the functional entity attribute is PEF, and the router node identifier is R3.

[0177] Assume that PEF-A-1 (i.e., R3) first receives a PREOF-TRACE message from P3. It then counts the number of PREOF-TRACE messages received by PEF-A-1 based on the message-specific sequence number (00100001) in the message. The current count for the message-specific sequence number (00100001) is 1, indicating that this PREOF-TRACE message is the first PREOF-TRACE message copy received by PEF-A-1 with the message-specific sequence number 00100001. Based on this first PREOF-TRACE message copy, PEF-A-1 generates a PREOF-TRACE message (4) and sends it to the next-hop node, R4.

[0178] The generation process of the PREOF-TRACE message ④ is as follows: the PEF-A-1 node replaces the forwarding label (F-lable) in the PREOF-TRACE message received from the P3 node with "toR4", indicating that it is forwarded to the R4 node; the service label remains unchanged; a PEF-A-1 functional entity data strip is added to the data area, and the PEF-A-1 node determines which information items need to be recorded in the PEF-A-1 functional entity data strip according to the value of the TRACE option in the PEEOF-TRACE header, and then adds the corresponding information item content to the PEF-A-1 functional entity data strip. As shown in Figure 9d, the PEF-A-1 functional entity data strip of the PEEOF-TRACE message ④ includes the following information items: the identifier of the functional entity (PEF-A-1), the attributes of the functional entity (PEF), the identifier of the router node where the functional entity is located (R3), and the timestamp of the functional entity processing the message (PEF processing timestamp), number of message copies (Null), length of the dedicated reordering buffer queue (Null), interface identifier of the node from which the message flows in (ingress-int of R3 from P3), interface identifier of the node from which the message flows out (engress-int of R3 to R4), timeslot ID of the node from which the message flows out (timeslot id of engress-int), and queue ID of the node from which the message flows out (queue id in ingress-int). It should be noted that if the PREOF-TRACE message header has a data length field, the value of the data length field must also be updated.

[0179] The PEF-A-1 node receives the PREOF-TRACE message sent by the P4 node, and then counts according to the message-specific sequence number (00100001) in the PREOF-TRACE message. The current count of the PEF-A-1 node for the message-specific sequence number (00100001) is 2, indicating that the PREOF-TRACE message is a copy of the second PREOF-TRACE message received by the PEF-A-1 node, whose message-specific sequence number is 00100001. The PEF-A-1 node sends a second detection feedback message (a second PREOF-RESPONCE message) to the source node R0; wherein the second PREOF-RESPONCE message includes: the flow identifier (flow A) of the PREOF-TRACE message, the node identifier (R3), all functional entity data strips in the data area of ​​the PREOF-TRACE message, and the number of copies of the PREOF-TRACE message (2).

[0180] (4) The relay node R5 is a P0F node with a service sublayer. The corresponding functional entity identifier is P0F-A-1, the functional entity attribute is P0F, and the router node identifier is R5.

[0181] Node P0F-A-1 (i.e., node R5) receives PREOF-TRACE message ⑤ from previous-hop node P8. As shown in Figure 9e, PREOF-TRACE message ⑤ contains the PRF-A-1 functional entity data strip, the PEF-A-1 functional entity data strip, and the PEF-A-2 functional entity data strip. Based on PREOF-TRACE message ⑤, node P0F-A-1 generates PREOF-TRACE message ⑥, which is sent to destination node R10. Node POF-A-1 replaces the forwarding label (F-label) in PREOF-TRACE message ⑤ with "to R6," indicating forwarding to node R6. The service label remains unchanged. Node POF-A-1 functional entity data strip is added to the data area. Based on the value of the TRACE option in the PEOF-TRACE header, node POF-A-1 determines which information items to record in the POF-A-1 functional entity data strip and then adds the corresponding information items to the POF-A-1 functional entity data strip. As shown in Figure 9f, the POF-A-1 functional entity data entry includes the following information items: functional entity identifier (POF-A-1), functional entity attributes (POF), identifier of the router node where the functional entity resides (R5), timestamp of the functional entity processing the message (POF processing timestamp), number of message copies (Null), length of the dedicated reordering buffer queue (odering buffer length), interface identifier of the message inflow node (ingress-int of R5 from P8), interface identifier of the message outflow node (egress-int of R5 to R6), timeslot ID of the message outflow node (timeslot id of egress-int), and queue ID of the message outflow node (queue id in ingress-int). It should be noted that if the PREOF-TRACE message header has a data length field, the value of the data length field must also be updated.

[0182] The P0F-A-1 node adds the PREOF-TRACE message ⑥ to the reordering dedicated buffer queue, which determines the sorting position in the queue according to the message dedicated sequence number of the PREOF-TRACE message ⑥.

[0183] (5) The destination node R6 receives the PREOF-TRACE message ⑥ from the previous hop node R5, and then sends a first detection feedback message (first PREOF-RESPONCE message) to the source node R1. The first PREOF-RESPONCE message includes: the flow identifier (flow A) of the PREOF-TRACE message ⑥, the node identifier (R6), and all functional entity data items in the data area of ​​the PREOF-TRACE message ⑥.

[0184] According to the embodiment of the present application, the OAM tool of the DetNet service sublayer can be obtained for the discovery and collection of the actual status of the service protection function. Since PREOF is performed on a flow basis, the OAM message needs to strictly follow the actual path of the deterministic service flow. The embodiment of the present application adopts an on-path mode (IOAM) to collect the location, configuration and status information of the PRF, PEP, and POF nodes, which can ensure that the path of the OAM message and the service message are exactly the same. Moreover, compared with the IOAM detection of general MPLS / IP data streams, the on-path OAM message involved in the embodiment of the present application is the OAM message of the DetNet service sublayer, which needs to be copied, eliminated and reordered, so that the OAM message traverses every branch in the PREOF mesh path. The path passed by the on-path OAM message involved in the embodiment of the present application has the characteristics of DetNet. The on-path OAM message and the service message share the same path, not only the link interface is the same, but also the time slot or queue number needs to be the same. Furthermore, compared to the end-to-end IOAM detection model used for typical MPLS / IP data flows, this embodiment of the present application utilizes an end-to-multi-end model because the PEF node also returns a PREOF-RESPONCE when eliminating duplicates. The PREOF data collected by this embodiment of the present application can provide a basis for performance analysis (e.g., service sublayer latency analysis) and performance optimization (e.g., optimization of redundant paths) of the DetNet service sublayer.

[0185] FIG10 shows an electronic device provided in an embodiment of the present application. The electronic device 900 includes but is not limited to:

[0186] at least one processor 910;

[0187] at least one memory 920, for storing at least one program;

[0188] When at least one program is executed by at least one processor 910, the message transmission method described in any of the above embodiments is executed.

[0189] It should be understood that the processor 910 and the memory 920 may be connected via a bus or other means.

[0190] It should be understood that the processor 910 can be a central processing unit (CPU). The processor can also be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. Alternatively, the processor 910 uses one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiments of the present application.

[0191] Memory 920, as a non-transitory computer-readable storage medium, can be used to store non-transitory software programs and non-transitory computer executable programs, such as the message transmission method described in any embodiment of this application. Processor 910 implements the above-described message transmission method by executing the non-transitory software program and instructions stored in memory 920.

[0192] The memory 920 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store and execute the above-mentioned message transmission method. In addition, the memory 920 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 920 may optionally include a memory remotely arranged relative to the processor 910, and these remote memories may be connected to the processor 910 via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0193] The non-transient software programs and instructions required to implement the above-mentioned message transmission method are stored in the memory 920. When executed by one or more processors 910, the message transmission method provided by any embodiment of the present application is executed.

[0194] An embodiment of the present application also provides a computer-readable storage medium, which stores a program executable by a processor. When the program executable by the processor is executed by the processor, it is used to implement the message transmission method described in any of the above embodiments.

[0195] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media.Computer-readable media can be computer-readable signal media or computer-readable storage media.Computer-readable storage media can be, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or components, or any combination thereof.More specific examples (non-exhaustive list) of computer-readable storage media include: electrical connections with one or more wires, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination thereof.In this document, computer-readable storage media can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0196] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, which carries computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0197] Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

[0198] Computer program code for performing the operations of the present application can be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code can be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (such as through the Internet using an Internet service provider).

[0199] The above is a specific description of several implementations of the present application, but the present application is not limited to the above-mentioned implementation methods. Technical personnel familiar with the art can also make various equivalent modifications or substitutions without violating the shared conditions of the scope of the present application. These equivalent modifications or substitutions are all included in the scope defined by the present application.

Claims

1. A message transmission method, applied to a first communication node, the method comprising: Send an associated OAM message, wherein the associated OAM message includes a data area and a data header, the data header includes a message-specific sequence number and a functional entity detection identifier, and the functional entity detection identifier is used to instruct a functional entity node on a forwarding path of the associated OAM message to add a functional entity data strip to the data area.

2. The method according to claim 1, wherein: The data header of the associated OAM message further includes a detection option field, and the detection option field is used to indicate, by taking a value, information items that the functional entity data strip added by the functional entity node to the data area should contain.

3. The method according to claim 2, wherein: The information items include at least one of the following: an identifier of a functional entity, an attribute of a functional entity, an identifier of a router node where the functional entity is located, a timestamp of a message processed by the functional entity, the number of message copies, the length of a dedicated reordering cache queue, an interface identifier of a message inflow node, an interface identifier of a message outflow node, a time slot number or a cycle number of a message outflow node, or a queue number of a message outflow node.

4. The method according to claim 1, further comprising: Receive a first detection feedback message sent by a second communication node, wherein the first detection feedback message includes: The flow identifier, the node identifier, the message-specific sequence number corresponding to the associated OAM message, and all functional entity data strips in the data area of ​​the associated OAM message received by the second communication node.

5. The method according to claim 1, further comprising: Receive a second detection feedback message sent by a message elimination function PEF node in the forwarding path of the associated OAM message, wherein the second detection feedback message includes: the flow identifier of the associated OAM message, the node identifier, the message-specific sequence number, all functional entity data strips in the data area of ​​the associated OAM message received by the PEF node, and the number of copies of the associated OAM message received by the PEF node.

6. The method according to claim 1, wherein: The message-specific sequence number includes a domain code and a sequence code, the domain code is used to identify the OAM domain from which the associated OAM message originates, and the sequence code has a unique corresponding relationship with the associated OAM message in the OAM domain.

7. The method according to claim 1, wherein: The functional entity node includes a message replication function PRF node, a PEF node, or a message sorting function POF node.

8. A message transmission method, applied to a functional entity node, the method comprising: Receiving an associated OAM message, wherein the associated OAM message includes a data area and a data header, and the data header includes a message-specific sequence number and a functional entity detection identifier; According to the functional entity detection identifier, adding a functional entity data strip in the data area of ​​the associated OAM message; The associated OAM message with the added functional entity data strip is sent to the next hop node.

9. The method according to claim 8, wherein: The functional entity node is a message replication function PRF node, the associated OAM message has multiple corresponding next hop nodes in the PRF node, and adding a functional entity data strip in the data area of ​​the associated OAM message includes: The associated OAM message is copied to obtain a plurality of associated OAM message copies, wherein each associated OAM message copy corresponds to one of the next hop nodes; For each of the associated OAM message copies, adding a corresponding PRF function entity data strip in the data area of ​​the associated OAM message copy; The sending of the associated OAM message to the next hop node after adding the functional entity data strip includes: Each of the associated OAM message copies after adding the PRF function entity data strip is sent to the corresponding next hop node.

10. The method according to claim 8, wherein: The functional entity node is a message elimination function PEF node, and the adding of a functional entity data strip in the data area of ​​the associated OAM message includes: Counting the number of received copies of the same associated OAM message according to the message-specific sequence number; When the number of copies is equal to 1, a PEF function is added to the data area of ​​the associated OAM message. Volume data bar; The sending of the associated OAM message to the next hop node after adding the functional entity data strip includes: The associated OAM message with the PEF function entity data strip added thereto is sent to the next hop node.

11. The method according to claim 10, further comprising: When the number of copies is greater than 1, sending a second detection feedback message to the first communication node; The second detection feedback message includes: the flow identifier of the associated OAM message, the node identifier, the message-specific sequence number, all functional entity data strips in the data area of ​​the associated OAM message received by the PEF node, and the number of copies of the associated OAM message received by the PEF node.

12. The method according to claim 11, wherein: When the number of copies is greater than 1, the method further includes: eliminating the currently received associated OAM message.

13. The method according to claim 8, wherein: The functional entity node is a message sorting function POF node, and the adding of a functional entity data strip in the data area of ​​the associated OAM message includes: Adding a POF function entity data strip in the data area of ​​the associated OAM message; The associated OAM message after adding the POF function entity data strip is sent to the next hop node.

14. The method according to claim 13, further comprising: Adding the currently received associated OAM message to the reordering dedicated buffer queue; The associated OAM messages in the dedicated reordering buffer queue are sorted according to the message-specific sequence numbers in the associated OAM messages.

15. The method according to claim 8, wherein: The functional entity data strip includes at least one of the following information items: the identifier of the functional entity, the attributes of the functional entity, the identifier of the router node where the functional entity is located, the timestamp of the functional entity processing the message, the number of message copies, the length of the reordering dedicated cache queue, the interface identifier of the message inflow node, the interface identifier of the message outflow node, the time slot number or cycle number of the message outflow node, or the queue number of the message outflow node.

16. The method according to claim 8, wherein: The data header of the associated OAM message also includes a detection option field, and the information items included in the functional entity data strip are determined by the value of the detection option field.

17. The method according to claim 8, wherein: The message-specific sequence number includes a domain code and a sequence code, the domain code is used to identify the OAM domain from which the associated OAM message originates, and the sequence code has a unique corresponding relationship with the associated OAM message in the OAM domain.

18. A message transmission method, applied to a second communication node, the method comprising: Receiving an associated OAM message, wherein the associated OAM message includes a data area and a data header, and the data header includes a message-specific sequence number and a functional entity detection identifier; A first detection feedback message is sent, wherein the first detection feedback message includes: a flow identifier, a node identifier, a message-specific sequence number corresponding to the associated OAM message, and all functional entity data strips in the data area of ​​the associated OAM message received by the second communication node.

19. An electronic device comprising: one or more processors; A memory having one or more programs stored thereon, when the one or more programs are executed by the one or more processors, the one or more processors implement: The message transmission method according to any one of claims 1 to 7; or The message transmission method according to any one of claims 8 to 17; or, The message transmission method as claimed in claim 18.

20. A computer-readable storage medium having a computer program stored thereon, wherein when the program is executed by a processor, the program implements: The message transmission method according to any one of claims 1 to 7; or The message transmission method according to any one of claims 8 to 17; or, The message transmission method as claimed in claim 18.

Images