CN117675078A - Data encoding method, data checking method and related equipment - Google Patents

Data encoding method, data checking method and related equipment Download PDF

Info

Publication number
CN117675078A
CN117675078A CN202211020657.5A CN202211020657A CN117675078A CN 117675078 A CN117675078 A CN 117675078A CN 202211020657 A CN202211020657 A CN 202211020657A CN 117675078 A CN117675078 A CN 117675078A
Authority
CN
China
Prior art keywords
field
target
block
check
overhead
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202211020657.5A
Other languages
Chinese (zh)
Inventor
孙亮
苏伟
郑述乾
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202211020657.5A priority Critical patent/CN117675078A/en
Publication of CN117675078A publication Critical patent/CN117675078A/en
Pending legal-status Critical Current

Links

Landscapes

  • Compression, Expansion, Code Conversion, And Decoders (AREA)

Abstract

The first aspect of the present application provides a data encoding method, which is applied to the field of communication. The data encoding method comprises the following steps: the transmitting device acquires N66-bit encoded blocks. N is an integer greater than 1. The transmitting apparatus compresses the N66-bit encoded blocks into a target encoded block. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The first check field is used to check the first overhead field. The transmitting device maps the target encoded block to a payload region of the data frame. The transmitting device transmits a data frame. According to the data coding scheme disclosed by the application, the overhead field is checked through the check field, so that the reliability of data transmission is improved.

Description

Data encoding method, data checking method and related equipment
Technical Field
The present disclosure relates to the field of communications, and in particular, to a data encoding method, a data verification method, and related devices.
Background
The payload of a 66 bit encoded block in ethernet traffic is 64 bits. When carrying ethernet traffic over an optical transport network (optical transport network, OTN), multiple 66-bit encoded blocks may be compressed to improve transmission efficiency. The compressed target code block deletes the 2-bit overhead in the 66-bit code block, and introduces a new overhead field. The size of the new overhead field is the same as the number of 66-bit encoded blocks comprised by the target encoded block. For example, the compressed target code block is obtained from 4 66-bit code blocks. The new overhead field is 4 bits in size. The 4 bits are used to indicate the type of 4 66-bit coded blocks. The code block type of the 66-bit code block includes a data code block or a control code block.
Disclosure of Invention
The application provides a data coding method, a data checking method and related equipment, wherein the reliability of data transmission can be improved by checking a first overhead field through a first checking field.
A first aspect of the present application provides a data encoding method. The data encoding method comprises the following steps: the transmitting device acquires N66-bit encoded blocks. The transmitting device may be an optical transport network (optical transport network, OTN) device or a metropolitan transport network (metro transport network, MTN) device, etc. N is an integer greater than 1. The transmitting apparatus compresses the N66-bit encoded blocks into a target encoded block. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The first check field is used to check the first overhead field. The transmitting device maps the target encoded block to a payload region of the data frame. The transmitting device transmits a data frame. The data frames may be OTN frames, flexible ethernet (flexible ethernet, flexE) frames, or MTN frames.
In an alternative form of the first aspect, the N66-bit encoded blocks include a first 66-bit encoded block. The first 66-bit coded block is of the control coded block type. The first 66-bit encoded block includes an f field, an s field, and a c field. The target coding block includes an f field and a c field. The first check field is also used to check the f-field. The f-field may also generate errors. By checking the f field through the first check field, the reliability of the transmission data can be improved.
In an alternative form of the first aspect, the first check field comprises a first check subfield and a second check subfield. The first check subfield is used to check the first overhead field. The second check subfield is used to check the f field. By the independent verification, the sequence of the N66-bit coding blocks in the target coding block can be omitted, so that the compression efficiency is improved.
In an alternative form of the first aspect, the f-field and the first overhead field are located adjacent. The sizes of the f field and the first overhead field may be different. When the f field and the first overhead field are adjacent, the first overhead field may be used to integrally check the f field and the first overhead field, thereby improving reliability of the check.
In an alternative form of the first aspect, the target coding block further comprises a second overhead field and a second parity field. The second overhead field is used to indicate whether the target coding block includes a control coding block. The second check field is used to check the second overhead field. The second overhead field may also generate errors. By checking the second overhead field through the second check field, the reliability of the transmission data can be improved.
In an alternative form of the first aspect, the second check field has a size of 1 bit and the second overhead field has a size of 1 bit.
In an alternative form of the first aspect, in one form, N is 4. The target coding block size is 260 bits. The first overhead field is 4 bits in size. The size of the first check field is 2 bits. In another mode, N is 2. The target coding block is 130 bits in size. The size of the f field is 4 bits. The first overhead field is 2 bits in size. The size of the first check field is 2 bits.
In an alternative form of the first aspect, N is an integer multiple of 2. The transmitting device compresses the N66-bit encoded blocks into N/2 target subcode blocks. Each target subcode block corresponds to 2 66-bit code blocks. Each target subcode block includes a second overhead field. The second overhead field is used to indicate whether each target sub-coded block includes a control coded block. The transmitting apparatus compresses the N/2 target sub-coded blocks into target coded blocks. The target coding block includes a second check field. The second check field is used to check N/2 second overhead fields. The second overhead field may also generate errors. By checking the second overhead field through the second check field, the reliability of the transmission data can be improved.
In an alternative form of the first aspect, the second check field has a size of 1 bit. Each target subcode block has a size of 129 bits. The size of the N/2 second overhead fields is N/2 bits.
In an alternative form of the first aspect, in one form, N is 4. The target coding block is 259 bits in size. The first overhead field is 4 bits in size. The first check field has a size of 4 bits. In another embodiment, N is 8. The size of the target coding block is 520 bits. The first overhead field and the first check field are each 8 bits in size.
In an alternative form of the first aspect, the first check field is used to check the target encoded block. The target coding block is integrally checked through the first check field, so that the change of the target coding block can be reduced, and the compatibility of different devices for checking data is improved.
In an alternative form of the first aspect, the payload region of the data frame is divided into a plurality of time slots, each time slot having a size equal to the size of the target coding block. The transmitting device maps the target encoded block to a time slot of the payload region. By directly mapping the target coding block to the slot, overhead may be reduced, thereby improving transmission efficiency.
In an alternative form of the first aspect, the data encoding method further comprises the steps of: the transmitting device acquires another target encoded block. The transmitting device maps another target encoded block to a traffic frame. The traffic frames may be optical traffic unit (optical service unit, OSU) frames or other data frames resembling OSU frame structures. The transmitting device maps the traffic frame to a time slot of a payload region of the data frame. The time slots in which the target encoded block is directly mapped to the data frame are direct mappings. The mapping of the target encoded block to the data frame by the traffic frame is an indirect mapping. Through the hybrid mapping, compatibility with different devices can be improved.
In an alternative form of the first aspect, the transmitting device maps the target encoded block to a traffic frame and maps the traffic frame to a payload region of the data frame. By introducing service frames, flexibility in service management can be improved.
A second aspect of the present application provides a data verification method. The data verification method comprises the following steps: the receiving device receives a data frame. The receiving device extracts the target encoded block from the payload region of the data frame. The target code block is compressed from N66 bit code blocks. N is an integer greater than 1. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The receiving device verifies the first overhead field by means of the first check field.
In an alternative form of the second aspect, the target coding block includes an f-field and a c-field. The data verification method comprises the following steps: the receiving device checks the f-field by the first check field.
In an alternative form of the second aspect, the first check field comprises a first check subfield and a second check subfield. The receiving device verifies the first overhead field by means of the first syndrome field. The receiving device checks the f-field through the second check subfield.
In an alternative form of the second aspect, the f field is located adjacent to the first overhead field. The receiving device integrally verifies the first overhead field and the f field through the first verification field.
In an alternative form of the second aspect, the target coding block further comprises a second overhead field and a second parity field. The second overhead field is used to indicate whether the target coding block includes a control coding block. The data verification method further comprises the following steps: the receiving device verifies the second overhead field by means of the second check field.
Regarding the size of the first overhead field, the first check field, the second check field and the second overhead field, N, the target coding block, the target sub-coding block and/or the f field may be referred to the alternatives of the first aspect. Here, the description is omitted.
In an alternative form of the second aspect, the receiving device verifies the target encoded block by means of the first verification field.
In an alternative form of the second aspect, the payload section of the data frame is divided into a plurality of time slots. The size of each slot is equal to the size of the target coding block. The target encoded block is located in a time slot of a payload region of the data frame.
In an alternative form of the second aspect, the data verification method further includes the steps of: the receiving device extracts the traffic frame from the payload region of the data frame. The traffic frame includes another target encoded block.
In an alternative form of the second aspect, the receiving device extracts the traffic frame from a payload region of the data frame. The traffic frame includes a target coding block.
A third aspect of the present application provides a transmitting apparatus. The transmitting device comprises an acquisition module, a compression module, a mapping module and a transmitting module. The acquisition module is used for acquiring N66-bit coding blocks. N is an integer greater than 1. The compression module is used for compressing the N66-bit coding blocks into a target coding block. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The first check field is used to check the first overhead field. The mapping module is used for mapping the target coding block to a payload area of the data frame. The sending module is used for sending the data frame.
In an alternative form of the third aspect, the payload region of the data frame is divided into a plurality of time slots, each time slot having a size equal to the size of the target coding block. The mapping module is used for mapping the target coding block to the time slot of the payload area.
In an alternative manner of the third aspect, the obtaining module is further configured to obtain another target coding block. The mapping module is also used for mapping another target coding block to the service frame. The mapping module is further configured to map the traffic frame to a time slot of a payload region of the data frame.
In an alternative form of the third aspect, the mapping module is configured to map the target encoded block to a traffic frame and map the traffic frame to a payload region of the data frame. For a description of a data frame reference may be made to the preceding first aspect or to the description in any of the alternatives of the first aspect.
A fourth aspect of the present application provides a receiving apparatus. The receiving device comprises a receiving module, an extracting module and a checking module. The receiving module is used for receiving the data frame. The receiving module is used for receiving the data frame. The extraction module is used for extracting a target coding block from a payload area of the data frame. The target code block is compressed from N66 bit code blocks. N is an integer greater than 1. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The checking module is used for checking the first overhead field through the first checking field.
In an alternative form of the fourth aspect, the target coding block includes an f-field and a c-field. The verification module is also used for verifying the f field through the first verification field.
In an alternative form of the fourth aspect, the first check field comprises a first check subfield and a second check subfield. The checking module is used for checking the first overhead field through the first checking sub-field. The checking module is used for checking the f field through the second checking sub-field.
In an alternative form of the fourth aspect, the target coding block further comprises a second overhead field and a second parity field. The second overhead field is used to indicate whether the target coding block includes a control coding block. The checking module is further configured to check the second overhead field with the second check field.
In an alternative form of the fourth aspect, N is an integer multiple of 2. The target coding block includes N/2 target sub-coding blocks. Each target subcode block corresponds to 2 66-bit code blocks. Each target subcode block includes a second overhead field. The second overhead field is used to indicate whether each target sub-coded block includes a control coded block. The target coding block includes N/2 second check fields. The checking module is further configured to check the second overhead field with the second check field.
In an alternative form of the fourth aspect, reference may be made to the description of the first aspect or any of the alternative forms of the first aspect.
A fifth aspect of the present application provides a transmitting apparatus. The transmitting device includes a processor and a transceiver. The processor is configured to perform the method of the first aspect or any of the alternatives of the first aspect to obtain a data frame. The transceiver is configured to transmit a data frame.
A sixth aspect of the present application provides a receiving apparatus. The transmitting device includes a processor and a transceiver. The transceiver is configured to receive a data frame. The processor is configured to extract a target encoded block in a payload region of a data frame. The processor is further configured to perform the method of the second aspect or any of the alternatives of the second aspect to verify the content in the target encoded block.
A seventh aspect of the present application provides a communication system. The communication system includes a transmitting device and a receiving device. The transmitting device is configured to obtain N66-bit encoded blocks. N is an integer greater than 1. The transmitting device is configured to compress the N66-bit encoded blocks into a target encoded block. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The transmitting device is configured to map the target encoded block to a payload region of the data frame. The transmitting device is configured to transmit a data frame. The receiving device is configured to receive a data frame. The receiving device is configured to extract a target encoded block from a payload region of a data frame. The receiving device is configured to check the first overhead field with the first check field.
In an alternative form of the seventh aspect, the transmitting device is further configured to perform the method as described in the foregoing first aspect or any one of the alternatives of the first aspect, and/or the receiving device is further configured to perform the method as described in the foregoing second aspect or any one of the alternatives of the second aspect.
An eighth aspect of the present application provides a data frame. The data frame includes a payload region and an overhead region. The payload region includes the target encoded block. The target code block is compressed from N66 bit code blocks. N is an integer greater than 1. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The first check field is used to check the first overhead field.
In an alternative form of the eighth aspect the N66-bit encoded blocks comprise the first 66-bit encoded block. The first 66-bit coded block is of the control coded block type. The first 66-bit encoded block includes an f field, an s field, and a c field. The target coding block includes an f field and a c field. The first check field is also used to check the f-field.
In an alternative form of the eighth aspect, the first check field includes a first check subfield and a second check subfield. The first check subfield is used to check the first overhead field. The second check subfield is used to check the f field.
In an alternative form of the eighth aspect, the f field is located adjacent to the first overhead field.
In an alternative of the eighth aspect, the target coding block further comprises a second overhead field and a second parity field. The second overhead field is used to indicate whether the target coding block includes a control coding block. The second check field is used to check the second overhead field.
In an alternative of the eighth aspect, the size of the second check field is 1 bit and the size of the second overhead field is 1 bit.
In an alternative form of the eighth aspect, in one form, N is 4. The target coding block size is 260 bits. The first overhead field is 4 bits in size. The size of the first check field is 2 bits. In another mode, N is 2. The target coding block is 130 bits in size. The size of the f field is 4 bits. The first overhead field is 2 bits in size. The size of the first check field is 2 bits.
In an alternative form of the eighth aspect, N is an integer multiple of 2. The target coding block includes N/2 target sub-coding blocks. Each target subcode block corresponds to 2 66-bit code blocks. Each target subcode block includes a second overhead field. The second overhead field is used to indicate whether each target sub-coded block includes a control coded block. The target coding block includes a second check field. The second check field is used to check N/2 second overhead fields.
In an alternative of the eighth aspect, the size of the second check field is 1 bit. Each target subcode block has a size of 129 bits. The size of the N/2 second overhead fields is N/2 bits.
In an alternative form of the eighth aspect, in one form, N is 4. The target coding block is 259 bits in size. The first overhead field is 4 bits in size. The first check field has a size of 4 bits. In another embodiment, N is 8. The size of the target coding block is 520 bits. The first overhead field is 8 bits in size. The first check field has a size of 8 bits.
In an alternative form of the eighth aspect, the first check field is used to check the target encoded block.
In an alternative form of the eighth aspect, the payload section of the data frame is divided into a plurality of time slots, each time slot having a size equal to the size of the target coding block. The target coding block is located in a slot of the payload area.
In an alternative form of the eighth aspect, the payload area of the data frame further comprises a traffic frame. The payload area in the traffic frame includes another target encoded block.
In an alternative form of the eighth aspect, the payload region of the data frame comprises a traffic frame. The payload area of the traffic frame includes the target encoded block.
It will be appreciated that there are relevant aspects to the various aspects described above. Thus, the description of the alternatives of any aspect may be taken as an matter of alternatives of other aspects, and the description is not repeated here.
A ninth aspect of the present application provides a computer storage medium. The computer storage medium having instructions stored therein, which when executed on a computer, cause the computer to perform the method according to the first aspect or any implementation of the first aspect; or cause the computer to perform the method according to the second aspect or any one of the embodiments of the second aspect.
A tenth aspect of the present application provides a computer program product. The computer program product, when executed on a computer, causes the computer to perform the method according to the first aspect or any implementation of the first aspect; or cause the computer to perform the method according to the second aspect or any one of the embodiments of the second aspect.
Drawings
Fig. 1 is a schematic structural diagram of an OTN provided in the present application;
fig. 2 is a schematic structural diagram of an OTN device provided in the present application;
fig. 3 is a schematic diagram of the structure of a data encoding block and a control encoding block;
fig. 4a is a schematic diagram of a first structure of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 4b is a second schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
Fig. 4c is a third schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 5a is a fourth schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 5b is a fifth schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 5c is a sixth schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 5d is a seventh structural schematic diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 6 is a first schematic structural diagram of a target coding block according to an embodiment of the present application;
FIG. 7a is a first block diagram of a plurality of 129 fields and target code blocks provided in an embodiment of the present application;
FIG. 7b is a second block diagram of a plurality of 129 fields and target code blocks provided in an embodiment of the present application;
fig. 8a is a first schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 8b is a second schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 8c is a third schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
Fig. 8d is a fourth schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 9a is an eighth schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 9b is a fifth schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application;
fig. 10 is a second schematic structural diagram of a target coding block according to an embodiment of the present application;
fig. 11 is a flow chart of a data encoding method according to an embodiment of the present application;
FIG. 12a is a flow chart of direct mapping provided in an embodiment of the present application;
FIG. 12b is a flow chart of indirect mapping provided by an embodiment of the present application;
FIG. 12c is a schematic flow chart of hybrid mapping according to an embodiment of the present disclosure;
fig. 13 is a flow chart of a data verification method according to an embodiment of the present application;
fig. 14 is a schematic structural diagram of a transmitting device according to an embodiment of the present application;
fig. 15 is a schematic structural diagram of a receiving device according to an embodiment of the present application;
fig. 16 is a schematic structural diagram of a communication device according to an embodiment of the present application;
fig. 17 is a schematic structural diagram of a communication system according to an embodiment of the present application.
Detailed Description
First, some terms in this application are explained for easy understanding by those skilled in the art.
1) Two or more fingers. And/or describes the association relationship of the association object, three relationships may exist. For example, a and/or B may represent: a exists alone, A and B exist together, and B exists alone. In addition, in the description of the present application, the words "first," "second," "target," and the like are used solely for the purpose of distinguishing between descriptions and not necessarily for indicating or implying a relative importance or order.
2) Mapping a to B referred to herein refers to encapsulating a into B. For example, mapping an optical service unit (optical service unit, OSU) frame to an OTN frame refers to encapsulating the OSU frame or OSU signal into the OTN frame.
3) Unless specifically stated otherwise, a specific description of one feature in one embodiment may also be applied to explaining the corresponding feature in other embodiments. For example, the size and function of the check field of the target encoding field in one embodiment may also be applied to the check fields mentioned in other embodiments. Furthermore, to more clearly illustrate the relationship of components in different embodiments, the present application uses the same or similar reference numbers to indicate functionally the same or similar components or method steps in different embodiments.
4) "checking" includes "detecting" and/or "correcting" errors. For example, checking the overhead field by the check field means that the check field detects and/or corrects errors in the overhead field. "detect" means that the receiving device can determine whether an error is present in the overhead field. "error correction" means that the receiving device can determine and correct the bit errors present in the overhead field.
The embodiment of the application is suitable for optical networks such as an optical transport network or a metropolitan transport network. The optical transport network comprises an OTN or a flexible ethernet (flexible ethernet, flexE). In the description subsequent to the present application, description will be made taking OTN as an example. An OTN is typically formed by connecting a plurality of OTN devices through optical fibers, and may be configured into different topology types such as linear, ring, mesh, etc. according to specific needs. Fig. 1 is a schematic structural diagram of an OTN provided in the present application. As shown in fig. 1, the OTN 100 is composed of 8 OTN devices 101, i.e., OTN devices a to H. Wherein 102 indicates an optical fiber for connecting two devices. 103 indicates a customer service interface for receiving or transmitting customer service data. As shown in fig. 1, the OTN 100 is used to transmit traffic data for the client devices 1-3. The client device is connected with the OTN device through the client service interface. For example, in FIG. 1, client devices 1-3 are connected to OTN devices A, H and F, respectively.
One OTN device may have different functions. Generally, OTN devices are classified into optical layer devices, electrical layer devices, and opto-electronic hybrid devices. An optical layer device refers to a device capable of processing an optical layer signal, such as: an optical amplifier (optical amplifier, OA), an optical add-drop multiplexer (OADM). OA may also be referred to as optical line amplifiers (optical line amplifier, OLA), and is primarily used to amplify optical signals to support transmission over greater distances while ensuring specific performance of the optical signals. OADM is used to spatially transform an optical signal so that it may be output from different output ports (sometimes also referred to as directions). An electrical layer device refers to a device capable of processing an electrical layer signal, such as: a device capable of processing OTN signals. An opto-electronic hybrid device refers to a device that has the capability to process both optical layer signals and electrical layer signals. It should be noted that, depending on the specific integration requirement, one OTN device may integrate a plurality of different functions. The technical scheme provided by the application is suitable for OTN equipment with different forms and integration levels and containing an electric layer function.
It should be noted that, the data frame structure used by the optical transmission device in the embodiment of the present application may be an OTN frame. The OTN frame is used to carry various service data and provide rich management and monitoring functions. The OTN frame may be an optical data unit frame (optical data unit k, ODUk), ODUCn, ODUflex, or an optical channel transmission unit k (optical transport unit k, OTUk), OTUCn, or flexible OTN (FlexO) frame, or the like. Wherein, the OTU frame includes an ODU frame and an OTU overhead. k represents different rate levels. For example, k=1 represents 2.5Gbps, and k=4 represents 100Gbps. Cn represents a variable rate, in particular a rate that is a positive integer multiple of 100Gbps. Unless specifically stated, an ODU frame refers to any one of ODUk, ODUCn, or ODUflex, and an OTU frame refers to any one of OTUk, OTUCn, or FlexO. It should also be noted that with the development of optical transport network technology, new types of OTN frames may be defined, and are also suitable for the present application. In addition, the method disclosed by the application can be also applied to other optical transport network frames such as FlexE frames.
Fig. 2 is a schematic structural diagram of an OTN device provided in the present application. The OTN device 200 may be any one of the OTN devices a-H in fig. 1. As shown in fig. 2, the OTN device 200 includes a tributary board 201, a cross board 202, a circuit board 203, an optical layer processing board (not shown in the figure), and a system control and communication class board 204.
The tributary board 201, the cross board 202 and the wiring board 203 are used for processing the electrical layer signals. The tributary board 201 is used to implement receiving and transmitting of various customer services, such as SDH services, packet services, ethernet services, and/or forwarding services, etc. Still further, the tributary board 201 may be divided into a client side transceiver module and a signal processor. The client-side transceiver module may also be referred to as an optical transceiver, for receiving and/or transmitting traffic data. The signal processor is used for realizing the mapping and demapping processing of the business data to the data frame. The cross board 202 is used to implement exchange of data frames, and exchange of one or more types of data frames is completed. The line board 203 mainly realizes processing of line-side data frames. Specifically, the wiring board 203 may be divided into a line-side optical module and a signal processor. The line-side optical module may be referred to as an optical transceiver, for receiving and/or transmitting data frames. The signal processor is used for multiplexing and demultiplexing data frames at the line side or mapping and demapping processing. The system control and communication class board 204 is used to implement system control. Specifically, information may be collected from different boards, or control instructions may be sent to corresponding boards. It should be noted that, unless specifically stated otherwise, a specific component (e.g., a signal processor) may be one or more, and the present application is not limited. It should also be noted that the present application does not limit the type of boards included in the device and the functional design and number of boards. It should be noted that, in a specific implementation, the two boards may also be designed as one board. In addition, the network device may also include a backup power source, a fan for dissipating heat, and the like.
It should be understood that fig. 2 is only one example of an OTN device provided in the present application. The OTN devices may contain different types and numbers of boards depending on the particular needs. For example, an OTN device as a core node does not have the tributary board 201. As another example, an OTN device as an edge node has multiple tributary boards 201, or no optical cross boards 202. For another example, an OTN device that supports only electrical layer functions may not have an optical layer processing board.
In the foregoing fig. 1, the data received by the OTN device from the client device may be 66-bit encoded blocks. The 66-bit encoded blocks are also referred to as 64B/66B encoded blocks or 66-bit encoded blocks. The code block type of the 66-bit code block includes a data code block or a control code block. The data encoding block is used for carrying data. The control coding block is used for transmitting control information such as a start or end of frame identification of a medium access control (media access control, MAC) address or an idle filling instruction. Fig. 3 is a schematic diagram of the structure of a data encoding block and a control encoding block. As shown in fig. 3, the data encoding block 301 and the control encoding block 302 include a Synchronization (SYNC) field. The SYNC field is 2 bits in size. The SYNC field carries data indicating the code block type of the 66 bit encoded block. For example, 01 indicates that the code block type of the 66-bit code block is a data code block. 10 indicates that the code block type of the 66-bit code block is a control code block. The data encoding block 301 further includes a d field for carrying data; the size is 64 bits. The control coding block 302 also includes an f field, an s field, and a c field. The size of both the f field and the s field is 4 bits. The f field and the s field are block type fields that control the encoded block 302. The value of the block type field may be 0x1E, 0x78, 0x4B, 0x87, 0x99, or the like. The f field may be the first 4 bits in the block type field. The s field may be the last 4 bits in the block type field. The size of the c field is 56 bits for carrying control codes.
In the following examples, to distinguish the d field in different encoded blocks, the d field may represent a d_0 field, a d_1 field, a d_2 field, or the like. Similarly, to distinguish the f, s, and c fields in different encoded blocks, the f, s, and c fields may also be represented in a similar manner.
The present application describes data frames provided in the present application using OTN as an example. In particular, the data frame may be an OTN frame or an OPU frame. The OTN device maps 66-bit encoded blocks to data frames. In order to improve transmission efficiency, the OTN device may compress a plurality of 66-bit encoding blocks to obtain a target encoding block. The OTN device maps the target encoded block to a data frame. However, the target coding block may introduce a new overhead field. The new overhead field may generate errors, thereby reducing the reliability of the transmission of the target encoded block.
To this end, the present application provides a data frame. The data frames may be OTN frames, OPU frames, flexE frames, MTN frames, or the like. The data frame includes a payload region and an overhead region. The payload area is used to carry the target encoded block. The target coding block is obtained by compressing N66-bit coding blocks by a transmitting device, wherein N is an integer greater than 1. The transmitting device may be the OTN device in fig. 1. The following description will take N equal to 2 as an example. The distribution of control code blocks and data code blocks among different target code blocks may be different. This will be described separately below.
Fig. 4a is a schematic diagram of a first structure of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 4a, 2 66-bit encoded blocks 401 include 1 data encoded block and 1 control encoded block. The SYNC field of the data encoding block is 01. The data encoding block further includes a d_0 field. The SYNC field of the control code block is 10. The control coding block also includes an f_1 field, an s_1 field, and a c_1 field. The compressed target encoded block 402 includes a d_0 field, an f_1 field, and a c_1 field. The target encoding block 402 also includes a first overhead field and a first check field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. For example, in fig. 4a, the first overhead field has a size of 2 bits. The first overhead field is 10. "1" means that the first 66-bit encoded block is a data encoded block. "0" means that the second 66-bit code block is a control code block. For convenience of description, in the present embodiment, "first" or "second" or the like indicates a position of a 66-bit encoding block in a target encoding block. The P field in fig. 4a represents a first check field. The first check field is used to check the first overhead field. The size of the first check field may be 1 bit or 2 bits.
In the embodiment of the present application, the size of the target coding block obtained after compression is smaller than the size of N66-bit coding blocks. For example, in fig. 4a, N66-bit encoded blocks 401 are 132 bits in size. When the size of the first check field is 2 bits, the size of the target encoding block 402 is 128 bits. In the subsequent examples, the size of the first check field will be described as an example of 2 bits.
Fig. 4b is a second schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 4b, the 2 66-bit encoding blocks 403 include 1 control encoding block and 1 data encoding block. The SYNC field of the control code block is 10. The control coding block further includes an f_0 field, an s_0 field, and a c_0 field. The SYNC field of the data encoding block is 01. The data encoding block further includes a d_1 field. The compressed target encoded block 404 includes a d_1 field, an f_0 field, and a c_0 field. The target encoding block 404 also includes a first overhead field and a first check field. For example, in fig. 4b, the first overhead field is 2 bits in size. The first overhead field is 01. "0" means that the first 66-bit code block is a control code block. "1" means that the second 66-bit encoded block is a data encoded block. The P field in fig. 4b represents a first check field. The first check field is used to check the first overhead field.
In practice, the N66-bit code blocks may include a plurality of control code blocks. In order to ensure that the target code blocks are the same size in different scenarios, the transmitting device may compress only one of the control code blocks, i.e. delete only the s field in one control code block.
Fig. 4c is a third schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 4c, the 2 66-bit encoded blocks 405 include 2 control encoded blocks. The SYNC field of the control code block is 10. The first control coding block also includes three fields f_0, s_0, and c_0. The second control coding block also includes three fields f_1, s_1, and c_1. The compressed target encoded block 406 includes five fields f_0, c_0, f_1, s_1, and c_1. The target encoding block 406 also includes a first overhead field and a first check field. For example, in fig. 4c, the first overhead field is 00, indicating that the first and second 66-bit encoded blocks are control encoded blocks. The P field in fig. 4c represents a first check field. The first check field is used to check the first overhead field.
In practical applications, the N66-bit encoded blocks may not include control encoded blocks. When the control code block is not included, the transmitting apparatus cannot compress the N66-bit code blocks through the s field. In order to determine whether the target coding block includes a control coding block, the target coding block may further include a second overhead field. The second overhead field is used to indicate whether the N66-bit coded blocks or the target coded block include a control coded block.
Fig. 5a is a fourth schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 5a, the target encoding block 502 further includes a second overhead field on the basis of fig. 4 a. The second overhead field has a size of 1 bit. The second overhead field is 1, indicating that the N66-bit encoded blocks 401 or the target encoded block 502 comprise control encoded blocks.
Fig. 5b is a fifth schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 5b, the target encoding block 504 further includes a second overhead field on the basis of fig. 4 b. The second overhead field has a size of 1 bit. The second overhead field is 1. "1" indicates that the N66-bit encoding blocks 403 or the target encoding block 504 include control encoding blocks.
Fig. 5c is a sixth schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 5c, the target encoding block 505 further includes a second overhead field on the basis of fig. 4 c. The second overhead field has a size of 1 bit. The second overhead field is 1. "1" indicates that the N66-bit encoded blocks 405 or the target encoded block 504 include control encoded blocks.
Fig. 5d is a seventh structural schematic diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 5d, 2 66-bit encoded blocks 501 comprise 2 data encoded blocks. The SYNC field of the data encoding block is 01. The first data encoding block further includes a d_0 field. The second data encoding block further includes a d_1 field. The compressed target encoded block 503 includes a d_0 field and a d_1 field. The target encoding block 503 also includes a second overhead field. In fig. 5d, the size of the second overhead field is 1 bit. The second overhead field is 0. "0" indicates that the N66-bit encoding blocks 501 or the target encoding block 503 do not include a control encoding block.
It should be appreciated that in the foregoing embodiments of fig. 5 a-5 d, a value of "1" for the second overhead field indicates that the N66-bit encoding blocks or target encoding blocks comprise control encoding blocks. The second overhead field "0" indicates that the N66-bit encoding blocks or the target encoding block does not include a control encoding block. In practical applications, the second overhead field "0" may also indicate that N66-bit encoding blocks or target encoding blocks include control encoding blocks. At this time, the second overhead field "1" indicates that the N66-bit encoding blocks or the target encoding block does not include the control encoding block. In the foregoing embodiments of fig. 4 a-4 c, the target coding block size is 128 bits when the first check field and the first overhead field are both 2 bits in size. In the foregoing fig. 5a to 5d, when the size of the second overhead field is 1 bit, the size of the target coding block is 129 bits. In the following example, the size of the second overhead field will be described as 1 bit.
In practical applications, the second overhead field may also generate errors, thereby reducing the reliability of the transmission target encoded block. To this end, the target coding block may further comprise a second check field. The second check field is used to check the second overhead field. Fig. 6 is a schematic diagram of a first structure of a target coding block according to an embodiment of the present application. As shown in fig. 6, the target encoding block 601 includes a Q field and a 129 field. The 129 field includes an F field and a 128 field. The F field is also referred to as a second overhead field. The Q field is also referred to as a second check field. The second check field is used to check the second overhead field. The size of the second check field may be 1 bit. In the subsequent example, the size of the second check field will be described as an example of 1 bit. The 129 field is any one of the target code blocks 502-505. Thus, for the description of the 129 field, reference may be made to the description in any of the preceding figures 5 a-5 d.
In practical applications, to obtain target encoded blocks of different sizes, the transmitting device may combine the 129 fields and check the second overhead fields by one second check field. The following describes each by taking the case where the transmitting apparatus combines 2 or 4 129 fields.
Fig. 7a is a first structural diagram providing a plurality of 129 fields and target coding blocks according to an embodiment of the present application. As shown in fig. 7a, the plurality of 129 fields 701 includes a first 129 field and a second 129 field. The first 129 field includes an F1 field. The second 129 field includes an F2 field. The F1 field is the second overhead field of the first 129 field. The F2 field is the second overhead field of the second 129 field. The target encoding block 702 includes a plurality of 129 fields 701 and Q fields. The Q field is used to check the F1 and F2 fields. The size of the Q field may be 1 bit. At this time, the size of the target coding block 702 is 259 bits.
Fig. 7b is a second structural diagram of providing a plurality of 129 fields and target coding blocks according to an embodiment of the present application. As shown in fig. 7b, the plurality of 129 fields 703 includes 4 129 fields. The 4 129 fields include respective F fields, e.g., the first 129 field includes an F1 field. The target encoding block 704 includes 4 129 fields and a Q field. The Q field is used to check 4F fields. The size of the Q field may be 4 bits. At this time, the size of the target encoding block 704 is 520 bits.
In the foregoing fig. 5a to 5d, N is equal to 2. In practical applications, N may also be other values, such as 4 or 8. The following description will take N equal to 4 as an example.
Fig. 8a is a schematic diagram of a first structure of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 8a, the 4 66-bit encoded blocks 801 include 3 data encoded blocks and 1 control encoded block. The SYNC field of the data encoding block is 01. The 3 data encoding blocks also include d_0, d_1, and d_2 fields, respectively. The SYNC field of the control code block is 10. The control coding block also includes f_3, s_3, and c_3 fields. The compressed target encoded block 802 includes d_0, d_1, d_2, f_3, and c_3 fields. The target encoding block 802 also includes a second overhead field and a second check field (Q field). The second overhead field is located between the Q field and the P field. The second check field is used to check the second overhead field. The second overhead field has a size of 1 bit. The second overhead field is 1. "1" indicates that the control coding block is included in the 4 66-bit coding blocks 801 or the target coding block 802. The target encoding block 802 also includes a first overhead field and a first check field (P field). The first overhead field is 4 bits in size. The first overhead field is 1110. "111" means the first to third 66-bit encoded blocks are data encoded blocks. "0" means that the fourth 66-bit code block is a control code block.
Fig. 8b is a second schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 8b, the 4 66-bit encoding blocks 803 include 1 control encoding block and 3 data encoding blocks. The SYNC field of the control code block is 10. The control coding block also includes f_0, s_0, and c_0 fields. The SYNC field of the data encoding block is 01. The 3 data encoding blocks also include d_1, d_2, and d_3 fields, respectively. The compressed target encoded block 804 includes d_1, d_2, d_3, f_0, and c_0 fields. Similarly, the target encoding block 804 also includes a second overhead field, a second check field (Q field), a first overhead field, and a first check field (P field). The first overhead field is 0111.
Fig. 8c is a third schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 8c, the 4 66-bit encoded blocks 805 include 4 control encoded blocks. The SYNC field of the control code block is 10. Each control code block also includes a respective f-field, s-field, and c-field. The compressed target encoded block 806 does not include an s_0 field. The target encoding block 806 also includes a second overhead field, a second check field (Q field), a first overhead field, and a first check field (P field). The first overhead field is 0000.
Fig. 8d is a fourth schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 8d, the 4 66-bit encoded blocks 807 include 4 data encoded blocks. The SYNC field of the data encoding block is 01. The 4 data encoding blocks also include d_0, d_1, d_2, and d_3 fields, respectively. The compressed target encoding block 808 includes d_0, d_1, d_2, and d_3 fields. The target encoding block 808 also includes a second overhead field and a second check field (Q field). The second overhead field is 0. "0" means that the 4 66-bit encoding blocks 807 or the target encoding block 808 do not include a control encoding block. The target encoding block 808 also includes a TC field. The TC field is used to fill data such that the size of the target encoding block 808 is the same as the size of the target encoding block 802, the target encoding block 804, or the target encoding block 806.
In the foregoing fig. 8a to 8d, the size of the first check field may be 1 bit or 2 bits. When the sizes of the first and second check fields are both 1 bit, the size of the target coding block 802, 804, or 806 is 259 bits. When the size of the TC field is 1 bit, the size of the target encoding block 808 is 259 bits. When the sizes of the first and second check fields are both 21 bits, the size of the target encoding block 802, the target encoding block 804, or the target encoding block 806 is 260 bits. When the size of the TC field is 2 bits, the size of the target encoding block 808 is 260 bits.
It should be appreciated that fig. 8 a-8 d share similarities to the previous fig. 5 a-5 d. Thus, with respect to the description of fig. 8 a-8 d, reference may be made to the descriptions in fig. 5 a-5 d and fig. 6-7 b previously described. For example, a description of the first check field, the first overhead field, the second overhead field, and the second check field. As another example, the transmitting device may combine 258 the fields and check 258 the second overhead fields with one second check field. 258 field may be any of the aforementioned target coding block 802, target coding block 804, target coding block 806, or target coding block 806. 258 field does not include the Q field therein.
As can be seen from the descriptions of fig. 4a to 8d, when the N66-bit encoded blocks include control encoded blocks, the target encoded block includes an f field corresponding to the deleted s field, for example, an f_3 field in the target encoded block 802. In the following example, for convenience of description, the f field corresponding to the deleted s field is simply referred to as the f field. In practical applications, the f-field may also generate errors. The first check field may also be used to check the f-field in order to improve the reliability of the transmission target encoded block. The first check field may be used to check the f-field and the first overhead field in whole or to check the f-field and the first overhead field separately.
When the first check field is used to separately check the f-field and the first overhead field, the first check field includes a first check subfield and a second check subfield. The first check subfield is used to check the first overhead field. The second check subfield is used to check the f field. For example, the first check field (P field) in the target encoding block 402 has a size of 2 bits. 1 bit is used to check the first overhead field. The 1 bit is used to check the f_1 field. As another example, the first check field (P field) in the target encoding block 404 is 2 bits in size. 1 bit is used to check the first overhead field. The 1 bit is used to check the f_0 field.
In the foregoing example, the position of the f-field in the target coding block may change. For example, in fig. 4a and 4b, the position of the f_1 field in the target encoding block 402 and the f_0 field in the target encoding block 404 are different. Thus, the correctness of the first overhead field affects the position of the f field. Thus, when the first check field is used to integrally check the f-field and the first overhead field, the f-field and the first overhead field must be positioned adjacent. To this end, embodiments of the present application may make the f-field adjacent to the location of the first overhead field by changing the location of the f-field. The following description will take N as 2 and 4 as examples, respectively.
Fig. 9a is an eighth schematic structural diagram of 2 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 9a, the description of the 2 66-bit encoded blocks 401 is referred to the description of fig. 4a above. The compressed target encoded block 901 includes d_0, f_1, and c_1 fields. The target encoding block 901 further includes a first overhead field and a first check field (P field). The first overhead field is used to indicate the code block type of the N66-bit coded blocks. In fig. 9a, the first overhead field has a size of 2 bits. The first overhead field is 10. "1" means that the first 66-bit encoded block is a data encoded block. "0" means that the second 66-bit code block is a control code block. However, the first 66-bit code block is replaced with a control code block for the purpose of the f-field being adjacent to the position of the first overhead field. Thus, the receiving apparatus extracts 2 66-bit encoded blocks from the target encoded block with "10" as "01". After extracting 2 66-bit encoded blocks, the receiving apparatus changes the order of the 2 66-bit encoded blocks, resulting in 2 66-bit encoded blocks ordered by "10". In comparison to the aforementioned fig. 4a, the positions of the f_1 field and the c_1 field are changed such that the positions of the f_1 field and the first overhead field are adjacent.
Fig. 9b is a fifth schematic structural diagram of 4 66-bit encoding blocks and a target encoding block according to an embodiment of the present application. As shown in fig. 9b, the description of the 4 66-bit coding blocks 801 is referred to the description of fig. 8a above. The compressed target encoded block 902 includes d_0, d_1, d_2, f_3, and c_3 fields. The target encoding block 902 also includes a second overhead field and a second check field (Q field). The target encoding block 902 also includes a first overhead field and a first check field (P field). The first overhead field is 4 bits in size. The first overhead field is 1110. "111" means the first to third 66-bit encoded blocks are data encoded blocks. "0" means that the fourth 66-bit encoded block is a data encoded block. However, the first 66-bit code block is replaced with a control code block for the purpose of the f-field being adjacent to the position of the first overhead field. Thus, the receiving apparatus extracts 4 66-bit encoded blocks in the target encoded block with "1110" as "0111". After extracting the 4 66-bit encoded blocks, the receiving device changes the order of the 4 66-bit encoded blocks, resulting in 4 66-bit encoded blocks ordered by "1110". In comparison with fig. 8a, the positions of the f_3 field and the first overhead field can be made adjacent by changing the positions of the f_3 field and the c_3 field.
In practice, there may be N66-bit encoded blocks ordered by "01" or "0111". If the first overhead field in fig. 9a or 9b is modified to "01" or "0111", then the first overhead field is caused to collide. To avoid collision of the first overhead field, in the embodiment of the present application, when the f field and the first overhead field are located adjacent to each other, the first overhead field may be used to indicate the arrangement order of the N66-bit encoded blocks before compression, instead of the arrangement order of the N66-bit encoded blocks among the target encoded blocks.
In the example of fig. 9a or 9b, the receiving device gets a new first overhead field (01 or 0111) from the first overhead field (10 or 1110) in the target coding block. The receiving device extracts the N66-bit encoded blocks from the new first overhead field, resulting in N66-bit encoded blocks ordered by the new first overhead field. After extracting the N66-bit encoded blocks, the receiving device changes the ordering order of the N66-bit encoded blocks, resulting in N66-bit encoded blocks ordered according to the first overhead field. Wherein the receiving device may derive the new first overhead field in the following manner: the receiving device exchanges the first control coding block identification and the location of the first data coding block identification in the first overhead field. For example, the receiving device changes the positions of the first "0" and the first "1" in "1110" to obtain "0111". After extracting the N66-bit encoded blocks according to the new first overhead field, the receiving device changes the arrangement order of the N66-bit encoded blocks by inverse swapping. For example, in the foregoing example, the receiving device swaps "1" in the first bit and "0" in the fourth bit. At this time, the receiving apparatus swaps the fourth 66-bit encoded block and the first 66-bit encoded block of the 4 66-bit encoded blocks, resulting in 4 66-bit encoded blocks ordered in "1110".
It should be appreciated that the first check field may also be used to check the f field and the first overhead field separately when the f field and the first overhead field are located adjacent. In order to improve the reliability of the check, the data size checked by the first check subfield and the data size checked by the second check subfield may be the same. For example, in fig. 9a, the size of the first check field is 2 bits. The first and second syndrome fields are both 1 bit in size. The first overhead field and f_1 field total size is 6 bits. The first check subfield is used to check the first 3 bits of the 6 bits. The second check subfield is used to check the last 3 bits of the 6 bits.
The size of the first check field may be reduced by the overall check. For example, in fig. 8a, at least 2 bits are required for the first check field to separately check the f-field and the first overhead field. In fig. 9b, the size of the first check field may be 1 bit. The 1 bit is used to check the first overhead field and the f_3 field in its entirety.
In the examples of fig. 4 a-9 b, the first check field is used to check the first overhead field in the target encoded block. In practical applications, the first overhead field may also be verified by integrally verifying the target encoded block. The following description will take N equal to 4 as an example. Fig. 10 is a second schematic structural diagram of a target coding block according to an embodiment of the present application. As shown in fig. 10, the target encoding block 1001 includes 4 257 fields and a first check field (P field). The 257 field has a size of 257 bits. For description of 257 fields, reference may be made to description of target coding block 802, target coding block 804, target coding block 806, or target coding block 808. Specifically, as can be seen from the foregoing descriptions of fig. 8a to 8d, when the target encoding block 802, the target encoding block 804 or the target encoding block 806 does not include the first check field and the second check field, the size of the target encoding block 802, the target encoding block 804 or the target encoding block 806 is 257 bits. When the target coding block 808 does not include the TC field, the target coding block 808 is 257 bits in size. The size of the first check field may be 8 bits. At this time, the size of the target code block 1001 is 1036 bits. The first check field is used to check the 4 257 fields in total.
Based on the foregoing description of the data frame provided in the present application, the data encoding method provided in the present application is described below. Fig. 11 is a flowchart of a data encoding method according to an embodiment of the present application. As shown in fig. 11, the data encoding method includes the following steps.
In step 1101, the transmitting device acquires N66-bit encoded blocks. The transmitting device may be an OTN device or an MTN device, etc. For the description of the N66-bit encoded blocks, reference may be made to the descriptions in fig. 3 to 10 described above.
In step 1102, the transmitting device compresses N66-bit encoded blocks into a target encoded block. The size of the target code block is smaller than the size of the N66 bit code blocks. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks, and the first check field is used to check the first overhead field. For the description of the target coding block, reference may be made to the descriptions in fig. 3 to 10 described above.
In step 1103, the transmitting device maps the target encoded block to a payload region of the data frame. In practical applications, the data frame may be obtained by direct mapping, indirect mapping or hybrid mapping. This will be described separately below.
Fig. 12a is a schematic flow chart of direct mapping provided in an embodiment of the present application. As shown in fig. 12a, the transmitting device receives N66-bit encoded blocks from a certain ethernet service. The transmitting apparatus compresses the N66-bit encoded blocks into a target encoded block. For descriptions of the N66-bit encoded blocks and the target encoded block, reference may be made to the descriptions in any of the foregoing fig. 3 to 10. The payload area of the data frame 1201 is divided into a plurality of slots. The size of each slot is the same as the size of the target coding block. For example, each slot may be 130 bits, 259 bits, 260 bits, 520 bits, or the like in size. By mapping the target encoded block to a time slot, a data frame can be obtained. The transmitting device may get different target encoded blocks for different ethernet services. The transmitting device maps different target code blocks to different time slots.
Fig. 12b is a schematic flow chart of indirect mapping provided in an embodiment of the present application. As shown in fig. 12b, the transmitting device receives N66-bit encoded blocks from a certain ethernet service. The transmitting apparatus compresses the N66-bit encoded blocks into a target encoded block. For descriptions of the N66-bit encoded blocks and the target encoded block, reference may be made to the descriptions in any of the foregoing fig. 3 to 10. The transmitting device first maps the target encoded block to a payload region in the traffic frame. The transmitting device maps the traffic frame to the payload region of the data frame 1202 to obtain the data frame. For different ethernet services, the transmitting device may get different service frames. The transmitting device maps different traffic frames to different locations of the payload area.
Fig. 12c is a schematic flow chart of hybrid mapping according to an embodiment of the present application. As shown in fig. 12c, the transmitting device receives N1 66-bit encoded blocks from ethernet service 1. N1 is an integer greater than 1. The transmitting apparatus compresses the N1 66-bit encoded blocks into a target encoded block 1. There are multiple slots in the payload area of the data frame 1103. The size of each slot is the same as the size of the target coding block 1. For example, each slot may be 130, 259, 260, or 520 bits in size. The transmitting device maps the target code block 1 to a slot. The transmitting device also receives N2 66-bit encoded blocks from ethernet traffic 2. N2 is an integer greater than 1. The transmitting apparatus compresses the N2 66-bit encoded blocks into the target encoded block 2. The transmitting device first maps the target coding block 2 to a payload area in the traffic frame. The sending device then maps the traffic frame to the payload area of the data frame 1203.
In step 1104, the transmitting device transmits a data frame.
Fig. 13 is a flow chart of a data verification method according to an embodiment of the present application. As shown in fig. 13, the data verification method includes the following steps.
In step 1301, a receiving device receives a data frame. The receiving device may be an OTN device or an MTN device, etc. The data frame may be an OTN frame, a FlexE frame, an MTN frame, or the like.
In step 1302, the receiving device extracts a target encoded block from a payload region of a data frame. The target code block is compressed from N66 bit code blocks. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. For descriptions of the target encoding block and the N66-bit encoding blocks, reference may be made to the descriptions in any of the foregoing fig. 3 to 10.
In step 1303, the receiving device verifies the first overhead field with the first check field.
It should be understood that, with respect to the description of the data verification method, reference may be made to the description of the data frame in any one of fig. 3 to 10. The receiving device may also check the f-field by the first check field, for example. As another example, the target coding block further includes a second overhead field and a second parity field. The receiving device may also check the second overhead field by means of a second check field. As another example, the receiving device extracts the traffic frame from the payload region of the data frame and extracts the target encoded block from the payload region of the traffic frame. It should be understood that the process of acquiring the target encoded block mentioned in the embodiment of the present application or a specific implementation thereof may also be understood as a process of decoding data.
Fig. 14 is a schematic structural diagram of a transmitting device according to an embodiment of the present application. As shown in fig. 14, the transmission apparatus 1400 includes an acquisition module 1401, a compression module 1402, a mapping module 1403, and a transmission module 1404. The acquisition module 1401 is configured to acquire N66-bit encoded blocks. N is an integer greater than 1. The compression module 1402 is configured to compress N66-bit encoded blocks into a target encoded block. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The first check field is used to check the first overhead field. The mapping module 1403 is used to map the target encoded block to a payload region of the data frame. The transmitting module 1404 is configured to transmit a data frame.
It should be understood that, regarding the description of the transmitting apparatus 1400, reference may be made to the description of the data frames in any of the foregoing fig. 3 to 10 or the description of the data encoding method in fig. 11. For example, the target coding block further includes an f field and a c field. The first check field is also used to check the f-field. As another example, the target coding block further includes a second overhead field and a second parity field. The second check field is used to check the second overhead field.
Fig. 15 is a schematic structural diagram of a receiving device according to an embodiment of the present application. As shown in fig. 15, the receiving apparatus 1500 includes a receiving module 1501, an extracting module 1502, and a verifying module 1503. The receiving module 1501 is configured to receive a data frame. The extracting module 1502 is configured to extract a target coding block from a payload area of a data frame. The target code block is compressed from N66 bit code blocks. N is an integer greater than 1. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The checking module 1503 is configured to check the first overhead field with the first check field.
It should be understood that, regarding the description of the receiving apparatus 1500, reference may be made to the description of the data frame in any of the foregoing fig. 3 to 10 or the description of the data verification method in fig. 13. For example, the target coding block includes an f field. The checking module 1503 is further configured to check the f-field with the first check field. As another example, the target coding block further includes a second overhead field and a second parity field. The checking module 1503 is further configured to check the second overhead field by the second check field.
Fig. 16 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device may be a transmitting device or a receiving device. As shown in fig. 16, the communication device 1600 includes a processor 1601 and a transceiver 1602. The processor 1601 may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP. The processor 1601 may further include a hardware chip or other general purpose processor. The hardware chip may be an application specific integrated circuit (application specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD), or a combination thereof. Transceiver 1602 may be an optical transceiver.
When the communication device 1600 is a transmitting device, the processor 1601 is configured to obtain N66-bit encoded blocks. N is an integer greater than 1. The processor 1601 is further configured to compress the N66-bit encoded blocks into a target encoded block. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The first check field is used to check the first overhead field. The processor 1601 is further configured to map a target encoded block to a payload area of a data frame. The transceiver 1602 is used to transmit data frames.
When the communication device 1600 is a receiving device, the transceiver 1602 is configured to receive a data frame. The processor 1601 is configured to extract a target encoded block from a payload area of a data frame. The target code block is compressed from N66 bit code blocks. N is an integer greater than 1. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The processor 1601 is further configured to check a first overhead field with a first check field.
In other embodiments, communication device 1600 may also include memory 1603. Memory 1603 may be volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an erasable ROM (EPROM), a flash memory, or the like. The volatile memory may be random access memory (random access memory, RAM). Memory 1603 may be used to store a target encoding block or N66 bit encoding blocks.
It should be understood that, regarding the description of the communication device 1600, reference may be made to the description of the data frames in any of the foregoing figures 3-10, the description of the data encoding method of figure 11, or the description of the data verification method of figure 13. For example, when the communication device 1600 is a transmitting device, the processor 1601 obtains a data frame by hybrid mapping. As another example, the target coding block also includes an f field. The processor 1601 is further configured to check the f-field with the first check field when the communication device 1600 is a receiving device. As another example, the target coding block further includes a second overhead field and a second parity field. The processor 1601 is further configured to check a second overhead field by a second check field.
The application also provides a communication system. Fig. 17 is a schematic structural diagram of a communication system according to an embodiment of the present application. As shown in fig. 17, the communication system 1700 includes a transmitting apparatus 1701 and a receiving apparatus 1702. The transmitting apparatus 1701 is configured to acquire N66-bit encoded blocks. N is an integer greater than 1. The transmitting apparatus 1701 is configured to compress N66-bit encoded blocks into a target encoded block. The target coding block includes a first check field and a first overhead field. The first overhead field is used to indicate the code block type of the N66-bit coded blocks. The transmitting apparatus 1701 is configured to map a target encoded block to a payload region of a data frame. The transmitting apparatus 1701 is configured to transmit a data frame. The receiving device 1702 is configured to receive a data frame. The receiving device 1702 is configured to extract a target encoded block from a payload region of a data frame. The receiving device 1702 is configured to check the first overhead field with a first check field.
It should be understood that, regarding the description of the transmitting apparatus 1701, reference may be made to the description of the data frames in any of the foregoing fig. 3 to 10 or the description of the data encoding method in fig. 11. For the description of the receiving apparatus 1702, reference may be made to the description of the data frame in any of the foregoing fig. 3 to 10 or the description of the data verification method in fig. 13. In practice, the receiving device 1702 may also be used to transmit data frames to the transmitting device 1701. The transmitting device 1701 may also be configured to extract a target encoded block from a received data frame. Accordingly, for the description of the receiving apparatus 1702, reference may be made to the description of the transmitting apparatus 1701. As for the description of the transmitting apparatus 1701, reference may be made to the description of the receiving apparatus 1702.
The foregoing is merely specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes or substitutions are intended to be covered by the scope of the present application.

Claims (23)

1. A method of encoding data, comprising:
the method comprises the steps that a transmitting device obtains N66-bit coding blocks, wherein N is an integer greater than 1;
the transmitting device compresses the N66-bit encoded blocks into target encoded blocks, the target encoded blocks including a first check field and a first overhead field, the first overhead field being used to indicate a code block type of the N66-bit encoded blocks, the first check field being used to check the first overhead field;
the transmitting device maps the target coding block to a payload area of a data frame;
the transmitting device transmits the data frame.
2. The data encoding method according to claim 1, wherein the N66-bit encoded blocks include a first 66-bit encoded block, the first 66-bit encoded block being of a control encoded block type, the first 66-bit encoded block including an f-field, an s-field, and a c-field;
Wherein the target coding block includes the f-field and the c-field, and the first check field is further used to check the f-field.
3. The data encoding method according to claim 2, wherein the first check field includes a first check subfield for checking the first overhead field and a second check subfield for checking the f field.
4. A data encoding method according to claim 2 or 3, characterized in that the f-field and the first overhead field are located adjacent.
5. The data encoding method according to any one of claims 1 to 4, wherein the target encoding block further comprises a second overhead field for indicating whether the target encoding block comprises a control encoding block and a second check field for checking the second overhead field.
6. The data encoding method of claim 5, wherein the size of the second parity field is 1 bit, and the size of the second overhead field is 1 bit.
7. The data encoding method according to any one of claims 1 to 6, wherein N is 4, the size of the target encoding block is 260 bits, the size of the first overhead field is 4 bits, and the size of the first check field is 2 bits.
8. The data encoding method according to any one of claims 1 to 6, wherein N is 2, the size of the target encoding block is 130 bits, the size of the first overhead field is 2 bits, and the size of the first check field is 2 bits.
9. The data encoding method according to any one of claims 1 to 6, wherein N is an integer multiple of 2;
the transmitting apparatus compressing the N66-bit encoded blocks into a target encoded block includes:
the transmitting device compresses the N66-bit coding blocks into N/2 target sub-coding blocks, each target sub-coding block corresponding to 2 66-bit coding blocks, each target sub-coding block including a second overhead field for indicating whether each target sub-coding block includes a control coding block;
the transmitting device compresses the N/2 target sub-encoded blocks into the target encoded blocks, the target encoded blocks including a second parity field for checking N/2 second overhead fields.
10. The data encoding method of claim 9, wherein the size of the second parity field is 1 bit, the size of each target subcode block is 129 bits, and the size of the N/2 second overhead fields is N/2 bits.
11. The data encoding method according to any one of claims 1 to 5, 9 or 10, wherein N is 4, the size of the target encoding block is 259 bits, the size of the first overhead field is 4 bits, and the size of the first check field is 4 bits.
12. The data encoding method according to any one of claims 1 to 5, 9 or 10, wherein N is 8, the size of the target encoding block is 520 bits, the size of the first overhead field is 8 bits, and the size of the first check field is 8 bits.
13. The data encoding method of claim 1, wherein the first check field for checking the first overhead field comprises: the first check field is used to check the target encoded block.
14. The data encoding method according to any one of claims 1 to 13, wherein the payload section of the data frame is divided into a plurality of slots, and the size of each slot is equal to the size of the target encoding block;
the mapping, by the transmitting device, the target encoded block to a payload region of a data frame includes: the transmitting device maps the target coding block to a slot of the payload region.
15. The data encoding method of claim 14, wherein the method further comprises:
the transmitting device acquires another target coding block;
the transmitting device maps the other target coding block to a traffic frame;
the transmitting device maps the traffic frame to a slot of the payload region.
16. The method for encoding data according to any one of claims 1 to 13, wherein,
the mapping, by the transmitting device, the target encoded block to a payload region of a data frame includes: the transmitting device maps the target coding block to a traffic frame and maps the traffic frame to a payload region of the data frame.
17. A method of data verification, comprising:
the receiving device receives the data frame;
the receiving device extracts a target coding block from a payload area of the data frame, wherein the target coding block is obtained by compressing N66-bit coding blocks, N is an integer greater than 1, and the target coding block comprises a first check field and a first overhead field, and the first overhead field is used for indicating the code block types of the N66-bit coding blocks;
the receiving device verifies the first overhead field by the first verification field.
18. The data verification method according to claim 17, wherein the target encoded block includes an f-field and a c-field, the method further comprising:
the receiving device verifies the f field through the first verification field.
19. The data verification method according to claim 17 or 18, wherein the target code block further comprises a second overhead field and a second parity field, the second overhead field being used to indicate whether the target code block comprises a control code block, the method further comprising:
the receiving device verifies the second overhead field by the second verification field.
20. The transmitting device is characterized by comprising an acquisition module, a compression module, a mapping module and a transmitting module, wherein:
the acquisition module is used for acquiring N66-bit coding blocks, wherein N is an integer greater than 1;
the compression module is used for compressing the N66-bit coding blocks into target coding blocks, the target coding blocks comprise first check fields and first overhead fields, the first overhead fields are used for indicating the code block types of the N66-bit coding blocks, and the first check fields are used for checking the first overhead fields;
The mapping module is used for mapping the target coding block to a payload area of a data frame;
the sending module is used for sending the data frame.
21. The receiving device is characterized by comprising a receiving module, an extracting module and a checking module, wherein:
the receiving module is used for receiving the data frame;
the extraction module is configured to extract a target coding block from a payload area of the data frame, where the target coding block is obtained by compressing N66-bit coding blocks, N is an integer greater than 1, and the target coding block includes a first check field and a first overhead field, where the first overhead field is used to indicate a code block type of the N66-bit coding blocks;
the checking module is configured to check the first overhead field through the first check field.
22. A transmitting device comprising a processor and a transceiver, wherein:
the processor is configured to perform the method of any of the preceding claims 1 to 16 to obtain a data frame;
the transceiver is configured to transmit the data frame.
23. A receiving device comprising a processor and a transceiver, wherein:
the transceiver is used for receiving data frames;
The processor is configured to extract a target encoded block in a payload region of the data frame, perform the method of any of the preceding claims 17 to 19, and verify the content in the target encoded block.
CN202211020657.5A 2022-08-24 2022-08-24 Data encoding method, data checking method and related equipment Pending CN117675078A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211020657.5A CN117675078A (en) 2022-08-24 2022-08-24 Data encoding method, data checking method and related equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211020657.5A CN117675078A (en) 2022-08-24 2022-08-24 Data encoding method, data checking method and related equipment

Publications (1)

Publication Number Publication Date
CN117675078A true CN117675078A (en) 2024-03-08

Family

ID=90077353

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211020657.5A Pending CN117675078A (en) 2022-08-24 2022-08-24 Data encoding method, data checking method and related equipment

Country Status (1)

Country Link
CN (1) CN117675078A (en)

Similar Documents

Publication Publication Date Title
CN108809901B (en) Method, equipment and system for carrying service
US11082199B2 (en) Data transmission method in optical network and optical network device
CN113395613B (en) Method, device and system for carrying service
US10992413B2 (en) Method and apparatus for transmitting optical transport unit signal
US20230164624A1 (en) Service data processing, exchange and extraction methods, devices, and computer-readable medium
CN113645524A (en) Method, device and equipment for processing service
US11962349B2 (en) Signal sending and receiving method, apparatus, and system
CN109962762B (en) Data transmission method, sending device and receiving device
CN110248260B (en) Method, device and system for processing Ethernet data in optical network
US20230299880A1 (en) Code block identification method and apparatus
CN112118073B (en) Data processing method, optical transmission equipment and digital processing chip
US10771178B2 (en) Method for sending and receiving optical transport network (OTN) signal, OTN device, and system
CN117675078A (en) Data encoding method, data checking method and related equipment
CN113078980A (en) Data transmission method and device
WO2021218639A1 (en) Service processing method, apparatus and device
JP2023523075A (en) Service processing method and apparatus
WO2024002084A1 (en) Method for verifying data frame, and related device
WO2024045869A1 (en) Data transmission method and data transmission apparatus
WO2023143577A1 (en) Method, apparatus and system for processing data frame in optical transport network
CN117135498A (en) Method and device for transmitting data
CN117354873A (en) Bearing method, communication equipment and storage medium
CN118074856A (en) Data mapping method, data demapping method and related equipment
CN116132851A (en) Optical signal transmission method and device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication