Data transmission method, and device and storage medium

Abstract

Provided in the present application are a data transmission method, and a device and a storage medium. The data transmission method, which is applied to a first communication device, comprises: by means of a first channel layer, performing rate adaptation on a service signal flow in a signal adaptation manner, so as to obtain a corresponding service signal frame; by means of the first channel layer, inserting into the service signal frame first information using a first coding format; by means of a first section layer, dividing a slot in a slot division manner, so as to obtain a corresponding slot granularity; and by means of the first section layer, selecting a corresponding section instance according to the slot granularity and transmitting same to a second communication device.

Description

Data transmission method, device and storage medium Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a data transmission method, device and storage medium. Background Art

[0002] The Metro Transport Network (MTN) is a proposed next-generation metropolitan area transport network standard system used to implement the Time Division Multiplexing (TDM) layer network in the IEEE Ethernet protocol stack. The MTN segment layer reuses the Flexible Ethernet (FlexE) processing logic of the Optical Internetworking Forum (OIF). The interface rates currently supported by MTN are basically consistent with the range described in OIF FlexE 2.2, that is, supporting rates from 50GE to 400GE. The MTN client layer can support standardized Ethernet interface rates (typically including 10GE, 25GE, 50GE, 100GE, 200GE, and 400GE).

[0003] As Ethernet interface rates continue to accelerate, the IEEE is developing the B400G rate interface for 800GE / 1.6TE. MTNs need to support Beyond 400G (B400G) Ethernet client layer signals. Meanwhile, the OIF has initiated work on 800GE / 1.6TE FlexE, requiring MTNs to support B400G MTN interface rates and MTN channel processing. However, current technologies for MTN channel layer client signal adaptation, channel switching, and segment layer adaptation are not yet capable of supporting B400G processing.

[0004] Summary of the Invention

[0005] In view of this, the embodiments of the present application provide a data transmission method, device and storage medium, which realize the processing function of B400G service signals, channel rates and interface rates.

[0006] An embodiment of the present application provides a data transmission method, applied to a first communication device, wherein the first communication device includes: a first channel layer and a first segment layer; wherein the first channel layer and the first segment layer support a first interface rate greater than 400G; the method includes:

[0007] Performing rate adaptation on the service signal stream using a signal adaptation method through the first channel layer to obtain a corresponding service signal frame;

[0008] inserting first information in a first coding format into the service signal frame through the first channel layer;

[0009] Dividing the time slots by using the time slot division method through the first segment layer to obtain corresponding time slot granularity;

[0010] The corresponding segment layer instance is selected and transmitted to the second communication device according to the time slot granularity through the first segment layer.

[0011] An embodiment of the present application provides a communication device, comprising: a memory, and one or more processors;

[0012] The memory is configured to store one or more programs;

[0013] When the one or more programs are executed by the one or more processors, the one or more processors implement the method described in any one of the above embodiments.

[0014] An embodiment of the present application provides a storage medium storing a computer program. When the computer program is executed by a processor, the method described in any one of the above embodiments is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] FIG1 is a schematic diagram of the architecture of a B400G MTN system provided in an embodiment of the present application;

[0016] FIG2 is a flow chart of a data transmission method provided in an embodiment of the present application;

[0017] FIG3 is a schematic diagram of a configuration of a 64 / 66b code block provided in an embodiment of the present application;

[0018] FIG4 is a schematic diagram of a configuration of a 256 / 257b encoding format provided in an embodiment of the present application;

[0019] FIG5 is a schematic diagram of a configuration of a coding format of a 256 / 257b idle code block provided in an embodiment of the present application;

[0020] FIG6 is a schematic diagram of a configuration of a coding format of a 256 / 257b OAM code block provided in an embodiment of the present application;

[0021] FIG7 is a schematic diagram of a static configuration method for MTN channel layer compatible coding provided in an embodiment of the present application;

[0022] FIG8 is a schematic diagram of a second static configuration method for MTN channel layer compatible coding provided in an embodiment of the present application;

[0023] FIG9 is a schematic diagram of a time slot division method of an MTN B400G L*64B coding section layer provided in an embodiment of the present application;

[0024] FIG10 is a schematic diagram of an MTN B400G L*64B coded hierarchical channel switching according to an embodiment of the present application;

[0025] FIG11 is a schematic diagram of an MTN B400G hierarchical instance provided in an embodiment of the present application;

[0026] FIG12 is a schematic diagram of an MTN B400G deactivation instance filled with an L*64B coding pattern provided in an embodiment of the present application;

[0027] FIG13 is a schematic diagram of MTN B400G segment layer instance activation / deactivation and Ethernet energy saving coordinated switching provided by an embodiment of the present application;

[0028] FIG14 is a schematic diagram of an MTN B400G fault filling L*64B coding pattern provided by an embodiment of the present application;

[0029] FIG15 is a schematic diagram of a newly defined coding type of MTN 800G 256 / 257b provided in an embodiment of the present application;

[0030] FIG16 is a schematic diagram of a newly defined IDLE and OAM coding for MTN 800G 256 / 257b provided in an embodiment of the present application;

[0031] FIG17 is a schematic diagram of an MTN 800G 256 / 257b Error and fault filling pattern provided by an embodiment of the present application;

[0032] FIG18 is a schematic diagram of an MTN 800G Instance deactivation or Ethernet interface energy saving shutdown bus triggering time slot table adjustment switching provided by an embodiment of the present application;

[0033] FIG19 is a schematic diagram of a newly defined coding type of MTN 1.6T 256 / 257b provided in an embodiment of the present application;

[0034] FIG20 is a schematic diagram of a newly defined IDLE and OAM coding for MTN 1.6T 256 / 257b provided in an embodiment of the present application;

[0035] FIG21 is a schematic diagram of an MTN B400G 256 / 257b coded hierarchical channel switching according to an embodiment of the present application;

[0036] FIG22 is a schematic diagram of a 256 / 257b segment layer coding of an MTN 800G 20G timeslot granularity provided by an embodiment of the present application;

[0037] FIG23 is a schematic diagram of an MTN B400G hierarchical instance compatibility process provided by an embodiment of the present application;

[0038] FIG24 is a schematic diagram of a newly defined IDLE and OAM coding for MTN 1.6T 512 / 514b provided in an embodiment of the present application;

[0039] FIG25 is a schematic diagram of an MTN B400G 256 / 257b coded hierarchical channel switching according to an embodiment of the present application;

[0040] FIG26 is a schematic diagram of an MTN B400G multi-layered instance compatibility process provided by an embodiment of the present application;

[0041] FIG27 is a structural block diagram of a data transmission device provided in an embodiment of the present application;

[0042] Figure 28 is a structural diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0043] The following describes the embodiments of the present application in conjunction with the accompanying drawings. The following describes the present application in conjunction with the accompanying drawings. The examples are only used to explain the present application and are not used to limit the scope of the present application.

[0044] The data transmission method in the embodiments of the present application is applied to a first communication device, where the first communication device is an MTN device serving as a source, and the second communication device is an MTN device serving as a sink. Furthermore, both the source and sink MTN devices include a first path layer and a first segment layer; wherein the first path layer and the first segment layer support a first interface rate greater than 400G.

[0045] For example, the architecture of the MTN system is described by taking the case where the first channel layer is a B400G channel layer and the first segment layer is a B400G segment layer as an example. Figure 1 is a schematic diagram of the architecture of a B400G MTN system provided in an embodiment of the present application. As shown in Figure 1, new functions such as B400G client signal adaptation, B400G channel processing, B400G segment layer processing, and B400G segment layer adaptation are added to the MTN layer network of the MTN system to support carrying B400G client signals, supporting MTN channels at B400G rates, operation administration and maintenance (OAM) and switching, and supporting processing solutions at B400G segment layer rates.

[0046] In one embodiment, Figure 2 is a flowchart of a data transmission method provided by an embodiment of the present application. This embodiment is applied to support greater than 400G client signal access adaptation, MTN channels, OAM, and switching at rates greater than 400G. This embodiment can be executed by a first communications device acting as a source. As shown in Figure 2, this embodiment includes: S110-S140.

[0047] S110 . Perform rate adaptation on the service signal stream by using a signal adaptation method through the first channel layer to obtain a corresponding service signal frame.

[0048] S120. Insert first information in a first coding format into a service signal frame through a first channel layer.

[0049] Exemplarily, the first encoding format refers to the 256 / 257b encoding format; the first information may be OAM information.

[0050] S130 , dividing the time slots by using a time slot division method through the first section layer to obtain corresponding time slot granularity.

[0051] S140 . Select and transmit a corresponding segment layer instance to the second communication device according to the time slot granularity through the first segment layer.

[0052] The first communication device as the source end adopts a signal adaptation method to rate adapt the service signal streams of different rates to obtain the corresponding service signal frame, and inserts the first information using the first coding format into the service signal frame through the first channel layer; then the time slot division method is adopted through the first segment layer to obtain different time slot granularities, and the corresponding segment layer instance is selected and transmitted to the second communication device as the host end according to the time slot granularity.

[0053] In one embodiment, the signal adaptation method includes at least one of the following: signal adaptation of a single-channel first interface rate; signal adaptation of at least two-channel second interface rates; wherein the second interface rate is less than the first interface rate. The signal of the first interface rate refers to a signal with a single-channel rate of B400G. For example, the first interface rate may be 800G or 1.6T; the signal of the second interface rate refers to a signal with a single-channel rate of 400G, such as K-channel 400G signals, where K is an integer greater than 1. In an embodiment, the method for access adaptation of B400G client signals may include multiple signal adaptation methods, including but not limited to single-channel B400G or K-channel 400G signal adaptation, and K is not less than 1. The encoding format can adopt L*64B encoding format signal adaptation, where when L is 1, it is compatible with the currently defined 64 / 66b signal adaptation method. Except that the rate exceeds 400G, other processes are basically the same as the existing scheme, as shown in the transcoding position option O2 in Figure 1; when L is 4, the encoding format is 256 / 257b encoding format, when L is 8, it is 512 / 514b encoding format, and so on, as shown in the transcoding position option O1 in Figure 1.

[0054] In one embodiment, a service signal stream includes a service signal frame, which includes a first number of first-type code blocks. The code block types of the first-type code blocks include at least one of the following: an idle code block; a local fault code block related to fault indication; a remote fault code block related to fault indication; a low power idle (LPI) code block; an error code block; a sequence code block; and a padding code block. Exemplarily, the first-type code block may be a 64 / 66b code block. When the first number is a positive integer greater than 1, transcoding of 64 / 66b encoded signals and L*64B encoded signals may occur. Conventional transcoding utilizes an existing general solution. Specific control code blocks include an idle code block (IDLE Block) required for rate adaptation, a local fault code block (LF Block) related to fault indication, a remote fault code block (RF Block) related to fault indication, a low power idle (LPI) code block, an error code block, an operation and maintenance code block (OAM Block), and a padding code block. Figure 3 is a configuration diagram of a 64 / 66b code block provided by an embodiment of the present application. 64 / 66b code blocks can be optimized, adapted, and transcoded to simplify the transcoding process. As shown in Figure 3, the first row is the general format of a 66b code block. A leading 10 indicates a control block. The second row is the general format of a 66b control code block. A leading 10 indicates a control code block. Type indicates the type of the control code block (including 0x1E and 0x4B). For a 0x1E control code block, in rows 3-6, C0-C7 indicate that there can be eight 7-bit indicators. The indicators can be Idle (abbreviated as I), Error (abbreviated as E), and LI (low power indication). For a 0x4B control code block, 0x4B is used to indicate a sequence Ordered Set code block, where the O code has been defined. 0xC is used to indicate that the Ordered Set code block is used for MTN OAM, and 0x0 is used for the above-mentioned LF or RF status indication.

[0055] In one embodiment, when a second type of code block is composed of a first number of first type code blocks, and the first number is greater than 1, the control code block is adjusted to the boundary of the first type of code block by adjusting the position of the control code block in the first type of code block and combining the rate adaptation of the first type of code block to obtain a corresponding second type of code block. Exemplarily, the second type of code block can be a 256 / 257b control code block or an L*64B control code block. When the first number L is greater than 1, the above-mentioned optimized adaptation and transcoding processing is to adjust the position of a specific control code block in the 64 / 66b code block and combining the rate adaptation of the 64 / 66b code block to adjust the specified control code block to the boundary of the L*64B encoding format to obtain a corresponding 256 / 257b control code block or an L*64B control code block, thereby simplifying the processing of the L*64B encoding format for the specified control code block.

[0056] In one embodiment, when the code blocks of the first number of code blocks of the first type are of the same code block type, all control code blocks in the first number of code blocks of the first type are adapted into a group of control code blocks, and the group of control code blocks is encoded in at least one of the following N*66B encoding formats: 64 / 66b encoding; 256 / 257b encoding; 512 / 514b encoding;

[0057] Overhead indication information is added to the coding format; wherein the overhead indication information includes at least one of the following: the code block type of the second type code block; the pattern type of the second type code block. Exemplarily, the second type code block can be an L*64B control code block. The code block type and pattern type of the second type code block are the code block type and pattern type of the L*64B control code block. L identical 64 / 66b control code blocks are adapted into a group for direct L*64B encoding, and the identification, extraction, replacement and termination processing of the specified control code block are further simplified. Since L identical 64 / 66b control code blocks constitute a group, there is a large amount of redundant information in the encoding, and the compression of the redundant information can be defined, and then the compressed space is used to add overhead indication information, including but not limited to the type and pattern type of the L*64B control code block. Figure 4 is a configuration diagram of a 256 / 257b encoding format provided in an embodiment of the present application. As shown in Figure 4, when L is 4, the encoding format is optimized 256 / 257b; when L is 8, the encoding format is optimized 512 / 514b, and so on.

[0058] In one embodiment, a method for determining the second type of code block includes:

[0059] Redefine the type header of the first first-type code block to a compatible new type; or

[0060] The control block type indicator in each first-type code block is moved to the first position, and the overhead content in each first-type code block is moved to the second position, where the first position is located before the second position, and the format or content of the first position is redefined. For example, the second position refers to the last L*56b position, and the first position refers to the first L*8b position. When the first number L is 4, there are two implementation methods for the optimized 256 / 257b encoding: Encoding Method 1 redefines the type header (BTF: Block Type, consisting of a 4-bit first nibble F and a 4-bit second nibble S) of the first 64 / 66b control code block to a type (N-BTF: New Block Type) that meets the Hamming distance; Encoding Method 2 directly moves the content of the control block (CB: Control Block) to the last L*56b position, and uses the first L*8b space as the overhead space for the entire encoding. The first L*8b space can include type indication information, as shown in Figure 4.

[0061] In one embodiment, the redefined type header includes: a redefined first half byte and a redefined second half byte. The first half byte refers to the first half byte F, and the second half byte refers to the second half node S. For the optimized new type header, when the first number L is 4, a new 256 / 257b forwarding scheme for the first half byte F and the second half byte S can be defined; or it can be based on the existing 256 / 257b scheme but using undefined or currently agreed invalid values. For example, for the 256 / 257b type indication, the control block is included, but the first half byte F is 1111 (indicating that it is composed of 4 data code blocks); or for the 256 / 257b first half byte, at least the first position indication is 0 (control code block), but the control code block type (CB Type) of the second half byte S is a currently undefined value. When L is 8, the method is the same, and so on.

[0062] In one embodiment, when the first type code block is an idle code block and the service signal flow does not match the rate of the first channel layer, the idle code block is added or deleted based on the newly defined idle coding format as a basic unit;

[0063] Among them, the redefined idle coding format includes: the first coding format in which the code block type in the type indication information is an idle code block; the first coding format in which the code block type in the overhead indication information is an idle code block. For the L*64b coding format and L is greater than 1, the idle coding format after optimization is used as the basic unit for rate adaptation. When L is 4, a new control type or an optimized 256 / 257b coding format with the type indication of the idle type in the overhead information is defined as the new idle coding format; when L is 8, a new control type or an optimized 512 / 514b coding format with the type indication of the idle type in the overhead information is defined as the new idle coding format, and so on. When the client signal rate does not match the channel layer rate, the idle coding blocks are added or deleted based on the defined idle coding format as the basic unit to achieve accurate rate matching. Figure 5 is a configuration diagram of a coding format for a 256 / 257b idle code block provided in an embodiment of the present application. As shown in Figure 5, two coding modes are included, namely IDLE coding mode 1 and IDLE coding mode 2, and CB0-CB3 shown in Figure 4 are replaced with the corresponding IDLE.

[0064] In one embodiment, the first path layer includes at least one of the following functions: OAM overhead insertion at the source end; OAM overhead termination at the sink end; non-intrusive monitoring overhead processing at intermediate nodes; and path switching at the first interface rate as the segment layer interface. If the first path layer is a B400G path layer, the B400G path layer includes the following functions: OAM overhead insertion at the source end, OAM overhead termination at the sink end, optional non-intrusive monitoring overhead processing at intermediate nodes, and B400G path switching.

[0065] In one embodiment, the first channel layer supports channel OAM processing; channel OAM processing includes at least one of the following functions: OAM encoding format; OAM transceiver processing; non-intrusive monitoring. B400G channel OAM processing includes functions such as OAM encoding format, OAM transceiver processing, and non-intrusive monitoring. The OAM encoding format adapts to the B400G channel encoding format and corresponds to the B400G adaptation signal encoding format. The B400G channel layer encoding format can use L*64b encoding. When L is 1, the defined OAM code block type is used, which is compatible with the G.8310 method; when L is 4, 4 consecutive 64 / 66b OAM encoding blocks can be specified to form a 256 / 257b encoding block as the encoding format of the B400G channel layer OAM overhead, and so on.

[0066] In one embodiment, the OAM function is processed by identifying the OAM type field of the first encoding format. The MTN channel source end, sink end or optional intermediate node processes the OAM function by identifying the OAM type field of the defined L*64B encoding format.

[0067] In one embodiment, the method of inserting the first information into the service signal frame through the first channel layer includes one of the following: using an OAM code block of the first coding format to identify and define to replace the existing idle code block of the first coding format; inserting the OAM code block in the coding frame gap and then deleting the idle code block; after deleting the OAM code block, filling the idle code block; inserting the OAM code block in real time at any position of the second type code block according to the insertion interval of the OAM code block. Exemplarily, the first coding format is the 256 / 257b coding format. The channel layer OAM code insertion can adopt a method compatible with the existing scheme to identify the 64 / 66b OAM code in the L*64B coding format, or directly identify the OAM code of the defined L*64B coding format, and then replace the existing L*64B idle code or forcibly insert the OAM code in the coding frame gap and then delete the idle code; the OAM code termination is simply to delete the OAM code and then fill the idle code or to add the idle code after forcibly deleting it. For the OAM encoding in the defined L*64B encoding format, the characteristics of the encoding format can also be utilized to insert the OAM in real time at any L*64B position according to the OAM insertion interval, thereby reducing the OAM insertion position changes caused by waiting for L*64 idle encoding or frame intervals.

[0068] In one embodiment, when the first type of code block is an OAM code block, the method for determining the second type of code block further includes: merging the payload bits in the first number of first type code blocks, and merging the overhead bits in the first number of first type code blocks. For B400G MTN channel OAM transceiver, as L in the coding format increases, the bandwidth of OAM increases accordingly, and the OAM overhead definition and transceiver processing can be optimized, and the OAM information can be uniformly defined. Figure 6 is a configuration diagram of a coding format of a 256 / 257bOAM code block provided in an embodiment of the present application. Assuming that the first number is 4, as shown in Figure 6, it includes 3 OAM coding methods, among which OAM coding method 1 and OAM coding method 2 are as shown in Figure 4 above, replacing the corresponding CB0-CB3 with the corresponding OAM0-OAM3; OAM coding method 3 merges 4 OAM code blocks (OAM0-OAM3) and merges the overhead bits of the 4 OAM code blocks to obtain the corresponding Overhead (occupying 32 bits).

[0069] In one embodiment, the product of the timeslot granularity and the number of timeslots satisfies the total rate of the first segment layer. B400G MTN channel switching is greater than 400G channel switching. For channel rates greater than 400G, a larger timeslot granularity can be used to configure the channel timeslot allocation table and perform channel switching compared to existing solutions. The timeslot granularity and the number of timeslots satisfy the mathematical relationship that the product of the two equals the B400G total segment layer rate (i.e., the relationship between the timeslot granularity G, the number of timeslots N, and the B400G segment layer total rate R is G*N=R).

[0070] In one embodiment, the configuration method for encoding a first number of first-type code blocks into second-type code blocks includes: using the product value between the first number and the number of bit repetitions for cyclic interleaving; and using a continuous first number of first-type code blocks. The time slot granularity can be compatible with the coding format. For the L*64B coding format, when L is greater than 1, the coding format is compatible with the 64 / 66b coding by selecting L 64 / 66b code blocks according to the configuration to be encoded into the L*64B coding format. As for how to select L 64 / 66b codes into the L*64B format, it can be technically specified through configuration, and the MTN channel can be consistent in end-to-end agreement. When L is 4, a 20Gbps time slot granularity can be selected, and when L is 8, an 80Gbps time slot granularity can be selected. Figure 7 is a schematic diagram of a first static configuration method for MTN channel layer compatible coding provided in an embodiment of the present application; Figure 8 is a schematic diagram of a second static configuration method for MTN channel layer compatible coding provided in an embodiment of the present application. As shown in FIG7 , the configuration is performed in a manner of L*1023 cyclic interleaving. As shown in FIG8 , the configuration is performed in a manner of L consecutive 64 / 66 bits.

[0071] In one embodiment, the data transmission method further includes: determining a corresponding number of time slots according to the time slot granularity;

[0072] Among them, the product value between the number of time slots and the time slot granularity is equal to the interface capacity of the first segment layer. If based on the coding format, a method that is friendly to the Ethernet segment layer rate can also be selected. In this case, a new MTN time slot division method needs to be defined, such as a time slot granularity of 25Gbps, 50Gbps or 100Gbps. Figure 9 is a schematic diagram of an MTN B400G L*64B coding segment layer time slot division method provided by an embodiment of the present application. Similar to the MTN segment layer, the number of time slots is selected according to the time slot granularity to meet the relationship that the product of the number of time slots and the time slot granularity is equal to the MTN segment layer interface capacity. For example, for an 800G segment layer interface, if 100G time slot granularity is selected, the number of time slots is 8, while for a 1.6T segment layer interface with 100G time slot granularity, the number of time slots is 16; and the selection of the repetition period M is determined according to the overhead budget, as shown in Figure 9.

[0073] In one embodiment, the first channel layer uses a hierarchical switching path when switching channels of different rate levels, and supports the switching of multiple rates and coding formats. Figure 10 is a schematic diagram of an MTN B400G L*64B coded hierarchical channel switching provided by an embodiment of the present application. B400G channel switching of channels of different rate levels can also use a hierarchical switching path and support the switching of multiple rates and coding formats. For example, the first level is an existing 64 / 66b coded switching path less than or equal to 400G. After completing the 400G and lower rate channel switching based on 5G time slot granularity, the 64 / 66b coding is transcoded into 256 / 257 coding, and further based on 20G time slot granularity, channel switching of 400G and higher rates is performed, as shown in Figure 10.

[0074] In one embodiment, the first segment layer includes at least one of the following functions: path layer and segment layer rate adaptation; segment layer timeslot mapping; and segment layer service layer adaptation. B400G segment layer processing includes B400G path layer and segment layer rate adaptation, segment layer timeslot mapping, and segment layer service layer adaptation.

[0075] In one embodiment, the rate adaptation method between the first channel layer and the first segment layer includes: adopting a signal adaptation method of the first interface rate; adopting different coding formats for rate adaptation. The B400G channel layer and segment layer rate adaptation can follow the above-mentioned B400G client signal rate adaptation method, or adopt different coding formats for rate adaptation, such as the client signal rate using a 64 / 66b coding format, while the channel layer and segment layer rate adaptation use a 256 / 257b coding format. Rate adaptation needs to consider inserting other overhead for the segment layer service layer to reserve position and space, and the reservation method is to fill idle coding. The rate adaptation here can also be completed together with the client signal rate adaptation.

[0076] In one embodiment, the first segment layer unifies and simplifies segment layer support for the first interface rate by instantiating, selecting a second number of segment layer instances with a third interface rate;

[0077] The time slot granularity of the first segment layer is the same as that of the first channel layer, or the rate level corresponding to the time slot granularity of the first segment layer is greater than the rate level corresponding to the time slot granularity of the first channel layer. Figure 11 is a schematic diagram of an MTN B400G hierarchical Instance provided by an embodiment of the present application. The B400G segment layer unifies and simplifies the segment layer's support for B400G through a similar MTN instance, and can select an MTN segment layer instance with an M*100G rate. When M is 1, it is compatible with the G.8312 solution; when M is 2, it can match the physical channel rate of 200G rate; when M is 4, it can match the IEEE 802.3 physical coding sublayer (PCS) 400G rate. The segment layer time slot granularity can be selected to be the same as the channel layer time slot granularity, or only the time slot granularity of the higher rate level can be selected. When M is greater than 1, the MTN B400G segment layer can support hierarchical instances compatible with existing 100G instances, as shown in Figure 11.

[0078] In one embodiment, the padding code block supports carrying auxiliary overhead for segment layer instance identification through a redefined code block. The redefinition of the padding code block includes redefining the original padding code block format and introducing a new padding code block format.

[0079] In one embodiment, the first segment layer supports dynamic activation and deactivation of segment layer instances. The B400G segment layer supports dynamic activation and deactivation of instances, enabling flexible adjustment of segment layer rates. Activation and deactivation can be combined with Energy-Efficient Ethernet (EEE) technology. This activation / deactivation functionality can be accomplished through the MTN management and control interface and newly added MTN negotiation signaling.

[0080] In one embodiment, the data transmission method further includes: transmitting the activated segment layer instance to the second communication device through the first segment layer; wherein the segment layer instance carries the instance identifier and service data; the filling pattern of the segment layer instance includes: at least one of an error code block and an idle code block. Figure 12 is a schematic diagram of an MTN B400G deactivation Instance filling L*64B coding pattern provided by an embodiment of the present application. The activation / deactivation of the B400G segment layer Instance can be distinguished by transmitting a specific Instance identifier (Identify, ID) and data. The filled data pattern can be a specific L*64B coding format, typically including a combination of M+N Error coding and IDLE coding. For example, when L is 1, a 64 / 66b error code block (64 / 66b Error Block) compatible with G.8312 is used. When L is 4, a new 256 / 257b error code block type is defined for filling. In order to support rate adaptation, the filling pattern can be filled with error code blocks (EB: Error Block) and idle code blocks interleaved, as shown in Figure 12.

[0081] In one embodiment, when the service traffic at the first segment layer is less than the preset energy-saving traffic, the LPI signal is replaced with overhead signaling at the first segment layer to trigger the first segment layer to switch timeslots. Figure 13 is a schematic diagram of a coordinated switching of MTN B400G segment layer instance activation / deactivation and Ethernet energy saving, provided by an embodiment of the present application. The capability negotiation signaling for B400G segment layer interface instance activation / deactivation can be extended using the Link Layer Discovery Protocol (LLDP). Combined with Ethernet energy-saving technology, the LPI can be replaced with overhead signaling. Combined with the MTN segment layer timeslot table switching mechanism, dynamic switching and conditional lossless switching can be achieved. When the service traffic at the segment layer decreases to a level that supports energy saving, the LPI signal is replaced with the MTN segment layer overhead signal, thereby triggering the modification and switching of the segment layer timeslot table, completing the dynamic switching of the segment layer timeslot table configuration along with the LPI signal. When the switching time between the LPI and timeslot table meets the lossless switching time requirement, energy-saving instance activation / deactivation services can be achieved without loss. The coordinated process is shown in Figure 13.

[0082] In one embodiment, the data transmission method further includes: redefining the fault overhead format and the fault coding format for the first coding format through the first segment layer to indicate the fault; wherein the filling pattern corresponding to the fault includes: at least one of an idle code block and an error code block. Figure 14 is a schematic diagram of an MTN B400G fault filling L*64B coding pattern provided in an embodiment of the present application. The B400G segment layer supports fault notification. The difference from the existing method is mainly that the fault overhead format and the fault coding format filled with it are newly defined for different coding formats. The filling pattern can adopt a specific L*66b coding format, typically including a combination of M+N Error coding and IDLE coding. For example, when L is 1, a 64 / 66b error code block (64 / 66b Error Block) compatible with G.8312 is used. When L is 4, a new 256 / 257b error code block type is defined for filling. To support rate adaptation, the filling pattern can adopt a local fault code block (LF) and idle code block interleaved filling method, as shown in Figure 14.

[0083] In Example 1, the data transmission process of an 800G interface supporting 20G time slot granularity of MTN is described. Figure 15 is a schematic diagram of a newly defined coding type of MTN 800G 256 / 257b provided in an embodiment of the present application; Figure 16 is a schematic diagram of a newly defined IDLE and OAM coding of MTN 800G 256 / 257b provided in an embodiment of the present application; Figure 17 is a schematic diagram of an MTN 800G 256 / 257b Error and fault filling pattern provided in an embodiment of the present application; Figure 18 is a schematic diagram of an MTN 800G Instance deactivation or Ethernet interface energy saving shutdown bus triggering time slot table adjustment switching provided in an embodiment of the present application. As shown in Figure 18, the following steps are included:

[0084] Step 1: Add 800G MTN segment layer interfaces to MTN equipment, and add MTN channel switching, channel OAM, and corresponding rate adaptation functions at 800G segment layer rates.

[0085] Step 2: Both the MTN channel layer and the section layer use the 4*64B (L*64B, when L is 4, corresponds to 256 / 257b) encoding format to define a 20G time slot granularity compatible with the current MTN. The control code block encoding format adopts method 1. The new type header can directly use the pre-configured 64 / 66b control code block type header but the uncompressed value (for example, 0xIE and 0x4B will not be repeated with the normal 256 / 257b encoding, and therefore can be normally recognized by the MTN channel layer), as shown in Figure 15.

[0086] Step 3: The MTN channel layer uses the defined 256 / 256b IDLE code to perform rate adaptation for customer services and inserts the defined 256 / 257b OAM code to transmit the channel layer's OAM information. The specific information format can directly follow the existing definition in ITU-T G.8312, as shown in Figure 16.

[0087] Step 4: The MTN segment layer divides time slots into four 1023*20 cycles, with a time slot granularity of 20G. For the 4*200G 800G interface physical layer solution, a 200G rate segment layer instance solution is selected to facilitate Ethernet energy-saving collaboration at the 200G bus level.

[0088] Step 5: The MTN segment layer fills the deactivated instance with an 8+1 Error code and an IDLE code pattern, and fills the faulty segment layer with an 8+1 LF code and an IDLE code pattern, as shown in Figure 17.

[0089] Step 6: The MTN section layer can use the current MTN time slot table switching process to coordinate the deactivation of the instance and the section layer overhead to adjust the MTN time slot capacity. That is, when the source MTN section layer confirms that the instance can be deactivated, or energy saving can be achieved by shutting down a certain section layer hardware interface link, when the source MTN section layer is about to deactivate the instance, or is about to shut down the instance corresponding to a certain bus due to energy saving, the source MTN implements dynamic MTN section layer time slot capacity adjustment by continuing to use the existing MTN section layer time slot table switching overhead (time slot table request CR, time slot table response CA and time slot table switching C). The process is shown in Figure 18.

[0090] In Example 2, the data transmission process is described using an MTN 1.6T interface supporting 50G time slot granularity. Figure 19 is a schematic diagram of a newly defined MTN 1.6T 256 / 257b encoding type, provided in this embodiment of the present application; Figure 20 is a schematic diagram of a newly defined MTN 1.6T 256 / 257b IDLE and OAM encoding, provided in this embodiment of the present application.

[0091] Step 1: Add a 1.6T MTN segment layer interface to the MTN equipment, and add MTN channel switching, channel OAM, and corresponding rate adaptation functions at the 1.6T segment layer rate.

[0092] Step 2: Both the MTN channel layer and the section layer adopt the 256 / 257b encoding format to define a 50G time slot granularity compatible with the current MTN. The control code block encoding format adopts method 2. The new type header can directly use the pre-configured 64 / 66b control code block type header but the uncompressed value (for example, 0xFE and 0xFB will not be repeated with the normal 256 / 257b encoding, so they can be normally recognized by the MTN channel layer). Other unused overhead is reserved as a field, as shown in Figure 19.

[0093] Step 3: The MTN channel layer uses the defined 256 / 256b IDLE code to perform rate adaptation for customer services and inserts the defined 256 / 257b OAM code to transmit the channel layer's OAM information. Since the 256 / 257b OAM overhead code can be directly recognized, the OAM format can be redefined to more efficiently utilize the OAM overhead space, as shown in Figure 20.

[0094] Step 4: The MTN segment layer divides the time slots into 639 (using the same overhead ratio as the current MTN segment layer: 1023*20 / 32=639)*32 cycles, with a time slot granularity of 50G. For the 8*200G 800G interface physical layer solution, a 200G rate segment layer instance solution is selected to facilitate Ethernet energy-saving collaboration at the 200G bus level.

[0095] Step 5: The MTN segment layer fills the deactivated instance with an 8+1 Error code and an IDLE code pattern, and fills the faulty segment layer with an 8+1 LF code and an IDLE code pattern, as shown in Figure 17.

[0096] In Example 3, the data transmission process is described using MTN's hybrid networking support for 5G and 20G granularity. Figure 21 is a schematic diagram of MTN B400G 256 / 257b coded hierarchical channel switching, provided in an embodiment of this application; Figure 22 is a schematic diagram of MTN 800G 20G time slot granular 256 / 257b segment layer coding, provided in an embodiment of this application; and Figure 23 is a schematic diagram of MTN B400G hierarchical instance compatibility processing, provided in an embodiment of this application.

[0097] Step 1: Add 800G MTN segment layer interfaces to MTN equipment, add MTN channel switching, channel OAM, and corresponding rate adaptation functions at 800G segment layer rates, and be compatible with current segment layer interfaces not exceeding 400G.

[0098] Step 2: Both the MTN channel layer and the section layer adopt the 256 / 257b encoding format to define a 20G time slot granularity that is compatible with the current MTN and is also compatible with the current MTN 5G time slot granularity. The control code block encoding format adopts method 1. The new type header can directly use the pre-configured 64 / 66b control code block type header but the uncompressed value, as shown in Figure 15.

[0099] Step 3: MTN channel switching supports hierarchical timeslot granularity and channel switching. B400G signals encoded with 256 / 257b are transmitted and received via the B400G interface. Service signals that do not require 5G granularity channel switching can directly be switched with 256 / 257b 20-timeslot granularity, without transcoding to 64 / 66b for 5G timeslot granularity channel switching. For service signals that require compatibility with existing 5G timeslot granularity channel switching, 256 / 257b is transcoded back to 64 / 66b at the MTN B400G segment layer, followed by channel switching with 5G timeslot granularity. After channel switching, 64 / 66b is transcoded back to 256 / 257b, and signals continue to be transmitted and received via the B400G segment layer using 256 / 257b encoding, as shown in Figure 21.

[0100] Step 4: The MTN channel exchange coding process can adopt a coding format compatible with the 5G time slot granule, that is, four consecutive 64 / 66b of the 5G time slot granule are encoded into one 256 / 257b to form a 20G time slot granule, as shown in FIG22.

[0101] Step 5: For the MTN B400G segment layer instance, a 200G rate is selected. This can be processed in the same hierarchical manner as MTN's existing 100G instance. The B400G segment layer 200G instance can be constructed by interleaving 2*100G existing MTN instances to form a hierarchical instance mapping relationship, as shown in Figure 23.

[0102] In Example 4, the data transmission process is described using the 512 / 514b encoding format for the MTN 1.6T interface supporting 50G time slot granularity. Figure 24 is a schematic diagram of newly defined IDLE and OAM encoding for MTN 1.6T 512 / 514b, provided in an embodiment of this application; Figure 25 is a schematic diagram of hierarchical channel switching for MTN B400G 256 / 257b encoding, provided in an embodiment of this application; and Figure 26 is a schematic diagram of multi-layered instance compatibility processing for MTN B400G, provided in an embodiment of this application.

[0103] Step 1: Except for the encoding format, other steps are the same as those in Example 2.

[0104] Step 2: Both the MTN channel layer and the segment layer use the 512 / 514b encoding format. The encoding format defined by 256 / 257b can be directly transcoded into the 512 / 514b encoding format. The transcoding rules are the same as the existing solution, except that 256 / 257b contains a specified defined encoding format, as shown in Figure 24.

[0105] Step 3: MTN channel switching supports hierarchical time slot granularity and channel switching. For B400G signals with 512 / 514b encoding, they are sent and received through the B400G interface. When channel switching in the 256 / 257b encoding format is not required, MTN channel switching in the 512 / 514b encoding format is directly performed without transcoding to the 256 / 267b encoding format. Conversely, MTN channel switching can be performed by transcoding to the 256 / 257b encoding format first. Similarly, for service signals that do not require MTN channel switching in the 64 / 66b encoding format, channel switching can be performed based on the transcoded 256 / 257b encoding format without further transcoding processing to restore to the 64 / 66b encoding format for channel switching. For service signals that require channel switching compatible with existing 5G time slot granularity, the MTN B400G segment layer first transcodes 512 / 514b to 256 / 257b, then further transcodes 256 / 257b back to 64 / 66b, and then performs channel switching for 5G time slot granularity. After channel switching is complete, 64 / 66b is transcoded to 256 / 257b, and further transcoded to 512 / 514b. Signals are then sent and received through the B400G segment layer using 512 / 514b encoding, as shown in Figure 25.

[0106] Step 4: For the MTN B400G segment layer 512 / 514b encoded instances, a 400G rate is selected. This is compatible with the B400G 256 / 257b encoded 200G instance rate and further combines with MTN's existing 64 / 66b encoded 100G instances to form a multi-layered processing approach. The B400G segment layer 512 / 514b encoded instance can be constructed by interleaving two 256 / 257b encoded 200G instances. Furthermore, the B400G segment layer 256 / 257b encoded 200G instance can be interleaved by interleaving two 64 / 66b encoded 100G instances, forming a multi-layered instance mapping relationship, as shown in Figure 26.

[0107] In one embodiment, Figure 27 is a block diagram of a data transmission apparatus provided in an embodiment of the present application. This embodiment is applied to a first communication device. As shown in Figure 27, the data transmission apparatus in this embodiment includes: a rate adaptation module 210, an insertion module 220, a division module 230, and a transmission module 240.

[0108] The rate adaptation module 210 is configured to perform rate adaptation on the service signal flow by using a signal adaptation method through the first channel layer to obtain a corresponding service signal frame.

[0109] The inserting module 220 is configured to insert first information in a first coding format into the service signal frame through the first channel layer.

[0110] The division module 230 is configured to divide the time slots by using the time slot division method through the first section layer to obtain corresponding time slot granularity.

[0111] The transmission module 240 is configured to select and transmit the corresponding segment layer instance to the second communication device according to the time slot granularity through the first segment layer.

[0112] In one embodiment, the signal adaptation method includes at least one of the following: signal adaptation of a single first interface rate; signal adaptation of at least two second interface rates; wherein the second interface rate is lower than the first interface rate.

[0113] In one embodiment, the service signal stream includes a service signal frame, which includes a first number of first-type code blocks; the code block type of the first-type code block includes at least one of the following: an idle code block; a local fault code block related to a fault indication; a remote fault code block related to a fault indication; a low power indication LPI code block; an error code block; a sequence code block; and a filling code block.

[0114] In one embodiment, when the second type code block is composed of a first number of first type code blocks and the first number is greater than 1, the control code block is adjusted to the boundary of the first type code block by adjusting the position of the control code block in the first type code block and combining the rate adaptation of the first type code block to obtain the corresponding second type code block.

[0115] In one embodiment, when the code blocks of the first number of code blocks of the first type are of the same code block type, all control code blocks in the first number of code blocks of the first type are adapted into a group of control code blocks, and the group of control code blocks is encoded using at least one of the following N*66B encoding formats: 64 / 66b encoding; 256 / 257b encoding; 512 / 514b encoding;

[0116] Overhead indication information is added to the coding format; wherein the overhead indication information includes at least one of the following: a code block type of the second type code block; and a pattern type of the second type code block.

[0117] In one embodiment, a method for determining the second type of code block includes:

[0118] Redefine the type header of the first first-type code block to a compatible new type; or

[0119] The control code block type indicator in each first type code block is moved to a first position, and the overhead content in each first type code block is moved to a second position, wherein the first position is located before the second position, and the format or content of the first position is redefined.

[0120] In one embodiment, the redefined type header includes: a redefined first nibble and a redefined second nibble.

[0121] In one embodiment, when the first type code block is an idle code block and the service signal flow does not match the rate of the first channel layer, the idle code block is added or deleted based on the newly defined idle coding format as a basic unit;

[0122] The redefined idle coding formats include: a first coding format in which the code block type in the type indication information is an idle code block; and a first coding format in which the code block type in the overhead indication information is an idle code block.

[0123] In one embodiment, the first channel layer includes at least one of the following functions: source end insertion of OAM overhead; sink end termination of OAM overhead; intermediate node non-intrusive monitoring of overhead; and channel switching at the first interface rate as the segment layer interface.

[0124] In one embodiment, the first channel layer supports channel OAM processing; the channel OAM processing includes at least one of the following functions: OAM encoding format; OAM transceiver processing; and non-intrusive monitoring.

[0125] In one embodiment, the OAM function is processed by identifying an OAM type field of the first encoding format.

[0126] In one embodiment, the method of inserting the first information into the service signal frame through the first channel layer includes one of the following: using the OAM code block of the identified and defined first coding format to replace the existing idle code block of the first coding format; inserting the OAM code block in the coding frame gap and then deleting the idle code block; filling the idle code block after deleting the OAM code block; real-time insertion at any position of the second type code block according to the insertion interval of the OAM code block.

[0127] In one embodiment, when the first type code block is an OAM code block, the method for determining the second type code block further includes:

[0128] Payload bits in a first number of code blocks of the first type are combined, and overhead bits in a first number of code blocks of the first type are combined.

[0129] In one embodiment, the product of the time slot granularity and the number of time slots satisfies the total rate of the first segment layer.

[0130] In one embodiment, the configuration method of encoding the first number of first type code blocks into the second type code blocks includes: using the product value between the first number and the bit repetition number for cyclic interleaving; using a continuous first number of first type code blocks.

[0131] In one embodiment, the data transmission device further includes:

[0132] A determination module configured to determine a corresponding number of time slots according to the time slot granularity;

[0133] The product of the number of time slots and the time slot granularity is equal to the interface capacity of the first segment layer.

[0134] In one embodiment, the first channel layer adopts a hierarchical switching path when switching channels of different rate levels, and supports switching of multiple levels of rates and coding formats.

[0135] In one embodiment, the first segment layer includes at least one of the following functions: channel layer and segment layer rate adaptation; segment layer timeslot mapping and segment layer service layer adaptation.

[0136] In one embodiment, the rate adaptation method between the first channel layer and the first segment layer includes: adopting a signal adaptation method of the first interface rate; and adopting different encoding formats for rate adaptation.

[0137] In one embodiment, the first segment layer unifies and simplifies segment layer support for the first interface rate by instantiating, and selects a second number of segment layer instances with a third interface rate;

[0138] The time slot granularity of the first segment layer is the same as the time slot granularity of the first channel layer, and the rate level corresponding to the time slot granularity of the first segment layer is greater than or equal to the rate level corresponding to the time slot granularity of the first channel layer.

[0139] In one embodiment, the padding code block supports carrying auxiliary overhead for segment layer instance identification through a redefined code block. The redefinition of the padding code block includes redefining the original padding code block format and introducing a new padding code block format.

[0140] In one embodiment, the first segment layer supports dynamic activation and deactivation of segment layer instances.

[0141] In one embodiment, the data transmission device further includes:

[0142] The transmission module is also configured to transmit the activated segment layer instance to the second communication device through the first segment layer; wherein the segment layer instance carries the instance identifier and service data; the filling pattern of the segment layer instance includes: at least one of an error code block and an idle code block.

[0143] In one embodiment, when the service flow of the first segment layer is less than the preset energy-saving flow, the LPI signal is replaced with the overhead signaling of the first segment layer to trigger the first segment layer to switch the time slot.

[0144] In one embodiment, the data transmission device further includes: a redefinition module configured to redefine the fault overhead format and the fault coding format of the first coding format through the first segment layer to indicate the fault; wherein the filling pattern corresponding to the fault includes: at least one of an idle code block and an error code block.

[0145] The data transmission device provided in this embodiment is configured to implement the data transmission method applied to the first communication device in the embodiment shown in FIG2 . The implementation principle and technical effects of the data transmission device provided in this embodiment are similar and will not be described in detail here.

[0146] In one embodiment, Figure 28 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. As shown in Figure 28, the device provided in this application includes: a processor 310, a memory 320, and a communication module 330. The device may have one or more processors 310, and Figure 28 uses one processor 310 as an example. The device may have one or more memories 320, and Figure 28 uses one memory 320 as an example. The processor 310, memory 320, and communication module 330 of the device may be connected via a bus or other means, and Figure 28 uses a bus connection as an example. In this embodiment, the device may be an MTN device.

[0147] The memory 320, as a computer-readable storage medium, can be configured to store software programs, computer executable programs, and modules, such as program instructions / modules corresponding to the device of any embodiment of the present application (for example, the rate adaptation module 210, the insertion module 220, the partitioning module 230, and the transmission module 240 in the data transmission device). The memory 320 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and applications required for at least one function; the data storage area may store data created based on the use of the device, etc. In addition, the memory 320 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device. In some instances, the memory 320 may further include a memory remotely located relative to the processor 310, and these remote memories may be connected to the device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0148] In the case where the communication device is a first communication device, the device provided above can be configured to execute the data transmission method applied to the first communication device provided in any of the above embodiments, and have corresponding functions and effects.

[0149] An embodiment of the present application also provides a storage medium containing computer-executable instructions, which, when executed by a computer processor, are used to execute a data transmission method applied to a first communication device, the method comprising: performing rate adaptation on a service signal stream by using a signal adaptation method through the first channel layer to obtain a corresponding service signal frame; inserting first information using a first coding format into the service signal frame through the first channel layer; dividing time slots by using a time slot division method through the first segment layer to obtain corresponding time slot granularity; selecting and transmitting a corresponding segment layer instance to a second communication device according to the time slot granularity through the first segment layer.

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

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

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

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

Claims

1. A data transmission method, applied to a first communication device, the first communication device comprising: The first channel layer and the first section layer; wherein, the first channel layer and the first section layer support carrying a first interface rate greater than 400G; the method includes: Adapting the rate of the service signal flow by the first channel layer in a signal adaptation manner to obtain a corresponding service signal frame; Inserting first information in the first coding format into the service signal frame by the first channel layer; Dividing time slots by the first section layer in a time slot division manner to obtain a corresponding time slot granularity; Selecting and transmitting a corresponding section layer instance to a second communication device by the first section layer according to the time slot granularity.

2. The method according to claim 1, wherein The signal adaptation manner includes at least one of the following: signal adaptation of a single-channel first interface rate; signal adaptation of at least two-channel second interface rates; wherein, the second interface rate is less than the first interface rate.

3. The method according to claim 1, wherein, The service signal flow includes service signal frames, and the service signal frames include a first number of first type code blocks; the code block types of the first type code blocks include at least one of the following: idle code blocks; local fault code blocks related to fault indication; remote fault code blocks related to fault indication; low power indication LPI code blocks; error code blocks; sequence code blocks; padding code blocks.

4. The method according to claim 1, wherein When a second type code block is formed by a first number of first type code blocks and the first number is greater than 1, by adjusting the position of the control code block in the first type code blocks and combining the rate adaptation of the first type code blocks, the control code block is adjusted to the boundary of the first type code blocks to obtain a corresponding second type code block.

5. The method according to claim 4, wherein When the code block types of the first number of first type code blocks are the same, all the control code blocks in the first number of first type code blocks are adapted into a group of control code blocks, and the group of control code blocks is encoded in at least one of the following N*66B coding formats: 64 / 66b coding; 256 / 257b coding; 512 / 514b coding; Adding overhead indication information to the coding format; wherein, the overhead indication information includes at least one of the following: the code block type of the second type code block; the pattern type of the second type code block.

6. The method according to claim 4, wherein, The determination method of the second type code block includes: Redefining the type header of the first first type code block as a compatible new type; or, Moving the control code block type indication in each first type code block to a first position, and moving the overhead content in each first type code block to a second position, wherein the first position is before the second position, and redefining the format or content of the first position.

7. The method according to claim 6, wherein, The redefined type header includes: a redefined first half-byte and a second half-byte.

8. The method according to claim 5 or 6, wherein, When the first type code block is an idle code block and the rate of the service signal flow does not match that of the first channel layer, adding or deleting idle code blocks with the redefined idle coding format as the basic unit; Wherein, the redefined idle coding format includes: the first coding format with the code block type of idle code block in the type indication information; the first coding format with the code block type of idle code block in the overhead indication information.

9. The method according to claim 1, wherein The first channel layer includes at least one of the following functions: inserting operation, administration, and maintenance (OAM) overhead at the source end; terminating OAM overhead at the sink end; non-intrusively monitoring overhead at intermediate nodes; and performing channel switching with the first interface rate as the section layer interface.

10. The method according to claim 1, wherein, The first channel layer supports channel OAM processing; the channel OAM processing includes at least one of the following functions: OAM coding format; OAM transmission and reception processing; and non-intrusive monitoring.

11. The method according to claim 1, wherein, Process the OAM function by identifying the OAM type field of the first coding format.

12. The method according to claim 4, wherein The methods for inserting the first information into the service signal frame through the first channel layer include one of the following: replacing the existing idle code block of the first coding format with an OAM code block of the identified defined first coding format; inserting an OAM code block in the coding frame gap and then deleting the idle code block; After deleting the OAM code block, filling the idle code block; and inserting in real time at any position of the second type of code block according to the insertion interval of the OAM code block.

13. According to the method described in claim 4, when the first type of code block is an OAM code block, the method for determining the second type of code block further includes: Merging the payload bits in the first number of first type of code blocks and merging the overhead bits in the first number of first type of code blocks.

14. The method according to claim 4, wherein The product value of the time slot granularity and the number of time slots satisfies the total rate of the first section layer.

15. The method according to claim 14, wherein, The configuration method for encoding the first number of first type of code blocks into the second type of code block includes: using the product value between the first number and the bit repetition times for an inter-cycle interleaving method; and using the continuous first number of first type of code blocks.

16. The method according to claim 1 further comprises: Determine the corresponding number of time slots according to the time slot granularity; wherein the product value between the number of time slots and the time slot granularity is equal to the interface capacity of the first section layer.

17. The method according to claim 1, wherein, During the switching process of different rate levels of channels by the first channel layer, a hierarchical switching path is adopted, and switching of multiple rate levels and coding formats is supported.

18. The method according to claim 1, wherein, The first section layer includes at least one of the following functions: channel layer and section layer rate adaptation; section layer time slot mapping and section layer service layer adaptation.

19. The method according to claim 1, wherein The rate adaptation method between the first channel layer and the first section layer includes: using a signal adaptation method with the first interface rate; and performing rate adaptation using different coding formats.

20. The method according to claim 1, wherein The first section layer unifies and simplifies the support for the first interface rate by the section layer through an instance, and selects a section layer instance with a second number and a third interface rate; The time slot granularity of the first section layer is the same as that of the first channel layer, or the rate level corresponding to the time slot granularity of the first section layer is higher than the rate level corresponding to the time slot granularity of the first channel layer.

21. The method according to claim 3, wherein The filled code block supports carrying auxiliary overhead for section layer instance identification through a redefined code block. The redefinition of the filled code block includes redefining the original filled code block format and introducing a new filled code block format.

22. The method according to claim 1, wherein, The first section layer supports dynamic activation and deactivation of the section layer instance.

23. According to the method described in claim 1, it further includes: Transmit the activated segment instance to the second communication device through the first segment layer; wherein, the segment instance carries an instance identifier and service data; the filling pattern of the segment instance includes at least one of an error code block and an idle code block.

24. The method according to claim 1, wherein, In the case where the service traffic of the first segment layer is less than a preset energy-saving traffic, replace the LPI signal with the overhead signaling of the first segment layer to trigger the first segment layer to perform time slot switching.

25. The method according to claim 1, further comprising: Redefine the fault overhead format and the fault coding format for the first coding format through the first segment layer to indicate a fault; wherein, the filling pattern corresponding to the fault includes at least one of an idle code block and an error code block.

26. A communication device, comprising: A memory, and one or more processors; The memory is configured to store one or more programs; When the one or more programs are executed by the one or more processors, the one or more processors implement the method according to any one of claims 1-25 above.

27. A storage medium storing a computer program, which when executed by a processor implements the method according to any one of claims 1-25 above.

Images