Data mapping method, data de-mapping method, and related device
Patent Information
- Application Number
- MYPI2025003113
- Authority / Receiving Office
- MY · MY
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2022-12-02
- Filing Date
- 2023-11-21
- Publication Date
- 2024-05-22
AI Technical Summary
When optical transport network (OTN) provides low-bandwidth transmission capabilities, the operation, management, and maintenance (OAM) performance of OSU frames is insufficient, making it difficult to effectively determine the boundaries of data encoding blocks, affecting transmission efficiency and reliability.
By designing the effective payload area size of the service frame, the receiving device can efficiently determine the data coding block boundary, and use multiple data coding blocks to map to the effective payload area of the service frame and transmit them in the data frame to ensure that the receiving device can accurately Extract data encoding blocks to improve OAM performance.
It improves the efficiency of data coding block boundary determination, enhances OTN OAM performance, reduces processing complexity and delay measurement accuracy, and improves transmission efficiency and reliability.
Smart Images

Figure PI2025003113_DRAWING_001 
Figure PI2025003113_DRAWING_002 
Figure PI2025003113_DRAWING_003
Abstract
Description
Data mapping method, data demapping method and related equipment
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on November 22, 2022, with application number 202211465674.X and application name “Data mapping method, data demapping method and related equipment”, and the Chinese patent application filed with the State Intellectual Property Office of China on December 2, 2022, with application number 202211536901.3 and application name “Data mapping method, data demapping method and related equipment”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] The present application relates to the field of communications, and in particular to a data mapping method, a data demapping method, and related devices. Background Art
[0003] Due to its high bandwidth, large capacity, high reliability, and low latency, the Optical Transport Network (OTN) has become a mainstream technology for transport networks. OTN can provide high-bandwidth transmission capabilities, such as n×1.25 gigabits per second (Gbps) and n×5 Gbps. To enable OTN to provide low-bandwidth transmission capabilities down to a few megabits per second (Mbps), optical service unit (OSU) frames are mapped into OTN frames. The structure of OSU frames is related to OTN operation, administration, and maintenance (OAM) performance (e.g., alarm generation time, protection switching time, etc.).
[0004] Therefore, designing an OSU frame that can improve OAM performance is an urgent problem to be solved.
[0005] Summary of the Invention
[0006] The present application provides a data mapping method, a data demapping method and related devices, which can improve the efficiency of the receiving device in determining the boundaries of data coding blocks by designing the size of the effective payload area of the service frame, thereby improving the OAM performance.
[0007] In a first aspect, the present application provides a data mapping method. The data mapping method includes the following steps. A sending device obtains multiple data coding blocks. The sending device can be an OTN device or a metropolitan transport network (MTN) device, etc. The sending device maps the multiple data coding blocks to the effective payload area of a service frame. The service frame can be a service subframe or a multiframe composed of multiple service subframes. The service subframe can be an optical service unit (OSU) frame or other data frame with an OSU frame structure. The size of the effective payload area of the service frame can be less than or equal to the size of the payload area of the service frame. When the size of the effective payload area of the service frame is less than the size of the payload area of the service frame, the payload area of the service frame also includes a padding payload area. The padding payload area is used to fill useless data. The size of the effective payload area of the service frame is equal to the size of the multiple data coding blocks. The sending device maps the service frame to the payload area of the data frame. The data frame can be an OTN frame, a flexible Ethernet (FlexE) frame, an MTN frame, etc. The sending device sends the data frame.
[0008] In this application, the size of multiple data coding blocks is equal to the size of the payload area. The payload area is fixed in position within the service frame. Therefore, after determining the start boundary of the service frame, the receiving device determines the data coding block boundary. Therefore, this application can improve the efficiency of determining data coding block boundaries, thereby improving OAM performance.
[0009] In an optional embodiment of the first aspect, the size of the service frame is an integer multiple of 16 bytes. When the payload area of the data frame is divided into multiple time slots and the interleaving size of each time slot is 16 bytes, the service frame occupies an integer number of time slots. In this case, the receiving device can improve the efficiency of determining the starting boundary of the service frame.
[0010] In an optional embodiment of the first aspect, the size of the effective payload area of the service frame is an integer multiple of 16 bytes. The size of the overhead area of the service frame is an integer multiple of 16 bytes. When the time slot interleaving granularity of the data frame is 16 bytes, the effective payload area and the overhead area of the service frame both occupy an integer number of time slots, thereby reducing the complexity of processing the OSU frame.
[0011] In an optional manner of the first aspect, a size of each data coding block in the M data coding blocks is 66 bits.
[0012] In an optional manner of the first aspect, the size of the service frame is 4×1064 bytes. The size of the effective payload area of the service frame is 4×1056 bytes. The size of the overhead area of the service frame is 4×8 bytes. In the present application, when the size of the data coding block is 66 bits, the payload area of the service frame can be used entirely to carry the data coding block, thereby improving transmission efficiency. In another optional manner of the first aspect, the size of the service frame is 4×1328 bytes. The size of the effective payload area of the service frame is 4×1320 bytes. The size of the overhead area of the service frame is 4×8 bytes. In the present application, when the size of the data coding block is 66 bits, the payload area of the service frame can be used entirely to carry the data coding block, thereby improving transmission efficiency.
[0013] In an optional manner of the first aspect, the size of each of the M data coding blocks is 257 bits. Compared with 66-bit coding blocks, 257-bit coding blocks can further improve carrying efficiency.
[0014] In an optional manner of the first aspect, the size of the service frame is 4×1036 bytes. The size of the effective payload area of the service frame is 4×1028 bytes. The size of the overhead area of the service frame is 4×8 bytes. In the present application, when the size of the data coding block is 257 bits, the payload area of the service frame can be used entirely to carry the data coding block, thereby improving transmission efficiency. In another optional manner of the first aspect, the size of the service frame is 4×1293 bytes. The size of the effective payload area of the service frame is 4×1258 bytes. The size of the overhead area of the service frame is 4×8 bytes. In the present application, when the size of the data coding block is 257 bits, the payload area of the service frame can be used entirely to carry the data coding block, thereby improving transmission efficiency.
[0015] In an optional manner of the first aspect, the overhead area of the service frame includes a plurality of different frame header indication overhead fields. By adding the frame header indication overhead fields, the efficiency of determining the starting boundary of the service frame can be improved.
[0016] In an optional embodiment of the first aspect, each of the multiple frame header indication overhead fields includes a frame header indication identifier field and a first field. The first field is used to indicate the order of each frame header indication overhead field within the multiple frame header indication overhead fields. By adding the first field, the efficiency of determining the starting boundary of a service frame can be improved.
[0017] In an optional manner of the first aspect, the number of the multiple frame header indication overhead fields is the number of rows in the overhead area of the service frame.
[0018] In an optional embodiment of the first aspect, the overhead area of the service frame includes a delay measurement (DM) overhead field. The size of the DM overhead field is 16 bits. By increasing the size of the DM overhead field, more timestamp information can be transmitted. Therefore, the present application can improve delay measurement accuracy.
[0019] In an optional embodiment of the first aspect, the overhead area of the service frame includes a justification control (JC) overhead field. The size of the JC overhead field is less than 4 bytes. By reducing the size of the JC overhead field, the size of the overhead required for transmission can be reduced, thereby improving transmission efficiency.
[0020] In an optional embodiment of the first aspect, the overhead area of the service frame includes a path monitoring (PM) automatic protection switching (APS) overhead field and a tandem connection monitoring (TCM) APS overhead field. By simultaneously transmitting the PM APS overhead field and the TCM APS overhead field in a single data frame, fault handling speed can be improved.
[0021] In an optional manner of the first aspect, the size of the service frame is smaller than or equal to the size of the payload area of the data frame.
[0022] In an optional manner of the first aspect, the service frame is an OSU frame, and the data frame is an OTN frame.
[0023] In an optional embodiment of the first aspect, the overhead area of a service frame includes multiple sub-overhead areas. The payload area of the service frame includes multiple sub-payload areas. The sub-overhead areas in the multiple sub-overhead areas are alternately arranged with the sub-payload areas in the multiple sub-payload areas. Each of the multiple sub-overhead areas includes a target overhead field. By providing the target overhead field in the multiple sub-overhead areas, the frequency of transmitting the target overhead field can be increased, thereby improving OAM performance.
[0024] In an optional embodiment of the first aspect, the target overhead field includes a frame header indication overhead field and / or an accumulated delay overhead field. When the target overhead field includes the frame header indication overhead field, the efficiency of determining the start boundary of the service frame can be improved. When the target overhead field includes the accumulated delay overhead field, the clock recovery performance of the receiving device can be improved.
[0025] In an optional embodiment of the first aspect, the size of the sub-payload area between any two adjacent sub-overhead areas in the plurality of sub-overhead areas is an integer multiple of 8 or 16 bytes. By setting the size of the sub-payload area, it is possible to maintain a certain processing capability while reducing processing complexity.
[0026] In an optional manner of the first aspect, the service frame is a multiframe composed of N service subframes, where N is an integer greater than 1. Carrying data by using a multiframe composed of multiple service subframes can improve carrying efficiency.
[0027] In an optional embodiment of the first aspect, N is 4. The size of the N service subframes is 4×3824 bytes. When the size of the multiframe composed of the N service subframes is 4×3824 bytes, the structure of the multiframe is consistent with the structure of the OTN frame. Therefore, the present application can reduce the complexity of multiframe processing by the receiving device.
[0028] In an optional manner of the first aspect, the size of each of the multiple sub-overhead areas is an integer multiple of 8 or 16 bytes. By setting the size of each sub-overhead area, the processing complexity can be reduced.
[0029] In an optional manner of the first aspect, the size occupied by each service subframe in each sub-overhead area of the N service subframes is an integer multiple of 8 or 16 bytes. By setting the size occupied by each service subframe in each sub-overhead area, the processing complexity can be reduced.
[0030] In an optional embodiment of the first aspect, the number of the multiple overhead sub-areas is two. Increasing the number of overhead sub-areas can increase the frequency of transmitting the target overhead field, thereby improving OAM performance. However, introducing too many overhead sub-areas can also increase the complexity of service frame processing on the receiving device, thereby reducing OAM performance. When the number of the multiple overhead sub-areas is two, reasonable OAM performance can be provided.
[0031] In an optional manner of the first aspect, each of the multiple sub-overhead areas includes N target overhead fields. The N target overhead fields correspond one-to-one to N service subframes. By increasing the frequency of transmitting the target overhead fields, OAM performance can be improved.
[0032] A second aspect of the present application provides a data demapping method. The data demapping method includes the following steps: a receiving device receives a data frame from a transmitting device. The receiving device may be an OTN device or an MTN device, for example. The data frame may be an OTN frame, a FlexE frame, or an MTN frame. The receiving device extracts a service frame from the payload area of the data frame. The service frame may be an OSU frame or other data frame with an OSU-like frame structure. The receiving device extracts multiple data coding blocks from the effective payload area of the service frame. The size of the effective payload area of the service frame is equal to the size of the multiple data coding blocks.
[0033] In an optional manner of the second aspect, the overhead area of the service frame includes multiple different frame header indication overhead fields. The data demapping method further includes: the receiving device determining the starting boundary of the service frame according to the multiple frame header indication overhead fields.
[0034] In an optional manner of the second aspect, the overhead area of the service frame includes a DM overhead field. The size of the DM overhead field is 8 bits. The data demapping method includes the following steps: the receiving device determines the delay between the receiving device and the transmitting device based on the DM overhead field.
[0035] It should be understood that the description of the second aspect is similar to the description of the first aspect. Therefore, with respect to the description of the second aspect, reference may be made to the description of any optional manner in the aforementioned first aspect.
[0036] A third aspect of the present application provides a data mapping method. The data mapping method includes the following steps. A transmitting device obtains multiple data coding blocks. The transmitting device maps the multiple data coding blocks to the effective payload area of a service frame. The overhead area of the service frame includes multiple sub-overhead areas. The payload area of the service frame includes multiple sub-payload areas. The sub-overhead areas in the multiple sub-overhead areas and the sub-payload areas of the multiple sub-payload areas are alternately distributed. Each sub-overhead area in the multiple sub-overhead areas includes a target overhead field. The size of the effective payload area of the service frame is less than or equal to the size of the multiple sub-payload areas.
[0037] It should be understood that the description of the third aspect is similar to the description of the first aspect. Therefore, with respect to the description of the third aspect, reference may be made to the description of the first aspect or any optional manner of the first aspect.
[0038] A fourth aspect of the present application provides a communication system. The communication system includes a transmitting device and a receiving device. The transmitting device is used to obtain multiple data coding blocks and map the multiple data coding blocks to the effective payload area of a service frame. The size of the effective payload area of the service frame is equal to the size of the multiple data coding blocks. The transmitting device is also used to map the service frame to the payload area of the data frame and transmit the data frame. The receiving device is used to receive the data frame from the transmitting device and extract the service frame from the payload area of the data frame. The receiving device is also used to extract the multiple data coding blocks from the effective payload area of the service frame.
[0039] In an optional embodiment of the fourth aspect, the sending device is also used to execute the method described in the aforementioned first aspect, the third aspect, or any optional embodiment of the first aspect, and / or the receiving device is also used to execute the method described in the aforementioned second aspect or any optional embodiment of the second aspect.
[0040] A fifth aspect of the present application provides a service frame. The service frame includes an overhead area and a valid payload area. The valid payload area is used to carry multiple data coding blocks. The size of the valid payload area of the service frame is equal to the size of the multiple data coding blocks.
[0041] In an optional manner of the fifth aspect, the service frame further includes the content described in any optional manner of the aforementioned first aspect.
[0042] A sixth aspect of the present application provides a data frame. The data frame includes an overhead area and a payload area. The payload area of the data frame is used to carry one or more service frames described in the fifth aspect or any optional manner of the fifth aspect.
[0043] A seventh aspect of the present application provides a sending device. The sending device includes an acquisition module, a mapping module, and a sending module. The acquisition module is configured to acquire multiple data coding blocks. The mapping module is configured to execute the method described in any one of the first, third, or first aspects above to obtain a data frame based on the multiple data coding blocks. The sending module is configured to send the data frame.
[0044] In an eighth aspect, the present application provides a receiving device. The receiving device includes a receiving module and an extraction module. The receiving module is configured to receive a data frame from a transmitting device. The extraction module is configured to execute the method described in the second aspect or any one of the second aspects to obtain multiple data coding blocks based on the data frame.
[0045] A ninth aspect of the present application provides a transmitting device. The transmitting device includes a processor and a transceiver. The processor is configured to execute the method described in the first aspect, the third aspect, or any optional embodiment thereof to obtain a data frame. The transceiver is configured to transmit the data frame.
[0046] In a tenth aspect, the present application provides a receiving device. The receiving device includes a processor and a transceiver. The transceiver is configured to receive a data frame. The processor is configured to execute the method described in the second aspect or any one of the second aspects to obtain multiple data coding blocks based on the data frame.
[0047] In an eleventh aspect of the present application, a computer storage medium is provided. The computer storage medium stores instructions that, when executed on a computer, cause the computer to perform the method described in the first aspect, the third aspect, or any one of the embodiments of the first aspect; or cause the computer to perform the method described in the second aspect or any one of the embodiments of the second aspect.
[0048] A twelfth aspect of the present application provides a computer program product. When the computer program product is executed on a computer, the computer is caused to perform the method according to the first aspect, the third aspect, or any one of the embodiments of the first aspect; or the computer is caused to perform the method according to the second aspect or any one of the embodiments of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS
[0049] FIG1 is a schematic diagram of the structure of an OTN;
[0050] FIG2 is a schematic diagram of the structure of an OTN device;
[0051] FIG3 is a schematic diagram of mapping an OSU frame to an OTN frame;
[0052] FIG4 is a first structural diagram of an OSU frame provided in an embodiment of the present application;
[0053] FIG5 is a second structural diagram of an OSU frame provided in an embodiment of the present application;
[0054] FIG6 is a first structural diagram of the overhead area of an OSU frame provided in an embodiment of the present application;
[0055] FIG7 is a second structural diagram of the overhead area of the OSU frame provided in an embodiment of the present application;
[0056] FIG8 is a schematic diagram of the structure of a frame header indication overhead field provided in an embodiment of the present application;
[0057] FIG9 is a third structural diagram of the overhead area of the OSU frame provided in an embodiment of the present application;
[0058] FIG10 is a fourth structural diagram of the overhead area of the OSU frame provided in an embodiment of the present application;
[0059] FIG11 is a fifth structural diagram of the overhead area of the OSU frame provided in an embodiment of the present application;
[0060] FIG12 is a sixth structural diagram of the overhead area of the OSU frame provided in an embodiment of the present application;
[0061] FIG13 is a third structural diagram of an OSU frame provided in an embodiment of the present application;
[0062] FIG14 is a first structural diagram of the first sub-overhead area provided in an embodiment of the present application;
[0063] FIG15 is a first structural diagram of the second sub-overhead area provided in an embodiment of the present application;
[0064] FIG16 is a fourth structural diagram of an OSU frame provided in an embodiment of the present application;
[0065] FIG17 is a second schematic diagram of the structure of the first sub-overhead area provided in an embodiment of the present application;
[0066] FIG18 is a second structural diagram of the second sub-overhead area provided in an embodiment of the present application;
[0067] FIG19 is a flow chart of a data mapping method according to an embodiment of the present application;
[0068] FIG20 is a schematic diagram of a flow chart of a data demapping method provided in an embodiment of the present application;
[0069] FIG21 is a schematic diagram of the structure of a sending device provided in an embodiment of the present application;
[0070] FIG22 is a schematic diagram of the structure of a receiving device provided in an embodiment of the present application;
[0071] FIG23 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;
[0072] Figure 24 is a structural diagram of the communication system provided in an embodiment of the present application. DETAILED DESCRIPTION
[0073] First, some terms in this application are explained to facilitate understanding by those skilled in the art.
[0074] 1) Multiple refers to two or more. "And / or" describes the relationship between related objects, and three types of relationships are possible. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. In addition, in the description of this application, words such as "first" and "second" are used only for the purpose of distinguishing descriptions and should not be understood to indicate or imply relative importance or order.
[0075] 2) Mapping A to B mentioned in this application refers to encapsulating A into B. For example, mapping an optical service unit (OSU) frame into an optical transport network (OTN) frame refers to encapsulating an OSU frame or an OSU signal into an OTN frame.
[0076] 3) Unless otherwise specified, the detailed description of certain technical features in one embodiment can also be applied to the explanation of corresponding technical features in other embodiments. For example, the overhead and meaning contained in a service frame in one embodiment can also be applied to the service frames mentioned in other embodiments. For another example, the specific examples and descriptions of optical transport network frames can be applied to optical transport network frames mentioned in different specific embodiments, or can be used to replace specific examples of optical transport network frames.
[0077] The embodiments of the present application are applicable to optical networks such as optical transport networks or metropolitan area transport networks. Optical transport networks include OTNs or flexible Ethernet (FlexE). In the subsequent description of this application, OTN will be used as an example. An OTN is typically composed of multiple OTN devices connected by optical fibers and can be organized into different topology types such as linear, ring, and mesh according to specific needs. Figure 1 is a schematic diagram of the structure of an OTN. As shown in Figure 1, OTN 100 is composed of eight OTN devices 101, namely OTN devices AH. Reference numeral 102 indicates an optical fiber used to connect two devices. Reference numeral 103 indicates a customer service interface used to receive or send customer service data. As shown in Figure 1, OTN 100 is used to transmit service data for customer devices 1-3. Customer devices are connected to OTN devices via customer service interfaces. For example, in Figure 1, customer devices 1-3 are connected to OTN devices A, H, and F, respectively.
[0078] Depending on actual needs, an OTN device may have different functions. Generally, OTN devices are divided into optical layer devices, electrical layer devices and optoelectronic hybrid devices. Optical layer devices refer to devices that can process optical layer signals, such as optical amplifiers (OAs) and optical add-drop multiplexers (OADMs). OAs are mainly used to amplify optical signals to support transmission over longer distances while ensuring the specific performance of optical signals. OADMs are used to spatially transform optical signals so that they can be output from different output ports (also called directions). Electrical layer devices refer to devices that can process electrical layer signals, such as devices that can process OTN signals. Optoelectronic hybrid devices refer to devices that have the ability to process both optical layer signals and electrical layer signals. It should be noted that, depending on specific integration needs, an OTN device can integrate multiple different functions. The technical solution provided in this application is applicable to OTN devices of different forms and integration levels that contain electrical layer functions.
[0079] It should be noted that the data frame structure used by the optical transmission equipment in the embodiments of the present application may be an OTN frame, which is used to carry various service data and provide rich management and monitoring functions. The OTN frame may be an optical data unit frame (ODUk), ODUCn, ODUflex, optical channel transport unit k (OTUk), OTUCn, or flexible OTN (FlexO) frame. The difference between ODU frames and OTU frames is that OTU frames include ODU frames and OTU overhead. k represents different rate levels. For example, k=1 represents 2.5Gbps, and k=4 represents 100Gbps. Cn represents a variable rate, specifically a rate that is a positive integer multiple of 100Gbps. Unless otherwise specified, 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, which are also applicable to the present application. In addition, the method disclosed in this application can also be applied to other optical transport network frames such as FlexE frames.
[0080] Figure 2 is a schematic diagram of the structure of an OTN device. OTN device 200 can be any of the OTN devices A and H in Figure 1. As shown in Figure 2, OTN device 200 includes a tributary board 201, a cross-connect board 202, a circuit board 203, an optical layer processing board (not shown), and a system control and communication board 204.
[0081] The tributary board 201, cross-connect board 202, and line board 203 are used to process electrical layer signals. The tributary board 201 is used to receive and transmit various customer services, such as SDH services, packet services, Ethernet services, and / or fronthaul services. Furthermore, the tributary board 201 can be divided into a customer-side optical transceiver module and a signal processor. The customer-side optical transceiver module, also known as an optical transceiver, is used to receive and / or transmit service data. The signal processor is used to map and demap service data to data frames. The cross-connect board 202 is used to exchange data frames, completing the exchange of one or more types of data frames. The line board 203 primarily processes line-side data frames. Specifically, the line board 203 can be divided into a line-side optical module and a signal processor. The line-side optical module, also known as an optical transceiver, is used to receive and / or transmit data frames. The signal processor is used to multiplex and demultiplex, or map and demap, line-side data frames. The system control and communication board 204 is used to implement system control; specifically, information can be collected from different boards, or control instructions can be sent to the corresponding board. Unless otherwise specified, the specific components (such as signal processors) can be one or more, and this application does not impose any restrictions. It should also be noted that this application does not impose any restrictions on the type of boards included in the device, as well as the functional design and quantity of the boards. It should be noted that in a specific implementation, the above two boards may also be designed as one board. In addition, the network equipment may also include a backup power supply, a fan for heat dissipation, etc.
[0082] It should be understood that Figure 2 is only one example of the OTN equipment provided herein. Depending on specific needs, the type and number of boards included in an OTN device may vary. For example, an OTN device serving as a core node may not have a tributary board 201. Another example is an OTN device serving as an edge node that may have multiple tributary boards 201 or no optical cross-connect board 202. Furthermore, an OTN device that only supports electrical layer functions may not have an optical layer processing board.
[0083] As can be seen from the preceding description, this application uses OTN as an example to illustrate the method provided herein. In this case, the service frame can be an OSU frame or a multiframe composed of multiple OSU frames. The data frame can be an OTN frame or an OPU frame. The following describes an exemplary process by which an OTN device maps an OSU frame to an OTN frame.
[0084] Figure 3 is a schematic diagram of mapping an OSU frame to an OTN frame. As shown in Figure 3, OTN frame 302 has a structure of 4 rows and 3824 columns. OTN frame 302 includes an overhead area, a payload area, and a forward error correction (FEC) area. It should be understood that OTN frame 302 is merely an example. Other variations of OTN frames are also applicable to this application. For example, an OTN frame that does not include an FEC area. Another example is a frame structure with different numbers of rows and columns than OTN frame 302.
[0085] One or more OSU frames are mapped to the payload area of the OTN frame. As shown in Figure 3, OSU frame 301 includes an overhead area and a payload area. The overhead area of OSU frame 301 carries overhead information. The overhead information includes one or more overhead fields. The payload area of OSU frame 301 carries service data. It should be understood that the OSU frame structure shown in Figure 3 is only an example. In other specific implementations, the OSU frame may also include an overhead subframe. This application does not limit this.
[0086] In practical applications, the structure of the OSU frame is related to the operation, management, and maintenance (OAM) performance of the OTN. Therefore, designing an OSU frame that can improve OAM performance is an urgent problem to be solved.
[0087] To this end, the present application provides an OSU frame. Figure 4 is a first structural diagram of the OSU frame provided in an embodiment of the present application. As shown in Figure 4, the OSU frame 401 includes an overhead area and a payload area. The payload area includes an effective payload area and a padding payload area. The effective payload area is used to carry multiple data coding blocks. The size of the effective payload area is equal to the size of multiple data coding blocks. The padding payload area is used to fill in useless data. In practical applications, in order to avoid transmitting too much useless data, the size of the padding payload area can be smaller than the size of a single data coding block.
[0088] In this embodiment of the present application, the position of the payload area in the OSU frame is fixed. That is, the size and position of the payload area and padding payload area are fixed in two consecutive OSU frames transmitted by the OTN device. For example, the two consecutive OSU frames include a first OSU frame and a second OSU frame. In both the first and second OSU frames, the payload area is 1056 bytes in size, and the padding payload area is 4 bytes in size. The payload area is located between bytes 33 and 1088 in the OSU frame. The padding payload area is located between bytes 1089 and 1092 in the OSU frame. When the payload area is fixed in the OSU frame, the receiving device processing the OSU frame can determine the boundaries of the data coding block by determining the starting boundary of the OSU frame. Therefore, this embodiment of the present application can improve the efficiency of determining the boundaries of the data coding block, thereby improving OAM performance.
[0089] In practical applications, the size of the effective payload area of the OSU frame can be equal to the size of the payload area of the OSU frame. In this case, the OSU frame does not include a padding payload area. Figure 5 is a second structural schematic diagram of the OSU frame provided in an embodiment of the present application. As shown in Figure 5, the OSU frame 501 includes an overhead area and an effective payload area. The effective payload area is used to fill multiple data coding blocks. The data coding blocks can be simply referred to as coding blocks. In the example of Figure 5, the number of multiple data coding blocks is M. M is an integer greater than 1. In subsequent examples, the size of the effective payload area of the OSU frame is equal to the size of the payload area of the OSU frame.
[0090] As shown in Figure 3, one or more OSU frames can be mapped into the payload area of an OTN frame. In practical applications, the payload area of an OTN frame can be divided into multiple time slots, each of which is 16 bytes. Therefore, when the OSU frame size is an integer multiple of 16 bytes, the OSU frame occupies an integer number of time slots. This allows the receiving device to more efficiently determine the start boundary of the OSU frame, thereby improving OAM performance.
[0091] In practical applications, to facilitate the determination of the boundary between the overhead area and the effective payload area of the OSU frame, the size of the overhead area of the OSU frame can be an integer multiple of 16 bytes, such as 16 or 32 bytes. When the size of the OSU frame is an integer multiple of 16 bytes, the size of the effective payload area of the OSU frame is also an integer multiple of 16 bytes, such as 4224 or 5280 bytes.
[0092] As previously described, the size of the effective payload area of an OSU frame is equal to the size of multiple data coding blocks. Therefore, the size of an OSU frame is related to the size of a data coding block. The following describes the size of an OSU frame using data coding block sizes of 66 and 257 bits as examples.
[0093] When the data block size is 66 bits, the OSU frame size is 4×1064 bytes. "4×1064" represents 4 rows and 1064 columns. The payload area of the OSU frame is 4×1056 bytes. The overhead area of the OSU frame is 4×8 bytes. The payload area of the OSU frame can carry 512 66-bit data blocks. When the OSU frame bit rate is 10.4 Mbit / s, the OSU frame period is approximately 3.27 ms. For signals such as the alarm indication signal (AIS) or lock (LCK) signal, which require filtering within three frame periods, the transmission period is approximately 9.81 ms. In practical applications, to ensure OAM performance, the transmission period can be less than 15 ms. Therefore, when the OSU frame size is 4×1064 bytes, OAM performance is relatively reasonable. Furthermore, as the OSU frame bit rate increases, the OSU frame period will further decrease, providing even better OAM performance. Alternatively, when the data coding block size is 66 bits, the OSU frame size is 4 × 1328 bytes. The effective payload area of the OSU frame is 4 × 1320 bytes. The overhead area of the OSU frame is 4 × 8 bytes. The effective payload area of the OSU frame can carry 640 66-bit data coding blocks. When the OSU frame bit rate is 10.4 Mbit / s, the OSU frame period is approximately 4.09 ms. For signals such as AIS or LCK that require filtering over three frame periods, the transmission period is approximately 12.27 ms. Therefore, when the OSU frame size is 4 × 1328 bytes, OAM performance is relatively reasonable.
[0094] When the data block size is 257 bits, the service frame size is 4 × 1036 bytes. The service frame's payload area is 4 × 1028 bytes. The service frame's overhead area is 4 × 8 bytes. The OSU frame's payload area can carry 128 257-bit data blocks. When the OSU frame bit rate is 10.4 Mbit / s, the OSU frame period is approximately 3.19 ms. For signals such as AIS or LCK, which require filtering over three frame periods, the transmission period is approximately 9.56 ms. Therefore, when the OSU frame size is 4 × 1036 bytes, OAM performance is relatively reasonable. Alternatively, when the data block size is 257 bits, the service frame size is 4 × 1293 bytes. The service frame's payload area is 4 × 1258 bytes. The service frame's overhead area is 4 × 8 bytes. The OSU frame's payload area can carry 160 257-bit data blocks. When the OSU frame bit rate is 10.4 Mbit / s, the OSU frame period is approximately 3.98 ms. For signals such as AIS or LCK, which require filtering over three frame periods, the transmission period is approximately 11.94 ms. Therefore, when the OSU frame size is 4 × 1293 bytes, OAM performance is relatively reasonable.
[0095] When the data coding block size is 257 bits or 66 bits, the service frame size is 34,560 bytes, for example, 4×1080 bytes. The payload area size of the service frame is 34,304 bits, for example, 4×1072 bytes. The effective payload area size of the service frame is 33,924 bits. The padding payload area size of the service frame is 380 bits. The effective payload area of the OSU frame can carry 514 66-bit data coding blocks. Alternatively, the effective payload area of the OSU frame can carry 132 257-bit data coding blocks. It should be understood that in the aforementioned example, the 380-bit padding payload area can also be used to carry one or more data coding blocks. For example, 380 bits are used to carry one 257-bit coding block. In this case, the effective payload area size of the service frame is 34,181 bits. The padding payload area size of the service frame is 123 bits. The effective payload area of the OSU frame can carry 133 257-bit data coding blocks. Alternatively, 380 bits are used to carry five 66-bit code blocks. In this case, the effective payload area of the service frame is 34254 bits. The padding payload area of the service frame is 50 bits. The effective payload area of the OSU frame can carry 519 66-bit data code blocks.
[0096] In practical applications, a receiving device processing an OSU frame can determine the starting boundary of the OSU frame using the frame header indication overhead field. To improve the efficiency of determining the starting boundary of the OSU frame, the overhead area of the OSU frame can include multiple frame header indication overhead fields. Figure 6 is a first structural diagram of the overhead area of an OSU frame provided in an embodiment of the present application. As shown in Figure 6, the overhead area 601 of the OSU frame has a four-row, multi-column structure. The overhead area 601 of the OSU frame includes two frame header indication overhead fields (i.e., frame header indication 1 and frame header indication 2). The two frame header indication overhead fields can be located in the middle area of the overhead area 601 or in the middle of each row. The size of the two frame header indication overhead fields is 8 bits. In Figure 6, the blank area is used to carry other overhead fields. The specific content and size of the other overhead fields are not limited in this embodiment of the present application. For example, the other overhead fields include one or more of the overhead fields listed in Table 1.
[0097] Table 1
[0098] In the example of Figure 6, the frame header indication overhead field is located in the middle area of the overhead area 601. In actual applications, multiple frame header indication overhead fields can also be located at the starting position of the overhead area 601. For example, the frame header indication 1 overhead field is located in the first byte of the first row, and the frame header indication 2 overhead field is located in the first byte of the second row. When the number of rows in the overhead area of the OSU frame is 4 and the number of multiple frame header indication overhead fields is 2, in order to improve the efficiency of the receiving device in determining the starting boundary of the OSU frame, the multiple frame header indication overhead fields can be separated by one row. For example, the frame header indication 1 overhead field is located in the first byte of the first row, and the frame header indication 2 overhead field is located in the first byte of the third row. Alternatively, the frame header indication 1 overhead field is located in the first byte of the second row, and the frame header indication 2 overhead field is located in the first byte of the fourth row.
[0099] In actual applications, too many frame header indication overhead fields will also reduce transmission efficiency. In order to balance OAM performance and transmission efficiency, the number of multiple frame header indication overhead fields can be equal to the number of rows in the overhead area of the OSU frame or a multiple of the number of rows in the overhead area of the OSU frame. Figure 7 is a second structural schematic diagram of the overhead area of the OSU frame provided in an embodiment of the present application. As shown in Figure 7, the overhead area 701 of the OSU frame is a 4-row and multi-column structure. The overhead area 701 of the OSU frame includes 4 frame header indication overhead fields (frame header indication 1, frame header indication 2, frame header indication 3 and frame header indication 4). The 4 frame header indication overhead fields are located in the middle area of the overhead area 701. The size of each frame header indication overhead field is 8 bits. In Figure 7, the blank area is used to carry other overhead fields.
[0100] In practical applications, when the number of multiple frame header indication overhead fields is an integer multiple of the number of rows in the overhead area, each row in the overhead area may include the same number of frame header indication overhead fields. For example, in Figure 7, each row in overhead area 701 includes one frame header indication overhead field. For another example, when the number of multiple frame header indication overhead fields is 8 and the number of rows in the overhead area is 2, each row in overhead area 701 includes two frame header indication overhead fields.
[0101] As shown in Figures 6 and 7 , the overhead area of an OSU frame can include multiple header indication overhead fields. To improve the efficiency of the receiving device in determining the starting boundary of the OSU frame, these multiple header indication overhead fields can be different. In practical applications, these multiple header indication overhead fields can be completely different or partially different. These fields are described separately below.
[0102] In the first mode, the multiple frame header indication overhead fields are completely different. For example, the number of the multiple frame header indication overhead fields is 2. The frame header indication 1 overhead field and the frame header indication 2 overhead field both include 8 bits, with values of 00000000 and 11111111, respectively.
[0103] In the second approach, each of the multiple frame header indication overhead fields includes a frame header indication identification field and a first field. Figure 8 is a schematic diagram of the structure of the frame header indication overhead field provided in an embodiment of the present application. As shown in Figure 8, frame header indication overhead field 801 includes a frame header indication identification field and a first field. The receiving device determines the position of frame header indication overhead field 801 using the frame header indication identification field. For example, the frame header indication identification field includes 7 bits. The values of the 7 bits are 1111111. The first field is used to indicate the order of each frame header indication overhead field among the multiple frame header indication overhead fields. For example, the first field includes 1 bit. The value of the 1 bit of the frame header indication 1 overhead field is 0. "0" indicates that the frame header indication 1 overhead field is the first frame header indication overhead field among the multiple frame header indication overhead fields. The value of the 1 bit of the frame header indication 2 overhead field is 1. "1" indicates that the frame header indication 2 overhead field is the second frame header indication overhead field among the multiple frame header indication overhead fields.
[0104] In practical applications, the overhead area of the OSU frame may include a JC overhead field for carrying mapping overhead information. In an embodiment of the present application, in order to reduce the size of the overhead that needs to be transmitted, the size of the JC overhead field may be less than 4 bytes. When the JC overhead field includes multiple overhead fields, the size of the JC overhead field refers to the sum of the sizes of the multiple overhead fields. Figure 9 is a third structural schematic diagram of the overhead area of the OSU frame provided in an embodiment of the present application. As shown in Figure 9, the overhead area 901 of the OSU frame has a 4-row, multi-column structure. The overhead area 901 of the OSU frame includes 2 JC overhead fields (JC1 and JC2, respectively). The JC1 overhead field is located in the first row. The JC2 overhead field is located in the second row. The size of each JC overhead field is 1 byte. In Figure 9, the size of the JC overhead field is 2 bytes.
[0105] It should be understood that the size of the JC overhead field is related to the size of the effective payload area of the OSU frame, the mapping granularity, or the degree of compression of the mapping overhead information. Therefore, to reduce the size of the JC overhead field, the transmitting device can reduce the size of the effective payload area of the OSU frame, or increase the mapping granularity, or compress the mapping overhead information. For example, for constant bit rate (CBR) service mapping, the transmitting device can only transmit the incremental change of its Cm value through the JC overhead field (Cm represents the amount of service data carried in each frame with m bits as the basic data unit). For another example, the size of the OSU frame is less than or equal to the size of the payload area of the OTN frame.
[0106] In practical applications, the overhead area of the OSU frame may include a DM overhead field for carrying delay information. To improve delay measurement accuracy, the size of the DM overhead field may be greater than or equal to 10 bits. For example, the size of the DM overhead field is 16 or 20 bits. When the DM overhead field includes multiple overhead fields, the size of the DM overhead field refers to the sum of the sizes of the multiple overhead fields. Figure 10 is a fourth structural schematic diagram of the overhead area of the OSU frame provided in an embodiment of the present application. As shown in Figure 10, the overhead area 1001 of the OSU frame has a 4-row, multi-column structure. The overhead area 1001 of the OSU frame includes two DM overhead fields (TCM DM and PM DM, each with a size of 1 byte), totaling 2 bytes. The TCM DM overhead field is located in the third row. The PM DM overhead field is located in the fourth row.
[0107] In practical applications, to improve fault handling speed, the overhead area of the OSU frame can include both the PM APS overhead field and the TCM APS overhead field. Figure 11 is a fifth structural diagram of the overhead area of the OSU frame provided in an embodiment of the present application. As shown in Figure 11, the overhead area 1101 of the OSU frame has a four-row, multi-column structure. The overhead area 1101 of the OSU frame includes the PM APS overhead field and the TCM APS overhead field. The TCM APS overhead field can be either the TCM1 APS overhead field or the TCM2 APS overhead field. To further improve fault handling speed, each OSU frame transmitted by the sending device can include both the PM APS overhead field and the TCM APS overhead field.
[0108] Figure 12 is a sixth structural diagram of the overhead area of an OSU frame provided by an embodiment of the present application. As shown in Figure 12, the overhead area 1201 of the OSU frame has a structure of 4 rows and 8 columns. The size of overhead area 1201 is 4 x 8 bytes. Overhead area 1201 includes four frame header indication overhead fields. These four frame header indication overhead fields are located in the first and second columns. Each frame header indication overhead field includes a frame header indication identification field and a first field. The frame header indication identification field is also called a FAS field. Each FAS field is 14 bits in size. Each first field is 2 bits in size. Overhead area 1201 also includes three JC overhead fields (JC1, JC2, and JC3). The three JC overhead fields are located in the eighth column. Each JC overhead field is 1 byte in size. Overhead area 1201 also includes two DM overhead fields (TCM DM and PM DM). The two DM overhead fields are located in the sixth column. Each DM overhead field is 1 byte in size. Overhead area 1201 also includes a PM APS field and a TCM APS field. The PM APS field and the TCM APS field are located in the seventh column. Each APS field is 1 byte in size. In Figure 12, BEI / BIAE indicates the BEI overhead field or the BIAE overhead field. For detailed descriptions of the other fields, please refer to Figure 12 and Table 1 and are not repeated here.
[0109] Figure 13 is a third schematic diagram of the structure of an OSU frame provided in an embodiment of the present application. As shown in Figure 13 , the overhead area of OSU frame 1301 includes multiple sub-overhead areas (a first sub-overhead area and a second sub-overhead area). The payload area of OSU frame 1301 includes multiple sub-payload areas (a first sub-payload area and a second sub-payload area). The sub-overhead areas within the multiple sub-overhead areas and the sub-payload areas within the multiple sub-payload areas are alternately arranged. Each of the multiple sub-overhead areas includes a target overhead field.
[0110] The target overhead field may include a frame header indication overhead field and / or an accumulated delay overhead field. The accumulated delay overhead field may also be referred to as an ADV overhead field. For a description of the ADV overhead field, reference may be made to the description in Table 1 above. When the target overhead field includes a frame header indication overhead field, each of the multiple sub-overhead areas includes a frame header indication overhead field. When the target overhead field includes an accumulated delay overhead field, each of the multiple sub-overhead areas includes an accumulated delay overhead field. When the target overhead field includes a frame header indication overhead field and an accumulated delay overhead field, each of the multiple sub-overhead areas includes a frame header indication overhead field and an accumulated delay overhead field. The following description takes the case where the target overhead field includes a frame header indication overhead field as an example.
[0111] Figure 14 is a first schematic diagram of the structure of the first sub-overhead area provided in an embodiment of the present application. As shown in Figure 14, the first sub-overhead area 1401 includes a frame header indication 1 overhead field and an ADV overhead field. The size of the frame header indication 1 overhead field is 2 bytes. The size of the ADV overhead field is 4 bytes. In Figure 14, the blank area is used to carry other overhead fields. The embodiment of the present application does not limit the specific content and size of other overhead fields. For example, other overhead fields include one or more overhead fields in Table 1. Figure 15 is a first schematic diagram of the structure of the second sub-overhead area provided in an embodiment of the present application. As shown in Figure 15, the second sub-overhead area 1501 includes a frame header indication 2 overhead field. The size of the frame header indication 2 overhead field is 2 bytes. In Figure 15, the blank area is used to carry other overhead fields. It should be understood that the contents of the frame header indication 2 overhead field and the frame header indication 1 overhead field can be completely different or partially different.
[0112] In practical applications, to reduce the complexity of OSU frame processing on a receiving device, the size of each of the multiple overhead sub-areas can be an integer multiple of 8 or 16 bytes. Similarly, the size of the sub-payload area between any two adjacent sub-overhead areas can be an integer multiple of 8 or 16 bytes. For example, in Figure 13, the size of the first sub-payload area is 1888 bytes.
[0113] In order to improve the efficiency of service frames in carrying data, service frames can be composed of N service subframes. N is an integer greater than 1. The following description will be made using N equal to 4 as an example. Figure 16 is a fourth structural diagram of the OSU frame provided in an embodiment of the present application. As shown in Figure 16, the OSU frame 1601 is a multiframe composed of 4 service subframes. The 4 service subframes are service subframes 1 to 4. Among them, service subframe 1 includes sub-overhead area 1, sub-payload area 1, sub-overhead area 2 and sub-payload area 2. For the description of other service subframes, please refer to the description of service subframe 1. OSU frame 1601 includes a first sub-overhead area, a second sub-overhead area, a first sub-payload area and a second sub-payload area. Among them, the first sub-overhead area includes sub-overhead area 1, sub-overhead area 3, sub-overhead area 5 and sub-overhead area 7. For the description of other sub-overhead areas or sub-payload areas, please refer to the description of the first sub-overhead area.
[0114] To further increase the frequency of target overhead field transmission, each sub-overhead area of a multiframe may include N target overhead fields. These N target overhead fields correspond one-to-one to N service subframes, meaning each service subframe includes one target overhead field in each sub-overhead area.
[0115] In practical applications, to reduce the complexity of multiframe processing on the receiving device, the multiframe size can be 4×3824 bytes. The size of each service subframe is 3824 bytes. In Figure 16, OSU frame 1601 includes 4 rows and 3824 columns. The first sub-overhead area can be located from columns 1 to 16. The size of the first sub-overhead area is 4×16 bytes. The first sub-payload area can be located from columns 17 to 1904. The size of the first sub-payload area is 4×1888 bytes. The second sub-overhead area can be located from columns 1905 to 1920. The size of the second sub-overhead area is 4×16 bytes. The second sub-payload area can be located from columns 1921 to 3824. The size of the second sub-payload area is 4×1904 bytes. The following describes the first sub-overhead area and the second sub-overhead area, each sized at 4×16 bytes.
[0116] Figure 17 is a second schematic diagram of the structure of the first sub-overhead area provided in an embodiment of the present application. As shown in Figure 17, the size of the first sub-overhead area 1701 is 4×16 bytes. The first sub-overhead area 1701 includes four rows, each row corresponding to the sub-overhead area of a service subframe. The size of the sub-overhead area of each service subframe is 16 bytes. The sub-overhead area of each service subframe includes a frame header indication 1 overhead field, an MFAS overhead field, a TCM2 overhead field, a TCM1 overhead field, a PM overhead field, and an ADV overhead field. Each overhead field is described below.
[0117] The size of the Frame Header Indication 1 Overhead field is 2 bytes. The Frame Header Indication 1 Overhead field may include the Frame Header Indication Identifier field. The value of the Frame Header Indication 1 Overhead field may be 0xF628.
[0118] The MFAS overhead field is 1 byte in size. It increments as the service subframe changes, and its value ranges from 0 to 255. For example, in service subframe 1, the MFAS overhead field has a value of 0. In service subframe 2, the MFAS overhead field has a value of 1.
[0119] The TCM2 overhead field is 3 bytes in size. The TCM2 overhead field includes a TTI overhead field, a BIP overhead field, a BEI overhead field, a BDI / BIAE overhead field, and / or a STAT overhead field. For example, the TCM2 overhead field includes a 1-byte TTI overhead field, a 1-byte BIP overhead field, a 4-bit BEI overhead field, a 1-bit BDI / BIAE overhead field, and a 3-bit STAT overhead field.
[0120] The TCM1 overhead field is 3 bytes in size. The TCM1 overhead field includes a TTI overhead field, a BIP overhead field, a BEI overhead field, a BDI / BIAE overhead field, and / or a STAT overhead field. For example, the TCM1 overhead field includes a 1-byte TTI overhead field, a 1-byte BIP overhead field, a 4-bit BEI overhead field, a 1-bit BDI / BIAE overhead field, and a 3-bit STAT overhead field.
[0121] The PM overhead field is 3 bytes in size. The PM overhead field includes a TTI overhead field, a BIP overhead field, a BEI overhead field, a BDI / BIAE overhead field, and / or a STAT overhead field. For example, the PM overhead field includes a 1-byte TTI overhead field, a 1-byte BIP overhead field, a 4-bit BEI overhead field, a 1-bit BDI overhead field, and a 3-bit STAT overhead field.
[0122] The ADV overhead field is 4 bytes long. The ADV overhead field can use the frame header indication 1 overhead field as a reference point. The ADV overhead field is used by the receiving device to recover the service clock.
[0123] Figure 18 is a second structural diagram of the second sub-overhead area provided in an embodiment of the present application. As shown in Figure 18, the size of the second sub-overhead area 1801 is 4×16 bytes. The second sub-overhead area 1801 includes four rows, each row corresponding to the sub-overhead area of a service subframe. The size of the sub-overhead area of each service subframe is 16 bytes. The sub-overhead area of each service subframe includes the frame header indication 2 overhead field, the TCM DM overhead field, the PM DM overhead field, the TCM APS overhead field, the PM APS overhead field, the RES overhead field, the PT overhead field, the ADV overhead field, and the POH overhead field. Each overhead field is described below.
[0124] The Frame Header Indication 2 Overhead field is 2 bytes in size. The Frame Header Indication 2 Overhead field can be different from the Frame Header Indication 1 Overhead field. For example, the value of the Frame Header Indication 2 Overhead field can be the negation of 0xF628. The different values of the Frame Header Indication 2 Overhead field and the Frame Header Indication 1 Overhead field are used to indicate the order of the Frame Header Indication 2 Overhead field and the Frame Header Indication 1 Overhead field in each service subframe.
[0125] The TCM DM, PM DM, TCM APS, and PM APS overhead fields can all be 1 byte in size. The RES overhead field is 3 bytes in size. The PT overhead field is 1 byte in size. The ADV overhead field is 4 bytes in size. The ADV overhead field can use the Frame Header Indication 2 overhead field as a reference point. The POH overhead field is 2 bytes in size. It should be understood that for the description of the various overhead fields in Figures 17 and 18, reference can be made to the description in Table 1 above.
[0126] It should be understood that Figures 13 and 16 are merely two examples of OSU frames provided in the embodiments of the present application. In practical applications, those skilled in the art may adapt the structure of the OSU frame as needed. For example, the OSU frame includes three overhead sub-areas and two payload sub-areas. It should be understood that the OSU frames described in Figures 13 to 18 share similarities with the OSU frames described in Figures 4 to 12. Therefore, the description of the OSU frames in Figures 13 to 18 can refer to the description of the OSU frames in Figures 4 to 12. For example, in Figure 13, the multiple payload sub-areas include a payload area. The size of the payload area is less than or equal to the size of the multiple payload sub-areas. The payload area is used to carry multiple coding blocks. The size of the multiple coding blocks is equal to the size of the payload area. In another example, the multiple payload sub-areas also include a padding payload area. The padding payload area is used to fill in useless data. The sum of the sizes of the padding payload area and the payload area is equal to the size of the multiple payload sub-areas.
[0127] The OSU frame provided in the embodiment of the present application is described above. The data mapping method and data demapping method provided in the embodiment of the present application are described below. Figure 19 is a flow chart of the data mapping method provided in the embodiment of the present application. As shown in Figure 19, the data mapping method includes the following steps.
[0128] In 1901, a sending device obtains a plurality of data encoding blocks.
[0129] The sending device may be an OTN device or an MTN device, etc. The sending device generates multiple data coding blocks, or the sending device receives multiple data coding blocks from other devices. The embodiment of the present application does not limit the size of each of the multiple data coding blocks. For example, the size of each data coding block may be 66 bits or 257 bits.
[0130] In 1902, the transmitting device maps multiple data coding blocks to the effective payload area of the service frame. The size of the effective payload area of the service frame is equal to the size of the multiple data coding blocks.
[0131] The service frame can be an OSU frame or other data frame with an OSU-like frame structure. The size of the effective payload area of the service frame can be smaller than or equal to the size of the payload area of the service frame. When the size of the effective payload area of the service frame is smaller than the size of the payload area of the service frame, the payload area of the service frame also includes a padding payload area. The padding payload area is used to fill in useless data. The size of the effective payload area of the service frame is equal to the size of multiple data coding blocks. It should be understood that for the description of the service frame, reference can be made to the description of any of Figures 4 to 18.
[0132] In 1903, the sending device maps the service frame to the payload area of the data frame.
[0133] The data frame can be an OTN frame, a FlexE frame, or an MTN frame. When the data frame is an OTN frame, it can have a structure of 4 rows and 3824 columns. The data frame can also include an overhead area. For example, the overhead area of a data frame is 4 x 16 bytes. The payload area of a data frame is 4 x 3808 bytes. For more information about step 1903, see Figure 3.
[0134] In 1904, the sending device sends a data frame.
[0135] The transmitting device sends a data frame to the receiving device. The receiving device can be another OTN device or an MTN device. The transmitting and receiving devices are connected via optical fiber. After receiving the data frame, the transmitting device modulates the data frame onto an optical carrier to generate an optical signal. The transmitting device then transmits the optical signal to the receiving device via optical fiber.
[0136] Figure 20 is a flow chart of a data demapping method according to an embodiment of the present invention. As shown in Figure 20, the data demapping method includes the following steps.
[0137] In step 2001, a receiving device receives a data frame from a sending device.
[0138] The receiving device can be an OTN device or an MTN device. The receiving device and the transmitting device are connected via an optical fiber. The receiving device receives optical signals from the transmitting device via the optical fiber. The receiving device demodulates the optical signals to obtain data frames.
[0139] In step 2002, the receiving device extracts a service frame from a data frame.
[0140] A data frame consists of an overhead area and a payload area. For example, the overhead area of a data frame is 4 x 16 bytes. The payload area of a data frame is 4 x 3808 bytes. The payload area of a data frame includes one or more service frames. Service frames can be OSU frames or other data frames with OSU-like structures.
[0141] In step 2003, the receiving device extracts multiple data encoding blocks from the service frame. The size of the effective payload area of the service frame is equal to the size of the multiple data encoding blocks.
[0142] The effective payload area of the service frame includes multiple data coding blocks. The size of the effective payload area of the service frame is equal to the size of the multiple data coding blocks. The embodiment of the present application does not limit the size of each data coding block in the multiple data coding blocks. For example, the size of each data coding block can be 66 bits or 257 bits. The size of the effective payload area of the service frame can be less than or equal to the size of the payload area of the service frame. When the size of the effective payload area of the service frame is less than the size of the payload area of the service frame, the payload area of the service frame also includes a padding payload area. The padding payload area is used to fill in useless data.
[0143] It should be understood that the description of the data demapping method is similar to the description of the aforementioned data mapping method and service frame. Therefore, the description of the data demapping method can refer to any of the descriptions in Figures 4 to 18. For example, the overhead area of the service frame includes multiple different frame header indication overhead fields. The receiving device determines the starting boundary of the service frame based on the multiple frame header indication overhead fields. For another example, the overhead area of the service frame includes a DM overhead field. The size of the DM overhead field is 8 bits. The receiving device determines the delay between the receiving device and the transmitting device based on the DM overhead field.
[0144] Figure 21 is a schematic diagram of the structure of a transmitting device provided in an embodiment of the present application. As shown in Figure 21, transmitting device 2100 includes an acquisition module 2101, a mapping module 2102, and a transmitting module 2103. Acquisition module 2101 is used to acquire multiple data coding blocks. Mapping module 2102 is used to map the multiple data coding blocks to the effective payload area of a data frame. Transmitting module 2103 is used to transmit the data frame. The size of the multiple data coding blocks is equal to the size of the effective payload area of the data frame.
[0145] It should be understood that the description of the transmitting device 2100 is similar to the description of the aforementioned data mapping method and service frame. Therefore, for the description of the service frame in the transmitting device 2100, reference may be made to the description of any of Figures 4 to 18. For the description of the steps performed by each module in the transmitting device 2100, reference may be made to the description of Figure 19. For example, the size of each data encoding block in the multiple data encoding blocks is 66 bits. For another example, the overhead area of the service frame includes multiple different frame header indication overhead fields.
[0146] Figure 22 is a schematic diagram of the structure of a receiving device provided in an embodiment of the present application. As shown in Figure 22, receiving device 2200 includes a receiving module 2201 and an extraction module 2202. Receiving module 2201 is configured to receive data frames from a transmitting device. Extraction module 2202 is configured to extract service frames from the payload area of the data frames. Extraction module 2202 can also be configured to extract multiple data coding blocks from the effective payload area of the data frames. The size of the multiple data coding blocks is equal to the size of the effective payload area of the data frames.
[0147] It should be understood that the description of the receiving device 2200 is similar to the description of the aforementioned data demapping method and service frame. Therefore, for the description of the service frame in the receiving device 2200, reference may be made to the description of any of Figures 4 to 18. For the description of the steps performed by each module in the receiving device 2200, reference may be made to the description of Figure 20. For example, the receiving device 2200 also includes a processing module. The overhead area of the service frame includes multiple different frame header indication overhead fields. The processing module is further configured to determine the starting boundary of the service frame based on the multiple frame header indication overhead fields. For another example, the overhead area of the service frame includes a DM overhead field, which is 8 bits in size. The processing module determines the delay between the receiving device 2200 and the transmitting device based on the DM overhead field.
[0148] Figure 23 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device can be a transmitting device or a receiving device. As shown in Figure 23, the communication device 2300 includes a processor 2301 and a transceiver 2302. The processor 2301 can be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 2301 can further include a hardware chip or other general-purpose processor. The above-mentioned hardware chip can be an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The transceiver 2302 can be an optical transceiver.
[0149] When the communication device 2300 is a transmitting device, the processor 2301 is configured to obtain multiple data coding blocks. The processor 2301 is further configured to map the multiple data coding blocks to the effective payload area of the data frame. The size of the multiple data coding blocks is equal to the size of the effective payload area of the data frame. The transceiver 2302 is configured to transmit the data frame.
[0150] When communication device 2300 is a receiving device, transceiver 2302 is configured to receive a data frame from a transmitting device. Processor 2301 is configured to extract a service frame from the payload area of the data frame. Processor 2301 may also be configured to extract multiple data coding blocks from the effective payload area of the data frame. The size of the multiple data coding blocks is equal to the size of the effective payload area of the data frame.
[0151] In other embodiments, the communication device 2300 may further include a memory 2303. The memory 2303 may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), or flash memory. The volatile memory may be a random access memory (RAM). The memory 1703 may be used to store data frames or service frames or other codes used to control and manage the device.
[0152] For a description of a service frame in communication device 2300, reference may be made to the description of the service frame in any one of Figures 4 to 18 . When communication device 2300 is a transmitting device, for a description of the steps executed by communication device 2300, reference may also be made to the description of the transmitting device in Figures 19 or 21 . When communication device 2300 is a receiving device, for a description of the steps executed by communication device 2300, reference may also be made to the description of the receiving device in Figures 20 or 22 .
[0153] The present application also provides a communication system. Figure 24 is a schematic diagram of the structure of the communication system provided in an embodiment of the present application. As shown in Figure 24, the communication system 2400 includes a sending device 2401 and a receiving device 2402. The sending device 2401 is used to obtain multiple data coding blocks and map the multiple data coding blocks to the effective payload area of the data frame. The size of the multiple data coding blocks is equal to the size of the effective payload area of the data frame. The sending device 2401 is also used to send data frames. The receiving device 2402 is used to receive data frames from the sending device and extract service frames from the payload area of the data frame. The receiving device 2402 can also be used to extract multiple data coding blocks from the effective payload area of the data frame.
[0154] For a description of the service frame in communication system 2400, refer to the description of the service frame in any of Figures 4 to 18. For a description of the steps performed by transmitting device 2401, refer to the description of the data mapping method in Figure 19. For a description of the steps performed by receiving device 2402, refer to the description of the data demapping method in Figure 20.
[0155] The above is only a specific implementation method of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with this technical field can easily think of changes or replacements within the technical scope disclosed in this application, which should be covered by the protection scope of the present application.
Claims
1. A data mapping method, characterized in that: include: The sending device obtains multiple data encoding blocks; The sending device maps the multiple data coding blocks to an effective payload area of a service frame, where the size of the effective payload area of the service frame is equal to the size of the multiple data coding blocks; The sending device maps the service frame to the payload area of the data frame; The sending device sends the data frame.
2. The data mapping method according to claim 1, wherein: The size of the service frame is an integer multiple of 16 bytes.
3. The data mapping method according to claim 1 or 2, characterized in that: The size of the effective payload area of the service frame is an integer multiple of 16 bytes, and the size of the overhead area of the service frame is an integer multiple of 16 bytes.
4. The data mapping method according to any one of claims 1 to 3, characterized in that: The size of each data encoding block in the multiple data encoding blocks is 66 bits.
5. The data mapping method according to claim 4, characterized in that: The size of the service frame is 4×1064 bytes, the size of the effective payload area of the service frame is 4×1056 bytes, and the size of the overhead area of the service frame is 4×8 bytes.
6. The data mapping method according to claim 4, characterized in that: The size of the service frame is 4×1328 bytes, the size of the effective payload area of the service frame is 4×1320 bytes, and the size of the overhead area of the service frame is 4×8 bytes.
7. The data mapping method according to any one of claims 1 to 3, characterized in that: The size of each data coding block in the M data coding blocks is 257 bits.
8. The data mapping method according to claim 7, characterized in that: The size of the service frame is 4×1036 bytes, the size of the effective payload area of the service frame is 4×1028 bytes, and the size of the overhead area of the service frame is 4×8 bytes.
9. The data mapping method according to claim 7, characterized in that: The size of the service frame is 4×1293 bytes, the size of the effective payload area of the service frame is 4×1258 bytes, and the size of the overhead area of the service frame is 4×8 bytes.
10. The data mapping method according to any one of claims 1 to 9, characterized in that: The overhead area of the service frame includes a plurality of different frame header indication overhead fields.
11. The data mapping method according to claim 10, wherein: Each frame header indication overhead field in the multiple frame header indication overhead fields includes a frame header indication identification field and a first field, where the first field is used to represent the order of each frame header indication overhead field in the multiple frame header indication overhead fields.
12. The data mapping method according to claim 10 or 11, characterized in that: The number of the multiple frame header indication overhead fields is the number of rows in the overhead area of the service frame.
13. The data mapping method according to any one of claims 1 to 12, characterized in that: The overhead area of the service frame includes a delay measurement DM overhead field, and the size of the DM overhead field is 16 bits.
14. The data mapping method according to any one of claims 1 to 13, characterized in that: The overhead area of the service frame includes a justification control JC overhead field, and the size of the JC overhead field is less than 4 bytes.
15. The data mapping method according to any one of claims 1 to 14, characterized in that: The overhead area of the service frame includes a path monitoring automatic protection switching (PM APS) overhead field and a tandem connection monitoring (TCM APS) overhead field.
16. The data mapping method according to any one of claims 1 to 4 and 7, characterized in that: The overhead area of the service frame includes multiple sub-overhead areas, and the payload area of the service frame includes multiple sub-payload areas. The sub-overhead areas in the multiple sub-overhead areas and the sub-payload areas in the multiple sub-payload areas are alternately distributed, and each sub-overhead area in the multiple sub-overhead areas includes a target overhead field.
17. The data mapping method according to claim 16, characterized in that: The target overhead field includes a frame header indication overhead field and / or an accumulated delay overhead field.
18. The data mapping method according to claim 16 or 17, characterized in that: The size of the sub-payload area between any two adjacent sub-overhead areas in the multiple sub-overhead areas is an integer multiple of 8 or 16 bytes.
19. The data mapping method according to any one of claims 16 to 18, characterized in that: The service frame is a multiframe composed of N service subframes, where N is an integer greater than 1.
20. The data mapping method according to claim 19, wherein: The N is 4, and the size of the N service subframes is 4×3824 bytes.
21. A data demapping method, characterized in that: include: The receiving device receives the data frame from the sending device; The receiving device extracts the service frame from the payload area of the data frame; The receiving device extracts a plurality of data coding blocks from an effective payload area of the service frame, and a size of the effective payload area of the service frame is equal to a size of the plurality of data coding blocks.
22. The data demapping method according to claim 21, wherein: The overhead area of the service frame includes a plurality of different frame header indication overhead fields, and the method further includes: The receiving device determines the starting boundary of the service frame according to the multiple frame header indication overhead fields.
23. The data demapping method according to claim 21 or 22, characterized in that: The overhead area of the service frame includes a delay measurement DM overhead field, the size of the DM overhead field is 16 bits, and the method further includes: The receiving device determines a delay between the receiving device and the sending device according to the DM overhead field.
24. A sending device, characterized in that: It includes acquisition module, mapping module and sending module, among which: The acquisition module is used to acquire multiple data encoding blocks; The mapping module is configured to perform the method according to any one of claims 1 to 20 to obtain a data frame according to the plurality of data coding blocks; The sending module is used to send the data frame.
25. A receiving device, characterized in that: It includes a receiving module and an extraction module, wherein: The receiving module is used to receive data frames from a sending device; The extraction module is used to execute the method described in any one of claims 21 to 23 to obtain multiple data coding blocks according to the data frame.
26. A sending device, characterized in that: Includes a processor and a transceiver, including: The processor is configured to execute the method according to any one of claims 1 to 20 to obtain a data frame; The transceiver is used to send the data frame.
27. A receiving device, characterized in that: Includes a processor and a transceiver, including: The transceiver is used to receive data frames; The processor is configured to execute the method according to any one of claims 21 to 23 to obtain a plurality of data coding blocks according to the data frame.
