CN118900290A - Message processing method, device, equipment and readable storage medium - Google Patents

Abstract

The present invention discloses a message processing method, device, equipment and readable storage medium, which relates to the field of data transmission technology, to solve the problem of high packet loss rate of business messages and low transmission reliability of business messages. The method is applied to a first device, and the method includes: receiving a first business message and a first data header sent by a second device through a target network side link, the first data header including first state information and first sequence identification information; determining a second business message based on the first state information; associating the second data header with the second business message, the second data header including second state information and second sequence identification information; sending the second business message and the second data header to the second device through the target network side link. The embodiment of the present invention can reduce the packet loss rate of business messages.

Description

Message processing method, device, equipment and readable storage medium

Technical Field

The present invention relates to the technical field of data transmission, and in particular to a message processing method, device, equipment and readable storage medium.

Background Art

For multi-service access, the Optical Transport Network (OTN) needs to support transmission pipelines for a variety of different services, including the fifth-generation mobile communication technology (5G), the fourth-generation mobile communication technology (4G), customer and home broadband, etc. Different services require different transmission levels. For some types of services, it is required that the corresponding service messages are transmitted between any two customer-side OTN devices (Customer Premise Equipment OTN, CPE OTN) without packet loss.

In the prior art, when CPE OTN devices transmit service messages, it is difficult to timely discover and resend the service message when the service message is not correctly received, resulting in a high packet loss rate of the service message and low transmission reliability of the service message.

Summary of the invention

The embodiments of the present invention provide a message processing method, apparatus, device and readable storage medium to solve the problems of high packet loss rate of business messages and low transmission reliability of business messages.

In a first aspect, an embodiment of the present invention provides a message processing method, which is applied to a first device, and the method includes:

receiving, through the target network side link, a first service message and a first data header sent by a second device, where the first data header is associated with the first service message, and the first data header includes first state information and first sequence identification information, where the first state information is used to characterize a reception state of the service message sent by the first device by the second device, and the first sequence identification information is used to identify a sequence number of the first service message;

Determine a second service message based on the first status information;

Associating a second data header with the second service message, where the second data header includes second state information and second sequence identification information, where the second state information is used to characterize a reception state of the service message sent by the first device to the second device, and the second sequence identification information is used to identify a sequence number of the second service message;

The second service message and the second data header are sent to the second device through the target network side link.

Optionally, the target network side link includes N network side links, where N is a positive integer greater than 1; and associating the second data header with the second service message includes:

Generate N second data headers corresponding one-to-one to the N network-side links, each of the second data headers including a corresponding link identifier;

Associating each of the N second data headers with the second service message respectively;

The sending the second service message and the second data header to the second device through the target network side link includes:

The second data header and the second service message corresponding to the network side link are sent to the second device through each of the N network side links.

Optionally, the first status information includes first confirmation identification information and first packet loss identification information, the first confirmation identification information is used to identify the sequence number of the service message successfully received by the second device in the service message sent by the first device, and the first packet loss identification information is used to identify the sequence number of the service message failed to be received by the second device in the service message sent by the first device.

Optionally, determining the second service message based on the first state information includes:

Based on the first packet loss identification information, a service message sent by the first device and which fails to be received by the second device is determined as a second service message.

Optionally, the first data header further includes service identification information, where the service identification information is used to characterize a target service corresponding to the first service message. Before sending the second service message and the second data header to the second device through the target network side link, the method further includes:

Determine the target service based on the service identification information;

Based on the predefined correspondence between the service and the network side link, a target network side link corresponding to the target service is determined.

Optionally, associating the second data header with the second service message includes:

Add the second data header to the second service message.

Optionally, associating the second data header with the second service message includes:

The second data header is inserted into the idle bytes between the second service messages.

In a second aspect, an embodiment of the present invention further provides a message processing device, wherein a first device includes the message processing device, and the message processing device includes:

a receiving module, configured to receive, through a target network side link, a first service message and a first data header sent by a second device, wherein the first data header is associated with the first service message, the first data header includes first status information and first sequence identification information, the first status information is used to characterize a reception status of the service message sent by the first device by the second device, and the first sequence identification information is used to identify a sequence number of the first service message;

A first determining module, used to determine a second service message based on the first state information;

an associating module, configured to associate a second data header with the second service message, wherein the second data header includes second state information and second sequence identification information, wherein the second state information is used to characterize a reception state of the service message sent by the first device to the second device, and the second sequence identification information is used to identify a sequence number of the second service message;

A sending module is used to send the second service message and the second data header to the second device through the target network side link.

In a third aspect, an embodiment of the present invention further provides a first device, comprising: a memory, a processor, and a program stored in the memory and executable on the processor;

The processor is used to read the program in the memory to implement the steps in the method described in the first aspect.

In a fourth aspect, an embodiment of the present invention further provides a readable storage medium for storing a program, wherein the program, when executed by a processor, implements the steps in the method described in the first aspect.

In an embodiment of the present application, the first device receives the first service message and the first data header sent by the second device through the target network side link. The first device can determine the reception status of the service message sent by the first device to the second device based on the first status information included in the first data header; the first device can determine the reception status of the service message sent by the first device to the second device based on the first sequence identification information included in the first data header. The first device can promptly determine the reception and transmission status of the service message, so as to promptly retransmit the service message that fails to be transmitted, thereby improving the transmission reliability of the service message and reducing the packet loss rate.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

FIG1 is a schematic diagram of the structure of a CPE OTN transmission network device;

2 is a flow chart of a message processing method provided by an embodiment of the present invention;

FIG3a is a schematic diagram of one of the data receiving methods provided in an embodiment of the present invention;

FIG3b is a second schematic diagram of a data receiving method provided in an embodiment of the present invention;

FIG4a is a third schematic diagram of a data receiving method provided in an embodiment of the present invention;

FIG4b is a fourth schematic diagram of a data receiving method provided in an embodiment of the present invention;

FIG5a is a schematic diagram of the structure of a second service message provided by an embodiment of the present invention;

FIG5b is one of the structural schematic diagrams of the target data message provided by an embodiment of the present invention;

FIG5c is a second schematic diagram of the structure of a data target data message provided by an embodiment of the present invention;

FIG6a is a schematic diagram of one of the transmission modes of service messages provided in an embodiment of the present invention;

FIG6b is a second schematic diagram of a transmission method of a service message provided in an embodiment of the present invention;

7 is a schematic diagram of a CPE OTN chip OSU mapping process flow according to an embodiment of the present invention;

8 is a schematic diagram of establishing a connection link on an OTN management and control platform according to an embodiment of the present invention;

9 is a schematic diagram of a data flow for sending and receiving provided in an embodiment of the present invention;

10 is a schematic diagram of a processing flow of a CPE OTN chip sending a service message according to an embodiment of the present invention;

11 is a schematic diagram of a process flow of receiving a service message by a CPE OTN chip according to an embodiment of the present invention;

12 is a schematic diagram of one of the interaction flow diagrams between CPE OTN chips provided in an embodiment of the present invention;

13 is a schematic diagram of the second interaction process between CPE OTN chips provided in an embodiment of the present invention;

14 is a schematic diagram of the structure of a message processing device provided in an embodiment of the present invention;

FIG. 15 is a schematic diagram of the structure of a first device provided in an embodiment of the present invention.

DETAILED DESCRIPTION

The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

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

An embodiment of the present invention provides a message processing method. Exemplarily, the message processing method provided by the embodiment of the present invention can be applied to a CPE OTN device to process service messages. More specifically, the method can be applied to a main chip of a CPE OTN transmission network device (referred to as a CPE OTN chip) to process service messages.

For ease of understanding, the following will first briefly introduce the relevant contents of the CPE OTN chip.

5G networks need to support a variety of services and application scenarios, such as enhanced mobile broadband (eMBB) services with higher bandwidth and lower latency, massive machine-type communication (mMTC) services that support massive user connections, and ultra-reliable and low latency (ultra-reliable & low latency communication, uRLLC), etc. It is foreseeable that many new user applications will be introduced in the 5G era, such as ubiquitous high-definition/ultra-high-definition and even three-dimensional (3D) holographic films and videos in dense urban areas, high-speed user experience of 100Mbps anywhere, high-speed mobile applications greater than 350km/h, sensor networks, tactile Internet, e-health, natural disaster monitoring, etc.

Due to the requirements of 5G networks, it is necessary to support the transmission of different types of services at the same time, which poses new technical challenges, such as large bandwidth, low latency, hard isolation, flexible connection, unified management and control, and high-precision time synchronization. The existing 4G transmission technology cannot meet the 5G challenges in all aspects, and a new slicing transmission network technology system is needed to support the transmission of 5G services.

5G transmission is based on the Slicing Packet Network (SPN) mechanism. After the data enters the SPN transmission device through the user-side interface (User-to-Network Interface, UNI), it is first classified and distinguished by data type before entering the network-side interface (Network Node Interface or Network to Network Interface, NNI) forwarding process.

For multi-service access, SPN/OTN needs to support transmission pipelines for a variety of different services, including 5G, 4G, customer and home broadband, etc. Different services require different transmission levels, involving bandwidth, latency, jitter, reliability and security, etc. Different transmission pipelines need to be configured to meet the needs. As shown in Figure 1, CPE OTN transmission network equipment supports multi-service access, supports a fixed number of customer services such as E1, Fast Ethernet (FE), Gigabit Ethernet (GE), 10GE Local Area Network (LAN), Synchronous Transfer Module (STM-Synchronous Transfer Module, STM)-1, STM-4, etc., and supports mapping of customer-side services to OTN line ports. The main chip performs multi-service (E1, FE, GE, 10GE LAN, STM-1, STM-4 and other customer services) access, OTN service transmission, (Multi-Service Transport Platform (MSTP) multi-service and Ethernet (ETH) functions. The CPE OTN main chip supports functions including service mapping processing, link monitoring and protection, Ethernet virtual local area network (VLAN) forwarding and operation and maintenance management (Operation Administration and Maintenance) and frequency synchronization.

For multiple service access, the main chip needs to support multiple interfaces, service mapping paths and OTN service processing. When processing OTN services, it is necessary to process multiple cascade mappings (VC12, VC4, STM1, STM4, STM16, OTN0 and OTN1, etc.), multiple encapsulations (Generic Framing Procedure (GFP), Generic Mapping Procedure (GMP), Asynchronous Mapping Procedure (AMP)/Bit-synchronous Mapping Procedure (BMP), etc.) and SNCP protection.

For the convenience of description, in the subsequent embodiments, the embodiment of the present invention is applied to the scenario where the main chip of the CPE OTN device (referred to as the CPE OTN chip) processes the service message. In the above application scenario, the first device and the second device are both CPE OTN chips, and the CPE OTN chips on both sides continuously transmit and process the service message by executing the message processing method provided by the embodiment of the present invention.

Referring to FIG. 2 , an embodiment of the present invention provides a message processing method, which is applied to a first device. The message processing method specifically includes the following steps:

Step 201: Receive a first service message and a first data header sent by a second device through a target network side link, wherein the first data header is associated with the first service message, and the first data header includes first status information and first sequence identification information, wherein the first status information is used to characterize a reception status of the service message sent by the second device to the first device, and the first sequence identification information is used to identify a sequence number of the first service message.

In a specific implementation, the first device and the second device continuously transmit service messages, the first device sends the service message of the first device side to the second device, the second device sends the service message of the second device side to the first device, and the first device stores the corresponding service message after receiving the service message. Among them, the first service message is the service message of the second device side.

The number of first service messages and first data headers is not limited here, the number of first service messages and first data headers is the same, and each first service message is associated with a first data header. The time interval for the first device to send service messages may be the same as or different from the time interval for the second device to send service messages, and the number of first service messages is determined based on the time interval for the first device to send service messages.

For ease of understanding, an example is given below. For example, the first device, as the sender of the service message, sends service message A to the second device at time A, and sends service message B to the second device at time B. The first device, as the receiver of the service message, simultaneously receives the service message sent by the second device. The first service message is the service message received by the first device between time A and time B, and the number of the first service messages is affected by the length of the time difference between time A and time B and the speed at which the second device sends the service message.

When the second device sends service messages to the first device, the service messages are sent in sequence according to the sequence numbers of the service messages. The first sequence identification information may identify the number of service messages sent by the second device that the current first service message is.

The first data header is associated with the first service message, so the first sequence identification information in the first data header is used to identify the sequence number of the first service message. The first device can determine the sequence number of the currently received first service message based on the first sequence identification information, and then determine whether the service message on the second device side has packet loss.

Optionally, in some embodiments, the target network side link includes N network side links, where N is a positive integer greater than 1. The second device sends the first service message and the first data header through the N network side links, and the first device receives the first service message and the first data header sent by the second device through the N network side links.

It should be understood that the second device will send the first service message and the first data header on N network side links, so the first device can receive the first service message and the first data header on each link of the N network side links, and the specific receiving method is not limited here.

As an optional implementation, any one of the N network side links is determined in advance as a main link, and the other network side links of the N network side links except the main link are determined as backup links. The first device receives the first service message and the first data header sent by the second device from the main link, and determines whether there is an unsuccessfully received service message on the main link based on the first sequence identification information. If there is an unsuccessfully received service message on the main link, the sequence number of the unsuccessfully received service message is determined based on the first sequence identification information, and the unsuccessfully received service message is received from the backup link.

For the convenience of description, the configuration mode provided in this embodiment is called a fixed mode, and an example is given below. The target network side links include Link1 and Link2, Link1 is predetermined as the main link, Link2 is predetermined as the backup link, the service message of Link1 is fixedly used as the main data, and the service message of Link2 is used as the backup data, and only when the service message of Link1 is not received, the service message of the corresponding sequence number of the backup data of other links is used as the received data for service processing.

The second device transmits the service message and the data header associated with each service message on Link1 and Link2 respectively. Under normal circumstances, as shown in Figure 3a, Link1 is in a normal state, the receiving data queue reads data from Link1, and the first device receives each service message from Link1 in sequence. When the link1 data is lost or short-circuited, the receiving data queue reads data from Link2.

Exemplarily, as shown in FIG3b , the first device receives service messages with sequence numbers 1, 2, 3, and 4 in sequence from Link1 , but since the service message with sequence number 5 on Link1 is lost, the first device receives the service message with sequence number 5 from Link2 .

As another optional implementation, according to the arrival time of the first service message on each network side link among the N network side links, the first service message is received from the network side link with the earliest arrival time.

For the convenience of description, the configuration mode provided in this embodiment is called the optimal mode, and an example is given below. The target network side link includes Link1 and Link2, and the data received from Link1 and Link2 can be primary data and back up each other. The data is processed according to the first-come-first-served principle and the sequence number order of the arriving service messages.

As shown in FIG4a, for a service message with a sequence number of 5, when the service message arrives at time T1<T2, Link1 arrives earlier than Link2, and the first device receives the service message with a sequence number of 5 from Link1. For a service message with a sequence number of 6, as shown in FIG4b, when the service message arrives at time T3>T4, Link2 arrives earlier than Link1, and the first device receives the service message with a sequence number of 6 from Link2.

Step 202: Determine a second service message based on the first status information.

The first status information is used to characterize the reception status of the service message of the first device side by the second device, wherein the reception status includes successful reception and failed reception. When the first device receives the service message of the second device side, it can determine the reception status of the service message sent by itself based on the first status information in the first data header, and then adaptively adjust the sending of the service message.

Optionally, in some embodiments, the step 202 determines, based on the first packet loss identification information, a service message sent by the first device and which fails to be received by the second device as a second service message.

When the first device determines, based on the first status information, that a certain service message among the service messages sent by the first device to the second device is not correctly received, the first device may choose to resend the service message at any time.

Optionally, in some embodiments, the first status information includes first confirmation identification information and first packet loss identification information, the first confirmation identification information is used to identify the sequence number of the service message successfully received by the second device in the service message sent by the first device, and the first packet loss identification information is used to identify the sequence number of the service message failed to be received by the second device in the service message sent by the first device.

In a specific implementation, the first device and the second device continuously perform bidirectional transmission of service messages, so the number of service messages transmitted between the first device and the second device is usually multiple.

As an optional implementation, the first confirmation identification information includes the serial numbers of all service messages on the first device side that are successfully received by the second device, and the first packet loss identification information includes the serial numbers of all service messages on the first device side that are failed to be received by the second device.

Exemplarily, the first device sends 6 service messages to the second device, whose sequence numbers are 0, 1, 2, 3, 4, and 5, respectively, wherein the service messages with sequence numbers 2 and 4 are not successfully received by the second device. In this embodiment, when the second device sends a service message to the first device, the first confirmation identification information in the associated data header is "0, 1, 3, 5", and the first packet loss identification information is "2, 4".

As another optional implementation, the first confirmation identification information includes a maximum sequence number, which is the maximum value of the sequence numbers of all service messages on the first device side that are successfully received by the second device, and is used to indicate that, except for the sequence number included in the first packet loss identification information, all other service messages corresponding to sequence numbers that are less than or equal to the maximum sequence number are successfully received.

Exemplarily, the first device sends 6 service messages to the second device, whose serial numbers are 0, 1, 2, 3, 4, and 5, respectively, among which the service messages with serial numbers 2 and 4 are not successfully received by the second device. In this embodiment, when the second device sends a service message to the first device, the first confirmation identification information in the associated data header is "5", and the first packet loss identification information is "2, 4". According to the first confirmation identification information, except for 2 and 4, the service messages corresponding to the serial numbers less than or equal to 5 (i.e., 0, 1, 3, 5) are all successfully received. Through the method provided in this embodiment, the number of bits occupied by the first confirmation identification information can be reduced, thereby improving the utilization rate of resources.

In this embodiment, the first status information includes first confirmation identification information and first packet loss identification information, the first confirmation identification information is used to identify the sequence number of the service message successfully received by the second device in the service message sent by the first device, and the first packet loss identification information is used to identify the sequence number of the service message failed to be received by the second device in the service message sent by the first device. Through the above settings, the first device can quickly determine the reception status of each service message based on the sequence number in the first status information, thereby improving the convenience, accuracy and efficiency of the first device in determining the reception status of the service message.

Step 203: associate a second data header with the second service message, wherein the second data header includes second status information and second sequence identification information, wherein the second status information is used to characterize a reception status of the service message sent by the first device to the second device, and the second sequence identification information is used to identify a sequence number of the second service message.

Since the service messages received by the first device are all associated with a data header, the first device can judge whether the service messages are unsuccessfully received based on the sequence numbers of the received service messages, and determine the sequence numbers of the unsuccessfully received service messages.

Exemplarily, after the first device has received and stored the business messages with serial numbers 0, 1, 2, and 3 sent by the second device, it determines through the first data header that the serial number of the currently received first business message is 5. At this time, the first device combines the serial numbers of the successfully received business messages and the serial number of the currently received business message to determine that the business message with serial number 4 has not been correctly received.

After the first device determines which service messages are successfully received and which service messages are not successfully received based on the sequence numbers of the received service messages, the second status information may be generated.

In some embodiments, the second status information includes second confirmation identification information and second packet loss identification information, the second confirmation identification information is used to identify the sequence number of the service message successfully received by the first device in the service message sent by the second device, and the second packet loss identification information is used to identify the sequence number of the service message failed to be received by the first device in the service message sent by the second device.

After generating the second data header, the second sequence identification information of the second data header is set to the serial number of the second business message, completing the association between the second data header and the second business message, so that after the second device receives the second business message and the second data header, it can determine the serial number of the second business message and the reception status of the first device for the first business message.

Step 204: Send the second service message and the second data header to the second device through the target network side link.

Optionally, as an optional implementation, step 203 includes:

Add the second data header to the second service message.

In this implementation, the second data header is added to the second service message to obtain a target data message.

The target data message is sent to the second device via the target network side link.

In this embodiment, the second data header is inserted into the second service message and becomes a part of the service message to obtain the target data message. The specific structure of the second service message can refer to the description in the related art, which will not be repeated here. In the specific implementation, the second data header can be added to any position of the second service message according to actual needs, such as the middle, head and tail of the Ethernet message.

Exemplarily, the structure of the second service message is shown in Figure 5a, and the second service message includes media access control (Media Access Control, MAC), virtual local area network (Virtual Local Area Network, VLAN), multi-protocol label switching (Multi-Protocol Label Switching, MPLS), Internet Protocol (Internet Protocol, IP), payload (Payload) and frame check sequence (Frame Check Sequence, FCS).

As an optional implementation, the second data header is added to the header of the service message to obtain the target data message as shown in Figure 5b, and the second data header + ETH format is obtained. As another optional implementation, the second data header is added after the IP header to obtain the target data message as shown in Figure 5c, and the ETH + IP + second data header + Payload format is obtained.

In this embodiment, the second data header is added to the second service message to obtain the target data message; the target data message is sent to the second device through the target network side link. Through the above method, the target data message is constructed and the target data message is transmitted, so that the second data header and the second service message are more closely associated, avoiding the situation where only one of the second data header and the second service message is successfully received. Since this embodiment changes the frame structure of the link layer, the message processing flow of the link layer will also change accordingly.

Optionally, as another optional implementation, step 203 includes:

The second data header is inserted into the idle bytes between the second service messages.

In this embodiment, the second service message and the second data header are sent to the second device via the target network side link, wherein the second data header occupies an idle block for transmission.

In the transmission of the service message, there are idle blocks (or idle bytes) between frames, and the second data header is transmitted using the idle blocks. For example, as shown in FIG6a, there are 20 bits (Bytes) of frame gap and preamble between ETH messages, and as shown in FIG6b, the second data header is transmitted using the frame gap and preamble.

In this embodiment, the second data header is transmitted by occupying the idle block. The second data header is transmitted by using the idle bytes between frames, which only affects the processing flow of the physical layer and does not affect the structure of the second service message, so that the data processing of the second service message can be compatible with the existing data processing flow, and the processing process is more convenient and efficient.

Optionally, in some embodiments, the target network side link includes N network side links, where N is a positive integer greater than 1; and step 203 includes:

Generate N second data headers corresponding one-to-one to the N network-side links, each of the second data headers including a corresponding link identifier;

Associating each of the N second data headers with the second service message respectively;

The step 204 includes:

The second data header and the second service message corresponding to the network side link are sent to the second device through each of the N network side links.

Since the target network side link includes N network side links, N second data headers need to be generated accordingly to be associated with the second service message transmitted on each network side link. Each second data header includes a link identifier for identifying on which network side link the second data header is transmitted.

After generating N second data headers, the first sequence identification information included in the N second data headers is respectively set as the sequence number of the second service message associated therewith, so as to associate each second data header with the second service message.

The second service message and the second data header are respectively sent on each network side link so that the second device receives the second service message and the second data header. The manner in which the second device receives the second service message and the second data header can be referred to the relevant description of FIG. 3a to FIG. 4b, which will not be described here.

In this embodiment, the target network side link includes at least two network side links. The first device sends the second data header and the second service message to the second device through at least two network side links. In the event of packet loss in any one of the network side links, the second device can still receive the second data header and the second service message from other network side links, thereby improving the success rate of the second device in receiving the second service message and reducing the packet loss rate.

In actual application, the CPE OTN chip supports multi-service access, and different services require different transmission levels. Some services have lower requirements on packet loss rate (for example, services with 50ms carrier-grade protection), and there is no need to process messages using the method provided in this embodiment.

Optionally, in some embodiments, the first data header further includes service identification information, and the service identification information is used to characterize a target service corresponding to the first service message. Before step 204, the method further includes:

Determine the target service based on the service identification information;

Based on the predefined correspondence between the service and the network side link, a target network side link corresponding to the target service is determined.

It should be understood that the network side links are pre-configured and there are multiple links. Through the OTN management and control platform, multiple network side links of the CPE OTN service are established. According to the actual service requirements, the corresponding relationship between the service and the network side link is pre-defined.

Exemplarily, for a service that does not need to process messages using the method provided in this embodiment, the corresponding network side link is not allocated, and the process in the prior art is executed. For a service that needs to process messages using the method provided in this embodiment, N network side links in the pre-configured network side links are determined as the target network side links corresponding to the service.

In specific implementation, the number of network side links corresponding to different services can be the same or different, and multiple network side links corresponding to the same service do not share the same optical fiber link, thereby improving the protection effect. By configuring different optical channel data units (ODUk), different OTN channels are established and sent to different network side links.

In this embodiment, after receiving the data header, the first device determines the target service corresponding to the service message based on the service identification information, and determines the target network side link based on the pre-defined correspondence between the service and the network side link, thereby transmitting the service message on the first device side on the target network side link.

In the embodiment of the application, the target service is determined based on the service identification information; based on the predefined correspondence between the service and the network side link, the target network side link corresponding to the target service is determined. Through the above method, the CPE OTN chip can execute different message processing methods for different service types, thereby improving the flexibility of the CPE OTN chip in multi-service processing, while avoiding the occupation of the network side link by other types of services, thereby improving the reliability of the network side link.

In an embodiment of the present application, the first device receives the first service message and the first data header sent by the second device through the target network side link. The first device can determine the reception status of the service message sent by the first device to the second device based on the first status information included in the first data header; the first device can determine the reception status of the service message sent by the first device to the second device based on the first sequence identification information included in the first data header. The first device can promptly determine the reception and transmission status of the service message, so as to promptly retransmit the service message that fails to be transmitted, thereby improving the transmission reliability of the service message and reducing the packet loss rate.

In some embodiments, the first data header and the second data header are both lossless optional delay data headers, and the lossless optional delay data header includes service identification information, lossless identification information, link identification information, sequence identification information, confirmation identification information and packet loss identification information;

Among them, the service identification information is used to identify the service flow identifier (Identifier, ID) corresponding to the lossless optional delay data header, the lossless identification information is used to identify whether the type of the service is a lossless service, the link identification information is used to identify the network side link ID corresponding to the lossless optional delay data header, the sequence identification information is used to identify the sequence number ID of the service message corresponding to the lossless optional delay data header, the confirmation identification information is used to identify the sequence number ID of the successfully received service message, and the packet loss identification information is used to identify the sequence number ID of the lost service message. The structure of the lossless optional delay data header can be seen in Table 1.

Table 1 Example of structure of lossless optional delay data header

When the lossless optional delay data header is used as the first data header, the sequence identification information can be understood as the first sequence identification information, the confirmation identification information can be understood as the first confirmation identification information, and the packet loss identification information can be understood as the first packet loss identification information.

When the lossless optional delay data header is used as the second data header, the sequence identification information can be understood as the second sequence identification information, the confirmation identification information can be understood as the second confirmation identification information, and the packet loss identification information can be understood as the second packet loss identification information.

After the first device sends the second service message and the second data header to the second device through the target network side link, the second device receives the second service message and the second data header sent by the second device through the target network side link, determines the next service message sent by the second device based on the second state information, associates the lossless optional delay data header with the service message, and sends the service message and the lossless optional delay data header to the first device through the target network side link. The specific method can be referred to the above content and is not limited here.

For ease of understanding, a specific embodiment is used as an example for explanation below. When CPE OTN processes multi-service access, it supports multiple interface services (E1, FE, GE, 10GE LAN, STM-1, STM-4 and other customer services), encapsulates multiple interface services into multi-level containers, and after cascading processing, sends them to the OTN interface for line-side transmission. Exemplarily, the CPE OTN chip optical service unit (Optical Service Unit, OSU) mapping processing flow is shown in Figure 7. The service mapping module encapsulates the customer signal into the ODU payload frame, and then encapsulates the optical channel transport unit overhead (Optical Channel Transport UnitOverhead, OUT OH) header, performs OTU channel layer processing, and encapsulates and sends it. During the encapsulation process, by adding a lossless optional delay function, rich service options are achieved, including lossless time slot forwarding, ultra-low delay processing, etc., to achieve more optimized OTN service processing.

Through the OTN management and control platform, a network side link of the CPE OTN service is established, as shown in Figure 8. Different service types are defined according to the service entry type and service requirements. The service type of 50ms carrier-level protection can be understood as a common service, that is, a service that does not need to be processed by the method provided in the embodiment of the present application. The service type of no packet loss can be understood as a lossless optional delay service, that is, a service that needs to be processed by the method provided in the embodiment of the present application. According to the service configuration, the corresponding table items are set, and the details can be seen in Table 2.

Table 2 Lossless optional delay service configuration table

business Stream ID Business Type Network side link PORT+VLAN 1 1 No packet loss Link 1 PORT+VLAN 2 2 No packet loss Link 1 PORT+VLAN 3 3 No packet loss Link 2 PORT+VLAN 4 4 No packet loss Link 3 PORT+VLAN 5 5 50ms carrier-grade protection - … … … …

In this embodiment, two network-side links are established between the CPE OTN1 chip (referred to as chip A) and the CPE OTN2 chip (referred to as chip B), which are called link1 and link2. To improve the protection effect, link1 and link2 do not share the same optical path. By configuring different ODUk, different OTN channels are established and sent to different links.

When a service is created, the corresponding data transmission and reception streams will be established at the same time, as shown in FIG9 :

Create service 1, corresponding to send stream ID 1, receive stream ID 2, and send and receive on link 1 and link 2;

Create service 2, corresponding to sending flow ID 3 and receiving flow ID 4, and send and receive on link 1 and link 2.

Table 3 Example of lossless optional delay data header

When the service message of the current service needs to be processed based on the message processing method provided in the embodiment of the present application, the current data stream enables the lossless optional delay function and constructs a lossless optional delay data header as shown in Table 3.

Referring to FIG. 10 , the processing flow of the CPE OTN chip sending a service message is as follows:

Step A: After receiving the service message, the CPE OTN chip first identifies the flow ID of the service data flow according to the definition, and determines whether it is a lossless optional delay service. If not, the message is processed according to the existing process. If yes, the process of step B is performed;

Step B: According to the flow ID of the identified service data flow and the correspondence between the pre-configured service and the network side link, a lossless optional delay data header as shown in Table 3 is formed;

Step C: according to the position of the predefined lossless optional delay data header, associating the lossless optional delay data header with the service message;

Step D: Send the service message associated with the lossless optional delay data header on the corresponding network side link (Link1-Linkn). Each time a service message is sent (that is, after the service message is sent on the network layer link (Link1-Linkn)), the sequence identifier in the lossless optional delay data header of the corresponding service message is increased by 1, the confirmation identifier is the currently received sequence identifier, and the packet loss identifier is the sequence identifier of the current link packet loss.

Referring to FIG. 11 , the processing flow of the CPE OTN chip receiving a service message is as follows:

When receiving a service message and the associated data header on Link1 or Link2, if the service is a lossless service, the following processing is performed, otherwise the message is processed according to the existing process. The stream ID, lossless identifier and link identifier in the received lossless optional delay data header will be used to check whether the corresponding link and service message match. The CPE OTN chip will store the received service message.

Parse the lossless optional delay data header and service message, select the configuration mode (for example, the fixed mode shown in FIG3a or the optimal mode shown in FIG3b, for details, please refer to the above content, which will not be repeated here). Update the corresponding confirmation identifier according to the sequence identifier, and add the confirmation identifier to the lossless optional delay data header associated with the service message when the reverse service is sent.

Whether packet loss occurs is determined based on the order in which the service messages arrive and the sequence identifier in the lossless optional delay data header associated with the service messages. The determination method can be found in the description of the aforementioned embodiment and is not limited here.

During the bidirectional transmission and reception of service messages between chip A and chip B, when chip A is used as a first device to execute the method provided in the embodiment of the present application, chip B is the second device corresponding to chip A. Similarly, when chip B is used as a first device to execute the method provided in the embodiment of the present application, chip A is the second device corresponding to chip B.

For ease of understanding, the following will explain the interaction process between chip A and chip B. Please refer to Figure 12, link connections Link1 and Link2 are established between chip A (A end) and chip B (B end). In a normal scenario, the message interaction process between end A and end B is as follows:

A side: A sends a service message on Link1 and Link2, with an associated lossless optional delay data header (referred to as data header). The data header contains the sequence identifier (seq) x, confirmation identifier (ack) and loss identifier (lost) of the service message being sent. A sends the data header and service message to B. The data format from A to B is Data+data header (seq x, ack, lost), where Data is the service message.

B side: B receives the service message sent by A on Link1 and Link2, and updates the confirmation mark to x according to the sequence mark of the received service message, to indicate that the service message with sequence number x sent by A is successfully received. At the same time, it determines whether there is a lost service message according to the sequence number of the received service message and updates the loss mark lost. The data header associated with the service message sent by B to A carries the sequence mark y, confirmation mark x and loss mark lost, and the data format from B to A is Data+data header (seq y, ack x, lost).

A side: A receives the service message sent by B on Link1 and Link2, and updates the confirmation flag to y according to the sequence flag of the received service message, to indicate that the service message with sequence number y sent by B is successfully received. At the same time, it determines whether there is a lost service message according to the sequence number of the received service message and updates the loss flag lost. The data header associated with the service message sent by A to B carries the sequence flag x+1, confirmation flag y and loss flag lost. The data format from A to B is Data+data header (seq x+1, ack y, lost).

As shown in Figure 13, Link 1 and Link 2 are established between A and B. In the packet loss scenario, the message exchange process between A and B is as follows:

A: A sends a service message on Link1 and Link2 with the associated data header. A sends the data header and service message to B. The data format from A to B is Data+data header (seq x1, ack y1, lost z).

B side: B receives the service message sent by A on Link1 and Link2, and updates the confirmation identifier to x1 according to the sequence identifier of the received service message, to indicate that the service message with sequence number x1 sent by A has been successfully received. B finds message z in B according to the loss identifier z in the data header, and resends message z to A from B. At the same time, it determines whether B has lost messages according to the sequence number of the received service message and updates the loss identifier lost. The service message sent from B to A is message z, and the data header contains the sequence identifier z, the confirmation identifier x1 and the loss identifier lost. The data format from B to A is Data+data header (seq z, ack x1, lost).

A side: A receives the service message sent by B on Link1 and Link2, updates the confirmation flag to z according to the sequence flag of the received service message, and determines whether there is a lost service message according to the sequence number of the received service message and updates the loss flag lost. The data header associated with the service message sent by B to A carries the sequence flag x+1, confirmation flag z and loss flag lost. The data format from A to B is Data+data header (seq x1+1, ack z, lost).

In this embodiment, both chip A and chip B can be used as the first device to execute the message processing method provided in this embodiment. This embodiment provides a new CPE OTN service chip processing flow, including the mapping flow of ETH frames to ODUs, by adding a lossless optional delay function and using a transmission protection link, to achieve lossless optional delay forwarding of OTN services, provide more reliable and efficient service transmission for upper layer services, provide more service function options, and achieve a more cost-effective CPE OTN chip design.

The embodiment of the present invention further provides a message processing device, and the first device includes the message processing device. Referring to FIG. 14, FIG. 14 is a structural diagram of the message processing device 1400 provided by the embodiment of the present invention. Since the principle of solving the problem by the message processing device 1400 is similar to the message processing method shown in FIG. 2 in the embodiment of the present invention, the implementation of the message processing device 1400 can refer to the implementation of the method, and the repeated parts will not be repeated.

Referring to FIG. 14 , an embodiment of the present invention further provides a message processing device 1400. The first device includes the message processing device 1400. The message processing device 1400 includes:

A receiving module 1401 is configured to receive, through a target network side link, a first service message and a first data header sent by a second device, where the first data header is associated with the first service message, and the first data header includes first state information and first sequence identification information, where the first state information is used to characterize a reception state of the service message sent by the first device by the second device, and the first sequence identification information is used to identify a sequence number of the first service message;

A first determining module 1402, configured to determine a second service message based on the first state information;

an associating module 1403, configured to associate a second data header with the second service message, where the second data header includes second state information and second sequence identification information, where the second state information is used to characterize a reception state of the service message sent by the first device to the second device, and the second sequence identification information is used to identify a sequence number of the second service message;

The sending module 1404 is used to send the second service message and the second data header to the second device through the target network side link.

Optionally, the target network side link includes N network side links, where N is a positive integer greater than 1; the association module 1403 includes:

A generating unit, configured to generate N second data headers corresponding one-to-one to the N network-side links, each of the second data headers including a corresponding link identifier;

an associating unit, configured to associate each of the N second data headers with the second service message respectively;

The sending module 1404 is specifically used for:

The second data header and the second service message corresponding to the network side link are sent to the second device through each of the N network side links.

Optionally, the first status information includes first confirmation identification information and first packet loss identification information, the first confirmation identification information is used to identify the sequence number of the service message successfully received by the second device in the service message sent by the first device, and the first packet loss identification information is used to identify the sequence number of the service message failed to be received by the second device in the service message sent by the first device.

Optionally, the first determining module 1402 is specifically configured to:

Based on the first packet loss identification information, a service message sent by the first device and which fails to be received by the second device is determined as a second service message.

Optionally, the first data header further includes service identification information, where the service identification information is used to characterize a target service corresponding to the first service message, and the message processing device 1400 further includes:

A second determination module, configured to determine the target service based on the service identification information;

The third determination module is used to determine the target network side link corresponding to the target service based on the predefined correspondence between the service and the network side link.

Optionally, the association module 1403 is specifically used for:

Add the second data header to the second service message.

Optionally, the association module 1403 is specifically used for:

The second data header is inserted into the idle bytes between the second service messages.

The message processing device 1400 provided in the embodiment of the present invention can implement each process implemented by the method embodiment shown in FIG. 2 , and can achieve the same beneficial effects. To avoid repetition, it will not be described again here.

The embodiment of the present invention further provides a first device. Since the principle of solving the problem by the first device is similar to the message processing method shown in FIG. 2 in the embodiment of the present invention, the implementation of the first device can refer to the implementation of the method, and the repeated parts will not be repeated.

As shown in FIG. 15 , the first device according to the embodiment of the present invention includes: a processor 1500 configured to read a program in a memory 1520 and execute the following process:

Receiving, through the transceiver 1510, a first service message and a first data header sent by a second device through a target network side link, where the first data header is associated with the first service message, and the first data header includes first state information and first sequence identification information, where the first state information is used to characterize a reception state of the service message sent by the first device by the second device, and the first sequence identification information is used to identify a sequence number of the first service message;

Determine a second service message based on the first status information;

Associating a second data header with the second service message, where the second data header includes second state information and second sequence identification information, where the second state information is used to characterize a reception state of the service message sent by the first device to the second device, and the second sequence identification information is used to identify a sequence number of the second service message;

The second service message and the second data header are sent to the second device through the target network side link via the transceiver 1510.

The transceiver 1510 is configured to receive and send data under the control of the processor 1500 .

In FIG. 15 , the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1500 and various circuits of memory represented by memory 1520 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver 1510 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium.

The processor 1500 is responsible for managing the bus architecture and general processing, and the memory 1520 can store data used by the processor 1500 when performing operations.

Optionally, the target network side link includes N network side links, where N is a positive integer greater than 1; the processor 1500 is further configured to read a program in the memory 1520 and execute the following steps:

Generate N second data headers corresponding one-to-one to the N network-side links, each of the second data headers including a corresponding link identifier;

Associating each of the N second data headers with the second service message respectively;

The second data header and the second service message corresponding to the network side link are sent to the second device through each of the N network side links.

Optionally, the first status information includes first confirmation identification information and first packet loss identification information, the first confirmation identification information is used to identify the sequence number of the service message successfully received by the second device in the service message sent by the first device, and the first packet loss identification information is used to identify the sequence number of the service message failed to be received by the second device in the service message sent by the first device.

Optionally, the processor 1500 is further configured to read a program in the memory 1520 and execute the following steps:

Based on the first packet loss identification information, a service message sent by the first device and which fails to be received by the second device is determined as a second service message.

Optionally, the first data header further includes service identification information, where the service identification information is used to characterize a target service corresponding to the first service message. The processor 1500 is further used to read a program in the memory 1520 and execute the following steps:

Determine the target service based on the service identification information;

Based on the predefined correspondence between the service and the network side link, a target network side link corresponding to the target service is determined.

Optionally, the processor 1500 is further configured to read a program in the memory 1520 and execute the following steps:

Add the second data header to the second service message.

Optionally, the processor 1500 is further configured to read a program in the memory 1520 and execute the following steps:

The second data header is inserted into the idle bytes between the second service messages.

The first device provided in the embodiment of the present invention can execute the method embodiment shown in Figure 2, and its implementation principle and technical effects are similar, which will not be repeated in this embodiment.

An embodiment of the present invention further provides a readable storage medium for storing a program, wherein the program, when executed by a processor, implements the steps in the message processing method shown in FIG. 2 .

In the several embodiments provided in the present application, it should be understood that the disclosed methods and devices can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may be physically included separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium, including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform some steps of the sending and receiving method described in each embodiment of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program codes.

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

Claims (10)

1. A message processing method, characterized in that it is applied to a first device, and the method comprises: receiving, through the target network side link, a first service message and a first data header sent by a second device, where the first data header is associated with the first service message, and the first data header includes first state information and first sequence identification information, where the first state information is used to characterize a reception state of the service message sent by the first device by the second device, and the first sequence identification information is used to identify a sequence number of the first service message; Determine a second service message based on the first status information; Associating a second data header with the second service message, where the second data header includes second state information and second sequence identification information, where the second state information is used to characterize a reception state of the service message sent by the first device to the second device, and the second sequence identification information is used to identify a sequence number of the second service message; The second service message and the second data header are sent to the second device through the target network side link. 2. The method according to claim 1, wherein the target network side link includes N network side links, where N is a positive integer greater than 1; and associating the second data header with the second service message comprises: Generate N second data headers corresponding one-to-one to the N network-side links, each of the second data headers including a corresponding link identifier; Associating each of the N second data headers with the second service message respectively; The sending the second service message and the second data header to the second device through the target network side link includes: The second data header and the second service message corresponding to the network side link are sent to the second device through each of the N network side links. 3. The method according to claim 1 is characterized in that the first status information includes first confirmation identification information and first packet loss identification information, the first confirmation identification information is used to identify the sequence number of the service message successfully received by the second device in the service message sent by the first device, and the first packet loss identification information is used to identify the sequence number of the service message failed to be received by the second device in the service message sent by the first device. 4. The method according to claim 3, characterized in that the determining the second service message based on the first state information comprises: Based on the first packet loss identification information, a service message sent by the first device and which fails to be received by the second device is determined as a second service message. 5. The method according to claim 1, wherein the first data header further includes service identification information, and the service identification information is used to characterize the target service corresponding to the first service message, and before sending the second service message and the second data header to the second device through the target network side link, the method further includes: Determine the target service based on the service identification information; Based on the predefined correspondence between the service and the network side link, a target network side link corresponding to the target service is determined. 6. The method according to claim 1, wherein associating the second data header with the second service message comprises: Add the second data header to the second service message. 7. The method according to claim 1, wherein associating the second data header with the second service message comprises: The second data header is inserted into the idle bytes between the second service messages. 8. A message processing device, characterized in that a first device comprises the message processing device, and the message processing device comprises: a receiving module, configured to receive, through a target network side link, a first service message and a first data header sent by a second device, wherein the first data header is associated with the first service message, the first data header includes first status information and first sequence identification information, the first status information is used to characterize a reception status of the service message sent by the first device by the second device, and the first sequence identification information is used to identify a sequence number of the first service message; A first determining module, used to determine a second service message based on the first state information; an associating module, configured to associate a second data header with the second service message, wherein the second data header includes second state information and second sequence identification information, wherein the second state information is used to characterize a reception state of the service message sent by the first device to the second device, and the second sequence identification information is used to identify a sequence number of the second service message; A sending module is used to send the second service message and the second data header to the second device through the target network side link. 9. A first device, comprising: a memory, a processor, and a program stored in the memory and executable on the processor; characterized in that: The processor is used to read the program in the memory to implement the steps in the method according to any one of claims 1 to 7. 10. A readable storage medium for storing a program, wherein when the program is executed by a processor, the program implements the steps in the method according to any one of claims 1 to 7.