CN108809901A - A kind of method, apparatus and system of service bearer - Google Patents

Abstract

The present application provides a service bearer method, device and system, wherein the method includes: a sending end device acquires a flexible Ethernet FlexE client signal; converts the FlexE client signal into a FlexE service frame, and the FlexE service frame includes at least A first overhead code block and at least one data code block, the at least one first overhead code block is used to carry the overhead information of the FlexE client signal, and the at least one data code block is used to carry the FlexE client signal Payload information; the FlexE service frame is mapped to one or more time slots of the physical channel to generate a FlexE overhead frame, the FlexE overhead frame includes a second overhead code block, and the second overhead code block is used to carry the the overhead information of the FlexE overhead frame; and send the FlexE overhead frame through the physical channel. In this application, the FlexE client signal is converted into a FlexE service frame, and the overhead information of the FlexE client signal is carried in the FlexE service frame, so that end-to-end network management and monitoring of the FlexE client signal can be realized.

Description

A method, device and system for carrying services

technical field

The present application relates to the field of communications, and in particular to a method, device and system for carrying services.

Background technique

Currently, the interface technology of the Flexible Ethernet Implementation Agreement (Flex Ethernet Implementation Agreement 1.0, FlexE IA 1.0) has been standardized in the Optical Internetworking Forum (Optical Internetworking Forum, OIF). FlexE can be applied to the interconnection of data center equipment, etc., by binding n 100G physical layer devices (physical layer devices, PHYs) to transmit multiple FlexE customer services at different rates, such as 10G, n*25G, 40G FlexE customer services, etc.

For long-distance transmission, the FlexE can encapsulate the FlexE client service into a FlexE signal, and then carry and transmit the FlexE signal through an optical transport network (optical transport network, OTN). As shown in Figure 1, the FlexE signal from FlexE 101 to FlexE 103, or the FlexE signal from FlexE 103 to FlexE 101 can pass through OTN 102, and realize long-distance transmission through OTN as a bearer network. In the prior art, the FlexE signal can be passed through the OTN in the following three ways: (1) FlexE unaware (FlexE unaware), that is, the n*100G FlexE signal is regarded as n independent 100GE (Gigbit Ethernet, Gigbit Ethernet ) signals are carried and transmitted through n channels of ODU4 (optical data unit-4, optical data unit-4). (2) FlexE aware (FlexE aware), that is, analyze n*100G FlexE signals, delete invalid time slots of FlexE signals, and complete bearer and transmission through one or more ODUflex channels. (3) FlexE termination (FlexE terminate), that is, to perform in-depth analysis on n*100G FlexE signals, analyze multiple channels of different rates of FlexE customer services, and then multiple channels of different rates of FlexE customer services are carried and transmitted through ODUflex respectively.

With the evolution of FlexE technology, FlexE may become a transport network technology like OTN. Therefore, to realize the transmission function of FlexE, it is necessary to solve the problem of end-to-end network management and monitoring in FlexE.

Contents of the invention

In view of this, the present application provides a service bearing method, device and system, which can solve the problem that end-to-end network management and monitoring cannot be performed in FlexE.

In a first aspect, the present application provides a service sending method, including: a sending end device acquires a flexible Ethernet FlexE client signal; converts the FlexE client signal into a FlexE service frame, and the FlexE service frame includes at least one first overhead a code block and at least one data code block, the at least one first overhead code block is used to carry the overhead information of the FlexE client signal, and the at least one data code block is used to carry the payload information of the FlexE client signal; Mapping the FlexE service frame to one or more time slots of a physical channel to generate a FlexE overhead frame, the FlexE overhead frame includes a second overhead code block, and the second overhead code block is used to carry the FlexE overhead frame overhead information; sending the FlexE overhead frame through the physical channel.

In this application, the FlexE client signal is converted into a FlexE service frame, and the overhead information of the FlexE client signal is carried in the FlexE service frame, so that end-to-end network management and monitoring of the FlexE client signal can be realized.

In a possible implementation manner, the converting the FlexE client signal into a FlexE service frame includes: periodically inserting the at least one first overhead code block into the FlexE service frame.

In this application, the first overhead code block may be periodically carried in the FlexE service frame, for example, one or more first overhead code blocks appear every preset number of code blocks in the FlexE service frame.

In a possible implementation manner, the converting the FlexE client signal into a FlexE service frame includes: converting the ^FlexE client signal into the The FlexE service frame, wherein, n is greater than or equal to 0.

In this application, the FlexE client signal with a preset length is converted into a FlexE service frame, which reduces the complexity of signal processing and improves transmission efficiency.

In a possible implementation manner, before mapping the FlexE service frame into one or more time slots of a physical channel, the method further includes: performing rate adaptation on the FlexE client signal.

In a possible implementation manner, the converting the FlexE client signal into a FlexE service frame includes: encoding overhead information of the FlexE client signal to generate the at least one first overhead code block.

In a possible implementation manner, the at least one first overhead code block is located at the frame header of the FlexE service frame, and/or, the at least one first overhead code block is located in any two data code blocks of the FlexE service frame between blocks.

In a second aspect, the present application provides a service receiving method, including: a receiving end device receives a flexible Ethernet FlexE overhead frame from a physical channel; identifies the overhead information of the FlexE overhead frame, and obtains the overhead information from the FlexE overhead frame according to the overhead information of the FlexE overhead frame Demapping one or more time slots of the physical channel to obtain a FlexE service frame, the overhead information of the FlexE overhead frame is carried by the second overhead code block of the FlexE overhead frame; converting the FlexE service frame into a FlexE client signal, the FlexE service frame includes at least one first overhead code block and at least one data code block, the at least one first overhead code block is used to carry the overhead information of the FlexE client signal, and the at least one data code block Used to carry the payload information of the FlexE client signal.

In this application, the FlexE service frame is converted into the FlexE client signal, and the overhead information of the FlexE client is carried through the FlexE service frame, so that end-to-end network management and monitoring of the FlexE client signal can be realized.

In a possible implementation manner, the converting the FlexE service frame into a FlexE client signal includes: periodically identifying the at least one first overhead code block from the FlexE service frame.

In this application, the first overhead code block may be periodically identified from the FlexE service frame, for example, one or more first overhead code blocks are identified every preset number of code blocks in the FlexE service frame.

In a possible implementation, the converting the FlexE service frame into a FlexE client signal includes: converting the FlexE service frame into a FlexE client signal in units of 1/(2 ⁿ ) of the length of a FlexE service frame Signal, where n is greater than or equal to zero.

In this application, the FlexE service frame with a preset length is converted into a FlexE client signal, which reduces the complexity of signal processing and improves transmission efficiency.

In a possible implementation manner, the converting the FlexE service frame into a FlexE client signal includes: deleting a synchronization header bit of the FlexE service frame, decoding the FlexE service frame, and filling a reserved field.

In a possible implementation manner, the at least one first overhead code block is located at the frame header of the FlexE service frame, and/or, the at least one first overhead code block is located in any two data code blocks of the FlexE service frame between blocks.

In a third aspect, the present application provides a sending device, including: a receiving module, configured to acquire a flexible Ethernet FlexE client signal; a processing module, configured to convert the FlexE client signal into a FlexE service frame, and the FlexE service frame includes At least one first overhead code block and at least one data code block, the at least one first overhead code block is used to carry the overhead information of the FlexE client signal, and the at least one data code block is used to carry the FlexE client signal Payload information; the FlexE service frame is mapped to one or more time slots of the physical channel to generate a FlexE overhead frame, the FlexE overhead frame includes a second overhead code block, and the second overhead code block is used to carry Overhead information of the FlexE overhead frame; a sending module, configured to send the FlexE overhead frame through the physical channel.

In a possible implementation manner, the processing module is configured to: periodically insert the at least one first overhead code block into the FlexE service frame.

In a possible implementation manner, the processing module is configured to convert the FlexE client signal into the FlexE service frame in units of 1/(2 ⁿ ) of the length of a FlexE client signal frame, where n greater than or equal to 0.

In a possible implementation manner, the processing module is further configured to: perform rate adaptation on the FlexE client signal.

In a possible implementation manner, the converting the FlexE client signal into a FlexE service frame includes: encoding overhead information of the FlexE client signal to generate the at least one first overhead code block.

In a possible implementation manner, the at least one first overhead code block is located at the frame header of the FlexE service frame, and/or, the at least one first overhead code block is located in any two data code blocks of the FlexE service frame between blocks.

In a fourth aspect, the present application provides a receiving device, including: a receiving module, configured to receive a flexible Ethernet FlexE overhead frame from a physical channel; a processing module, configured to identify the overhead information of the FlexE overhead frame, according to the FlexE overhead frame The overhead information of the frame is demapped from one or more time slots of the physical channel to obtain a FlexE service frame, and the overhead information of the FlexE overhead frame is carried by the second overhead code block of the FlexE overhead frame; the FlexE service The frame is converted into a FlexE client signal, the FlexE service frame includes at least one first overhead code block and at least one data code block, the at least one first overhead code block is used to carry the overhead information of the FlexE client signal, the At least one data code block is used to carry payload information of the FlexE client signal.

In a possible implementation manner, the processing module is configured to: periodically identify the at least one first overhead code block from the FlexE service frame.

In a possible implementation, the processing module is configured to convert the FlexE service frame into a FlexE client signal in units of 1/(2 ⁿ ) of the length of a FlexE service frame, where n is greater than or equal to 0.

In a possible implementation manner, the processing module is configured to: delete a synchronization header bit of the FlexE service frame, decode the FlexE service frame, and fill in a reserved field.

In a possible implementation manner, the at least one first overhead code block is located at the frame header of the FlexE service frame, and/or, the at least one first overhead code block is located in any two data code blocks of the FlexE service frame between blocks.

In the fourth aspect, the embodiment of the present invention provides a network system, including the sending device of the third aspect or any possible implementation of the third aspect, and the receiving device of the fourth aspect or any of the possible implementations of the fourth aspect equipment.

Yet another aspect of the present application provides a computer-readable storage medium, where instructions are stored in the computer-readable storage medium, and when the computer-readable storage medium is run on a computer, it causes the computer to execute the methods described in the above aspects.

Yet another aspect of the present application provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute the methods described in the above aspects.

Description of drawings

In order to illustrate the embodiments of the present invention or the technical solutions in the prior art more clearly, the following briefly introduces the drawings used in describing the background technology and the embodiments.

FIG. 1 is a schematic diagram of a network architecture in which a FlexE signal passes through an OTN in the prior art;

FIG. 2 is a schematic diagram of a network architecture in which an OTN signal passes through FlexE provided by an embodiment of the present invention;

FIG. 3 is a schematic diagram of a frame structure of an OTN frame in the prior art;

Fig. 4 is a schematic diagram of converting an OTN frame into a FlexE service frame provided by an embodiment of the present invention;

Fig. 5a is a schematic diagram of a code block format of a FlexE service frame provided by an embodiment of the present invention;

Fig. 5b is a schematic diagram of a code block format of a FlexE service frame provided by an embodiment of the present invention;

Fig. 6a is a schematic diagram of the format of a FlexE service frame provided by an embodiment of the present invention;

Fig. 6b is a schematic diagram of the format of another FlexE service frame provided by the embodiment of the present invention;

Fig. 7 is a schematic diagram of the format of an overhead code block provided by an embodiment of the present invention;

FIG. 8 is a schematic diagram of the format of a FlexE service frame provided by an embodiment of the present invention;

FIG. 9 is a schematic diagram of a service sending process provided by an embodiment of the present invention;

FIG. 10 is a schematic diagram of a time slot distribution process provided by an embodiment of the present invention;

FIG. 11 is a schematic diagram of a process for inserting a FlexE overhead code block provided by an embodiment of the present invention;

FIG. 12 is a schematic diagram of a service transmission process provided by an embodiment of the present invention;

Fig. 13 is a schematic diagram of a service sending process provided by an embodiment of the present invention;

FIG. 14 is a schematic diagram of another service sending process provided by an embodiment of the present invention;

Fig. 15 is a schematic diagram of a service receiving process provided by an embodiment of the present invention;

FIG. 16 is a schematic diagram of a network architecture provided by an embodiment of the present invention;

Fig. 17 is an exemplary flow chart of a service sending method provided by an embodiment of the present invention;

Fig. 18 is an exemplary flow chart of a service receiving method provided by an embodiment of the present invention;

FIG. 19 is a schematic structural diagram of a sending device provided by an embodiment of the present invention;

Fig. 20 is a schematic structural diagram of a receiving device provided by an embodiment of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments.

FIG. 2 is a schematic diagram of a network architecture in which an OTN signal passes through a FlexE provided by an embodiment of the present invention. As shown in Figure 2, the OTN 201 can encapsulate the customer service of the client equipment 204 into an OTN signal, carry and transmit the OTN signal through the FlexE 202, and the OTN 203 receives the OTN signal, restores the customer service from the OTN signal and sends it To the client device 205. Alternatively, the OTN 203 can encapsulate the customer service of the client equipment 205 into an OTN signal, carry and transmit the OTN signal through the FlexE 202, and the OTN 201 receives the OTN signal, restores the customer service from the OTN signal and sends it to the customer equipment 204 . Client devices 204 and 205 may be data centers, routers, servers, computers, and other devices. When the OTN signal is carried and transmitted through the FlexE 202, it involves converting the frame format of the OTN signal into a frame format suitable for the FlexE service frame transmitted on the FlexE. The frame format of the FlexE service frame provided by the embodiment of the present invention has a good corresponding relationship with the frame format of the OTN frame, which simplifies the process of signal processing and improves the efficiency of signal processing. Moreover, the overhead information of the OTN frame is reserved in the FlexE service frame, enabling end-to-end network management and monitoring.

In the embodiment of the present invention, the OTN signal and the OTN frame can refer to the same object, such as OTUk (opticaltransport unit-k, optical transport unit-k), OTUCn (optical transport unit-Cn, optical transport unit-Cn), etc.; including ODUk (optical data unit-k, optical data unit-k), ODUflex (optical data unit-flex, flexible optical data unit), ODUCn (optical data unit-Cn, optical data unit-Cn), etc.; may also include OPUk (optical payload unit-k, optical payload unit-k), OPUflex (optical payload unit-flex, flexible optical payload unit), OPUCn (optical payload unit-Cn, optical payload unit-Cn), etc. Among them, k can be 0, 1, 2, 2e, 3, 4, etc., and Cn represents an integer multiple of 100G.

FIG. 3 is a schematic diagram of a frame structure of an OTN frame in the prior art. As shown in FIG. 3 , the frame structure of ODUk or ODUflex is taken as an example for description. An OTN frame may consist of 4 rows x 3824 columns of bytes. Wherein, the first column to the 16th column are the overhead information of the OTN frame, and the 17th column to the 3824th column are the payload information of the OTN frame. The overhead information of the OTN frame may include frame alignment overhead, OTU (optical transport unit, optical transport unit) overhead, OPU (optical payload unit, optical payload unit) overhead, ODU (optical data unit, optical data unit) overhead, and the like. The frame alignment overhead may include FAS (frame alignment signal, frame alignment signal) and/or MFAS (multiframe alignment signal, multiframe alignment signal). ODU overhead can include: PM (path monitoring, channel monitoring), TCM (tandem connection monitoring, serial link monitoring), EXP (experimental, experiment), GCC (general communication channel, general communication channel), APS (automatic protection switching, automatic protection switching ), PCC (protection communication channel, protection communication channel), etc. Among them, PM can also include TTI (trailtrace identifier, path trace identification), BIP8 (bit interleaved parity-level 8, bit interleaved parity-level 8), BEI (backward error indication, backward error indication), BDI (backward defect indication, backward defect indication), STAT (status), etc.

Conversion method one:

Fig. 4 is a schematic diagram of converting an OTN frame into a FlexE service frame according to an embodiment of the present invention. As shown in Fig. 4, a FlexE service frame converted from an OTN frame may include a start code block S, 1910 data code blocks D and a frame end code block T. The S, D, and T code blocks may be 66B code blocks. A 66B code block may also be called a 64B/66B code block, and includes a 2-bit sync header and 64-bit data. In an example, 1/(2 ⁿ ) of the length of an OTN frame can be used as a unit, starting from the start byte of the OTN frame, and converting every 8 bytes into a 66B code block. Then 1/(2 ⁿ ) of an OTN frame can be converted into a FlexE service frame including 1912/(2 ⁿ ) 66B code blocks. Wherein, the FlexE service frame may include a start code block S, 1912/(2 ⁿ )-2 data code blocks D and a frame end code block T. Wherein, n is greater than or equal to 0. When n=0, the conversion is performed in units of one OTN frame length, and the converted FlexE service frame includes 1912 code blocks. When n=1, conversion is performed in units of 1/2 OTN frame length, and the converted FlexE service frame includes 956 code blocks. When n=2, conversion is performed in units of 1/4 OTN frame length, and the converted FlexE service frame includes 478 code blocks. And so on. In practical applications, n may also be set to be less than 0, such as n=-1, -2, and so on. Then, the number of code blocks included in a FlexE service frame may be 3824, 7648 and so on.

In this example, the OTN frame is ODUk or ODUflex as an example for description. Certainly, the embodiment of the present invention is also applicable to OPUk, OPUflex, etc., and the number of 66B code blocks included in the FlexE service frame converted from OPUk or OPUflex may be different from the FlexE service frame converted from ODUk or ODUflex. For example, an OPUk or OPUflex can be converted into a FlexE service frame including 1905 66B code blocks.

Taking n=0 as an example for illustration, that is, one OTN frame is transformed into a FlexE service frame including 1912 66B code blocks (the FlexE service frame shown in FIG. 4 ). Fig. 5a is a schematic diagram of a code block format of a FlexE service frame provided by an embodiment of the present invention. As shown in Figure 5a, the start code block of the FlexE service frame, that is, the S code block can carry the frame header information of the i+1th frame ODUk or ODUflex. The frame end code block of the FlexE service frame, that is, the T code block can carry the frame end information of the i-th frame ODUk or ODUflex. The S code block can also use the free field D1 to carry the last byte in the ODUk or ODUflex frame end information of the i-th frame. Fig. 5b is a schematic diagram of a code block format of a FlexE service frame provided by an embodiment of the present invention. As shown in Figure 5b, the data code block of the FlexE service frame, that is, the D code block, can carry the intermediate bytes of ODUk or ODUflex, that is, bytes other than frame header information and frame tail information.

(1) The S code block can be converted and generated from the frame header information of the OTN frame, that is, the first 8 overhead bytes of the first line. The S code block may include a 2-bit synchronization header "10", an 8-bit code block type field "0x78", and the remaining 7 bytes are used to carry the first 8 overhead bytes of the first line of the OTN frame. Since 7 bytes are not enough to fully carry 8 overhead bytes, the 8 overhead bytes of the OTN frame can be compressed. For example, the first to sixth bytes of the first line of the OTN frame carry fixed pattern information, "0xF6F6F6282828", the repeated bytes of the first line of the OTN frame can be discarded, for example, any two "F6F6" bytes are discarded, Or discard any two "2828" bytes. In this way, the frame header information of the OTN frame, that is, the first 8 overhead bytes of the first line are compressed into 6 bytes. In another example, the 5th and 6th bytes of the first row of the OTN frame can be placed in the 66B code block converted from the reserved bytes of the OTN frame overhead area, which is equivalent to the 5th and 6th bytes of the first row of the OTN frame The 6 bytes occupy the reserved field of the reserved bytes in the OTN frame overhead area in the 66B code block. For example, the 5th and 6th bytes of the first line of the OTN frame can be converted from the 1st and 2nd overhead area reserved bytes of the second line of the OTN frame or the 9th to 14th overhead area reserved bytes of the fourth line A reserved field in the 66B code block.

(2) The T code block can be converted and generated from the frame end information of the OTN frame, that is, the last 8 bytes of the fourth line. The T code block may include a 2-bit synchronization header "10", an 8-bit code block type field "0xff", and the remaining 7 bytes are used to carry the last 8 bytes of the fourth line of the OTN frame. Since the overhead bytes carried by the S code block are compressed, there is a free field D1 in the S code block that can carry the frame end information of the OTN frame. In another example, a byte at the end of the OTN frame may also be placed in the reserved field of the 66B code block converted from the reserved bytes in the overhead area of the OTN frame.

As shown in Figure 5a, the frame header information of the i+1 frame ODUk or ODUflex, "0xF6F6F6282828+MFAS+D1" is compressed into 6 bytes and placed in the D2-D7 fields of the S code block. The D1 field of the S code block can be used to carry a byte D8 in the frame end information of the i-th frame ODUk or ODUflex. The frame end information of the i-th frame ODUk or ODUflex, "D1D2D3D4D5D6D7" has a total of 7 bytes, which are placed in the D1~D7 fields of the T code block.

(3) The D code block can be converted and generated from the middle bytes of the OTN frame, that is, bytes other than the first 8 overhead bytes in the first row and the last 8 bytes in the fourth row. As shown in Figure 5b, the D code block may include a 2-bit sync header "01", and the remaining 8 bytes are used to carry any 8 intermediate bytes of the OTN frame. For example, eight consecutive intermediate bytes may be placed in the D1-D8 fields of a D code block.

Conversion method two:

Fig. 6a is a schematic diagram of a format of a FlexE service frame provided by an embodiment of the present invention. Fig. 6b is a schematic diagram of the format of another FlexE service frame provided by an embodiment of the present invention. In an example, the overhead code block can be placed at the frame header of the FlexE service frame. As shown in Fig. 6a, a FlexE frame may include x 66B overhead code blocks OH and y consecutive 66B data code blocks D. x 66B overhead code blocks are set at the frame header of the FlexE service frame. In another example, the overhead code blocks of the FlexE service frame may also be inserted into the FlexE service frame at a certain period. As shown in Fig. 6b, a FlexE service frame may include p 66B overhead code blocks of group z. Taking p 66B overhead code blocks as a unit, it is inserted in z positions of the FlexE service frame according to a certain cycle. Alternatively, p 66B overhead code blocks are inserted in front of every q 66B data code blocks. As shown in FIG. 6a or 6b, the overhead code block may carry one or more types of overhead information for end-to-end management and monitoring, for example, any one or more of TTI, BIP8, BEI, BDI, and STAT. In addition, the overhead code block can also be used to carry frame header alignment overhead (FAS/MFAS) and the like.

Fig. 7 is a schematic diagram of the format of an overhead code block provided by an embodiment of the present invention. As shown in FIG. 7 , the overhead code block may be a 66B code block, including a 2-bit sync header "10" and an 8-bit code block type field "0x4b". In the existing standard, "0x4b" is a used code block type, so the 4-bit "0xa" code block type field can also be set for identification. Alternatively, the code block type field can also be set to a code block type not used in the existing standard, such as "0x4C". If the code block type field in the overhead code block occupies 8 bits, the remaining 56 bits can be used to bear the overhead information of the OTN frame. However, each line of the OTN frame contains 16 overhead bytes. If the overhead bytes of each line of the OTN frame are completely placed in 2 overhead code blocks, each overhead code block should contain 64 bits to carry the OTN frame. overhead bytes. Therefore, some overhead bytes in the OTN frame, such as TCM, APS, PCC and other bytes, can be discarded, set as the reserved field RES in the overhead code block, or fill all 0s in the field of the overhead code block.

Fig. 8 is a schematic diagram of a format of a FlexE service frame provided by an embodiment of the present invention. Similar to the first conversion method, 1/(2 ⁿ ) of an OTN frame length can be used as a unit, starting from the start byte of the OTN frame, and converting every 8 bytes into a 66B code block. Similarly, the OTN frame is ODUk or ODUflex, and n=0 is taken as an example for illustration. As shown in Figure 8, taking one ODUk or ODUflex frame as a unit, the first 16 bytes of each line of ODUk or ODUflex are converted into two 66B overhead code blocks, and the remaining 3808 bytes are converted into 476 66B data code blocks. Two 66B overhead code blocks are inserted into every 476 66B data code blocks, so a total of 8 66B overhead code blocks are inserted into 4 groups of 476 66B data code blocks (overhead code block OH1, overhead code block OH2...overhead code block OH7, overhead code block code block OH8). An ODUk or ODUflex is converted into a FlexE service frame including 8 66B overhead code blocks plus 4x476 66B data code blocks. The overhead code block OH1 carries the 1st to 8th overhead bytes of the first row of ODUk or ODUflex, and the overhead code block OH2 can carry the 9th to 16th overhead bytes of the first row of ODUk or ODUflex. The overhead code block OH3 can carry the 1st to 8th overhead bytes of the second row of ODUk or ODUflex, and the overhead code block OH4 can carry the 9th to 16th overhead bytes of the second row of ODUk or ODUflex. The overhead code block OH5 can carry the 1st to 8th overhead bytes in the third row of ODUk or ODUflex, and the overhead code block OH6 can carry the 9th to 16th overhead bytes in the third row of ODUk or ODUflex. The overhead code block OH7 can carry the 1st to 8th overhead bytes of the fourth row of ODUk or ODUflex, and the overhead code block OH8 can carry the fourth row and the 9th to 16th overhead bytes of ODUk or ODUflex.

(1) An overhead code block, which can be used to carry overhead information (overhead bytes) of an OTN frame. As shown in Fig. 8, the overhead code block OH1 can carry the frame header positioning overhead FAS and MFAS, and the overhead code block OH6 can carry the path management monitoring overhead PM (including TTI, BIP8, BDI, BEI, etc.). Reserved fields may be set in overhead code blocks OH2, OH3, OH4, OH5, OH7, and OH8. Of course, when it is necessary to add other overhead bytes of the OTN frame, it can be set in the reserved field of the overhead code block. In the embodiment of the present invention, the OAM (operation, administration and maintenance) characteristic of the OTN frame is reserved in the FlexE service frame, and the overhead information of the OTN frame can be used to realize end-to-end network management and monitoring.

(2) The D code block can be used to carry the payload information (payload bytes) of the OTN frame. For the format of the D code block, refer to FIG. 5b. The 17th to 3824th bytes of each line of the OTN frame can be converted into 476 D code blocks, D can be 66B code blocks, including the 2-bit synchronization header "01", and the remaining 8 bytes can be placed in each line of the OTN frame Any 8 bytes from the 17th to the 3824th byte of . For example, 8 consecutive bytes in the payload area of the OTN frame can be placed in the D1-D8 fields of a D code block.

In the embodiment of the present invention, if the FlexE service frame is converted into an OTN frame, the 2-bit synchronization header of each 66B code block in the FlexE service frame can be deleted, and the code block type field of the overhead code block can be converted into the OTN frame. Reserved bytes. A FlexE service frame can be exactly converted into an OTN frame, and the original overhead information of the OTN frame can be restored. The FlexE service frame and the OTN frame in the embodiment of the present invention have a good correspondence in the frame structure, and when the FlexE service frame is converted into an OTN frame, there is no need to map the FlexE service frame into the payload of the OTN frame and regenerate the OTN Frame overhead reduces signal processing complexity and improves transmission efficiency.

The following describes the processing of FlexE service transmission:

FIG. 9 is a schematic diagram of a service sending process provided by an embodiment of the present invention. As shown in Figure 9, the FlexE interface forms a FlexE group (FlexE group, also called a FlexE member group) through bound N PHY (also called PHY member or FlexE member) channels, and through the binding of N PHY channels The FlexE group is used to transmit multiple FlexE services of different rates (also called FlexE client, FlexE client signal, FlexE client service, etc.). FIG. 9 shows at least three FlexE services. For example, the FlexE services may include OTN signals (or called OTN services), packet services, and Ethernet services. Wherein, the bandwidth of each PHY channel may be 100G, 200G, 400G, etc. For example, in the existing FlexE standard, a 100G PHY channel is used. In the shim layer (Calendar or main time layer) of FlexE, the FlexE group can be divided into 20xN time slots (Calendar slot) of 5G granularity. Each PHY channel is divided into 20 5G time slots.

Step 900, acquire at least one FlexE service. For example, ODUk or ODUflex, FlexE service #a and FlexE service #z, etc. This embodiment is described by taking ODUk or ODUflex as an example, and the FlexE service #a and the FlexE service #z are described in the embodiment shown in FIG. 12 . ODUk or ODUflex can be used as a FlexE client signal to carry and transmit through FlexE.

In step 901, the obtained FlexE service is converted into a FlexE service frame. For example, for ODUk or ODUflex, any conversion method in the foregoing embodiments may be used, or any two or more conversion methods may be combined to convert ODUk or ODUflex into a FlexE service frame.

Step 902, performing rate adaptation on the FlexE service frame.

The purpose of the rate adaptation is to make the FlexE service frame occupy an integer number of time slots at the FlexE shim layer in step 903 .

For example, if ODUk or ODUflex is converted into the FlexE service frame described in conversion mode 1 or conversion mode 2, an idle code block (IDLE) or a preset special code block can be added to the FlexE service frame for rate adaptation.

If the ODUk or ODUflex is first converted into the FlexE service frame A described in the conversion method 1, and then the FlexE service frame A is converted into the FlexE service frame B described in the conversion method 2, an idle code block can be added to the FlexE service frame A ( IDLE) or a preset special code block for rate adaptation, and an idle code block (IDLE) or a preset special code block for rate adaptation may also be added in the FlexE service frame B. For example, an idle code block (IDLE) or a preset special code block can be added between the T code block of the previous FlexE service frame A and the S code block of the next FlexE service frame A. Or, an idle code block (IDLE) or a preset special code block is added between two FlexE service frames B. The conversion of the FlexE service frame A into the FlexE service frame B may be realized by inserting an overhead code block for carrying overhead information of the OTN frame based on the FlexE service frame A. The 66B code block of the FlexE service frame A may include any one or more of S code blocks, T code blocks, D code blocks, and idle code blocks. For the frame format of the FlexE service frame B, refer to the embodiment shown in FIG. 8 . The 66B code block of the FlexE service frame A can be regarded as the D code block of the FlexE service frame B. For example, in FlexE service frame A, two 66B overhead code blocks are inserted for every 476 66B code blocks to generate FlexE service frame B. Alternatively, in the FlexE service frame A, two 66B overhead code blocks are inserted for every 478 66B code blocks, so that one FlexE service frame A is just converted into one FlexE service frame B.

Step 903, generating a FlexE group signal: assigning one or more time slots to the FlexE service frame according to the bandwidth of the FlexE service frame, and mapping the rate-adapted FlexE service frame to the allocated one or more time slots. The one or more time slots here may be any time slot in the 20xN time slots divided in the FlexE shim layer. For example, the bandwidth of ODU0 is 1.25G, and a 5G time slot can be allocated for the FlexE service frame generated by ODU0. The bandwidth of ODU2 is 10G, and two 5G time slots can be allocated for the FlexE service frame generated by ODU2. If multiple time slots are allocated, the multiple time slots may be located in the same PHY channel or in different PHY channels.

Fig. 10 is a schematic diagram of a time slot distribution process provided by an embodiment of the present invention. As shown in Figure 10 (taking 4 PHY channels as an example), the Calendar is divided into 20x4 time slots, and each PHY channel (or sub-Calendar) is divided into 20 time slots (identified as time slots 0- time slot 19). In Figure 10, two time slots are allocated for the FlexE service frame generated by ODU2, one time slot is located in PHY channel 1, and the other time slot is located in PHY channel 2. Alternatively, the two time slots of the FlexE service frame generated by ODU2 may also be located in PHY channel 1.

Step 904, generating PHY channel signals: after distributing the FlexE group signals carrying the FlexE service frames to one or more PHY channels, adding overhead information of the FlexE overhead frames. The overhead information of the FlexE overhead frame may include a FlexE group number, a PHY channel number, time slot occupancy indication information, and the like. The PHY channel signal can be transmitted in the format of the FlexE overhead frame, and one PHY channel signal can correspond to one FlexE overhead frame. As shown in FIG. 10 , four PHY channel signals are generated, wherein ODU2 is carried in PHY channel signal 1 and PHY channel signal 2 .

Fig. 11 is a schematic diagram of a process for inserting a FlexE overhead code block according to an embodiment of the present invention. The overhead information of the FlexE overhead frame may include several FlexE overhead code blocks inserted in the PHY channel signal at a certain period. As shown in FIG. 11 , the FlexE overhead frame may be formed by any PHY channel signal. In one cycle, one FlexE overhead code block can be inserted before every 20x1023 data code blocks. A FlexE overhead frame may include 8 consecutive periods, that is, 8 FlexE overhead code blocks plus 8x (20x1023) data code blocks. Wherein, several periodically occurring data code blocks can be transmitted through one time slot. As shown in Figure 11, the first time slot transmits the data code block "1" that occurs periodically every 20 code blocks, and the second time slot transmits the data code block "2" that occurs periodically every 20 code blocks. ..., the 20th time slot transmits the data code block "20" that occurs periodically every 20 code blocks. The FlexE service frame can be carried in any code block of 20x1023 data code blocks, and is transmitted through the time slot corresponding to the carried data code block. For example, the FlexE service frame generated by ODU0 is at the position of data code block "2", and is transmitted through the second time slot.

Step 905, scrambling the generated PHY channel signal.

Step 906, inserting an alignment word (alignment marker, AM) into the PHY channel signal for alignment of different virtual channels in the same PHY. AM can be used as the frame start identifier of the PHY channel signal.

Step 907, perform FEC encoding processing on the PHY channel signal, and send the processed PHY channel signal.

In the above several steps, some steps may not be executed, or the execution sequence is not limited to the above examples. For example, step 902, step 907, etc. may not be executed. Step 902 may also be performed before step 901.

Fig. 12 is a schematic diagram of a service sending process provided by an embodiment of the present invention. As shown in FIG. 12 , the difference from FIG. 9 is that in this embodiment of the present invention, a FlexE service other than ODUk or ODUflex can also be converted into any FlexE service frame in the foregoing embodiments.

Step 1200, acquire at least one FlexE service. For example, FlexE service #a, FlexE service #b, FlexE service #z, etc.

Step 1201, perform rate adaptation on the acquired FlexE service.

For example, rate adaptation is performed on the FlexE service #a. The FlexE service #a may be a packet service or an Ethernet service (such as GE, 10GE) and the like. Packet traffic can consist of a series of Ethernet frames and frame gaps. The length of each Ethernet frame may not be fixed, including one 66B start code block (S), several 66B data code blocks (D) and one frame end code block (T). A frame gap may include several idle code blocks (IDLE). The rate adaptation of the FlexE service #a can be performed by adding and/or deleting idle code blocks (IDLE).

Step 1202, converting the FlexE service into a FlexE service frame.

For example, the FlexE service #a is converted into a FlexE service frame. For example, in the packet service, two 66B overhead code blocks may be inserted periodically for every 476 66B code blocks. Four consecutive groups (476 66B code blocks + 2 66B overhead code blocks) constitute a FlexE service frame. For the frame format of the FlexE service frame, refer to FIG. 8 . The 66B code blocks of the packet service may include any one or more of S code blocks, D code blocks, T code blocks, and IDLE code blocks. The inserted 66B overhead code block can be preset by the sender, or generated according to the packet service. The 66B overhead code block can carry one or more types of overhead information for end-to-end management and monitoring, for example, any one or more of TTI, BIP8, BEI, BDI, STAT, and the like.

Optionally, step 1201 may be performed before step 1202, or may be performed after step 1202. Alternatively, step 1201 may not be executed.

For steps 1203-1207, reference may be made to steps 903-907, which will not be repeated here. The FlexE service frame structure proposed by the embodiment of the present invention is applicable to any kind of FlexE service. Since the FlexE service frame has a good correspondence with the OTN frame, when the FlexE signal needs to pass through the OTN, the processing complexity of converting the FlexE service frame into an OTN frame is reduced, and the conversion efficiency is improved. By using the overhead of the FlexE service frame, end-to-end network management and monitoring can be realized.

Fig. 13 is a schematic diagram of a service sending process provided by an embodiment of the present invention. As shown in Figure 13, the FlexE service can be ODUKm in the OTN frame. For example, the ODUKm can be ODUCn whose rate is an integral multiple of 100G, or the rate of ODUKm can also be an integral multiple of 200G, etc.

In step 1300, the ODUKm can be distributed into m-channel ODUKs (ODUK#1, ODUK#2, ..., ODUK#m), which is equivalent to changing the FlexE service from 1-channel to m-channel. The frame structure of ODUKm can be composed of m ODUK frames interleaved, and the frame format of each ODUK frame can refer to the OTN frame structure shown in Figure 3 .

In step 1301, each channel of ODUK is converted into any kind of FlexE service frame in the embodiment of the present invention, and m channels of FlexE service frames are obtained. For example, use any of the preceding conversion methods to convert each ODUK channel into a FlexE service frame. In another example, instead of distributing the ODUKm into m-channel ODUKs, the ODUKm can be regarded as one FlexE service and converted into a FlexE service frame. For example, one ODUKm can be converted into a FlexE service frame, 1/m ODUKm can be converted into a FlexE service frame, and 1/(2 ⁿ xm) ODUKm can be converted into a FlexE service frame.

For steps 1302-1207, reference may be made to steps 902-907, which will not be repeated here.

Fig. 14 is a schematic diagram of another service sending process provided by an embodiment of the present invention. As shown in FIG. 14, the difference from FIG. 13 is that step 1403, the time slot allocation of the FlexE shim layer, is omitted. In steps 1401 and 1404, after obtaining m channels of FlexE service frames, distribute m channels of FlexE service frames to m channels of PHY channels, and each channel of FlexE service frames corresponds to one channel of PHY. Add FlexE overhead code blocks to the FlexE service frames in each PHY channel at a certain period to form m-channel FlexE overhead frames, that is, m-channel PHY channel signals. Other steps are similar to those in Figure 13.

Fig. 15 is a schematic diagram of a service receiving process provided by an embodiment of the present invention. The process of service reception is roughly opposite to the process of service transmission, and the process of service reception corresponding to FIG. 9 is taken as an example for illustration.

Step 1500, receive one or more PHY channel signals.

For example, in FIG. 15, N PHY channel signals are received, for example, PHY channel signal #1, PHY channel signal #2, . . . , PHY channel signal #N, and so on.

Step 1501: Identify the AM in the PHY channel signal, align multiple virtual channels in the PHY according to the AM in the PHY channel signal, delete the AM, and obtain the aligned PHY channel signal.

Step 1502, perform FEC decoding on the recovered PHY channel signal.

Step 1503, descrambling the PHY channel signal.

Steps 1501-1503 and steps 905-907 are reverse processes. If the sending end does not perform one or more steps of steps 905-907, the receiving end may not perform corresponding reverse processing. For example, if the sending end does not perform FEC encoding, the receiving end may not perform FEC decoding.

Step 1504, extract the overhead information of the FlexE overhead frame of each PHY channel signal, and restore the N PHY channel signals to a FlexE group signal.

In step 1505, the FlexE service frame is obtained by demapping from one or more time slots of the FlexE group signal.

For example, the time slot occupancy indication information in the overhead code block of the FlexE overhead frame is analyzed, and the FlexE service frame is obtained by demapping from one or more time slots of the FlexE group signal.

Step 1506, perform rate adaptation on the FlexE service frame.

For example, an idle code block (IDLE) or a preset special code block is added and/or deleted at any position of the FlexE service frame to implement rate adaptation.

Optionally, if the FlexE service frame obtained by demapping in step 1505 is the FlexE service frame (FlexE service frame B) as described in the second conversion method, the FlexE service frame B can be converted into the FlexE service as described in the first conversion method frame (FlexE service frame A), and then perform rate adaptation based on FlexE service frame A. The way to realize the rate adaptation is to add or delete the IDLE code block between the T code block of the last FlexE service frame and the S code block of the next FlexE service frame.

Step 1507, identify the overhead code block of the FlexE service frame, and convert the FlexE service frame into ODUk or ODUflex. For example, there are 2 overhead code blocks for every 476 data code blocks in a FlexE service frame. The overhead code block of the FlexE service frame can be detected periodically, and the frame header of the ODUk or ODUflex can be determined when the frame alignment overhead FAS and/or MFAS is obtained. After obtaining a FlexE service frame, the FlexE service frame can be converted into ODUk or ODUflex. Or, after obtaining one or more code blocks of the FlexE service frame, the obtained code blocks can be converted into some bytes of ODUk or ODUflex.

In the above steps, some steps may not be executed, or the execution sequence is not limited to the above example. For example, step 1502, step 1506, etc. may not be executed. Step 1506 may also be performed after step 1507.

The embodiments of the present invention can also be applied to a scenario where a FlexE signal passes through the OTN. Fig. 16 is a schematic diagram of a network architecture provided by an embodiment of the present invention. As shown in Figure 16, the source device and the sink device are located in FlexE network 1 and FlexE network 2 respectively, and signals transmitted between the two FlexE networks are carried and transmitted through the OTN. OTN can use any kind of OTN frame (such as ODUflex) to bear the FlexE signal. The FlexE signal may be a FlexE service frame or a FlexE overhead frame carrying the FlexE service frame. Edge device B of the FlexE network 1 is connected to edge device C of the OTN, so that the FlexE network 1 is connected to the OTN. The edge device E of the FlexE network 2 is connected to the edge device D of the OTN, so that the FlexE network 2 is connected to the OTN. Edge device B or edge device E can access the OTN through the FlexE member group.

The source device can convert the FlexE service into a FlexE service frame, for example, the FlexE service can include OTN signal, packet service, Ethernet service and so on. FlexE service frames can carry 66B overhead code blocks. When OTN edge device C converts FlexE service frames into ODUflex, it can convert the 66B overhead code blocks of FlexE service frames into overhead bytes. The OTN edge device D restores the ODUflex to a FlexE service frame, and the sink device receives the FlexE service frame and can restore the FlexE service frame to a FlexE service. Since the FlexE service frame can carry overhead information, the end-to-end network management and monitoring can be realized through the FlexE service frame.

Fig. 17 is an exemplary flow chart of a service sending method provided by an embodiment of the present invention. As shown in Fig. 17, the method can be executed by the sending end device. The method may include the steps of:

S1701: Obtain a FlexE client signal.

The FlexE client signal can be obtained from the client device or generated by the sender device. FlexE client signals may include, for example, OTN signals (or called OTN services), packet services, Ethernet services, and the like.

S1702: Convert the FlexE client signal into a FlexE service frame, the FlexE service frame includes at least one first overhead code block and at least one data code block, and the at least one first overhead code block is used to carry the FlexE client Signal overhead information, the at least one data code block is used to carry payload information of the FlexE client signal.

Optionally, the at least one first overhead code block is periodically inserted into the FlexE service frame. The FlexE client signal is converted into the FlexE service frame in units of 1/(2 ⁿ ) of the length of a FlexE client signal frame, where n is greater than or equal to 0. For example, when n=0, a FlexE client signal frame can be converted into a FlexE service frame. Optionally, encode the overhead information of the FlexE client signal to generate the at least one first overhead code block. Optionally, the at least one first overhead code block is located at the frame header of the FlexE service frame, and/or, the at least one first overhead code block is between any two data code blocks of the FlexE service frame. For example, when the FlexE client signal is an OTN frame, the overhead information of the FlexE client signal can include any one or more of frame header positioning overhead and path management monitoring overhead, which can be used for end-to-end network management and monitoring.

S1703: Map the FlexE service frame to one or more time slots of the physical channel to generate a FlexE overhead frame, the FlexE overhead frame includes a second overhead code block, and the second overhead code block is used to carry the FlexE Overhead information of the overhead frame.

Optionally, rate adaptation may be performed on the FlexE client signal before the FlexE service frame is mapped to one or more time slots of the physical channel. The rate-adapted FlexE client signal can be exactly mapped to an integer number of time slots of the physical channel.

S1704: Send the FlexE overhead frame through the physical channel.

In this application, the FlexE client signal is converted into a FlexE service frame, and the overhead information of the FlexE client signal is carried in the FlexE service frame, so that end-to-end network management and monitoring of the FlexE client signal can be realized.

Fig. 18 is an exemplary flow chart of a service receiving method provided by an embodiment of the present invention. As shown in FIG. 18, the method can be executed by the receiving end device. The method may include the steps of:

S1801: Receive a FlexE overhead frame from a physical channel.

The FlexE overhead frame can be received directly from the sender device, or can be received after passing through one or more intermediate devices after being sent by the sender device.

S1802: Identify the overhead information of the FlexE overhead frame, demap from one or more time slots of the physical channel to obtain a FlexE service frame according to the overhead information of the FlexE overhead frame, and obtain the FlexE service frame through the overhead information of the FlexE overhead frame through the The second overhead code block of the FlexE overhead frame is carried.

The overhead information of the FlexE frame may include time slot occupancy indication information, which is used to indicate from which time slot/slots the FlexE service frame is acquired.

S1803: Convert the FlexE service frame into a FlexE client signal, the FlexE service frame includes at least one first overhead code block and at least one data code block, and the at least one first overhead code block is used to carry the FlexE client Signal overhead information, the at least one data code block is used to carry payload information of the FlexE client signal.

Optionally, the at least one first overhead code block is periodically identified from the FlexE service frame. Converting the FlexE service frame into a FlexE client signal in units of 1/(2 ⁿ ) of the length of a FlexE service frame, where n is greater than or equal to 0. During the process of converting the FlexE service frame into the FlexE client signal, the synchronization header bits of the FlexE service frame may be deleted, the FlexE service frame may be decoded, and reserved fields may be filled. The at least one first overhead code block is located at the frame header of the FlexE service frame, and/or, the at least one first overhead code block is between any two data code blocks of the FlexE service frame.

In this application, the FlexE service frame is converted into the FlexE client signal, and the overhead information of the FlexE client is carried through the FlexE service frame, so that end-to-end network management and monitoring of the FlexE client signal can be realized.

FIG. 19 is a schematic structural diagram of a sending device 1900 provided by an embodiment of the present invention. The sending device 1900 may be an optical transmission device, an Ethernet device, a flexible Ethernet device, a router, a switch, and the like. As shown in FIG. 19 , the sending device 1900 may include a receiving module 1901 , a processing module 1902 and a sending module 1903 .

The receiving module 1901 is configured to acquire a FlexE client signal.

A processing module 1902, configured to convert the FlexE client signal into a FlexE service frame, the FlexE service frame includes at least one first overhead code block and at least one data code block, and the at least one first overhead code block is used to carry The overhead information of the FlexE client signal, the at least one data code block is used to carry the payload information of the FlexE client signal; the FlexE service frame is mapped to one or more time slots of the physical channel to generate the FlexE overhead frame, where the FlexE overhead frame includes a second overhead code block, where the second overhead code block is used to carry overhead information of the FlexE overhead frame.

The sending module 1903 is configured to send the FlexE overhead frame through the physical channel.

The sending device 1900 may execute the method steps in any one of the implementation manners shown in FIG. 9 , FIG. 12 , FIG. 13 , FIG. 14 , and FIG. 17 .

FIG. 20 is a schematic structural diagram of a receiving device 2000 provided by an embodiment of the present invention. The receiving device 2000 and the sending device 1900 shown in FIG. 19 may be located in the same device, or may be located in different devices. The receiving device 2000 may be an optical transmission device, an Ethernet device, a flexible Ethernet device, a router, a switch, and the like. As shown in FIG. 20 , the receiving device 2000 may include a receiving module 2001 and a processing module 2002 .

The receiving module 2001 is configured to receive a FlexE overhead frame from a physical channel.

The processing module 2002 is configured to identify the overhead information of the FlexE overhead frame, and demap one or more time slots of the physical channel to obtain a FlexE service frame according to the overhead information of the FlexE overhead frame, and the FlexE overhead frame The overhead information is carried by the second overhead code block of the FlexE overhead frame. Converting the FlexE service frame into a FlexE client signal, the FlexE service frame includes at least one first overhead code block and at least one data code block, and the at least one first overhead code block is used to carry the FlexE client signal Overhead information, the at least one data code block is used to carry payload information of the FlexE client signal.

The receiving device 2000 may execute the method steps shown in any one of the implementation manners shown in FIG. 15 and FIG. 18 .

In the above embodiments, all or part of them may be implemented by software, hardware, firmware or any combination thereof. When implemented using software, it may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, all or part of the processes or functions according to the embodiments of the present invention will be generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media. The available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a Solid State Disk (SSD)).

Claims (27)

1. a kind of method that business is sent, which is characterized in that the method includes：

Obtain flexible Ethernet FlexE client signals；

Convert the FlexE client signals to FlexE traffic frames, the FlexE traffic frames include at least one first expense Code block and at least one data code block, at least one first expense code block is for carrying opening for the FlexE client signals Information is sold, at least one data code block is used to carry the payload information of the FlexE client signals；

The FlexE traffic frames are mapped in the one or more time slot of physical channel, FlexE expense frames, the FlexE are generated Expense frame includes the second expense code block, and the second expense code block is used to carry the Overhead of the FlexE expenses frame；

The FlexE expenses frame is sent by the physical channel.

2. the method as described in claim 1, which is characterized in that described to convert the FlexE client signals to FlexE business Frame, including：

At least one first expense Code Block Cycle is inserted into the FlexE traffic frames.

3. method as claimed in claim 1 or 2, which is characterized in that described to convert the FlexE client signals to FlexE Traffic frame, including：

With the 1/ (2 of a FlexE client signal frame lengthⁿ) it is unit, the FlexE client signals are converted to the FlexE Traffic frame, wherein n is greater than or equal to 0.

4. the method as described in claim 1, which is characterized in that by the FlexE traffic frames be mapped to physical channel one or Before in multiple time slots, the method further includes：

Rate adaptation is carried out to the FlexE client signals.

5. method as claimed in claim 1 or 2, which is characterized in that described to convert the FlexE client signals to FlexE Traffic frame, including：

The Overhead of the FlexE client signals is encoded, at least one first expense code block is generated.

6. method as claimed in claim 1 or 2, which is characterized in that at least one first expense code block is located at described The frame head of FlexE traffic frames, and/or, any two numeric data code of at least one first expense code block in FlexE traffic frames Between block.

7. a kind of method that business receives, which is characterized in that the method includes：

Flexible Ethernet FlexE expense frames are received from physical channel；

The Overhead for identifying the FlexE expenses frame, according to the Overhead of the FlexE expenses frame from the physical channel One or more time slot demappings obtain FlexE traffic frames, the Overhead of the FlexE expenses frame passes through the FlexE Second expense code block of expense frame carries；

Convert the FlexE traffic frames to FlexE client signals, the FlexE traffic frames include at least one first expense Code block and at least one data code block, at least one first expense code block is for carrying opening for the FlexE client signals Information is sold, at least one data code block is used to carry the payload information of the FlexE client signals.

8. the method for claim 7, which is characterized in that described to convert the FlexE traffic frames to FlexE client's letter Number, including：

At least one first expense code block is periodically recognized from the FlexE traffic frames.

9. method as claimed in claim 7 or 8, which is characterized in that described to convert the FlexE traffic frames to FlexE visitors Family signal, including：

With the 1/ (2 of a FlexE business frame lengthⁿ) it is unit, convert the FlexE traffic frames to FlexE client signals, Wherein, n is greater than or equal to 0.

10. method as claimed in claim 7 or 8, which is characterized in that described to convert the FlexE traffic frames to FlexE visitors Family signal, including：

The synchronous head bit for deleting the FlexE traffic frames is decoded the FlexE traffic frames, and fills reserved field.

11. method as claimed in claim 7 or 8, which is characterized in that at least one first expense code block is located at described The frame head of FlexE traffic frames, and/or, any two numeric data code of at least one first expense code block in FlexE traffic frames Between block.

12. a kind of sending device, which is characterized in that the equipment includes：

Receiving module, for obtaining flexible Ethernet FlexE client signals；

Processing module, for converting the FlexE client signals to FlexE traffic frames, the FlexE traffic frames include at least One the first expense code block and at least one data code block, at least one first expense code block is for carrying the FlexE The Overhead of client signal, at least one data code block are used to carry the payload information of the FlexE client signals；It will The FlexE traffic frames are mapped in the one or more time slot of physical channel, generate FlexE expense frames, the FlexE expenses frame Including the second expense code block, the second expense code block is used to carry the Overhead of the FlexE expenses frame；

Sending module, for sending the FlexE expenses frame by the physical channel.

13. equipment as claimed in claim 12, which is characterized in that the processing module is used for：

At least one first expense Code Block Cycle is inserted into the FlexE traffic frames.

14. equipment as described in claim 12 or 13, which is characterized in that the processing module is used for：

With the 1/ (2 of a FlexE client signal frame lengthⁿ) it is unit, the FlexE client signals are converted to the FlexE Traffic frame, wherein n is greater than or equal to 0.

15. equipment as claimed in claim 12, which is characterized in that the processing module is additionally operable to：

Rate adaptation is carried out to the FlexE client signals.

16. equipment as described in claim 12 or 13, which is characterized in that described to convert the FlexE client signals to FlexE traffic frames, including：

The Overhead of the FlexE client signals is encoded, at least one first expense code block is generated.

17. equipment as described in claim 12 or 13, which is characterized in that at least one first expense code block is located at described The frame head of FlexE traffic frames, and/or, any two numeric data code of at least one first expense code block in FlexE traffic frames Between block.

18. a kind of receiving device, which is characterized in that the equipment includes：

Receiving module, for receiving flexible Ethernet FlexE expense frames from physical channel；

Processing module, the Overhead of the FlexE expenses frame for identification, according to the Overhead of the FlexE expenses frame FlexE traffic frames, the Overhead of the FlexE expenses frame are obtained from one or more time slot demappings of the physical channel It is carried by the second expense code block of the FlexE expenses frame；

Convert the FlexE traffic frames to FlexE client signals, the FlexE traffic frames include at least one first expense Code block and at least one data code block, at least one first expense code block is for carrying opening for the FlexE client signals Information is sold, at least one data code block is used to carry the payload information of the FlexE client signals.

19. equipment as claimed in claim 18, which is characterized in that the processing module is used for：

At least one first expense code block is periodically recognized from the FlexE traffic frames.

20. the equipment as described in claim 18 or 19, which is characterized in that the processing module is used for：

With the 1/ (2 of a FlexE business frame lengthⁿ) it is unit, convert the FlexE traffic frames to FlexE client signals, Wherein, n is greater than or equal to 0.

21. the equipment as described in claim 18 or 19, which is characterized in that the processing module is used for：

The synchronous head bit for deleting the FlexE traffic frames is decoded the FlexE traffic frames, and fills reserved field.

22. the equipment as described in claim 18 or 19, which is characterized in that at least one first expense code block is located at described The frame head of FlexE traffic frames, and/or, any two numeric data code of at least one first expense code block in FlexE traffic frames Between block.

23. a kind of network system, which is characterized in that the system comprises the sending device as described in claim 12-17 is any, And the receiving device as described in claim 18-22 is any.

24. a kind of computer readable storage medium, including instruction, when run on a computer so that computer executes such as Method described in claim 1-6 any one.

25. a kind of computer readable storage medium, including instruction, when run on a computer so that computer executes such as Method described in claim 7-11 any one.

26. a kind of computer program product including instruction, when run on a computer so that computer executes such as right It is required that the method described in 1-6 any one.

27. a kind of computer program product including instruction, when run on a computer so that computer executes such as right It is required that the method described in 7-11 any one.