Message processing method, device and equipment and readable storage medium

Abstract

The application discloses a message processing method and device, equipment and a readable storage medium, and relates to the technical field of data transmission, to solve the problems of high packet loss rate of service messages and low transmission reliability of service messages. The method is applied to a first device, and the method comprises the following steps: receiving 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 comprises first state information and first sequence identification information; determining a second service message based on the first state information; associating a second data header with the second service message, wherein the second data header comprises second state information and second sequence identification information; and sending the second service message and the second data header to the second device through the target network side link. The application can reduce the packet loss rate of service messages.

Description

Technical Field

[0001] This invention relates to the field of data transmission technology, and in particular to a message processing method, apparatus, device, and readable storage medium. Background Technology

[0002] For multi-service access, the Optical Transport Network (OTN) needs to support transmission channels for various services, including 5G, 4G, enterprise broadband, and home broadband. Different services require different transmission levels; for some service types, it is required that their corresponding service packets be transmitted without packet loss between any two customer-side OTN (Customer Premise Equipment OTN) devices.

[0003] In the existing technology, when CPE OTN devices transmit service messages, it is difficult to detect and retransmit the service message in a timely manner if the service message is not received correctly, resulting in a high packet loss rate and low reliability of service message transmission. Summary of the Invention

[0004] This invention provides a message processing method, apparatus, device, and readable storage medium to solve the problems of high packet loss rate and low transmission reliability of service messages.

[0005] In a first aspect, embodiments of the present invention provide a message processing method applied to a first device, the method comprising:

[0006] The first service packet and the first data header sent by the second device are received through the target network side link. The first data header is associated with the first service packet. The first data header includes first status information and first sequence identifier information. The first status information is used to characterize the receiving status of the second device in receiving the service packet sent by the first device. The first sequence identifier information is used to identify the sequence number of the first service packet.

[0007] The second service message is determined based on the first status information;

[0008] The second data header is associated with the second service message. The second data header includes second status information and second sequence identifier information. The second status information is used to characterize the reception status of the first device for the service message sent by the second device, and the second sequence identifier information is used to identify the sequence number of the second service message.

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

[0010] Optionally, the target network-side link includes N network-side links, where N is a positive integer greater than 1; associating the second data header with the second service packet includes:

[0011] Generate N second data headers that correspond one-to-one with the N network-side links, each second data header including the corresponding link identifier;

[0012] Each of the N second data headers is associated with the second service message;

[0013] Sending the second service message and the second data header to the second device via the target network side link includes:

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

[0015] Optionally, the first status information includes first confirmation identifier information and first packet loss identifier information. The first confirmation identifier 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 identifier information is used to identify the sequence number of the service message that the second device failed to receive in the service message sent by the first device.

[0016] Optionally, determining the second service message based on the first status information includes:

[0017] Based on the first packet loss identifier information, the service message that the second device failed to receive in the service message sent by the first device is identified as the second service message.

[0018] Optionally, the first data header further includes service identification information, which is used to characterize the target service corresponding to the first service packet. Before sending the second service packet and the second data header to the second device through the target network side link, the method further includes:

[0019] The target service is determined based on the service identification information;

[0020] Based on the predefined correspondence between services and network-side links, the target network-side link corresponding to the target service is determined.

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

[0022] Add the second data header to the second service message.

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

[0024] Insert the second data header into the free bytes between the second service messages.

[0025] Secondly, embodiments of the present invention also provide a message processing apparatus, wherein a first device includes the message processing apparatus, and the message processing apparatus includes:

[0026] The receiving module is configured to receive a first service packet and a first data header sent by a second device through a target network side link. The first data header is associated with the first service packet. The first data header includes first status information and first sequence identifier information. The first status information is used to characterize the receiving status of the second device for the service packet sent by the first device. The first sequence identifier information is used to identify the sequence number of the first service packet.

[0027] The first determining module is used to determine the second service message based on the first status information;

[0028] The association module is used to associate the second data header with the second service message. The second data header includes second status information and second sequence identifier information. The second status information is used to characterize the reception status of the first device for the service message sent by the second device, and the second sequence identifier information is used to identify the sequence number of the second service message.

[0029] The 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.

[0030] Thirdly, embodiments of the present invention also provide a first device, comprising: a memory, a processor, and a program stored in the memory and executable on the processor;

[0031] The processor is configured to read a program from memory to implement the steps described in the first aspect of the method.

[0032] Fourthly, embodiments of the present invention also provide a readable storage medium for storing a program, which, when executed by a processor, implements the steps described in the first aspect.

[0033] In this embodiment, a first device receives a first service packet and a first data header sent by a second device via a target network side link. Based on the first status information included in the first data header, the first device can determine the reception status of the service packet sent by the second device by the second device; based on the first sequence identifier information included in the first data header, the first device can also determine the reception status of the service packet sent by the second device by the first device. The first device can promptly determine the transmission and reception status of the service packet, thereby promptly retransmitting failed service packets, improving the transmission reliability of the service packet and reducing the packet loss rate. Attached Figure Description

[0034] To more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 This is a schematic diagram of the structure of a CPE OTN transmission network device;

[0036] Figure 2 This is a flowchart of the message processing method provided in the embodiments of the present invention;

[0037] Figure 3a This is one of the schematic diagrams of the data receiving method provided in the embodiments of the present invention;

[0038] Figure 3b This is a second schematic diagram of the data receiving method provided in the embodiments of the present invention;

[0039] Figure 4a This is the third schematic diagram of the data receiving method provided in the embodiment of the present invention;

[0040] Figure 4b This is the fourth schematic diagram of the data receiving method provided in the embodiments of the present invention;

[0041] Figure 5a This is a schematic diagram of the structure of the second service message provided in an embodiment of the present invention;

[0042] Figure 5b This is one of the structural schematic diagrams of the target data packet provided in the embodiments of the present invention;

[0043] Figure 5c This is a second schematic diagram of the structure of the target data packet provided in the embodiments of the present invention;

[0044] Figure 6a This is one of the schematic diagrams of the transmission method of service messages provided in the embodiments of the present invention;

[0045] Figure 6b This is the second schematic diagram of the transmission method of service messages provided in the embodiments of the present invention;

[0046] Figure 7 This is a schematic diagram of the CPE OTN chip OSU mapping processing flow provided in an embodiment of the present invention;

[0047] Figure 8 This is a schematic diagram of the connection link established by the OTN management and control platform provided in this embodiment of the invention;

[0048] Figure 9 This is a schematic diagram of the data stream transmission and reception provided in an embodiment of the present invention;

[0049] Figure 10 This is a schematic diagram of the processing flow of the CPE OTN chip sending service messages provided in an embodiment of the present invention;

[0050] Figure 11 This is a schematic diagram of the processing flow of the CPE OTN chip receiving service packets provided in an embodiment of the present invention;

[0051] Figure 12 This is one of the schematic diagrams of the interaction process between CPE OTN chips provided in the embodiments of the present invention;

[0052] Figure 13 This is the second schematic diagram of the interaction process between CPE OTN chips provided in the embodiments of the present invention;

[0053] Figure 14 This is a schematic diagram of the message processing device provided in an embodiment of the present invention;

[0054] Figure 15 This is a schematic diagram of the structure of the first device provided in an embodiment of the present invention. Detailed Implementation

[0055] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0056] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first" and "second" are generally of the same class, not limited in number; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0057] This invention provides a message processing method. For example, the message processing method provided by this invention can be applied to CPE OTN equipment to process service messages. More specifically, the method can be applied to the main chip (referred to as CPE OTN chip) of CPE OTN transmission network equipment to process service messages.

[0058] To facilitate understanding, a brief introduction to the CPE OTN chip will be provided below.

[0059] 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 supporting massive user connections, and ultra-reliable and low-latency communication (uRLLC). It is foreseeable that the 5G era will introduce many new user applications, such as: ubiquitous high-definition / ultra-high-definition and even 3D holographic films and videos in densely populated urban areas; high-speed user experiences of 100Mbps anywhere; high-speed mobile applications exceeding 350km / h; sensor networks; tactile internet; e-health; and natural disaster monitoring.

[0060] Due to the demands of 5G networks, which require simultaneous support for different service types, new technical challenges arise, such as high bandwidth, low latency, hard isolation, flexible connectivity, unified management and control, and high-precision time synchronization. Existing 4G transmission technologies cannot meet the challenges of 5G in all aspects, necessitating a new slicing transmission network technology to support 5G service transmission.

[0061] 5G transmission is based on the Slicing Packet Network (SPN) mechanism. After data enters the SPN transmission equipment through the User-to-Network Interface (UNI), it first undergoes data classification to distinguish the data type, and then enters the Network Node Interface (NNI) forwarding process.

[0062] For multi-service access, SPN / OTN needs to support transmission channels for various services, including 5G, 4G, enterprise broadband, and home broadband. Different services require different transmission levels, involving bandwidth, latency, jitter, reliability, and security, necessitating the configuration of different transmission channels to meet these needs. For example... Figure 1 As shown, the CPE OTN transmission network equipment supports multi-service access, including a fixed number of E1, Fast Ethernet (FE), Gigabit Ethernet (GE), 10GE Local Area Network (LAN), STM-1, and STM-4 customer services. It also supports mapping customer-side services to OTN line ports. The main chip performs multi-service (E1, FE, GE, 10GE LAN, STM-1, STM-4, etc. customer services) access, OTN service transmission, and multi-service and Ethernet (ETH) functions (Multi-Service Transport Platform, MSTP). The CPE OTN main chip supports functions including service mapping processing, link monitoring and protection, Ethernet Virtual Local Area Network (VLAN) forwarding and operation administration and maintenance, and frequency synchronization.

[0063] To support multiple service access methods, the main chip needs to support various interfaces, service mapping paths, and OTN service processing. During OTN service processing, it is necessary to handle various cascading mappings (VC12, VC4, STM1, STM4, STM16, OTN0, and OTN1, etc.), various encapsulations (Generic Framing Procedure (GFP), Generic Mapping Procedure (GMP), Asynchronous Mapping Procedure (AMP) / Bit-synchronous Mapping Procedure (BMP), etc.), and SNCP protection.

[0064] For ease of description, the following embodiments will be illustrated using the scenario where the main chip (hereinafter referred to as the CPE OTN chip) of the CPE OTN device processes service packets, as an example. In the above application scenario, both the first device and the second device are CPE OTN chips, and both CPE OTN chips continuously transmit and process service packets by executing the packet processing method provided in the embodiments of the present invention.

[0065] Please see Figure 2 This invention provides a message processing method applied to a first device, the message processing method specifically including the following steps:

[0066] Step 201: Receive a first service packet and a first data header sent by the second device through the target network side link. The first data header is associated with the first service packet. The first data header includes first status information and first sequence identifier information. The first status information is used to characterize the receiving status of the second device for the service packet sent by the first device. The first sequence identifier information is used to identify the sequence number of the first service packet.

[0067] In practice, the first device and the second device continuously transmit service messages. The first device sends its own service messages to the second device, and the second device sends its own service messages to the first device. Upon receiving a service message, the first device stores the corresponding service message. The first service message is the service message from the second device's side.

[0068] The number of first service packets and first data headers is not limited here, and the number of first service packets and first data headers is the same. Each first service packet is associated with one first data header. The time interval between the first device sending service packets and the time interval between the second device sending service packets may be the same or different. The number of first service packets is determined based on the time interval between the first device sending service packets.

[0069] To facilitate understanding, an example is given below. For instance, a first device, acting as the sender of service messages, sends service message A to a second device at time A and service message B to the second device at time B. The first device, acting as the receiver of service messages, simultaneously receives service messages sent by the second device. Therefore, the first service message consists of the service messages received by the first device between time A and time B, and its quantity is affected by the length of the time difference between time A and time B and the speed at which the second device sends service messages.

[0070] When the second device sends service messages to the first device, it sends them sequentially according to the sequence number of the service messages. The first sequence identifier information can identify which service message the current first service message is sent by the second device.

[0071] The first data header is associated with the first service message; therefore, the first sequence identifier information in the first data header is used to identify the sequence number of the first service message. Based on the first sequence identifier information, the first device can determine the sequence number of the currently received first service message, and thus determine whether there is packet loss in the service messages on the second device side.

[0072] 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 packet and the first data header through the N network side links, and the first device receives the first service packet and the first data header sent by the second device through the N network side links.

[0073] It should be understood that the second device will send the first service message and the first data header on all N network-side links. Therefore, the first device can receive the first service message and the first data header on each of the N network-side links. The specific receiving method is not limited here.

[0074] As an optional implementation, one of the N network-side links is pre-determined as the primary link, and the other network-side links besides the primary link are designated as backup links. The first device receives a first service packet and a first data header from the second device via the primary link, and determines whether there are any unreceived service packets on the primary link based on the first sequence identifier information. If there are unreceived service packets on the primary link, the sequence number of the unreceived service packets is determined based on the first sequence identifier information, and the unreceived service packets are received from the backup links.

[0075] For ease of description, the configuration mode provided in this embodiment will be referred to as the fixed mode, and an example will be given below. The target network-side links include Link1 and Link2. Link1 is pre-determined as the primary link and Link2 as the backup link. Service packets of Link1 are always used as primary data, and service packets of Link2 are used as backup data. Only when no service packets of Link1 are received will service packets with the corresponding sequence number of the backup data of other links be used as received data for service processing.

[0076] The second device transmits service packets and the associated data header for each service packet on Link1 and Link2 respectively. Under normal circumstances, such as Figure 3a As shown, when Link1 is in normal condition, the receive data queue reads data from Link1, and the first device sequentially receives each service packet from Link1. When data is lost or short-circuited in Link1, the receive data queue reads data from Link2.

[0077] For example, such as Figure 3b As shown, the first device receives service packets with sequence numbers 1, 2, 3 and 4 sequentially from Link1. However, since the service packet with sequence number 5 on Link1 is lost, the first device receives the service packet with sequence number 5 from Link2.

[0078] As another optional implementation, the first service packet is received from the network side link with the earliest arrival time, based on the arrival time of the first service packet on each of the N network side links.

[0079] For ease of description, the configuration mode provided in this embodiment will be referred to as the optimal mode, and an example will be given below. The target network-side links include Link1 and Link2. Data received from both Link1 and Link2 can be primary data and serve as backups for each other. Data is processed according to the first-come-first-served principle based on arrival time and the sequence number of the arriving service packets.

[0080] like Figure 4aAs shown, for a service message with sequence number 5, when the service message arrival time T1 < T2, Link1 arrives before Link2, and the first device receives the service message with sequence number 5 from Link1. For a service message with sequence number 6, as... Figure 4b As shown, when the service message arrives at time T3>T4, Link2 arrives before Link1, and the first device receives the service message with sequence number 6 from Link2.

[0081] Step 202: Determine the second service message based on the first status information.

[0082] The first status information is used to characterize the reception status of the service packets from the second device to the first device, wherein the reception status includes successful reception and reception failure. Upon receiving the service packets from the second device, the first device can determine the reception status of its own sent service packets based on the first status information in the first header, and thus adaptively adjust the transmission of service packets.

[0083] Optionally, in some embodiments, step 202 determines the service message that the second device failed to receive in the service message sent by the first device as the second service message based on the first packet loss identification information.

[0084] If the first device determines, based on the first status information, that a certain service message sent to the second device has not been correctly received, the first device may choose to resend the service message at any time.

[0085] Optionally, in some embodiments, the first status information includes first confirmation identifier information and first packet loss identifier information. The first confirmation identifier 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 identifier information is used to identify the sequence number of the service message that the second device failed to receive in the service message sent by the first device.

[0086] In practice, the first device and the second device continuously transmit service messages bidirectionally, so the number of service messages transmitted between the first device and the second device is usually multiple.

[0087] As an optional implementation, the first confirmation identifier information includes the sequence number of all service messages successfully received by the second device from the first device side, and the first packet loss identifier information includes the sequence number of all service messages that the second device failed to receive from the first device side.

[0088] For example, the first device sends six service messages to the second device, with sequence numbers 0, 1, 2, 3, 4, and 5 respectively. Among them, the service messages with sequence numbers 2 and 4 are not successfully received by the second device. In this embodiment, the first acknowledgment information in the data header associated with the second device sending the service messages to the first device is "0, 1, 3, 5", and the first packet loss information is "2, 4".

[0089] As another optional implementation, the first confirmation identifier information includes a maximum sequence number, which is the maximum value among the sequence numbers of all service packets successfully received by the second device from the first device side. This maximum sequence number is used to indicate that, apart from the sequence number included in the first packet loss identifier information, all service packets corresponding to sequence numbers less than or equal to the maximum sequence number have been successfully received.

[0090] For example, a first device sends six service packets to a second device, with sequence numbers 0, 1, 2, 3, 4, and 5 respectively. Service packets with sequence numbers 2 and 4 are not successfully received by the second device. In this embodiment, the first acknowledgment identifier in the header associated with the service packets sent by the second device to the first device is "5", and the first packet loss identifier is "2" and "4". According to the first acknowledgment identifier, all service packets with sequence numbers less than or equal to 5 (i.e., 0, 1, 3, and 5) except for 2 and 4 are successfully received. The method provided in this embodiment reduces the number of bits occupied by the first acknowledgment identifier, improving resource utilization.

[0091] In this embodiment, the first status information includes first confirmation identifier information and first packet loss identifier information. The first confirmation identifier 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 identifier information is used to identify the sequence number of the service message that the second device failed to receive 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, improving the convenience, accuracy, and efficiency of the first device in determining the reception status of service messages.

[0092] Step 203: Associate the second data header with the second service message. The second data header includes second status information and second sequence identifier information. The second status information is used to characterize the reception status of the first device for the service message sent by the second device, and the second sequence identifier information is used to identify the sequence number of the second service message.

[0093] Since all service messages received by the first device are associated with a data header, the first device can determine whether a service message was not successfully received based on the sequence number of the received service message, and determine the sequence number of the unsuccessfully received service message.

[0094] For example, after the first device has received and stored the service messages with sequence numbers 0, 1, 2, and 3 sent by the second device, it determines that the sequence number of the currently received first service message is 5 through the first data header. At this time, the first device can determine that the service message with sequence number 4 has not been correctly received by combining the sequence number of the successfully received service message and the sequence number of the currently received service message.

[0095] Once the first device determines which service messages were successfully received and which were not, based on the sequence number of the received service messages, it can generate the second status information.

[0096] In some embodiments, the second status information includes second confirmation identifier information and second packet loss identifier information. The second confirmation identifier 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 identifier information is used to identify the sequence number of the service message that the first device failed to receive in the service message sent by the second device.

[0097] After generating the second data header, the second sequence identifier information of the second data header is set as the sequence number of the second service message, thus completing the association between the second data header and the second service message. This enables the second device to determine the sequence number of the second service message and the receiving status of the first device for the first service message after receiving the second service message and the second data header.

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

[0099] Optionally, as an alternative implementation, step 203 includes:

[0100] Add the second data header to the second service message.

[0101] In this embodiment, the second data header is added to the second service message to obtain the target data message.

[0102] The target data packet is sent to the second device via the target network side link.

[0103] In this embodiment, the second data header is inserted into the second service message, becoming part of the service message, thus obtaining the target data message. The specific structure of the second service message can be found in the description in related technologies, and will not be repeated here. In specific implementation, the second data header can be added to any position in the second service message according to actual needs, such as the middle, header, and tail of the Ethernet message.

[0104] For example, the structure of the second service message is as follows: Figure 5a As shown, the second service message includes Media Access Control (MAC), Virtual Local Area Network (VLAN), Multi-Protocol Label Switching (MPLS), Internet Protocol (IP), Payload, and Frame Check Sequence (FCS).

[0105] As an optional implementation, a second data header is added to the header of the service message, resulting in: Figure 5b The target data packet shown is obtained in the form of a second header + ETH. As an alternative implementation, the second header is appended after the IP header, resulting in... Figure 5c The target data packet shown is in the form of ETH+IP+second header+Payload.

[0106] In this embodiment, a second data header is added to the second service packet to obtain the target data packet; the target data packet is then sent to the second device via the target network-side link. By constructing and transmitting the target data packet using the above method, the association between the second data header and the second service packet is strengthened, preventing a situation where only one of the second data header and the second service packet is successfully received. Since this embodiment changes the frame structure at the link layer, the packet processing flow at the link layer will also change accordingly.

[0107] Alternatively, as another optional implementation, step 203 includes:

[0108] Insert the second data header into the free bytes between the second service messages.

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

[0110] In the transmission of service messages, there are idle blocks (or idle bytes) between frames, which are used to transmit the second data header. For example, as shown... Figure 6a As shown, there are 20-bit (bytes) gaps and preambles between ETH messages, such as... Figure 6b As shown, the second data header is transmitted using the frame gap and preamble.

[0111] In this embodiment, a free block is used to transmit the second data header. Transmitting the second data header using free bytes between frames only affects the physical layer processing flow and does not affect the structure of the second service message. This allows the data processing of the second service message to be compatible with existing data processing flows, making the processing more convenient and efficient.

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

[0113] Generate N second data headers that correspond one-to-one with the N network-side links, each second data header including the corresponding link identifier;

[0114] Each of the N second data headers is associated with the second service message;

[0115] Step 204 includes:

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

[0117] Since the target network-side link includes N network-side links, N second data headers need to be generated accordingly to associate them with the second service packets transmitted on each network-side link. Each second data header includes a link identifier to identify which network-side link the second data header was transmitted on.

[0118] After generating N second data headers, the first sequence identifier information included in each of the N second data headers is set as the sequence number of the second service message associated with it, thereby realizing the association between each second data header and the second service message.

[0119] On each network-side link, a second service packet and a second data header are sent respectively, so that the second device can receive the second service packet and the second data header. The method by which the second device receives the second service packet and the second data header can be found in [reference needed]. Figures 3a-4b Some related explanations will not be repeated here.

[0120] 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 on any one network side link, 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.

[0121] In practical applications, the CPE OTN chip supports multi-service access. Different services require different transmission levels. Some services have lower requirements for packet loss rate (such as services with 50ms carrier-grade protection) and do not need to be processed by the method provided in this embodiment.

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

[0123] The target service is determined based on the service identification information;

[0124] Based on the predefined correspondence between services and network-side links, the target network-side link corresponding to the target service is determined.

[0125] It should be understood that the network-side links are pre-configured, and there are multiple of them. Multiple network-side links for CPEOTN services are established through the OTN management platform. The mapping relationship between services and network-side links is pre-defined according to actual service requirements.

[0126] For example, for services that do not require packet processing using the method provided in this embodiment, no corresponding network-side link is allocated, and the process is executed according to the prior art. For services that require packet processing using the method provided in this embodiment, N pre-configured network-side links are determined as the target network-side links corresponding to the service.

[0127] In practice, 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.

[0128] 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 predefined correspondence between the service and the network-side link, thereby transmitting the service message of the first device on the target network-side link.

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

[0130] In this embodiment, a first device receives a first service packet and a first data header sent by a second device via a target network side link. Based on the first status information included in the first data header, the first device can determine the reception status of the service packet sent by the second device by the second device; based on the first sequence identifier information included in the first data header, the first device can also determine the reception status of the service packet sent by the second device by the first device. The first device can promptly determine the transmission and reception status of the service packet, thereby promptly retransmitting failed service packets, improving the transmission reliability of the service packet and reducing the packet loss rate.

[0131] In some embodiments, both the first data header and the second data header are 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, acknowledgment identification information and packet loss identification information;

[0132] The lossless optional delay header is defined as follows: the service identifier information identifies the service flow identifier (ID) corresponding to it; the lossless identifier information identifies whether the service type is lossless; the link identifier information identifies the network-side link ID corresponding to it; the sequence identifier information identifies the sequence number ID of the service packet corresponding to it; the acknowledgment identifier information identifies the sequence number ID of the successfully received service packet; and the packet loss identifier information identifies the sequence number ID of the lost service packet. The structure of the lossless optional delay header is shown in Table 1.

[0133] Table 1 shows an example of the structure of a lossless optional delay data header.

[0134]

[0135] When the lossless optional delay data header is used as the first data header, the sequence identifier information can be understood as the first sequence identifier information, the acknowledgment identifier information can be understood as the first acknowledgment identifier information, and the packet loss identifier information can be understood as the first packet loss identifier information.

[0136] When the lossless optional delay data header is used as the second data header, the sequence identifier information can be understood as the second sequence identifier information, the acknowledgment identifier information can be understood as the second acknowledgment identifier information, and the packet loss identifier information can be understood as the second packet loss identifier information.

[0137] After the first device sends the second service packet and the second data header to the second device through the target network side link, the second device receives the second service packet and the second data header sent by the first device through the target network side link. Based on the second status information, the second device determines the next service packet to be sent, associates the lossless optional delay data header with the service packet, and sends the service packet and the lossless optional delay data header to the first device through the target network side link. The specific method is described above and will not be limited here.

[0138] For ease of understanding, a specific embodiment is used as an example below. When CPE OTN performs multi-service access processing, it supports various interface services (E1, FE, GE, 10GE LAN, STM-1, STM-4, etc.). These various interface services are encapsulated into multi-level containers, cascaded, and then sent to the OTN interface for line-side transmission. For example, the mapping processing flow of the CPE OTN chip's Optical Service Unit (OSU) is as follows: Figure 7 As shown, the service mapping module encapsulates the customer signal into the ODU payload frame, then encapsulates the Optical Channel Transport Unit Overhead (OUT OH) header, performs OTU channel layer processing, and transmits the encapsulated signal. During the encapsulation process, a lossless optional delay function is added to enable rich service options, including lossless time slot forwarding and ultra-low latency processing, achieving more optimized OTN service processing.

[0139] Through the OTN management platform, establish the network-side link for CPE OTN services, specifically as follows: Figure 8 As shown in Table 2, different service types are defined based on the service entry type and service requirements. A service type with 50ms carrier-grade protection can be understood as a normal service, i.e., a service that does not require packet processing using the method provided in this application embodiment. A service type with no packet loss can be understood as a lossless optional latency service, i.e., a service that requires packet processing using the method provided in this application embodiment. Corresponding table entries are set according to the service configuration; see Table 2 for details.

[0140] Table 2. Configuration Table for Lossless Optional Delay Services

[0141] 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 - …… …… …… ……

[0142] In this embodiment, two network-side links, referred to as link1 and link2, are established between the CPE OTN1 chip (referred to as chip A) and the CPE OTN2 chip (referred to as chip B). To enhance protection, link1 and link2 do not share an optical path. By configuring different ODUk, different OTN channels are established and data is sent to different links.

[0143] When a service is created, a corresponding send and receive data stream will be established simultaneously. For example, such as... Figure 9 As shown:

[0144] Create Service 1, corresponding to Send Stream ID1 and Receive Stream ID2, and send and receive on link1 and link2;

[0145] Create service 2, corresponding to sending stream ID3 and receiving stream ID4, and send and receive on link1 and link2.

[0146] Table 3 Example of Lossless Optional Delay Data Header

[0147]

[0148] When the current business message needs to be processed based on the message processing method provided in this application embodiment, the current data stream enables the lossless optional delay function and constructs the lossless optional delay data header as shown in Table 3.

[0149] Please see Figure 10 The processing flow for CPE OTN chips to send service messages is as follows:

[0150] Step A: After receiving the service message, the CPE OTN chip first identifies the flow ID of the service data stream according to the definition and determines whether it is a lossless optional delay service. If not, it performs the original processing of the message according to the existing technology process. If it is, it proceeds to step B.

[0151] Step B: Based on the flow ID of the identified service data stream and the pre-configured correspondence between the service and the network-side link, form a lossless optional delay data header as shown in Table 3;

[0152] Step C: Associate the lossless optional delay data header with the service message according to the predefined position of the lossless optional delay data header;

[0153] Step D: Send the service packets with the associated lossless optional delay headers on the corresponding network-side links (Link1-Linkn). After each service packet is sent (i.e., the service packet is sent on all network-layer links (Link1-Linkn), increment the sequence identifier in the lossless optional delay header of the corresponding service packet by 1. The acknowledgment identifier is the currently received sequence identifier, and the packet loss identifier is the sequence identifier of the packet loss on the current link.

[0154] Please see Figure 11 The processing flow of service messages received by the CPE OTN chip is as follows:

[0155] Upon receiving service packets and associated data headers at Link1 or Link2, if the service is lossless, the following processing is performed; otherwise, the packets are processed according to existing procedures. The flow ID, lossless identifier, and link identifier in the received lossless optional delay data header are used to verify whether the corresponding link and service packet match. The CPE OTN chip stores the received service packets.

[0156] Parse the lossless optional latency data header and service message, and select the configuration mode (e.g.) Figure 3a The fixed pattern shown or Figure 3b The optimal mode shown is detailed above (and will not be repeated here). The corresponding acknowledgment identifier is updated based on the sequence identifier, and this acknowledgment identifier is included in the lossless optional delay header associated with the service message during reverse service transmission.

[0157] Whether packet loss has occurred 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 in the foregoing embodiments and is not limited here.

[0158] During the bidirectional transmission and reception of service messages between chip A and chip B, when chip A acts as the first device executing the method provided in this application embodiment, chip B is the second device corresponding to chip A. Similarly, when chip B acts as the first device executing the method provided in this application embodiment, chip A is the second device corresponding to chip B.

[0159] To facilitate understanding, the interaction process between chip A and chip B will be explained below. Please refer to [link / reference]. Figure 12 A link connection, Link1, is established between chip A (A end) and chip B (B end). Under normal circumstances, the message exchange process between A end and B end is as follows:

[0160] End A: A sends service messages via Link1 and Link2, along with an associated lossless optional delay data header (referred to as the data header). The data header contains the sequence identifier (seq)x, acknowledgment identifier (ack), and loss identifier (lost) of the service message being transmitted. A then 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.

[0161] B: Upon receiving service messages from A via Link1 and Link2, B updates its acknowledgment flag to 'x' based on the sequence number of the received service message, indicating that the service message with sequence number 'x' sent by A was successfully received. Simultaneously, B checks for any lost service messages based on their sequence numbers and updates the 'lost' flag accordingly. The data header associated with the service message sent from B to A includes the sequence number 'y', acknowledgment flag 'x', and 'lost' flag. The data format from B to A is Data + header (seq y, ack x, lost).

[0162] End A: Upon receiving service messages from B via Link1 and Link2, A updates its acknowledgment flag to 'y' based on the sequence number of the received service message, indicating that the service message with sequence number 'y' sent by B was successfully received. Simultaneously, A checks for lost service messages based on their sequence numbers and updates the 'lost' flag accordingly. The data header associated with the service message sent from A to B includes the sequence number 'x+1', the acknowledgment flag 'y', and the 'lost' flag. The data format from A to B is Data + header (seq x+1, ack y, lost).

[0163] Please see Figure 13 Link1 and Link2 are established between A and B. In a packet loss scenario, the message exchange process between A and B is as follows:

[0164] End A: A sends service messages via Link1 and Link2, including the associated data header. A includes the sequence identifier x1, acknowledgment identifier y1, and loss identifier z of the service message being sent in both the data header and the service message header. A then 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).

[0165] B-end: Upon receiving service messages from A via Link1 and Link2, B updates its acknowledgment flag to x1 based on the sequence number of the received service message, indicating that the service message with sequence number x1 sent by A was successfully received. Based on the loss flag z in the data header, B locates message z and retransmits it to A. Simultaneously, B checks for lost messages based on the sequence number of the received service messages and updates the loss flag lost accordingly. The service message sent from B to A is message z, with a data header containing the sequence number z, acknowledgment flag x1, and loss flag lost. The data format from B to A is Data + data header (seq z, ack x1, lost).

[0166] End A: Upon receiving service messages from B via Link1 and Link2, A updates its acknowledgment flag to 'z' based on the sequence number of the received service message. Simultaneously, it checks for lost service messages based on their sequence numbers and updates the lost flag accordingly. The data header associated with the service message sent from B to A includes the sequence number 'x+1', the acknowledgment flag 'z', and the lost flag 'lost'. The data format from A to B is Data + header (seq x1+1, ack z, lost).

[0167] In this embodiment, both chip A and chip B can serve 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 a mapping process from ETH frames to ODUs. By adding a lossless optional delay function and utilizing a transmission protection link, it achieves lossless optional delay forwarding of OTN services, providing more reliable and efficient service transmission for upper-layer services, offering more service function options, and realizing a more cost-effective CPE OTN chip design.

[0168] This invention also provides a message processing apparatus, wherein a first device includes the message processing apparatus. See also... Figure 14 , Figure 14 This is a structural diagram of the message processing device 1400 provided in an embodiment of the present invention. Because the problem-solving principle of the message processing device 1400 is similar to that in the embodiment of the present invention... Figure 2 The message processing method shown is similar, so the implementation of the message processing device 1400 can be found in the implementation of the method, and the repeated parts will not be described again.

[0169] Please see Figure 14 This invention also provides a message processing apparatus 1400, a first device including the message processing apparatus 1400, the message processing apparatus 1400 including:

[0170] The receiving module 1401 is used to receive a first service packet and a first data header sent by a second device through a target network side link. The first data header is associated with the first service packet. The first data header includes first status information and first sequence identifier information. The first status information is used to characterize the receiving status of the second device for the service packet sent by the first device. The first sequence identifier information is used to identify the sequence number of the first service packet.

[0171] The first determining module 1402 is used to determine the second service message based on the first status information;

[0172] The association module 1403 is used to associate the second data header with the second service message. The second data header includes second status information and second sequence identification information. The second status information is used to characterize the reception status of the first device for the service message sent by the second device, and the second sequence identification information is used to identify the sequence number of the second service message.

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

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

[0175] The generation unit is used to generate N second data headers that correspond one-to-one with the N network-side links, and each second data header includes a corresponding link identifier;

[0176] The association unit is used to associate each of the N second data headers with the second service message;

[0177] The sending module 1404 is specifically used for:

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

[0179] Optionally, the first status information includes first confirmation identifier information and first packet loss identifier information. The first confirmation identifier 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 identifier information is used to identify the sequence number of the service message that the second device failed to receive in the service message sent by the first device.

[0180] Optionally, the first determining module 1402 is specifically used for:

[0181] Based on the first packet loss identifier information, the service message that the second device failed to receive in the service message sent by the first device is identified as the second service message.

[0182] Optionally, the first data header further includes service identification information, which is used to characterize the target service corresponding to the first service message. The message processing device 1400 further includes:

[0183] The second determining module is used to determine the target service based on the service identification information;

[0184] The third determining module is used to determine the target network-side link corresponding to the target service based on a predefined correspondence between services and network-side links.

[0185] Optionally, the association module 1403 is specifically used for:

[0186] Add the second data header to the second service message.

[0187] Optionally, the association module 1403 is specifically used for:

[0188] Insert the second data header into the free bytes between the second service messages.

[0189] The message processing apparatus 1400 provided in this embodiment of the invention can achieve Figure 2 The various processes implemented in the method embodiments shown are capable of achieving the same beneficial effects, and will not be described again here to avoid repetition.

[0190] This invention also provides a first device. Because the principle by which the first device solves the problem is similar to that in this invention... Figure 2 The message processing methods shown are similar, so the implementation of the first device can refer to the implementation of the method, and the repeated parts will not be described again.

[0191] like Figure 15 As shown, the first device according to an embodiment of the present invention includes: a processor 1500, configured to read a program from a memory 1520 and execute the following processes:

[0192] The transceiver 1510 receives a first service message and a first data header sent by the second device through the target network side link. The first data header is associated with the first service message. The first data header includes first status information and first sequence identifier information. The first status information is used to characterize the receiving status of the second device in receiving the service message sent by the first device. The first sequence identifier information is used to identify the sequence number of the first service message.

[0193] The second service message is determined based on the first status information;

[0194] The second data header is associated with the second service message. The second data header includes second status information and second sequence identifier information. The second status information is used to characterize the reception status of the first device for the service message sent by the second device, and the second sequence identifier information is used to identify the sequence number of the second service message.

[0195] The transceiver 1510 sends the second service message and the second data header to the second device via the target network side link.

[0196] Transceiver 1510 is used to receive and send data under the control of processor 1500.

[0197] Among them, Figure 15 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, such as one or more processors represented by processor 1500 and memory represented by memory 1520. The bus architecture can also link together various other circuits, such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 1510 can be multiple elements, including transmitters and receivers, providing a unit for communicating with various other devices over a transmission medium.

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

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

[0200] Generate N second data headers that correspond one-to-one with the N network-side links, each second data header including the corresponding link identifier;

[0201] Each of the N second data headers is associated with the second service message;

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

[0203] Optionally, the first status information includes first confirmation identifier information and first packet loss identifier information. The first confirmation identifier 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 identifier information is used to identify the sequence number of the service message that the second device failed to receive in the service message sent by the first device.

[0204] Optionally, the processor 1500 is also used to read the program from the memory 1520 and perform the following steps:

[0205] Based on the first packet loss identifier information, the service message that the second device failed to receive in the service message sent by the first device is identified as the second service message.

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

[0207] The target service is determined based on the service identification information;

[0208] Based on the predefined correspondence between services and network-side links, the target network-side link corresponding to the target service is determined.

[0209] Optionally, the processor 1500 is also used to read the program from the memory 1520 and perform the following steps:

[0210] Add the second data header to the second service message.

[0211] Optionally, the processor 1500 is also used to read the program from the memory 1520 and perform the following steps:

[0212] Insert the second data header into the free bytes between the second service messages.

[0213] The first device provided in this embodiment of the invention can perform the following: Figure 2 The method embodiments shown are similar in principle and technical effect, and will not be described again here.

[0214] This invention also provides a readable storage medium for storing a program, which, when executed by a processor, implements as follows: Figure 2 The steps in the message processing method shown.

[0215] In the several embodiments provided in this application, it should be understood that the disclosed methods and apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0216] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can be physically comprised separately, or two or more units can be integrated into one unit. The integrated unit described above can be implemented in hardware or in the form of hardware plus software functional units.

[0217] The integrated units implemented as software functional units described above can be stored in a computer-readable storage medium. These software functional units, stored in a storage medium, include several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute some steps of the transmission and reception methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0218] The above description represents the preferred embodiments of the present invention. It should be noted that those skilled in the art can make various improvements and modifications without departing from the principles of the present invention, and these improvements and modifications should also be considered within the scope of protection of the present invention.

Claims

1. A method of processing a packet, the method comprising: Applied to a first device, the method comprises: receiving, through a target network sidelink, a first service packet and a first data header sent by a second device, the first data header being associated with the first service packet, the first data header comprising first status information and first sequence identification information, the first status information being used to represent a receiving status of the second device to a service packet sent by the first device, and the first sequence identification information being used to identify a sequence number of the first service packet; determining a second service packet based on the first status information; associating a second data header with the second service packet, the second data header comprising second status information and second sequence identification information, the second status information being used to represent a receiving status of the first device to a service packet sent by the second device, and the second sequence identification information being used to identify a sequence number of the second service packet; sending, through the target network sidelink, the second service packet and the second data header to the second device.

2. The method of claim 1, wherein, The target network sidelink comprises N network sidelinks, N being a positive integer greater than 1. The association of the second data header with the second service packet comprises: generating N second data headers corresponding to the N network sidelinks respectively, each second data header comprising a corresponding link identifier; respectively associating each second data header in the N second data headers with the second service packet; The sending of the second service packet and the second data header to the second device through the target network sidelink comprises: sending, through each network sidelink in the N network sidelinks, the second data header corresponding to the network sidelink and the second service packet to the second device.

3. The method of claim 1, wherein, The first status information comprises first acknowledgement identification information and first packet loss identification information, the first acknowledgement identification information being used to identify a sequence number of a service packet successfully received by the second device in service packets sent by the first device, and the first packet loss identification information being used to identify a sequence number of a service packet unsuccessfully received by the second device in service packets sent by the first device.

4. The method of claim 3, wherein, The determination of the second service packet based on the first status information comprises: determining, based on the first packet loss identification information, a service packet unsuccessfully received by the second device in service packets sent by the first device as the second service packet.

5. The method of claim 1, wherein, The first data header further comprises service identification information, the service identification information being used to represent a target service corresponding to the first service packet, and before the sending of the second service packet and the second data header to the second device through the target network sidelink, the method further comprises: determining the target service based on the service identification information; determining a target network sidelink corresponding to the target service based on a pre-defined correspondence relationship between services and network sidelinks.

6. The method of claim 1, wherein, The association of the second data header with the second service packet comprises: adding the second data header to the second service packet.

7. The method of claim 1, wherein, The association of the second data header with the second service packet comprises: The second data header is inserted into idle bytes between the second service packets.

8. A packet processing device, characterized by, The first device comprises the packet processing apparatus, and the packet processing apparatus comprises: The receiving module is configured to receive, through a target network sidelink, a first service packet and a first data header sent by a second device, the first data header being associated with the first service packet, the first data header comprising first state information and first sequence identification information, the first state information being used to represent a receiving state of the second device for a service packet sent by the first device, and the first sequence identification information being used to identify a sequence number of the first service packet. The first determining module is configured to determine a second service packet based on the first state information. The associating module is configured to associate a second data header with the second service packet, the second data header comprising second state information and second sequence identification information, the second state information being used to represent a receiving state of the first device for a service packet sent by the second device, and the second sequence identification information being used to identify a sequence number of the second service packet. The sending module is configured to send, through the target network sidelink, the second service packet and the second data header to the second device.

9. A first device comprising: The memory, the processor, and a program stored in the memory and capable of running on the processor; and The processor is configured 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, characterized in that, The program, when executed by the processor, implements the steps in the method according to any one of claims 1 to 7.

Images