Data mapping methods, data demapping methods, and related equipment

Abstract

This application provides a data mapping method applied in the field of communications. The data mapping method includes the following steps: a transmitting device acquires multiple data encoded blocks. The transmitting device maps the multiple data encoded blocks to the payload area of ​​a service frame. The size of the payload area of ​​the service frame is equal to the size of the multiple data encoded blocks. The transmitting device maps the service frame to the payload area of ​​the data frame. The transmitting device transmits the data frame. By designing the size of the payload area of ​​the service frame, the technical solution disclosed in this application reduces the processing complexity of the device, while also meeting the requirements for operation, management, and maintenance performance of low-rate services carried by this service frame.

Description

[0001] This application claims priority to Chinese Patent Application No. 202211465674.X, filed on November 22, 2022, entitled "Data Mapping Method, Data Demapping Method and Related Equipment", filed on December 2, 2022, filed on the same date, which are incorporated herein by reference in their entirety. Technical Field

[0002] This application relates to the field of communications, and in particular to data mapping methods, data demapping methods, and related equipment. Background Technology

[0003] Due to its high bandwidth, large capacity, high reliability, and low latency, the optical transport network (OTN) has become the mainstream technology adopted by 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 can be mapped to OTN frames. The structure of the OSU frame is related to the operation, administration, and maintenance (OAM) performance of the OTN (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. Summary of the Invention

[0005] This application provides a data mapping method, a data demapping method, and related equipment. By designing the size of the effective payload area of ​​the service frame, the efficiency of the receiving equipment in determining the boundary of the data coding block can be improved, thereby improving OAM performance.

[0006] This application provides a data mapping method in its first aspect. The data mapping method includes the following steps: A transmitting device acquires multiple data encoded blocks. The transmitting device can be an OTN device or a metro transport network (MTN) device, etc. The transmitting device maps the multiple data encoded blocks to the 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 frames with similar OSU frame structures. The size of the payload area of ​​the service frame can be less than or equal to the size of the service frame's payload area. When the size of the payload area of ​​the service frame is less than the size of the service frame's payload area, the payload area of ​​the service frame also includes a padding payload area. The padding payload area is used to fill in unused data. The size of the payload area of ​​the service frame is equal to the size of the multiple data encoded blocks. The transmitting device maps the service frame to the payload area of ​​a data frame. The data frame can be an OTN frame, a flexible Ethernet (FlexE) frame, or an MTN frame, etc. The transmitting device transmits the data frame.

[0007] In this application, the size of the multiple data coding blocks is equal to the size of the effective payload area. The position of the effective payload area within the service frame is fixed. Therefore, after determining the start boundary of the service frame, the receiving device determines the data coding block boundaries. Thus, this application can improve the efficiency of determining data coding block boundaries, thereby improving OAM performance.

[0008] In one alternative approach of the first aspect, the size of the service frame is an integer multiple of 16 bytes. When the payload area of ​​a data frame is divided into multiple time slots, with each time slot having an interleaving size of 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 start boundary of the service frame.

[0009] In one alternative approach of the first aspect, the size of the payload area of ​​the service frame is an integer multiple of 16 bytes. The size of the overhead area of ​​the service frame is also an integer multiple of 16 bytes. When the time slot interpolation granularity of the data frame is 16 bytes, both the payload area and the overhead area of ​​the service frame occupy an integer number of time slots, thereby reducing the complexity of processing OSU frames.

[0010] In one alternative approach of the first aspect, the size of each of the M data coding blocks is 66 bits.

[0011] In one alternative embodiment 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 this application, when the size of the data encoding block is 66 bits, the entire payload area of ​​the service frame can be used to carry the data encoding block, thereby improving transmission efficiency. In another alternative embodiment 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 this application, when the size of the data encoding block is 66 bits, the entire payload area of ​​the service frame can be used to carry the data encoding block, thereby improving transmission efficiency.

[0012] In one alternative approach of the first aspect, each of the M data coding blocks is 257 bits in size. Compared to 66-bit coding blocks, 257-bit coding blocks can further improve carrying efficiency.

[0013] In one alternative embodiment 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 this application, when the size of the data encoding block is 257 bits, the entire payload area of ​​the service frame can be used to carry the data encoding block, improving transmission efficiency. In another alternative embodiment 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 this application, when the size of the data encoding block is 257 bits, the entire payload area of ​​the service frame can be used to carry the data encoding block, improving transmission efficiency.

[0014] In one alternative approach of the first aspect, the overhead region of the service frame includes multiple different frame header indication overhead fields. By adding frame header indication overhead fields, the efficiency of determining the start boundary of the service frame can be improved.

[0015] In one alternative embodiment of the first aspect, each of the plurality of frame header indication overhead fields includes a frame header indication identifier field and a first field. The first field is used to characterize the order of each frame header indication overhead field among the plurality of frame header indication overhead fields. By adding the first field, the efficiency of determining the start boundary of a service frame can be improved.

[0016] In one alternative approach of the first aspect, the number of overhead fields in the multiple frame headers is equal to the number of rows in the overhead area of ​​the service frame.

[0017] In one alternative embodiment of the first aspect, the overhead area of ​​the service frame includes a delay measurement (DM) overhead field. The DM overhead field is 16 bits in size. By increasing the size of the DM overhead field, more timestamp information can be transmitted. Therefore, this application can improve the accuracy of delay measurement.

[0018] In one alternative approach 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 amount of overhead that needs to be transmitted can be reduced, thereby improving transmission efficiency.

[0019] In one alternative approach 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. Transmitting both the PM APS overhead field and the TCM APS overhead field simultaneously in a single data frame can improve the speed of fault handling.

[0020] In one alternative approach of the first aspect, the size of the service frame is less than or equal to the size of the payload area of ​​the data frame.

[0021] In one alternative approach of the first aspect, the service frame is an OSU frame, and the data frame is an OTN frame.

[0022] In one alternative embodiment of the first aspect, the overhead area of ​​the service frame comprises multiple sub-overhead areas. The payload area of ​​the service frame comprises multiple sub-payload areas. The sub-overhead areas within the multiple sub-overhead areas and the sub-payload areas within the multiple sub-payload areas are distributed alternately. Each of the multiple sub-overhead areas includes a target overhead field. By setting 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.

[0023] In one alternative embodiment of the first aspect, the target overhead field includes a frame header indication overhead field and / or a cumulative delay overhead field. When the target overhead field includes a frame header indication overhead field, the efficiency of determining the start boundary of a service frame can be improved. When the target overhead field includes a cumulative delay overhead field, the clock recovery performance of the receiving device can be improved.

[0024] In one alternative approach of the first aspect, the size of the sub-payload area between any two adjacent 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 level of processing capacity while reducing processing complexity.

[0025] In one alternative approach of the first aspect, the service frame is a complex frame composed of N service subframes. N is an integer greater than 1. Carrying data through a complex frame composed of multiple service subframes can improve carrying efficiency.

[0026] In one alternative 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 matches the structure of the OTN frame. Therefore, this application can reduce the complexity of the receiving device in processing multiframes.

[0027] In one alternative approach 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.

[0028] In one alternative approach of the first aspect, each of the N service subframes occupies a size that is an integer multiple of 8 or 16 bytes in each sub-overhead area. By setting the size occupied by each service subframe in each sub-overhead area, the processing complexity can be reduced.

[0029] In one alternative approach of the first aspect, the number of sub-overhead areas is two. Increasing the number of sub-overhead areas can increase the frequency of transmitting the target overhead field, thereby improving OAM performance. However, introducing too many sub-overhead areas also increases the complexity of the receiving device in processing service frames, thus reducing OAM performance. A reasonable OAM performance can be provided when the number of sub-overhead areas is two.

[0030] In one alternative approach 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 with the N service subframes. OAM performance can be improved by increasing the frequency of the transmitted target overhead fields.

[0031] A second aspect of this 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 can be an OTN device or an MTN device, etc. The data frame can 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 can be an OSU frame or other data frame with a similar OSU 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.

[0032] In an alternative approach of the second aspect, the overhead region of the service frame includes multiple different frame header indication overhead fields. The data demapping method further includes: the receiving device determining the start boundary of the service frame based on the multiple frame header indication overhead fields.

[0033] In an alternative approach of the second aspect, the overhead area of ​​the service frame includes a DM overhead field. The DM overhead field is 8 bits in size. 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.

[0034] It should be understood that the description of the second aspect is similar to that of the first aspect. Therefore, the description of the second aspect can be referenced to any of the alternative methods described in the aforementioned first aspect.

[0035] A third aspect of this application provides a data mapping method. The data mapping method includes the following steps: A transmitting device acquires multiple data encoded blocks. The transmitting device maps the multiple data encoded blocks to the 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 within the multiple sub-overhead areas and the sub-payload areas within the multiple sub-payload areas are alternately distributed. Each sub-overhead area includes a target overhead field. The size of the payload area of ​​the service frame is less than or equal to the size of the multiple sub-payload areas.

[0036] It should be understood that the description of the third aspect is similar to that of the first aspect. Therefore, the description of the third aspect may refer to the description of the first aspect or any alternative method within the first aspect.

[0037] A fourth aspect of this application provides a communication system. The communication system includes a transmitting device and a receiving device. The transmitting device is used to acquire multiple data encoded blocks and map the multiple data encoded blocks to the payload area of ​​a service frame. The size of the payload area of ​​the service frame is equal to the size of the multiple data encoded 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 encoded blocks from the payload area of ​​the service frame.

[0038] In an alternative embodiment of the fourth aspect, the transmitting device is further configured to perform the method described in the first aspect, the third aspect, or any alternative embodiment of the first aspect, and / or the receiving device is further configured to perform the method described in the second aspect or any alternative embodiment of the second aspect.

[0039] A fifth aspect of this application provides a service frame. The service frame includes an overhead area and a payload area. The payload area is used to carry multiple data encoded blocks. The size of the payload area of ​​the service frame is equal to the size of the multiple data encoded blocks.

[0040] In one alternative of the fifth aspect, the service frame also includes the content described in any of the alternatives of the first aspect.

[0041] A sixth aspect of this 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 as described in the fifth aspect or any alternative embodiment of the fifth aspect.

[0042] A seventh aspect of this application provides a transmitting device. The transmitting device includes an acquisition module, a mapping module, and a transmitting module. The acquisition module is used to acquire a plurality of data encoded blocks. The mapping module is used to perform the method described in the first aspect, the third aspect, or any one of the first aspects to obtain a data frame based on the plurality of data encoded blocks. The transmitting module transmits the data frame.

[0043] An eighth aspect of this application provides a receiving device. The receiving device includes a receiving module and an extraction module. The receiving module is used to receive data frames from a transmitting device. The extraction module is used to perform the method described in the second aspect or any one of the preceding aspects to obtain a plurality of data encoded blocks based on the data frames.

[0044] A ninth aspect of this application provides a transmitting apparatus. The transmitting apparatus includes a processor and a transceiver. The processor is configured to perform the methods described in the first aspect, the third aspect, or any alternative method thereof, to obtain a data frame. The transceiver is configured to transmit the data frame.

[0045] A tenth aspect of this application provides a receiving device. The receiving device includes a processor and a transceiver. The transceiver is used to receive data frames. The processor is used to perform the method described in the second aspect or any one of the preceding aspects to obtain a plurality of data encoded blocks based on the data frames.

[0046] The eleventh aspect of this application provides a computer storage medium. 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 embodiment of the first aspect; or cause the computer to perform the method described in the second aspect or any embodiment of the second aspect.

[0047] The twelfth aspect of this application provides a computer program product. When executed on a computer, the computer program product causes the computer to perform the method as described in the first aspect, the third aspect, or any embodiment of the first aspect; or causes the computer to perform the method as described in the second aspect or any embodiment of the second aspect. Attached Figure Description

[0048] Figure 1 This is a schematic diagram of the structure of an OTN.

[0049] Figure 2 This is a schematic diagram of the structure of an OTN device;

[0050] Figure 3 This is a schematic diagram of an OSU frame mapped to an OTN frame.

[0051] Figure 4 This is a first structural diagram of an OSU frame provided in an embodiment of this application;

[0052] Figure 5 This is a second structural diagram of an OSU frame provided in an embodiment of this application;

[0053] Figure 6 This is a first structural diagram of the overhead region of an OSU frame provided in an embodiment of this application;

[0054] Figure 7 A second structural schematic diagram of the overhead region of an OSU frame provided in an embodiment of this application;

[0055] Figure 8 This is a schematic diagram of the structure of the frame header indication overhead field provided in an embodiment of this application;

[0056] Figure 9 A third structural diagram of the overhead region of an OSU frame provided in an embodiment of this application;

[0057] Figure 10 This is a fourth structural diagram of the overhead region of an OSU frame provided in an embodiment of this application;

[0058] Figure 11 The fifth structural diagram of the overhead region of the OSU frame provided in the embodiments of this application;

[0059] Figure 12 The sixth structural diagram of the overhead region of the OSU frame provided in the embodiments of this application;

[0060] Figure 13 A third structural diagram of an OSU frame provided in an embodiment of this application;

[0061] Figure 14 This is a first structural schematic diagram of the first sub-overhead region provided in an embodiment of this application;

[0062] Figure 15 This is a first structural schematic diagram of the second sub-overhead region provided in an embodiment of this application;

[0063] Figure 16 This is a fourth structural diagram of an OSU frame provided in an embodiment of this application;

[0064] Figure 17 A second structural schematic diagram of the first sub-overhead region provided in an embodiment of this application;

[0065] Figure 18 This is a second structural schematic diagram of the second sub-overhead region provided in an embodiment of this application;

[0066] Figure 19 A flowchart illustrating the data mapping method provided in this application embodiment;

[0067] Figure 20 A flowchart illustrating the data demapping method provided in this application embodiment;

[0068] Figure 21 This is a schematic diagram of the structure of the transmitting device provided in an embodiment of this application;

[0069] Figure 22 This is a schematic diagram of the receiving device provided in an embodiment of this application;

[0070] Figure 23 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application;

[0071] Figure 24 This is a schematic diagram of the communication system provided in an embodiment of this application. Detailed Implementation

[0072] First, some of the terms used in this application will be explained to facilitate understanding by those skilled in the art.

[0073] 1) Multiple refers to two or more. "And / or" describes the relationship between related objects, which can exist in three ways. For example, A and / or B can represent: A alone, A and B simultaneously, or B 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 construed as indicating or implying relative importance or order.

[0074] 2) The mapping of A to B mentioned in this application refers to encapsulating A into B. For example, mapping an optical service unit (OSU) frame to an optical transport network (OTN) frame means encapsulating the OSU frame or OSU signal into an OTN frame.

[0075] 3) Unless otherwise specified, the specific description of certain technical features in one embodiment can also be used to explain the corresponding technical features mentioned in other embodiments. For example, the overhead and meaning of a service frame in one embodiment can also be applied to service frames mentioned in other embodiments. Similarly, specific examples and descriptions of optical transport frames can be applied to optical transport frames mentioned in different specific embodiments or to specific examples used to replace optical transport frames.

[0076] This application applies to optical networks such as optical transport networks or metropolitan area transport networks. Optical transport networks include OTN or Flexible Ethernet (FlexE). In the following description, OTN will be used as an example. An OTN typically consists of multiple OTN devices connected by optical fibers, and can be configured into different topologies such as linear, ring, and mesh, depending on specific needs. Figure 1 This is a schematic diagram of an OTN structure. (Example) Figure 1 As shown, OTN 100 consists of eight OTN devices 101, collectively known as OTN devices AH. 102 indicates an optical fiber used to connect two devices. 103 indicates a customer service interface used to receive or send customer service data. Figure 1 As shown, OTN 100 is used to transmit service data for customer equipment 1-3. The customer equipment connects to the OTN equipment through a customer service interface. For example, Figure 1 In the middle, customer equipment 1-3 are connected to OTN equipment A, H and F respectively.

[0077] Depending on the specific needs, an OTN device may possess different functions. Generally, OTN devices are categorized into optical layer devices, electrical layer devices, and hybrid optoelectronic devices. Optical layer devices refer to those capable of processing optical layer signals, such as optical amplifiers (OAs) and optical add-drop multiplexers (OADMs). OAs are primarily used to amplify optical signals to support longer transmission distances while maintaining specific optical signal performance. OADMs are used to spatially transform optical signals, allowing them to be output from different output ports (also known as directions). Electrical layer devices refer to those capable of processing electrical layer signals, such as devices capable of processing OTN signals. Hybrid optoelectronic devices refer to devices capable of processing both optical and electrical layer signals. It should be noted that, depending on specific integration requirements, an OTN device can integrate multiple different functions. The technical solutions provided in this application are applicable to OTN devices with different forms and integration levels that include electrical layer functions.

[0078] It should be noted that the data frame structure used by the optical transmission equipment in this application embodiment can be an OTN frame, used to carry various service data and provide rich management and monitoring functions. An OTN frame can be an optical data unit frame (ODUk), ODUcn, ODUflex, optical transport unit k (OTUk), OTUcn, or a flexible OTN (FlexO) frame, etc. The difference between an ODU frame and an OTU frame is that an OTU frame includes both the ODU frame and OTU overhead. k represents different rate levels. For example, k=1 represents 2.5Gbps, 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 also apply to this application. Furthermore, the method disclosed in this application can also be applied to other optical transport frames such as FlexE frames.

[0079] Figure 2 This is a structural diagram of an OTN device. The OTN device 200 can be... Figure 1 Any device in the OTN device AH. For example... Figure 2 As shown, the OTN device 200 includes a tributary board 201, a cross-connect board 202, a circuit board 203, an optical layer processing board (not shown in the figure), and a system control and communication board 204.

[0080] Tributary board 201, cross-connect board 202, and line board 203 are used to process electrical layer signals. Tributary board 201 is used to receive and transmit various customer services, such as SDH services, packet services, Ethernet services, and / or fronthaul services. Further, tributary board 201 can be divided into a customer-side optical transceiver module and a signal processor. The customer-side optical transceiver module, also called an optical transceiver, is used to receive and / or transmit service data. The signal processor is used to perform mapping and demapping processing of service data to data frames. Cross-connect board 202 is used to switch data frames, completing the exchange of one or more types of data frames. Line board 203 mainly implements the processing of line-side data frames. Specifically, line board 203 can be divided into a line-side optical module and a signal processor. The line-side optical module, also called an optical transceiver, is used to receive and / or transmit data frames. The signal processor is used to perform multiplexing and demultiplexing, or mapping and demapping processing of line-side data frames. System control and communication board 204 is used to implement system control; specifically, it can collect information from different boards or send control commands to the corresponding boards. Unless otherwise specified, 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, or on the functional design and number of the boards. It should also be noted that in a specific implementation, the two boards mentioned above may also be designed as a single board. In addition, network devices may also include backup power supplies, fans for heat dissipation, etc.

[0081] It should be understood that Figure 2 This is merely an example of an OTN device provided in this application. Depending on specific needs, the type and number of boards included in an OTN device may vary. For example, an OTN device acting as a core node may not have a tributary board 201. Alternatively, an OTN device acting as an edge node 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.

[0082] As described above, this application uses OTN as an example to describe the method provided in this application. 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 process of an OTN device mapping OSU frames to OTN frames is described below as an example.

[0083] Figure 3 This is a schematic diagram illustrating the mapping of an OSU frame to an OTN frame. For example... Figure 3As shown, OTN frame 302 has a 4-row, 3824-column structure. 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 also apply to this application. For example, OTN frames that do not include an FEC area. Or, frame structures with a different number of rows and columns than OTN frame 302.

[0084] One or more OSU frames are mapped to the payload area of ​​an OTN frame. For example... Figure 3 As shown, OSU frame 301 includes an overhead area and a payload area. The overhead area of ​​OSU frame 301 is used to carry overhead information. The overhead information includes one or more overhead fields. The payload area of ​​OSU frame 301 is used to carry service data. It should be understood that... Figure 3 The OSU frame structure shown is merely an example. In other specific implementations, the OSU frame can also be a data structure that includes overhead subframes. This application does not limit this.

[0085] In practical applications, the structure of the OSU frame is related to the performance of OTN's operation, administration, and maintenance (OAM). Therefore, designing an OSU frame that can improve OAM performance is an urgent problem to be solved.

[0086] Therefore, this application provides an OSU frame. Figure 4 This is a schematic diagram of the first structure of an OSU frame provided in an embodiment of this application. Figure 4 As shown, OSU frame 401 includes an overhead area and a payload area. The payload area includes a valid payload area and a padding payload area. The valid payload area is used to carry multiple data coded blocks. The size of the valid payload area is equal to the size of the multiple data coded blocks. The padding payload area is used to fill in unused data. In practical applications, to avoid transmitting too much unused data, the size of the padding payload area can be smaller than the size of a single data coded block.

[0087] In this embodiment, the position of the effective payload area within the OSU frame is fixed; that is, the size and position of the effective payload area and the padding payload area are fixed in two consecutive OSU frames transmitted by the OTN device. For example, two consecutive OSU frames include a first OSU frame and a second OSU frame. In both the first and second OSU frames, the effective payload area is 1056 bytes in size, and the padding payload area is 4 bytes in size. The effective payload area is located in bytes 33 to 1088 of the OSU frame. The padding payload area is located in bytes 1089 to 1092 of the OSU frame. When the position of the effective payload area within the OSU frame is fixed, the receiving device processing the OSU frame can determine the boundary of the data coding block by determining the start boundary of the OSU frame. Therefore, this embodiment can improve the efficiency of determining the boundary of the data coding block, thereby improving OAM performance.

[0088] In practical applications, the size of the effective payload area of ​​an 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 the padding payload area. Figure 5 This is a second structural diagram of an OSU frame provided in an embodiment of this application. Figure 5 As shown, OSU frame 501 includes an overhead area and a payload area. The payload area is used to fill multiple data coding blocks. These data coding blocks can be simply referred to as coding blocks. Figure 5 In the example, the number of data coded blocks is M. M is an integer greater than 1. In subsequent examples, the description will be based on the premise that the size of the OSU frame's payload area is equal to the size of the OSU frame's payload area.

[0089] According to the foregoing Figure 3 As described, one or more OSU frames can be frame-mapped to 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 16 bytes in size. Therefore, when the size of an OSU frame is an integer multiple of 16 bytes, the OSU frame occupies an integer number of time slots. In this case, the receiving device can improve the efficiency of determining the start boundary of the OSU frame, thereby improving OAM performance.

[0090] In practical applications, to facilitate the determination of the boundaries between the overhead and payload areas of an OSU frame, the size of the OSU frame overhead area 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 OSU frame payload area is also an integer multiple of 16 bytes, such as 4224 or 5280 bytes.

[0091] As described above, the size of the 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 its data coding blocks. The following description uses data coding block sizes of 66 and 257 bits as examples to illustrate the size of an OSU frame.

[0092] 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 frame period is approximately 3.27 ms. For alarm indication signals (AIS) or lock (LCK) signals that require filtering over 3 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, the OAM performance is relatively reasonable. Furthermore, as the OSU frame bit rate increases, the frame period of the OSU frame will further decrease, providing even better OAM performance. Alternatively, when the data block size is 66 bits, the OSU frame size is 4 × 1328 bytes. The payload area of ​​the OSU frame is 4 × 1320 bytes. The overhead area of ​​the OSU frame is 4 × 8 bytes. The payload area of ​​the OSU frame can carry 640 66-bit data blocks. When the bit rate of the OSU frame is 10.4 Mbit / s, the frame period of the OSU frame is approximately 4.09 ms. For AIS or LCK signals that need to be filtered through 3 frame periods, the transmission period is approximately 12.27 ms. Therefore, when the OSU frame size is 4 × 1328 bytes, the performance of OAM is relatively reasonable.

[0093] When the data block size is 257 bits, the service frame size is 4 × 1036 bytes. The service frame payload area is 4 × 1028 bytes. The service frame overhead area is 4 × 8 bytes. The OSU frame 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 AIS or LCK signals that require filtering over 3 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 payload area is 4 × 1258 bytes. The service frame overhead area is 4 × 8 bytes. The OSU frame payload area can carry 160 257-bit data blocks. When the bit rate of the OSU frame is 10.4 Mbit / s, the frame period of the OSU frame is approximately 3.98 ms. For signals such as AIS or LCK that need to be filtered through 3 frame periods, the transmission period is approximately 11.94 ms. Therefore, when the size of the OSU frame is 4 × 1293 bytes, the performance of OAM is relatively reasonable.

[0094] When the data block size is 257 bits or 66 bits, the service frame size is 34,560 bytes, for example, 4 × 1080 bytes. The payload size of the service frame is 34,304 bits, for example, 4 × 1072 bytes. The effective payload size of the service frame is 33,924 bits. The padding payload size of the service frame is 380 bits. The effective payload of an OSU frame can carry 514 66-bit data blocks. Alternatively, the effective payload of an OSU frame can carry 132 257-bit data blocks. It should be understood that in the aforementioned example, a 380-bit padding payload can also be used to carry one or more data blocks. For example, 380 bits can be used to carry one 257-bit block. In this case, the effective payload size of the service frame is 34,181 bits. The padding payload size of the service frame is 123 bits. The effective payload of an OSU frame can carry 133 257-bit data blocks. Alternatively, 380 bits can be used to carry five 66-bit coded blocks. In this case, the payload size of the service frame is 34,254 bits. The padding payload size of the service frame is 50 bits. The payload of an OSU frame can carry 519 66-bit data coded blocks.

[0095] In practical applications, receiving devices processing OSU frames can determine the start boundary of the OSU frame using the frame header indication overhead field. To improve the efficiency of determining the start boundary of the OSU frame, the overhead area of ​​the OSU frame may include multiple frame header indication overhead fields. Figure 6This is a first structural diagram of the overhead region of an OSU frame provided in an embodiment of this application. (See diagram below.) Figure 6 As shown, the overhead area 601 of the OSU frame has a 4-row, multi-column structure. The overhead area 601 includes two frame header indication overhead fields (i.e., frame header indication 1 and frame header indication 2). These two frame header indication overhead fields can be located in the middle area of ​​overhead area 601 or in the middle of each row. Both frame header indication overhead fields are 8 bits in size. Figure 6 In this document, blank areas are used to hold other expense fields. This application does not limit the specific content and size of these other expense fields. For example, other expense fields may include one or more expense fields from Table 1.

[0096] Table 1

[0097]

[0098] exist Figure 6 In the example, the frame header indication overhead field is located in the middle area of ​​overhead region 601. In practical applications, multiple frame header indication overhead fields can also be located at the beginning of overhead region 601. For example, the frame header indication 1 overhead field is located in the first byte of the first line, and the frame header indication 2 overhead field is located in the first byte of the second line. When the number of rows in the overhead region 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 start boundary of the OSU frame, the multiple frame header indication overhead fields can be spaced one row apart. For example, the frame header indication 1 overhead field is located in the first byte of the first line, and the frame header indication 2 overhead field is located in the first byte of the third line. Or, the frame header indication 1 overhead field is located in the first byte of the second line, and the frame header indication 2 overhead field is located in the first byte of the fourth line.

[0099] In practical applications, too many header overhead fields can also reduce transmission efficiency. To balance OAM performance and transmission efficiency, the number of header overhead fields can be equal to the number of rows in the OSU frame overhead area or a multiple of the number of rows in the OSU frame overhead area. Figure 7 This is a second structural diagram of the overhead region of an OSU frame provided in an embodiment of this application. (See diagram below.) Figure 7 As shown, the overhead area 701 of the OSU frame has a 4-row, multi-column structure. The overhead area 701 includes four frame header indication overhead fields (Frame Header Indicator 1, Frame Header Indicator 2, Frame Header Indicator 3, and Frame Header Indicator 4). These four frame header indication overhead fields are located in the middle area of ​​overhead area 701. Each frame header indication overhead field is 8 bits in size. Figure 7 In the blank area, other overhead fields are used to hold the blank areas.

[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 can include the same number of frame header indication overhead fields. For example, Figure 7 In the overhead area 701, each row includes one frame header indication overhead field. For 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 the overhead area 701 includes 2 frame header indication overhead fields.

[0101] according to Figures 6-7 As described above, the overhead area of ​​an OSU frame can include multiple header indicator overhead fields. To improve the efficiency of the receiving device in determining the start boundary of the OSU frame, these multiple header indicator overhead fields can be different. In practical applications, these multiple header indicator overhead fields can be completely different or partially different. These will be described separately below.

[0102] In the first approach, the multiple header indicator overhead fields are completely different. For example, the number of multiple header indicator overhead fields is 2. Both the header indicator 1 overhead field and the header indicator 2 overhead field consist of 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 identifier field and a first field. Figure 8 This is a schematic diagram illustrating the structure of the frame header indication overhead field provided in an embodiment of this application. For example... Figure 8 As shown, the frame header indication overhead field 801 includes a frame header indication identifier field and a first field. The receiving device determines the position of the frame header indication overhead field 801 through the frame header indication identifier field. For example, the frame header indication identifier field includes 7 bits. The value of the 7 bits is 1111111. The first field is used to characterize the order of each frame header indication overhead field among multiple frame header indication overhead fields. For example, the first field includes 1 bit. The value of the 1 bit in 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 multiple frame header indication overhead fields. The value of the 1 bit in 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 multiple frame header indication overhead fields.

[0104] In practical applications, the overhead area of ​​an OSU frame may include a JC overhead field to carry mapping overhead information. In this embodiment, to reduce the size of the overhead 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 This is a third structural diagram of the overhead region of an OSU frame provided in an embodiment of this application. (See diagram below.) Figure 9 As shown, the overhead area 901 of the OSU frame has a 4-row, multi-column structure. The overhead area 901 of the OSU frame includes two JC overhead fields (JC1 and JC2). The JC1 overhead field is located in the first row. The JC2 overhead field is located in the second row. Each JC overhead field is 1 byte in size. Figure 9 In this context, the JC overhead field is 2 bytes in size.

[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 transmit only the incremental change of its Cm value (Cm represents the amount of service data carried in each frame in m-bit units) through the JC overhead field. Another example is when 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 ​​an OSU frame may include a DM overhead field to carry delay information. To improve the accuracy of delay measurement, the size of the DM overhead field can be greater than or equal to 10 bits. For example, the size of the DM overhead field can be 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 This is a fourth structural diagram of the overhead region of an OSU frame provided in an embodiment of this application. Figure 10 As shown, 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 1 byte in size), 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 the speed of fault handling, the overhead area of ​​the OSU frame can include both the PM APS overhead field and the TCM APS overhead field. Figure 11 This is the fifth structural diagram of the overhead region of the OSU frame provided in an embodiment of this application. Figure 11As shown, the overhead area 1101 of the OSU frame has a 4-row, multi-column structure. The overhead area 1101 of the OSU frame includes a PM APS overhead field and a TCM APS overhead field. The TCM APS overhead field can be either a TCM1 APS overhead field or a TCM2 APS overhead field. To further improve the speed of fault handling, each OSU frame transmitted by the transmitting device can include both a PM APS overhead field and a TCM APS overhead field.

[0108] Figure 12 This is the sixth structural diagram of the overhead region of the OSU frame provided in an embodiment of this application. Figure 12 As shown, the overhead area 1201 of the OSU frame has a 4x8 column structure. Overhead area 1201 is 4×8 bytes in size. Overhead area 1201 includes four frame header indicator overhead fields. These four fields are located in the first and second columns. Each frame header indicator overhead field includes a frame header indicator identifier field and a first field. The frame header indicator identifier field can also be called the 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). These three fields are located in the eighth column. Each JC field is 1 byte in size. Overhead area 1201 also includes two DM overhead fields (TCM DM and PM DM). These two fields are located in the sixth column. Each DM field is 1 byte in size. Overhead area 1201 also includes PM APS and TCM APS fields. These fields are located in the seventh column. Each APS field is 1 byte in size. exist Figure 12 In this context, BEI / BIAE represents the BEI cost field or the BIAE cost field. For detailed descriptions of other fields, please refer to [link to relevant documentation]. Figure 12 As shown in Table 1, it will not be repeated here.

[0109] Figure 13 This is a third structural diagram of an OSU frame provided in an embodiment of this application. Figure 13 As shown, the overhead area of ​​OSU frame 1301 includes multiple sub-overhead areas (referred to as the first sub-overhead area and the second sub-overhead area, respectively). The payload area of ​​OSU frame 1301 also includes multiple sub-payload areas (referred to as the first sub-payload area and the second sub-payload area, respectively). The sub-overhead areas within the multiple sub-overhead areas and the sub-payload areas within the multiple sub-payload areas are distributed alternately. Each sub-overhead area within the multiple sub-overhead areas includes a target overhead field.

[0110] The target cost field may include a frame header indication cost field and / or a cumulative delay cost field. The cumulative delay cost field may also be called the ADV cost field. For a description of the ADV cost field, please refer to Table 1 above. When the target cost field includes a frame header indication cost field, each of the multiple sub-cost areas includes a frame header indication cost field. When the target cost field includes a cumulative delay cost field, each of the multiple sub-cost areas includes a cumulative delay cost field. When the target cost field includes both a frame header indication cost field and a cumulative delay cost field, each of the multiple sub-cost areas includes both a frame header indication cost field and a cumulative delay cost field. The following description uses the example of a target cost field including a frame header indication cost field.

[0111] Figure 14 This is a first structural schematic diagram of the first sub-overhead region provided in an embodiment of this application. (See attached diagram.) Figure 14 As shown, the first sub-overhead area 1401 includes a Frame Header Indicator 1 overhead field and an ADV overhead field. The Frame Header Indicator 1 overhead field is 2 bytes in size. The ADV overhead field is 4 bytes in size. Figure 14 In this document, blank areas are used to hold other expense fields. This application does not limit the specific content and size of these other expense fields. For example, other expense fields may include one or more expense fields from Table 1. Figure 15 This is a first structural schematic diagram of the second sub-overhead region provided in an embodiment of this application. (See attached diagram.) Figure 15 As shown, the second sub-overhead area 1501 includes a Frame Header Indicator 2 overhead field. The Frame Header Indicator 2 overhead field is 2 bytes in size. Figure 15 In the header, blank areas are used to carry other overhead fields. It should be understood that the contents of the Frame Header Indicator 2 overhead field and the Frame Header Indicator 1 overhead field can be completely different or partially different.

[0112] In practical applications, to reduce the complexity of receiving devices processing OSU frames, the size of each sub-overhead area in multiple sub-overhead 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 in multiple sub-overhead areas can be an integer multiple of 8 or 16 bytes. For example, in Figure 13 In this context, the size of the first sub-payload area is 1888 bytes.

[0113] To improve the efficiency of data transmission in service frames, a service frame can be composed of N service subframes to form a multiframe. N is an integer greater than 1. The following description will use N equal to 4 as an example. Figure 16 This is a fourth structural diagram of an OSU frame provided in an embodiment of this application. Figure 16As shown, OSU frame 1601 is a multiframe composed of four service subframes. These four service subframes are designated as service subframes 1 through 4. Service subframe 1 includes sub-overhead area 1, sub-payload area 1, sub-overhead area 2, and sub-payload area 2. For descriptions of the 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. The first sub-overhead area includes sub-overhead area 1, sub-overhead area 3, sub-overhead area 5, and sub-overhead area 7. For descriptions of the 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 transmission target overhead fields, each sub-overhead area of ​​a multiframe can include N target overhead fields. These N target overhead fields correspond one-to-one with the N service subframes; that is, each service subframe includes one target overhead field in each sub-overhead area.

[0115] In practical applications, to reduce the complexity of processing multiframes by the receiving device, the size of a multiframe can be 4 × 3824 bytes. Each service subframe is 3824 bytes in size. At this point, in... Figure 16 In the OSU frame 1601, there are 4 rows and 3824 columns. The first sub-overhead area can be located in columns 1 to 16. The size of the first sub-overhead area is 4 × 16 bytes. The first sub-payload area can be located in columns 17 to 1904. The size of the first sub-payload area is 4 × 1888 bytes. The second sub-overhead area can be located in columns 1905 to 1920. The size of the second sub-overhead area is 4 × 16 bytes. The second sub-payload area can be located in columns 1921 to 3824. The size of the second sub-payload area is 4 × 1904 bytes. The first and second sub-overhead areas, each 4 × 16 bytes in size, are described below.

[0116] Figure 17 This is a second structural schematic diagram of the first sub-overhead region provided in an embodiment of this application. (See attached diagram.) Figure 17 As shown, the size of the first sub-overhead area 1701 is 4 × 16 bytes. The first sub-overhead area 1701 consists of four rows, each 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 Indicator 1 overhead field, MFAS overhead field, TCM2 overhead field, TCM1 overhead field, PM overhead field, and ADV overhead field. Each overhead field is described below.

[0117] The size of the Frame Header Indicator 1 (FTI) overhead field is 2 bytes. The FTI overhead field may include the Frame Header Indicator I identifier field. The value of the FTI overhead field can be 0xF628.

[0118] The MFAS overhead field is 1 byte in size. The MFAS overhead field increments with each service subframe, 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 may include 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 may include 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 in size. The ADV overhead field can use the frame header indicator 1 overhead field as a reference point. The ADV overhead field is used by the receiving device to restore the service clock.

[0123] Figure 18 This is a second structural schematic diagram of the second sub-overhead region provided in an embodiment of this application. (See attached diagram.) Figure 18 As shown, the second sub-overhead area 1801 is 4 × 16 bytes in size. The second sub-overhead area 1801 consists of four rows, each corresponding to the sub-overhead area of ​​one service subframe. The sub-overhead area of ​​each service subframe is 16 bytes in size. Each service subframe's sub-overhead area includes the Frame Header Indicator 2 overhead field, TCM DM overhead field, PM DM overhead field, TCM APS overhead field, PM APS overhead field, RES overhead field, PT overhead field, ADV overhead field, and POH overhead field. Each overhead field is described below.

[0124] The Frame Header Indicator 2 (FTI) overhead field is 2 bytes in size. The FTI can differ from the FTI indicator 1 (FTI). For example, the FTI value can be the inverted value of 0xF628. These different values ​​of the FTI and FTI are used to indicate their order within each service subframe.

[0125] The overhead fields TCM DM, PM DM, TCM APS, and PM APS 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 indicator 2 overhead field as a reference point. The POH overhead field is 2 bytes in size. It should be understood that regarding Figure 17 and Figure 18 For a description of each expense field, please refer to the description in Table 1 above.

[0126] It should be understood that Figure 13 and Figure 16 These are merely two examples of OSU frames provided in this application. In practical applications, those skilled in the art can adapt the structure of the OSU frame to their needs. For example, an OSU frame may include three sub-overhead areas and two sub-payload areas. It should be understood that... Figures 13-18 The OSU frames described in the document and Figures 4-12 The OSU frames described in [the text] have similarities. Therefore, regarding [the text]... Figures 13-18 For a description of the OSU frame, please refer to [link / reference]. Figures 4-12 The description of OSU frames. For example, in Figure 13 In this context, multiple sub-payload areas include a valid payload area. The size of the valid payload area is less than or equal to the size of the multiple sub-payload areas. The valid payload area is used to carry multiple coded blocks. The size of the multiple coded blocks is equal to the size of the valid payload area. Similarly, multiple sub-payload areas also include a padding payload area. The padding payload area is used to fill in unused data. The sum of the sizes of the padding payload area and the valid payload area equals the size of the multiple sub-payload areas.

[0127] The OSU frames provided in the embodiments of this application have been described above. The data mapping method and data demapping method provided in the embodiments of this application are described below. Figure 19 This is a flowchart illustrating the data mapping method provided in an embodiment of this application. Figure 19 As shown, the data mapping method includes the following steps.

[0128] In 1901, the transmitting device acquires multiple data encoded blocks.

[0129] The transmitting device can be an OTN device or an MTN device, etc. The transmitting device generates multiple data encoded blocks, or receives multiple data encoded blocks from other devices. The embodiments of this application do not limit the size of each data encoded block. For example, the size of each data encoded block can be 66 bits or 257 bits.

[0130] In 1902, the transmitting device maps multiple data coded blocks into the payload area of ​​the service frame. The size of the payload area of ​​the service frame is equal to the size of the multiple data coded blocks.

[0131] A service frame can be an OSU frame or other data frame with a similar OSU frame structure. The size of the service frame's effective payload area can be less than or equal to the service frame's payload area size. When the effective payload area size is less than the service frame's payload area size, the service frame's payload area also includes a padding payload area. The padding payload area is used to fill in unused data. The size of the service frame's effective payload area is equal to the size of multiple data coding blocks. It should be understood that for a description of service frames, please refer to... Figures 4-18 Description of any figure.

[0132] In 1903, the transmitting device maps service frames to the payload area of ​​data frames.

[0133] Data frames can be OTN frames, FlexE frames, or MTN frames, etc. When the data frame is an OTN frame, it can have a 4x3824 column structure. Data frames may also include an overhead area. For example, the overhead area of ​​a data frame is 4 × 16 bytes. The payload area of ​​a data frame is 4 × 3808 bytes. For more details on step 1903, please refer to [link to relevant documentation]. Figure 3 .

[0134] In 1904, the transmitting device sends data frames.

[0135] The transmitting device sends data frames to the receiving device. The receiving device can be another OTN or MTN device. The transmitting and receiving devices are connected via optical fiber. After receiving the data frames, the transmitting device modulates them onto an optical carrier to obtain an optical signal. The transmitting device then transmits the optical signal to the receiving device via the optical fiber.

[0136] Figure 20 This is a flowchart illustrating the data demapping method provided in an embodiment of this application. Figure 20 As shown, the data demapping method includes the following steps.

[0137] In step 2001, the receiving device receives a data frame from the sending device.

[0138] The receiving device can be either an OTN or MTN device. The receiving and transmitting devices are connected via 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 the service frame from the 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 × 16 bytes in size. The payload area of ​​a data frame is 4 × 3808 bytes in size. The payload area of ​​a data frame includes one or more service frames. Service frames can be OSU frames or other data frames with similar OSU frame structures.

[0141] In step 2003, the receiving device extracts multiple data coding 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 coding blocks.

[0142] The effective payload area of ​​a 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. This application embodiment does not limit the size of each data coding block; 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 service frame's payload area. When the size of the effective payload area of ​​the service frame is less than the size of the service frame's payload area, the service frame's payload area also includes a padding payload area. The padding payload area is used to fill in unused 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, for the description of the data demapping method, please refer to... Figures 4-18 Any of these descriptions. For example, the overhead region of a service frame includes multiple different header indicator overhead fields. The receiving device determines the start boundary of the service frame based on these header indicator overhead fields. As another example, the overhead region of a service frame includes a DM overhead field. The DM overhead field is 8 bits in size. The receiving device determines the delay between the receiving device and the transmitting device based on the DM overhead field.

[0144] Figure 21 This is a schematic diagram of the structure of the transmitting device provided in an embodiment of this application. Figure 21 As shown, the transmitting device 2100 includes an acquisition module 2101, a mapping module 2102, and a transmitting module 2103. The acquisition module 2101 acquires multiple data encoded blocks. The mapping module 2102 maps the multiple data encoded blocks to the payload area of ​​a data frame. The transmitting module 2103 transmits the data frame. The size of the multiple data encoded blocks is equal to the size of the payload area of ​​the data frame.

[0145] It should be understood that the description of the transmitting device 2100 is similar to the aforementioned description of the data mapping method and service frames. Therefore, the description of the service frames in the transmitting device 2100 can be found by referring to... Figures 4-18 A description of any one of them. For a description of the steps performed by each module in the transmitting device 2100, please refer to... Figure 19 The description is as follows. For example, each data encoding block in multiple data encoding blocks is 66 bits in size. Another example is that the overhead area of ​​a service frame includes multiple different frame header indication overhead fields.

[0146] Figure 22 This is a schematic diagram of the receiving device provided in an embodiment of this application. Figure 22 As shown, the receiving device 2200 includes a receiving module 2201 and an extraction module 2202. The receiving module 2201 is used to receive data frames from the transmitting device. The extraction module 2202 is used to extract service frames from the payload area of ​​the data frames. The extraction module 2202 can also be used to extract multiple data encoding blocks from the effective payload area of ​​the data frames. The size of the multiple data encoding 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 aforementioned data demapping method and service frame description. Therefore, the description of the service frame in the receiving device 2200 can be found by referring to... Figures 4-18 A description of any one of them. For a description of the steps performed by each module in the receiving device 2200, please refer to... Figure 20 The description is as follows. 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 also used to determine the start boundary of the service frame based on the multiple frame header indication overhead fields. For 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 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. The communication device can be a transmitting device or a receiving device. Figure 23As shown, the communication device 2300 includes a processor 2301 and a transceiver 2302. The processor 2301 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP. The processor 2301 may further include a hardware chip or other general-purpose processor. The aforementioned hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The transceiver 2302 may be an optical transceiver.

[0149] When the communication device 2300 is a transmitting device, the processor 2301 is used to acquire multiple data encoded blocks. The processor 2301 is also used to map the multiple data encoded blocks to the payload area of ​​the data frame. The size of the multiple data encoded blocks is equal to the size of the payload area of ​​the data frame. The transceiver 2302 is used to transmit the data frame.

[0150] When the communication device 2300 is a receiving device, the transceiver 2302 is used to receive data frames from the transmitting device. The processor 2301 is used to extract service frames from the payload area of ​​the data frame. The processor 2301 can also be used 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 volatile memory or non-volatile memory, or may include both. The non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), or flash memory, etc. The volatile memory may be random access memory (RAM). The memory 2303 may be used to store data frames or service frames, or other code used for controlling and managing the device.

[0152] For a description of service frames in communication equipment 2300, please refer to... Figures 4 to 18 The description of any service frame. When the communication device 2300 is a transmitting device, the description of the steps performed by the communication device 2300 can also be found in [reference needed]. Figure 19 or Figure 21The description of the transmitting device is provided below. When the communication device 2300 is a receiving device, the description of the steps performed by the communication device 2300 can also be found in [reference needed]. Figure 20 or Figure 22 The description of the receiving device.

[0153] This application also provides a communication system. Figure 24 This is a schematic diagram of the communication system provided in an embodiment of this application. Figure 24 As shown, the communication system 2400 includes a transmitting device 2401 and a receiving device 2402. The transmitting device 2401 is used to acquire multiple data encoded blocks and map these blocks to the payload area of ​​a data frame. The size of the multiple data encoded blocks is equal to the size of the payload area of ​​the data frame. The transmitting device 2401 is also used to transmit data frames. The receiving device 2402 is used to receive data frames from the transmitting device and extract service frames from the payload area of ​​the data frames. The receiving device 2402 can also be used to extract multiple data encoded blocks from the payload area of ​​the data frames.

[0154] For a description of service frames in the 2400 communication system, please refer to... Figures 4-18 A description of any service frame. For a description of the steps performed by the transmitting device 2401, please refer to... Figure 19 The description of the data mapping method is provided in [the document]. For a description of the steps performed by the receiving device 2402, please refer to [the document / reference]. Figure 20 The description of data demapping methods in the document.

[0155] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application.

Claims

1. A business data mapping method, characterized in that, include: Sending device acquires service data; The transmitting device carries the service data in the payload area of ​​the service frame. The service frame includes an overhead area and the payload area. The overhead area of ​​the service frame includes multiple frame header indication overhead fields. Each of the multiple frame header indication overhead fields includes a first field, which is used to characterize the order of each frame header indication overhead field in the multiple frame header indication overhead fields. The transmitting device maps the service frame to the payload area of ​​the data frame; The transmitting device sends the data frame.

2. The method according to claim 1, characterized in that, The number of overhead fields indicated by the multiple frame headers is a multiple of the number of rows in the overhead area of ​​the service frame.

3. The method according to claim 2, characterized in that, The number of the multiple frame header indication fields is 8.

4. The method according to any one of claims 1-3, characterized in that, The overhead area of ​​the service frame includes multiple sub-overhead areas, and the payload area 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 distributed alternately.

5. The method according to claim 4, characterized in that, The multiple frame header indication overhead fields are distributed in the multiple sub-overhead areas.

6. The method according to claim 4, characterized in that, The service frame comprises 4 rows and 3824 columns. The multiple sub-overhead areas are located in columns 1 to 16 and columns 1905 to 1920, respectively. The multiple sub-payload areas are located in columns 17 to 1904 and columns 1921 to 3824, respectively.

7. The method according to any one of claims 1-6, characterized in that, The overhead area of ​​the service frame also includes a delay measurement (DM) overhead field, which includes multiple 1-byte fields.

8. The method according to any one of claims 1-7, characterized in that, The overhead area of ​​the service frame also includes the Channel Monitoring Automatic Protection Switching (PM APS) overhead field and the Serial Connection Monitoring (TCM APS) overhead field, with the PM APS overhead field and the TCM APS overhead field occupying different fields.

9. The method according to any one of claims 1-8, characterized in that, The overhead area of ​​the service frame also includes a Status Indicator (STAT) overhead field and / or a Backward Defect Indicator (BDI) overhead field, and each line of the service frame includes the STAT overhead field and / or the BDI overhead field.

10. The method according to any one of claims 1-9, characterized in that, The overhead area of ​​the service frame also includes a payload type (PT) overhead field and a customer signal failure indication (CSF) overhead field, with the PT overhead field and the CSF overhead field occupying different fields.

11. The method according to any one of claims 1-10, characterized in that, The size of the service frame is an integer multiple of 16 bytes.

12. The method according to any one of claims 1-11, characterized in that, The size of the 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.

13. The method according to any one of claims 1-12, characterized in that, The business data includes multiple 66-bit or 257-bit data encoding blocks.

14. A business data demapping method, characterized in that, include: The receiving device receives data frames; The receiving device extracts a service frame from the payload area of ​​the data frame. The service frame includes an overhead area and the payload area. The overhead area of ​​the service frame includes multiple frame header indication overhead fields. Each of the multiple frame header indication overhead fields includes a first field, which is used to characterize the order of each frame header indication overhead field in the multiple frame header indication overhead fields. The receiving device extracts service data from the payload area of ​​the service frame.

15. The method according to claim 14, characterized in that, The number of overhead fields indicated by the multiple frame headers is a multiple of the number of rows in the overhead area of ​​the service frame.

16. The method according to claim 15, characterized in that, The number of the multiple frame header indication fields is 8.

17. The method according to any one of claims 14-16, characterized in that, The overhead area of ​​the service frame includes multiple sub-overhead areas, and the payload area 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 distributed alternately.

18. The method according to claim 17, characterized in that, The multiple frame header indication overhead fields are distributed in the multiple sub-overhead areas.

19. The method according to claim 17, characterized in that, The service frame comprises 4 rows and 3824 columns. The multiple sub-overhead areas are located in columns 1 to 16 and columns 1905 to 1920, respectively. The multiple sub-payload areas are located in columns 17 to 1904 and columns 1921 to 3824, respectively.

20. The method according to any one of claims 14-19, characterized in that, The overhead area of ​​the service frame also includes a delay measurement (DM) overhead field, which includes multiple 1-byte fields.

21. The method according to any one of claims 14-20, characterized in that, The overhead area of ​​the service frame also includes the Channel Monitoring Automatic Protection Switching (PM APS) overhead field and the Serial Connection Monitoring (TCM APS) overhead field, with the PMAPS overhead field and the TCM APS overhead field occupying different fields.

22. The method according to any one of claims 14-21, characterized in that, The overhead area of ​​the service frame also includes a Status Indicator (STAT) overhead field and / or a Backward Defect Indicator (BDI) overhead field, and each line of the service frame includes the STAT overhead field and / or the BDI overhead field.

23. The method according to any one of claims 14-22, characterized in that, The overhead area of ​​the service frame also includes a payload type (PT) overhead field and a customer signal failure indication (CSF) overhead field, with the PT overhead field and the CSF overhead field occupying different fields.

24. A transmitting device, characterized in that, It includes an acquisition module, a mapping module, and a sending module, among which: The acquisition module is used to acquire business data; The mapping module is used to carry the service data in the payload area of ​​the service frame. The service frame includes an overhead area and the payload area. The overhead area of ​​the service frame includes multiple frame header indication overhead fields. Each of the multiple frame header indication overhead fields includes a first field, which is used to characterize the order of each frame header indication overhead field in the multiple frame header indication overhead fields. The mapping module is also used to map the service frame to the payload area of ​​the data frame; The sending module is used to send the data frame.

25. The transmitting device according to claim 24, characterized in that, The number of overhead fields indicated by the multiple frame headers is a multiple of the number of rows in the overhead area of ​​the service frame.

26. The transmitting device according to claim 25, characterized in that, The number of the multiple frame header indication fields is 8.

27. The transmitting device according to any one of claims 24-26, characterized in that, The overhead area of ​​the service frame includes multiple sub-overhead areas, and the payload area 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 distributed alternately.

28. The transmitting device according to claim 27, characterized in that, The multiple frame header indication overhead fields are distributed in the multiple sub-overhead areas.

29. A receiving device, characterized in that, It includes a receiving module and an extracting module, wherein: The receiving module is used to receive data frames; The extraction module is used to extract service frames from the payload area of ​​the data frame. The service frame includes an overhead area and the payload area. The overhead area of ​​the service frame includes multiple frame header indication overhead fields. Each of the multiple frame header indication overhead fields includes a first field, which is used to characterize the order of each frame header indication overhead field in the multiple frame header indication overhead fields. The extraction module is also used to extract service data from the payload area of ​​the service frame.

30. The receiving device according to claim 29, characterized in that, The number of overhead fields indicated by the multiple frame headers is a multiple of the number of rows in the overhead area of ​​the service frame.

31. The receiving device according to claim 30, characterized in that, The number of the multiple frame header indication fields is 8.

32. The receiving device according to any one of claims 29-31, characterized in that, The overhead area of ​​the service frame includes multiple sub-overhead areas, and the payload area 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 distributed alternately.

33. The receiving device according to claim 32, characterized in that, The multiple frame header indication overhead fields are distributed in the multiple sub-overhead areas.

Images