Bearer frame and bearing method for VC12 service, and electronic device and storage medium

Abstract

Provided in the present application are a bearer frame and bearing method for a VC12 service, and an electronic device and a storage medium. The bearer frame consists of an S code block, D code blocks and a T code block. The bearer frame comprises an overhead area and a bearer area, wherein the overhead area is used for bearing overhead information of a VC12 service, and the bearer area is used for bearing client content of the VC12 service. The bearer frame is used for mapping to a sub-slot of a service layer for transmission, and one bearer frame is used for bearing one or more VC12 services.

Description

VC12 service carrying frame, carrying method, electronic device and storage medium

[0001] Cross-references

[0002] This application claims priority to a Chinese patent application filed with the Patent Office of China on March 8, 2024, with application number 202410267641.7 and invention name “Bearer frame, bearing method, electronic device and storage medium for VC12 service”. The entire contents of the application are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a bearer frame, a bearer method, an electronic device, and a storage medium for a VC12 service. Background Art

[0004] The Flexible Ethernet (FlexE) protocol standard technical specification defines a method for delivering customer services at speeds of n (n is a positive integer) * 5G (in bits per second). FlexE physical interfaces can efficiently carry customer services at speeds above 5G. To address the need to carry customer services slower than 5G, the protocol standard also establishes a fine-grained frame structure. This divides a 5G-speed FlexE slot into 480 sub-slots, each with a 10M bandwidth, capable of carrying customer services of 10M or higher.

[0005] For virtual container (VC) services in the Synchronous Digital Hierarchy (SDH) standard, such as VC12 services, the above-mentioned sub-time slots can also be used to carry services in related technologies. However, there is currently no relevant solution. Summary of the Invention

[0006] The present application provides a bearer frame, a bearer method, an electronic device, and a storage medium for a VC12 service.

[0007] In the first aspect, a carrier frame for VC12 services is provided, the carrier frame being composed of an S code block, a D code block and a T code block, the carrier frame including an overhead area and a carrier area; the overhead area being used to carry overhead information of the VC12 service; the carrier area being used to carry customer content of the VC12 service; the carrier frame being used to be mapped to a sub-time slot of a service layer for transmission, and one carrier frame being used to carry one or more VC12 services.

[0008] In the second aspect, a method for carrying VC12 services based on the bearer frame of the VC12 services described in the first aspect is provided, which is applied to the sending end, including: mapping the VC12 services to be carried into the bearer frame; mapping the bearer frame into the sub-timeslot; and sending the sub-timeslot to the receiving end.

[0009] On the third aspect, a method for carrying VC12 services based on the bearer frame of the VC12 services described in the first aspect is provided, which is applied to the receiving end and includes: receiving the sub-timeslot sent by the transmitting end; parsing the sub-timeslot and extracting the bearer frame in the sub-timeslot; parsing the S code block, D code block and T code block in the bearer frame and extracting the customer content of the VC12 services carried by the bearer frame.

[0010] In a fourth aspect, an electronic device is provided, comprising: a processor; and a memory for storing instructions executable by the processor; wherein the processor is configured to execute the instructions to implement the method described in the second aspect or the third aspect.

[0011] In a fifth aspect, a computer-readable storage medium is provided. When the instructions in the storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the method described in the second aspect or the third aspect.

[0012] In a sixth aspect, a computer program product is provided, comprising a computer program stored on a non-transitory computer-readable storage medium, wherein the computer program comprises program instructions, which, when executed by a computer, cause the computer to execute the method described in the second aspect or the third aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] In order to more clearly illustrate the technical solutions in this application or the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0014] Figure 1 is a schematic diagram of the existing FlexE protocol combining four 100G optical modules to form a 400G transmission channel;

[0015] FIG2 is a schematic diagram of a data block transmission format of a 100G service in the related art;

[0016] FIG3 is a schematic diagram of code blocks included in a fine-grained frame structure in the related art;

[0017] FIG4 is a schematic diagram of a fine-grained frame structure developed in the related art;

[0018] FIG5 is a schematic diagram of another fine-grained frame structure developed in the related art;

[0019] FIG6 is a schematic diagram of a bearer frame of a VC12 service according to an embodiment of the present application;

[0020] FIG7 is a schematic diagram of a bearer frame of a VC12 service according to an embodiment of the present application;

[0021] FIG8 is a schematic diagram of a bearer frame of a VC12 service according to an embodiment of the present application;

[0022] FIG9 is a schematic diagram of an overhead area according to an embodiment of the present application;

[0023] FIG10 is a schematic diagram showing a second pointer indicating a value that increases or decreases by one unit by bit flipping according to an embodiment of the present application;

[0024] FIG11 is a schematic diagram of an embodiment of the present application using the majority judgment principle to judge the validity of the second pointer indication value;

[0025] FIG12 is a schematic diagram of mapping a bearer frame of a VC12 service to a sub-time slot for transmission according to an embodiment of the present application;

[0026] FIG13 is a schematic diagram of a VC12 service structure according to an embodiment of the present application;

[0027] FIG14 is a schematic diagram of 140 bytes of a complete VC12 service carried in a bearer frame of a VC12 service according to an embodiment of the present application;

[0028] 15 is a schematic diagram of a bearer frame obtained after multiplexing the V1, V2, and V3 bytes in the TU12 service bearer frame of a VC12 service according to an embodiment of the present application;

[0029] FIG16 is a schematic diagram showing an embodiment of the present application in which four VC12 bearer frames are interleaved in units of frames and mapped into a sub-timeslot;

[0030] FIG17 is a schematic diagram showing an embodiment of the present application in which four VC12 bearer frames are interleaved in units of code blocks and mapped into a sub-timeslot;

[0031] FIG18 is a schematic diagram of deinterleaving four VC12 bearer frames in units of frames according to an embodiment of the present application;

[0032] FIG19 is a schematic diagram of deinterleaving four VC12 bearer frames in units of code blocks according to an embodiment of the present application;

[0033] FIG20 is a schematic diagram of 140 bytes of a complete VC12 service carried in a bearer frame of a VC12 service according to an embodiment of the present application;

[0034] FIG21 is a schematic diagram of a bearer frame obtained by multiplexing the V1, V2, and V3 bytes of a TU12 service bearer frame of a VC12 service according to an embodiment of the present application;

[0035] FIG22 is a schematic diagram showing an embodiment of the present application in which three VC12 bearer frames are interleaved in frames and mapped into a sub-timeslot;

[0036] FIG23 is a schematic diagram showing an embodiment of the present application in which three VC12 bearer frames are interleaved in units of code blocks and mapped into a sub-timeslot;

[0037] FIG24 is a schematic diagram of deinterleaving three VC12 bearer frames in units of frames according to an embodiment of the present application;

[0038] FIG25 is a schematic diagram of deinterleaving three VC12 bearer frames in units of code blocks according to an embodiment of the present application;

[0039] FIG26 is a schematic diagram showing a portion of a VC12 service bearer frame carrying four VC12 services according to an embodiment of the present application;

[0040] FIG27 is a schematic diagram showing a portion of a VC12 service bearer frame carrying four VC12 services according to an embodiment of the present application;

[0041] FIG28 is a schematic diagram of a VC12 service bearer frame carrying four complete VC12 services according to an embodiment of the present application;

[0042] FIG29 is a schematic diagram of a VC12 service bearer frame carrying four complete VC12 services according to an embodiment of the present application;

[0043] FIG30 is a schematic diagram of a VC12 service bearer frame carrying four complete VC12 services according to an embodiment of the present application;

[0044] FIG31 is a schematic diagram of a VC12 service bearer frame carrying four complete VC12 services according to an embodiment of the present application;

[0045] FIG32 is a flow chart of a method for carrying VC12 services according to an embodiment of the present application;

[0046] FIG33 is a flow chart of a method for carrying VC12 services according to an embodiment of the present application;

[0047] FIG34 is a schematic structural diagram of an electronic device according to an embodiment of the present application;

[0048] FIG35 is a schematic structural diagram of a VC12 service bearer device according to an embodiment of the present application;

[0049] FIG36 is a schematic structural diagram of a device for carrying VC12 services according to an embodiment of the present application. DETAILED DESCRIPTION

[0050] The rapid increase in user network traffic is driving the rapid development of information transmission bandwidth in communication networks. The interface bandwidth of communication equipment has increased from 10M (unit: bits per second, the same applies to the following content) to 100M, and then from 100M to 1G and 10G, now reaching 100G bandwidth. 100G optical modules are now widely commercialized. 400G optical modules have been developed, but they are expensive, exceeding the price of four 100G modules, affecting their commercial economic value. To deliver 400G services over 100G optical modules, the International Standards Organization defined the FlexE protocol. The FlexE protocol combines multiple 100G optical modules to form a high-speed transmission channel. As shown in Figure 1, four 100G optical modules can be combined using the FlexE protocol to form a 400G transmission channel, equivalent to the transmission speed of a single 400G module. This addresses the need for 400G service delivery without increasing costs.

[0051] For 100G physical layer services, the Ethernet protocol defines that before transmitting 100G data packets, 64 / 66 encoding is performed on the data packet. This expands the 64-bit data block into a 66-bit information block. The additional two bits are placed at the beginning of the 66-bit block to mark the start of the 66-bit block. The 66-bit blocks are then transmitted from the optical port in 66-bit blocks. During reception, the optical port identifies the 66-bit blocks in the received data stream, recovers the original 64-bit data from the 66-bit blocks, and reassembles the data packet. The FlexE protocol operates below the 64-bit to 66-bit block conversion layer and sorts and arranges the 66-bit data blocks before transmission. As shown in Figure 2, for 100G services, every 20 66-bit data blocks are grouped into a data block group. Each group contains 20 data blocks, representing 20 time slots, with each time slot representing a 5G (bit / s) bandwidth service speed. When sending 66-bit data blocks, a FlexE overhead block (the black block in Figure 2) is inserted after every 1023 data block groups (1023 * 20 data blocks). After inserting the overhead block, data blocks continue to be sent. After sending the second 1023 * 20 data blocks, another overhead block is inserted, and so on. In this way, overhead blocks are periodically inserted during the data block transmission process, with the interval between two adjacent overhead blocks being 1023 * 20 data blocks. For services with a physical line speed of 100G (bit / s), the FlexE protocol divides the physical port into 20 time slots, so the bandwidth corresponding to each time slot is 5G.

[0052] The number of timeslots and bandwidth defined by the FlexE protocol can meet the transmission needs of customer services such as routers and optical transport networks (OTNs). However, applying the FlexE protocol in packet transport networks (PTNs) presents several challenges: 1. A 100G physical channel has only 20 timeslots, which is too few; 2. The bandwidth of each timeslot is 5G, and the granularity of a single timeslot is too large. The FlexE protocol has a relatively small number of timeslots and a relatively large granularity. The basic characteristics of timeslots are fewer timeslots and larger granularity. In the PTN service domain, however, the number of customer services is large, and the bandwidth of each service is relatively small. This means that the number of timeslots is large and the bandwidth granularity of each timeslot is small. This makes the FlexE protocol unsuitable for PTN service applications.

[0053] To address customer service needs at speeds less than 5G, communications network operators have defined technical requirements for fine-grained slicing of packet networks and proposed a fine-grained frame structure. This fine-grained frame structure consists of S-blocks, D-blocks, and T-blocks. These blocks are Ethernet-defined encoding blocks. Figure 3 illustrates the 64 / 66 encoding rules of the Ethernet 802.3 protocol. Each block consists of 66 bits, with the first two bits forming the synchronization header. A synchronization header of "01" indicates a D-block (data block). The following eight bytes (64 bits) contain eight bytes of data. A synchronization header of "10" indicates a control block. The first byte after the synchronization header indicates the control block type, followed by the next seven bytes, which are determined by the control block type.

[0054] As shown in Figure 3, the S block, T block, O block, and idle block (also known as IDLE block, I block, or I-block) all belong to the control block. The first byte of the S block is 0x78, indicating that the control block type is an S block. The S block represents the first block in a data message block stream. The T block represents the last block in a data message block stream and is the end block of the message. In addition to indicating the end block, the T block can also carry client byte content (located in the last 7 bytes of the block). The Ethernet standard divides T code blocks into eight types: T0, T1, T2, T3, T4, T5, T6, and T7. The first byte of a T0 code block is 0x87, and the T0 code block does not carry any client information (or client content). The first byte of a T1 code block is 0x99, and the T1 code block carries one byte of client information. The first byte of a T2 code block is 0xAA, and the T2 code block carries two bytes of client information. The first byte of a T3 code block is 0xB4, and the T3 code block carries three bytes of client information. The first byte of a T4 code block is 0xCC, and the T4 code block carries four bytes of client information. The first byte of a T5 code block is 0xD2, and the T5 code block carries five bytes of client information. The first byte of a T6 code block is 0xE1, and the T6 code block carries six bytes of client information. The first byte of a T7 code block is 0xFF, and the T7 code block carries seven bytes of client information. The IDLE block (also called the I block) is an idle block or an error indication block, and its first byte (i.e., the control word) is 0x1E. The O block is a maintenance block, and its first byte is 0x4B.

[0055] Currently, different standards around the world have established different formats for fine-grained frames (also known as fine-grained bearer frames, small-grained bearer frames, or small-grained frames). Figure 4 shows the fine-grained frame structure developed by China Mobile. This fine-grained frame consists of one S-code block, 195 D-code blocks, and one T-code block. Overhead bytes and 24 sub-timeslots are allocated within the D-code block within a fine-grained frame. Every 20 fine-grained frames form a multiframe, with 480 sub-timeslots within a multiframe period. Figure 5 shows the fine-grained frame structure in the standard document currently being developed by the International Telecommunication Union (ITU). This fine-grained frame consists of one S-code block, 990 D-code blocks, and one T-code block. Overhead bytes and 480 sub-timeslots are allocated within the D-code block within a fine-grained frame. 480 fine-grained frames form a multiframe. Each frame in the multiframe carries the relevant overhead information for one time slot, and the 480 fine-grained frames in a multiframe carry all the relevant overhead information for 480 sub-timeslots.

[0056] The fine-grained frames shown in Figures 4 and 5 can be carried on the 5G timeslots of the FlexE interface. Each fine-grained frame is divided into 480 sub-timeslots, dividing the bearer channel of a 5G timeslot into 480 sub-timeslots. Each sub-timeslot has a bandwidth of 10 Mbps (actually slightly higher than 10 Mbps). Therefore, a sub-timeslot in a fine-grained frame can carry a 10 Mbps customer service, which basically meets the carrying requirements of ordinary Ethernet services (current Ethernet service bandwidths include 10 Mbps, 100 Mbps, 1 Mbps, and above, and services greater than 10 Mbps are carried using multiple sub-timeslots). When a fine-grained sub-timeslot carries a 10 Mbps customer service, the 10 Mbps customer service is first 64 / 66 encoded. After encoding, some sub-timeslots are selected for carrying. The fine-grained frame is then mapped to the FlexE protocol timeslot and transmitted, and then delivered to the remote destination device via the 5G timeslots of the FlexE protocol.

[0057] The aforementioned fine-grained slicing technology for the packet network is required to carry 10M customer services. However, in some application scenarios, the device needs to replace SDH equipment and carry various VC services in the SDH system. However, no solution has been considered to achieve the carrying of VC services.

[0058] The embodiment of the present application proposes a bearer frame, a bearing method, an electronic device, and a storage medium for VC12 services. The bearer frame is composed of an S code block, a D code block, and a T code block. The bearer frame includes an overhead area and a bearer area. The overhead area is used to carry the overhead information of the VC12 service, and the bearer area is used to carry the customer content of the VC12 service. The bearer frame is used to be mapped to the sub-timeslot of the service layer for transmission. One bearer frame is used to carry one or more VC12 services. In this way, when carrying VC12 services in the SDH system based on the sub-timeslot in the FlexE protocol standard, one or more VC12 services to be carried can be mapped to the bearer frame, and then the bearer frame can be mapped to the sub-timeslot for transmission. In this way, the carrying of VC12 services can be realized and the carrying requirements for VC12 services can be met.

[0059] In order to help those skilled in the art better understand the technical solutions of this application, the following will clearly and completely describe the technical solutions of this application in conjunction with the drawings of one or more embodiments of this application. Obviously, the described embodiments are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments of this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0060] The terms "first," "second," and the like in this application and the claims are used to distinguish similar objects and are not used to describe a particular order or precedence. It should be understood that such terms are interchangeable where appropriate so that this application can be implemented in sequences other than those illustrated or described herein. In addition, the term "and / or" in this application and the claims refers to at least one of the connected objects, and the character " / " generally indicates that the connected objects are in an "or" relationship.

[0061] The following describes in detail the technical solutions provided by various embodiments of the present application in conjunction with the accompanying drawings.

[0062] FIG6 is a schematic diagram of a bearer frame of a VC12 service according to an embodiment of the present application.

[0063] As shown in Figure 6, the VC12 bearer frame provided by the embodiment of the present application is composed of an S code block, a D code block, and a T code block. Among them, the S code block, the D code block, and the T code block are code blocks of 66 bits in length defined by the Ethernet 802.3 international standard. The S code block is the starting code block of the bearer frame, and the number of S code blocks is 1. The D code block is an intermediate code block of the bearer frame and is a data code block that can be used to carry customer content. One D code block can carry 8 bytes of customer content. The number of data in the D code block is n (n is an integer greater than 1), which can be determined according to the customer content that needs to be carried. The T code block is an intermediate code block of the bearer frame. The data of the T code block is 1, and can specifically be any of the T0 code block, T1 code block, T2 code block, T3 code block, T4 code block, T5 code block, T6 code block, and T7 code block defined in the Ethernet standard.

[0064] The bearer frame for VC12 services includes an overhead area and a bearer area (not shown in Figure 6). The overhead area carries overhead information for the VC12 service (denoted as OH, meaning "overhead"). This overhead information indicates the characteristics of the bearer frame structure. The overhead area can include multiple bytes, such as 2, 3, or 4 bytes, though this is not specifically defined. The overhead area can be located in an S code block, a D code block (for example, in the first D code block), or both an S code block and a D code block (for example, in both an S code block and the first D code block).

[0065] The bearer area is used to carry customer content for VC12 services and can be located in a D code block, in an S code block and a D code block, in a D code block and a T code block, or in an S code block, a D code block, and a T code block. The bearer area can include a bearer adjustment area and a fixed bearer area. The bearer adjustment area can be located in an S code block, a D code block, or both an S code block and a D code block, and can carry customer content or not. Since the bearer adjustment area can carry or not carry customer content, it can be used to adjust the number of bytes used to carry customer content. Whether the bearer adjustment area carries customer content can be determined based on the speed of the customer service being carried, and this is not specifically defined here. The bearer adjustment area can include one or more bytes. If the bearer adjustment area includes multiple bytes, when carrying (or not carrying) customer content, it can be carried (or not) by some or all of the bytes, and this is not specifically defined here. If some bytes carry (or not carry) customer content, these bytes can be located anywhere in the bearer adjustment area, and this is not specifically defined here. For example, the bearer adjustment area includes two bytes. In the case where one byte carries customer content and the other does not carry customer content, the first byte may carry customer content and the second byte may not carry customer content, or the first byte may not carry customer content and the second byte may carry customer content. In a specific implementation, whether to carry customer content in the bearer adjustment area can be determined based on the speed of the customer service to be carried, and the overhead information in the overhead area indicates the number of bytes in the bearer adjustment area used to carry customer content. The entire area of ​​the fixed bearer area is used to carry customer content and is not affected by the customer service speed. The fixed bearer area may include multiple bytes and may be located in a D code block, or in an S code block and a D code block, or in a D code block and a T code block, or in an S code block, a D code block, and a T code block.

[0066] In some implementations, the bearer frame for VC12 services may also include a fixed stuffing area. This fixed stuffing area is an inactive area that does not carry any clients and can be configured as needed. For example, when the bearer area in the bearer frame is too large, some fixed stuffing areas can be configured to reduce the number of bytes in the bearer area used to carry client content, thereby reducing the number of bytes in the effective bearer area. The fixed stuffing area can be located in the D code block and can contain 0 or more bytes. 0 indicates no fixed stuffing area, meaning that the bearer area of ​​the bearer frame is sized exactly to accommodate the required bytes and is not too large. Therefore, there is no need to configure a fixed stuffing area to reduce the size of the effective bearer area.

[0067] Figure 7 is a schematic diagram of a bearer frame for a VC12 service in an embodiment of the present application. The bearer frame shown in Figure 7 consists of one S code block, n D code blocks, and one T code block, where the T code block is a T7 code block. The overhead area (the OH area shown in Figure 7) is located in the S code block and includes a total of 7 bytes. The fixed insertion area (the area where the black box shown in Figure 7 is located) is located in the first D code block and includes a total of 5 bytes. The bearer adjustment area (the area where the asterisk box shown in Figure 7 is located) is located in the first D code block and includes 2 bytes, the first byte being the -adjustment area, and the second byte being the +adjustment area. The fixed bearer area (the white box shown in Figure 7) is located in the D code block and the T code block.

[0068] Figure 8 is a schematic diagram of a bearer frame for a VC12 service according to an embodiment of the present application. The bearer frame shown in Figure 8 consists of one S code block, n D code blocks, and one T code block, where the T code block is a T7 code block. The overhead area (the OH area shown in Figure 8) is located in the first D code block and includes a total of 5 bytes. The fixed insertion area (the area where the black box shown in Figure 8 is located) is located in the first D code block and includes a total of 1 byte. The bearer adjustment area (the area where the asterisk box shown in Figure 8 is located) is located in the first D code block and includes 2 bytes, the first byte being the -adjustment area, and the second byte being the +adjustment area. The fixed bearer area (the white box shown in Figure 8) is located in the D code block and the T code block.

[0069] It should be noted that Figures 7 and 8 are exemplary illustrations of the bearer frame of the VC12 service provided in the embodiment of the present application. In other possible implementations, the structure of the bearer frame may also be in other forms other than those in Figures 7 and 8, which will not be illustrated one by one here.

[0070] A bearer frame for a VC12 service can be used to carry one or more VC12 services. One VC12 service corresponds to one customer, and multiple VC12 services correspond to multiple customers. In the case where a bearer frame is used to carry multiple VC12 services, the multiple VC12 services can be all the services (that is, multiple complete VC12 services) or part of the multiple VC12 services. The bearer frame for VC12 services can be used to map to a sub-timeslot of the service layer for transmission. When mapping the bearer frame to the sub-timeslot, one bearer frame can be mapped to one sub-timeslot, or multiple bearer frames can be mapped to one sub-timeslot, as long as the carrying efficiency requirements are met.

[0071] Based on the bearer frame provided in the embodiment of the present application, when it is necessary to carry VC12 services in a sub-time slot, one or more VC12 services to be carried can be mapped to the bearer frame, and then the bearer frame is mapped to the sub-time slot for transmission. In this way, the carrying of VC12 services can be realized and the carrying requirements for VC12 services can be met.

[0072] In some embodiments, the overhead information carried by the overhead area may include at least one of the following: SDH frame overhead content, used to carry the regeneration section layer and multiplexing section layer overhead; a first pointer indication value, used to indicate whether an abnormal change occurs in the second pointer indication value; and a second pointer indication value, used to indicate the location information of the customer's specific content in the carrying frame.

[0073] The SDH frame overhead content, the first pointer indication value, and the second pointer indication value may each include one or more bytes, which is not specifically limited here.

[0074] The overhead of the regeneration section layer and the multiplexing section layer has been explained in the existing standard protocols and will not be described in detail here.

[0075] The second pointer indicator value can also be called the customer-specific content position pointer value, which can be used to indicate the position information of the specific content of the customer service carried in the bearer frame in the bearer frame, and is a position indication information. The specific content of the customer service can be the first overhead byte of the VC12 service content (such as the V5 byte of the VC12 service), or it can be other byte content, which is not specifically limited here. Generally, the position of the customer's specific content in the bearer frame is not fixed, so the second pointer indicator value is also not fixed, that is, the second pointer indicator value can change. Usually, the change of the second pointer indicator value is relatively small, and this change is a normal change, not an abnormal change. In abnormal circumstances (such as abnormal circumstances such as service interruption), the change of the second pointer indicator value will be relatively large, and this change is an abnormal change. In order to facilitate knowing whether the second pointer indicator value has undergone abnormal changes, in the overhead area of ​​the bearer frame, the first pointer indicator value can indicate whether the second pointer indicator value has undergone abnormal changes.

[0076] In some embodiments, the overhead information carried by the overhead area may also include at least one of the following: a multiframe indication, used to indicate the sequential relationship of multiple bearer frames in the multiframe group; a customer number, used to distinguish different bearer frames carrying different customer services; a customer type, used to characterize the service type carried by the bearer frame; and a cyclic redundancy check (CRC) field.

[0077] The multiframe indication, client number, client type and CRC fields may each include one or more bytes, which are not specifically limited here.

[0078] A multiframe group can include multiple bearer frames. For a bearer frame, if it forms a multiframe group with other bearer frames, the bearer frame's overhead information may include a multiframe indicator. The multiframe indicator can be represented by a sequence value, such as frame 0, frame 1, frame 2, frame 3, etc., or by other means. Examples are not provided here.

[0079] Different bearer frames can carry VC12 services of different customers. When multiple bearer frames carry VC12 services of multiple customers, the overhead information in each bearer frame can include a customer number to distinguish different bearer frames carrying different customer services by the customer number.

[0080] The customer type is used to indicate the service type of the customer service carried by the bearer frame. For a bearer frame carrying VC12 service, the overhead information may include the customer type to indicate that the service type carried by the bearer frame is VC12 service, not other types of customer services such as VC11, VC3 or VC4.

[0081] In actual applications, the overhead information carried in the overhead area can be any one or more of the seven items of overhead information (i.e., SDH frame overhead content, first pointer indicator value, second pointer indicator value, multiframe indicator, customer number, customer type, and CRC field) described above. The specific order can be determined based on actual service requirements and is not specifically limited here. The number of bytes occupied by each item of overhead information can also be determined based on actual service requirements and is not specifically limited here. In a more specific implementation, when the overhead area carries the seven items of overhead information described above, the overhead area can be as shown in Figure 9. In Figure 9, each item of overhead information occupies one byte, and each of the seven items of overhead information occupies seven bytes, meaning that the overhead area occupies a total of seven bytes. The order of the overhead information in the overhead area can be the order shown in Figure 8, or other orders, which are not specifically limited here.

[0082] In some implementations, when the bearer area includes a bearer adjustment area, the aforementioned second pointer indicator value can also be used to indicate a change in the number of bytes used to carry the customer content in the bearer adjustment area. In other words, the second pointer indicator value can have two functions: first, indicating the location of the customer's specific content in the bearer frame, and second, indicating the number of bytes used to carry the customer content in the bearer adjustment area.

[0083] When the second pointer indication value indicates the position of the customer's specific content in the bearer frame and the number of bytes used to carry the customer's content in the bearer adjustment area, in some embodiments, the indication can be performed in the following manner: when the second pointer indication value is increased by one, the position information of the customer's specific content in the bearer frame moves backward by one unit, and the number of bytes used to carry the customer's content in the bearer adjustment area decreases by one unit (the second pointer indication value becomes larger at this time = the bearer area adjustment decrease information); when the second pointer indication value is decreased by one, the position information of the customer's specific content in the bearer frame moves forward by one unit, and the number of bytes used to carry the customer's content in the bearer adjustment area increases by one unit (the second pointer indication value becomes smaller at this time = the bearer area adjustment increase information); when the second pointer indication value remains unchanged, the position information of the customer's specific content in the bearer frame remains unchanged, and the number of bytes used to carry the customer's content in the bearer adjustment area remains unchanged (the second pointer indication value remains stable at this time = the bearer area is adjusted to maintain its original stable value).

[0084] The above-mentioned one unit may be one byte or multiple bytes.

[0085] The position information of the client-specific content in the bearer frame is shifted forward or backward by one unit. This can be done by shifting the byte position occupied by the client-specific content in the bearer frame forward or backward by one unit. For example, if the position information of the client-specific content in the bearer frame is the fifth byte of the second D-code block, and assuming that one unit represents one byte, then after the position information of the client-specific content in the bearer frame is shifted forward by one unit, the new position information is the fourth byte of the second D-code block. After the position information of the client-specific content in the bearer frame is shifted backward by one unit, the new position information is the sixth byte of the second D-code block.

[0086] The bearer adjustment area may include at least two units of bytes. For example, when one unit represents one byte, the bearer adjustment area may include at least two bytes, and when one unit represents three bytes, the bearer adjustment area may include at least six bytes. In some embodiments, the bearer adjustment area may include two areas, namely a first adjustment area and a second adjustment area, and the first adjustment area and the second adjustment area may each include one unit of bytes (i.e., each includes one or more bytes). When the second pointer indication value is increased by one, neither the first adjustment area nor the second adjustment area carries customer content. When the second pointer indication value is decreased by one, both the first adjustment area and the second adjustment area carry customer content. When the second pointer indication value remains unchanged, the first adjustment area does not carry customer content, and the second adjustment area carries customer content.

[0087] For easier understanding, please refer to Figures 7 and 8. In Figures 7 and 8, the bearer adjustment area consists of two bytes: the - adjustment area and the + adjustment area. The - adjustment area can be considered the first adjustment area mentioned above and includes one byte, while the + adjustment area can be considered the second adjustment area mentioned above and includes one byte. Under normal and stable conditions, the second pointer indicates a stable value, and the bearer adjustment area maintains a stable bearer mode. In this stable bearer mode, the - adjustment area does not carry any customer content, and only the + adjustment area carries customer content. This state is called a stable bearer state. When the customer service speed is high and more customer content needs to be carried, the second pointer indicates a decrease of one unit, and the bearer adjustment area changes to an increase bearer mode. In this increase bearer mode, both the - adjustment area and the + adjustment area carry customer content, with the - adjustment area carrying an additional unit of customer content compared to the normal stable state. Because the - adjustment area carries one more unit of customer content, all customer content in the bearer area must be shifted forward by one unit, and the customer-specific content (such as the V5 byte) is also shifted forward by one unit. The new position is the result of the second pointer indicating a decrease of one unit, and the second pointer indicates the new position of the customer-specific content. When the customer service speed is relatively slow and less customer content needs to be carried, the second pointer indication value indicates an increase of one unit, and the carrying adjustment area changes to a reduced carrying mode. In the reduced carrying mode, neither the - adjustment area nor the + adjustment area carries customer services, and the + adjustment area carries less customer content than in the normal stable state. Since the carrying adjustment area carries one unit less customer content, all customer content in the carrying area needs to be moved back one unit in turn, and the customer's specific content (such as V5 bytes) is also moved back one unit. The new position is the result of the second pointer indication value being increased by one unit, and the second pointer indication value indicates the new position of the customer's specific content.

[0088] In Figures 7 and 8 , the -adjustment area and the +adjustment area each comprise one byte. In other implementations, the -adjustment area and the +adjustment area may also comprise 2 bytes, 3 bytes, 4 bytes, 5 bytes, 6 bytes, etc. When both the -adjustment area and the +adjustment area are 2 bytes in size, this is equivalent to adding 2 bytes each time the bytes used to carry customer content are increased, and subtracting 2 bytes each time the bytes used to carry customer content are decreased. Similarly, when both the -adjustment area and the +adjustment area are 3 bytes in size, this is equivalent to adding 3 bytes each time the bytes used to carry customer content are increased, and subtracting 3 bytes each time the bytes used to carry customer content are decreased.

[0089] Changes in the second pointer indicator value indicate changes in the number of valid bytes carrying customer content in the bearer adjustment area, specifically, whether the number of valid bytes carrying customer content this time has increased or decreased relative to the previous number of valid bytes carrying customer content. In actual applications, when the clock frequency of the VC12 service is generally stable, the VC12 service speed is allowed to remain generally stable within a deviation range while meeting clock jitter and drift requirements. Any changes are slow. Accordingly, the number of bytes used to carry customer content in the bearer adjustment area for the VC12 service is generally stable, and any changes are slow. Therefore, changes in the second pointer indicator value are also slow, meaning that the second pointer indicator value changes by only one unit at a time (i.e., by adding or subtracting 1). The new second pointer indicator value is typically an increase or decrease from the previous value, with a limited range of variation. Therefore, when the second pointer indicator value changes, it is not necessary to immediately indicate the second pointer indicator value; it is sufficient to indicate whether the change is an increase, decrease, or no change.

[0090] Based on this idea, in some embodiments, the second pointer indication value can indicate the position information of the customer's specific content in the bearer frame and the change in the number of bytes used to carry the customer content in the bearer adjustment area by the change in the value of the bit at a specific position.

[0091] Specifically, taking the example of a second pointer indicator value including N bits (N may be an integer greater than or equal to 4), the N bits may be divided into two groups, namely a first group of bits and a second group of bits (the two groups of bits may or may not overlap), the first group of bits including P bits (P is an integer greater than or equal to 1 and less than N), and the second group of bits including Q bits (Q is an integer greater than or equal to 1 and less than N, and Q and P may be equal or unequal). If at least half of the P bits (rounded up to a maximum of P) are flipped, the second pointer indicator value is used to indicate that the position information of the client's specific content in the bearer frame is shifted backward by one unit, and the number of bytes in the bearer adjustment area used to carry the client's content is reduced by one unit. If at least half of the Q bits (rounded up to a maximum of Q) are flipped, the second pointer indicator value is used to indicate that the position information of the client's specific content in the bearer frame is shifted forward by one unit, and the number of bytes in the bearer adjustment area used to carry the client's content is increased by one unit. When the N bit values ​​remain unchanged, the second pointer indicator value is used to indicate that the location information of the client's specific content in the bearer frame remains unchanged, and the number of bytes used to carry the client content in the bearer adjustment area remains unchanged.

[0092] For ease of understanding, the following description is given using FIG. 10 as an example.

[0093] The second pointer indication value shown in FIG10 is a 10-bit value. This 10-bit value can be divided into two groups according to even positions and odd positions: the five bits in the even positions (i.e., b9, b7, b5, b3, b1) form one group, and the five bits in the odd positions (i.e., b8, b6, b4, b2, b0) form another group. When the second pointer indication value changes, only the information of whether the change is increased or decreased is required. For example, a group of five bits in the even positions can indicate an increase in the change indication information, and a group of five bits in the odd positions can indicate a decrease in the change indication information (or, a group of five bits in the even positions can indicate a decrease in the change indication information, and a group of five bits in the odd positions can indicate an increase in the change indication information). When the second pointer indication value needs to be increased by 1, all five bits in the even positions are flipped, indicating an increase in the change indication information. When the second pointer indication value needs to be decreased by 1, all five bits in the odd positions are flipped, indicating a decrease in the change indication information. After a bit flip in the even or odd group, the next value is the new one. After all five bits in the even position flip, the next second pointer indicator value is the previous historical stable value plus one. After all five bits in the odd position flip, the next second pointer indicator value is the previous historical stable value minus one. Bit flips in the even or odd group indicate a new second pointer indicator value. At the receiving end, when the second pointer indicator value is inconsistent with the previous historical value, the bit changes in the even or odd group are analyzed separately. If the bits in the even group flip with the even bits in the previous value, the second pointer indicator value has changed by one, and the new second pointer indicator value is the result of adding one to the previous value. If the bits in the odd group flip with the odd bits in the previous value, the second pointer indicator value has changed by one, and the new second pointer indicator value is the result of subtracting one from the previous value. To avoid misjudgment in the event of a single-bit error, whether the five bits in each group have flipped can be determined by majority rule. For example, if any three of the five bits flip, it is determined that the bits in that group have flipped. If any three bits among the five bits are not flipped, it is determined that the group of bits is not flipped and the original value is retained. In this way, even if two bits of the pointer value are wrong, no misjudgment will occur during transmission.

[0094] It should be noted that the above two implementation methods are used as examples to illustrate how the second pointer indication value indicates the location information of the customer's specific content in the bearer frame and the change in the number of bytes used to carry the customer content in the bearer adjustment area. In other possible implementation methods, other indication methods can also be used for indication. Other possible indication methods will not be given one by one here.

[0095] In some embodiments, the second pointer indicator value can take effect in the current frame. After receiving the bearer frame, the receiving end can determine the location information of the customer's specific content in the current bearer frame and the number of bytes used to carry the customer content in the bearer adjustment area based on the second pointer indicator value in the bearer frame. However, in actual applications, the second pointer indicator value may cause an error due to a bit error, thereby indicating erroneous information. For the receiving end, this will also lead to an erroneous judgment result, causing the receiving end to make an error when performing service bearer recovery based on the second pointer indicator value. In order to reduce the erroneous judgment caused by the bit error, in some embodiments, the sending end can transmit the second pointer indicator value multiple times, and the receiving end can use the majority judgment principle to determine the final second pointer indicator value.

[0096] When the majority judgment principle is used to determine the final second pointer indication value, in some embodiments, the majority judgment principle may be such that, if the second pointer indication values ​​in L bearer frames out of M consecutive bearer frames undergo the same change, the second pointer indication value takes effect in the last frame of the M bearer frames. M is an integer greater than or equal to 3, and L is an integer greater than or equal to M / 2 and less than or equal to M. For example, when M is 3, L may be 2, and when M is 4, L may be 3.

[0097] For ease of understanding, please refer to Figure 11. Figure 11 is explained by taking the example that the second pointer indication value takes effect only once every four frames. Specifically, every four consecutive bearer frames can be regarded as a multi-frame group, and in each multi-frame group, the multi-frame sequence values ​​of the four bearer frames are "00", "01", "10" and "11" respectively. For the sending end, when sending a bearer frame to the receiving end, the new second pointer indication value can be transmitted in the four bearer frames of the multi-frame group (there may be bit errors). At the receiving end, for the bearer frames in a multiframe group, the three bearer frames with multiframe sequence values ​​of "00", "01" and "10" operate according to the historical second pointer indication value, but at the same time, the second pointer indication value carried by these three frames and the frame with a multiframe sequence of "11" is extracted. In the case of a single-bit error, even if a bit error occurs and causes one of the values ​​to be wrong, the other three values ​​are correct and the values ​​are completely consistent. According to the majority judgment principle, the three identical second pointer indication values ​​are the updated second pointer indication values, and the updated second pointer indication value will take effect in the frame with a multiframe sequence value of "11", that is, the updated second pointer indication value is used in the frame with a multiframe sequence value of "11" to determine the location information of the customer-specific content and the number of bytes used to carry the customer content in the bearer adjustment area, and the customer content status carried by the bearer adjustment area is determined according to this value and the customer content is extracted. Since the four frames of "00", "01", "10" and "11" all have second pointer indication values, the second pointer indication values ​​of any three frames are selected from these four second pointer indication values ​​for majority judgment principle and the final second pointer indication value is given. This can reduce the erroneous judgment caused by bit errors, ensure the correctness of the receiving end when restoring the service bearer according to the second pointer indication value, and avoid service errors.

[0098] It should be noted that, for the four carrying frames of the above-mentioned multi-frame group, when using the majority judgment principle to judge the second pointer indication value, in addition to using three frames for judgment, two frames can also be used for judgment. That is to say, as long as the second pointer indication values ​​of at least two frames among the four frames have changed and are consistent, it can be considered that the second pointer indication value has changed and takes effect in the last frame.

[0099] In one possible implementation, the bearer frame of the VC12 service may not include the bearer adjustment area, that is, the bearer area only includes a fixed bearer area. In this case, the overhead area may not include the first pointer indication value and the second pointer indication value, and the position of the customer's specific content in the bearer area is fixed.

[0100] Based on the bearer frame of the VC12 service provided in the embodiment of the present application, when carrying the VC12 service, the format of the bearer frame of the VC12 service can be first determined, and then the VC12 service can be encapsulated according to the format, that is, the VC12 service is mapped to the bearer frame of the VC12 service, and finally the bearer frame is mapped to the sub-time slot of the service layer for transmission. Among them, before the bearer frame is mapped to the sub-time slot, idle code blocks and operation, maintenance and management (OAM) code blocks can be inserted between the bearer frames. The specific process can be shown in Figure 12. In Figure 12, after the VC12 service is mapped to the bearer frame of the VC12 service, a certain number of idle code blocks (IDLE code blocks, or I blocks for short) can be inserted between the bearer frames. In this way, the intermediate network device nodes in the network can adapt to the clock deviation between different network device nodes by adding or deleting idle code blocks. In order to monitor the service quality of the service layer during the bearer transmission process, such as delay time and bit error status, idle code blocks can be inserted between bearer frames. An appropriate number of OAM code blocks (abbreviated as o-code blocks, o-blocks) can also be inserted between bearer frames. After inserting IDlE blocks and o-blocks between bearer frames, they are sent out through the fine-grained pipe bearer formed by the service layer sub-time slots.

[0101] When determining the format of the bearer frame, specifically, a bearer frame consists of 1 S code block, multiple D code blocks and 1 T code block, the S code block is the frame header flag block, the D code block is the data block, and the T code block is the end flag block. The bearer frame includes an overhead area and a bearer area, and the bearer area includes a bearer adjustment area and a fixed bearer area. The overhead area carries overhead information. The bearer adjustment area is a dynamic area that may or may not carry customer services, and can be specifically determined according to the speed of the customer services that need to be carried. The fixed bearer area carries customer services at all locations and is not affected by the speed of the customer services. In one embodiment, when the carrying capacity of the bearer frame is too large, a fixed stuffing area can be set in the bearer frame, and the fixed stuffing area does not carry customer services. When the carrying capacity of the bearer frame is just right, the fixed stuffing area may not be set in the bearer frame.

[0102] The length of a bearer frame is a key characteristic of a bearer frame. It is determined by the number of D code blocks in the bearer frame and is related to the bearer frame's carrying efficiency. The bearer frame's carrying efficiency is the ratio of the number of bytes in the bearer frame used to carry customer services to the total number of bytes in the bearer frame. Because the overhead area, fixed insertion area, control word portion of the S code block, and control word portion of the T code block in the bearer frame do not carry customer services, the bearer frame's carrying efficiency is less than 100%. Generally speaking, the greater the number of D code blocks in a bearer frame, the longer the bearer frame length, and the greater the number of bytes in the bearer frame used to carry customer services, the higher the bearer frame's carrying efficiency. When carrying VC12 services, the required carrying efficiency of the bearer frame can be determined based on the desired VC12 service client speed and the selected number of service layer subslots (the number of service layer subslots is equivalent to the total service layer rate). Based on this carrying efficiency requirement, the number of D code blocks in the bearer frame is determined, which in turn determines the bearer frame length and ultimately the bearer frame format.

[0103] Figure 13 shows the VC12 service structure in the SDH system standard. A VC12 service consists of four groups of bytes, each containing one overhead byte and 34 content bytes, totaling 35 bytes per group and 140 bytes in total. The first byte of a VC12 service is the V5 byte. The VC12 service operates at a rate of 2.24 Mbps (in bits per second), while the pipe rate of a sub-timeslot in a fine-grained frame in the service layer is 10 Mbps (in bits per second; in some scenarios, this rate may be higher, such as 10.1 Mbps). Therefore, a sub-timeslot in a fine-grained frame can carry up to four VC12 services. This means that a sub-timeslot in a fine-grained frame can carry one, two, three, or four VC12 services. When one sub-timeslot carries one VC12 service, the corresponding carrying efficiency must be at least 1*2.24 / 10 = 22.4% (when the sub-timeslot speed is calculated at 10.1 Mbps, the corresponding carrying efficiency must be at least 2*2.24 / 10 = 44.8% (when the sub-timeslot speed is calculated at 10.1 Mbps, the corresponding carrying efficiency must be at least 3*2.24 / 10 = 67.2% (when the sub-timeslot speed is calculated at 10.1 Mbps, the corresponding carrying efficiency must be at least 4*2.24 / 10 = 89.6% (when the sub-timeslot speed is calculated at 10.1 Mbps, the corresponding carrying efficiency must be at least 88.71%).

[0104] In actual applications, the sub-timeslot's carrying mode can be determined based on the required carrying efficiency. For example, if a sub-timeslot's speed is 10 Mbps and the required carrying efficiency is 22.4%, a sub-timeslot can carry one, two, three, or four VC12 services. If the required carrying efficiency is 44.8%, a sub-timeslot can carry two, three, or four VC12 services. If the required carrying efficiency is 67.2%, a sub-timeslot can carry three or four VC12 services. If the required carrying efficiency is 89.6%, a sub-timeslot must carry four VC12 services.

[0105] When a sub-timeslot is used to carry one VC12 service, the bearer frame can carry the VC12 service in the following ways: one bearer frame is used to carry one VC12 service, and one bearer frame is mapped to one sub-timeslot for transmission. When a sub-timeslot is used to carry X (X is equal to 2, 3, or 4) VC12 services, the bearer frame can carry the VC12 services in the following ways, including but not limited to the following three:

[0106] Case 1: One bearer frame is used to carry one VC12 service. X bearer frames are mapped to one sub-timeslot for transmission. The X bearer frames carry the VC12 service of one customer or the VC12 services of Y customers (Y is an integer greater than 1 and less than or equal to X).

[0107] In the second case, one bearer frame is used to carry part of the services in X VC12 services (X VC12 services correspond to X customers, one VC12 service corresponds to one customer, and for any VC12 service, one bearer frame is used to carry one-Xth of the customer services). X bearer frames are used to carry all the services of the X VC12 services, and the X bearer frames are mapped to one sub-timeslot for transmission.

[0108] The third case: one bearer frame is used to carry X VC12 services (X VC12 services correspond to X customers, and one VC12 service corresponds to one customer), and the one bearer frame is mapped to one sub-timeslot for transmission.

[0109] The first scenario described above is independent encapsulation mode. In this mode, each VC12 service is independently encapsulated in its own bearer frame. Specifically, one VC12 service per customer is encapsulated in a single bearer frame. The second and third scenarios describe co-encapsulation mode. In this mode, X VC12 services are encapsulated in a single bearer frame. Specifically, all or part of the VC12 services of X customers are encapsulated in a single bearer frame. In this co-encapsulation mode, X VC12 services can share the S-code block, T-code block, and overhead field of the bearer frame, and each VC12 service can have an independent bearer area and independent second pointer indicator value.

[0110] The following will take some more specific implementations as examples to illustrate possible frame structures of a VC12 service bearer frame when the bearer frame carries one or more VC12 services.

[0111] When a bearer frame is used to carry a VC12 service, in some implementations, it can consist of one S code block, 17 D code blocks, and one T code block. The bearer frame's overhead area can be located in the S code block, and the bearer area can be located in the D code block and the T code block. The bearer area includes a 2-byte bearer adjustment area and a 139-byte fixed bearer area. For details, see Figure 14.

[0112] Figure 14 is a schematic diagram of the 140 bytes of a complete VC12 service carried in a bearer frame of a VC12 service. The bearer frame in Figure 14 consists of 1 S code block, 17 D code blocks, and 1 T code block. The bearer frame includes an overhead area, a fixed insertion area, a bearer adjustment area, and a fixed bearing area. The overhead area (OH area) is located in the S code block and includes a total of 7 bytes. The fixed insertion area is located in the first two bytes of the second D code block (in other possible implementations, these two bytes can also be used to place overhead fields, and no fixed insertion area is set). The bearer adjustment area is located after the fixed insertion area and includes 2 bytes (corresponding to the 2 asterisk boxes in the figure), the first byte is the -adjustment area, and the second byte is the +adjustment area. The fixed bearing area includes 139 bytes (corresponding to the 139 white boxes in the figure).

[0113] In the bearer frame shown in Figure 14, during normal transmission, the - adjustment area does not carry customer services, while the + adjustment area and the 139-byte fixed bearer area carry customer services, totaling 140 bytes. This bearer frame can precisely carry the 140 bytes required for a single VC12 service. In this case, the bearer frame's efficiency is 140 / (20*8) = 92% (ignoring the insertion of idle blocks and / or OAM blocks), meeting the efficiency requirements for carrying four VC12 services per sub-timeslot. The bearer frame shown in Figure 14 can carry a complete VC12 service. The position of the VC12 service within the bearer frame is floating, and the location of the first V5 byte of the VC12 service is not fixed. In Figure 14 , the V5 byte is located at the 8th byte position of the first D block of the bearer frame. If the - adjustment area position is used as a reference and is defined as the 0th byte position, then the + adjustment area position is the 1st byte position, and so on. The V5 byte position is the 5th byte position, and the second pointer indicator value in the overhead area can be equal to 5. At the receiving end, upon receiving the bearer frame and extracting the second pointer indicator value from the overhead area as 5, if this second pointer indicator value is the same as the previous value, it can be determined that the second pointer indicator value has not changed. The receiving end can then determine that the - adjustment area does not carry customer content, that customer content begins to be carried in the + adjustment area, and that the + adjustment area and the following 139 byte positions carry customer content for the VC12 service. The first V5 byte in the VC12 service is at the 5th byte position.

[0114] When the speed of VC12 customer services is relatively slow, the bearer frame needs to carry less customer services. The second pointer indicator value can be increased by 1. In the bearer frame, neither the - adjustment area nor the + adjustment area of ​​the bearer adjustment area carries customer services. Only the 139 bytes in the fixed bearer area carry customer services. In this way, a bearer frame carries 139 bytes of VC12 services, reducing the amount of customer services carried and adapting to the slower VC12 services. The first V5 byte in the VC12 services is also delayed by one byte, that is, carried at the first byte of the second D code block.

[0115] When the speed of VC12 customer services is relatively high, the bearer frame needs to carry more customer services. The second pointer indicator value can be reduced by 1. In the bearer frame, both the - adjustment area and the + adjustment area of ​​the bearer adjustment area carry customer services. The 139 bytes of the fixed bearer area also carry customer services. In this way, a bearer frame carries a total of 141 bytes of VC12 services, increasing the carrying space to accommodate the higher-speed VC12 services. The first V5 byte of the VC12 services is also moved forward by one byte to the 7th byte of the first D code block.

[0116] In the SDH system, the TU12 service (defined in the SDH standard, the 140 bytes of the VC12 service plus the four bytes V1, V2, V3, and V4 constitute TU12. TU12 has a total of 144 bytes. The V1 and V2 pointer values ​​are used to indicate the distance between the V5 byte and the V3 byte in the TU12 bearer frame. The V3 byte is used for negative adjustment. When one more byte is carried, the customer service is carried at the V3 byte position. The V4 byte is a null byte). The V1 and V2 bytes are used as overhead bytes for the customer-specific content position pointer value. The V3 byte is placed in the -adjustment area. The 140 bytes after the V3 byte of TU12 are placed in the +adjustment area and the fixed bearer area, respectively. In this way, the VC12 bearer frame can directly copy the V1 byte, V2 byte, V3 byte and all VC12 content bytes in the TU12 into the VC12 bearer frame to complete the encapsulation of the VC12 bearer frame. As shown in Figure 15, Figure 15 is a schematic diagram of a bearer frame for the VC12 service provided by an embodiment of the present application obtained after multiplexing the V1, V2, and V3 bytes in the TU12 service bearer frame. In Figure 15, the V1 byte and the V2 byte are placed in the client-specific content position pointer value in the overhead area, which is equivalent to the second pointer indication value in the VC12 service bearer frame. The V3 byte is placed in the -adjustment area, which is equivalent to the -adjustment area in the VC12 service bearer frame. All VC12 bytes after V3 in the TU12 are placed in sequence in the area after the V3 byte position of the VC12 bearer frame (including the +adjustment area and the fixed bearer area, and the first byte after the V3 byte is equivalent to the +adjustment area in the VC12 service bearer frame).

[0117] When the bearer frames shown in FIG. 14 or FIG. 15 are mapped into one sub-timeslot for transmission, four such bearer frames may be mapped into one sub-timeslot.

[0118] In actual applications, a customer's VC12 service can be carried by one or more bearer frames. One bearer frame is used to carry a complete VC12 service for one customer, and different customers' VC12 services can be carried using different bearer frames. Thus, for the bearer frames shown in FIG14 or FIG15 , when mapping multiple (which can be 2, 3, or 4) bearer frames to one sub-timeslot for transmission, multiple bearer frames corresponding to one customer can be mapped to one sub-timeslot for transmission, or multiple bearer frames corresponding to multiple customers (each bearer frame is used to carry a customer's VC12 service, and different bearer frames are used to carry VC12 services for different customers, and multiple bearer frames corresponding to multiple customers can be represented as a multi-channel bearer frame) can be mapped to one sub-timeslot for transmission.

[0119] When mapping multiple bearer frames into a sub-timeslot, in some implementations, the multiple bearer frames can be mapped into the sub-timeslot using interleaving to equalize the delay of each customer's VC12 service. There are at least two ways to map multiple bearer frames into a sub-timeslot using interleaving: one is to interleave the multiple bearer frames sequentially in frames and then map them into the sub-timeslot; the other is to interleave the multiple bearer frames sequentially in code blocks and then map them into the sub-timeslot. This interleaving using code blocks not only equalizes the delay of each customer's VC12 service, but also reduces the encapsulation delay of the VC12 service.

[0120] For ease of understanding, the following will take a 4-channel bearer frame as an example to illustrate the interleaving method of the multi-channel bearer frame. For details, please refer to Figures 16 and 17.

[0121] In Figure 16, for each bearer frame for Customer 1, Customer 2, Customer 3, and Customer 4 (a total of four bearer frames, each of which can be the bearer frame shown in Figure 14 or Figure 15), the corresponding four bearer frames can be interleaved on a frame-by-frame basis, in the order of Customer 1, Customer 2, Customer 3, and Customer 4, to obtain a set of bearer frame streams. After obtaining a set of bearer frame streams, idle code blocks and OAM code blocks can be inserted into the bearer frame stream (the number of idle code blocks and OAM code blocks inserted can be selected based on actual needs), and then mapped to fine-grained pipe sub-timeslots for transmission. By interleaving each bearer frame on a frame-by-frame basis, the transmission delay time of each customer service can be made equal. Among them, when interleaving the four bearer frames in frame units, interleaving can only be performed after each bearer frame is encapsulated. The delay time of each customer service is the encapsulation completion time of one bearer frame. It takes 500us to complete the encapsulation of 140 bytes of VC12 service, so the encapsulation delay time of each VC12 service is 500us.

[0122] In Figure 17 , for each bearer frame for Client 1, Client 2, Client 3, and Client 4 (a total of four bearer frames, each of which can be the bearer frame shown in Figure 14 or Figure 15 ), the four bearer frames can be interleaved in the order of Client 1, Client 2, Client 3, and Client 4, using code blocks as units to obtain a set of code block streams. In this group of code block streams, the order of the code blocks is: S code block of the first VC12 bearer frame, S code block of the second VC12 bearer frame, S code block of the third VC12 bearer frame, S code block of the fourth VC12 bearer frame, D code block of the first VC12 bearer frame, D code block of the second VC12 bearer frame, D code block of the third VC12 bearer frame, D code block of the fourth VC12 bearer frame, D code block of the first VC12 bearer frame, D code block of the second VC12 bearer frame, D code block of the third VC12 bearer frame, D code block of the fourth VC12 bearer frame, ..., T code block of the first VC12 bearer frame, T code block of the second VC12 bearer frame, T code block of the third VC12 bearer frame, T code block of the fourth VC12 bearer frame. After obtaining the code block stream, idle code blocks and OAM code blocks can be inserted into the code block stream (the number of idle code blocks and the number of OAM code blocks to be inserted can be selected according to actual needs), and then mapped to fine-grained sub-time slots for transmission. Among them, when interleaving the 4-way bearer frames in code block units, there is no need to wait until each VC12 bearer frame is fully encapsulated before starting the interleaving activity. Instead, after each VC12 bearer frame completes partial encapsulation, the interleaving in code block units can be started. In other words, the VC12 bearer frame can be interleaved while being encapsulated, and the interleaving of one frame is completed at the end of encapsulation. In this way, the encapsulation delay of each VC12 service is very small, generally a delay of two or three code blocks. Compared with the interleaving in frame units, the delay time is reduced by at least 10 times, reaching the encapsulation delay level of SDH.

[0123] For the interleaved interleaving method shown in Figure 16, at the receiving end, upon receiving a fine-grained sub-timeslot carrying a bearer frame stream, as shown in Figure 18, the bearer frame stream can be extracted from the fine-grained sub-timeslot. The OAM code blocks and idle code blocks in the bearer frame stream are then stripped off, and deinterleaving is performed on a frame-by-frame basis, resulting in four bearer frames. After obtaining the four bearer frames, the customer's VC12 service can be extracted from the bearer frames.

[0124] For the interleaved interleaving method shown in Figure 17, at the receiving end, upon receiving a fine-grained sub-timeslot carrying a block stream, as shown in Figure 19, the block stream can be extracted from the fine-grained sub-timeslot. The OAM blocks and idle blocks in the block stream are then stripped. The remaining blocks consist entirely of S blocks, D blocks, and T blocks. Deinterleaving can then be performed on a block-by-block basis, with every four S blocks, every four D blocks, and every four T blocks deinterleaved into four groups. The S blocks, D blocks, and T blocks in the same group are then combined to form a VC12 bearer frame, resulting in a four-way bearer frame. After obtaining the four-way bearer frame, the customer's VC12 service can be extracted from the bearer frame.

[0125] When a bearer frame is used to carry one VC12 service, in some implementations, it can consist of one S code block, 18 D code blocks, and one T code block. The bearer frame's overhead area is located in the D code block, while the bearer area is located in both the D code block and the T code block. The bearer area includes a 2-byte bearer adjustment area and a 139-byte fixed bearer area. For details, see Figure 20.

[0126] Figure 20 is a schematic diagram of the 140 bytes of a complete VC12 service carried in a bearer frame of a VC12 service. The bearer frame in Figure 20 consists of 1 S block, 18 D blocks, and 1 T block. The bearer frame includes an overhead area, a bearer adjustment area, and a fixed bearer area. The overhead area (OH area) is located in the D code block and includes a total of 8 bytes. The fixed stuffing area is located in the first two bytes of the second D code block (in other possible implementations, these two bytes can also be used to place overhead fields, and no fixed stuffing area is set). The bearer adjustment area is located after the fixed stuffing area and includes 2 bytes (corresponding to the 2 asterisk boxes in the figure), the first byte is the -adjustment area, and the second byte is the +adjustment area. The fixed bearer area includes 139 bytes (corresponding to the 139 white boxes in the figure).

[0127] In the bearer frame shown in Figure 20, during normal transmission, the - adjustment area does not carry customer traffic, while the + adjustment area and the 139-byte fixed bearer area carry customer traffic, totaling 140 bytes. The first V5 byte of the VC12 service is located at the last byte of the second D code block, as shown in Figure 20. When the VC12 service speed is relatively slow, neither the - adjustment area nor the + adjustment area carries customer traffic, leaving only the 139-byte fixed bearer area carrying customer traffic. The first V5 byte of the VC12 service is carried one byte later, i.e., at the first byte of the third D code block. When the VC12 service speed is relatively fast, the - adjustment area, the + adjustment area, and the 139-byte fixed bearer area all carry customer traffic, totaling 141 bytes. The first V5 byte of the VC12 service is carried one byte earlier, i.e., at the seventh byte of the second D code block.

[0128] In the bearer frame shown in Figure 20, the second pointer indicator value in the overhead area can reuse the V1 and V2 bytes of the TU12 service, and the -adjustment area can reuse the V3 byte of the TU12 service. In this case, the bearer frame shown in Figure 20 can be as shown in Figure 21. In the bearer frame shown in Figure 21, the overhead area includes 10 bytes, of which the V1 and V2 bytes are placed in the client-specific content position pointer value in the overhead area, which is equivalent to the second pointer indicator value in the VC12 service bearer frame. The V3 byte is placed in the -adjustment area, which is equivalent to the -adjustment area in the VC12 service bearer frame. All VC12 bytes after V3 in the TU12 are placed sequentially in the area after the V3 byte position of the VC12 bearer frame (including the +adjustment area and the fixed bearer area; the first byte after the V3 byte is equivalent to the +adjustment area in the VC12 service bearer frame).

[0129] When the bearer frames shown in FIG. 20 or FIG. 21 are mapped into one sub-timeslot for transmission, three such bearer frames are mapped into one sub-timeslot.

[0130] In practical applications, a customer's VC12 service can be carried by one or more bearer frames. One bearer frame is used to carry a complete VC12 service for one customer, and different customers' VC12 services can be carried using different bearer frames. Thus, for the bearer frames shown in Figures 20 or 21, when mapping multiple (possibly two or three) bearer frames to a sub-timeslot for transmission, multiple bearer frames corresponding to a single customer can be mapped to a single sub-timeslot for transmission, or multiple bearer frames corresponding to multiple customers (each bearer frame is used to carry a single customer's VC12 service, and different bearer frames are used to carry VC12 services for different customers, so multiple bearer frames corresponding to multiple customers can be represented as multiple bearer frames) can be mapped to a single sub-timeslot for transmission. When mapping multiple bearer frames to a sub-timeslot, the multiple bearer frames can be interleaved sequentially in frames and then mapped to a sub-timeslot, or interleaved sequentially in code blocks and then mapped to a sub-timeslot. See Figures 22 and 23.

[0131] In Figure 22, for each bearer frame for Customer 1, Customer 2, and Customer 3 (a total of three bearer frames, each of which can be the bearer frame shown in Figure 20 or Figure 21), the corresponding three bearer frames can be interleaved in the order of Customer 1, Customer 2, and Customer 3 to obtain a set of bearer frame streams. After obtaining a set of bearer frame streams, idle code blocks and OAM code blocks can be inserted into the bearer frame stream (the number of idle code blocks and OAM code blocks inserted can be selected based on actual needs), and then mapped to fine-grained pipe sub-timeslots for transmission. By interleaving each bearer frame on a frame basis, the transmission delay of each customer service can be made equal. When interleaving the three bearer frames on a frame basis, each bearer frame must be fully encapsulated before interleaving can be performed. The delay time for each customer service is the time it takes to complete the encapsulation of one bearer frame. It takes 500us to complete the encapsulation of a 140-byte VC12 service, so the encapsulation delay of each VC12 service is 500us.

[0132] In Figure 23 , for each bearer frame of Client 1, Client 2, and Client 34 (a total of three bearer frames, each of which can be the bearer frame shown in Figure 20 or Figure 21 ), the three bearer frames can be interleaved in the order of Client 1, Client 2, and Client 3, resulting in a set of code block streams. The code blocks in this set of code block streams are in the following order: S code block of the first VC12 bearer frame, S code block of the second VC12 bearer frame, S code block of the third VC12 bearer frame, D code block of the first VC12 bearer frame, D code block of the second VC12 bearer frame, D code block of the third VC12 bearer frame, D code block of the first VC12 bearer frame, D code block of the second VC12 bearer frame, D code block of the third VC12 bearer frame, ..., T code block of the first VC12 bearer frame, T code block of the second VC12 bearer frame, T code block of the third VC12 bearer frame. After obtaining the code block stream, idle code blocks and OAM code blocks can be inserted into the code block stream (the number of idle code blocks and the number of OAM code blocks to be inserted can be selected according to actual needs), and then mapped to fine-grained sub-time slots for transmission. Among them, when interleaving the three bearer frames in code block units, there is no need to wait until each VC12 bearer frame is fully encapsulated before starting the interleaving activity. Instead, after each VC12 bearer frame completes partial encapsulation, the interleaving in code block units can be started. In other words, the VC12 bearer frame can be interleaved while being encapsulated, and the interleaving of one frame is completed at the end of encapsulation. In this way, the encapsulation delay of each VC12 service is very small, generally the delay time of two or three code blocks. Compared with the interleaving in frame units, the delay time is reduced by at least 10 times, reaching the encapsulation delay level of SDH.

[0133] For the interleaved interleaving method shown in Figure 22, at the receiving end, upon receiving a fine-grained sub-timeslot carrying a bearer frame stream, as shown in Figure 24, the bearer frame stream can be extracted from the fine-grained sub-timeslot. The OAM code blocks and idle code blocks in the bearer frame stream are then stripped off, and deinterleaving is performed on a frame-by-frame basis, resulting in a three-way bearer frame. After obtaining the four-way bearer frame, the customer's VC12 service can be extracted from the bearer frame.

[0134] For the interleaved interleaving method shown in Figure 23, at the receiving end, upon receiving a fine-grained sub-timeslot carrying a block stream, as shown in Figure 25, the block stream can be extracted from the fine-grained sub-timeslot. The OAM blocks and idle blocks in the block stream are then stripped. The remaining blocks consist entirely of S blocks, D blocks, and T blocks. Deinterleaving can then be performed on a block-by-block basis, with every three S blocks, every three D blocks, and every three T blocks deinterleaved into three groups. The S blocks, D blocks, and T blocks in the same group are then combined to form a VC12 bearer frame, resulting in a three-way bearer frame. After obtaining the three-way bearer frame, the customer's VC12 service can be extracted from the bearer frame.

[0135] In the case where a bearer frame is used to carry multiple VC12 services, taking the example of one bearer frame being used to carry part of the services in four VC12 services, four bearer frames being used to carry all the services of the four VC12 services, and the four bearer frames being used to map into one sub-timeslot, in some implementations, a bearer frame may be composed of one S code block, 17 D code blocks, and one T code block. The overhead area of ​​the bearer frame is located in the S code block, the bearer area is located in the D code block and the T code block, and the bearer area may include an 8-byte bearer adjustment area and a 136-byte fixed bearer area. The bearer adjustment area includes four groups of bearer adjustment areas, each group of bearer adjustment areas may include two bytes (one byte is a -adjustment area, the other byte is a +adjustment area), and one group of bearer adjustment areas corresponds to one VC12 service. The fixed bearer area includes four groups of fixed bearer areas, each group of fixed bearer areas includes 34 bytes, and one group of fixed bearer areas is used to carry the customer content of one VC12 service.

[0136] For easier understanding, please refer to Figure 26.

[0137] Figure 26 shows a schematic diagram of a VC12 service bearer frame carrying a portion of four VC12 services. The bearer frame in Figure 26 consists of one S code block, 17 D code blocks, and one T code block. The bearer frame includes an overhead area, a bearer adjustment area, and a fixed bearer area. The overhead area (OH area) is located in the S code block and consists of 6 bytes. The bearer adjustment area (corresponding to the asterisk box in the figure) consists of 8 bytes and is located in the S code block and D code block. The fixed bearer area (corresponding to the white box in the figure) consists of 136 bytes and is located in the D code block and T code block.

[0138] The bearer frame shown in Figure 26 carries four VC12 services, each carrying 35 bytes, for a total of 140 bytes. These four VC12 services share a common overhead area. Aside from the overhead area, the remaining fields are divided into four groups (numbered 1, 2, 3, and 4 in the lower right corner of the byte frame) using byte interleaving. Each group carries a portion of a customer's VC12 service. Each group has independent overhead bytes for customer-specific content location pointer values, independent - and + adjustment areas, and independent fixed bearer areas. Different groups are independent of each other.

[0139] During actual carrying, each VC12 service is carried independently in its own carrying area, and is carried in three modes according to its own service speed: normal service carrying, pointer value reduction to adjust more carried services, and pointer value increase to adjust less carried services. The adjustment method is independently encapsulated in the same way.

[0140] In Figure 26, for any VC12 service, each bearer frame carries only one-fourth of the byte content of the VC12 service. Four bearer frames are required to carry the entire 140 bytes of the VC12 service. In this way, each bearer frame only needs to carry a portion of the content with an independent customer-specific content location pointer value.

[0141] In a TU12 service bearer frame, the pointer value of the combined V1 and V2 bytes indicates the distance between the V5 byte and the V3 byte. When the pointer value of the combined V1 and V2 bytes decreases, the V3 byte carries customer service, and the V5 byte moves forward. When the pointer value of the combined V1 and V2 bytes remains unchanged, the V3 byte does not carry customer service, the area after the V3 byte carries customer service, and the V5 byte remains unchanged. When the pointer value of the combined V1 and V2 bytes increases, the V3 byte and the first byte after the V3 byte do not carry customer service, the second byte area after the V3 byte begins to carry customer service, and the V5 byte lags behind by one byte. This shows that the function of the pointer value of the combined V1 and V2 bytes is equivalent to the function of the second pointer indicator value in a VC12 service bearer frame. The V3 byte is equivalent to the - adjustment area in a VC12 service bearer frame, and the first byte after the V3 byte is equivalent to the + adjustment area in a VC12 service bearer frame. In this way, when the bearer frame of the VC12 service is used to carry part of the services in the four-channel VC12 services, the content of TU12 can be directly copied when the bearer frame of the VC12 service is generated, and each bearer frame carries a quarter of the TU12 content.

[0142] For example, in Figure 27, bytes V1-V4 (V1, V2, V3, V4, only one of which appears in each bearer frame, appear in rotation, and repeat every four VC12 service bearer frames. V in Figure 27 can be V1, V2, V3, or V4) are placed as a single byte in the overhead area as the pointer value of the client's specific content position. The V3 byte position of the VC12 service bearer frame where the V3 byte appears also serves as the -adjustment area. All bytes after V3 in TU12 are placed in sequence in the area after the client's V3 byte position of the VC12 service bearer frame (including the client's +adjustment area and fixed bearer area). Each frame contains 35 bytes, and four consecutive frames contain 140 bytes of a VC12 service. These four consecutive frames can be mapped to one sub-timeslot for transmission.

[0143] For any VC12 service, the bearer frame shown in Figure 27 carries the 35 bytes of the VC12 service and one V byte (V1, V2, V3, or V4) of the TU12. The bearer frame sequence number indicates the frame number of the current VC frame and which V byte it carries. In a specific implementation, the bearer frames can be divided into sequence numbers 0, 1, 2, 3, 0, 1, 2, 3, 0, 1, 2, 3, .... The 0th VC12 bearer frame carries the V1 byte and the first group of 35 bytes in the VC12 service, the 1st VC12 bearer frame carries the V2 byte and the second group of 35 bytes in the VC12 service, the 2nd VC12 bearer frame carries the V3 byte and the third group of 35 bytes in the VC12 service, and the 3rd VC12 bearer frame carries the V4 byte and the fourth group of 35 bytes in the VC12 service. In this way, every four VC12 bearer frames can carry the V1, V2, V3, and V4 bytes of the TU12 and the 140 bytes of one VC12 service (four groups of 35 bytes, totaling 140 bytes). In the above method, the position where the second VC12 bearer frame carries the V3 byte is the - adjustment area, and the first byte after the position where the second VC12 bearer frame carries the V3 byte is the + adjustment area.

[0144] The bearer frame shown in Figure 27 consists of one S code block, 17 D code blocks, and one T code block. The overhead area is located in the S code block. One bearer frame carries four VC12 services, but each VC12 service only carries one-fourth of the TU12 content, that is, one V byte of the TU12 and one-fourth of the VC12 content.

[0145] In the case where a bearer frame is used to carry multiple VC12 services, taking a bearer frame used to carry all services in 4 VC12 services, and the bearer frame is used to map to a sub-timeslot as an example, in some implementations, a bearer frame can be composed of 1 S code block, 71 D code blocks and 1 T code block. The overhead area of ​​the bearer frame is located in the D code block, and the bearer area is located in the D code block and the T code block. The bearer area includes an 8-byte bearer adjustment area and a 556-byte fixed bearer area. The bearer adjustment area includes 4 groups of bearer adjustment areas, each group of bearer adjustment areas can include 2 bytes (one byte is the - adjustment area, and the other byte is the + adjustment area), and one group of bearer adjustment areas corresponds to one VC12 service. The fixed bearer area includes 4 groups of fixed bearer areas, each group of fixed bearer areas includes 139 bytes, and one group of fixed bearer areas is used to carry the customer content of one VC12 service.

[0146] For easier understanding, please refer to Figure 28.

[0147] Figure 28 shows a VC12 service bearer frame carrying four VC12 services. The bearer frame in Figure 28 consists of one S-block, 71 D-blocks, and one T-block. The bearer frame includes an overhead area, a bearer adjustment area, and a fixed bearer area. The overhead area (OH area) is located in the first and second D-blocks and consists of 11 bytes. The bearer adjustment area (corresponding to the asterisked box in the figure) is 8 bytes and is located in the D-block. The fixed bearer area (corresponding to the white box in the figure) is 556 bytes and is located in the D-block and T-block.

[0148] The bearer frame shown in Figure 28 carries four complete VC12 services. These four VC12 services share the overhead area. Aside from the overhead area, the remaining fields are divided into four groups (numbered 1, 2, 3, and 4 in the lower right corner of the byte frame) using byte interleaving. Each group carries a single customer's VC12 service. Each group has independent overhead bytes for customer-specific content location pointer values, independent - and + adjustment areas, and independent fixed bearer areas. Different groups are independent of each other.

[0149] During actual carrying, each VC12 service is independently carried in its own bearer area and at its own service speed. For any VC12 service, during normal carrying, the -adjustment area does not carry customer services, while the +adjustment area and the 139-byte fixed bearer area carry customer services, for a total of 140 bytes carrying customer services. When the speed of the VC12 service is relatively slow, neither the -adjustment area nor the +adjustment area carries customer services, and only the 139-byte fixed bearer area carries customer services. When the speed of the VC12 service is relatively fast, the -adjustment area, the +adjustment area, and the 139-byte fixed bearer area all carry customer services, for a total of 141 bytes carrying customer services.

[0150] In the bearer frame shown in Figure 28, the overhead area and the bearer area can be moved forward 8 bytes. In this way, the overhead area can be located on the S code block and the first D code block, thereby reducing one D code block. At this time, the bearer frame can be composed of 1 S block, 70 D blocks, and 1 T code block, as shown in Figure 29.

[0151] In the bearer frame shown in Figure 28, each VC12 service has an independent client-specific content location pointer value and bearer adjustment area. If the client-specific content location pointer value reuses the V1 and V2 bytes of the TU12, and the -adjustment area in the bearer adjustment area reuses the V3 byte of the TU12 service, the bearer frame shown in Figure 28 can also be shown as in Figure 30. The bearer frame shown in Figure 30 carries the V1, V2, and V3 bytes of the TU12 of a client, as well as 140 bytes of the VC12 service. The V3 byte position is the -adjustment area, and the first byte after the V3 byte position is the +adjustment area.

[0152] The bearer frame shown in Figure 30 consists of one S code block, 71 D code blocks, and one T code block. If the overhead is located in the first S code block, the bearer frame can consist of one S code block, 70 D code blocks, and one T code block, as shown in Figure 31. Compared to the bearer frame shown in Figure 30, the bearer frame shown in Figure 31 has one fewer D code block, and the overhead bytes are moved forward from being located in the D code block to being located in the S code block.

[0153] It should be noted that the bearer frames shown in Figures 14, 15, 20, 21, and 26 to 31 are exemplary illustrations of the bearer frames for the VC12 service provided in the embodiments of the present application. In other possible implementations, the bearer frames for the VC12 service may also be in formats other than the bearer frames shown in Figures 14, 15, 20, 21, and 26 to 31, or in other variations of the bearer frames shown in Figures 14, 15, 20, 21, and 26 to 31, which are not further exemplified here. Furthermore, the bearer adjustment area in Figures 14, 15, 20, 21, and 26 to 31 is illustrated using 2 bytes as an example. In other possible implementations, it may also include more bytes, which are not further exemplified here.

[0154] The bearer frame provided in the embodiment of the present application is composed of an S code block, a D code block, and a T code block. The bearer frame includes an overhead area and a bearer area. The overhead area is used to carry overhead information of the VC12 service, and the bearer area is used to carry the customer content of the VC12 service. The bearer frame is used to be mapped to the sub-timeslot of the service layer for transmission. One bearer frame is used to carry one or more VC12 services. In this way, when carrying VC12 services based on the sub-timeslots in the FlexE protocol standard, the one or more VC12 services to be carried can be mapped to the bearer frame, and then the bearer frame can be mapped to the sub-timeslot for transmission. In this way, the carrying of VC12 services can be realized and the carrying requirements for VC12 services can be met.

[0155] Based on the bearer frame of the VC12 service provided in the embodiment of the present application, when carrying the VC12 service, for the transmitting end, its bearing method can be as shown in Figure 32.

[0156] Figure 32 is a flow chart of a method for carrying VC12 services according to an embodiment of the present application. The carrying method shown in Figure 32 can be executed by a transmitting end and specifically includes the following steps.

[0157] Step S322: Map the VC12 service to be carried into the bearer frame.

[0158] The bearer frame here is the bearer frame of the VC12 service provided in the embodiment of the present application. The specific structure of the bearer frame can be found in the embodiments shown in Figures 6 to 31 above, and will not be described in detail here.

[0159] When carrying VC12 services, the transmitter can map the VC12 services to be carried into the bearer frame of the VC12 services. Specifically, a customer's VC12 services (i.e., one VC12 service) can be mapped into one bearer frame, corresponding to the independent encapsulation mode, or all or part of the VC12 services of multiple customers (i.e., multiple VC12 services) can be mapped into one bearer frame, corresponding to the co-encapsulation mode.

[0160] Step S324: Map the bearer frame to the sub-time slot.

[0161] When mapping bearer frames to sub-timeslots, one or more bearer frames can be mapped to one sub-timeslot. For example, for the bearer frames shown in Figures 14 or 15, four such bearer frames can be mapped to one sub-timeslot (one bearer frame is used to carry one VC12 service). For the bearer frames shown in Figures 20 or 21, three such bearer frames can be mapped to one sub-timeslot (one bearer frame is used to carry one VC12 service). For the bearer frames shown in Figures 26 and 27, four such bearer frames can be mapped to one sub-timeslot (one bearer frame is used to carry part of four VC12 services, and four bearer frames are used to carry all of four VC12 services). For the bearer frames shown in any one of the embodiments in Figures 29 to 31, one such bearer frame can be mapped to one sub-timeslot (one bearer frame is used to carry four VC12 services).

[0162] In some embodiments, the VC12 service to be carried may include VC12 services of multiple customers. In this case, when carrying the VC12 service, the VC12 services of different customers may be carried in different bearer frames, and one bearer frame is used to carry the complete VC12 service of one customer. Then, when mapping multiple bearer frames corresponding to multiple customers (i.e., multi-channel bearer frames) to one sub-timeslot, the multi-channel bearer frames may be interleaved sequentially in units of frames and then mapped to one sub-timeslot, or interleaved sequentially in units of code blocks and then mapped to one sub-timeslot, so that the transmission delay time of the VC12 service of each customer is equal.

[0163] For example, for the bearer frames shown in Figure 14 or Figure 15, four such bearer frames (each bearer frame is used to carry one VC12 service for one customer, and four bearer frames are used to carry one VC12 service for each of four customers) can be interleaved sequentially in frames and mapped into one sub-timeslot, as shown in Figure 16. In addition, to further reduce the encapsulation delay time of the VC12 service, the four such bearer frames can be interleaved sequentially in code blocks and mapped into one sub-timeslot, as shown in Figure 17. For another example, for the bearer frames shown in Figure 20 or Figure 21, three such bearer frames can be interleaved sequentially in frames and mapped into one sub-timeslot, as shown in Figure 22. In addition, to further reduce the encapsulation delay time of the VC12 service, the three such bearer frames can be interleaved sequentially in code blocks and mapped into one sub-timeslot, as shown in Figure 23.

[0164] When mapping multiple bearer frames into a single sub-timeslot, idle blocks can be inserted between bearer frames. This allows intermediate devices in the network to adapt the block rate to the speed of their device clocks by adding or removing idle blocks. When inserting idle blocks, the number of inserted idle blocks must meet the required bearer efficiency for the bearer frame. For example, if the required bearer efficiency is greater than or equal to 89.6%, then for a VC12 service bearer frame consisting of one S block, 17 D blocks, and one T block, one idle block can be inserted approximately every two VC12 bearer frames. This insertion of idle blocks reduces the equivalent bearer efficiency of the VC12 service bearer frame (counting the idle blocks in the bearer frame). The reduced equivalent efficiency of the VC12 bearer frame is 89.74%, slightly exceeding the desired 89.6% but meeting the required efficiency. When 5095 idle blocks are inserted between 10,000 VC12 service bearer frames, the reduced equivalent efficiency of the VC12 bearer frame is 89.6%. Since the bandwidth of each sub-timeslot is actually slightly higher than 10M (the domestic SPN standard is 10.1M, with a bandwidth margin of 1% higher than 10M, and the international MTN standard is 10.4M, with a bandwidth margin of 4% higher than 10M), when 5000-5200 idle code blocks are inserted between 10,000 VC12 service bearer frames, the carrying efficiency requirements can be met.

[0165] When inserting idle blocks between bearer frames, you can also insert OAM blocks (abbreviated as O-blocks or O-blocks) based on actual needs. OAM blocks can be used to monitor the service quality of the service layer during bearer frame transmission, such as delay time and bit error status. When OAM monitoring is required, an appropriate number of OAM blocks can be inserted between VC12 service bearer frames.

[0166] Step S326: Send the sub-time slot to the receiving end.

[0167] After the bearer frame is mapped to the sub-timeslot, the sub-timeslot can be sent to the receiver, thereby realizing the bearing and transmission of the VC12 service.

[0168] Based on the bearer frame of the VC12 service provided in the embodiment of the present application, when the transmitting end carries the VC12 service based on the bearer frame, for the receiving end, its bearing method can be as shown in Figure 33.

[0169] Figure 33 is a flow chart of a method for carrying VC12 services according to an embodiment of the present application. The carrying method shown in Figure 33 can be executed by a receiving end and specifically includes the following steps.

[0170] Step S332: Receive the sub-time slot sent by the transmitting end.

[0171] When the transmitting end maps the bearer frame to the sub-timeslot based on the method described in the embodiment shown in FIG. 32 and sends the sub-timeslot to the receiving end, the receiving end can receive the sub-timeslot.

[0172] Step S334: parse the sub-timeslot and extract the bearer frame in the sub-timeslot.

[0173] When mapping a bearer frame to a sub-timeslot, the receiving end may use a variety of mapping methods. When parsing the sub-timeslot, the receiving end may perform corresponding demapping according to the mapping method, thereby extracting the bearer frame in the sub-timeslot. In practical applications, the transmitting end and the receiving end may pre-agree (or be specified by the protocol) on which mapping method to use for mapping. In this way, when mapping the bearer frame to the sub-timeslot, the transmitting end may use the agreed (or protocol-specified) mapping method for mapping, and when demapping, the receiving end may use the corresponding method for demapping. The mapping methods may include, but are not limited to: mapping a bearer frame to a sub-timeslot, mapping multiple bearer frames to a sub-timeslot without interleaving, and mapping multiple bearer frames (each bearer frame is used to carry the VC12 service of one customer, and multiple bearer frames are used to carry the VC12 services of multiple customers) to a sub-timeslot after sequential interleaving (in frames or in code blocks).

[0174] When the transmitting end interleaves and maps multiple bearer frames to a sub-timeslot, the receiving end parses the sub-timeslot and extracts the bearer frames in the sub-timeslot, which may include: extracting the bearer frames according to the interleave order in frames to obtain multi-channel bearer frames; or extracting code blocks according to the interleave order in code blocks, merging the S code blocks, D code blocks and T code blocks corresponding to the same VC12 service to obtain multi-channel bearer frames.

[0175] For example, for the bearer frames shown in Figures 14 or 15, when mapping four such bearer frames into a sub-timeslot, if the four bearer frames are sequentially interleaved and interleaved in frames and then mapped into the sub-timeslot, the receiving end can extract the bearer frames according to the interleaving order in frames when parsing the sub-timeslot, thereby obtaining a four-way bearer frame, as shown in Figure 18. If the four bearer frames are sequentially interleaved and interleaved in code blocks and then mapped into the sub-timeslot, the receiving end can extract the code blocks according to the interleaving order in code blocks when parsing the sub-timeslot, and then merge the S code blocks, D code blocks, and T code blocks corresponding to the same VC12 service, thereby obtaining a four-way bearer frame, as shown in Figure 19.

[0176] For another example, for the bearer frames shown in Figures 20 or 21, when mapping three such bearer frames into a sub-timeslot, if the three bearer frames are sequentially interleaved and interleaved in frames and then mapped into the sub-timeslot, the receiving end can extract the bearer frames according to the interleaving order in frames when parsing the sub-timeslot, thereby obtaining a three-way bearer frame, as shown in Figure 24. If the three bearer frames are sequentially interleaved and interleaved in code blocks and then mapped into the sub-timeslot, the receiving end can extract the code blocks according to the interleaving order in code blocks when parsing the sub-timeslot, and then merge the S code blocks, D code blocks, and T code blocks corresponding to the same VC12 service, thereby obtaining a three-way bearer frame, as shown in Figure 25.

[0177] In some embodiments, when the transmitting end maps the bearer frame to the sub-timeslot, the idle code block and / or the OAM code block can be inserted between the bearer frames. Then, when the receiving end parses the sub-timeslot, the OAM code block and the idle code block can be stripped off first, and then the bearer frame can be extracted.

[0178] Step S336: Parse the S code block, D code block, and T code block in the bearer frame to extract the customer content of the VC12 service carried by the bearer frame.

[0179] After extracting the bearer frame from the sub-timeslot, the receiver can first parse the S and D blocks in the bearer frame to obtain the overhead field in the bearer frame's overhead area. Based on the indication in the overhead field, the receiver can determine the byte positions in the D and T blocks that carry the customer content and then extract the customer content carried in these byte positions. After parsing the T block, the customer content of the VC12 carried in the bearer frame can be extracted.

[0180] In some embodiments, the second pointer indication value in the overhead area will only take effect in the case of multiple frames. In this way, after the receiving end extracts the second pointer indication value from the overhead area, it is necessary to use the majority judgment principle to determine the validity of the second pointer indication value, and when it is determined that the second pointer indication value is valid, determine the location information of the customer's specific content in the bearer frame and the number of bytes used to carry the customer content in the bearer adjustment area based on the second pointer indication value. The specific implementation method can be found in the embodiments shown in Figures 10 and 11, which will not be described in detail here.

[0181] Based on the VC12 bearer frame provided in the embodiment of the present application, when carrying VC12 services based on the sub-timeslots in the FlexE protocol standard, one or more VC12 services to be carried can be mapped into the bearer frame, and then the bearer frame can be mapped into the sub-timeslot for transmission. In this way, the carrying of VC12 services can be realized and the carrying requirements for VC12 services can be met.

[0182] The foregoing description describes specific embodiments of the present application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims can be performed in an order different from that described in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require the specific order shown or the sequential order to achieve the desired results. In certain embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0183] FIG34 is a schematic diagram of the structure of an electronic device according to an embodiment of the present application. Referring to FIG34 , at the hardware level, the electronic device includes a processor, an internal bus, a network interface, and a memory. The memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory (non-volatile memory), such as at least one disk storage device. Of course, the electronic device may also include hardware required for other services.

[0184] The processor, network interface, and memory can be interconnected via an internal bus, such as an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus. These buses can be classified as address buses, data buses, and control buses. For ease of illustration, FIG34 shows only one bidirectional arrow, but this does not imply that there is only one bus or only one type of bus.

[0185] The memory is used to store programs. Specifically, the program may include program code, which includes computer operating instructions. The memory may include internal memory and non-volatile memory, and provides instructions and data to the processor.

[0186] The processor reads the corresponding computer program from the non-volatile memory into the internal memory and then runs it, forming a carrier device for the VC12 service at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations: mapping the VC12 service to be carried into the carrier frame of the VC12 service; mapping the carrier frame into a sub-timeslot; and sending the sub-timeslot to the receiving end. Alternatively, it is used to perform the following operations: receiving the sub-timeslot sent by the transmitting end; parsing the sub-timeslot to extract the carrier frame for carrying the VC12 service in the sub-timeslot; parsing the S code block, D code block, and T code block in the carrier frame to extract the customer content of the VC12 service carried by the carrier frame.

[0187] The method performed by the VC12 service bearer device disclosed in the embodiment shown in FIG. 34 of the present application can be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the method can be completed by hardware integrated logic circuits or software instructions in the processor. The processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. The methods, steps, and logic block diagrams disclosed in this application can be implemented or executed. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly implemented and executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in the memory, and the processor reads the information in the memory and, in conjunction with its hardware, completes the steps of the above method.

[0188] The electronic device can also execute the methods of Figures 32 and 33 and implement the functions of the VC12 service bearer device in the embodiments shown in Figures 32 and 33, which will not be described in detail in this application.

[0189] Of course, in addition to software implementation, the electronic device of this application does not exclude other implementation methods, such as logic devices or a combination of software and hardware, etc. That is to say, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0190] The present application also proposes a computer-readable storage medium that stores one or more programs, each of which includes instructions. When executed by a portable electronic device that includes multiple application programs, the instructions enable the portable electronic device to execute the method of the embodiments shown in Figures 32 and 33, and are specifically used to perform the following operations: mapping the VC12 service to be carried into a bearer frame for the VC12 service; mapping the bearer frame into a sub-timeslot; and sending the sub-timeslot to a receiving end. Alternatively, the instructions are used to perform the following operations: receiving a sub-timeslot sent by a transmitting end; parsing the sub-timeslot to extract the bearer frame for carrying the VC12 service in the sub-timeslot; parsing the S code block, D code block, and T code block in the bearer frame to extract the customer content of the VC12 service carried by the bearer frame.

[0191] Figure 35 is a schematic diagram of the structure of a VC12 service bearer device 350 according to an embodiment of the present application. Referring to Figure 35 , in a software implementation, the VC12 service bearer device 350 may include: a first mapping module 351, a second mapping module 352, and a sending module 353. The first mapping module 351 maps the VC12 service to be carried into a bearer frame for the VC12 service; the second mapping module 352 maps the bearer frame into a sub-timeslot; and the sending module 353 sends the sub-timeslot to a receiving end.

[0192] In some embodiments, the second mapping module 352 maps the bearer frame to the sub-timeslot, including: mapping one or more bearer frames to one sub-timeslot; wherein, when mapping one bearer frame to one sub-timeslot, one bearer frame is used to carry multiple VC12 services, and when mapping multiple bearer frames to one sub-timeslot, each bearer frame is used to carry one VC12 service or part of multiple VC12 services.

[0193] In some embodiments, the second mapping module 352 maps multiple bearer frames into one sub-timeslot, including: interleaving the multiple bearer frames in sequence in units of frames and mapping them into one sub-timeslot; or, interleaving the multiple bearer frames in sequence in units of code blocks and mapping them into one sub-timeslot.

[0194] The VC12 service carrying device 350 provided in the present application can also execute the method of FIG32 and realize the functions of the VC12 service carrying device 350 in the embodiment shown in FIG32 , which will not be described in detail in the present application.

[0195] Figure 36 is a schematic diagram of the structure of a VC12 service carrying device 360 ​​according to an embodiment of the present application. Referring to Figure 36 , in a software implementation, the VC12 service carrying device 360 ​​may include: a receiving module 361, a first parsing module 362, and a second parsing module 363. The receiving module 361 receives sub-timeslots sent by a transmitting end; the first parsing module 362 parses the sub-timeslots to extract the bearer frames within the sub-timeslots for carrying the VC12 service; and the second parsing module 363 parses the S code blocks, D code blocks, and T code blocks within the bearer frames to extract the client content of the VC12 service carried by the bearer frames.

[0196] In some embodiments, the first parsing module 362 parses the sub-timeslot and extracts the bearer frame in the sub-timeslot, including: extracting the bearer frame according to an interleaving order based on frames to obtain multiple bearer frames; or extracting the code block according to an interleaving order based on code blocks to merge the S code blocks, D code blocks and T code blocks corresponding to the same VC12 service to obtain multiple bearer frames.

[0197] The VC12 service carrying device 360 ​​provided in this application can also execute the method of Figure 33 and realize the functions of the VC12 service carrying device 360 ​​in the embodiment shown in Figure 33, which will not be repeated in this application.

[0198] In short, the above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

[0199] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0200] Computer-readable media includes permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. The information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0201] The present application also provides a computer program product, comprising a computer program stored on a non-transitory computer-readable storage medium. The computer program includes program instructions that, when executed by a computer, cause the computer to execute the method of the embodiments shown in Figures 32 and 33 , and specifically to perform the following operations: mapping the VC12 service to be carried into a bearer frame for the VC12 service; mapping the bearer frame into a sub-timeslot; and transmitting the sub-timeslot to a receiving end. Alternatively, the computer program product is configured to perform the following operations: receiving a sub-timeslot transmitted by a transmitting end; parsing the sub-timeslot to extract the bearer frame for carrying the VC12 service in the sub-timeslot; and parsing the S code block, D code block, and T code block in the bearer frame to extract the customer content of the VC12 service carried by the bearer frame. It should also be noted that the terms "comprise," "include," or any other variant thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus comprising a series of elements includes not only those elements but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity, or apparatus. Without further constraints, an element defined by the phrase "comprises a..." does not preclude the existence of additional identical elements in the process, method, product or apparatus that includes the element.

[0202] The various embodiments in this application are described in a progressive manner. Similar parts between the various embodiments can be referred to in conjunction with each other. Each embodiment focuses on the differences between the other embodiments. In particular, the system embodiment is generally similar to the method embodiment, so the description is relatively simple. For relevant parts, refer to the partial description of the method embodiment.

Claims

1. A bearer frame for a VC12 service, the bearer frame comprising an S code block, a D code block, and a T code block, and comprising an overhead area and a bearer area; The overhead area is used to carry overhead information of VC12 services; The bearer area is used to carry customer content of VC12 services; The bearer frame is used for mapping to the sub-time slot of the service layer for transmission, and one bearer frame is used for carrying one or more VC12 services; Multiframe indication; Customer number; Customer type; Cyclic redundancy check.

2. The bearer frame according to claim 1, wherein the overhead information includes at least one of the following: SDH frame overhead content, used to carry the regenerator section layer and multiplex section layer overhead; The first pointer indication value is used to indicate whether the second pointer indication value has changed abnormally; The second pointer indication value is used to indicate the location information of the client's specific content in the bearer frame.

3. The bearer frame according to claim 2, wherein the bearer area includes a bearer adjustment area, and the second pointer indication value is further used to indicate a change in the number of bytes used to bear client content in the bearer adjustment area.

4. The bearer frame as described in claim 3, wherein the second pointer indication value includes a V1 byte and a V2 byte.

5. The bearer frame according to claim 3, wherein when the second pointer indicates a value incremented by one, the position information of the client's specific content in the bearer frame is shifted backward by one unit, and the number of bytes used to carry the client's content in the bearer adjustment area is reduced by one unit; When the second pointer indicates a value minus one, the position information of the client's specific content in the bearer frame moves forward by one unit, and the number of bytes used to carry the client's content in the bearer adjustment area increases by one unit; When the second pointer indication value remains unchanged, the location information of the client's specific content in the bearer frame remains unchanged, and the number of bytes used to carry the client's content in the bearer adjustment area remains unchanged; Wherein, the unit includes one or more bytes.

6. The bearer frame according to claim 3, wherein the second pointer indicator value comprises N bits, the N bits comprising a first group of bits and a second group of bits, the first group of bits comprising P bits, the second group of bits comprising Q bits, N is an integer greater than or equal to 4, P is an integer greater than or equal to 1 and less than N, and Q is an integer greater than or equal to 1 and less than N; in, When at least half of the bit values ​​in the P bits are flipped, the position information of the client's specific content in the bearer frame is moved backward by one unit, and the number of bytes used to carry the client content in the bearer adjustment area is reduced by one unit; When at least half of the bit values ​​in the Q bits are flipped, the position information of the client's specific content in the bearer frame is moved forward by one unit, and the number of bytes used to carry the client content in the bearer adjustment area is increased by one unit; When the value of the N bits remains unchanged, the location information of the client's specific content in the bearer frame remains unchanged, and the number of bytes used to carry the client's content in the bearer adjustment area remains unchanged; Wherein, the unit includes one or more bytes.

7. The bearer frame according to claim 5, wherein the bearer adjustment area comprises a first adjustment area and a second adjustment area, and the first adjustment area and the second adjustment area each comprise one or more bytes; in, When the second pointer indication value is used to indicate an increase of one unit, the first adjustment area and the second adjustment area do not carry customer content; In a case where the second pointer indication value is used to indicate a decrease of one unit, both the first adjustment area and the second adjustment area carry customer content; When the value indicated by the second pointer remains unchanged, the first adjustment area does not carry the user content, and the second adjustment area carries the user content.

8. The bearer frame according to claim 7, wherein the first adjustment area includes a V3 byte, and the second adjustment area is located at the first byte after the V3 byte.

9. According to the bearer frame as described in any one of claims 2 to 8, when the second pointer indication value in L of the consecutive M bearer frames undergoes the same change, the second pointer indication value takes effect in the last frame of the M bearer frames, where M is an integer greater than or equal to 3, and L is an integer greater than or equal to M / 2. 10 . The bearer frame according to claim 9 , wherein when M is equal to 3, L is equal to 2; and when M is equal to 4, L is equal to 3.

11. The bearer frame according to any one of claims 1 to 8, wherein when one of the bearer frames is used to carry one VC12 service: One of the bearer frames consists of one S code block, 17 D code blocks, and one T code block, the overhead area is located in the S code block, the bearer area is located in the D code block and the T code block, and the bearer area includes a 2-byte bearer adjustment area and a 139-byte fixed bearer area; or, A carrying frame consists of 1 S code block, 18 D code blocks and 1 T code block, the overhead area is located in the D code block, the carrying area is located in the D code block and the T code block, and the carrying area includes a 2-byte carrying adjustment area and a 139-byte fixed carrying area.

12. The bearer frame according to claim 11, wherein a plurality of the bearer frames are used to be mapped into one sub-timeslot; in, In the case of mapping multiple bearer frames into one sub-timeslot, the multiple bearer frames are interleaved and interleaved in sequence in units of frames and then mapped into one sub-timeslot, or are interleaved and interleaved in sequence in units of code blocks and then mapped into one sub-timeslot.

13. The bearer frame according to any one of claims 1 to 8, wherein when one of the bearer frames is used to carry multiple VC12 services, the multiple VC12 services share the S code block, T code block and overhead area in the bearer frame, and the multiple VC12 services have independent bearer areas and independent second pointer indication values.

14. The bearer frame according to claim 13, wherein the multiple VC12 services are part of four VC12 services, the four bearer frames are used to carry all of the four VC12 services, and the four bearer frames are used to be mapped into one sub-timeslot; in, A bearer frame consists of 1 S code block, 17 D code blocks and 1 T code block, the overhead area is located in the S code block, the bearer area is located in the D code block and the T code block, the bearer area includes an 8-byte bearer adjustment area and a 136-byte fixed bearer area, the bearer adjustment area includes 4 groups of bearer adjustment areas, each group of bearer adjustment areas includes 2 bytes, and one group of bearer adjustment areas corresponds to one VC12 service, the fixed bearer area includes 4 groups of fixed bearer areas, each group of fixed bearer areas includes 34 bytes, and one group of fixed bearer areas is used to carry the customer content of one VC12 service.

15. The bearer frame according to claim 13, wherein the multiple VC12 services are part of four VC12 services, four bearer frames are used to carry all of the four VC12 services, four bearer frames are used to map into one sub-timeslot, one bearer frame consists of one S code block, 17 D code blocks, and one T code block, the overhead area is located in the S code block and the D code block, and the bearer area is located in the D code block and the T code block; in, For any VC12 service, the first of the four bearer frames is used to carry the V1 byte of the TU12 bearer frame and 35 bytes of customer content of the VC12 service, the second bearer frame is used to carry the V2 byte of the TU12 bearer frame and 35 bytes of customer content of the VC12 service, the third bearer frame is used to carry the V3 byte of the TU12 bearer frame and 35 bytes of customer content of the VC12 service, and the fourth bearer frame is used to carry the V4 byte of the TU12 bearer frame and 35 bytes of customer content of the VC12 service.

16. The bearer frame according to claim 13, wherein the multiple VC12 services are all services in four VC12 services, one bearer frame is used to be mapped to one sub-timeslot, one bearer frame consists of one S code block, 71 D code blocks, and one T code block, the overhead area is located in the D code block, and the bearer area is located in the D code block and the T code block; or, one bearer frame consists of one S code block, 70 D code blocks, and one T code block, the overhead area is located in the S code block and the D code block, and the bearer area is located in the D code block and the T code block; in, The bearer area includes an 8-byte bearer adjustment area and a 556-byte fixed bearer area. The bearer adjustment area includes 4 groups of bearer adjustment areas, each group of bearer adjustment areas includes 2 bytes, and one group of bearer adjustment areas corresponds to one VC12 service. The fixed bearer area includes 4 groups of fixed bearer areas, each group of fixed bearer areas includes 139 bytes, and one group of fixed bearer areas is used to carry customer content of one VC12 service.

17. The bearer frame according to claim 1, wherein idle code blocks and / or OAM code blocks are inserted between the bearer frames and then mapped to the sub-time slot of the service layer for transmission.

18. A method for carrying a VC12 service based on the bearer frame for the VC12 service according to any one of claims 1 to 17, applied to a transmitting end, comprising: Mapping the VC12 service to be carried into the bearer frame; Mapping the bearer frame into the sub-time slot; The sub-time slot is sent to a receiving end.

19. The bearer method according to claim 18, wherein mapping the bearer frame to the sub-timeslot comprises: Mapping one or more of the bearer frames into one of the sub-timeslots; Among them, when one bearer frame is mapped to one sub-timeslot, one bearer frame is used to carry multiple VC12 services; when multiple bearer frames are mapped to one sub-timeslot, each bearer frame is used to carry one VC12 service or part of the services in multiple VC12 services.

20. The bearer method according to claim 19, wherein mapping a plurality of the bearer frames into one of the sub-timeslots comprises: Interleave the multiple bearer frames in sequence in frames and map them into one of the sub-time slots; or, The multiple bearer frames are interleaved and interleaved in sequence in units of code blocks and then mapped into one of the sub-time slots.

21. A method for carrying a VC12 service based on the bearer frame of the VC12 service according to any one of claims 1 to 17, applied to a receiving end, comprising: Receive the sub-time slot sent by the transmitter; Parsing the sub-timeslot to extract the bearer frame in the sub-timeslot; The S code block, the D code block and the T code block in the bearer frame are parsed to extract the customer content of the VC12 service carried by the bearer frame.

22. The bearer method according to claim 21, wherein parsing the sub-timeslot to extract the bearer frame in the sub-timeslot comprises: Extracting bearer frames according to an interleaving sequence in frames to obtain multiple bearer frames; or, The code blocks are extracted according to the interleaving order in code block units, and the S code blocks, D code blocks and T code blocks corresponding to the same VC12 service are merged to obtain multiple bearer frames.

23. An electronic device comprising: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the method according to any one of claims 18 to 22. 24 . A computer-readable storage medium, which, when instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the method according to claim 18 .

25. A computer program product, comprising a computer program stored on a non-transitory computer-readable storage medium, the computer program comprising program instructions, which, when executed by a computer, cause the computer to perform the method according to any one of claims 18 to 22.

Images