Carrier frames, transmission methods, electronic device, storage medium and program product

Abstract

Provided in the present application are carrier frames, transmission methods, an electronic device, a storage medium and a program product. A carrier frame consists of a plurality of bytes, and the plurality of bytes comprise: a preamble byte, used for carrying a preamble; an overhead byte, used for carrying overhead information of a service; and a time slot byte, used for carrying service content, the carrier frame being sent after being coded; or the carrier frame consists of a plurality of code groups, each code group having a length of 10 bits, and the plurality of code groups comprising: a control code group, the control code group being a start code group of the carrier frame; a first data code group, used for carrying overhead information of a service; and a second data code group, used for carrying service content, the carrier frame being used for transmission performed by means of a physical coding sublayer (PCS).

Description

Bearer frames, transmission methods, electronic devices, storage media and program products

[0001] Cross-references

[0002] This application claims priority to Chinese Patent Application No. 202411717522.3, filed on November 27, 2024, entitled "Bearer Frame, Transmission Method, Electronic Device, Storage Medium and Program Product", the entire contents of which are incorporated herein by reference. Technical Field

[0003] This application relates to the field of communication technology, and in particular to a carrier frame, transmission method, electronic device, storage medium, and program product. Background Technology

[0004] The Flexible Ethernet (FlexE) protocol standard specification defines a method for transmitting customer services at speeds of n (n is a positive integer) * 5G (in bits per second). The FlexE physical interface can efficiently carry customer services at speeds above 5G. To meet the needs of carrying customer services at speeds below 5G, the protocol standard also specifies a fine-grained frame structure, dividing a 5G-rate FlexE slot into 480 sub-slots, each with a bandwidth of 10M, capable of carrying customer services at 10M and above.

[0005] However, current fine-grained services are typically suited for FlexE or 10 Gigabit Ethernet (GE) interfaces, but not for GE interfaces. There is currently no solution for carrying fine-grained services on GE interfaces. Summary of the Invention

[0006] This application provides a carrier frame, a transmission method, an electronic device, a storage medium, and a program product.

[0007] Firstly, a bearer frame is provided, consisting of multiple bytes, including: a preamble byte for carrying a preamble; an overhead byte for carrying overhead information of the service; and a time slot byte for carrying service content; wherein the bearer frame is transmitted after encoding.

[0008] Secondly, a bearer frame is provided, which consists of multiple code groups, each code group having a length of 10 bits. The multiple code groups include: a control code group, which is the start code group of the bearer frame; a first data code group, used to carry service overhead information; and a second data code group, used to carry service content. The bearer frame is used for transmission through the Physical Coding System (PCS) layer.

[0009] Thirdly, a transmission method is provided, applied at a transmitting end, comprising: transmitting a bearer frame to a receiving end, the bearer frame including the bearer frame as described in the first or second aspect.

[0010] Fourthly, a transmission method is provided, applied at a receiving end, comprising: receiving a bearer frame sent by a sending end, the bearer frame including the bearer frame as described in the first or second aspect; parsing the bearer frame to extract the content carried by the bearer frame.

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

[0012] A sixth aspect provides a computer-readable storage medium that, when instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to perform the method described in the third or fourth aspect.

[0013] In a seventh aspect, a computer program product is provided, the computer program product including a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps in the method described in the third aspect, or to perform some or all of the steps in the method described in the fourth aspect. Attached Figure Description

[0014] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0015] Figure 1 is a schematic diagram of how the existing FlexE protocol combines four 100G optical modules to form a 400G transmission channel.

[0016] Figure 2 is a schematic diagram of the data block transmission format for 100G services in related technologies;

[0017] Figure 3 is a schematic diagram of the code blocks included in the fine-grained frame structure in the related technology;

[0018] Figure 4 is a schematic diagram of the structure of a fine-grained frame in a related technology;

[0019] Figure 5 is a schematic diagram of a fine-grained frame unfolding technique in related technologies;

[0020] Figure 6 is a schematic diagram of the structure of a fine-grained frame as defined by Chinese telecommunications industry standards.

[0021] Figure 7 is a schematic diagram of a multiframe composed of fine-grained frames in related technologies;

[0022] Figure 8 is a schematic diagram of transmitting OAM code blocks in related technologies;

[0023] Figure 9 is a schematic diagram of the periodic transmission of OAM code blocks in related technologies;

[0024] Figure 10 is a schematic diagram of the structure of the O code block in the Ethernet standard;

[0025] Figure 11 is a schematic diagram of the structure of the OAM code block as defined by China Mobile's enterprise standard;

[0026] Figure 12 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0027] Figure 13 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0028] Figure 14 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0029] Figure 15 is a schematic diagram of MII interface bus message transmission according to an embodiment of this application;

[0030] Figure 16 is a schematic diagram of OAM information according to an embodiment of this application;

[0031] Figure 17 is a schematic diagram of OAM information according to an embodiment of this application;

[0032] Figure 18 is a schematic diagram of transmitting OAM information between bearer frames according to an embodiment of this application;

[0033] Figure 19 is a schematic diagram of transmitting OAM information between bearer frames according to an embodiment of this application;

[0034] Figure 20 is a schematic diagram of the combination of OAM information and bearer frame according to an embodiment of this application;

[0035] Figure 21 is a schematic diagram of an embodiment of this application showing the transmission of OAM information combined with a bearer frame;

[0036] Figure 22 is a schematic diagram of an embodiment of this application that carries and transmits OAM information by using fixed OAM bytes in the bearer frame;

[0037] Figure 23 is a schematic diagram of an embodiment of this application that carries and transmits OAM information by using fixed OAM bytes in the bearer frame;

[0038] Figure 24 is a schematic diagram of an embodiment of this application in which the bearer frame carries and transmits OAM information through the preamble byte in the bearer frame;

[0039] Figure 25 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0040] Figure 26 is a schematic diagram of transmitting OAM information between bearer frames according to an embodiment of this application;

[0041] Figure 27 is a schematic diagram of an embodiment of this application in which OAM information is combined with a bearer frame and then transmitted.

[0042] Figure 28 is a schematic diagram of an embodiment of this application that carries and transmits OAM information by using fixed OAM bytes in the bearer frame;

[0043] Figure 29 is a schematic diagram of a fine-grained frame structure defined by international standards;

[0044] Figure 30 is a schematic diagram of a fine-grained frame structure unfolding as defined by international standards;

[0045] Figure 31 is a schematic diagram of OAM information according to an embodiment of this application;

[0046] Figure 32 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0047] Figure 33 is a schematic diagram of OAM information according to an embodiment of this application;

[0048] Figure 34 is a schematic diagram of transmitting OAM information between bearer frames according to an embodiment of this application;

[0049] Figure 35 is a schematic diagram of an embodiment of this application showing the transmission of OAM information combined with a bearer frame;

[0050] Figure 36 is a schematic diagram of an embodiment of this application that carries and transmits OAM information by using fixed OAM bytes in the bearer frame;

[0051] Figure 37 is a schematic diagram of an embodiment of this application in which the bearer frame carries and transmits OAM information through the preamble byte in the bearer frame;

[0052] Figure 38 is a schematic diagram of an embodiment of this application in which the bearer frame carries and transmits OAM information through the preamble byte in the bearer frame;

[0053] Figure 39 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0054] Figure 40 is a schematic diagram of transmitting OAM information between bearer frames according to an embodiment of this application;

[0055] Figure 41 is a schematic diagram of an embodiment of this application showing the transmission of OAM information combined with a bearer frame;

[0056] Figure 42 is a schematic diagram of an embodiment of this application that carries and transmits OAM information by using fixed OAM bytes in the bearer frame;

[0057] Figure 43 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0058] Figure 44 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0059] Figure 45 is a schematic diagram of transmitting the OAM valid field between bearer frames according to an embodiment of this application;

[0060] Figure 46 is a schematic diagram of an embodiment of this application in which OAM information is combined with a bearer frame and then transmitted.

[0061] Figure 47 is a schematic diagram of an embodiment of this application that carries and transmits OAM information through a fixed code group in the bearer frame;

[0062] Figure 48 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0063] Figure 49 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application;

[0064] Figure 50 is a flowchart illustrating a transmission method according to an embodiment of this application;

[0065] Figure 51 is a flowchart illustrating a transmission method according to an embodiment of this application;

[0066] Figure 52 is a schematic diagram of the structure of an electronic device according to an embodiment of this application;

[0067] Figure 53 is a schematic diagram of the structure of a transmission device according to an embodiment of this application;

[0068] Figure 54 is a schematic diagram of the structure of a transmission device according to an embodiment of this application. Detailed Implementation

[0069] The rapid increase in user network traffic has spurred the rapid development of communication network bandwidth. The interface bandwidth of communication equipment has increased from 10 Mbps (bits per second) to 100 Mbps, then further increased by 1 Gbps and 10 Gbps, currently reaching 100 Gbps. 100 Gbps optical modules are now widely used in the market. While 400 Gbps optical modules have been developed, their high price—exceeding the cost of four 100 Gbps modules—affects their commercial economic value. To transmit 400 Gbps services over 100 Gbps optical modules, the international standards organization defined the FlexE protocol. The FlexE protocol combines multiple 100 Gbps optical modules to form a high-speed transmission channel. As shown in Figure 1, combining four 100 Gbps optical modules using the FlexE protocol can form a 400 Gbps transmission channel, equivalent to the transmission speed of a single 400 Gbps module, thus solving the 400 Gbps service transmission requirement without increasing costs.

[0070] For 100G physical layer services, the Ethernet protocol defines that before sending a 100G data packet, the data packet is 64 / 66 encoded, expanding the 64-bit data block into a 66-bit information block. The added 2 bits are placed at the beginning of the 66-bit block as a start marker, and then it is sent out from the optical interface in 66-bit blocks. Upon reception, the optical interface identifies the 66-bit blocks from the received data stream, then recovers the original 64-bit data from the 66-bit blocks and reassembles the data packet. The FlexE protocol, located below the 64-bit to 66-bit block conversion layer, sorts and plans the 66-bit data blocks before sending them. As shown in Figure 2, for 100G services, every 20 66-bit data blocks are divided into a block group, with each group containing 20 blocks, representing 20 time slots, each time slot representing a service speed of 5G (bit / s) bandwidth. 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 data block transmission, with an interval of 1023 * 20 data blocks between adjacent overhead blocks. For a service with a physical line speed of 100 Gbps, the FlexE protocol divides the physical port into 20 time slots, so each time slot corresponds to a bandwidth of 5 Gbps.

[0071] The FlexE protocol defines a sufficient number of time slots and bandwidth to meet the transmission needs of customer services such as routers and Optical Transport Networks (OTN). However, its application in Packet Transport Networks (PTN) presents several challenges: 1. A 100G physical channel has only 20 time slots, which is too few; 2. Each time slot has a bandwidth of 5G, resulting in excessively large granularity. The FlexE protocol suffers from both a limited number of time slots and excessively large granularity, defining a time slot as a small number of slots with high granularity. In contrast, PTN services involve numerous customer services with relatively small bandwidth per service, resulting in a large number of time slots and low granularity for each slot. This makes the FlexE protocol unsuitable for PTN application scenarios.

[0072] To address the needs of customer services operating at speeds lower than 5G, communication network operators have defined the technical requirements for fine-grained slicing in packet slicing networks, proposing a fine-grained service bearer frame (also referred to as a fine-grained bearer frame or fine-grained frame) structure. The fine-grained frame structure consists of S-blocks, D-blocks, and T-blocks. These are coded blocks defined by Ethernet. Figure 3 shows the 64 / 66 encoding rules of the Ethernet 802.3 protocol. Each block consists of 66 bits, with the first two bits being the block's synchronization header. A synchronization header bit of "01" indicates that the block is a D-block (data block), followed by 8 bytes (64 bits) of data content. A synchronization header bit of "10" indicates that the block is a control block. The first byte after the synchronization header bit of a control block indicates the type of control block, followed by 7 bytes of control block content, determined by the control block type.

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

[0074] Figure 4 shows a common fine-grained frame structure in related technologies. The fine-grained frame structure shown in Figure 4 consists of S-blocks, D-blocks, and T-blocks. Figure 5 is a structural diagram showing the expanded form of each block shown in Figure 4. In Figure 5, each block is expanded into 66 bits. The fine-grained frame contains an overhead field, i.e., OH (overhead information), and blank spaces are used to carry fine-grained services.

[0075] Currently, different frame formats (sometimes called fine-granularity bearer frames, small-granularity bearer frames, small-granularity frames, or fine-granularity units (FGU)) have been established both domestically and internationally. Figure 6 shows a fine-granularity frame structure established by the Chinese telecommunications industry standard. A fine-granularity frame consists of one S-block, 195 D-blocks, and one T-block. When transmitting this fine-granularity frame, an idle block (called an idle block or I-block) is inserted between each fine-granularity frame. Intermediate devices in the network adjust the speed by adding or removing idle blocks to adapt to clock frequency differences between different devices. The D-block in the fine-granularity frame is divided into overhead bytes and 24 sub-time slots. Every 20 fine-granularity frames form a multiframe, and a multiframe cycle contains 480 sub-time slots, as shown in Figure 7. Fine-grained frames are carried on 5G-speed time slots of the FlexE interface. Each fine-grained frame is divided into 480 sub-slots, effectively dividing the transport pipeline of a single 5G-speed time slot into 480 sub-slots. Each sub-slot has a bandwidth of 10Mbps (or slightly higher). Therefore, one sub-slot of a fine-grained frame can carry 10Mbps customer services, basically meeting the transport requirements of ordinary Ethernet services (currently, Ethernet service bandwidths are 10Mbps, 100Mbps, 1Gbps and above; services greater than 10Mbps use multiple sub-slots). In practical applications, when a fine-grained sub-slot carries a 10Mbps customer service, the 10Mbps customer service is first 64 / 66 encoded. After encoding, it is carried on a selection of sub-slots. The fine-grained frame is then mapped to FlexE protocol time slots and sent out, reaching the remote destination device through the 5G-speed time slots of the FlexE protocol.

[0076] In related technologies, to monitor the quality of service pipelines carrying customer services, an Operation, Administration, and Maintenance (OAM) function has been developed to detect the service quality status of the pipeline, such as bit error rate, latency, and service interruption. The implementation method is shown in Figure 8. OAM blocks (carrying maintenance information) are inserted into the transmitted customer message block stream. Thus, the OAM blocks and customer message blocks are carried and transmitted together, following the same transmission path. The service quality of the pipeline can be monitored through the information carried by the OAM blocks. For example, the sending end sends OAM blocks at fixed intervals. If the receiving end does not receive OAM blocks within multiple intervals, it determines that a service pipeline failure has caused a service interruption. Alternatively, the receiving end can measure the latency of the service pipeline by measuring the transmission time of the OAM blocks. Many similar OAM functions exist, which will not be described in detail here.

[0077] Typically, OAM code blocks can be periodically inserted into the customer code block stream, as shown in Figure 9. Device 1 inserts OAM code blocks into the customer message code block stream, and the OAM code blocks are transmitted together with the customer message code blocks through the network. The receiving device 6 detects the OAM code blocks. After detecting the OAM code blocks, the receiving end analyzes the content of the OAM code blocks, and the pipeline quality status can be monitored based on the analysis results.

[0078] Different types of values ​​carried in the OAM code block can enable various quality of service monitoring functions, such as bit error detection, connectivity monitoring, connection verification, remote bit error detection, remote fault detection, delay measurement, fast protection switching, customer signal failure detection, and customer signal type indication. In related technologies, the O code block format in the Ethernet standard is typically extended, and this extended format is used as the OAM code block format. In the Ethernet standard, the O code block is a control code block, as shown in Figure 10. The 2-bit synchronization header is "10", and the control word content is "0x4B". Bits 34-37 of the code block are the sequence values ​​of the O code block. Different sequence values ​​represent different meanings of the O code block content. The Ethernet standard uses four sequence values: 0x0, 0x1, 0x2, 0x5, and 0xF. China Mobile's enterprise standard uses the 0xC sequence value, and O code blocks with the 0xC sequence value are used as OAM code blocks. Figure 11 shows the OAM code block format defined by China Mobile's enterprise standard. An OAM code block uses a combination of a synchronization header "10", a control word "0x4B", and an O sequence value "0xC" as its identifier. A code block conforming to this identifier is an OAM code block. Bits 10 and 11 are reserved bits. Bits 12-17 are the OAM code block's type field, used for various types of OAM code blocks (such as base function OAM code blocks, APS function OAM code blocks, CS function OAM code blocks, 1DM function OAM code blocks, 2DM function OAM code blocks, etc., each type of function code block may consist of multiple sequence code blocks). Bits 18-33 and 42-57 are used to carry the OAM code block content. Bits 38-41 are reserved bits. Bits 58-61 are used to transmit the sequence numbers of multiple OAM code blocks. Bits 62-65 are used to transmit the CRC checksum, verifying the preceding content of the OAM code block. The quality of service (QoS) status of the network pipeline can be determined by inserting an OAM code block when the transmitting device sends the client code block, and by checking the OAM code block in the client service code block when the receiving device receives the data.

[0079] The above describes the existing fine-grained frames and OAM code blocks. However, these fine-grained frames are generally only applicable to the FlexE and 10GE interfaces (because the information code blocks of these interfaces are 66-bit long, thus suitable for the current 66-bit code block structure of the fine-grained bearer frame). For the GE interface, since the GE interface uses an 8b / 10b encoding structure, the encoded 10b code block is 10 bits long. Therefore, it is not possible to directly use the current fine-grained bearer frame composed of 66-bit long code blocks.

[0080] This application provides a bearer frame (which can be represented as a fine granularity unit (FGU), fine-granular bearer frame, small-granular bearer frame, small-granular frame, etc.) that can be used to carry fine-granular services of the GE interface. Based on this, this application also provides a transmission method that can transmit the bearer frame provided in this application. Furthermore, when transmitting the bearer frame, OAM information can also be transmitted concurrently. This OAM information can be carried by the bearer frame, transmitted between bearer frames, or combined with bearer frames before transmission. Thus, the receiving end can perform quality control on the service pipeline carrying customer services based on the OAM information.

[0081] To enable those skilled in the art to better understand the technical solutions in this application, the technical solutions in this application will be clearly and completely described below with reference to the accompanying drawings of one or more embodiments. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this application.

[0082] The terms "first," "second," etc., used in this application and the claims are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that this application can be implemented in orders other than those illustrated or described herein. Furthermore, in this application and the claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0083] The technical solutions provided by the various embodiments of this application are described in detail below with reference to the accompanying drawings.

[0084] Figure 12 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application. The bearer frame shown in Figure 12 consists of multiple bytes, including preamble bytes, overhead bytes, and time slot bytes, with the overhead bytes located between the preamble bytes and the time slot bytes. The preamble bytes are used to carry the preamble, and the number of bytes can be one or more (the specific number of bytes is not shown in Figure 12). The overhead bytes are used to carry service overhead information, and the number of bytes can be one or more (the specific number of bytes is not shown in Figure 12). The time slot bytes are used to carry service content, and the number of bytes is usually multiple (the specific number of bytes is not shown in Figure 12).

[0085] The bearer frame shown in Figure 12 can be encoded before being sent. For example, it can be transmitted to the physical coding sublayer (PCS) layer via an interface, and then encoded by the PCS layer before being sent. This interface can be a Media Independent Interface (MII) of the GE interface. Transmission to the PCS layer via the interface can be via the MII bus. The encoding of the PCS layer can be 10-bit encoding.

[0086] Since the GE interface uses an 8b / 10b encoding structure, and the bearer frame shown in Figure 12 consists of multiple bytes, each byte containing 8 bits, the bearer frame shown in Figure 12 can be used to carry fine-grained services on the GE interface, thus meeting the requirements for carrying fine-grained services on the GE interface.

[0087] Optionally, in some embodiments, the bearer frame shown in FIG12 may further include a frame delimiter byte, which is used to carry a frame delimiter, as shown in FIG13. In addition to the preamble byte, overhead byte, and time slot byte, the bearer frame shown in FIG13 also includes a frame delimiter byte, which is located between the preamble byte and the overhead byte. The number of the frame delimiter byte can be one or more (the specific number of bytes is not shown in FIG13).

[0088] The bearer frame shown in Figure 13 can be encoded before being sent. For example, it can be transmitted to the PCS layer via an interface, and then encoded by the PCS layer before being sent. This interface can be the MII interface of the GE interface. Transmission to the PCS layer via the interface can also be via the MII bus. The encoding by the PCS layer can be 10-bit encoding.

[0089] Since the GE interface uses an 8b / 10b encoding structure, and the bearer frame shown in Figure 13 consists of multiple bytes, each byte containing 8 bits, the bearer frame shown in Figure 13 can be used to carry fine-grained services on the GE interface, thus meeting the requirements for carrying fine-grained services on the GE interface.

[0090] The following will use some more specific implementation examples to further illustrate the carrier frames shown in Figures 12 and 13.

[0091] In some implementations, the bearer frame shown in Figure 13 may consist of 1575 bytes, including 7 preamble bytes, 1 frame delimiter byte, 7 overhead bytes, and 1560 time slot bytes, which are divided into 24 time slots, as shown in Figure 14.

[0092] The bearer frame shown in Figure 14 includes 7 preamble bytes (0x55), 1 frame delimiter byte (0xD5), 7 overhead bytes (OH), and 1560 time slot bytes. These 1560 time slot bytes constitute the bearer area of ​​the bearer frame, which can be divided into 24 time slots. In some implementations, when transmitting bearer frames, 4 bearer frames can be combined into a multiframe, with each multiframe containing 96 time slots. Thus, when using multiframes to carry fine-grained services on the GE interface, the fine-grained bearer of the GE interface is divided into 96 time slots, with each time slot still having a bandwidth of 10 Mbps.

[0093] In related technologies, when transmitting fine-grained bearer frames of the FlexE interface, a free block is placed between frames. A free block is 8 bytes, plus the T7 control field bytes of the fine-grained bearer frame, totaling 9 bytes. Similarly, in this embodiment, multiple bytes can be placed between bearer frames during transmission. Optionally, to ensure that the ratio of valid to invalid bytes transmitted when transmitting the bearer frames in this embodiment is the same as the ratio of valid to invalid bytes transmitted when currently transmitting fine-grained bearer frames of the FlexE interface, this embodiment can place a 9-byte gap between adjacent bearer frames when transmitting multiple bearer frames.

[0094] Figure 15 is a schematic diagram of message transmission via the MII interface bus according to an embodiment of this application. In Figure 15, after each transmission of 1575 bytes of bearer, there is a 9-byte interval before transmitting another 1575-byte bearer frame, followed by another 9-byte interval, and so on, repeating sequentially (4 frames constitute one multiframe). The MII bus consists of a clock signal clock, an enable signal tx_en, and an 8-bit data signal txd. The enable signal tx_en is high when valid data is transmitted, and low when idle. The 8-bit data bus txd contains the transmitted valid data content.

[0095] In related technologies, to perform quality control on the service pipeline carrying customer services, the sending end can also transmit OAM code blocks when transmitting the bearer frame of the FlexE interface. The OAM code block carries OAM information, and the receiving end can perform quality control on the service pipeline carrying customer services based on the OAM code block. In this embodiment, to perform quality control on the service pipeline carrying customer services, OAM information can also be transmitted when transmitting the bearer frame to implement the OAM function. However, the OAM code block in related technologies consists of 66 bits, while the GE interface uses an 8b / 10b encoding structure. Therefore, when transmitting OAM information, it is impossible to carry the OAM information in the OAM code block and send it to the receiving end. In view of this, this embodiment provides a transmission method that can transmit OAM information in byte-by-byte format.

[0096] Figure 16 is a schematic diagram of OAM information according to an embodiment of this application. In Figure 16, the first byte (bits 2-9) and the fifth byte (bits 34-41) of the OAM code block are used to identify that the code block is an OAM code block (to distinguish it from the customer service code block), and do not contain specific OAM functional content. The second, third, and fourth bytes (bits 10-33) and the sixth, seventh, and eighth bytes (bits 42-65) of the OAM code block carry the OAM information content, which can be represented as the OAM_1 field and the OAM_2 field, respectively. Each field has 3 bytes, for a total of 6 bytes of OAM information content.

[0097] As can be seen, when implementing the OAM function, it is only necessary to carry and transmit the OAM_1 and OAM_2 fields along with the customer service to the receiving end to achieve the purpose. Therefore, in some implementations of this embodiment, when transmitting OAM information, only the two valid fields OAM_1 and OAM_2 shown in Figure 16, totaling 6 bytes, can be transmitted. That is to say, the OAM information transmitted in this embodiment may include the content of the second, third, fourth, sixth, seventh, and eighth bytes of the first OAM code block. This first OAM code block is an OAM code block under a first standard, which is the China Mobile enterprise standard (hereinafter referred to as the Chinese standard). The first OAM code block is the OAM code block shown in Figure 16.

[0098] It should be noted that in the actual implementation, for each byte in the OAM_1 and OAM_2 fields shown in Figure 16, only a portion of the 8 bits in the byte may be used to carry the OAM information content. When implementing the OAM function, it is only necessary to extract the bits carrying the OAM information content from the OAM_1 and OAM_2 fields to form n bytes (n is 1, 2, 3, 4, or 5), and transmit these n bytes along with the customer's service to the receiving end to achieve the purpose. For example, OAM information such as Bit-Interleaved-Parity (BIP), Remote Error Indicator (REI), and Remote Default Indicator (RDI) can be extracted and transmitted. In view of this, in some implementations of this embodiment, when transmitting OAM information, the OAM information may include the content obtained by compressing the second, third, fourth, sixth, seventh, and eighth bytes of the first OAM code block. This content is n bytes (n is 1, 2, 3, 4, or 5) obtained by combining the bits used to carry OAM information in the OAM_1 and OAM_2 fields shown in Figure 16, as shown in Figure 17. The first OAM code block is an OAM code block under a first standard, which is the Chinese standard, and the first OAM code block is the OAM code block shown in Figure 16.

[0099] In the case where the bearer frame shown in Figure 14 and the OAM information are transmitted together to the receiving end, in some embodiments, the OAM information can be transmitted between two adjacent bearer frames. Specifically, the OAM information is carried by one or more bytes, and when transmitting OAM information between two adjacent bearer frames, it can be that one or more bytes used to carry the OAM information are transmitted between the two bearer frames.

[0100] In practical implementation, when transmitting OAM information between two adjacent bearer frames, there may be two scenarios: one where the number of bytes between the two bearer frames is sufficient to transmit all bytes of OAM information at once, and another where it is insufficient. For example, assuming there is a 9-byte interval between two bearer frames (i.e., 9 bytes of free space), after each bearer frame transmission, 2 or 3 bytes need to be reserved to transmit the end flag of the bearer frame, leaving only 6 or 7 bytes of available free space. If the OAM information has 6 bytes of content (such as the 6 bytes of OAM_1 and OAM_2 fields shown in Figure 16), then when transmitting the 6 bytes of OAM information, 1 byte is needed to represent the start flag (S byte or S code), and 2 or 3 bytes are needed for the end flag. Thus, transmitting the 6 bytes of OAM information requires a total of 9 or 10 bytes. Obviously, the remaining free space (6 or 7 bytes in total) between two adjacent bearer frames is insufficient to transmit the 6 bytes of OAM information at once. If the OAM information has 1 or 2 bytes of content (such as the 1 or 2 bytes obtained after extracting and compressing the 6 bytes of OAM_1 and OAM_2 fields as shown in Figure 17), then when sending 1 or 2 bytes of OAM information, 1 byte is needed to represent the start flag (S byte or S code) and 2 or 3 bytes are needed for the end flag. In this way, sending 1 or 2 bytes of OAM information will occupy a total of 4-6 bytes. Obviously, the remaining free space (6 or 7 bytes in total) between two adjacent bearer frames can be used to send all 6 bytes of OAM information at once.

[0101] If the number of bytes between two bearer frames is sufficient to transmit all bytes of OAM information in one go, then the entire OAM information can be transmitted between the two bearer frames in one transmission. For example, with a 9-byte interval between bearer frames and OAM information consisting of 2 bytes, the transmission of OAM information between bearer frames can be as shown in Figure 18.

[0102] When the number of bytes between two bearer frames is insufficient to transmit all bytes of OAM information at once, to avoid the inability to implement OAM functionality due to the inability to transmit all bytes of OAM information between two bearer frames, some implementations can transmit partial bytes of OAM information between adjacent bearer frames, with the full bytes of OAM information transmitted in multiple transmissions. For example, if the full bytes of OAM information are 6 bytes, the 6 bytes can be divided into two groups and transmitted in two separate transmissions, with each group containing 3 bytes. Alternatively, the 6 bytes can be divided into three groups and transmitted in three separate transmissions, with each group containing 2 bytes. Yet another example is that the 6 bytes can be divided into four groups and transmitted in four separate transmissions, with the first two groups containing 2 bytes each and the last two groups containing 1 byte each. No specific limitations are made regarding how the full bytes of OAM information are transmitted in multiple transmissions. In the case of transmitting all bytes of OAM information in multiple transmissions, each transmitted byte can be located between specified bearer frames. That is, partial bytes of OAM information can be transmitted between specified bearer frames (for example, half of the OAM information can be transmitted after the first and second frames of a multiframe). In this way, when the receiving end receives the data, it can combine the byte content between the specified bearer frames to recover the complete OAM information content.

[0103] Taking a 9-byte interval between bearer frames, dividing the OAM information into two groups of 3 bytes each for transmission in two separate transmissions, as an example, the transmission of bearer frames and OAM information can be as shown in Figure 19. Figure 19 divides the 6 bytes of OAM information into two groups of 3 bytes each. These two groups can be the OAM_1 field and OAM_2 field shown in Figure 16. When transmitting the OAM_1 and OAM_2 fields, a start byte (S byte, content 0x55) can be added before the 3 bytes of the OAM_1 field to represent the start flag, forming the 4-byte field content S+OAM_1. Only the S+OAM_1 field content is sent between the two bearer frames. Adding the end flag, only a minimum of 6 bytes are needed, allowing transmission between bearer frames (leaving 6 or 7 bytes of free space between bearer frames). Similarly, a start byte S (content 0x55) is added before the 3 bytes of the OAM_2 field to form the 4-byte field S+OAM_2, which is then sent between bearer frames.

[0104] As shown in Figure 19, the transmitting end sends the OAM information in two parts: the OAM_1 field and the OAM_2 field. During transmission, the transmitting end can send the S+OAM_1 field and the S+OAM_2 field sequentially between two consecutive bearer frame intervals. The receiving end can determine whether the received information is bearer frame content (bearer frame length is much greater than 4 bytes) or OAM information content (4 bytes long) based on the length of the received information. Furthermore, for OAM information content, combining two consecutive OAM information pieces constitutes the complete OAM information content. When OAM information content exists between multiple consecutive bearer frame intervals, it is necessary to determine which two consecutive OAM information pieces to combine. For example, if the consecutive OAM information fields are A, B, C, D, E..., should A and B be combined, or C and D, or B and C, or D and E? In some implementations, the transmitting and receiving ends can pre-agree on a certain pattern. For example, a multiframe is composed of four bearer frames. The transmitting and receiving ends can agree to combine the OAM information fields after the first frame and the second frame, and the OAM information fields after the third frame and the fourth frame, as shown in Figure 19. In this way, the transmitting end can send the OAM_1 and OAM_2 functional information fields according to the agreed-upon pattern. The receiving end can determine the OAM information fields based on the received length and combine the OAM_1 and OAM_2 fields according to the agreed-upon pattern to recover the complete OAM information content.

[0105] The above examples illustrate that when transmitting OAM information, the transmission method can be to transmit part or all of the OAM information bytes between bearer frames, that is, to transmit all the OAM information bytes in one or multiple transmissions. In some implementations, the OAM information can also be transmitted by combining all the OAM information bytes with the bearer frame, that is, sending the entire OAM information content together with the bearer frame. This eliminates the need for the additional start flag S byte and end flags T, R, etc., required when transmitting OAM information separately, and allows the entire OAM information content to be sent at once. Specifically, when the entire OAM information bytes are combined with the bearer frame for transmission, the combined byte count is 1575 + n bytes, where n bytes are used to carry the OAM information, and n can be 1, 2, 3, 4, 5, 6, 7, or 8.

[0106] There are several ways to combine all the bytes of the OAM information with the bearer frame. In some implementations, the combination of all the bytes of the OAM information with the bearer frame may include any of the following:

[0107] All bytes of the OAM information are located after the timeslot bytes of the bearer frame; all bytes of the OAM information are located between the overhead bytes and timeslot bytes of the bearer frame; all bytes of the OAM information are located between the frame delimiter bytes and overhead bytes of the bearer frame; all bytes of the OAM information are located between the preamble bytes and frame delimiter bytes of the bearer frame.

[0108] Please refer to Figure 20. Figure 20 shows three ways (Method 1, Method 2, and Method 3) to combine all bytes of the OAM information with the bearer frame shown in Figure 14. Method 1 places all bytes of the OAM information at the end of the bearer frame, i.e., after the timeslot bytes of the bearer frame. Method 2 places all bytes of the OAM information between the frame delimiter 0xD5 byte and the overhead OH byte of the bearer frame. Method 3 places the OAM information between the overhead OH byte and the timeslot bytes of the bearer frame. The value of n can be 1, 2, 3, 4, 5, 6, 7, or 8.

[0109] As shown in Figure 20, in methods 1, 2, and 3, when OAM information needs to be sent, all bytes of the OAM information and the content of the carrier frame are combined and sent together. In this case, the length of the carrier frame is 1575+n bytes (including the original 1575 bytes of the carrier frame and n bytes of the OAM information, where n can be 1, 2, 3, 4, 5, 6, 7, or 8). When OAM information does not need to be sent, only the content of the carrier frame is sent, and the length of the carrier frame is the original 1575 bytes. At the receiving end, as shown in Figure 21, for methods 1, 2, and 3, when the length of the received bearer frame is not the expected original bearer frame length (1575 bytes), but rather the sum of the expected length (1575 bytes) and n bytes of OAM information, it indicates that OAM information is appended to the bearer frame. In this case, the receiving end can extract the OAM information bytes from the received new length field according to the combination method of the bearer frame bytes and all bytes of OAM information (the sending and receiving ends can pre-agree on the combination method of the bearer frame and OAM information bytes). The remaining content is the content of the bearer frame. In this way, the receiving end can recover the original bearer frame and OAM information from the received field.

[0110] It should be noted that the above explanation uses the example of combining all bytes of the OAM field with the bearer frame for transmission. In some possible implementations, only a portion of the OAM information can be combined with the bearer frame for transmission. The entire OAM information can be combined with multiple bearer frames and transmitted in multiple batches. This eliminates the need for the additional start flag (S byte) and end flags (T, R, etc.) required when transmitting OAM information separately. However, considering that this transmission method typically increases the difficulty of parsing and recognizing OAM information at the receiving end in practical applications, this method is not recommended. Instead, the method of combining all bytes of the OAM field with the bearer frame for transmission is preferred.

[0111] The above example illustrates that the bearer frame can be combined with all bytes of OAM information before transmission. In this case, when OAM information needs to be sent, all bytes of the OAM information and the bearer frame content are combined and sent together (increasing the length); when OAM information is not needed, only the bearer frame content (original length) is sent. The receiving end can analyze whether the received bearer frame carries OAM information based on the length changes of the received content. In some implementations, the bearer frame may also include a fixed number of OAM bytes, which are used to carry OAM information. When OAM information needs to be sent, the OAM bytes can carry the OAM information; when OAM information is not needed, the OAM bytes can be a default value or idle content. The number of OAM bytes can be 1, 2, 3, 4, 5, 6, 7, or 8.

[0112] When the bearer frame includes OAM bytes, the position of the OAM bytes within the bearer frame can vary. In some implementations, the position of the OAM bytes within the bearer frame can include any of the following: the OAM bytes are located after the timeslot bytes of the bearer frame; the OAM bytes are located between the overhead bytes and the timeslot bytes of the bearer frame; the OAM bytes are located between the frame delimiter bytes and the overhead bytes of the bearer frame; or the OAM bytes are located between the preamble bytes and the frame delimiter bytes of the bearer frame.

[0113] When using OAM bytes to carry OAM information, in some implementations, the OAM byte can carry the entire content of the OAM information. In other implementations, the OAM byte can also carry a portion of the OAM information, with the entire content of the OAM information carried across multiple carrier frames' OAM bytes. Specifically, when the OAM byte carries part or all of the OAM information, if the number of OAM bytes exceeds the actual number of bytes of OAM information carried, the remaining OAM bytes can carry a default value (e.g., 0 or 1). For example, if the OAM information consists of 2 bytes, and the OAM byte includes 3 bytes, then 2 OAM bytes can carry the 2 bytes of OAM information. After one frame carries the entire OAM information, the remaining OAM byte can carry the default value. As another example, if the OAM information consists of 6 bytes, and the OAM byte includes 4 bytes, then 3 OAM bytes can carry half of the OAM information (the other half is carried in another carrier frame), and the remaining OAM byte carries the default value.

[0114] Please refer to Figure 22. The bearer frame shown in Figure 22 includes n OAM bytes in addition to the bearer frame shown in Figure 14. n can be a natural number such as 1, 2, 3, 4, 5, 6, 7, or 8. Assuming n equals 6, the OAM information consists of 6 bytes, meaning one frame can carry the entire OAM information when transmission is needed. Assuming n equals 2, the OAM information consists of 2 bytes, again meaning one frame can carry the entire OAM information when transmission is needed. Assuming n equals 3, the OAM information consists of 6 bytes, meaning one frame cannot carry the entire OAM information when transmission is needed; it needs to be carried in multiple bearer frames, with each frame carrying a portion of the OAM information. When OAM information is not needed, the content at the OAM byte position can be an invalid value (a fixed default value, such as all 0s or all 1s).

[0115] As shown in Figure 22, the length of the bearer frame is the same whether or not OAM information is transmitted. For the receiver, the presence or absence of OAM information in the bearer frame can be determined by checking if the content carried by the OAM bytes is the default value. Furthermore, a bearer frame can carry the entire OAM information or only a portion of it. For example, if the OAM information is 6 bytes, each frame can carry less than 6 bytes of OAM information, with multiple frames carrying the entire OAM information. In this case, the receiver can combine the partial OAM information from each frame to recover the complete OAM information. For instance, as shown in Figure 23, four bearer frames form a multiframe. If each frame carries 2 bytes of OAM information, then a multiframe carries a total of 8 bytes of OAM information, which is sufficient to carry the entire OAM information. The receiver can then combine the OAM bytes from the multiframe to recover the complete OAM information.

[0116] The bearer frame shown in Figure 14 includes 7 preamble bytes (0x55) and 1 frame delimiter byte (0xD5). Since the preamble byte content is a fixed value of 0x55, in some implementations, when transmitting OAM information, the OAM information can be placed in the preamble byte position of the bearer frame, with the preamble byte carrying the OAM information. When the sending end needs to send OAM information, the content of the OAM information can be placed in the preamble position and sent; when OAM information does not need to be sent, the original preamble byte 0x55 can be sent.

[0117] When OAM information is carried by preamble bytes, it can be carried in the last 6 bytes of the preamble bytes. Specifically, it can carry the entire content of the OAM information or a portion of it. The exact position of the preamble bytes occupied by the OAM information is not specifically limited. For example, if the OAM information is 6 bytes long, it can occupy the last 6 bytes of the preamble bytes. Alternatively, the 6 bytes of OAM information can be carried in the preamble bytes of two carrier frames, with the last three preamble bytes of each carrier frame carrying half of the OAM information. As another example, if the OAM information is 2 bytes long, it can occupy the first 2 bytes, the middle 2 bytes, or the last 2 bytes of the last 6 bytes of the preamble bytes. Here, the exact position of the preamble bytes occupied by the OAM information is not specifically limited.

[0118] Please refer to Figure 24. In Figure 24, OAM information can be carried in the last 6 bytes of the 7 preamble bytes (these 6 bytes do not necessarily all carry OAM information), and a frame can carry part or all of the OAM information. Regardless of whether the preamble bytes in the carrying frame carry OAM information, the length of the carrying frame does not change, and there can be a 9-byte interval between two adjacent carrying frames.

[0119] When OAM information is carried by the preamble byte in the bearer frame, for the receiver, if the received byte content of the preamble portion of the bearer frame is not 0x55, it indicates that the content carried at that position is OAM information. In this case, the receiver can extract the OAM information byte content at the corresponding position according to the bearer method of the sender (which can be agreed upon in advance by the sender and receiver), and then reset the content at that position to the preamble byte content of 0x55, thus restoring the original bearer frame structure. This method determines whether OAM information is carried by analyzing whether the preamble position is the original preamble content (0x55).

[0120] The bearer frame shown in Figure 14 includes 7 preamble bytes (0x55) and 1 frame delimiter byte (0xD5). Since these bytes contain fixed content, they do not need to be transmitted during transmission. This allows for a redefinition of the GE interface bearer frame. Specifically, in some implementations, the bearer frame can consist of 1 preamble byte, 7 overhead bytes, and 1560 time slot bytes, totaling 1568 bytes (a specific implementation of the bearer frame shown in Figure 12, which reduces 6 0x55 bytes and one 0xD5 byte compared to the bearer frame shown in Figure 14).

[0121] Please refer to Figure 25. The bearer frame shown in Figure 25 includes one preamble byte (0x55), seven overhead bytes (OH), and 1560 time slot bytes. These 1560 time slot bytes constitute the bearer area of ​​the bearer frame, which can be divided into 24 time slots. In some implementations, when transmitting bearer frames, four bearer frames can be combined into a multiframe, with each multiframe containing 96 time slots. Thus, when using multiframes to carry fine-grained services on the GE interface, the fine-grained bearer of the GE interface is divided into 96 time slots, with each time slot still having a bandwidth of 10 Mbps.

[0122] When transmitting bearer frames, there can be a gap of multiple bytes between frames. In some implementations, there can be a gap of 16 bytes between two adjacent bearer frames (an increase of 7 bytes from the 9-byte gap shown in Figure 14, which is a reduction of 7 bytes compared to the bearer frame shown in Figure 14). That is, when transmitting bearer frames, after sending every 1568 bytes of bearer frames, there can be a 16-byte gap, then another 1568-byte bearer frame is sent, then another 16-byte gap is sent, and so on, repeating in this manner (4 frames make up a multiframe).

[0123] For the bearer frame shown in Figure 25, the transmitting end can also send the bearer frame along with OAM information to the receiving end when sending it. In some embodiments, the OAM information can be 6 bytes of OAM information composed of the OAM_1 field and the OAM_2 field shown in Figure 16. In other embodiments, the OAM information can also be n bytes of OAM information obtained by compressing the 6 bytes of OAM information as shown in Figure 17, where n can be 1, 2, 3, 4, or 5.

[0124] When transmitting the bearer frame shown in Figure 25 and the OAM information together to the receiving end, in some embodiments, the OAM information can be transmitted between two adjacent bearer frames. Specifically, the OAM information is carried by bytes, and transmitting it between two adjacent bearer frames can involve transmitting bytes used to carry the OAM information between the two bearer frames.

[0125] For the bearer frame shown in Figure 25, when transmitting OAM information between two adjacent bearer frames, since there can be a 16-byte interval between the two adjacent bearer frames, and the maximum length of the entire OAM information is 6 bytes (the OAM information shown in Figure 16 is 6 bytes, and the OAM information shown in Figure 17 is n bytes, where n can be 1, 2, 3, 4, or 5), plus the 2 or 3 bytes reserved for the end flag after sending the bearer frame, the 1 byte added to indicate the start flag (S byte or S code) when sending the OAM information, and the 2 or 3 bytes for the end flag, the maximum length is 13 bytes. Therefore, all bytes of the OAM information can be transmitted between the two bearer frames in one go. In other words, when transmitting OAM information between two adjacent bearer frames, the specific transmission method of the OAM information can be to transmit all bytes of the OAM information between the two bearer frames. Of course, in some possible implementations, partial bytes of OAM information can be transmitted between two bearer frames, while all bytes of OAM information are transmitted between multiple bearer frames. However, considering that this transmission method would increase the difficulty of parsing and recognizing OAM information at the receiving end, this transmission method is not recommended. Instead, it is preferable to transmit all bytes of OAM information between two bearer frames.

[0126] Figure 26 is a schematic diagram of OAM information transmission between the bearer frames shown in Figure 25. As shown in Figure 26, all bytes of the OAM information can be transmitted in one go during the idle period between two adjacent bearer frames, where n can be equal to 2, 3, 4, 5, 6, or 7 (1 start flag byte and 1-6 bytes of OAM information). For the receiving end, the length of the received information can determine whether the received information is the bearer frame content (bearer frame length is much greater than 4 bytes) or the OAM information content (4 bytes).

[0127] In some implementations, when transmitting the bearer frame and OAM information shown in Figure 25, the OAM information can also be transmitted by combining all bytes of the OAM information with the bearer frame. This eliminates the need for additional start flag S bytes and end flags T, R, etc., required when transmitting OAM information separately, and allows the entire OAM information to be transmitted at once. Specifically, when all bytes of the OAM information are combined with the bearer frame, the combined number of bytes is 1568 + n bytes, where n bytes are used to carry the OAM information, and n can be 1, 2, 3, 4, 5, 6, 7, or 8.

[0128] There are several ways to combine all the bytes of the OAM information with the bearer frame. In some implementations, the combination of all the bytes of the OAM information with the bearer frame may include any of the following: all the bytes of the OAM information are located after the timeslot bytes of the bearer frame; all the bytes of the OAM information are located between the overhead bytes and the timeslot bytes of the bearer frame; all the bytes of the OAM information are located between the preamble bytes and the overhead bytes of the bearer frame.

[0129] Please refer to Figure 27. In Figure 27, when combining the bearer frame and OAM information shown in Figure 25, all bytes of the OAM information are placed after the bearer frame, that is, all bytes of the OAM information are located after the timeslot bytes of the bearer frame. The value of n can be 1, 2, 3, 4, 5, 6, 7, or 8. When OAM information needs to be sent, all bytes of the OAM information and the bearer frame can be combined and sent together. When OAM information does not need to be sent, only the content of the bearer frame can be sent. For the receiving end, when the length of the received bearer frame is not the expected original bearer frame length (1568 bytes), but the sum of the expected length (1568 bytes) and the length of n bytes of the OAM information, it means that OAM information is appended to the bearer frame. At this time, the receiving end can extract the OAM information byte content from the received new length field according to the combination method of the bearer frame bytes and all bytes of the OAM information by the sending end (the sending end and the receiving end can agree on the combination method of the bearer frame and OAM information in advance). The remaining content is the content of the bearer frame. In this way, the receiving end can recover the original bearer frame and OAM information from the received fields.

[0130] It should be noted that the above explanation uses the example of combining all bytes of the OAM information with the bearer frame for transmission. In some possible implementations, only a portion of the OAM information can be combined with the bearer frame for transmission. The entire OAM information can be combined with multiple bearer frames in multiple transmissions. This eliminates the need for the additional start flag (S byte) and end flags (T, R, etc.) required when transmitting OAM information separately. However, considering that this transmission method typically increases the difficulty of parsing and recognizing the OAM information at the receiving end in practical applications, this method is not recommended. Instead, the method of combining all bytes of the OAM information with the bearer frame for transmission is preferred.

[0131] In some implementations, when transmitting the bearer frame and OAM information shown in Figure 25, the OAM information can also be transmitted by including OAM bytes in the bearer frame, with the OAM bytes carrying the OAM information. The number of OAM bytes is n, and n can be 1, 2, 3, 4, 5, 6, 7, or 8. When OAM information needs to be sent, the OAM bytes can carry the OAM information; when OAM information does not need to be sent, the OAM bytes can be a default value or idle content.

[0132] When the bearer frame includes OAM bytes, the position of the OAM bytes within the bearer frame can vary. In some implementations, the position of the OAM bytes within the bearer frame can include any of the following: the OAM bytes are located after the timeslot bytes of the bearer frame; the OAM bytes are located between the overhead bytes and the timeslot bytes of the bearer frame; or the OAM bytes are located between the preamble bytes and the overhead bytes of the bearer frame.

[0133] When using OAM bytes to carry OAM information, in some implementations, the OAM byte can carry the entire content of the OAM information. In other implementations, the OAM byte can also carry a portion of the OAM information, with the entire content of the OAM information carried across multiple carrier frames' OAM bytes. Specifically, when the OAM byte carries part or all of the OAM information, if the number of OAM bytes exceeds the actual number of bytes of OAM information carried, the remaining OAM bytes can carry a default value (e.g., 0 or 1). For example, if the OAM information consists of 2 bytes, and the OAM byte includes 3 bytes, then 2 OAM bytes can carry the 2 bytes of OAM information. After one frame carries the entire OAM information, the remaining OAM byte can carry the default value. As another example, if the OAM information consists of 6 bytes, and the OAM byte includes 4 bytes, then 3 OAM bytes can carry half of the OAM information (the other half is carried in another carrier frame), and the remaining OAM byte carries the default value.

[0134] Please refer to Figure 28. The bearer frame shown in Figure 28, in addition to the bearer frame shown in Figure 25, includes n fixed OAM bytes, where n can be a natural number such as 1, 2, 3, 4, 5, 6, 7, or 8. Assuming n equals 6, the OAM information consists of 6 bytes, meaning one frame can carry the entire OAM information when transmission is required. Assuming n equals 2, the OAM information consists of 2 bytes, again meaning one frame can carry the entire OAM information when transmission is required. Assuming n equals 3, the OAM information consists of 6 bytes, meaning one frame cannot carry the entire OAM information when transmission is required; it needs to be carried in multiple bearer frames, with each frame carrying a portion of the OAM information. When OAM information is not needed, the content at the OAM byte position can be an invalid value (a fixed default value, such as all 0s or all 1s). For the receiving end, whether a bearer frame carries OAM information can be determined by checking whether the content carried by the OAM bytes in the bearer frame is a default value. For example, if the OAM byte in the bearer frame does not carry a fixed default value, then the OAM byte is determined to carry valid OAM information; otherwise, it is determined to carry invalid OAM information. Furthermore, the bearer frame can carry the entire OAM information, or it can carry only a portion of the OAM information. When carrying only a portion of the OAM information, the receiving end can combine the portions from each frame to reconstruct the complete OAM information.

[0135] The embodiments shown in Figures 14 to 28 above are fine-grained bearer frame schemes for the GE interface based on the fine-grained bearer frame scheme of the FlexE interface in the Chinese standard. The International Telecommunication Union (ITU) has also formulated a fine-grained frame structure for the FlexE interface. Under the international standard, a fine-grained bearer frame consists of one S-block, 990 D-blocks, and one T-block. The D-block of a fine-grained bearer frame is divided into overhead bytes and 480 sub-slots. The bearer frame contains a 7-byte overhead field and a 7920-byte slot area, divided into 480 slots, each slot being two 66-bit segments with a bandwidth of 10 Mbps. For the GE interface, since the GE interface rate is one-fifth of the 5G rate, dividing the GE interface into 10 Mbps sub-slots results in 96 sub-slots (one-fifth of 480). Therefore, for the GE interface, the current fine-grained bearer frame structure under the international standard can be shown in Figure 29, and the corresponding unfolded diagram can be shown in Figure 30. The bearer frame shown in Figure 30 consists of one S-block, 198 D-blocks, and one T-block, including a 7-byte overhead field and a 1584-byte time slot area. The time slot area is divided into 96 time slots, each with a length of two 66-bit segments and a bandwidth of 10 MHz. For fine-grained bearer frames under the international standard, an idle block (or OAM block) is also used between fine-grained bearer frames during transmission. The international standard OAM block is also an extension of the O block, similar to the Chinese standard OAM block, but only three byte positions (bits 10-33) in the O block are used to transmit OAM information, as shown in Figure 31. The effective number of OAM information bytes is only 3 bytes.

[0136] For international standards, in some implementations, the bearer frame provided in this application embodiment can consist of 1599 bytes, including 7 preamble bytes, 1 frame delimiter byte, 7 overhead bytes, and 1584 time slot bytes. These 1584 time slot bytes are divided into 96 time slots, as shown in Figure 32. The bearer frame shown in Figure 32 includes 7 preamble bytes (0x55), 1 frame delimiter byte (0xD5), 7 overhead bytes (OH), and 1584 time slot bytes. These 1584 time slot bytes constitute the bearer area of ​​the bearer frame and can be divided into 96 time slots.

[0137] In related technologies, for international standards, when transmitting fine-grained bearer frames, a free block is placed between frames. A free block is 8 bytes, plus the T7 control field bytes of the fine-grained bearer frame, totaling 9 bytes. Similarly, in this embodiment, multiple bytes can be placed between bearer frames during transmission. Optionally, to ensure that the ratio of valid to invalid bytes transmitted when transmitting the bearer frames in this embodiment is the same as the ratio of valid to invalid bytes transmitted when transmitting fine-grained bearer frames under the current international standard, this embodiment can place a 9-byte gap between adjacent bearer frames when transmitting multiple bearer frames.

[0138] In related technologies, to perform quality control on the service pipeline carrying customer services, the transmitting end can also transmit OAM code blocks when transmitting fine-grained bearer frames. The OAM code blocks carry OAM information, and the receiving end can perform quality control on the service pipeline carrying customer services based on the OAM code blocks. In this embodiment, to perform quality control on the service pipeline carrying customer services, OAM information can also be transmitted when transmitting bearer frames to implement the OAM function.

[0139] As shown in Figure 31, under the international standard, the effective number of OAM information bytes is only 3 bytes. When implementing the OAM function, it is sufficient to carry these 3 bytes along with the customer service to the receiving end to achieve the purpose. Therefore, in some embodiments, when transmitting OAM information, only the 3 effective bytes shown in Figure 29 may be transmitted. That is to say, the OAM information transmitted in this embodiment includes the contents of the second, third, and fourth bytes of the second OAM code block. This second OAM code block is an OAM code block under the second standard, which is an international standard. The second OAM code block is the OAM code block shown in Figure 31.

[0140] It should be noted that in specific implementations, for each valid byte of OAM shown in Figure 31, only a portion of the 8 bits of the byte may carry the valid content of OAM information. When implementing the OAM function, it is only necessary to extract the bits carrying the OAM information content from these 3 valid bytes of OAM to form n (n is 1 or 2) bytes, and then transmit these n bytes along with the customer service to the receiving end to achieve the desired result. Therefore, in some implementations of this embodiment, when transmitting OAM information, the OAM information may include the content obtained by compressing the second, third, and fourth bytes of the second OAM code block. This content is n bytes (n is 1 or 2) obtained by combining the bits used to carry the OAM information content in the valid bytes of OAM shown in Figure 31, as shown in Figure 33. The second OAM code block is the OAM code block under the second standard, which is an international standard, and the second OAM code block is the OAM code block shown in Figure 31.

[0141] In the case where the bearer frame shown in Figure 32 and the OAM information are transmitted together to the receiving end, in some embodiments, the OAM information can be transmitted between two adjacent bearer frames. Specifically, the OAM information is carried by bytes, and when transmitting OAM information between two adjacent bearer frames, it can be that bytes used to carry the OAM information are transmitted between the two bearer frames.

[0142] For the bearer frame shown in Figure 32, when transmitting OAM information between two adjacent bearer frames, since the total number of bytes of OAM information is at most 3 bytes (the OAM information shown in Figure 31 is a 3-byte OAM valid field, and the OAM information shown in Figure 33 is 1 or 2 bytes obtained after compressing the OAM valid field), plus the 1 byte needed to represent the start flag (S byte or S code) when sending OAM information, a total of 4 bytes, can generally be transmitted in one go during the idle period between two bearer frames. Therefore, in some implementations, when transmitting OAM information between two adjacent bearer frames, the specific transmission method of OAM information can be to transmit all bytes of OAM information between the two bearer frames. Of course, in some possible implementations, partial bytes of OAM information can also be transmitted between two bearer frames, with the total number of bytes of OAM information transmitted between multiple bearer frames. Considering that this transmission method increases the difficulty of parsing and recognizing OAM information at the receiving end, this transmission method is not recommended. Instead, it is preferable to transmit the total number of bytes of OAM information between two bearer frames.

[0143] Taking a 9-byte interval between bearer frames as an example, the transmission of bearer frames and OAM information can be as shown in Figure 34. In Figure 34, a start flag byte S is added before all bytes (1, 2, or 3 bytes) of the OAM information to form an n-byte field of S+OAM (n can be 2, 3, or 4 bytes), which is transmitted in one go between bearer frames. When OAM information is not needed, after sending 1599 bytes of bearer frame content, the next bearer frame content is sent after a 9-byte idle period. When OAM information is needed, the n-byte content of S+OAM can be sent during the idle period between bearer frames. For the receiving end, the length of the received information can be used to determine whether the received information is bearer frame content (the bearer frame length is much larger than the S+OAM byte length) or OAM information content (the S+OAM byte length).

[0144] In some implementations, when transmitting the bearer frame and OAM information shown in Figure 32, the OAM information can also be transmitted by combining all bytes of the OAM information with the bearer frame, that is, combining 1, 2, or 3 bytes of OAM information with the bearer frame and sending them together. This eliminates the need for the additional start flag S bytes required when transmitting OAM information separately. Specifically, when all bytes of the OAM information are combined with the bearer frame, the total number of bytes after combination is 1599 + n bytes, where n bytes are used to carry the OAM information, and the value of n can be a positive integer such as 1, 2, or 3.

[0145] There are several ways to combine all the bytes of the OAM information with the bearer frame. In some implementations, the combination of all the bytes of the OAM information with the bearer frame may include any of the following: all the bytes of the OAM information are located after the timeslot bytes of the bearer frame; all the bytes of the OAM information are located between the overhead bytes and the timeslot bytes of the bearer frame; all the bytes of the OAM information are located between the frame delimiter bytes and the overhead bytes of the bearer frame.

[0146] Please refer to Figure 35. Figure 35 shows one way to combine the complete bytes of the OAM information with the bearer frame shown in Figure 32. The complete bytes of the OAM information are placed after the bearer frame, specifically after the timeslot bytes of the bearer frame. Here, n can be a natural number such as 1, 2, 3, 4, 5, 6, 7, or 8. In Figure 35, when OAM information is not needed, only the bearer frame content can be sent. When OAM information is needed, the bearer frame and OAM information can be combined and sent. The receiving end can determine whether the received content is the bearer frame content or a combination of the bearer frame content and OAM information content based on the received length. For example, if the length of the received bearer frame is not the expected original bearer frame length (1599 bytes), but rather the sum of the expected length (1599 bytes) and the length of the OAM information bytes (n bytes, such as n = 1, 2, or 3), it indicates that OAM information is appended to the bearer frame. In this case, the receiver can extract the OAM information bytes from the newly received length field according to the combination method of all bytes of the bearer frame bytes and OAM information (which can be agreed upon in advance by the sender and receiver). The remaining content is the content of the bearer frame. In this way, the receiver can recover the original bearer frame and OAM information from the received field.

[0147] It should be noted that the above explanation uses the example of transmitting all bytes of the OAM field combined with the bearer frame. In some possible implementations, only some bytes of the OAM information can be combined with the bearer frame before transmission, and the entire OAM information can be transmitted in multiple batches combined with multiple bearer frames. However, considering that in practical applications, this method of transmitting OAM information usually increases the difficulty of parsing and recognizing the OAM information at the receiving end, this method is not recommended. Instead, the method of transmitting the entire OAM field combined with the bearer frame is preferred.

[0148] In some implementations, when transmitting the bearer frame and OAM information shown in Figure 32, the OAM information can be transmitted in a manner where the bearer frame includes fixed OAM bytes, which are used to carry OAM information. When OAM information needs to be sent, the OAM bytes can carry the OAM information; when OAM information does not need to be sent, the OAM bytes can be a default value or idle content.

[0149] When the bearer frame includes OAM bytes, the position of the OAM bytes within the bearer frame can vary. In some implementations, the position of the OAM bytes within the bearer frame can include any of the following: the OAM bytes are located after the timeslot bytes of the bearer frame; the OAM bytes are located between the overhead bytes and the timeslot bytes of the bearer frame; the OAM bytes are located between the frame delimiter bytes and the overhead bytes of the bearer frame; or the OAM bytes are located between the preamble bytes and the frame delimiter bytes of the bearer frame.

[0150] When using OAM bytes to carry OAM information, in some implementations, the OAM byte can carry the entire content of the OAM information. In other implementations, the OAM byte can carry a portion of the OAM information, with the entire content of the OAM information carried across multiple OAM bytes in multiple carrying frames. Where the OAM byte carries part or all of the OAM information, if the number of OAM bytes exceeds the actual number of bytes of OAM information being carried, the remaining OAM bytes can carry a default value (e.g., 0 or 1). For example, if the OAM information consists of 3 bytes, and the OAM byte itself comprises 3 bytes, then the 3 OAM bytes can carry the 3 bytes of OAM information, with one frame carrying the entire content of the OAM information. As another example, if the OAM information consists of 2 bytes, and the OAM byte itself comprises 3 bytes, then 2 OAM bytes can carry the 2 bytes of OAM information, with one frame carrying the entire content of the OAM information, and the remaining OAM byte can carry a default value.

[0151] Please refer to Figure 36. The bearer frame shown in Figure 36, based on the bearer frame shown in Figure 32, also includes n OAM bytes, where n can be a natural number such as 1, 2, 3, 4, 5, 6, 7, or 8. Assuming n equals 3, when OAM information needs to be transmitted, one frame can carry the entire content of the OAM information (occupying 1, 2, or 3 bytes; if there are remaining OAM bytes, the remaining bytes can be invalid values). When OAM information is not needed, the content at the OAM byte position can be invalid values ​​(a fixed default value, such as all 0s or all 1s).

[0152] The length of the bearer frame shown in Figure 36 is the same whether or not OAM information is transmitted. For the receiving end, it can determine whether the bearer frame carries OAM information by judging whether the content carried by the OAM byte in the bearer frame is the default value.

[0153] The bearer frame shown in Figure 32 includes 7 preamble bytes (0x55) and 1 frame delimiter byte (0xD5). Since the preamble byte content is a fixed value of 0x55, in some implementations, when transmitting OAM information, the OAM information can be placed in the preamble byte position of the bearer frame, with the preamble byte carrying the OAM information. When the transmitting end needs to send OAM information, it can place the OAM information in the preamble position for transmission; when it does not need to send OAM information, it can send the original preamble byte 0x55.

[0154] When the OAM information is carried by the preamble byte, n bytes (n equals 1, 2, or 3) can be selected from the last 6 bytes of the preamble byte to carry part of the OAM information. For example, with n equal to 3, the last 3 bytes of the preamble byte can carry the entire OAM information, as shown in Figure 37. Alternatively, the first 3 bytes of the preamble byte can carry the entire OAM information, as shown in Figure 38. No specific limitations are made here regarding the method of carrying OAM information using the preamble byte.

[0155] When OAM information is carried by the preamble byte in the bearer frame, for the receiver, if the received byte content of the preamble portion of the bearer frame is not 0x55, it indicates that the content carried at that position is OAM information. In this case, the receiver can extract the OAM information byte content at the corresponding position according to the bearer method of the sender (which can be agreed upon in advance by the sender and receiver), and then reset the content at that position to the preamble byte content of 0x55, thus restoring the original bearer frame structure. This method determines whether OAM information is carried by analyzing whether the preamble position is the original preamble content (0x55).

[0156] The bearer frame shown in Figure 32 includes 7 preamble bytes (0x55) and 1 frame delimiter byte (0xD5). Since the content of these bytes is fixed, they do not need to be transmitted during transmission. In this way, the bearer frame of the GE interface under the international standard can be redefined.

[0157] Specifically, in some implementations, the bearer frame can consist of 1 preamble byte, 7 overhead bytes, and 1584 time slot bytes, totaling 1592 bytes (this is a specific implementation of the bearer frame shown in Figure 12, which reduces 6 0x55 bytes and one 0xD5 byte compared to the bearer frame shown in Figure 32). Please refer to Figure 39. The bearer frame shown in Figure 39 includes 1 preamble byte (0x55), 7 overhead bytes (OH), and 1584 time slot bytes. These 1584 time slot bytes constitute the bearer area of ​​the bearer frame and can be divided into 96 time slots.

[0158] When transmitting bearer frames, there can be a gap of multiple bytes between frames. In some implementations, there can be a gap of 16 bytes between two adjacent bearer frames (an increase of 7 bytes from the 9-byte gap shown in Figure 32, which is a reduction of 7 bytes compared to the bearer frame shown in Figure 32). That is, when transmitting bearer frames, after sending every 1592 bytes of bearer frames, there can be a 16-byte gap, then another 1592 bytes of bearer frames are sent, then another 16-byte gap is sent, and so on, repeating in this manner.

[0159] For the bearer frame shown in Figure 39, the transmitting end can also send the bearer frame along with OAM information to the receiving end when sending it. In some embodiments, the OAM information can be the 3-byte OAM information shown in Figure 31. In other embodiments, the OAM information can also be the n-byte OAM information obtained by compressing the 3-byte OAM information shown in Figure 33, where n can be 1 or 2.

[0160] When the bearer frame shown in Figure 39 and the OAM information are transmitted together to the receiving end, in some embodiments, the OAM information can be transmitted between two adjacent bearer frames. Specifically, the OAM information is carried by bytes, and when transmitting OAM information between two adjacent bearer frames, it can be that bytes used to carry the OAM information are transmitted between the two bearer frames.

[0161] For the bearer frame shown in Figure 39, when transmitting OAM information between two adjacent bearer frames, since there can be a 16-byte interval between two adjacent bearer frames, and the maximum size of the entire OAM information is 3 bytes (the OAM information shown in Figure 31 is 3 bytes, and the OAM information shown in Figure 33 is n bytes, where n is 1 or 2), plus the 2 or 3 bytes of end flag that need to be reserved after sending the bearer frame, the 1 byte that needs to be added when sending the OAM information to represent the start flag (S byte or S code), and the 2 or 3 bytes of end flag, the maximum size is 7 bytes. Therefore, the entire OAM information can be transmitted between two bearer frames in one go. Therefore, in some implementations, when transmitting OAM information between two adjacent bearer frames, the specific transmission method of OAM information can be to transmit the entire OAM information between the two bearer frames. Of course, in some possible implementations, partial bytes of OAM information can be transmitted between two bearer frames, while all bytes of OAM information are transmitted between multiple bearer frames. However, considering that this transmission method would increase the difficulty of parsing and recognizing OAM information at the receiving end, this transmission method is not recommended. Instead, it is preferable to transmit all bytes of OAM information between two bearer frames.

[0162] Taking a 16-byte interval between bearer frames as an example, the transmission of bearer frames and OAM information can be as shown in Figure 40. In Figure 40, a start flag byte S is added before all bytes of the OAM information to form an n-byte field of S+OAM, which is transmitted in one go between bearer frames. n can be equal to 2, 3, or 4. When OAM information is not needed, after sending 1592 bytes of bearer frame content, the next bearer frame content is sent after a 16-byte idle period. When OAM information is needed, the n-byte content of S+OAM can be sent during the idle period between bearer frames. For the receiving end, it can determine whether the received information is bearer frame content or OAM information content based on the length of the received information (the byte length of the bearer frame is much larger than the byte length of the OAM).

[0163] In some implementations, when transmitting the bearer frame and OAM information shown in Figure 39, the OAM information can also be transmitted by combining all bytes of the OAM information with the bearer frame. This eliminates the need for the additional start flag S bytes required when transmitting OAM information separately. Specifically, when all bytes of the OAM information are combined with the bearer frame, the combined number of bytes is 1592+n bytes, where n bytes are used to carry the OAM information, and n is an integer such as 1, 2, or 3.

[0164] There are several ways to combine all the bytes of the OAM information with the bearer frame. In some implementations, the combination of all the bytes of the OAM information with the bearer frame may include any of the following: all the bytes of the OAM information are located after the timeslot bytes of the bearer frame; all the bytes of the OAM information are located between the overhead bytes and the timeslot bytes of the bearer frame; all the bytes of the OAM information are located between the preamble bytes and the overhead bytes of the bearer frame.

[0165] Please refer to Figure 41. In Figure 41, when combining the bearer frame and OAM information, all bytes of the OAM information (Figure 41 shows n bytes, where n is an integer such as 1, 2, or 3) are placed after the bearer frame, i.e., all bytes of the OAM information are located after the timeslot bytes of the bearer frame. When OAM information needs to be sent, all bytes of the OAM information and the bearer frame can be combined and sent together; when OAM information does not need to be sent, only the content of the bearer frame can be sent. For the receiving end, when the length of the received bearer frame is not the expected original bearer frame length (1592 bytes), but is the sum of the expected length (1592 bytes) and the length of the OAM information bytes (n bytes, such as n=3), it indicates that OAM information is appended to the bearer frame. In this case, the receiving end can extract the OAM information byte content from the received new length field according to the combination method of the bearer frame bytes and the OAM information bytes by the sending end (the sending end and receiving end can agree on the combination method of the bearer frame and OAM information bytes in advance). The remaining content is the content of the bearer frame. In this way, the receiving end can recover the original bearer frame and OAM information from the received fields.

[0166] It should be noted that the above explanation uses the example of transmitting all bytes of the OAM field combined with the bearer frame. In some possible implementations, only some bytes of the OAM information can be combined with the bearer frame for transmission, and the entire OAM information can be transmitted in multiple batches combined with multiple bearer frames. However, considering that in practical applications, this method of transmitting OAM information usually increases the difficulty of parsing and recognizing the OAM information at the receiving end, this method is not recommended. Instead, the preferred method is to transmit the entire OAM field combined with the bearer frame.

[0167] In some implementations, when transmitting the bearer frame and OAM information shown in Figure 39, the OAM information can also be transmitted by including an OAM byte in the bearer frame, with the OAM byte carrying the OAM information. When OAM information needs to be sent, the OAM byte can carry the OAM information; when OAM information does not need to be sent, the OAM byte can be a default value or idle content.

[0168] When the bearer frame includes OAM bytes, the position of the OAM bytes within the bearer frame can vary. In some implementations, the position of the OAM bytes within the bearer frame can include any of the following: the OAM bytes are located after the timeslot bytes of the bearer frame; the OAM bytes are located between the overhead bytes and the timeslot bytes of the bearer frame; or the OAM bytes are located between the preamble bytes and the overhead bytes of the bearer frame.

[0169] When using OAM bytes to carry OAM information, in some implementations, the OAM bytes can carry the entire content of the OAM information. In this case, the number of OAM bytes can be n, where n is an integer such as 1, 2, or 3. In other implementations, the OAM bytes can also carry a portion of the OAM information, with the entire content of the OAM information carried across multiple OAM bytes in multiple carrying frames. Where the OAM bytes carry part or all of the OAM information, if the number of OAM bytes is greater than the actual number of bytes of OAM information carried, the remaining OAM bytes can carry a default value (e.g., 0 or 1). For example, if the OAM information consists of 3 bytes, and the OAM bytes comprise 3 bytes, then 3 OAM bytes can carry the 3 bytes of OAM information, and one frame carries the entire content of the OAM information. As another example, if the OAM information consists of 2 bytes, and the OAM bytes comprise 3 bytes, then 2 OAM bytes can carry the 2 bytes of OAM information, and one frame carries the entire content of the OAM information, with the remaining OAM byte carrying a default value.

[0170] Please refer to Figure 42. The bearer frame shown in Figure 42, based on the bearer frame shown in Figure 39, also includes n fixed OAM bytes, where n can be an integer such as 1, 2, 3, 4, 5, 6, 7, or 8. Assuming n equals 3, when OAM information needs to be transmitted, one frame can carry the entire content of the OAM information (occupying 1, 2, or 3 bytes; if there are remaining OAM bytes, the remaining bytes can be invalid values). When OAM information is not needed, the content at the OAM byte position can be invalid values ​​(fixed default values, such as all 0s or all 1s). For the receiving end, it can determine whether the bearer frame carries OAM information by judging whether the content carried by the OAM bytes in the bearer frame is a default value. For example, if the content carried by the OAM bytes in the bearer frame is not a fixed default value, then the OAM bytes are determined to carry valid OAM information; otherwise, the OAM bytes are determined to carry invalid OAM information. Furthermore, the bearer frame can carry the entire content of the OAM information, or it can carry only a portion of the OAM information. Even when carrying only partial OAM information, the receiving end can combine the partial OAM information carried in each frame to recover the complete OAM information.

[0171] It should be noted that in some implementations of transmitting OAM information between bearer frames, burst mode can be used. For example, in the embodiments shown in Figures 18, 19, 26, 34, and 40, when the transmitting end sends the bearer frame and OAM information, after sending the bearer frame and the end flag byte, it may not send idle bytes, but directly send the byte structure corresponding to the OAM information (i.e., S bytes + OAM information bytes). Similarly, after sending the byte structure corresponding to the OAM information and the end flag byte, it may not send idle bytes, but directly send the bearer frame.

[0172] The bearer frame in the embodiments shown in Figures 12 to 42 consists of multiple bytes, including a preamble byte, an overhead byte, and a timeslot byte. The preamble byte carries the preamble, the overhead byte carries the overhead information of the service, and the timeslot byte carries the service content. This bearer frame is transmitted after encoding. Since the GE interface uses an 8b / 10b encoding structure, and the bearer frame shown in Figures 12 to 42 consists of multiple bytes, each byte containing 8 bits, the bearer frames shown in Figures 12 to 39 can be used to carry fine-grained services on the GE interface, thus meeting the requirements for carrying fine-grained services on the GE interface. Furthermore, a method for carrying OAM information is also provided. This OAM information can be carried by the bearer frames shown in Figures 12 to 42, transmitted between bearer frames, or combined with bearer frames before transmission. This allows the receiving end to perform quality control of the customer service pipeline based on the OAM information.

[0173] The embodiments shown in Figures 12 to 42 above describe the carrying scheme and transmission method of bearer frames and OAM information at the MII interface. When the MII interface sends the bearer frames and OAM information to the PCS layer of the GE interface, the PCS layer of the GE interface performs 8b / 10b encoding on each transmitted byte. 8b / 10b encoding is the encoding rule of the Ethernet protocol, which can encode 8 bits of a byte into a 10-bit code group. The 10-bit code group is divided into a data code group and a control code group. The data code group is represented by Dx.x, and the control code group is represented by Kx.x, where x is the code group content value. A single data code group generally represents customer information data content, and the control code group generally represents command indication information. A control code group can represent a command message by itself. For example, / K27.7 / is an S code group, indicating the start indication of the transmission content, and / K30.7 / indicates an error indication. Control code groups can also be combined with several data code groups to represent a command group and implement a specific meaning. For example, the combination / K28.5 / D5.6 / represents an idle indicator (represented by I), indicating that the system is in an idle state and has no client data content.

[0174] For messages sent via the MII interface, the first byte must be 0x55. During 8b / 10b encoding, this is encoded as k27.7 (not D21.2) to indicate the start code group. Subsequent transmitted content is encoded into data code groups based on the transmitted byte content. For example, 0x55 starting with the second byte is encoded as D21.2, and 0xD5 is encoded as D21.6. Other bytes are also encoded into their corresponding data code groups. When tx_en becomes invalid (changing from high to low) and no content is transmitted, two control code groups, K29.7 (represented by T) and K23.7 (represented by R), are encoded first. The combination of T and R code groups indicates the end of the previously transmitted data. T and R code groups occupy 2 bytes of idle time. Depending on whether the length of the transmitted field is odd or even, the end marker is represented by either two T and R code groups (2 bytes of time) or three T and R code groups (3 bytes of time). If no new content is transmitted after sending T+R or T+R+R (tx_en is in a low-level invalid state), an idle indicator is sent. There are two sets of idle indicator information: idle1 and idle2. The idle1 indicator is in the / K28.5 / D5.6 / command group, and the idle2 indicator is in / K28.5 / D16.2 / . If new client content is transmitted during the idle indicator transmission, the idle state ends, and new client content information is transmitted.

[0175] In view of this, embodiments of this application also provide a bearer frame composed of code blocks of 10 bits in length, which can be obtained by 8b / 10b encoding the bearer frames shown in Figures 12 to 42. Details are as follows.

[0176] Figure 43 is a schematic diagram of the structure of a bearer frame according to an embodiment of this application. The bearer frame shown in Figure 43 consists of multiple code groups, each 10 bits long. These multiple code groups include a control code group, a first data code group, and a second data code group, with the first data code group located between the control code group and the second data code group. The control code group is the start code group of the bearer frame, and there is only one control code group. The first data code group is used to carry service overhead information, and there can be one or more code groups (the specific number of bytes is not shown in Figure 43). The second data code group is used to carry service content, and there can be one or more second data code groups (the specific number of bytes is not shown in Figure 43). The bearer frame shown in Figure 43 can be obtained by 10-bit encoding the bearer frame shown in Figure 12.

[0177] The bearer frame shown in Figure 43 is used for transmission through the PCS layer of the GE interface.

[0178] Since the GE interface uses an 8b / 10b encoding structure, and the bearer frame shown in Figure 43 consists of 10-bit code groups, the bearer frame shown in Figure 43 can be used to carry fine-grained services on the GE interface, thus meeting the requirements for carrying fine-grained services on the GE interface.

[0179] Optionally, in some embodiments, the bearer frame shown in FIG43 may further include a third data code group and a fourth data code group, both of which are 10 bits long. The third data code group is used to carry the preamble, and the fourth data code group is used to carry the frame delimiter, as shown in FIG44. The bearer frame shown in FIG44 includes a control code group, a first data code group, a second data code group, a third data code group, and a fourth data code group. The third data code group is located between the control code group and the fourth data code group, and the number of code groups can be one or more (the specific number of bytes is not shown in FIG44). The fourth data code group is located between the third data code group and the first data code group, and the number of code groups can be one or more (the specific number of bytes is not shown in FIG44). The bearer frame shown in FIG44 can be obtained by 10-bit encoding the bearer frame shown in FIG13.

[0180] The bearer frame shown in Figure 44 is used for transmission through the PCS layer of the GE interface.

[0181] Since the GE interface uses an 8b / 10b encoding structure, and the bearer frame shown in Figure 44 consists of 10-bit code groups, the bearer frame shown in Figure 44 can be used to carry fine-grained services on the GE interface, thus meeting the requirements for carrying fine-grained services on the GE interface.

[0182] The following will use some more specific implementation examples to further illustrate the carrier frames shown in Figures 43 and 44.

[0183] In some implementations, the bearer frame shown in Figure 43 can specifically consist of 1575 code groups (corresponding to the Chinese standard). These 1575 code groups include one control code group, six third data code groups, one fourth data code group, seven first data code groups, and 1560 second data code groups, with the 1560 second data code groups divided into 24 time slots. These 1575 code groups can be obtained by 8b / 10b encoding the bearer frame shown in Figure 14.

[0184] In some implementations, when transmitting the aforementioned bearer frame consisting of 1575 code groups, there may be a gap of 9 code groups (10 bits) between two adjacent bearer frames. Optionally, when transmitting multiple bearer frames, four adjacent bearer frames may form a multiframe.

[0185] To monitor the quality of service pipelines carrying customer services, the aforementioned bearer frame composed of 1575 code groups can also be transmitted to the receiving end along with OAM information. In some embodiments, the OAM information can be obtained by 10-bit encoding of the second, third, fourth, sixth, seventh, and eighth bytes of a first OAM code block, which is an OAM code block under a first standard, specifically the Chinese standard. That is, the OAM information can be obtained by 10-bit encoding of the six bytes OAM_1 and OAM_2 shown in Figure 16. In other embodiments, the OAM information can be obtained by compressing and 10-bit encoding the second, third, fourth, sixth, seventh, and eighth bytes of the first OAM code block. That is, the OAM information can be obtained by 10-bit encoding of the compressed n bytes (n can be 1, 2, 3, 4, or 5) shown in Figure 17.

[0186] When transmitting a bearer frame consisting of 1575 code groups and OAM information to the receiving end, there are various methods for transmitting the OAM information, which can be the same as the method used when transmitting the bearer frame and OAM information shown in Figure 14 to the receiving end. Specifically, in some embodiments, the OAM information transmission method may include any of the following: transmitting OAM information between two adjacent bearer frames; the OAM information is carried by multiple 10-bit data code groups, and all code groups of the OAM information are combined with the bearer frame before transmission; the bearer frame also includes a fifth data code group, which is used to carry the OAM information; or the OAM information is carried in multiple third data code groups of the bearer frame.

[0187] In some implementations, transmitting OAM information between two adjacent bearer frames may include any of the following: transmitting the entire code group of the OAM information between two adjacent bearer frames; transmitting a portion of the code group of the OAM information between two adjacent bearer frames, wherein the entire code group of the OAM information is transmitted multiple times. In the case of transmitting the entire code group of the OAM information multiple times, in some more specific implementations, the entire code group of the OAM information may be transmitted in two separate transmissions, each transmitting half of the OAM information. Each transmitted code group is located between specified bearer frames, so that the receiving end can combine the OAM information between these specified bearer frames to recover the original OAM information.

[0188] In some implementations, when all code groups of the OAM information are combined with the bearer frame for transmission, the combination of all code groups of the OAM information with the bearer frame may include any of the following: all code groups of the OAM information are located after the second data code group of the bearer frame; all code groups of the OAM information are located between the first and second data code groups of the bearer frame; all code groups of the OAM information are located between the fourth data code group and the first data code group of the bearer frame; all code groups of the OAM information are located between the third and fourth data code groups of the bearer frame.

[0189] In some embodiments, when a bearer frame includes a fifth data code group for carrying OAM information, the fifth data code group for carrying OAM information may include any of the following: the fifth data code group is used to carry the entire content of the OAM information; or the fifth data code group is used to carry a portion of the OAM information, wherein the entire content of the OAM information is carried in the fifth data code group of multiple bearer frames.

[0190] In this case, the number of fifth data code groups is fixed, and the content carried by the fifth data code group is the default value when the fifth data code group does not carry OAM information.

[0191] The transmission method of the bearer frame composed of 1575 code groups and OAM information can be referred to the embodiments shown in Figures 18 to 24 above, and will not be described in detail here.

[0192] In some implementations, the bearer frame shown in Figure 41 can specifically consist of 1568 code groups (corresponding to the Chinese standard). These 1568 code groups include one control code group, seven first data code groups, and 1560 second data code groups, with the 1560 second data code groups divided into 24 time slots. This 1568-code-group bearer frame can be obtained by reducing the third and fourth data code groups of the aforementioned 1575-code-group bearer frame, or it can be obtained by performing 8b / 10b encoding on the bearer frame shown in Figure 25.

[0193] In some implementations, when transmitting the aforementioned bearer frame consisting of 1568 code groups, a gap of 16 code groups (10 bits) can be placed between two adjacent bearer frames. Optionally, when transmitting multiple bearer frames, four adjacent bearer frames can form a multiframe.

[0194] To monitor the quality of service pipelines carrying customer services, in some implementations, the aforementioned bearer frame composed of 1568 code groups can also be transmitted to the receiving end along with OAM information. The OAM information can be obtained by 10-bit encoding of the second, third, fourth, sixth, seventh, and eighth bytes of a first OAM code block, which is an OAM code block under a first standard, specifically the Chinese standard. In other words, the OAM information can be obtained by 10-bit encoding of the six bytes OAM_1 and OAM_2 shown in Figure 16. In other implementations, the OAM information can be obtained by compressing and 10-bit encoding the second, third, fourth, sixth, seventh, and eighth bytes of the first OAM code block. That is, the OAM information can be obtained by 10-bit encoding of the compressed n bytes (n can be 1, 2, 3, 4, or 5) shown in Figure 17.

[0195] When transmitting a bearer frame consisting of 1568 code groups and OAM information together to the receiving end, there are various methods for transmitting the OAM information, which can be the same as the method used when transmitting the bearer frame and OAM information shown in Figure 25 to the receiving end. Specifically, in some embodiments, the OAM information transmission method may include any of the following:

[0196] OAM information is transmitted between two adjacent bearer frames. The OAM information is carried by multiple 10-bit data code groups. All the code groups of the OAM information are combined with the bearer frame and then transmitted. The bearer frame also includes a fifth data code group, which is used to carry the OAM information.

[0197] In some implementations, transmitting OAM information between two adjacent bearer frames may include any of the following: transmitting the entire code group of OAM information between two adjacent bearer frames; or transmitting a portion of the code group of OAM information between two adjacent bearer frames, wherein the entire code group of OAM information is transmitted multiple times.

[0198] In some more specific implementations, when all code groups of OAM information are transmitted multiple times, all code groups of OAM information can be transmitted in two separate transmissions, with half of the code group of OAM information transmitted each time. The code group transmitted each time is located between specified bearer frames, so that the receiving end can combine the OAM information between the specified bearer frames to recover the original OAM information.

[0199] When transmitting the entire code group of OAM information in combination with the bearer frame, the combination method of the entire code group of OAM information and the bearer frame may include any of the following: the entire code group of OAM information is located after the second data code group of the bearer frame; the entire code group of OAM information is located between the first data code group and the second data code group of the bearer frame; the entire code group of OAM information is located between the control code group and the first data code group of the bearer frame.

[0200] The transmission method of the bearer frame composed of 1568 code groups and OAM information can be referred to the embodiments shown in Figures 26 to 28 above, and will not be described in detail here.

[0201] In some implementations, the bearer frame shown in Figure 44 can specifically consist of 1599 code groups (corresponding to international standards). These 1599 code groups include one control code group, six third data code groups, one fourth data code group, seven first data code groups, and 1584 second data code groups. The 1584 second data code groups are divided into 96 time slots. These 1599 code groups can be obtained by 8b / 10b encoding the bearer frame shown in Figure 32.

[0202] In some implementations, when transmitting the aforementioned bearer frame consisting of 1599 code groups, there may be a gap of 9 code groups (10 bits in length) between two adjacent bearer frames.

[0203] To monitor the quality of service pipelines carrying customer services, the aforementioned bearer frame composed of 1599 code groups can also be transmitted to the receiving end along with OAM information. In some embodiments, the OAM information can be obtained by 10-bit encoding of the second, third, and fourth bytes of a second OAM code block, which is an OAM code block under a second standard, an international standard. That is, the OAM information can be obtained by 10-bit encoding of the effective OAM bytes shown in Figure 31. In other embodiments, the OAM information can be obtained by compressing and 10-bit encoding the second, third, and fourth bytes of the second OAM code block. That is, the OAM information can be obtained by 10-bit encoding of the compressed n bytes (n can be 1 or 2) shown in Figure 33.

[0204] When transmitting a bearer frame consisting of 1599 code groups and OAM information to the receiving end, there are various methods for transmitting the OAM information, which can be the same as the method used when transmitting the bearer frame and OAM information shown in Figure 32 to the receiving end. Specifically, in some embodiments, the OAM information transmission method may include any of the following: transmitting OAM information between two adjacent bearer frames; the OAM information is carried by multiple 10-bit data code groups, and all code groups of the OAM information are combined with the bearer frame before transmission; the bearer frame also includes a fifth data code group, which is used to carry the OAM information; or the OAM information is carried in multiple third data code groups of the bearer frame.

[0205] In some implementations, transmitting OAM information between two adjacent bearer frames may include any of the following: transmitting the entire code group of OAM information between two adjacent bearer frames; or transmitting a portion of the code group of OAM information between two adjacent bearer frames, wherein the entire code group of OAM information is transmitted multiple times.

[0206] In some more specific implementations, when all code groups of OAM information are transmitted multiple times, all code groups of OAM information can be transmitted in two separate transmissions, with half of the code group of OAM information transmitted each time. The code group transmitted each time is located between specified bearer frames, so that the receiving end can combine the OAM information between the specified bearer frames to recover the original OAM information.

[0207] In some implementations, when all code groups of the OAM information are combined with the bearer frame for transmission, the combination of all code groups of the OAM information with the bearer frame may include any of the following: all code groups of the OAM information are located after the second data code group of the bearer frame; all code groups of the OAM information are located between the first and second data code groups of the bearer frame; all bytes of the OAM information are located between the fourth data code group and the first data code group of the bearer frame; or all code groups of the OAM information are located between the third and fourth data code groups of the bearer frame.

[0208] In some implementations, where the fifth data code group of a bearer frame carries OAM information, the fifth data code group used to carry OAM information may include any of the following: the fifth data code group is used to carry the entire content of the OAM information; or the fifth data code group is used to carry a portion of the OAM information, and the entire content of the OAM information is carried in the fifth data code groups of multiple bearer frames.

[0209] In this case, the number of fifth data code groups is fixed, and the content carried by the fifth data code group is the default value when the fifth data code group does not carry OAM information.

[0210] The transmission method of the bearer frame composed of 1599 code groups and OAM information can be found in the embodiments shown in Figures 34 to 38 above, and will not be described in detail here.

[0211] In some implementations, the bearer frame shown in Figure 43 can specifically consist of 1592 code groups (corresponding to international standards). These 1592 code groups include one control code group, seven first data code groups, and 1584 second data code groups, with the 1584 second data code groups divided into 96 time slots. This 1592-code-group bearer frame can be obtained by reducing the third and fourth data code groups of the aforementioned 1599-code-group bearer frame, or it can be obtained by performing 8b / 10b encoding on the bearer frame shown in Figure 39.

[0212] In some implementations, when transmitting the aforementioned bearer frame consisting of 1592 code groups, there may be a gap of 16 code groups (10 bits in length) between two adjacent bearer frames.

[0213] To monitor the quality of service pipelines carrying customer services, the aforementioned bearer frame composed of 1592 code groups can also be transmitted to the receiving end along with OAM information. In some embodiments, the OAM information includes OAM code blocks, which can be obtained by 10-bit encoding of the second, third, and fourth bytes of a second OAM code block. This second OAM code block is an OAM code block under a second standard, which is an international standard. In other words, the OAM information can be obtained by 10-bit encoding of the effective OAM bytes shown in Figure 31. In other embodiments, the OAM information can be obtained by compressing and 10-bit encoding the second, third, and fourth bytes of the second OAM code block. That is, the OAM information can be obtained by 10-bit encoding of the compressed n bytes (n can be 1 or 2) shown in Figure 33.

[0214] When transmitting a bearer frame consisting of 1592 code groups and OAM information to the receiving end, there are various methods for transmitting the OAM information, which can be the same as the method used when transmitting the bearer frame and OAM information shown in Figure 39 to the receiving end. Specifically, in some embodiments, the OAM information transmission method may include any of the following: transmitting OAM information between two adjacent bearer frames; the OAM information is carried by multiple 10-bit data code groups, and all code groups of the OAM information are combined with the bearer frame before transmission; the bearer frame also includes a fifth data code group, which is used to carry the OAM information.

[0215] In some implementations, transmitting OAM information between two adjacent bearer frames may include any of the following: transmitting the entire code group of OAM information between two adjacent bearer frames; or transmitting a portion of the code group of OAM information between two adjacent bearer frames, wherein the entire code group of OAM information is transmitted multiple times.

[0216] In some more specific implementations, when all code groups of OAM information are transmitted multiple times, all code groups of OAM information can be transmitted in two separate transmissions, with half of the code group of OAM information transmitted each time. The code group transmitted each time is located between specified bearer frames, so that the receiving end can combine the OAM information between the specified bearer frames to recover the original OAM information.

[0217] In the case of transmitting the complete code group of OAM information combined with the bearer frame, in some embodiments, the combination method of the complete code group of OAM information with the bearer frame may include any of the following: the complete code group of OAM information is located after the second data code group of the bearer frame; the complete code group of OAM information is located between the first data code group and the second data code group of the bearer frame; the complete code group of OAM information is located between the control code group and the first data code group of the bearer frame.

[0218] The transmission method of the bearer frame composed of 1592 code groups and OAM information can be found in the embodiments shown in Figures 40 to 42 above, and will not be described in detail here.

[0219] To facilitate understanding of the bearer frame consisting of 10-bit code groups provided in the embodiments of this application, the following description will take the embodiments shown in Figures 45 to 49 as examples.

[0220] The embodiment shown in Figure 45 is the result of 10-bit encoding of the bearer frames shown in Figures 18, 19, 26, 34, and 40. That is, after 8b / 10b encoding at the PCS layer, the byte structure streams of Figures 18, 19, 26, 34, and 40 can be transformed into a 10-bit code group stream structure as shown in Figure 45 (the lower 10b code group stream in Figure 45). Similarly, when OAM information needs to be sent and the OAM information and the time slot content of the bearer frame are combined and transmitted, the byte structure streams of Figures 21, 27, 35, and 41 become a 10-bit code group stream structure as shown in Figure 46. Similarly, when the carrier frame includes a fixed code group for carrying OAM information (such as the case where OAM information is carried by the third data code group or the fifth data code group), the byte structure streams of Figures 22, 23, 24, 28, 36, 37, 38, and 42 are transformed into the 10-bit code group stream structure of Figure 47.

[0221] Looking directly at the 10-bit code stream, the structures of these code groups are shown in Figures 48 and 49. In Figure 48, no OAM information is transmitted between the bearer frames. In Figure 49, OAM information is interspersed between the bearer frames. The bearer frame structure is as follows: {K27.7, 6 D21.2, D21.6, 7 overhead Dx.x, several fine-grained frame slot contents Dx.x, K29.7, 1 or 2 K23.7}, with a total length of 1575 code groups according to the Chinese standard or 1599 code groups according to the international standard. When the bearer frame contains OAM information, the length increases by n code groups, where n is the length occupied by the OAM information alone. Optionally, under the Chinese standard, n can be equal to 1, 2, 3, 4, 5, or 6; under the international standard, n can be equal to 1, 2, or 3. When reducing the 1575 code groups of the Chinese standard or the 1599 code groups of the international standard, the total length of the bearer frame decreases by m code groups. Optionally, m can be equal to 7. Following the carrier frame code group are K27.7, 1 or 2 / K23.7 / code groups, indicating the end of the carrier frame. The remaining portion consists of idle code groups and I code groups. When OAM information is inserted between two carrier frames, as shown in Figure 49, the code group structure corresponding to the OAM information is: {K27.7, n OAM Dx.x, K29.7, 1 or 2 K23.7}, where n = 1, 2, 3, 4, 5, or 6. K29.7 and 1 or 2 K23.7 are the end-of-frame marker code groups. If no OAM information is transmitted between two carrier frames, then all code groups are I code groups.

[0222] In some implementations, burst mode can be used when transmitting OAM information between bearer frames. For example, in the embodiment shown in Figure 49, when the transmitting end sends the bearer frame and OAM information, after sending the bearer frame and the end flag code group (T+R or T+R+R), it may not send the I code group, but directly send the code group structure corresponding to the OAM information. Similarly, after sending the code group structure corresponding to the OAM information and the end flag code group, it may not send the I code group, but directly send the bearer frame.

[0223] It should be noted that, in some implementations, when transmitting a 10-bit code stream, the sending end can set the first code group (i.e., the first code group represented by S in Figures 48 and 49) to an even or odd position. In other words, the sending end can decide for itself whether the first code group in the 10-bit code stream is an even or odd position in the sequence. Optionally, if the sending end does not specify whether the first code group in the 10-bit code stream is an odd or even position, the original odd and even position counting rules can be used.

[0224] Another bearer frame provided in this application embodiment consists of multiple code groups, each 10 bits long. These multiple code groups include a control code group, a first data code group, and a second data code group. The control code group is the start code group of the bearer frame. The first data code group carries service overhead information, and the second data code group carries service content. This bearer frame is used for transmission through the PCS layer. Since the GE interface uses an 8b / 10b encoding structure, and the bearer frame provided in this application embodiment consists of multiple code groups, each 10 bits long, it can be used to carry fine-grained services on the GE interface, thus meeting the requirements for carrying fine-grained services on the GE interface. Furthermore, a method for carrying OAM information is also provided. This OAM information can be carried by the bearer frame, sent between bearer frames, or combined with bearer frames before being sent. This allows the receiving end to perform quality control based on the OAM information carrying the service pipeline for customer services.

[0225] This application also provides a transmission method that can be used to transmit any of the bearer frames provided in this application or to transmit the bearer frame and OAM information.

[0226] Figure 50 is a schematic flowchart of a transmission method according to an embodiment of this application. The transmission method shown in Figure 50 can be applied to the sending end; in other words, the transmission method shown in Figure 50 can be executed by software or hardware installed on the sending end. The transmission method includes the following steps.

[0227] S502: Send a bearer frame to the sender. The bearer frame includes multiple bytes or multiple 10-bit code groups.

[0228] The bearer frame here can be a bearer frame composed of multiple bytes as provided in the embodiments of this application, as shown in Figures 12 to 42, which will not be described in detail here. Alternatively, the bearer frame here can also be a bearer frame composed of multiple 10-bit code groups as provided in the embodiments of this application, as shown in Figures 43 to 49, which will also not be described in detail here. Specifically, in the scenario where the sending end sends a message to the PCS layer through the MII interface, the sending end can send a bearer frame composed of multiple bytes. In the scenario where the sending end sends a message through the PCS layer, the sending end can send a bearer frame composed of multiple 10-bit code groups.

[0229] In some implementations, the bearer frame may carry OAM information in addition to client content. Specifically, when the bearer frame consists of multiple bytes, the OAM information may be six bytes (OAM_1 and OAM_2) as shown in Figure 16, or n bytes (n = 1, 2, 3, 4, or 5) obtained by compressing OAM_1 and OAM_2 as shown in Figure 17. The bearer frame carrying OAM information may specifically include OAM bytes for carrying OAM information, or the OAM information may be carried by bytes in the bearer frame used for carrying preamble content. For specific implementation details, please refer to the embodiments shown in Figures 22, 23, 24, 28, 36, 37, 38, and 42 above, which will not be described in detail here. When the bearer frame consists of multiple 10-bit code groups, the OAM information can be the three valid OAM bytes shown in Figure 31, or the n code groups (n=1 or 2) obtained by compressing and encoding the three valid OAM bytes into 10 bits, as shown in Figure 33. For specific implementation details, please refer to the embodiments shown in Figures 45-47 above, which will not be described in detail here. In this way, when the transmitter sends the bearer frame to the receiver, it can send the client content and OAM information together to the receiver.

[0230] In some implementations, the bearer frame may not carry OAM information. In this case, the transmitting end may send both the bearer frame and OAM information to the receiving end when transmitting the bearer frame. The transmitting end sending OAM information to the receiving end may include at least one of the following: transmitting OAM information between two adjacent bearer frames; or combining OAM information with the bearer frame before transmission.

[0231] In the case of transmitting OAM information between two adjacent bearer frames, in some implementations, the entire content of the OAM information can be transmitted between the two adjacent bearer frames. In other implementations, a portion of the OAM information can be transmitted between the two adjacent bearer frames, with the entire content of the OAM information being transmitted in multiple transmissions. For example, half of the OAM information can be transmitted between the two adjacent bearer frames, with the entire content of the OAM information being transmitted in two separate transmissions. When the bearer frame consists of multiple bytes, the specific implementation method for the transmitter to transmit OAM information between two adjacent bearer frames can be found in the embodiments shown in Figures 18, 19, 26, 34, and 40, which will not be described in detail here. When the bearer frame consists of multiple 10-bit code groups, the specific implementation method for the transmitter to transmit OAM information between two adjacent bearer frames can be found in the embodiments shown in Figures 45-47, which will also not be described in detail here.

[0232] When OAM information is combined with the bearer frame before transmission, there are several ways to combine the OAM information with the bearer frame. Taking a bearer frame consisting of multiple bytes as an example, the OAM information can be located after the timeslot byte of the bearer frame, or between the overhead byte and the timeslot byte, or between the frame delimiter byte and the overhead byte, or between the preamble byte and the frame delimiter byte, or between the preamble byte and the overhead byte. For specific implementation methods, please refer to the embodiments shown in Figures 21, 22, 27, 35, and 41, which will not be described in detail here.

[0233] The transmission method provided in this application can meet the requirements for carrying fine-grained services on the GE interface. Furthermore, since the sending end can also send OAM information along with the bearer frame to the receiving end, the receiving end can easily perform quality control on the service pipeline carrying customer services based on the OAM information.

[0234] Figure 51 is a schematic flowchart of a transmission method according to an embodiment of this application. The transmission method shown in Figure 51 can be applied to a receiving end; in other words, the transmission method shown in Figure 51 can be executed by software or hardware installed on the receiving end. The transmission method includes the following steps.

[0235] S512: Receives a bearer frame sent by the transmitting end. The bearer frame includes multiple bytes or multiple code groups with a length of 10 bits.

[0236] The bearer frame here can be a bearer frame composed of multiple bytes as provided in the embodiments of this application, as shown in Figures 12 to 42, which will not be described in detail here. Alternatively, the bearer frame here can also be a bearer frame composed of multiple 10-bit code groups as provided in the embodiments of this application, as shown in Figures 43 to 49, which will also not be described in detail here.

[0237] S514: Parse the bearer frame and extract the content carried by the bearer frame.

[0238] After receiving the bearer frame, the receiving end can parse the bearer frame to extract the content carried in the bearer frame.

[0239] In some implementations, the bearer frame may carry client content but not OAM information. In this case, the content extracted by the receiving end includes client content but not OAM information. When the bearer frame does not carry OAM information, the sending end can transmit OAM information between bearer frames. In this case, when receiving a bearer frame, the receiving end may further include: identifying the received content based on its length; and determining whether the received content is a bearer frame or OAM information based on its length.

[0240] Generally, the length of the bearer frame is much greater than the length of the OAM information. Thus, when the sending end transmits OAM information between bearer frames, the receiving end, upon receiving the information, can determine whether the length of the received content is the length of the bearer frame or the length of the OAM information (since the bearer frame length is much greater than the OAM information length), and thus determine whether the received content is a bearer frame or OAM information.

[0241] In some implementations, when the transmitting end sends OAM information between bearer frames, it can send a portion of the OAM information between two adjacent bearer frames, while the complete OAM information is sent multiple times between specified bearer frames. In this case, after recognizing the OAM information, the receiving end can also combine the OAM information between the specified bearer frames to obtain the complete OAM information. For example, consider the embodiment shown in Figure 19. Four bearer frames form a multiframe. The transmitting and receiving ends can agree to combine the OAM information fields after the first frame and the second frame, and the OAM information fields after the third frame and the fourth frame. In this way, the transmitting end can send the OAM_1 and OAM_2 functional information fields according to the agreed rules. The receiving end can determine the OAM information fields based on the received length, and then combine the OAM_1 and OAM_2 fields according to the agreed rules to recover the complete OAM information content.

[0242] In some implementations, when the bearer frame consists of multiple bytes, it may carry both client content and OAM information (the bearer frame includes fixed OAM bytes for carrying OAM information, or the OAM information is carried by preamble bytes in the bearer frame), or the bearer frame may be combined with OAM information and then sent to the receiving end. In this case, the receiving end parses the bearer frame and extracts the content carried by the bearer frame, which may include at least one of the following (1) to (4):

[0243] (1) The position of the preamble byte in the bearer frame is parsed. If the parsing result is not the preamble content, the parsing result is determined to be OAM information.

[0244] This scenario corresponds to a bearer frame containing multiple preamble bytes, each carrying OAM information. In this case, after parsing the preamble byte positions, if the content of the preamble byte is not 0x55, it indicates that the content carried at that position is OAM information. The receiver can then extract the OAM information byte content at the corresponding position according to the sender's bearing method (which can be pre-agreed upon by the sender and receiver), and then reset the content at that position to the preamble byte content of 0x55, thus restoring the original bearer frame structure.

[0245] (2) Parse the position of the OAM byte in the carrier frame. If the parsing result is not the default value, determine the parsing result as OAM information.

[0246] This scenario corresponds to a bearer frame containing a fixed OAM byte. In this case, when OAM information needs to be sent, the sender will include the OAM information in the OAM byte of the bearer frame; when OAM information is not needed, the sender will include a default value in the OAM byte. Therefore, after receiving the bearer frame, the receiver can determine whether the bearer frame contains OAM information by parsing the OAM byte position and checking whether the content carried by the OAM byte is a default value.

[0247] (3) Extract OAM information from the carrier frame if the length of the carrier frame is not the specified length.

[0248] This scenario corresponds to the sending end combining the bearer frame and OAM information before sending. For the receiving end, when the length of the received bearer frame is not the expected original bearer frame length, but the sum of the expected length and the OAM information byte length, it means that OAM information is attached to the bearer frame. In this case, the receiving end can extract the OAM information content from the new length field according to the way the sending end combines the bearer frame bytes and OAM information (which can be agreed upon in advance by the sending end and the receiving end). The remaining content is the content of the bearer frame.

[0249] (4) Determine whether to combine the parsed OAM information according to the agreed rules.

[0250] This situation corresponds to the scenario described in (1) to (3) above, where the sending end only sends a portion of the OAM information in a single frame. In this case, the sending end and the receiving end can pre-agree on whether to send the OAM information once or multiple times. If it is to send multiple times, they can also agree on which frames' OAM information will be combined. For example, if four carrier frames form a multiframe, the sending end and the receiving end can agree on combining the OAM information fields carried in the first frame and the second frame of the multiframe. In this way, the sending end can carry a portion of the OAM information in the first and second frames of the multiframe according to the agreed-upon rules. After receiving the carrier frames, the receiving end can combine the OAM information carried in the first and second frames of the multiframe according to the agreed-upon rules, thereby recovering the complete OAM information content.

[0251] In some implementations, when the bearer frame consists of multiple 10-bit code groups, the bearer frame may carry both client content and OAM information (corresponding to the bearer frame including a fixed fifth data code group (used to carry OAM information, also called the OAM code group), or the OAM information may be carried by the third data code group (used to carry preamble content) in the bearer frame). Alternatively, the bearer frame may be combined with OAM information and then sent to the receiving end. In this case, the receiving end parses the bearer frame and extracts the content carried by the bearer frame, which may include at least one of the following:

[0252] The third data code group in the bearer frame is parsed. If the parsing result is not preamble content, the parsing result is determined to be OAM information. This situation corresponds to a scenario where the bearer frame includes multiple third data code groups (used to carry preamble content), and multiple third data code groups carry OAM information. In this case, after the receiver parses the third data code group, if the code group content is not preamble content, it means that the content carried at that position is OAM information. At this time, the receiver can extract the OAM information at the corresponding position according to the bearer method of the sender (which can be agreed upon in advance by the sender and receiver). The information content is then reset to the preamble content, thus restoring the original bearer frame structure. The fifth data code group in the bearer frame is parsed, and if the parsing result is not the default value, the parsing result is determined to be OAM information. This situation corresponds to the scenario where the bearer frame includes a fixed fifth data code group (used to carry OAM information). In this case, when OAM information needs to be sent, the sender will carry OAM information in the fifth data code group of the bearer frame, and when OAM information does not need to be sent, the sender will carry the default value in the fifth data code group of the bearer frame. Therefore, after receiving the bearer frame, the receiver can determine whether the bearer frame carries OAM information by parsing the fifth data code group in the bearer frame and judging whether the content carried by the fifth data code group is the default value. If the length of the bearer frame is not the specified length, the OAM information is extracted from the bearer frame. For the specific implementation method, please refer to the explanation of the corresponding step (3) in the case where the bearer frame consists of multiple bytes. It will not be described again here.

[0253] The determination of whether to combine the parsed OAM information is based on the predetermined rules. For the specific implementation method, please refer to the explanation of the corresponding step (4) in the case where the carrier frame consists of multiple bytes. It will not be described again here.

[0254] The transmission method provided in this application can meet the requirements for carrying fine-grained services on the GE interface. Furthermore, since the sending end can also send OAM information along with the bearer frame to the receiving end, the receiving end can perform quality control on the service pipeline carrying customer services based on the OAM information.

[0255] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired results. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

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

[0257] The processor, network interface, and memory can be interconnected via an internal bus, which can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. This bus can be categorized as an address bus, data bus, control bus, etc. For ease of illustration, only a single bidirectional arrow is used in Figure 52, but this does not imply that there is only one bus or one type of bus.

[0258] Memory is used to store programs. Specifically, programs may include program code, which includes computer operation instructions. Memory may include main memory and non-volatile memory, and provides instructions and data to the processor.

[0259] The processor reads the corresponding computer program from non-volatile memory into memory and then runs it, forming a transmission device at the logical level. The processor executes the program stored in memory and specifically performs the following operations: sending a bearer frame to the sending end, the bearer frame comprising multiple bytes or multiple 10-bit code groups; or specifically performing the following operations: receiving a bearer frame sent by the sending end, the bearer frame comprising multiple bytes or multiple 10-bit code groups; parsing the bearer frame to extract the content carried by the bearer frame.

[0260] The method executed by the transmission device disclosed in the embodiment shown in Figure 52 of this application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. 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. It can implement or execute the methods, steps, and logic block diagrams disclosed in this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can reside in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, or registers. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0261] The electronic device can also perform the methods of FIG50 and FIG51 and implement the functions of the drive access device in the embodiments shown in FIG50 and FIG51, which will not be described again in this application.

[0262] 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 hardware and software, etc. In other words, the execution subject of the following processing flow is not limited to each logic unit, but can also be hardware or logic devices.

[0263] This application also proposes a computer-readable storage medium storing one or more programs, the programs including instructions that, when executed by a portable electronic device including multiple applications, enable the portable electronic device to perform the methods of the embodiments shown in Figures 50 and 51, specifically for performing the following operations: sending a bearer frame to a transmitting end, the bearer frame including multiple bytes or multiple 10-bit code groups; or specifically for performing the following operations: receiving a bearer frame sent by a transmitting end, the bearer frame including multiple bytes or multiple 10-bit code groups; parsing the bearer frame to extract the content carried by the bearer frame.

[0264] Figure 53 is a schematic diagram of the structure of a transmission device 530 according to an embodiment of this application. Referring to Figure 53, in one software implementation, the transmission device 530 may include: a sending module 531, wherein: the sending module 531 sends a bearer frame to a sending end, the bearer frame including multiple bytes or multiple 10-bit code groups.

[0265] The bearer frame here can be a bearer frame composed of multiple bytes as provided in the embodiments of this application, as shown in Figures 12 to 42, which will not be described in detail here. Alternatively, the bearer frame here can also be a bearer frame composed of multiple 10-bit code groups as provided in the embodiments of this application, as shown in Figures 43 to 49, which will also not be described in detail here.

[0266] In some embodiments, when the bearer frame does not carry OAM information, the transmitting module 531 further includes at least one of the following: transmitting the OAM information between two adjacent bearer frames; and combining the OAM information with the bearer frame before transmitting it.

[0267] The transmission device 530 provided in this application can also execute the method of FIG50 and realize the function of the transmission device 530 in the embodiment shown in FIG50, which will not be described again here.

[0268] Figure 54 is a schematic diagram of the structure of a transmission device 540 according to an embodiment of this application. Referring to Figure 54, in a software implementation, the transmission device 540 may include: a receiving module 541 and a processing module 542, wherein: the receiving module 541 receives a bearer frame sent by the sending end, the bearer frame including multiple bytes or multiple code groups of 10 bits in length; the processing module 542 parses the bearer frame and extracts the content carried by the bearer frame.

[0269] The bearer frame here can be a bearer frame composed of multiple bytes as provided in the embodiments of this application, as shown in Figures 12 to 42, which will not be described in detail here. Alternatively, the bearer frame here can also be a bearer frame composed of multiple 10-bit code groups as provided in the embodiments of this application, as shown in Figures 43 to 49, which will also not be described in detail here.

[0270] In some embodiments, OAM information is included between two adjacent bearer frames; the processing module 542 further includes: identifying the received content according to the length of the received content; wherein, if the length of the received content is greater than a first length, the received content is determined to be the bearer frame; if the length of the received content is less than a second length, the received content is determined to be OAM information, wherein the second length is less than or equal to the first length.

[0271] In some implementations, when the entire content of the OAM information is transmitted by the sending end in multiple parts, the processing module 542 further includes: combining the OAM information between specified bearer frames to obtain the entire content of the OAM information.

[0272] In some implementations, when the bearer frame consists of multiple bytes, the processing module 542 parses the bearer frame to extract the content carried by the bearer frame, including at least one of the following: parsing the preamble bytes in the bearer frame, and determining the parsing result as OAM information if the parsing result is not preamble content; parsing the OAM bytes in the bearer frame, and determining the parsing result as OAM information if the parsing result is not a default value; extracting OAM information from the bearer frame if the length of the bearer frame is not a specified length; and determining whether to combine the parsed OAM information according to agreed rules.

[0273] In some implementations, when the bearer frame consists of multiple 10-bit code groups, the processing module 542 parses the bearer frame to extract the content carried by the bearer frame, including at least one of the following: parsing the third data code group in the bearer frame, and determining the parsing result as OAM information if the parsing result is not preamble content; parsing the fifth data code group in the bearer frame, and determining the parsing result as OAM information if the parsing result is not a default value; extracting OAM information from the bearer frame if the length of the bearer frame is not a specified length; and determining whether to combine the parsed OAM information according to agreed rules.

[0274] The transmission device 540 provided in this application can also execute the method of FIG51 and realize the function of the transmission device 540 in the embodiment shown in FIG51, which will not be described again here.

[0275] This application also proposes a computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps described in the above-described transmission method embodiments.

[0276] In summary, the above description is merely a preferred embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

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

[0278] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0279] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0280] The various embodiments in this application are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

Claims

1. A carrier frame, comprising multiple bytes, said multiple bytes including: The preamble byte is used to carry the preamble. Overhead bytes, used to carry business overhead information; The timeslot byte is used to carry business content; The carrier frame is transmitted after being encoded.

2. The bearer frame as described in claim 1, wherein the bearer frame consists of 1568 bytes, the 1568 bytes including 1 preamble byte, 7 overhead bytes and 1560 time slot bytes, the 1560 time slot bytes being divided into 24 time slots.

3. The bearer frame as described in claim 1, wherein the bearer frame consists of 1592 bytes, the 1592 bytes including 1 preamble byte, 7 overhead bytes and 1584 time slot bytes, the 1584 time slot bytes being divided into 96 time slots.

4. The bearer frame as described in claim 2 or 3, wherein when transmitting multiple bearer frames, there is a 16-byte interval between two adjacent bearer frames.

5. The bearer frame as described in claim 1, wherein the bearer frame consists of 1575 bytes, the 1575 bytes including 7 preamble bytes, 1 frame delimiter byte, 7 overhead bytes and 1560 time slot bytes, the 1560 time slot bytes being divided into 24 time slots.

6. The bearer frame as described in claim 1, wherein the bearer frame consists of 1599 bytes, the 1599 bytes including 7 preamble bytes, 1 frame delimiter byte, 7 overhead bytes and 1584 time slot bytes, the 1584 time slot bytes being divided into 96 time slots.

7. The bearer frame as described in claim 5 or 6, wherein when transmitting multiple bearer frames, there is a 9-byte interval between two adjacent bearer frames.

8. The bearer frame as described in claim 2 or 5, wherein in the case of transmitting multiple bearer frames, four adjacent bearer frames constitute a multiframe.

9. The bearer frame as described in any one of claims 1 to 3, 5 and 6, wherein the bearer frame is further used to transmit together with Operation and Maintenance Management (OAM) information to the receiving end.

10. The bearer frame as described in claim 9, wherein the transmission method of the OAM information includes any one of the following: The OAM information is transmitted between two adjacent bearer frames; The OAM information is carried by multiple bytes, and all bytes of the OAM information are combined with the carrier frame before transmission; The bearer frame also includes OAM bytes, which are used to carry the OAM information; When the bearer frame includes multiple preamble bytes, the OAM information is carried in the multiple preamble bytes of the bearer frame.

11. The bearer frame as described in claim 10, wherein the OAM information is carried by multiple bytes; the transmission of the OAM information between two adjacent bearer frames includes any one of the following: Transmit all bytes of the OAM information between two adjacent bearer frames; Partial bytes of the OAM information are transmitted between two adjacent bearer frames, while the complete bytes of the OAM information are transmitted in multiple transmissions.

12. The bearer frame as described in claim 11, wherein all bytes of the OAM information are transmitted in multiple transmissions, including: The entire OAM information is transmitted in two parts, with half a byte of the OAM information transmitted each time, and the bytes transmitted each time are located between the specified bearer frames.

13. The bearer frame as described in claim 10, wherein the combination of all bytes of the OAM information with the bearer frame includes any one of the following: All bytes of the OAM information are located after the slot bytes of the bearer frame; All bytes of the OAM information are located between the overhead byte and the time slot byte of the bearer frame; All bytes of the OAM information are located between the preamble byte and the overhead byte of the bearer frame.

14. The bearer frame of claim 10, wherein the OAM byte is used to carry the OAM information, including any one of the following: The OAM byte is used to carry the entire content of the OAM information; The OAM byte is used to carry part of the OAM information, and the entire content of the OAM information is carried in the OAM bytes of multiple carrying frames; wherein, The number of OAM bytes is fixed, and if the OAM bytes do not carry the OAM information, the content carried by the OAM bytes is the default value.

15. The bearer frame as described in any one of claims 10 to 14, wherein the OAM information includes any one of the following: The contents of the second, third, fourth, sixth, seventh, and eighth bytes of the first OAM code block, wherein the first OAM code block is an OAM code block under the first standard; The content obtained by compressing the second, third, fourth, sixth, seventh, and eighth bytes of the first OAM code block; The contents of the second, third, and fourth bytes of the second OAM code block, where the second OAM code block is an OAM code block under the second standard; The content obtained by compressing the second, third, and fourth bytes of the second OAM code block.

16. A carrier frame comprising multiple code groups, each code group having a length of 10 bits, wherein the multiple code groups include: Control code group, wherein the control code group is the start code group of the bearer frame; The first data code group is used to carry the overhead information of the service; The second data code group is used to carry business content; The bearer frame is used for transmission through the Physical Coding System (PCS) layer.

17. The bearer frame as claimed in claim 16, wherein the bearer frame consists of 1568 code groups, the 1568 code groups including 1 control code group, 7 first data code groups and 1560 second data code groups, the 1560 second data code groups being divided into 24 time slots.

18. The bearer frame as claimed in claim 16, wherein the bearer frame consists of 1592 code groups, the 1592 code groups including 1 control code group, 7 first data code groups and 1584 second data code groups, the 1584 second data code groups being divided into 96 time slots.

19. The bearer frame as described in claim 17 or 18, wherein when transmitting multiple bearer frames, there is a 16-code-group interval between two adjacent bearer frames.

20. The bearer frame as described in claim 16, wherein the plurality of code groups further comprises a third data code group and a fourth data code group, wherein the third data code group is used to carry a preamble and the fourth data code group is used to carry a frame delimiter; in, The bearer frame consists of 1575 code groups, including 1 control code group, 6 third data code groups, 1 fourth data code group, 7 first data code groups, and 1560 second data code groups. The 1560 second data code groups are divided into 24 time slots.

21. The bearer frame as described in claim 16, wherein the plurality of code groups further comprises a third data code group and a fourth data code group, wherein the third data code group is used to carry a preamble and the fourth data code group is used to carry a frame delimiter; in, The bearer frame consists of 1599 code groups, including 1 control code group, 6 third data code groups, 1 fourth data code group, 7 first data code groups, and 1584 second data code groups. The 1584 second data code groups are divided into 96 time slots.

22. The bearer frame as described in claim 20 or 21, wherein when transmitting multiple bearer frames, there is a 9-code interval between two adjacent bearer frames.

23. The bearer frame as described in claim 17 or 20, wherein in the case of transmitting multiple bearer frames, four adjacent bearer frames constitute a multiframe.

24. The bearer frame as described in any one of claims 16 to 18, 20 and 21, wherein the bearer frame is further configured to be transmitted to the receiving end together with OAM information.

25. The bearer frame as described in claim 24, wherein the transmission method of the OAM information includes any one of the following: The OAM information is transmitted between two adjacent bearer frames; The OAM information is carried by multiple data code groups, and all code groups of the OAM information are combined with the carrier frame before transmission; The bearer frame also includes a fifth data code group, which is used to carry the OAM information; When the bearer frame includes multiple third data code groups, the OAM information is carried in the multiple third data code groups of the bearer frame.

26. The bearer frame as described in claim 25, wherein the OAM information is carried by a plurality of data code groups; the transmission of the OAM information between two adjacent bearer frames includes any one of the following: Transmit all code groups of the OAM information between two adjacent bearer frames; A portion of the code group of the OAM information is transmitted between two adjacent bearer frames, and the entire code group of the OAM information is transmitted multiple times.

27. The bearer frame as described in claim 26, wherein all code components of the OAM information are transmitted multiple times, including: The entire code group of the OAM information is transmitted in two parts, with half of the code group of the OAM information being transmitted each time, and the code group transmitted each time is located between the specified bearer frames.

28. The bearer frame as described in claim 25, wherein the combination of all code groups of the OAM information with the bearer frame includes any one of the following: All code groups of the OAM information are located after the second data code group of the bearer frame; All code groups of the OAM information are located between the first data code group and the second data code group of the bearer frame; All code groups of the OAM information are located between the control code group and the first data code group of the bearer frame.

29. The bearer frame as described in claim 25, wherein the fifth data code group is used to carry the OAM information, including any one of the following: The fifth data code group is used to carry the entire content of the OAM information; The fifth data code group is used to carry part of the OAM information, and the entire content of the OAM information is carried in the fifth data code group of multiple carrying frames; in, The number of the fifth data code group is fixed. If the fifth data code group does not carry the OAM information, the content carried by the fifth data code group is the default value.

30. The bearer frame as described in any one of claims 25 to 29, wherein the OAM information includes any one of the following: The content obtained by encoding the contents of the second, third, fourth, sixth, seventh, and eighth bytes of the first OAM code block, wherein the first OAM code block is an OAM code block under the first standard; The content obtained by compressing and encoding the second, third, fourth, sixth, seventh, and eighth bytes of the first OAM code block; The content obtained by encoding the contents of the second byte, third byte and fourth byte in the second OAM code block, the second OAM code block is the OAM code block under the second standard; The content obtained by compressing and encoding the contents of the second, third, and fourth bytes of the second OAM code block.

31. A transmission method, applied at a sending end, comprising: Send a bearer frame to the receiving end, the bearer frame including the bearer frame according to any one of claims 1 to 30.

32. The method of claim 31, wherein if the bearer frame does not carry OAM information, the method further comprises at least one of the following: The OAM information is transmitted between two adjacent bearer frames; The OAM information is combined with the bearer frame and then sent.

33. A transmission method, applied at a receiving end, comprising: Receive a bearer frame sent by a transmitter, wherein the bearer frame includes the bearer frame as described in any one of claims 1 to 30; The carrier frame is parsed to extract the content carried by the carrier frame.

34. The method of claim 33, wherein OAM information is included between two adjacent bearer frames; the method further includes: The received content is identified based on its length; Specifically, if the length of the received content is greater than the first length, the received content is determined to be the bearer frame; if the length of the received content is less than the second length, the received content is determined to be OAM information, wherein the second length is less than or equal to the first length.

35. The method of claim 34, wherein when the entire content of the OAM information is transmitted by the sending end in multiple transmissions, the method further comprises: The OAM information between the specified bearer frames is combined to obtain the complete content of the OAM information.

36. The method of claim 33, wherein when the bearer frame consists of multiple bytes, parsing the bearer frame and extracting the content carried by the bearer frame includes at least one of the following: The position of the preamble byte in the bearer frame is parsed. If the parsing result is not the preamble content, the parsing result is determined to be OAM information. The position of the OAM byte in the bearer frame is parsed, and if the parsing result is not the default value, the parsing result is determined to be OAM information; If the length of the bearer frame is not the specified length, extract the OAM information from the bearer frame; The decision on whether to combine the parsed OAM information is based on the agreed-upon rules.

37. The method of claim 33, wherein when the bearer frame consists of multiple code groups, parsing the bearer frame and extracting the content carried by the bearer frame includes at least one of the following: The third data code group in the bearer frame is parsed, and if the parsing result is not the preamble content, the parsing result is determined to be OAM information; The fifth data code group in the bearer frame is parsed, and if the parsing result is not the default value, the parsing result is determined as OAM information; If the length of the bearer frame is not the specified length, extract the OAM information from the bearer frame; The decision on whether to combine the parsed OAM information is based on the agreed-upon rules.

38. An electronic device comprising: processor; Memory used to store the processor's executable instructions; The processor is configured to execute the instructions to implement the method as described in any one of claims 31 to 37.

39. A computer-readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the method as described in any one of claims 31 to 37.

40. A computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of the method as claimed in any one of claims 31 to 37.

Images