Method and apparatus for service processing in optical transport network, device, and storage medium

Abstract

A method and apparatus for service processing in an optical transport network (OTN), a device, and a storage medium. The method comprises: acquiring service data (S1301); mapping the service data onto a basic frame (S1302); mapping the basic frame onto some time slots in an OTN frame bearing area (S1303); and sending an OTN frame (S1304).

Description

Service processing method, device, equipment and storage medium in optical transport network

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on June 29, 2023, with application number 202310793874.6. The entire contents of the above application are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of optical communication technology, for example, to a service processing method, apparatus, device and storage medium in an optical transport network. Background Art

[0003] The Optical Transport Network (OTN), a core technology for backbone transport networks, includes optical bearer containers with various rates. For example, Optical Data Unit 0 (ODU0), the lowest-rate bearer container in current OTN technology, operates at approximately 1.25 Gigabits per second (Gbps) and is used to carry 1 Gbps of customer service data.

[0004] For low-rate services below 1.25 Gbps, current OTN bearer containers cannot provide an effective carrying solution. Therefore, how to use traditional OTN frames to carry service data at rates below 1.25 Gbps has become a technical problem that those skilled in the art urgently need to solve.

[0005] Summary of the Invention

[0006] Embodiments of the present application provide a service processing method, apparatus, device, and storage medium in an optical transport network.

[0007] In a first aspect, an embodiment of the present application provides a service processing method in an optical transport network (OTN), including:

[0008] Obtain business data;

[0009] Mapping the service data into a basic frame; wherein the size of the basic frame is 4 lines, each line is 3824 bytes;

[0010] Mapping the basic frame to a portion of time slots in the OTN frame bearing area;

[0011] The OTN frame is sent.

[0012] In a second aspect, an embodiment of the present application provides a service processing method in an optical transport network, including:

[0013] Receive the OTN frame; wherein, a basic frame is carried in some time slots within the OTN frame carrying area, and the size of the basic frame is 4 lines, each line is 3824 bytes;

[0014] Extracting the basic frame from a corresponding time slot of the OTN frame;

[0015] Acquire service data from the basic frame.

[0016] In a third aspect, an embodiment of the present application provides a service processing device in an optical transport network, including:

[0017] Acquisition module, set to obtain business data;

[0018] A processing module configured to map the service data into a basic frame; wherein the size of the basic frame is 4 lines, each line 3824 bytes;

[0019] The processing module is further configured to map the basic frame to a portion of time slots in the OTN frame bearing area;

[0020] The sending module is configured to send the OTN frame.

[0021] In a fourth aspect, an embodiment of the present application provides a service processing device in an optical transport network, including:

[0022] A receiving module configured to receive the OTN frame; wherein a basic frame is carried in some time slots within the OTN frame carrying area, and the size of the basic frame is 4 lines, each line being 3824 bytes;

[0023] A processing module, configured to extract the basic frame from a corresponding time slot of the OTN frame;

[0024] The processing module is further configured to obtain service data from the basic frame.

[0025] In a fifth aspect, an embodiment of the present application provides an optical transport network device, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the service processing method in the optical transport network provided in the first and second aspects of the embodiments of the present application are implemented.

[0026] In a sixth aspect, an embodiment of the present application provides a storage medium, which stores a computer program. When the computer program is executed by a processor, it implements the steps of the service processing method in the optical transport network provided in the first and second aspects of the embodiments of the present application.

[0027] The technical solution provided in the embodiment of the present application defines a new basic frame structure to carry customer service data, and uses part of the time slots in the traditional OTN frame carrying area to carry the basic frame, thereby achieving the purpose of transmitting low-rate service data through traditional OTN frames. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] FIG1 is a schematic diagram of the structure of an OTN frame provided in an embodiment of the present application;

[0029] FIG2 is another schematic diagram of the structure of an OTN frame provided in an embodiment of the present application;

[0030] FIG3 is a schematic diagram of a structure of a basic frame provided in an embodiment of the present application;

[0031] FIG4 is another structural diagram of a basic frame provided in an embodiment of the present application;

[0032] FIG5 is a schematic diagram of a structure of a subframe provided in an embodiment of the present application;

[0033] FIG6 is another structural diagram of a basic frame provided in an embodiment of the present application;

[0034] FIG7 is a schematic structural diagram of an overhead area of ​​a basic frame or subframe provided in an embodiment of the present application;

[0035] FIG8 is a schematic diagram of a structure of frame header flag information of a basic frame or subframe provided in an embodiment of the present application;

[0036] FIG9 is another schematic diagram of the structure of a subframe provided in an embodiment of the present application;

[0037] FIG10 is a schematic diagram of another structure of a subframe provided in an embodiment of the present application;

[0038] FIG11 is another structural diagram of a basic frame provided in an embodiment of the present application;

[0039] FIG12 is another structural diagram of a basic frame provided in an embodiment of the present application;

[0040] FIG13 is a flow chart of a service processing method for an optical transport network provided in an embodiment of the present application;

[0041] FIG14 is a schematic diagram of a structure of a code block after 64 / 66 encoding provided in an embodiment of the present application;

[0042] FIG15 is a schematic diagram of the 64 / 66-bit code block encoding principle provided in an embodiment of the present application;

[0043] FIG16 is a schematic diagram of the structure of a data code block and a control code block after 64 / 66 encoding according to an embodiment of the present application;

[0044] FIG17 is a schematic diagram of a structure of a code block stream obtained after 64 / 66 encoding of service data provided in an embodiment of the present application;

[0045] FIG18 is a structural diagram of a process for separating synchronization headers and code block bytes in a 66-bit code block provided by an embodiment of the present application;

[0046] FIG19 is a schematic structural diagram of a payload area of ​​a subframe or basic frame provided in an embodiment of the present application;

[0047] FIG20 is another flow chart of a service processing method for an optical transport network provided in an embodiment of the present application;

[0048] FIG21 is a schematic diagram of a subframe or basic frame framing process provided in an embodiment of the present application;

[0049] FIG22 is another schematic diagram of a subframe or basic frame framing process according to an embodiment of the present application;

[0050] FIG23 is another schematic diagram of a subframe or basic frame framing process according to an embodiment of the present application;

[0051] FIG24 is another schematic diagram of a subframe or basic frame framing process according to an embodiment of the present application;

[0052] FIG25 is a schematic structural diagram of a service processing device for an optical transport network provided in an embodiment of the present application;

[0053] FIG26 is another structural diagram of a service processing device for an optical transport network provided in an embodiment of the present application;

[0054] FIG27 is a schematic diagram of the structure of an optical transmission network device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0055] It should be understood that the embodiments described herein are only used to explain the present application and are not intended to limit the present application. The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0056] The embodiments of the present application are applicable to OTN devices of any form and integration level. The data frame structure used by the OTN device is an OTN frame, which is used to carry various service data and provide rich management and monitoring functions. The OTN frame can be an ODUk, ODUCn, ODUflex, or an Optical Transport Unit k (OTUk), OTUCn, or a flexible OTN (Flex0) frame. The difference between an ODU frame and an OTU frame is that an OTU frame includes an ODU frame and an OTU overhead; k represents the rate level passed, for example, k=1 represents 2.5Gbps, k=4 represents 100Gbps; Cn represents a variable rate, for example, a rate that is a positive integer multiple of 100Gbps. Unless otherwise specified, an ODU frame refers to any of ODUk, ODUCn, or ODUflex, and an OTU frame refers to any of OTUk, OTUCn, or Flex0. It should also be noted that as OTN technology develops, new types of OTN frames may be defined, which are also applicable to this application. Figure 1 shows the structure of an OTN frame, which consists of 4*3824 bytes (i.e., 4 rows and 3824 columns). In Figure 1, the Optical Path Unit (OPU) overhead field is located in columns 15 and 16 of the OTN frame; the ODU (ODU) overhead field is located in the ODU overhead field; the OTU (OTU) overhead field is located in the OTU overhead field; and alignm is the OTN frame header alignment marker. This means that each row of the OTN frame overhead occupies 16 bytes. Customer service data is loaded and transmitted in the OPU, which is the bearer area of ​​the OTN frame. The OTN frame bearer area is located in columns 17-3824 of the frame.

[0057] Figure 2 shows another OTN frame structure. The bearer area of ​​an OTN frame is divided into time slots, each of which is 16 bytes. Each row in the bearer area of ​​an OTN frame contains 3824-16 = 3808 bytes, resulting in 238 time slots. A four-row bearer area can be divided into 952 time slots. Each time slot is 16 bytes long, and the service speed associated with each time slot is 10 Mbps (actually slightly higher than 10 Mbps, after deducting various overheads to ensure that customer service speeds reach 10 Mbps).

[0058] For low-rate services below 1.25 Gbps, current OTN bearer containers cannot provide an effective transport solution. Therefore, this application defines a new frame structure, which, for simplicity, will be referred to as the basic frame. It should be noted that this name is merely an example and should not limit the frame structure defined in this application. This name can also be replaced with other names such as low-rate frame or low-rate service frame.

[0059] As shown in Figure 3, the basic frame is sized at 4 rows, each row containing 3824 bytes. In an alternative embodiment, each row of the basic frame includes two overhead areas for carrying overhead information and two payload areas for carrying customer service data. The overhead and payload areas are adjacent to each other. In other words, a basic frame includes eight overhead areas and eight payload areas.

[0060] In one embodiment, the size of the overhead area in each row of the basic frame is 16 bytes, and the size of the payload area in each row is 1896 bytes, that is, all overhead areas in the basic frame have the same size, and all payload areas have the same size.

[0061] In one embodiment, as shown in FIG4 , the size of the payload area in each row of a basic frame may also be different. Optionally, the size of the overhead area in each row of a basic frame is 16 bytes, and the sizes of the payload areas from left to right in each row are 1888 bytes and 1904 bytes, respectively; or, the size of the overhead area in each row is 16 bytes, and the sizes of the payload areas from left to right in each row are 1904 bytes and 1888 bytes, respectively.

[0062] In order to carry low-speed services in the bearer area of ​​the OTN frame, the embodiment of the present application further defines a subframe, as shown in FIG5 , which includes an overhead area for carrying overhead information and a payload area for carrying customer service data.

[0063] Optionally, the size of the above subframe is 1912 bytes, the first 16 bytes in the subframe are the overhead area of ​​the subframe, used to carry overhead information, and the 17th byte to the 1912th byte in the subframe are the payload area of ​​the subframe, used to carry customer service data, occupying 1896 bytes.

[0064] In one embodiment, as shown in FIG6 , eight subframes are defined to constitute a basic frame, that is, each row of the basic frame includes two subframes, the first row consists of subframe 1 and subframe 2, the second row consists of subframe 3 and subframe 4, the third row consists of subframe 5 and subframe 6, and the fourth row consists of subframe 7 and subframe 8. Each subframe constituting the basic frame has the same size and occupies 1912 bytes.

[0065] Optionally, as shown in FIG7 , the overhead area of ​​a subframe or basic frame includes frame header flag information and other overhead information other than the frame header flag information. The frame header flag information occupies 4 bytes, and the other overhead information occupies 12 bytes. The frame header flag information is used to determine the starting position of the subframe or basic frame, and to implement the framing function of the basic frame or subframe. The other overhead information includes at least one of the following: multiframe flag information of the basic frame, overhead multiframe flag information, error checking information, tandem connection monitoring information, channel trace information, protection switching information, indication information for indicating the starting mapping position of the service data after 64 / 66 encoding, and bandwidth lossless adjustment information.

[0066] Optionally, as shown in FIG8 , the frame header flag information includes frame header positioning flag information and sequence flag information. The frame header positioning flag information occupies the first three bytes of the four bytes and the first five bits of the fourth byte, and is used to implement the framing function of the subframe or basic frame. In practical applications, the specific values ​​of the first three bytes of the frame header positioning flag information and the first five bits of the fourth byte can be set based on actual needs, and this embodiment of the present application does not limit this. For example, the first three bytes of the frame header positioning flag information can be 0xF6 in hexadecimal, i.e., "11110110" in binary, and the first five bits of the fourth byte can be "00101." Of course, the first two bytes of the frame header positioning flag information can also be set to 0xF6 in hexadecimal, i.e., "11110110" in binary, the third byte can be set to 0x28 in hexadecimal, i.e., "00101000" in binary, and the first five bits of the fourth byte can be set to "00101."

[0067] In FIG8 , FAS stands for Frame Alignment Signal.

[0068] The sequence flag information above occupies the last three bits of the fourth byte of the frame header flag information and is used to indicate the order of the subframes in the basic frame. The sequence flag information of the eight subframes in the basic frame is as follows: the sequence flag information of subframe 1 is "000", the sequence flag information of subframe 2 is "001", the sequence flag information of subframe 3 is "010", the sequence flag information of subframe 4 is "011", the sequence flag information of subframe 5 is "100", the sequence flag information of subframe 6 is "101", the sequence flag information of subframe 7 is "110", and the sequence flag information of subframe 8 is "111".

[0069] In the above embodiment, the lengths of the eight subframes that make up the basic frame are fixed, meaning each subframe is 1912 bytes in size. In some embodiments, two subframe structures are further defined: a first subframe and a second subframe. As shown in Figures 9 and 10, the size of the first subframe is 1904 bytes, the size of its overhead area is 16 bytes, and the size of its payload area is 1888 bytes. The size of the second subframe is 1920 bytes, the size of its overhead area is 16 bytes, and the size of its payload area is 1904 bytes. The overhead area of ​​the second subframe is the same size as the first subframe, and the overhead bytes are defined in the same way. The only difference between the second subframe and the first subframe is the size of the payload area: the payload area of ​​the first subframe occupies 1888 bytes, while the payload area of ​​the second subframe occupies 1904 bytes.

[0070] That is to say, the first 4 bytes of the overhead area of ​​the first subframe and the second subframe represent the frame header flag information, and the following 12 bytes represent other overhead information, which is used to indicate the multi-frame flag information of the basic frame, the overhead multi-frame flag information, the error check information, the tandem connection monitoring information, the channel trace information, the protection switching information, the indication information for indicating the starting mapping position of the service data after 64 / 66 encoding, and the bandwidth lossless adjustment information.

[0071] The frame header flag information of the first subframe and the second subframe also includes two parts: frame header positioning flag information and sequence flag information; wherein, the frame header positioning flag information also occupies the first 3 bytes of the 4 bytes and the first 5 bits of the 4th byte, and the sequence flag information occupies the last 3 bits of the 4th byte. In practical applications, the specific value of the frame header positioning flag information of the first subframe or the second subframe can be set based on actual needs, and the embodiments of the present application do not limit this. For example, the first three bytes of the frame header positioning flag information of the first subframe or the second subframe can be hexadecimal 0xF6, that is, binary "11110110", and the first 5 bits of the fourth byte can be "00101". Alternatively, the first two bytes of the frame header positioning flag information can be set to hexadecimal 0xF6, that is, binary "11110110", the third byte is set to hexadecimal 0x28, that is, binary "00101000", and the first 5 bits of the fourth byte are set to "00101".

[0072] The sequence flag information in the first and second subframes occupies the last three bits of the fourth byte of the frame header flag information and is used to indicate the order of the subframes in the basic frame. The sequence flag information of the eight subframes in the basic frame is as follows: the sequence flag information of subframe 1 is "000", the sequence flag information of subframe 2 is "001", the sequence flag information of subframe 3 is "010", the sequence flag information of subframe 4 is "011", the sequence flag information of subframe 5 is "100", the sequence flag information of subframe 6 is "101", the sequence flag information of subframe 7 is "110", and the sequence flag information of subframe 8 is "111".

[0073] In an application, when the first subframe and the second subframe are used to form a basic frame, as shown in FIG11 , in the basic frame, odd-numbered subframes can be set as first subframes, and even-numbered subframes can be set as second subframes, i.e., subframes 1, 3, 5, and 7 in the basic frame are first subframes, and subframes 2, 4, 6, and 8 in the basic frame are second subframes. Alternatively, as shown in FIG12 , odd-numbered subframes can be set as second subframes, and even-numbered subframes can be set as first subframes, i.e., subframes 1, 3, 5, and 7 in the basic frame are second subframes, and subframes 2, 4, 6, and 8 in the basic frame are first subframes.

[0074] After defining the basic frame and subframe structures, the service processing method proposed in this application is introduced in conjunction with Figure 13. As shown in Figure 13, the OTN device as the transmitting end needs to perform the following steps to complete the carrying of service data.

[0075] S1301. Obtain business data.

[0076] For example, OTN equipment on the transmitting side acquires service data through a customer service interface. Alternatively, the transmitting device locally generates service data to be transmitted. Service data refers to services that can be carried by the optical transport network. Examples include Ethernet services, packet services, and wireless backhaul services.

[0077] S1302: Map the service data into the basic frame.

[0078] For example, the OTN device on the transmitting side maps the service data into a basic frame or a subframe of the basic frame, specifically, maps the service data into the payload area of ​​the basic frame or the payload area of ​​the subframe.

[0079] S1303: Map the basic frame to some time slots in the OTN frame bearer area.

[0080] The OTN frame bearer area consists of multiple time slots. After a basic frame is obtained, it is carried in the bearer area of ​​the OTN frame as customer service content. For example, one or more time slots are selected based on the service data rate requirements, and the basic frame is mapped to the corresponding one or more time slots. For example, if a time slot corresponds to a 10M service rate, the service data is first mapped into a subframe or basic frame and then carried in a time slot within the OTN frame. Each time slot carries 16 bytes of subframe or basic frame content at a time. After multiple times of carrying, all bytes of the basic frame are carried and transmitted.

[0081] S1304: Send an OTN frame.

[0082] The service processing method in the optical transport network provided by the embodiment of the present application defines a new basic frame structure to carry customer service data, and carries the basic frame through part of the time slots in the traditional OTN frame carrying area, thereby achieving the purpose of transmitting low-rate service data through traditional OTN frames.

[0083] In one embodiment, when the service data is an Ethernet service, the process of mapping the service data into a basic frame may be:

[0084] S13021. Perform 64 / 66 encoding on the service data to obtain a corresponding code block stream.

[0085] The code block stream includes multiple code blocks, and each code block includes a 2-bit synchronization header and 64 bits of data.

[0086] For Ethernet services, Ethernet packets must be 64 / 66 encoded. For example, as shown in Figure 14, every 8 bytes (64 bits total) of customer service data is encoded with 2 bits added to expand it into a 66-bit code block. The added 2 bits are located at the beginning of the 66-bit code block and are called the synchronization header (these two bits are fixed to "01" or "11", with "01" indicating that the code block is a data code block and "11" indicating that the code block is a control code block). After the 64-bit content of 8 bytes is converted into a 66-bit code block through 64 / 66 encoding, it is mapped into a subframe or basic frame for carriage.

[0087] Figure 15 shows the 64 / 66 encoding rules of the Ethernet 802.3 protocol. Each block consists of 66 bits. The first two bits are the synchronization header. The synchronization header bits "01" indicate that the block is a D block (i.e., a data block). The following 8 bytes (64 bits) contain 8 bytes of data. The synchronization header bit "10" indicates that the block is a control block. The first byte following the synchronization header indicates the control block type. The following 7 bytes contain the control block content, which is determined by the control block type. As shown in Figure 16, both S blocks and T blocks are control blocks. The first byte of an S block is 0x78, indicating that the control block is an S block. In addition to indicating the end of a block, a T block can also carry client bytes (located in the last 7 bytes of the block). The Ethernet standard classifies T blocks into eight types: T0, T1, T2, T3, T4, T5, T6, and T7. The T0 (first byte is 0x87) code block does not carry customer information, the T1 code block (first byte is 0x99) carries 1 byte of customer information, the T2 code block (first byte is 0x99) carries 2 bytes of customer information, and so on. The T7 code block (first byte is 0xFF) carries 7 bytes of customer information.

[0088] Each Ethernet message is converted into a 66-bit code block stream after 64 / 66 encoding, as shown in Figure 17. Each message consists of an S code block, several D code blocks and a T code block.

[0089] S13022. Map the code block stream to the payload area in the basic frame or subframe.

[0090] After obtaining the code block stream, it is mapped to the payload area of ​​a basic frame or subframe. As an optional implementation, the code block stream can be directly mapped to the payload area of ​​a basic frame or subframe. The payload area of ​​a basic frame or subframe consists of many bytes, each byte is 8 bits long. 8 bits is not a factor of 66 bits. Therefore, when each 66-bit code block is mapped to a byte, it needs to span multiple bytes, and the starting position of the 66-bit code block is different in each byte. In this direct mapping scenario, to facilitate the receiver to extract the 66-bit code block from the subframe or basic frame, corresponding indication information can be added to the overhead area of ​​the subframe or basic frame to indicate the starting mapping position of the 66-bit code block in the basic frame. There are multiple ways to indicate this, one of which is to directly indicate the starting position of the 66-bit code block in each basic frame. Furthermore, since the 66-bit code block is mapped to the very beginning of the basic frame's payload area every 11 basic frames, the indication information can also be the order of the current basic frame to which the 66-bit code block is mapped within the 11 basic frames. In this way, the starting mapping position of the 66-bit code block in the current basic frame can also be derived through this sequence.

[0091] As another optional implementation, to facilitate mapping and demapping, the synchronization header portion and the code block byte portion of the 66-bit code block can be separated. As shown in Figure 18, each code block has a 2-bit synchronization header. The 2-bit synchronization headers of multiple code blocks are separated and carried together. After the synchronization header and code block byte are separated, since the code block byte portion is 64 bits long, which is 8 bytes in length, a code block byte portion can be mapped exactly into 8 bytes. Based on this concept, as shown in Figure 19, the payload area of ​​a basic frame or subframe can be divided into a synchronization header area and a code block byte area. The synchronization header area is used to store the 2-bit synchronization header separated from each code block, and the code block byte area is used to store the 8-byte content separated from each code block.

[0092] Based on this, the process of mapping a code block stream to a payload area in a basic frame or subframe can be as follows: dividing 4*n code blocks in the code block stream into a group to obtain multiple groups of sub-code block streams; mapping the synchronization headers of each code block in each group of sub-code block streams into a synchronization header region corresponding to each group of sub-code block streams; and mapping the data of each code block in each group of sub-code block streams into a code block byte region corresponding to each group of sub-code block streams; wherein n is a natural number greater than or equal to 1. The size of the synchronization header region corresponding to each group of sub-code block streams is equal to the number of bits occupied by the synchronization headers of each code block in each group of sub-code block streams after being concentrated; and the size of the code block byte region corresponding to each group of sub-code block streams is equal to the number of bytes occupied by the data of each code block in each group of sub-code block streams after being concentrated.

[0093] For example, assuming n is 1, four 66-bit code blocks can be grouped together. Eight synchronization header bits can be separated from the four 66-bit code blocks. The eight synchronization header bits are mapped to one byte in the payload area of ​​a subframe or basic frame. Four 66-bit code blocks can be separated to produce 4*8 bytes, which are mapped to 32 bytes in the payload area of ​​a subframe or basic frame. Thus, in Figure 19 , the synchronization header area length x = 1 byte, and the code block byte area length y = 32 bytes.

[0094] Of course, in addition to the division of the payload area of ​​the subframe or basic frame according to the synchronization header area length x=1 byte and the code block byte area length y=32 bytes, it can also be divided according to the following rules:

[0095] Mode 1: x=1&y=32; 4 code blocks per group

[0096] Mode 2: x=2&y=64; 8 code blocks per group

[0097] Mode 3: x=3&y=96; 12 code blocks per group

[0098] Mode 4: x=4&y=128; 16 code blocks per group

[0099] Mode 5: x=5&y=160; 20 code blocks in a group, and so on.

[0100] In this embodiment, the 66-bit code block stream of the Ethernet message is grouped. The synchronization headers in each group are separated and carried together, and the code block bytes in each group are separated and carried together. Furthermore, the payload area of ​​the subframe or basic frame is divided into a synchronization header area and a code block byte area. The synchronization header area stores the separated synchronization headers in each group, and the code block byte area stores the separated code block bytes in each group. This facilitates 66-bit mapping and demapping.

[0101] Figure 20 is another flow chart of a service processing method in an optical transport network provided by an embodiment of the present application. As shown in Figure 20, the receiving-end OTN device needs to perform the following steps to complete the reassembly of service data.

[0102] S2001. Receive an OTN frame.

[0103] The basic frame is carried in some time slots within the OTN frame bearer area. The basic frame consists of four rows, each containing 3824 bytes. Each row of the basic frame includes two overhead areas for carrying overhead information and two payload areas for carrying customer service data. The overhead and payload areas are arranged adjacent to each other. In other words, a basic frame consists of eight overhead areas and eight payload areas.

[0104] Optionally, each row of the basic frame includes two subframes, each subframe including an overhead area for carrying overhead information and a payload area for carrying service data. In other words, a basic frame includes eight subframes. Optionally, the lengths of the eight subframes can be fixed, or the first subframe and the second subframe can be arranged in an interlaced manner, that is, the odd-numbered frames of the basic frame can be the first subframe, and the even-numbered frames can be the second subframe. Of course, the odd-numbered frames of the basic frame can also be the second subframe, and the even-numbered frames are the first subframe. For the specific structure and byte definition of the subframe, please refer to the description of the above embodiment, and this embodiment will not be repeated here.

[0105] S2002: Extract a basic frame from a corresponding timeslot of the OTN frame.

[0106] After receiving the OTN frame, a subframe or a basic frame is extracted from the corresponding bearer timeslot in the OTN frame.

[0107] S2003. Obtain service data from the basic frame.

[0108] After extracting the subframe or basic frame, the customer's service data is extracted from the payload area of ​​the subframe or basic frame.

[0109] In one embodiment, the process of S2003 may include: performing framing processing on the basic frame; and obtaining service data from the basic frame when the framing is successful.

[0110] After receiving the basic frame, it is initially in a lost frame state and needs to be fixed on the subframe or basic frame. The process of fixing the frame is to determine the frame header position of the basic frame or subframe. Optionally, the process of fixing the basic frame is as follows:

[0111] If the last frame header alignment flag information and sequence flag information are correct, determining whether the data content at a position T bytes after the last frame header alignment flag information conforms to the frame header alignment flag information; wherein T is the sum of the sizes of an overhead area and a payload area;

[0112] If yes, determine whether the current sequence flag information and the previous sequence flag information satisfy the specified sequence relationship based on the three bit values ​​after the data content;

[0113] If so, the current frame header positioning mark information is used as the new previous frame header positioning mark information, and the step of determining whether the data content at the position T bytes after the previous frame header positioning mark information conforms to the frame header positioning mark information is continued;

[0114] When the frame header positioning flag information and the sequence flag information are correct for m consecutive times, it is determined that the basic frame is successfully framed; wherein m is a natural number greater than or equal to 1.

[0115] Case 1: Taking the example of a subframe contained in a basic frame with a fixed length of 1912 bytes (i.e., T equals 1912 bytes), the following describes the framing process for a subframe or basic frame:

[0116] Step 1: First, detect whether the extracted data content is the frame header positioning flag information of the subframe or basic frame. If not, continue to extract the data content of the subsequent corresponding time slots in the OTN payload area until the data content carried by the extracted time slot matches the frame header positioning flag information of the subframe or basic frame (for example, the frame header positioning flag information includes 3 bytes and 5 bits, a total of 29 bits, of which the three bytes are "0xF6" in hexadecimal or "11110110" in binary, and the 5-bit value is "00101"). The frame header position of the subframe or basic frame is detected for the first time.

[0117] Step 2: extract the last three bit values ​​in the frame header flag information of the subframe or basic frame, and determine the sequence flag information of the subframe or basic frame according to these three bit values.

[0118] Step 3: Determine whether the data content at the interval of T bytes after the frame header flag information of the subframe or basic frame conforms to the frame header alignment flag information and whether the current sequence flag information and the previous sequence flag information conform to a sequential relationship of increasing by 1. If the current frame header alignment flag information is incorrect or the current sequence flag information is also incorrect, return to step 1.

[0119] Step 4: If the current frame header alignment flag information and sequence flag information are correct, repeatedly determine whether the frame header alignment flag value of subsequent subframes or basic frames is correct and whether the sequence flag information of the subframes or basic frames is correct at intervals of T bytes. If the frame header alignment flag information and sequence flag information are correct for m consecutive times, it is determined that the basic frame framing is successful.

[0120] In order to avoid the extracted data content being not the frame header but the customer's business data, that is, to ensure the accuracy of the frame header positioning, the extracted data content can be detected m times. It should be noted that the above m can be set based on actual needs, such as m can be 3, 5, 8, 16, 24... When m=3, it means that the frame header positioning mark information of the subframe or basic frame is detected correctly for 3 consecutive times, and the sequence mark information of the subframe or basic frame is also correct, and the frame state is entered. When m=5, it means that the frame header positioning mark information of the subframe or basic frame is detected correctly for 5 consecutive times, and the sequence mark information of the subframe or basic frame is also correct, and the frame state is entered. When m=8, it means that the frame header positioning mark information of the subframe or basic frame is detected correctly for 8 consecutive times (i.e., 1 basic frame length), and the sequence mark information of the subframe or basic frame is also correct, and the frame state is entered. When m=16, it indicates that the frame header positioning flag information of the subframe or basic frame is correct for 16 consecutive times (i.e., 2 basic frame lengths), and the sequence flag information of the subframe or basic frame is also correct, and the frame enters the fixed frame state. When m=24, it indicates that the frame header positioning flag information of the subframe or basic frame is correct for 24 consecutive times (i.e., 3 basic frame lengths), and the sequence flag information of the subframe or basic frame is also correct, and the frame enters the fixed frame state.

[0121] The framing process described above can be described using a state machine, as shown in FIG21 . FIG21 separates the detection of the subframe or basic frame header alignment flag information and the detection of the subframe or basic frame sequence flag information into two independent steps. In implementation, the detection of the subframe or basic frame header alignment flag information and the detection of the subframe or basic frame sequence flag information can also be performed simultaneously, in a single step. In this way, the state machine in FIG21 becomes the state machine in FIG22 .

[0122] In the fixed-frame state, the frame header alignment flag information and the sequence flag information of the subframe or basic frame are checked for correctness at every interval period of T bytes. If either of these is incorrect, the subframe or basic frame detection fails. The frame header alignment flag information and the sequence flag information of the subframe or basic frame are checked for correctness at every interval period of T bytes. If the detection fails a times in a row, the fixed-frame state is exited and the lost-frame state is entered. Where a is a natural number greater than or equal to 1.

[0123] The second case: For example, the subframes included in the basic frame are the first subframe and the second subframe (the size of the first subframe is 1904 bytes, and the size of the second subframe is 1920 bytes, that is, T1 is equal to 1904 bytes, and T2 is equal to 1920 bytes), and subframes 1, 3, 5, and 7 of the basic frame are the first subframe, and subframes 2, 4, 6, and 8 of the basic frame are the second subframe. Initially, the frame is lost, and the subframe or basic frame framing process begins. The framing process is as follows:

[0124] Step 1: First, detect whether the extracted data content is the frame header positioning flag information of the subframe or basic frame. If not, continue to extract the data content of the subsequent corresponding time slots in the OTN payload area until the data content carried by the extracted time slot matches the frame header positioning flag information of the subframe or basic frame (for example, the frame header positioning flag information includes 3 bytes and 5 bits, a total of 29 bits, of which the three bytes are "0xF6" in hexadecimal or "11110110" in binary, and the 5-bit value is "00101"). The frame header position of the subframe or basic frame is detected for the first time.

[0125] Step 2: extract the last three bit values ​​in the frame header flag information of the subframe or basic frame, and determine the sequence flag information of the subframe or basic frame according to these three bit values.

[0126] Step 3: Check whether the data content at the interval T1 or T2 bytes after the frame header flag information of the subframe or basic frame conforms to the frame header positioning flag information, and whether the current sequence flag information and the previous sequence flag information conform to the order relationship of increasing by 1. If the current frame header positioning flag information is incorrect or the current sequence flag information is also incorrect, return to step 1.

[0127] Among them, if the last time was the sequence flag information of the first subframe, then the frame header position of the second subframe is after an interval of T2 bytes, that is, it is necessary to determine the correct situation of the data content at the interval of T2 bytes after the frame header flag information; if the last time was the sequence flag information of the second subframe, then the frame header position of the first subframe is after an interval of TI bytes, that is, it is necessary to determine the correct situation of the data content at the interval of T1 bytes after the frame header flag information.

[0128] Step 4: If the current frame header alignment flag information and sequence flag information are correct, repeatedly determine whether the frame header alignment flag value of subsequent subframes or basic frames is correct and whether the sequence flag information of the subframes or basic frames is correct based on the byte position of the interval period T1 or T2. If the frame header alignment flag information and sequence flag information are correct for m consecutive times, it is determined that the basic frame framing is successful.

[0129] In order to avoid the extracted data content being not the frame header but the customer's business data, that is, to ensure the accuracy of the frame header positioning, the extracted data content can be detected m times. It should be noted that the above m can be set based on actual needs, such as m can be 3, 5, 8, 16, 24... When m=3, it means that the frame header positioning mark information of the subframe or basic frame is detected correctly for 3 consecutive times, and the sequence mark information of the subframe or basic frame is also correct, and the frame state is entered. When m=5, it means that the frame header positioning mark information of the subframe or basic frame is detected correctly for 5 consecutive times, and the sequence mark information of the subframe or basic frame is also correct, and the frame state is entered. When m=8, it means that the frame header positioning mark information of the subframe or basic frame is detected correctly for 8 consecutive times (i.e., 1 basic frame length), and the sequence mark information of the subframe or basic frame is also correct, and the frame state is entered. When m=16, it indicates that the frame header positioning flag information of the subframe or basic frame is correct for 16 consecutive times (i.e., 2 basic frame lengths), and the sequence flag information of the subframe or basic frame is also correct, and the frame enters the fixed frame state. When m=24, it indicates that the frame header positioning flag information of the subframe or basic frame is correct for 24 consecutive times (i.e., 3 basic frame lengths), and the sequence flag information of the subframe or basic frame is also correct, and the frame enters the fixed frame state.

[0130] The framing process described above can be described using a state machine, as shown in FIG23 . FIG23 separates the detection of the subframe or basic frame header alignment flag information and the detection of the subframe or basic frame sequence flag information into two independent steps. In implementation, the detection of the subframe or basic frame header alignment flag information and the detection of the subframe or basic frame sequence flag information can also be performed simultaneously, in a single step. In this way, the state machine in FIG23 becomes the state machine in FIG24 .

[0131] In the fixed-frame state, the frame header alignment flag information and the sequence flag information of the subframe or basic frame are checked for correctness at each interval period T1 or T2 byte position. If either of these is incorrect, the subframe or basic frame detection fails. The frame header alignment flag information and the sequence flag information of the subframe or basic frame are checked for correctness at each interval period T1 or T2 byte position. If the detection fails a times in a row, the fixed-frame state is exited and the lost-frame state is entered. Where a is a natural number greater than or equal to 1.

[0132] In this embodiment, a framing process of a subframe or a basic frame is provided, so that service data can be accurately extracted from the subframe or the basic frame, thereby improving the accuracy of service data detection.

[0133] FIG25 is a schematic diagram of a structure of a service processing device in an optical transport network provided by an embodiment of the present application. As shown in FIG25 , the device may include: an acquisition module 2501 , a processing module 2502 , and a sending module 2503 .

[0134] The acquisition module 2501 is used to acquire business data;

[0135] The processing module 2502 is used to map the service data into a basic frame; wherein the size of the basic frame is 4 lines, each line is 3824 bytes;

[0136] The processing module 2502 is further configured to map the basic frame to a portion of time slots within the OTN frame bearing area;

[0137] The sending module 2503 is used to send the OTN frame.

[0138] Based on the above embodiment, optionally, each row of the basic frame includes two overhead areas for carrying overhead information and two payload areas for carrying the service data.

[0139] Based on the above embodiment, optionally, each row of the basic frame includes 2 subframes, and each subframe includes an overhead area for carrying overhead information and a payload area for carrying the service data.

[0140] Based on the above embodiment, optionally, the size of each subframe is the same.

[0141] Based on the above embodiment, optionally, the two subframes in each row are the first subframe and the second subframe from left to right; or, the two subframes in each row are the second subframe and the first subframe from left to right; wherein the size of the first subframe is smaller than that of the second subframe.

[0142] Based on the above embodiment, optionally, the overhead area includes frame header flag information and other overhead information except the frame header flag information; wherein the frame header flag information is used to implement a framing function of a basic frame or a subframe.

[0143] Based on the above embodiment, optionally, the frame header flag information includes frame header positioning flag information and sequence flag information; wherein the sequence flag information is used to indicate the sequence of subframes in the basic frame.

[0144] Based on the above embodiment, optionally, the size of the overhead area is 16 bytes, and the size of the payload area is 1896 bytes.

[0145] Based on the above embodiment, optionally, the size of the overhead area of ​​the first subframe is 16 bytes, the size of the payload area of ​​the first subframe is 1888 bytes, the size of the overhead area of ​​the second subframe is 16 bytes, and the size of the payload area of ​​the second subframe is 1904 bytes.

[0146] Based on the above embodiment, optionally, the frame header flag information occupies 4 bytes, and the other overhead information occupies 12 bytes.

[0147] Based on the above embodiment, optionally, the frame header positioning flag information occupies the first 3 bytes of the 4 bytes and the first 5 bits of the 4th byte, and the sequence flag information occupies the last 3 bits of the 4th byte.

[0148] Based on the above embodiment, optionally, the other overhead information includes at least one of the following: multi-frame flag information of the basic frame, overhead multi-frame flag information, error checking information, serial connection monitoring information, channel trace information, protection switching information, indication information for indicating the starting mapping position of the service data after 64 / 66 encoding, and bandwidth lossless adjustment information.

[0149] Based on the above embodiment, optionally, the processing module 2502 is also used to perform 64 / 66 encoding on the service data to obtain a corresponding code block stream; wherein the code block stream includes multiple code blocks, each code block includes a 2-bit synchronization header and 64 bits of data; and the code block stream is mapped to the payload area in the basic frame or subframe.

[0150] Based on the above embodiment, optionally, the processing module 2502 is further configured to directly map the code block stream to a payload area in a basic frame or a subframe.

[0151] Based on the above embodiment, optionally, the payload area of ​​the basic frame or subframe includes a synchronization header area and a code block byte area;

[0152] The processing module 2502 is further configured to divide the 4*n code blocks in the code block stream into a group to obtain multiple groups of sub-code block streams; wherein n is a natural number greater than or equal to 1;

[0153] Mapping the synchronization headers of each code block in each group of sub-code block streams to the synchronization header region corresponding to each group of sub-code block streams;

[0154] The data of each code block in each group of sub-code block streams are centrally mapped to the code block byte area corresponding to each group of sub-code block streams.

[0155] Based on the above embodiment, optionally, the size of the synchronization header region corresponding to each group of subcode block streams is equal to the number of bits occupied by the synchronization headers of each code block in each group of subcode block streams after being concentrated;

[0156] The size of the code block byte area corresponding to each group of sub-code block streams is equal to the number of bytes occupied by each code block in each group of sub-code block streams after data is concentrated.

[0157] FIG26 is a schematic diagram of a structure of a service processing device in an optical transport network provided by an embodiment of the present application. As shown in FIG26 , the device may include: a receiving module 2601 and a processing module 2602 .

[0158] The receiving module 2601 is used to receive the OTN frame; wherein, some time slots in the OTN frame carrying area carry basic frames, and the size of the basic frame is 4 lines, each line is 3824 bytes;

[0159] The processing module 2602 is configured to extract the basic frame from the corresponding timeslot of the OTN frame;

[0160] The processing module 2602 is further configured to obtain the service data from the basic frame.

[0161] Based on the above embodiment, optionally, each row of the basic frame includes two overhead areas for carrying overhead information and two payload areas for carrying the service data.

[0162] Based on the above embodiment, optionally, each row of the basic frame includes 2 subframes, and each subframe includes an overhead area for carrying overhead information and a payload area for carrying the service data.

[0163] On the basis of the above embodiment, optionally, the processing module 2602 is further configured to perform framing processing on the basic frame; and if the framing is successful, obtain the service data from the basic frame.

[0164] On the basis of the above embodiment, optionally, the processing module 2602 is also used to determine whether the data content at the position T bytes after the last frame header positioning flag information conforms to the frame header positioning flag information when the last frame header positioning flag information and the sequence flag information are correct; wherein T is the sum of the sizes of an overhead area and a payload area; if so, determine whether the current sequence flag information and the previous sequence flag information meet the specified sequence relationship based on the three bit values ​​after the data content; if so, use the current frame header positioning flag information as the new previous frame header positioning flag information, and continue to execute the step of determining whether the data content at the position T bytes after the previous frame header positioning flag information conforms to the frame header positioning flag information; when the frame header positioning flag information and the sequence flag information are correct for m consecutive times, determine that the basic frame is framed successfully; wherein m is a natural number greater than or equal to 1.

[0165] In one embodiment, an optical transport network device is provided, the internal structure of which may be shown in FIG27 . The device includes a processor, a memory, a network interface, and a database connected via a system bus. The processor of the device is configured to provide computing and control capabilities. The memory of the device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the device is configured to store data generated during service processing in the optical transport network. The network interface of the device is configured to communicate with an external terminal via a network connection. When the computer program is executed by the processor, a service processing method in the optical transport network is implemented.

[0166] Those skilled in the art will understand that the structure shown in Figure 27 is merely a block diagram of a portion of the structure related to the solution of the present application, and does not constitute a limitation on the device to which the solution of the present application is applied. The specific device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0167] In one embodiment, an optical transport network device is provided. The device includes a memory and multiple processors. The memory stores a computer program. When one of the multiple processors executes the computer program, the following steps are implemented:

[0168] Obtain business data;

[0169] Mapping the service data into a basic frame; wherein the size of the basic frame is 4 lines, each line is 3824 bytes;

[0170] Mapping the basic frame to a portion of time slots in the OTN frame bearing area;

[0171] The OTN frame is sent.

[0172] The present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the following steps are implemented:

[0173] Obtain business data;

[0174] Mapping the service data into a basic frame; wherein the size of the basic frame is 4 lines, each line is 3824 bytes;

[0175] Mapping the basic frame to a portion of time slots in the OTN frame bearing area;

[0176] The OTN frame is sent.

[0177] The computer storage medium of the embodiment of the present application can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to: an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination of the above. The computer-readable storage medium includes (a non-exhaustive list): an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), a flash memory, an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0178] A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, the data signal carrying computer-readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0179] The program code contained on the computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wire, optical cable, radio frequency (RF), etc., or any suitable combination of the foregoing.

[0180] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages ​​or a combination of multiple programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, Ruby, Go), and conventional procedural programming languages ​​(such as "C" or similar programming languages). The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0181] It will be appreciated by those skilled in the art that the term user terminal covers any suitable type of wireless user equipment, such as a mobile phone, a portable data processing device, a portable web browser or a vehicle-mounted mobile station.

[0182] In general, various embodiments of the present application may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, although the present application is not limited thereto.

[0183] Embodiments of the present application may be implemented by executing computer program instructions by a data processor of a mobile device, for example, in a processor entity, or by hardware, or by a combination of software and hardware. The computer program instructions may be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages.

[0184] The block diagram of any logic flow in the drawings of this application may represent program steps, or may represent interconnected logic circuits, modules and functions, or may represent a combination of program steps and logic circuits, modules and functions. A computer program may be stored on a memory. The memory may be of any type suitable for the local technical environment and may be implemented using any suitable data storage technology, such as, but not limited to, read-only memory (ROM), random access memory (RAM), optical memory devices and systems (digital versatile discs (DVD) or CDs), etc. Computer-readable media may include non-transitory storage media. A data processor may be of any type suitable for the local technical environment, such as, but not limited to, a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a programmable logic device (FPGA), and a processor based on a multi-core processor architecture.

Claims

1. A service processing method in an optical transport network (OTN), comprising: Get business data; Mapping the service data into a basic frame; wherein the size of the basic frame is 4 lines, each line is 3824 bytes; Mapping the basic frame to a portion of time slots in an OTN frame bearing area; The OTN frame is sent.

2. The method according to claim 1, wherein: Each row of the basic frame includes two overhead areas for carrying overhead information and two payload areas for carrying the service data.

3. The method according to claim 1, wherein: Each row of the basic frame includes 2 subframes, and each subframe includes an overhead area for carrying overhead information and a payload area for carrying the service data.

4. The method according to claim 3, wherein: Each subframe has the same size.

5. The method according to claim 3, wherein: The two subframes in each row are the first subframe and the second subframe from left to right; Alternatively, the two subframes in each row are respectively the second subframe and the first subframe from left to right; The size of the first subframe is smaller than that of the second subframe.

6. The method according to claim 2 or 3, wherein: The overhead area includes frame header flag information and other overhead information except the frame header flag information; wherein the frame header flag information is used to implement a framing function of a basic frame or a subframe.

7. The method according to claim 6, wherein: The frame header flag information includes frame header positioning flag information and sequence flag information; wherein the sequence flag information is used to indicate the sequence of subframes in a basic frame.

8. The method according to claim 2 or 4, wherein: The size of the overhead area is 16 bytes, and the size of the payload area is 1896 bytes.

9. The method according to claim 5, wherein: The size of the overhead area of ​​the first subframe is 16 bytes, the size of the payload area of ​​the first subframe is 1888 bytes, the size of the overhead area of ​​the second subframe is 16 bytes, and the size of the payload area of ​​the second subframe is 1904 bytes.

10. The method according to claim 7, wherein: The frame header flag information occupies 4 bytes, and the other overhead information occupies 12 bytes.

11. The method according to claim 10, wherein: The frame header positioning flag information occupies the first 3 bytes of the 4 bytes and the first 5 bits of the 4th byte, and the sequence flag information occupies the last 3 bits of the 4th byte.

12. The method according to claim 6, wherein: The other overhead information includes at least one of the following: basic frame multiframe flag information, overhead multiframe flag information, error checking information, serial connection monitoring information, channel trace information, protection switching information, indication information for indicating the starting mapping position of service data after 64 / 66 encoding, and bandwidth lossless adjustment information.

13. The method according to claim 1, wherein: Mapping the service data into a basic frame includes: Performing 64 / 66 encoding on the service data to obtain a corresponding code block stream; wherein the code block stream includes a plurality of code blocks, each code block includes a 2-bit synchronization header and 64 bits of data; The code block stream is mapped to a payload area in a basic frame or a subframe.

14. The method according to claim 13, wherein: Mapping the code block stream to a payload area in a basic frame or a subframe includes: The code block stream is directly mapped to the payload area in a basic frame or a subframe.

15. The method according to claim 13, wherein: The payload area of ​​the basic frame or subframe includes a synchronization header area and a code block byte area; Mapping the code block stream to a payload area in a basic frame or a subframe includes: Dividing 4*n code blocks in the code block stream into a group to obtain multiple groups of sub-code block streams; wherein n is a natural number greater than or equal to 1; Concentrating the synchronization headers of the code blocks in each group of sub-code block streams and mapping them to the synchronization header area corresponding to each group of sub-code block streams; The data of each code block in each group of sub-code block streams are centrally mapped to the code block byte area corresponding to each group of sub-code block streams.

16. The method according to claim 15, wherein: The size of the synchronization header area corresponding to each group of sub-code block streams is equal to the number of bits occupied by the synchronization headers of each code block in each group of sub-code block streams after being concentrated; The size of the code block byte area corresponding to each group of sub-code block streams is equal to the number of bytes occupied by each code block in each group of sub-code block streams after data is concentrated.

17. A service processing method in an optical transport network, comprising: Receive the OTN frame; wherein, a basic frame is carried in some time slots in the OTN frame carrying area, and the size of the basic frame is 4 lines, each line is 3824 bytes; Extracting the basic frame from a corresponding time slot of the OTN frame; The service data is obtained from the basic frame.

18. The method according to claim 17, wherein: Each row of the basic frame includes two overhead areas for carrying overhead information and two payload areas for carrying the service data.

19. The method according to claim 17, wherein: Each row of the basic frame includes 2 subframes, and each subframe includes an overhead area for carrying overhead information and a payload area for carrying the service data.

20. The method according to claim 17, wherein: The acquiring the service data from the basic frame comprises: Performing frame fixing processing on the basic frame; In response to successful framing, the service data is acquired from the basic frame.

21. The method according to claim 20, wherein: The performing frame fixing processing on the basic frame comprises: In response to the last frame header positioning mark information and the sequence mark information being correct, determining whether the data content at a position spaced T bytes after the last frame header positioning mark information conforms to the frame header positioning mark information; wherein T is the sum of the sizes of an overhead area and a payload area; In response to the data content being consistent with the frame header positioning flag information, determining whether the current sequence flag information and the previous sequence flag information satisfy a specified sequence relationship according to three bit values ​​after the data content; In response to the sequence flag information of this time and the sequence flag information of the previous time satisfying the specified sequence relationship, the frame header positioning flag information of this time is used as the new frame header positioning flag information of the previous time, and the step of determining whether the data content at the position spaced T bytes after the frame header positioning flag information of the previous time conforms to the frame header positioning flag information is continued; In response to the frame header positioning mark information and the sequence mark information being correct for m consecutive times, it is determined that the basic frame framing is successful; wherein m is a natural number greater than or equal to 1.

22. A service processing device in an optical transport network, comprising: Acquisition module, set to acquire business data; A processing module, configured to map the service data into a basic frame; wherein the size of the basic frame is 4 lines, each line having 3824 bytes; The processing module is further configured to map the basic frame to a portion of time slots in the OTN frame bearing area; The sending module is configured to send the OTN frame.

23. A service processing device in an optical transport network, comprising: A receiving module, configured to receive the OTN frame; wherein a basic frame is carried in some time slots in the OTN frame carrying area, and the size of the basic frame is 4 lines, each line is 3824 bytes; A processing module, configured to extract the basic frame from a corresponding time slot of the OTN frame; The processing module is further configured to obtain service data from the basic frame.

24. An optical transmission network device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the method according to any one of claims 1 to 21 when executing the computer program.

25. A storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the steps of the method according to any one of claims 1 to 21.

Images