CN109600188B

CN109600188B - Data transmission method, transmission equipment and transmission system

Info

Publication number: CN109600188B
Application number: CN201710919348.4A
Authority: CN
Inventors: 向俊凌; 丁炽武
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-09-30
Filing date: 2017-09-30
Publication date: 2020-04-28
Anticipated expiration: 2037-09-30
Also published as: WO2019062227A1; CN109600188A

Abstract

The application provides a data transmission method, transmission equipment and a transmission system. The data transmission method comprises the following steps: acquiring at least one 64B/66B code block stream, wherein the rate of each 64B/66B code block stream is positive integer multiple of 5G; mapping at least one 64B/66B code block stream to a corresponding time slot of at least one flexible optical transport network FlexO frame; adding FlexO overhead to at least one FlexO frame to form a FlexO code block stream; a stream of FlexO code blocks is transmitted. The data transmission method, the transmission equipment and the transmission system can form a simple transmission system and provide a flexible bearing scheme.

Description

Data transmission method, transmission equipment and transmission system

Technical Field

The present application relates to the field of transport networks and, more particularly, to data transmission techniques.

Background

In the flexible Ethernet Implementation proposal (Flex Ethernet Implementation agent) released by the Optical networking Forum (Optical Internet Forum, OIF) in 2016, the concept of flexible Ethernet (flexle Ethernet) interface is proposed. The FlexE specifically establishes several Ethernet Physical Layer (PHY) links into a flexible Ethernet Group (FlexE Group) to support functions such as binding, subrate, channelization, and the like for Ethernet services.

Meanwhile, with the rapid increase of service traffic and the diversification of service types, the fixed rate interface provided by the conventional transport network cannot meet the interconnection requirement, and the industry is more inclined to the flexible rate interface. Thus, the international Telecommunication union Telecommunication standard division for ITU (ITU-T) proposed the concept of a Flexible Optical Transport Network (FlexO) interface.

The application scenarios of FlexE and FlexO are gradually increased, the importance is gradually increased, and the requirement for using FlexO to carry FlexE signals or using FlexE and FlexO for cooperative transmission is also increased. According to the current protocol, the mapping path of the FlexE signal to the FlexO is too long. After receiving the FlexE signal, the transmission device needs to map a flexible ethernet thin layer (FlexE Shim) or a FlexE Client (Client) service to an Optical Data Unit flex (Optical Data Unit-flex, ODUflex), then to an Optical Data Unit cn (oducn), and finally to transmit the FlexO signal. The processing delay and complexity of the mapping process is significant.

Disclosure of Invention

The application provides a data transmission method, transmission equipment and a transmission system, which can form a simple transmission system and provide a flexible bearing scheme.

In a first aspect, an embodiment of the present application provides a data transmission method, including: acquiring at least one 64B/66B code block stream, wherein the rate of each 64B/66B code block stream is positive integer multiple of 5G; mapping the at least one 64B/66B code block stream to a corresponding time slot of at least one flexible optical transport network FlexO frame; adding a FlexO Overhead (OH) to the at least one FlexO frame to form a FlexO code block stream; and transmitting the FlexO code block stream.

In the data transmission method of the first aspect, the 64B/66B code block stream is directly mapped to the corresponding time slot of at least one FlexO frame, and the FlexO code block stream is formed and then transmitted, so that a compact transmission system can be formed, and a flexible bearer scheme is provided.

It should be understood that a 64B/66B code block stream may include a class FlexE frame, which may include a class FlexE data code block and a class FlexE overhead code block. The structure of the FlexE-like frame may be the same as or similar to the structure of the FlexE frame specified by the protocol.

It is also understood that a FlexO frame may include a payload region and an overhead region. The payload region of a FlexO frame may be slotted.

It should also be understood that FlexO frames may be slotted at 16 byte granularity.

In a possible implementation manner of the first aspect, the FlexO overhead comprises slot allocation information, and the slot allocation information is used to indicate a position where the at least one 64B/66B code block stream is mapped to a slot of the at least one FlexO frame. Since the time slot is introduced into the FlexO frame in the data transmission method of the first aspect, the time slot allocation information can be carried in the FlexO overhead, so that the receiving end can perform analysis conveniently.

In a possible implementation manner of the first aspect, the size of the time slot of the FlexO frame is 5G. The size of the division time slot of the FlexO frame is the same as that of the division time slot of the FlexE frame, so that the FlexE service can be more efficiently mapped to the time slot of the FlexO frame.

In a possible implementation manner of the first aspect, the obtaining at least one 64B/66B code block stream includes: receiving a first customer service; carrying out 64B/66B coding on the first customer service to obtain a 64B/66B data code block; rate-adapting the 64B/66B data code block; inserting overhead code blocks into the rate adapted 64B/66B data code blocks to form the at least one 64B/66B code block stream. The realization mode can use FlexO to transmit non-FlexE service, codes other client services into 64B/66B code block streams similar to the FlexE code block streams, and maps the 64B/66B code block streams to the FlexO transmission layer through the FlexE channel layer for transmission, and the process is very efficient and simple.

It should be understood that the first client service may be a non-FlexE service.

In one possible implementation manner of the first aspect, the first customer service includes at least one of a packet service and a fixed bit rate CBR service.

In a possible implementation manner of the first aspect, the obtaining at least one 64B/66B code block stream includes: receiving at least two paths of second customer services; carrying out 64B/66B coding on the at least two paths of second customer services to obtain at least two paths of 64B/66B data code blocks; performing rate adaptation on the at least two paths of 64B/66B data code blocks; respectively inserting overhead code blocks into the at least two paths of 64B/66B data code blocks after rate adaptation to form at least two 64B/66B code block substreams; and multiplexing the at least two 64B/66B code block substreams to obtain the at least one 64B/66B code block stream. The realization mode can transmit the client service with low rate after multiplexing, thereby saving transmission resources and improving transmission efficiency.

It should be appreciated that the second customer service may be a non-FlexE service.

In a possible implementation manner of the first aspect, the obtaining at least one 64B/66B code block stream includes: receiving a Flexe service code block stream, and analyzing the Flexe service code block stream into at least one Flexe client service code block stream, wherein code blocks in the Flexe client service code block stream are 64B/66B code blocks; inserting overhead code blocks into the Flexe customer service code block stream to form the at least one 64B/66B code block stream. The implementation manner of the embodiment can be applied to a scene of a Termination mapping manner.

In a possible implementation manner of the first aspect, the obtaining at least one 64B/66B code block stream includes: and receiving a Flexe service code block stream, and taking the Flexe service code block stream as the at least one 64B/66B code block stream. The implementation manner of the embodiment can be applied to a scene of an Unaware mapping manner.

In a possible implementation manner of the first aspect, the obtaining at least one 64B/66B code block stream includes: and receiving a Flexe service code block stream, deleting unused time slots in the Flexe service code block stream, and taking the Flexe service code block stream with the deleted unused time slots as the at least one 64B/66B code block stream. The implementation manner of the embodiment can be applied to a scene of an Aware mapping manner.

In a second aspect, an embodiment of the present application provides a data transmission method, including: receiving a FlexO code block stream; and resolving at least one 64B/66B code block stream from the time slot of the FlexO frame of the FlexO code block stream according to the FlexO overhead of the FlexO frame in the FlexO code block stream, wherein the rate of each 64B/66B code block stream is positive integer multiple of 5G.

In the data transmission method of the second aspect, at least one 64B/66B code block stream is parsed from the time slot of the FlexO frame of the FlexO code block stream by receiving the FlexO code block stream, so that a compact transmission system can be formed, and a flexible bearer scheme can be provided.

In one possible implementation of the second aspect, the FlexO overhead comprises slot allocation information indicating a position where the at least one 64B/66B code block stream is mapped to a slot of the FlexO frame.

In one possible implementation manner of the second aspect, the size of the time slot of the FlexO frame is 5G.

In a possible implementation manner of the second aspect, the data transmission method further includes: and recovering original traffic data according to the at least one 64B/66B code block stream.

In a third aspect, an embodiment of the present application provides a transmission device, configured to perform the method in the first aspect or any possible implementation manner of the first aspect. In particular, the transmission device may comprise means for performing the method of the first aspect or any possible implementation manner of the first aspect.

In a fourth aspect, an embodiment of the present application provides a transmission device, where the transmission device includes a processor and a memory, where the memory is configured to store instructions, and the processor is configured to execute the instructions stored in the memory, so that the transmission device executes the method in the first aspect or any possible implementation manner of the first aspect.

In a fifth aspect, an embodiment of the present application provides a transmission device, configured to execute the method in the second aspect or any possible implementation manner of the second aspect. In particular, the transmission device may comprise means for performing the method of the second aspect or any possible implementation of the second aspect.

In a sixth aspect, an embodiment of the present application provides a transmission device, where the transmission device includes a processor and a memory, where the memory is configured to store instructions, and the processor is configured to execute the instructions stored in the memory, so that the transmission device executes the method in the second aspect or any possible implementation manner of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer storage medium, on which instructions are stored, and when the instructions are executed on a computer, the computer is caused to execute the method according to the first aspect or any possible implementation manner of the first aspect.

In an eighth aspect, embodiments of the present application provide a computer storage medium having instructions stored thereon, which when executed on a computer, cause the computer to perform the method of the second aspect or any possible implementation manner of the second aspect.

In a ninth aspect, embodiments of the present application provide a computer program product comprising instructions, which when executed by a computer, performs the method of the first aspect or any one of the possible implementation manners of the first aspect.

In a tenth aspect, embodiments of the present application provide a computer program product comprising instructions, which when executed by a computer, performs the method of the second aspect or any possible implementation manner of the second aspect.

In an eleventh aspect, embodiments of the present application provide a transmission system, which includes the transmission apparatus of the third and fifth aspects, or includes the transmission apparatus of the fourth and sixth aspects.

The effects obtained by the third aspect to the eleventh aspect correspond to the effects obtained by the first or second aspect, and are not described in detail herein.

Drawings

FIG. 1 is a schematic diagram of a data plane of one embodiment of the present application.

Fig. 2 is a schematic flow chart of a data transmission method according to an embodiment of the present application.

Fig. 3 is a schematic diagram of mapping each service to FlexO according to an embodiment of the present application.

Fig. 4 is a schematic diagram of information included in a FlexE overhead code block.

FIG. 5 is a schematic diagram of an application scenario of the Termination mapping scheme.

Fig. 6 is a schematic diagram of a FlexO-bearing FlexE service code block flow according to an embodiment of the present application.

Fig. 7 is a schematic diagram of an application scenario of the Unaware mapping approach.

Fig. 8 is a schematic diagram of a FlexO-bearing FlexE service code block flow according to another embodiment of the present application.

FIG. 9 is a schematic diagram of an application scenario of an Aware mapping manner.

Fig. 10 is a schematic diagram of a FlexO-bearing FlexE service code block flow according to another embodiment of the present application.

Fig. 11 is a diagram of a FlexO frame according to an embodiment of the present application.

Fig. 12 is a schematic diagram of a FlexO multiframe according to another embodiment of the present application.

Fig. 13 is a diagram of FlexO overhead for one embodiment of the present application.

Fig. 14 is a schematic block diagram of a transmission apparatus of an embodiment of the present application.

Fig. 15 is a schematic block diagram of a transmission apparatus of another embodiment of the present application.

Fig. 16 is a schematic block diagram of a transmission apparatus of yet another embodiment of the present application.

Fig. 17 is a schematic block diagram of a transmission apparatus of yet another embodiment of the present application.

Fig. 18 is a schematic block diagram of a transmission apparatus of a further embodiment of the present application.

Fig. 19 is a schematic block diagram of a transmission apparatus of yet another embodiment of the present application.

Detailed Description

The technical solution in the present application will be described below with reference to the accompanying drawings.

It should be understood that the physical layer link of the embodiments of the present application may be simply referred to as "link" and may also be referred to as "PHY link".

The following is a brief introduction to the FlexO technique referred to in this specification.

With the rapid increase of traffic and the diversification of traffic types, the fixed rate interface provided by the conventional transport network cannot meet the interconnection requirement, and the industry is more inclined to the flexible rate interface. An international Telecommunication union Telecommunication standard branch office (Telecommunication Standardization Sector) for ITU, ITU-T) establishes an nx100G FlexO group interface, and provides a flexible rate interface based on an n-way 100G rate optical module, so as to be used for bearing optical channel transmission Unit Cn (optical channel Transport Unit Cn, OTUCn) signals and realize interface interconnection between OTUCn signal domains. The multi-channel characteristic and flexibility of the n x 100GFlexO group interface break through the interface form between the traditional single-channel fixed-rate optical channel transmission units k (OTUk). The n x 100G FlexO group interface consists of n paths of 100G FlexO channels, and each path of 100G FlexO channel can be directly realized by using a standard low-cost 100G speed optical module. The n x 100G FlexO group interface can correspondingly adjust the channel number of 100G FlexO along with the specific speed of the carried OTUCn signal, so that the n x 100GFLexO group interface not only can meet the flexibility requirement of an inter-domain interface, but also can greatly reduce the network construction cost.

With the advance of IEEE 802.3 definitions regarding 200GE and 400GE standards, FlexO and FlexE are both currently discussing 200G and 400G port bindings. According to the current protocol, the mapping path of the FlexE signal to the FlexO is too long. After receiving the FlexE signal, the transmission device needs to map a flexible ethernet thin layer (FlexE Shim) or a FlexE Client (Client) service to an Optical Data Unit flex (Optical Data Unit-flex, ODUflex), then to an Optical Data Unit cn (oducn), and finally to transmit the FlexO signal. The processing delay and complexity of the mapping process is significant. With the increasing application scenes of FlexE and FlexO and the increasing importance of FlexE and FlexO, the requirement for using FlexO to carry FlexE signals or using FlexE and FlexO for cooperative transmission is also increasing. How to use FlexO to simply carry FlexE, or how to make FlexE and FlexO cooperate efficiently to form a simple transmission system, provide a flexible carrying scheme, and become a problem to be solved urgently.

In order to solve the above problem, an embodiment of the present application provides a data transmission method, where functions of a corresponding transmission layer and a channel layer are extended, and a FlexE signal can be directly carried by a FlexO, so that cooperative transmission of the FlexE and the FlexO can be enhanced. FIG. 1 is a schematic diagram of a data plane 100 according to one embodiment of the present application. As shown in fig. 1, the data plane 100 includes at least a FlexE channel layer 110 and a FlexO transport layer 120. And the code block stream of the FlexE channel layer is directly mapped to the FlexO transmission layer to form a new transmission system.

As shown in fig. 1, in the sending direction of the embodiment of the present application, the processing flows of services differ according to different types. For example, for a FlexE service, since the service itself is a 64B/66B code block stream, it may be mapped to the FlexO transport layer 120 through the FlexE channel layer 110. For other services, such as video services, Time Division Multiplexing (TDM) services, EtherNet (Eth) services, Common Public Radio Interface (CPRI) services, and other packet services, i.e. dynamic Bit Rate (VBR) services, or Constant Bit Rate (CBR) services, the data plane 100 further needs to have a service adaptation layer 130. The packet traffic and/or CBR traffic is processed by the service adaptation layer 130 to generate a 64B/66B code block stream. The 64B/66B code block stream is then mapped to the FlexO transport layer 120 by the FlexE channel layer 110. The 64B/66B code block stream is mapped to a corresponding time slot of at least one FlexO frame at the FlexO transport layer 120 and added with a FlexO overhead to form a FlexO code block stream. Finally, the transmission device streams out the FlexO code blocks.

It should be understood that the 64B/66B code block stream of the embodiment of the present application may include a class FlexE frame, and the class FlexE frame may include a class FlexE data code block and a class FlexE overhead code block. The structure of the FlexE-like frame may be the same as or similar to the structure of the FlexE frame specified by the protocol, or may be different from the structure of the FlexE frame specified by the protocol, which is not limited in this embodiment of the present application. The rate of the 64B/66B code block stream may be similar to the rate of FlexE as specified by the protocol. For example, the rate of the 64B/66B code block stream may be a positive integer multiple of 5G, such as 5G, 10G, 15G, 20G, 30G, 50G, 60G, or 75G, and so on. The rate of the 64B/66B code block stream may also be a rate other than a positive integer multiple of 5G, which is not limited in the embodiment of the present application.

It should also be understood that the FlexO frame of embodiments of the present application may include a payload region and an overhead region. The payload area of the FlexO frame of the embodiment of the present application may be divided into time slots. The size of the time slot of the FlexO frame may be 5G, or may be other sizes, which is not limited in this embodiment of the present application.

It should also be understood that the time slots of the FlexO frame may be divided according to 16-byte granularity in the embodiments of the present application, and other granularities may also be used to divide the time slots of the FlexO frame. The time slot of the FlexO frame is divided by adopting 16-byte granularity, so that the FlexO frame structure can be well matched. In addition, when Mapping data into a FlexO frame by a General Mapping Procedure (GMP), the existing ODUCn is mapped with a 16-byte granularity. The time slot of the FlexO frame is divided by adopting 16-byte granularity, so that the method and the device can be better compatible with the prior art.

To sum up, a data transmission method according to an embodiment of the present application may include: acquiring at least one 64B/66B code block stream, wherein the rate of each 64B/66B code block stream is positive integer multiple of 5G; mapping at least one 64B/66B code block stream to a corresponding time slot of at least one flexible optical transport network FlexO frame; adding FlexO overhead to at least one FlexO frame to form a FlexO code block stream; a stream of FlexO code blocks is transmitted.

According to the data transmission method, the 64B/66B code block stream is directly mapped to the corresponding time slot of at least one FlexO frame, transmission is carried out after the FlexO code block stream is formed, a simple transmission system can be formed, and therefore a flexible bearing scheme is provided.

Still as shown in fig. 1, in the receiving direction, the receiving end receives the FlexO code block stream through the FlexO transport layer 120 in the embodiment of the present application. At least one 64B/66B code block stream is analyzed from the time slot of the FlexO frame of the FlexO code block stream by the receiving end at a FlexE channel layer 110, and then the original service data is recovered. If the FlexO code block stream carries the FlexE service, the receiving end can analyze the FlexO frame and then directly apply the FlexO frame because the FlexE service is a 64B/66B code block stream. If the FlexO code block stream carries other types of services, such as packet services like video service, TDM service, Eth service, CPRI service, that is, VBR service, or carries CBR service, the data plane 100 further needs the service adaptation layer 130. After the receiving end parses the 64B/66B code block stream from the FlexE channel layer 110, the original packet service and/or CBR service is obtained through parsing by the service adaptation layer 130.

In summary, for the receiving end, another data transmission method according to the embodiment of the present application may include: receiving a FlexO code block stream; and resolving at least one 64B/66B code block stream from the time slot of the FlexO frame of the FlexO code block stream according to the FlexO overhead of the FlexO frame in the FlexO code block stream, wherein the rate of each 64B/66B code block stream is positive integral multiple of 5G. Optionally, the data transmission method may further include: and recovering the original traffic data according to at least one 64B/66B code block stream.

Fig. 2 is a schematic flow chart of a data transmission method according to an embodiment of the present application. Fig. 2 shows a process of transmitting a FlexE service (FlexE service code block stream), an Eth service, a CBR service #1, a CBR service #2, and a CBR service #3 by the method according to the embodiment of the present application. Of course, the method in the embodiment of the present application may be used to transmit more or fewer types of services, and each service may also be processed in other manners, which is not limited in the embodiment of the present application.

The FlexE service code block stream includes FlexE frames and has a rate usually equal to a positive integer multiple of 5G, and can be directly mapped to a corresponding time slot of at least one FlexO frame (e.g., FlexO frame #1, FlexO frame #2, …, FlexO frame # N) as a 64B/66B code block stream (e.g., 64B/66B code block stream # 1).

The Eth service is 64B/66B encoded to obtain 64B/66B data code blocks, then the 64B/66B data code blocks are rate-adapted, and overhead code blocks are inserted into the rate-adapted 64B/66B data code blocks (for example, one overhead code block is inserted into every 1023 × 20 data code blocks), so as to form a 64B/66B code block stream (for example, 64B/66B code block stream # 2). In one specific example, the rate of the 64B/66B code block stream #2 is exactly a positive integer multiple of 5G, and the 64B/66B code block stream #2 is directly mapped to corresponding time slots of at least one FlexO frame (e.g., FlexO frame #1, FlexO frame #2, …, FlexO frame # N).

The CBR service #1 is 64B/66B encoded to obtain a 64B/66B data code block, and then the 64B/66B data code block is rate-adapted. In a specific example, although the rate of the CBR service #1 does not satisfy the positive integer multiple of 5G, the difference is small, and the rate may be made the positive integer multiple of 5G after the IDLE padding is performed on the CBR service # 1. Overhead code blocks are inserted into the rate-adapted 64B/66B data code blocks (e.g., one overhead code block is inserted every 1023 × 20 data code blocks), forming a 64B/66B code block stream (e.g., 64B/66B code block stream # 3). The 64B/66B code block stream #3 is mapped to a corresponding slot of at least one FlexO frame (e.g., FlexO frame #1, FlexO frame #2, …, FlexO frame # N).

The 64B/66B coding is performed by the CBR service #2 to obtain a 64B/66B data code block, then the 64B/66B data code block is rate-adapted to obtain a 64B/66B code block substream # X (which we call a 64B/66B code block substream because of its lower rate), the 64B/66B coding is performed by the CBR service #3 to obtain a 64B/66B data code block, and then the 64B/66B data code block is rate-adapted to obtain a 64B/66B code block substream # Y (which we call a 64B/66B code block substream because of its lower rate). It should be appreciated that the role of rate adaptation here is mainly to clock switch the two services. As mentioned in the foregoing, the slot size of the FlexO frame may be 5G. When the rate of the 64B/66B code block substream # X and the 64B/66B code block substream # Y is low (e.g., the rate of the 64B/66B code block substream is 2.5G), two 64B/66B code block substreams (64B/66B code block substream # X and 64B/66B code block substream # Y) may be multiplexed to form a 64B/66B code block stream #4 that matches the slot grain of the FlexO frame, as shown in fig. 2. The sum of the rates of the 64B/66B code block substream # X and the 64B/66B code block substream # Y may be a positive integer multiple of 5G, or the sum of the rates may not satisfy the positive integer multiple of 5G, but the rate may be a positive integer multiple of 5G after multiplexing and IDLE padding. The multiplexed 64B/66B code block stream #4 is mapped to a corresponding slot of at least one FlexO frame (e.g., FlexO frame #1, FlexO frame #2, …, FlexO frame # N). It should be understood that the 64B/66B code block stream #4 may have a frame structure that differs significantly from the structure of the FlexE frame because it is multiplexed. Accordingly, the obtaining at least one 64B/66B code block stream may include: receiving at least two paths of second customer services; carrying out 64B/66B coding on the at least two paths of second customer services to obtain at least two paths of 64B/66B data code blocks; performing rate adaptation on the at least two paths of 64B/66B data code blocks; respectively inserting overhead code blocks into the at least two paths of 64B/66B data code blocks after rate adaptation to form at least two 64B/66B code block substreams; and multiplexing the at least two 64B/66B code block substreams to obtain the at least one 64B/66B code block stream.

The data transmission method can be applied to transmission of the FlexE service code block stream, and FlexO can simply bear the FlexE, so that the FlexE and the FlexO are efficiently cooperated to form a simple transmission system. In addition, the data transmission method of the embodiment of the application can also be applied to transmitting other types of client services (for example, non-FlexE services), the other client services are encoded into 64B/66B code block streams similar to FlexE code block streams, and the 64B/66B code block streams are mapped to a FlexO transport layer through a FlexE channel layer for transmission, and the process is very efficient and simple.

Fig. 3 is a schematic diagram of mapping each service to FlexO according to an embodiment of the present application. Specifically, in the embodiment of the present application, each path of service is mapped to the FlexO transport layer through the FlexE channel layer. For example, as shown in fig. 3, 3 64B/66B code block streams (64B/66B code block stream # a, 64B/66B code block stream # B, and 64B/66B code block stream # C) are obtained, which can carry the aforementioned services, and the rates are all positive integer multiples of 5G. Each 64B/66B code block stream may be multiplexed (e.g., 64B/66B code block stream # a) or may be non-multiplexed (e.g., 64B/66B code block stream # B and 64B/66B code block stream # C). In the non-multiplexed 64B/66B code block stream # B and 64B/66B code block stream # C, there is one overhead code block at every other data code block (#1, #2, # …, # e-1, # e), and e may be 1023 × 20. In the multiplexed 64B/66B code block stream # a, one overhead code block exists for every predetermined data code block (#1, #2, …, # d-1, # d), and d is not strictly 1023 × 20. The 3 64B/66B code block streams are mapped to the FlexO transport layer by the FlexE channel layer.

It will be appreciated that for customer traffic at a rate well below 5G and no other customer traffic can be multiplexed with it, an alternative is to add a large number of IDLE code blocks directly at rate adaptation to increase its rate to 5G. Another alternative is to generate a low-speed 64B/66B code block substream for the customer traffic and generate at least one 64B/66B code block substream that fills all IDLE code blocks (i.e., the content is empty), the sum of the rates of the at least two 64B/66B code block substreams being 5G. And multiplexing at least two 64B/66B code block substreams and mapping the substreams to corresponding time slots of FlexO. For example: if the 64B/66B code block substream rate carrying customer traffic is 2.5G, a single padded code block substream of the same rate may be generated. As another example, if the 64B/66B code block substream rate carrying customer traffic is 1.25G, three equal rate padded code block substreams may be generated.

The following describes in detail a process for acquiring a 64B/66B code block stream in data transmission according to an embodiment of the present application with reference to several embodiments.

Example 1:

in this embodiment, acquiring at least one 64B/66B code block stream may include: receiving a first client service (e.g., a non-Flexe service); carrying out 64B/66B coding on the first customer service to obtain a 64B/66B data code block; rate adaptation for 64B/66B data code blocks; and inserting overhead code blocks into the rate-adapted 64B/66B data code blocks to form at least one 64B/66B code block stream.

It should be understood that the client service in this embodiment may include at least one of the packet service and the fixed bit rate CBR service described in the foregoing, and may also include other types of client services, which is not limited in this embodiment.

Specifically, the present embodiment uniformly adapts customer traffic to 64B/66B code blocks, and rate adapts 64B/66B data code blocks to coincide with the slot size of a FlexO frame by IDLE puncturing, and then inserts overhead code blocks. For example: an overhead code block is inserted every 1023 x 20 code blocks to monitor the respective traffic. Thereby forming a 64B/66B code block stream for each rate class. Finally, the 64B/66B code block streams of each rate class are mapped into corresponding slots of the FlexO frame.

Fig. 4 is a schematic diagram of information included in a FlexE overhead code block. As shown in fig. 4, 32 consecutive FlexE frames constitute one FlexE multiframe, and one FlexE OH frame is composed of 8 consecutive FlexE OH code blocks. The first code block in the FlexE frame has a "0 x 4B" or "0 x 5" field as a flag field for identifying the code block as an OH code block. The FlexE OH frame transmitted on each link includes fields such as a flexible ethernet Group id (FlexE Group identification), physical link mapping (PHYMap) information, a physical link id (phy identification), a timeslot allocation table (calenar) a, calenar B, a Section Management Channel (Section Management Channel), and a layer-to-layer Management Channel (shim-to-shim Management Channel). There are also some Reserved (Reserved) areas in the FlexE OH frame. The Flexe group pIDentification is used for indicating the number of the flexible Ethernet group where the link is located; the PHY Map is used to indicate the distribution of PHYs included in the flexible ethernet group in which the link is located; the calenar a and the calenar B are respectively used for indicating the current calenar configuration and the standby calenar configuration of the FlexEGroup. The content of the inserted overhead code block of the embodiment of the present application may include additional information in addition to the content of the FlexE overhead code block. For example, the inserted overhead code block of the embodiment of the present application may further include timestamp information, which is used for the receiving end to perform clock recovery on each customer service. Alternatively, the timestamp information may be 32 bits. The inserted overhead code block of the embodiment of the present application may further include Automatic Protection Switching (APS) information. Alternatively, the APS information may be 32 bits. The inserted overhead code block of the embodiment of the present application may further include delay measurement information, which may support loop measurement and one-way measurement. Alternatively, the delay measurement information may be 32 bits. The inserted overhead code block of the embodiment of the present application may further include a path tracking indicator (TTI), which may be defined along 64 bytes of an Optical Transport Network (OTN). Since the indication can be processed slowly, it can be embodied in a multi-frame manner, and an overhead frame can occupy 1 byte or 2 bytes.

The above-mentioned additional information may occupy a Reserved area of the FlexE overhead code block shown in fig. 4, and may also occupy a Section Management Channel (Section Management Channel), which is not limited in this embodiment of the present application.

In a specific example, the accessed signal is a Gigabit Ethernet (GE) service, and the code blocks of the GE service are 8B/10B code blocks. One method of converting an 8B/10B code block into a 64B/65B code block is specified in the standard g.7041, as shown in table 1. The difference between the 64B/66B coding and the 64B/65B coding of the embodiment is that when the 8B (8bit) blocks are added, 1 bit (bit) is not added to form a 65B code block, but a 2bit synchronization head is added to form 66B. The sync header "01" indicates that the following 64 bits are all data. And then rate matching is performed by adding IDLE code blocks. Overhead code blocks are added every 1023 × 20 64B/66B data code blocks.

TABLE 164B/65B transcode TABLE

In the case that the rate of the GE traffic is low, this embodiment may form a 64B/66B code block sub-stream by 64B/66B coding, and form a 5G 64B/66B code block stream by inter-code block interleaving (i.e., multiplexing) the 64B/66B code block sub-stream corresponding to the 4 paths of GE traffic. The specific process of multiplexing has been described in detail in the foregoing, and is not described herein again.

The above description is developed from the perspective of the transmitting end, and for the receiving end, the receiving end parses the 64B/66B code block stream according to the information in the FlexO overhead. For the 5G 64B/66B code block stream formed by multiplexing, the receiving end demultiplexes the original 64B/66B code block stream according to the overhead code block in the analyzed 64B/66B code block stream, and then performs IDLE addition and deletion to obtain the original customer service.

Example 2:

in this embodiment, acquiring at least one 64B/66B code block stream may include: receiving a Flexe service code block stream, and analyzing the Flexe service code block stream into at least one Flexe client service code block stream, wherein code blocks in the Flexe client service code block stream are 64B/66B code blocks; overhead code blocks are inserted into the Flexe client traffic code block stream to form at least one 64B/66B code block stream.

It should be understood that the present embodiment can be considered as mapping 64B/66B code block streams to corresponding time slots of a FlexO frame by means of Termination (Termination) mapping.

FIG. 5 is a schematic diagram of an application scenario of the Termination mapping scheme. Fig. 6 is a schematic diagram of FlexO carrying FlexE service code block streams in Termination mapping manner in an embodiment of the present application. In this embodiment, a sending end of an Optical Transport Network (OTN) receives a FlexE service code block stream. For example, 100G FlexE frame #1, …, 100G FlexE frame # j, …, 100G FlexE frame # m are received through m × 100G FlexE Group shown in fig. 6. The sending terminal senses and terminates the Ethernet thin sheet (Flexe Shim), and analyzes and recovers a flexible Ethernet Client (Flex Ethernet Client) service code block stream. For example, the FlexE Client service code block stream #1, the FlexE Client service code block stream #2, …, the FlexE Client service code block stream # i, …, the FlexE Client service code block stream # j, …, the FlexEClient service code block stream # n-1, and the FlexE Client service code block stream # n shown in fig. 6. And the sending terminal performs rate adaptation on each FlexeE Client service code block stream through an incremental IDLE code block, and inserts an overhead code block into each 1023 × 20 code blocks to form an extended FlexeE code block stream (64B/66B code block stream). It should be understood that the inserted overhead code blocks may be consistent with the overhead code blocks described in embodiment 1, and are not described herein again. Each FlexE Client service code block stream can be flexibly distributed to a time slot of q × 100G FlexO group, and each FlexE Client service code block stream is mapped into one or more FlexO frames according to an IDLE Mapping Procedure (IMP) or GMP method. For example, the codestream is mapped into corresponding slots of the FlexO frame #1, …, the FlexO frame # j, …, and the FlexO frame # q. Among them, a FlexO frame may include p slots (e.g., slot #1, …, slot # j, …, slot # p), and there is a FlexO overhead in the FlexO frame. It should be noted that fig. 12 and the related description give an example of a specific method for performing timeslot division on a FlexO frame, and details are not repeated here. The at least one FlexO frame forms at least one FlexO code block stream, which may be a 100G code block stream.

The above description is developed from the perspective of the transmitting end, and for the receiving end, the receiving end analyzes the extended FlexE code block stream by the IMP/GMP method according to the information in the FlexO overhead. And the receiving end recovers the Flexe Shim according to the overhead code block in the extended Flexe code block stream.

Example 3:

in this embodiment, acquiring at least one 64B/66B code block stream may include: and receiving the Flexe service code block stream, and using the Flexe service code block stream as at least one 64B/66B code block stream.

It should be understood that the present embodiment may be considered as mapping 64B/66B code block streams to corresponding time slots of a FlexO frame by means of an Unaware (Unaware) mapping manner.

Fig. 7 is a schematic diagram of an application scenario of the Unaware mapping approach. Fig. 8 is a schematic diagram of FlexO carrying a FlexE service code block stream in an Unaware mapping manner in another embodiment of the present application. In this embodiment, the transmitting end receives a FlexE service code block stream. For example, 100G FlexE frame #1, …, 100G FlexE frame # j, …, 100G FlexE frame # m are received through m × 100G FlexE Group shown in fig. 8. Each path of the FlexE 100G FlexE frame (i.e. FlexE service code block stream) is processed independently, FlexO does not sense whether the FlexE service is carried, and the FlexE service code block stream is mapped to a corresponding time slot of the FlexO frame according to GMP with 16-byte granularity. Wherein each FlexO frame may include p slots (e.g., slot #1, …, slot # j, …, slot # p), and there is FlexO overhead in the FlexO frame. The embodiment needs to satisfy that the total rate of the FlexE is less than or equal to the total rate of the FlexO, for example, both the FlexE service code block stream and the FlexO code block stream are 100G, and the FlexO frame has only 1 timeslot. If a 100G FlexE service code block stream is mapped into a FlexO frame of a 200G FlexO code block stream, the FlexO frame needs to be divided into 2 slots.

Example 4:

in this embodiment, acquiring at least one 64B/66B code block stream may include: and receiving a Flexe service code block stream, deleting unused time slots in the Flexe service code block stream, and taking the Flexe service code block stream with the deleted unused time slots as at least one 64B/66B code block stream.

It should be understood that the present embodiment can be considered as mapping 64B/66B code block streams to corresponding time slots of a FlexO frame by way of perceptual (Aware) mapping.

Fig. 9 is a schematic diagram of an application scenario of an Aware mapping scheme. Fig. 10 is a schematic diagram of FlexO carrying a FlexE service code block stream in an Aware mapping manner in another embodiment of the present application. In this embodiment, the transmitting end receives a FlexE service code block stream, for example, receives 100G FlexE frames #1, …, 100G FlexE frames # j, …, and 100G FlexE frames # m through an m × 100G FlexE Group shown in fig. 10. The FlexO senses the FlexE service, identifies the time slot use condition of the FlexE Shim, deletes the unused time slot to form an extended FlexE code block stream, and the extended FlexE code block stream respectively has a sub-rate (sub-rate), for example. The FlexE service code block stream is mapped into the corresponding time slots of the FlexO frame in GMP with 16 byte granularity. Among them, a FlexO frame may include p slots (e.g., slot #1, …, slot # j, …, slot # p), and there is a FlexO overhead in the FlexO frame. FlexO may carry FlexE traffic through one or more pipes. In the case of a multi-path bearer, each path needs to have the same transmission path. It should be noted that fig. 12 and the related description give an example of the timeslot division method for the FlexO frame, and details are not repeated here.

The above description is developed from the perspective of the transmitting end, and for the receiving end, the receiving end parses the extended FlexE code block stream according to the information in the FlexO overhead. And the receiving end restores the deleted unused time slot according to the overhead code block in the extended Flexe code block stream, thereby restoring the Flexe Shim.

The FlexO frame of various embodiments of the present application is described in detail below. Fig. 11 is a diagram of a FlexO frame according to an embodiment of the present application. As shown in fig. 11, one FlexO frame may include a frame header (overhead region) of 10 byte block size and a payload (payload) region of 5130 byte block size. Specific division of byte blocks is shown in fig. 12. Fig. 12 is a schematic diagram of a FlexO multiframe according to one embodiment of the present application. As shown in fig. 12, a FlexO frame may include 128 rows of 5440 bits each. Wherein each row includes 300bit Forward Error Correction (FEC). A FlexO frame is divided into 16 bytes and can be divided into 5140 byte blocks (each byte block size is 16 bytes). The header may include Alignment Markers (AM) and OH for a total of 160 bytes (10 byte blocks). According to the above FlexO frame format, if a FlexO code block stream with a slot size of 5G is to be obtained, each FlexO multiframe needs to be divided into 20 slots (time slots). An even number of FlexO frames may constitute a FlexO multiframe, and for example, fig. 12 shows a case where 2 FlexO frames constitute one FlexO multiframe. A 5G time slot may comprise 513 byte blocks, and the first time slot (e.g., referred to as time slot 1, denoted as ts1) as shown in fig. 12 may be comprised of byte blocks ts1.1, ts1.2, …, ts1.i, …, ts1.217, …, ts1.j, …, ts 1.513. The remaining 19 time slots are similar and will not be described further herein. It should be noted that, as shown in fig. 12, the 217 th byte block of slot 1 to slot 10 is in the first FlexO frame of the FlexO multiframe, and the 217 th byte block of slot 11 to slot 20 is in the second FlexO frame of the FlexO multiframe.

It should be understood that the structures of the FlexO frame and the FlexO multiframe shown in fig. 11 and 12 are only exemplary and do not limit the embodiments of the present application. In practical implementations, the size of the FEC area may vary depending on the different techniques of FEC encoding. Or the payload region may have padded code blocks. But none of these affect the division of the FlexO frame by 16 bytes, the payload area of which will remain a positive integer multiple of 16 bytes. In other words, in the above example, one FlexO frame includes a payload area with a size of 5130 byte blocks, which is only an example, and this embodiment of the present application may flexibly deform the payload area to obtain other FlexO frame formats. When the FlexO frame is divided in other formats, the number of FlexO frames included in the FlexO multiframe may not be limited to an even number.

It should also be understood that, in the embodiment of the present application, the time slot may be divided by 5G particles, and may also be divided by other bandwidths, which is not limited in the embodiment of the present application.

Fig. 13 is a schematic structural diagram of a FlexO overhead according to an embodiment of the present application. A complete overhead (hereinafter referred to as FlexO overhead) is constructed by 8 multiframes as shown in fig. 13. Since the time slots are divided in the FlexO frame according to the embodiment of the present application, the FlexO overhead may include time Slot (caledar Slot) allocation information, where the time Slot allocation information is used to indicate a position of the time Slot where the at least one 64B/66B code block stream is mapped to the FlexO frame. I.e. slot allocation information may be included in the FlexO overhead to indicate which slot position each 64B/66B code block stream is mapped to, respectively. Specifically, the timeslot allocation information may include a stream identifier of the 64B/66B code block stream, or a stream identifier of the multiplexed 64B/66B code block stream, or a service type identifier corresponding to the 64B/66B code block stream, which is not limited in this embodiment of the present application.

It is to be understood that in the case where a plurality of 64B/66B code block streams are multiplexed, the slot allocation information in the FlexO overhead indicates that the multiplexed 64B/66B code block streams are mapped to the slot positions of the FlexO frame.

In addition, the FlexO overhead may also include a CR/CA/C field to support slot adjustment and refresh functions. The definition of FlexO overhead can be as shown in fig. 13. The definition of the overhead can follow the corresponding overhead definition of FlexE. The field C is a field for indicating a used slot allocation (capacity configuration in use). The field CR is a slot exchange Request (call Switch Request) field. The field CA is a slot exchange acknowledgement (callback switch acknowledge) field.

The FlexO overhead may further include clock information, where the clock information is used to carry relevant information of a clock channel, such as 1588 message and other information.

The FlexO overhead may further include a Multi-frame Alignment Signal (MFAS), a Group IDentification (GID), a physical link IDentification (PID), a physical link Map (PHY Map, Map), Status (Status, STAT) information, OTUC available (AVAIL) information, a Cyclic Redundancy Check (CRC) bit, and a FlexO management Channel (FCC), and the present embodiment is not limited thereto.

It should be understood that the structure of the FlexO overhead shown in fig. 13 is merely an example, and the FlexO overhead may have other structures, which is not limited in this embodiment of the present application.

Optionally, the data transmission method according to the embodiments of the present application may perform interleaving on the obtained at least one 64B/66B code block stream, complete traffic grooming of the extended FlexE code block stream, and map the at least one 64B/66B code block stream to a corresponding time slot of the at least one FlexO frame after the interleaving. The interleaving may be based on existing TDM interleaving mechanisms and/or cell (cell) interleaving mechanisms.

The data transmission method provided by the embodiment of the present application is described above, and the data transmission device provided by the embodiment of the present application is described below.

Fig. 14 is a schematic block diagram of a transmission apparatus 200 according to an embodiment of the present application. The transmission device 200 is a device on the transmitting side. A transmission apparatus 200 as shown in fig. 14 may include: an obtaining module 210, configured to obtain at least one 64B/66B code block stream, where a rate of each 64B/66B code block stream is a positive integer multiple of 5G; a mapping module 220, configured to map the at least one 64B/66B code block stream acquired by the acquisition module 210 to a corresponding timeslot of at least one flexible optical transport network FlexO frame; an overhead module 230, configured to add a FlexO overhead to the at least one FlexO frame to form a FlexO code block stream; a sending module 240, configured to transmit the FlexO code block stream.

The transmission device in the embodiment of the application directly maps the 64B/66B code block stream to the corresponding time slot of at least one FlexO frame, and transmits the FlexO code block stream after forming the FlexO code block stream, so that a simple transmission system can be formed, and a flexible bearing scheme is provided.

Optionally, as an embodiment, the FlexO overhead includes slot allocation information, and the slot allocation information is used to indicate a position of a slot where the at least one 64B/66B code block stream is mapped to the at least one FlexO frame.

Optionally, as an embodiment, the size of the slot of the FlexO frame is 5G.

Optionally, as an embodiment, the obtaining module 210 is specifically configured to: receiving a first customer service; carrying out 64B/66B coding on the first customer service to obtain a 64B/66B data code block; rate-adapting the 64B/66B data code block; inserting overhead code blocks into the rate adapted 64B/66B data code blocks to form the at least one 64B/66B code block stream.

Optionally, as an embodiment, the client service includes at least one of a packet service and a fixed bit rate CBR service.

Optionally, as an embodiment, the obtaining module 210 is specifically configured to: receiving at least two paths of second customer services; carrying out 64B/66B coding on the at least two paths of second customer services to obtain at least two paths of 64B/66B data code blocks; performing rate adaptation on the at least two paths of 64B/66B data code blocks; respectively inserting overhead code blocks into the at least two paths of 64B/66B data code blocks after rate adaptation to form at least two 64B/66B code block substreams; and multiplexing the at least two 64B/66B code block substreams to obtain the at least one 64B/66B code block stream.

Optionally, as an embodiment, the obtaining module 210 is specifically configured to: receiving a Flexe service code block stream, and analyzing the Flexe service code block stream into at least one Flexe client service code block stream, wherein code blocks in the Flexe client service code block stream are 64B/66B code blocks; inserting overhead code blocks into the Flexe customer service code block stream to form the at least one 64B/66B code block stream.

Optionally, as an embodiment, the obtaining module 210 is specifically configured to: and receiving a Flexe service code block stream, and taking the Flexe service code block stream as the at least one 64B/66B code block stream.

Optionally, as an embodiment, the obtaining module 210 is specifically configured to: and receiving a Flexe service code block stream, deleting unused time slots in the Flexe service code block stream, and taking the Flexe service code block stream with the deleted unused time slots as the at least one 64B/66B code block stream.

Fig. 15 is a schematic block diagram of a transmission apparatus 300 according to an embodiment of the present application. The transmission device 300 is a device on the transmitting side. A transmitting device 300 as shown in fig. 15 may comprise a processor 310 and a memory 320, the memory 310 having stored therein computer instructions, the processor 320 when executing the computer instructions causing the transmitting device 300 to perform the steps of:

acquiring at least one 64B/66B code block stream, wherein the rate of each 64B/66B code block stream is positive integer multiple of 5G;

mapping the at least one 64B/66B code block stream to a corresponding time slot of at least one flexible optical transport network FlexO frame;

adding FlexO overhead to the at least one FlexO frame to form a FlexO code block stream;

and transmitting the FlexO code block stream.

When the processor 320 executes the computer instructions, the transmission device 300 may specifically execute the related embodiments of the foregoing data transmission method, which is not described herein any more.

Optionally, the transmission device 300 may further include a network interface 330 for transmitting data.

It should be understood that the transmission device 200 shown in fig. 14 or the transmission device 300 shown in fig. 15 may be used to perform the operations or processes of the above method embodiments, and the operations and/or functions of each module and device in the transmission device 200 or the transmission device 300 are respectively for implementing the corresponding processes in the above method embodiments, and are not described herein again for brevity.

Fig. 16 is a schematic block diagram of a transmission apparatus 400 according to an embodiment of the present application. The transmission apparatus 400 is an apparatus on the receiving side. A transmission apparatus 400 as shown in fig. 16 may include: a receiving module 410, configured to receive a FlexO code block stream; a first parsing module 420, configured to parse at least one 64B/66B code block stream from a time slot of a FlexO frame in the FlexO code block stream according to a FlexO overhead of the FlexO frame in the FlexO code block stream received by the receiving module 410, where a rate of each 64B/66B code block stream is a positive integer multiple of 5G.

The transmission device of the embodiment of the application receives the FlexO code block stream, analyzes at least one 64B/66B code block stream from the time slot of the FlexO frame of the FlexO code block stream, and can form a simple transmission system, thereby providing a flexible bearing scheme.

Optionally, as an embodiment, the FlexO overhead includes slot allocation information, and the slot allocation information is used to indicate a position where the at least one 64B/66B code block stream is mapped to a slot of the FlexO frame.

Optionally, as an embodiment, the size of the slot of the FlexO frame is 5G.

Optionally, as an embodiment, the transmission device 400 further includes a second parsing module, configured to: and restoring original service data according to the at least one 64B/66B code block stream obtained by the analysis of the first analysis module.

Fig. 17 is a schematic block diagram of a transmission apparatus 500 according to an embodiment of the present application. The transmission apparatus 500 is an apparatus on the receiving side. A transmitting device 500 as shown in fig. 17 may comprise a processor 510 and a memory 520, the memory 510 having stored therein computer instructions, which when executed by the processor 520, cause the transmitting device 500 to perform the steps of:

receiving a FlexO code block stream;

and resolving at least one 64B/66B code block stream from the time slot of the FlexO frame of the FlexO code block stream according to the FlexO overhead of the FlexO frame in the FlexO code block stream, wherein the rate of each 64B/66B code block stream is positive integer multiple of 5G.

When the processor 520 executes the computer instructions, the transmission device 500 may specifically execute the related embodiments of the foregoing data transmission method, which is not described herein any more.

Optionally, the transmission device 500 may further comprise a network interface 530 for transmitting data.

It should be understood that the transmission device 400 shown in fig. 16 or the transmission device 500 shown in fig. 17 may be used to perform the operations or processes of the above method embodiments, and the operations and/or functions of each module and device in the transmission device 400 or the transmission device 500 are respectively for implementing the corresponding processes in the above method embodiments, and are not described herein again for brevity.

Fig. 18 is a schematic block diagram of a transmission apparatus 600 according to an embodiment of the present application. The transmission apparatus 600 is an apparatus of a transmitting end. The transmission apparatus 600 has a crossover or scheduling capability and is structured as a branch line splitting structure. As shown in fig. 16, the transmission device 600 may include three chips, a tributary board 610, a cross board 620, and a line board 630. The tributary board is used for receiving traffic, and performs at least one of code block type conversion (transcoding), stream slicing, Shim processing, 64B/66B encoding, rate adaptation, multiplexing, and demultiplexing, and the processing performed by the tributary board is not limited thereto. For example, for the Eth service, the tributary board shown in fig. 18 first completes code block type conversion and rate adaptation (completed by the transcoding adaptation module 611), then inserts overhead code blocks to form an extended FlexE code block stream (completed by the class FlexE module 612), and then sends the extended FlexE code block stream to the class multiplexing module 613 (if the receiving device is a class demultiplexing module for demultiplexing, not shown in the figure) for multiplexing, although multiplexing may not be needed. As another example, for TDM services, slicing and rate adaptation of data stream are performed (performed by the slice adaptation module 614), overhead is inserted to form an extended FlexE code block stream (performed by the class FlexE module 615), and then the extended FlexE code block stream is sent to the class multiplexing module 613 for multiplexing (or multiplexing may not be required). For another example, for a FlexE service, after standard Shim processing (completed by Shim module 616), the service may be directly sent to the next module (for example, class multiplexing module 613, or may be directly sent to cross board 620), or after standard Shim is terminated, the service may be inserted into overhead to form an extended FlexE code block stream (completed by class FlexE module 617), and then sent to the next module. The cross board is used for grooming and adapting the traffic. The line card is used for at least one of multiplexing, demultiplexing, mapping, FlexO framing, and sending out over the PHY interface, and the processing by the line card is not limited thereto. For example, fig. 18 shows a mapping module 631, a mapping module 632, a FlexO framing module 633, a FlexO framing module 634, a PHY interface 635, a PHY interface 636, and a class multiplexing module 637 (if the receiving device can be a class demultiplexing module for demultiplexing, not shown).

It should be understood that the corresponding receiving end device has a similar structure to the transmitting device 600, except that the data transmission direction is opposite, and will not be described herein again.

Fig. 19 is a schematic block diagram of a transmitting device 700 of one embodiment of the present application. The transmission apparatus 700 is a transmitting-end apparatus. The transmission apparatus 700 is used for fixed line transmission, and is a repeater (transponder) or a muxponder (muxponder), and has no cross module or cross board, including one chip. As shown in fig. 19, the transmission apparatus 700 may include a transcoding adaptation module 701 and a class FlexE module 702, configured to process Eth traffic; a slice adaptation module 703 and a class FlexE module 704, configured to process TDM traffic; a Shim module 705 and a class FlexE module 706, which are used for processing FlexE services; the class multiplexing module 707 is used for multiplexing (if it is a receiving end device, it may be a class demultiplexing module for demultiplexing, not shown in the figure); the mapping module 708, the mapping module 709, the FlexO framing module 710, the FlexO framing module 711, the PHY interface 712, and the PHY interface 713 are configured to map the extended FlexE code block stream to FlexO and frame, and finally send out.

It should be understood that the corresponding receiving end device has a similar structure to the transmitting device 700, except that the data transmission direction is reversed, and will not be described herein again.

It should be noted that, for example, the two devices shown in fig. 18 and fig. 19 may perform the steps in the foregoing method embodiments, and are not described herein again.

It should be understood that the processor mentioned in the embodiments of the present Application may be a Central Processing Unit (CPU), and may also be other general purpose processors, Digital Signal Processors (DSP), Application Specific Integrated Circuits (ASIC), Field Programmable Gate Arrays (FPGA) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It will also be appreciated that the memory referred to in the embodiments of the application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The non-volatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable PROM (EEPROM), or a flash Memory. Volatile Memory can be Random Access Memory (RAM), which acts as external cache Memory. By way of example, but not limitation, many forms of RAM are available, such as Static random access memory (Static RAM, SRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic random access memory (Synchronous DRAM, SDRAM), Double data rate Synchronous Dynamic random access memory (DDR SDRAM), Enhanced Synchronous SDRAM (ESDRAM), Synchronous link SDRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

It should be noted that when the processor is a general-purpose processor, a DSP, an ASIC, an FPGA or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component, the memory (memory module) is integrated in the processor.

It should be noted that the memory described herein is intended to comprise, without being limited to, these and any other suitable types of memory.

The embodiment of the present application further provides a computer-readable storage medium, on which instructions are stored, and when the instructions are executed on a computer, the instructions cause the computer to execute the data transmission method of the above method embodiment.

The embodiment of the present application further provides a computer program product including instructions, where when a computer runs the instructions of the computer program product, the computer executes the data transmission method of the above method embodiment.

An embodiment of the present application further provides a transmission system, including: the transmission device of the sending end in the embodiment of the present application and the transmission device of the receiving end in the embodiment of the present application.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, 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 loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored on a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website, computer, server, or data center to another website, computer, server, or data center via wire (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., Digital Video Disk (DVD)), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It should be understood that the reference herein to first, second, and various numerical designations is merely a convenient division to describe and is not intended to limit the scope of the present application.

It should be understood that the term "and/or" herein is merely one type of association relationship that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.

It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of data transmission, comprising:

and transmitting the FlexO code block stream.

2. The data transmission method according to claim 1, wherein the FlexO overhead comprises slot allocation information indicating the position of the slot where the at least one 64B/66B code block stream is mapped to the at least one FlexO frame.

3. The data transmission method according to claim 1, wherein the size of the time slot of the FlexO frame is 5G.

4. The data transmission method according to claim 1, wherein the obtaining at least one 64B/66B code block stream comprises:

receiving a first customer service;

carrying out 64B/66B coding on the first customer service to obtain a 64B/66B data code block;

rate-adapting the 64B/66B data code block;

inserting overhead code blocks into the rate adapted 64B/66B data code blocks to form the at least one 64B/66B code block stream.

5. The data transmission method of claim 4, wherein the first customer service comprises at least one of a packet service and a fixed bit rate (CBR) service.

6. The data transmission method according to any one of claims 1 to 5, wherein the obtaining at least one 64B/66B code block stream comprises:

receiving at least two paths of second customer services;

carrying out 64B/66B coding on the at least two paths of second customer services to obtain at least two paths of 64B/66B data code blocks;

performing rate adaptation on the at least two paths of 64B/66B data code blocks;

respectively inserting overhead code blocks into the at least two paths of 64B/66B data code blocks after rate adaptation to form at least two 64B/66B code block substreams;

and multiplexing the at least two 64B/66B code block substreams to obtain the at least one 64B/66B code block stream.

7. The data transmission method according to any one of claims 1 to 5, wherein the obtaining at least one 64B/66B code block stream comprises:

receiving a Flexe service code block stream, and analyzing the Flexe service code block stream into at least one Flexe client service code block stream, wherein code blocks in the Flexe client service code block stream are 64B/66B code blocks;

inserting overhead code blocks into the Flexe customer service code block stream to form the at least one 64B/66B code block stream.

8. The data transmission method according to any one of claims 1 to 5, wherein the obtaining at least one 64B/66B code block stream comprises:

and receiving a Flexe service code block stream, and taking the Flexe service code block stream as the at least one 64B/66B code block stream.

9. The data transmission method according to any one of claims 1 to 5, wherein the obtaining at least one 64B/66B code block stream comprises:

and receiving a Flexe service code block stream, deleting unused time slots in the Flexe service code block stream, and taking the Flexe service code block stream with the deleted unused time slots as the at least one 64B/66B code block stream.

10. A transmitting device comprising a processor and a memory, the memory having stored therein computer instructions that, when executed by the processor, cause the transmitting device to perform the steps of:

and transmitting the FlexO code block stream.

11. The transmission apparatus according to claim 10, wherein the FlexO overhead comprises slot allocation information indicating the position of the slot where the at least one 64B/66B code block stream is mapped to the at least one FlexO frame.

12. Transmission device according to claim 10, characterized in that the size of the time slots of the FlexO frame is 5G.

13. The transmission device of claim 10, wherein the processor, when executing the computer instructions, causes the transmission device to perform in particular:

receiving a first customer service;

rate-adapting the 64B/66B data code block;

14. The transmission apparatus of claim 13, wherein the first customer service comprises at least one of a packet service and a fixed bit rate CBR service.

15. The transmission apparatus according to any one of claims 10 to 14, wherein the processor, when executing the computer instructions, causes the transmission apparatus to perform in particular:

receiving at least two paths of second customer services;

16. The transmission apparatus according to any one of claims 10 to 14, wherein the processor, when executing the computer instructions, causes the transmission apparatus to perform in particular:

17. The transmission apparatus according to any one of claims 10 to 14, wherein the processor, when executing the computer instructions, causes the transmission apparatus to perform in particular:

18. The transmission apparatus according to any one of claims 10 to 14, wherein the processor, when executing the computer instructions, causes the transmission apparatus to perform in particular:

19. A method of data transmission, comprising:

receiving a FlexO code block stream;

20. The data transmission method according to claim 19, wherein the FlexO overhead comprises slot allocation information indicating the position of the slot where the at least one 64B/66B code block stream is mapped to the FlexO frame.

21. The data transmission method according to claim 19 or 20, wherein the size of the time slot of the FlexO frame is 5G.

22. The data transmission method according to claim 19 or 20, characterized in that the data transmission method further comprises:

and recovering original traffic data according to the at least one 64B/66B code block stream.

23. A transmitting device comprising a processor and a memory, the memory having stored therein computer instructions that, when executed by the processor, cause the transmitting device to perform the steps of:

receiving a FlexO code block stream;

24. The transmission apparatus according to claim 23, wherein the FlexO overhead comprises slot allocation information indicating the position of the slot to which the at least one 64B/66B code block stream is mapped in the FlexO frame.

25. Transmission apparatus according to claim 23 or 24, characterized in that the size of the time slots of the FlexO frame is 5G.

26. The transmission apparatus according to claim 23 or 24, wherein the computer instructions, when executed, further cause the transmission apparatus to perform the steps of:

27. A transmission system, comprising: the transmission apparatus of any one of claims 10 to 18 and the transmission apparatus of any one of claims 23 to 26.