WO2019062227A1 - Data transmission method, transmission device and transmission system - Google Patents

Abstract

Provided are a data transmission method, transmission device and transmission system. The data transmission method comprises: acquiring at least one 64B/66B code block stream, the rate of each 64B/66B code block stream being a 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 a FlexO overhead to at least one FlexO frame to form a FlexO code block stream; and transmitting the FlexO code block stream. The data transmission method, transmission device and transmission system provided by the present application can form a simple transmission system and provide a flexible bearer solution.

Description

Data transmission method, transmission device and transmission system

This application claims the priority of the Chinese Patent Application entitled "Data Transmission Method, Transmission Equipment, and Transmission System" filed on September 30, 2017 by the Chinese Patent Office, Application No. 201710919348.4, the entire contents of which is incorporated herein by reference. In the application.

Technical field

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

Background technique

The Optical Internet Forum (OIF) proposed the concept of Flexible Ethernet (FlexE) interface in the Flexible Ethernet Implementation Agreement released in April 2016. FlexE specifically establishes several Ethernet physical layer (PHY) links into a flexible Ethernet group (FlexE Group) to support binding, sub-rate, channelization, etc. for Ethernet services. Features.

At the same time, with the rapid growth of service traffic and the diversification of service types, the fixed rate interface provided by the traditional transmission network can no longer meet the interconnection requirements, and the industry prefers the flexible rate interface. Therefore, the Telecommunication Standardization Sector for ITU (ITU-T) proposes the concept of a Flexible Optical Transport Network (FlexO) interface.

The application scenarios of FlexE and FlexO are gradually increasing, and the importance is gradually increasing. The need to use FlexO to carry FlexE signals or use FlexE to coordinate with FlexO is also increasing. According to the current protocol, the mapping path of FlexE signals to FlexO is too long. After receiving the FlexE signal, the transmission device needs to map the flexible Ethernet thin layer (FlexE Shim) or the FlexE client (Client) service to the optical data unit flex (ODUflex), and then to the optical data unit Cn. (ODUCn), and finally transmitted through FlexO. The processing delay and complexity of this mapping process are large.

Summary of the invention

The present application provides a data transmission method, a transmission device, and a transmission system, which can form a simple transmission system and provide a flexible bearer solution.

In a first aspect, the embodiment of the present application provides a data transmission method, including: acquiring at least one 64B/66B code block stream, and the rate of each of the 64B/66B code block streams is a 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 a FlexO overhead (Overhead, OH) to the at least one FlexO frame to form a FlexO code block stream; transmitting the FlexO code Block flow.

The data transmission method of the first aspect directly maps the 64B/66B code block stream to corresponding time slots of at least one FlexO frame, and forms a FlexO code block stream for transmission, thereby forming a compact transmission system, thereby providing a flexible bearer solution.

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

It should also be understood that a FlexO frame may include a payload area and an overhead area. The payload area of a FlexO frame can be divided into time slots.

It should also be understood that FlexO frames can be divided into time slots in a 16 byte granularity.

In a possible implementation manner of the first aspect, the FlexO overhead includes time slot allocation information, where the time slot allocation information is used to indicate that the at least one 64B/66B code block stream is mapped to the at least one FlexO The location of the time slot of the frame. Since the data transmission method of the first aspect introduces a time slot in the FlexO frame, the time slot allocation information can be carried in the FlexO overhead for the receiving end to perform parsing.

In a possible implementation manner of the first aspect, the size of the time slot of the FlexO frame is 5G. In this implementation, the size of the FlexO frame division slot is the same as the size of the FlexE frame division slot, which facilitates more efficient mapping of the FlexE service to the slot of the FlexO frame.

In a possible implementation manner of the first aspect, the acquiring the at least one 64B/66B code block stream includes: receiving a first client service, performing 64B/66B encoding on the first client service, and obtaining 64B/66B a data code block; performing rate adaptation on the 64B/66B data code block; inserting an overhead code block into the rate-adapted 64B/66B data code block to form the at least one 64B/66B code block stream. This implementation can use FlexO to transmit non-FlexE services, encode other client services into a 64B/66B code block stream like a FlexE code block stream, and map to the FlexO transport layer for transmission through the FlexE channel layer. This process is very efficient and simple.

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

In a 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 acquiring the at least one 64B/66B code block stream includes: receiving at least two second client services; performing 64B/66B on the at least two second client services Encoding, obtaining at least two 64B/66B data code blocks; performing rate adaptation on the at least two 64B/66B data code blocks; inserting an overhead code in at least two 64B/66B data code blocks after rate adaptation Blocking, forming at least two 64B/66B code block substreams; multiplexing the at least two 64B/66B code block substreams to obtain the at least one 64B/66B code block stream. In this implementation manner, the low-rate customer service can be multiplexed and transmitted, which can save transmission resources and improve transmission efficiency.

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

In a possible implementation manner of the first aspect, the acquiring the at least one 64B/66B code block stream includes: receiving a FlexE service code block stream, and parsing the FlexE service code block stream into at least one FlexE client service code a block stream, the code block in the FlexE client service code block stream is a 64B/66B code block; an overhead code block is inserted in the FlexE client service code block stream to form the at least one 64B/66B code block stream. The implementation of this embodiment can be applied to the scenario of the Termination mapping mode.

In a possible implementation manner of the first aspect, the acquiring the at least one 64B/66B code block stream includes: receiving a FlexE service code block stream, and using the FlexE service code block stream as the at least one 64B/66B Code block stream. The implementation of this embodiment can be applied to the scenario of the Unaware mapping mode.

In a possible implementation manner of the first aspect, the acquiring the at least one 64B/66B code block stream includes: receiving a FlexE service code block stream, deleting an unused time slot in the FlexE service code block stream, The FlexE service code block stream after the unused time slot is deleted as the at least one 64B/66B code block stream. The implementation of this embodiment can be applied to the scenario of the Aware mapping mode.

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

The data transmission method of the second aspect, by receiving the FlexO code block stream, parsing at least one 64B/66B code block stream from the time slot of the FlexO frame of the FlexO code block stream, can form a compact transmission system, thereby providing flexible bearer Program.

In a possible implementation manner of the second aspect, the FlexO overhead includes time slot allocation information, where the time slot allocation information is used to indicate that the at least one 64B/66B code block stream is mapped to the FlexO frame. The location of the time slot.

In a 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: recovering original service data according to the at least one 64B/66B code block stream.

In a third aspect, the embodiment of the present application provides a transmission device, which is used to perform the method in any of the foregoing first aspect or the first aspect. In particular, the transmission device may comprise means for performing the method of the first aspect or any of the possible implementations 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 used to store an instruction, and the processor is configured to execute the instruction stored in the memory, so that the transmission device Performing the method of the first aspect or any of the possible implementations of the first aspect.

In a fifth aspect, the embodiment of the present application provides a transmission device, which is used to perform the method in any of the foregoing possible implementation manners of the second aspect or the second aspect. In particular, the transmission device may comprise means for performing the method of any of the possible implementations of the second aspect or 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 used to store an instruction, and the processor is configured to execute the instruction stored in the memory, so that the transmission device Performing the method of the second aspect or any of the possible implementations of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer storage medium having stored thereon instructions that, when executed on a computer, cause the computer to perform any of the first aspect or the first aspect of the first aspect. The method described in the manner.

In an eighth aspect, an embodiment of the present application provides a computer storage medium, where instructions are stored, and when the instruction is run on a computer, the computer is configured to perform any possible implementation of the second aspect or the second aspect. The method described in the manner.

In a ninth aspect, the embodiment of the present application provides a computer program product comprising instructions, when the computer runs the finger of the computer program product, the computer performs the first aspect or any possible implementation of the first aspect The method described in the manner.

In a tenth aspect, the embodiment of the present application provides a computer program product, including instructions, when the computer runs the finger of the computer program product, the computer performs any possible implementation of the second aspect or the second aspect. The method described in the manner.

In an eleventh aspect, the embodiment of the present application provides a transmission system, including the transmission device of the third and fifth aspects, or the transmission device of the fourth and sixth aspects.

The effects that can be obtained by the third aspect to the eleventh aspect correspond to the effects that can be obtained by the first or second aspects, and are not described herein again.

DRAWINGS

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

FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present application.

FIG. 3 is a schematic diagram of mapping various services to FlexO according to an embodiment of the present application.

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 a termination mapping method.

6 is a schematic diagram of a FlexO bearer FlexE service code block stream according to an embodiment of the present application.

FIG. 7 is a schematic diagram of an application scenario of the Unaware mapping mode.

FIG. 8 is a schematic diagram of a FlexO bearer FlexE service code block stream according to another embodiment of the present application.

Figure 9 is a schematic diagram of an application scenario of the Aware mapping mode.

FIG. 10 is a schematic diagram of a FlexO bearer FlexE service code block stream according to another embodiment of the present application.

11 is a schematic diagram of a FlexO frame of one embodiment of the present application.

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

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

FIG. 14 is a schematic block diagram of a transmission device of an embodiment of the present application.

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

16 is a schematic block diagram of a transmission device of still another embodiment of the present application.

FIG. 17 is a schematic block diagram of a transmission device according to still another embodiment of the present application.

FIG. 18 is a schematic block diagram of a transmission device according to still another embodiment of the present application.

FIG. 19 is a schematic block diagram of a transmission device according to still another embodiment of the present application.

Detailed ways

The technical solutions 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 embodiment of the present application may be simply referred to as a “link” and may also be referred to as a “PHY link”.

A brief introduction to the FlexO technology in this manual is given below.

With the rapid growth of service traffic and the diversification of service types, the fixed rate interface provided by the traditional transmission network can no longer meet the interconnection requirements, and the industry prefers the flexible rate interface. The Telecommunication Standardization Sector for ITU (ITU-T) has developed an n×100G FlexO interface, which provides a flexible rate interface based on n-channel 100G rate optical modules for carrying optical channel transmission units Cn (Optical Channel). Transport Unit Cn, OTUCn) signal to achieve interface interconnection between OTUCn signal domains. The multi-channel characteristics and flexibility of the n×100G FlexO group interface breaks the interface form between the traditional single-channel fixed-rate optical channel transmission unit k (OTUk) domain. The n×100G FlexO group interface consists of n 100G FlexO channels, and each 100G FlexO channel can be directly implemented using standard low-cost 100G rate optical modules. The n×100G FlexO group interface can adjust the number of channels of the 100G FlexO according to the specific rate of the OTUCn signal carried, so that the n×100G FlexO interface can not only meet the flexibility requirements of the inter-domain interface, but also greatly reduce the flexibility. Network construction costs.

With the advancement of the IEEE 802.3 definition of the 200GE and 400GE standards, both FlexO and FlexE are discussing port bonding for 200G and 400G. According to the current protocol, the mapping path of FlexE signals to FlexO is too long. After receiving the FlexE signal, the transmission device needs to map the flexible Ethernet thin layer (FlexE Shim) or the FlexE client (Client) service to the optical data unit flex (ODUflex), and then to the optical data unit Cn. (ODUCn), and finally transmitted through FlexO. The processing delay and complexity of this mapping process are large. As the application scenarios of FlexE and FlexO increase, the importance increases, and the need to use FlexO to carry FlexE signals or use FlexE to coordinate with FlexO is increasing. How to use FlexO to simply carry FlexE, or how to make FlexE and FlexO work together efficiently to form a compact transmission system and provide a flexible bearer solution becomes an urgent problem to be solved.

In order to solve the above problem, the embodiment of the present application provides a data transmission method, which expands the corresponding transmission layer and channel layer functions, and the FlexO can directly carry the FlexE signal, thereby enhancing the coordinated transmission of the FlexE and the FlexO. 1 is a schematic diagram of a data plane 100 of one embodiment of the present application. As shown in FIG. 1, data plane 100 includes at least FlexE channel layer 110 and FlexO transport layer 120. The code block stream of the FlexE channel layer maps directly to the FlexO transport 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 flow of the service is different according to the type thereof. For example, for the FlexE service, since the service itself is a 64B/66B code block stream, it can 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 (EtherNet, Eth) services, and Common Public Radio Interface (CPRI) services, that is, dynamic bits. The data plane 100 also needs to have a service adaptation layer 130, which is a variable bit rate (VBR) service or a fixed bit rate (CBR) service. After the packet service and/or CBR service is processed by the service adaptation layer 130, a 64B/66B code block stream is generated. The 64B/66B code block stream is then mapped to the FlexO transport layer 120 through the FlexE channel layer 110. The 64B/66B code block stream is mapped to the corresponding time slot of at least one FlexO frame at the FlexO transport layer 120 and is added with FlexO overhead. Form a FlexO code block stream. Finally, the transmission device streams the FlexO code block out.

It should be understood that the 64B/66B code block stream in the embodiment of the present application may include a FlexE-like frame, and the FlexE-like frame may include a FlexE-like data code block and a FlexE-like 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, and may be different. The rate of the 64B/66B code block stream can be similar to the rate of the FlexE 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 the like. 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 this embodiment of the present application.

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

It should also be understood that the embodiment of the present application may divide the time slot of the FlexO frame according to the 16-byte granularity, or may divide the time slot of the FlexO frame by other granularity. The time slot of the FlexO frame is divided by 16-byte granularity, which can well match the FlexO frame structure. In addition, when the existing ODUCn maps data into a FlexO frame through the Generic Mapping Procedure (GMP), it is mapped with 16-byte granularity. The embodiment of the present application divides the time slot of the FlexO frame by using 16-byte granularity, which can be better compatible with the existing technology.

In summary, a data transmission method in the embodiment of the present application may include: acquiring at least one 64B/66B code block stream, each 64B/66B code block stream rate is a positive integer multiple of 5G; at least one 64B/ The 66B code block stream is mapped to corresponding time slots of at least one flexible optical transport network FlexO frame; FlexO overhead is added for at least one FlexO frame to form a FlexO code block stream; and the FlexO code block stream is transmitted.

The data transmission method of the embodiment of the present application directly maps the 64B/66B code block stream to the corresponding time slot of at least one FlexO frame, and forms a FlexO code block stream for transmission, thereby forming a compact transmission system, thereby providing a flexible bearer solution. .

As shown in FIG. 1 , in the receiving direction, the receiving end receives the FlexO code block stream through the FlexO transport layer 120. At the FlexE channel layer 110, the receiving end parses at least one 64B/66B code block stream from the time slot of the FlexO frame of the FlexO code block stream, thereby recovering the original service data. If the FlexE code stream carries the FlexE service, the FlexE service itself is a 64B/66B code block stream, and the receiving end directly parses the FlexO frame and applies it. If the FlexO code block stream carries other types of services, such as a video service, a TDM service, an Eth service, a CPRI service, or the like, that is, a VBR service, or carries a CBR service, the data plane 100 also needs the service adaptation layer 130. . After receiving the 64B/66B code block stream from the FlexE channel layer 110, the receiving end parses the original packet service and/or CBR service through the service adaptation layer 130.

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

FIG. 2 is a schematic flowchart of a data transmission method according to an embodiment of the present application. FIG. 2 shows a process of transmitting the FlexE service (FlexE service code block stream), Eth service, CBR service #1, CBR service #2, and CBR service #3 by the method of the embodiment of the present application. Certainly, the method in this embodiment of the present application may be used to transmit more or less types of services, and the services may be processed in other manners.

The FlexE service code block stream includes a FlexE frame and is typically at a positive integer multiple of 5G, and can be directly mapped to at least one FlexO frame (eg, FlexO) as a 64B/66B code block stream (eg, 64B/66B code block stream #1). Frame #1, FlexO frame #2, ..., FlexO frame #N) corresponding time slot.

Perform 64B/66B encoding on the Eth service, obtain a 64B/66B data code block, and then perform rate adaptation on the 64B/66B data code block, and insert an overhead code block into the rate-matched 64B/66B data code block (for example, each 1023*20 data code blocks are inserted into an overhead code block) to form a 64B/66B code block stream (for example, 64B/66B code block stream #2). In a specific example, the rate of 64B/66B code block stream #2 is exactly a positive integer multiple of 5G, and 64B/66B code block stream #2 is directly mapped to at least one FlexO frame (eg, FlexO frame #1, FlexO). The corresponding time slot of frame #2, ..., FlexO frame #N).

The 64B/66B encoding is performed on the CBR service #1, and the 64B/66B data code block is obtained, and then the 64B/66B data code block is rate-adapted. In a specific example, the rate of CBR service #1 does not satisfy the positive integer multiple of 5G, but the difference is small. After IDLE filling of CBR service #1, the rate can be a positive integer multiple of 5G. Inserting an overhead code block into the rate-matched 64B/66B data code block (for example, inserting an overhead code block every 1023*20 data code blocks) to form a 64B/66B code block stream (for example, a 64B/66B code block stream) #3). The 64B/66B code block stream #3 is mapped to the corresponding time slot of at least one FlexO frame (eg, FlexO frame #1, FlexO frame #2, ..., FlexO frame #N).

64B/66B encoding is performed by CBR service #2, 64B/66B data code block is obtained, and then 64B/66B data code block is rate-adapted to obtain 64B/66B code block sub-stream #X (due to its low rate, we call It is a 64B/66B code block substream), 64B/66B encoding is performed by CBR service #3, 64B/66B data code block is obtained, and then the 64B/66B data code block is rate-adapted to obtain a 64B/66B code block substream. #Y(Because of its low rate, we call it a 64B/66B code block substream). It should be understood that the role of rate adaptation here is mainly to clock the two services. As mentioned in the foregoing, the size of the time slot of the FlexO frame can be 5G. When the rate of the 64B/66B code block substream #X and 64B/66B code block substream #Y is low (for example, the rate of the 64B/66B code block substream is 2.5G), as shown in FIG. 2, two pairs can be used. The 64B/66B code block substream (64B/66B code block substream #X and 64B/66B code block substream #Y) is multiplexed to form a 64B/66B code block stream #4 that matches the slot particles of the FlexO frame. The rate of the 64B/66B code block substream #X and 64B/66B code block substream #Y can be a positive integer multiple of 5G, or the rate and does not satisfy the positive integer multiple of 5G, but after multiplexing and IDLE filling It can be made to have a positive integer multiple of 5G. The multiplexed 64B/66B code block stream #4 is mapped to a corresponding time slot of at least one FlexO frame (eg, FlexO frame #1, FlexO frame #2, ..., FlexO frame #N). It should be understood that the 64B/66B code block stream #4 is obtained by multiplexing, and its frame structure may be different from the structure of the FlexE frame. Correspondingly, the acquiring the at least one 64B/66B code block stream may include: receiving at least two second client services; performing 64B/66B encoding on the at least two second client services to obtain at least two 64B/66B Data code block; performing rate adaptation on the at least two 64B/66B data code blocks; inserting overhead code blocks in at least two 64B/66B data code blocks after rate adaptation to form at least two 64B/66B a code block substream; 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 of the embodiment of the present application can be applied to transmit a FlexE service code block stream, and the FlexO can simply carry the FlexE, so that the FlexE and the FlexO can efficiently cooperate to form a compact transmission system. In addition, the data transmission method of the embodiment of the present application can also be applied to transmit other types of client services (for example, non-FlexE services), and encode other client services into a 64B/66B code block stream similar to the FlexE code block stream, through the FlexE channel layer. Mapped to the FlexO transport layer for transfer, the process is very efficient and simple.

FIG. 3 is a schematic diagram of mapping various services to FlexO according to an embodiment of the present application. Specifically, the embodiment of the present application maps each service to the FlexO transport layer through the FlexE channel layer. For example, as shown in FIG. 3, three 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 acquired, which can carry The various services described above have rates that are positive integer multiples of 5G. Each 64B/66B code block stream may be multiplexed (eg 64B/66B code block stream #A) or unmultiplexed (eg 64B/66B code block stream #B and 64B/66B code) Block stream #C). Among them, 64B/66B code block stream #B and 64B/66B code block stream #C obtained without multiplexing are every certain data code block (#1, #2,...,#e-1,#e) There is an overhead code block, usually e can be 1023*20. After every multiplexed data block (#1, #2, ..., #d-1, #d) in the 64B/66B code block stream #A obtained by multiplexing, there is an overhead code block, and d is not strictly 1023. *20. Three 64B/66B code block streams are mapped to the FlexO transport layer through the FlexE channel layer.

It should be understood that for customer services where the rate is much lower than 5G and there is no other customer service multiplexable 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 optional solution is to generate a low-speed 64B/66B code block substream for the client service, and generate at least one 64B/66B code block substream filled with all IDLE code blocks (ie, the content is empty). The rate sum of at least two 64B/66B code block substreams is 5G. The at least two 64B/66B code block substreams are multiplexed and mapped to corresponding time slots of the FlexO. For example, if the 64B/66B code block sub-flow rate carrying the customer service is 2.5G, a fill code block substream of the same rate can be generated. For another example, if the 64B/66B code block sub-flow rate carrying the customer service is 1.25G, three filled code block substreams of the same rate can be generated.

The process of obtaining a 64B/66B code block stream in data transmission in the embodiment of the present application is described in detail below 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 (for example, a non-FlexE service), performing 64B/66B encoding on the first client service, and obtaining a 64B/66B data code block. Rate adapting the 64B/66B data code block; inserting the overhead code block into the rate-matched 64B/66B data code block 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, in this embodiment, the client service is uniformly adapted to the 64B/66B code block, and the 64B/66B data code block rate is adapted to match the time slot size of the FlexO frame by IDLE addition and deletion, and then the overhead code block is inserted. For example, an overhead code block is inserted every 1023*20 code blocks to monitor their respective services. Thereby, a 64B/66B code block stream of each rate class is formed. Finally, the 64B/66B code block streams of each rate class are mapped into corresponding time slots of the FlexO frame.

4 is a schematic diagram of information included in a FlexE overhead code block. As shown in Figure 4, 32 consecutive FlexE frames form a FlexE multiframe, and a FlexE OH frame consists of 8 consecutive FlexE OH blocks. The first code block in the FlexE frame has a "0x4B" or "0x5" field as a tag field for identifying the code block as an OH code block. FlexE OH frames transmitted on each link include FlexE Group IDentification, Physical Link Mapping (PHY Map) information, Physical Link ID (PHY IDentification), Time Slot Allocation Table (Calendar) A, Fields such as Calendar B, Section Management Channel, and Shim-to-shim Management Channel. There are also reserved areas in the FlexE OH frame. The FlexE Group IDentification is used to indicate the number of the flexible Ethernet group where the link is located; the PHY Map is used to indicate the distribution of the PHYs included in the flexible Ethernet group where the link is located; Calendar A and Calendar B are used to indicate the FlexE, respectively. The current Calendar configuration of the Group and the alternate Calendar configuration. The content of the inserted overhead code block of the embodiment of the present application may further 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 time stamp information, which is used by the receiving end to perform clock recovery on each customer service. Optionally, the timestamp information may be 32 bits. The inserted overhead code block of the embodiment of the present application may further include Automatic Protection Switched (APS) information. Optionally, 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. Optionally, the delay measurement information may be 32 bits. The inserted overhead code block of the embodiment of the present application may further include a Trail Trace Identifier (TTI), which may be defined by 64 bytes of an Optical Transport Network (OTN). Since the indication can be processed slowly, it can be embodied in a multiframe manner, and an overhead frame can occupy 1 byte or 2 bytes.

The foregoing additional information may occupy the Reserved area of the FlexE overhead code block of FIG. 4, and may also occupy a Section Management Channel, which is not limited in this embodiment of the present application.

In a specific example, the access signal is a G-bit (Gigabit) Ethernet (GE) service, and the code block of the GE service is an 8B/10B code block. A method for converting an 8B/10B code block into a 64B/65B code block is defined in the standard G.7041, as shown in Table 1. The difference between the 64B/66B encoding and the 64B/65B encoding in this embodiment is that the 8 8Bs (8 bits) that are solved do not add 1 bit (bit) to form the 65B code block when adding the block synchronization header, but add 2bit synchronization. The head forms 66B. The sync header "01" indicates that the next 64 bits are all data. Rate matching is then performed by adding an IDLE code block. An overhead code block is added every 1023*20 64B/66B data code blocks.

Table 1 64B/65B transcoding table

In the case that the rate of the GE service is low, the embodiment can form a 64B/66B code block substream by using 64B/66B coding, and 64B/ corresponding to the four GE services by code block interleaving (ie, multiplexing). The 66B code block substream forms a 5G 64B/66B code block stream. The specific process of multiplexing has been described in detail in the previous section and will not be described here.

The above description is developed from the perspective of the transmitting end. For the receiving end, the receiving end parses out 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 parsed 64B/66B code block stream, and then performs IDLE addition and deletion. Get the original customer business.

Example 2:

In this embodiment, acquiring at least one 64B/66B code block stream may include: receiving a FlexE service code block stream, parsing the FlexE service code block stream into at least one FlexE client service code block stream, and the FlexE client service code block stream. The code block is a 64B/66B code block; an overhead code block is inserted in the FlexE client service code block stream to form at least one 64B/66B code block stream.

It should be understood that this embodiment may be considered to map a 64B/66B code block stream to a corresponding time slot of a FlexO frame by a Termination mapping method.

FIG. 5 is a schematic diagram of an application scenario of a termination mapping method. FIG. 6 is a schematic diagram of a FlexO carrying a FlexE service code block stream in a Termination mapping manner in an embodiment of the present application. In this embodiment, the transmitting end of the optical transport network (OTN) receives the FlexE service code block stream. For example, 100G FlexE frames #1, ..., 100G FlexE frames #j, ..., 100G FlexE frames #m are received through the m*100G FlexE Group shown in FIG. The sender senses and terminates the Ethernet slice (FlexE Shim), parses and restores the flexible Ethernet client Flex Ethernet Client (FlexE Client) service code block stream. For example, FlexE Client service code block stream #1, FlexE Client service code block stream #2, ..., FlexE Client service code block stream #i, ..., FlexE Client service code block stream #j, ..., FlexE Client Service code block stream #n-1, FlexE Client service code block stream #n. The sender performs rate adaptation on each FlexE Client service code block stream by adding and deleting IDLE code blocks, and then inserts an overhead code block every 1023*20 code blocks to form an extended FlexE code block stream (64B/66B code block stream). . It should be understood that the inserted overhead code block may be consistent with the overhead code block described in Embodiment 1, and details are not described herein again. Each FlexE Client service code block stream can be flexibly distributed to the time slots of the q*100G FlexO group, and each FlexE Client service code block stream is mapped to one or more FlexO frames according to an IDLE Mapping Procedure (IMP) or a GMP method. in. For example, the code stream is mapped into the corresponding time slot of FlexO frame #1, ..., FlexO frame #j, ..., FlexO frame #q. Among them, the FlexO frame may include p time slots (for example, time slot #1, ..., time slot #j, ..., time slot #p), and there is FlexO overhead in the FlexO frame. It should be noted that FIG. 12 and the related descriptions show an example of a specific method for performing time slot division on a FlexO frame, which is not described herein. At least one FlexO frame forms at least one FlexO code block stream, and the FlexO code block stream may be a 100G code block stream.

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

Example 3:

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

It should be understood that this embodiment may be considered to map a 64B/66B code block stream to a corresponding time slot of a FlexO frame by an Unaware mapping method.

FIG. 7 is a schematic diagram of an application scenario of the Unaware mapping mode. FIG. 8 is a schematic diagram of a FlexO carrying a FlexE service code block stream in an Unaware mapping manner according to another embodiment of the present application. In this embodiment, the transmitting end receives the FlexE service code block stream. For example, 100G FlexE frames #1, ..., 100G FlexE frames #j, ..., 100G FlexE frames #m are received through the m*100G FlexE Group shown in FIG. Each of the FlexE 100G FlexE frames (ie, the FlexE service code block stream) is processed independently. The FlexO does not sense whether it carries the FlexE service. The FlexE service code block stream is mapped to the corresponding time slot of the FlexO frame according to the 16-byte granularity GMP. Wherein, each of the FlexO frames may include p time slots (eg, time slot #1, . . . , time slot #j, . . . , time slot #p), and there is FlexO overhead in the FlexO frame. In this embodiment, the total FlexE rate is less than or equal to the total FlexO rate. For example, the FlexE service code block stream and the FlexO code block stream are both 100G, and there is only one time slot in the FlexO frame. If the 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 time slots.

Example 4:

In this embodiment, acquiring at least one 64B/66B code block stream may include: receiving a FlexE service code block stream, deleting an unused time slot in the FlexE service code block stream, and deleting the unused FlexE service code block. The stream acts as at least one 64B/66B code block stream.

It should be understood that this embodiment may be considered to map a 64B/66B code block stream to a corresponding time slot of a FlexO frame by an Aware mapping method.

FIG. 9 is a schematic diagram of an application scenario of the Aware mapping mode. FIG. 10 is a schematic diagram of a FlexO carrying a FlexE service code block stream in an Aware mapping manner according to another embodiment of the present application. In this embodiment, the transmitting end receives the FlexE service code block stream, for example, receives 100G FlexE frame #1, . . . , 100G FlexE frame #j, . . . , 100G FlexE frame #m through the m*100G FlexE Group shown in FIG. FlexO senses the FlexE service, identifies the time slot usage of the FlexE Shim, deletes the unused time slots to form an extended FlexE code block stream, and extends the FlexE code block streams to have respective sub-rates, for example. The FlexE service code block stream is mapped to the corresponding time slot of the FlexO frame in accordance with 16-byte granularity of GMP. Among them, the FlexO frame may include p time slots (for example, time slot #1, ..., time slot #j, ..., time slot #p), and there is FlexO overhead in the FlexO frame. FlexO can carry FlexE services through one or more pipes. In the case of multiple bearers, each path needs to have the same transmission path. It should be noted that FIG. 12 and the related description give an example of a method for dividing a time slot of a FlexO frame, which is not described herein.

The above description is developed from the perspective of the transmitting end. For the receiving end, the receiving end parses out the extended FlexE code block stream according to the information in the FlexO overhead. The receiving end recovers the deleted unused time slots according to the overhead code blocks in the extended FlexE code block stream, thereby restoring the FlexE Shim.

The FlexO frame of each embodiment of the present application is described in detail below. 11 is a schematic diagram of a FlexO frame of one embodiment of the present application. As shown in FIG. 11, a FlexO frame may include a header of 10 byte block size (overhead area) and a payload area of 5130 byte block size. See Figure 12 for the specific division of the byte block. 12 is a schematic diagram of a FlexO multiframe of an embodiment of the present application. As shown in Figure 12, a FlexO frame can include 128 lines of 5440 bits per line. Each line includes a 300 bit 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 frame header may include an alignment mark (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 having a slot size of 5G is to be obtained, each FlexO multiframe needs to be divided into 20 time slots. An even number of FlexO frames may constitute a FlexO multiframe. For example, FIG. 12 shows a case where two FlexO frames constitute one FlexO multiframe. A 5G time slot may include 513 byte blocks, and the first time slot shown in FIG. 12 (for example, called time slot 1, denoted as ts1) may be obtained by byte blocks ts1.1, ts1.2, ..., Ts1.i,...,ts1.217,...,ts1.j,...,ts1.513. The remaining 19 time slots are also similar and will not be described here. It should be noted that, as shown in FIG. 12, the 217th byte block of slot 1 to slot 10 is in the first FlexO frame of the FlexO multiframe, and the 217th byte block of slot 11 to slot 20. The second FlexO frame in the FlexO multiframe.

It should be understood that the structures of the FlexO frame and the FlexO multiframe shown in FIG. 11 and FIG. 12 are merely exemplary and are not intended to limit the embodiments of the present application. In actual implementation, the size of the FEC area may vary according to different technologies of FEC coding. Or the payload area can have padding blocks. However, these do not affect the FlexO frame divided by 16 bytes, and its effective payload area will remain a positive integer multiple of 16 bytes. In other words, a FlexO frame in the above example includes a payload area of 5130 byte block sizes. This is only an example, and the embodiment of the present application can flexibly transform it 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 be understood that the embodiment of the present application may divide the time slot by 5G granules, and may also divide the time slot by other bandwidths, which is not limited in this embodiment of the present application.

FIG. 13 is a schematic structural diagram of FlexO overhead according to an embodiment of the present application. A full overhead (hereinafter referred to as FlexO overhead) is formed by 8 multiframes as shown in FIG. Since the embodiment of the present application divides the time slot in the FlexO frame, the FlexO overhead may include time slot (Calendar Slot) allocation information, and the time slot allocation information is used to indicate that the at least one 64B/66B code block stream is mapped to the FlexO. The location of the time slot of the frame. That is, slot allocation information may be included in the FlexO overhead to indicate which slot position the respective 64B/66B code block streams are mapped to. Specifically, the slot 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. This embodiment of the present application does not limit this.

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

In addition, FlexO overhead can also include CR/CA/C fields to support slot adjustment and refresh functions. The definition of FlexO overhead can be as shown in Figure 13. The definition of overhead can be defined by the corresponding overhead of FlexE. Field C is a field for indicating the calendar configuration in use. The field CR is a Calendar Switch Request field. The field CA is a Calendar Switch Acknowledge field.

The FlexO overhead may also include clock information, which is used to carry information about a clock channel, such as a 1588 message.

In addition, the FlexO overhead may also include a Multi-frame Alignment Signal (MFAS), a Group ID (GID), a Physical Link Identification (PID), and a Physical Link Mapping (PHY Map). MAP), Status (STAT) information, OTUC Availability (AVAIL) information, Cyclic Redundancy Check (CRC) bits, and FlexO management Communications Channel (FCC), etc., this application The embodiment is not limited to this.

It should be understood that the structure of the FlexO overhead shown in FIG. 13 is only exemplary, and the FlexO overhead may have other structures, which is not limited by the embodiment of the present application.

Optionally, the data transmission method in the embodiments of the present application may cross the obtained at least one 64B/66B code block stream to complete service grooming of the extended FlexE code block stream, and then at least one 64B/66B code block after the intersection. The stream is mapped to a corresponding time slot of at least one FlexO frame. The crossover can be based on existing TDM crossover mechanisms and/or cell crossover mechanisms.

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

FIG. 14 is a schematic block diagram of a transmission device 200 of one embodiment of the present application. The transmission device 200 is a device at the transmitting end. A transmission device 200 as shown in FIG. 14 may include: an obtaining module 210, configured to acquire at least one 64B/66B code block stream, each of the 64B/66B code block streams having a rate of 5G positive integer multiple; a mapping module 220. The at least one 64B/66B code block stream acquired by the obtaining module 210 is mapped to a corresponding time slot of the at least one flexible optical transport network FlexO frame, and the overhead module 230 is configured to add a FlexO to the at least one FlexO frame. The overhead forms a FlexO code block stream; the sending module 240 is configured to transmit the FlexO code block stream.

The transmission device of the embodiment of the present application directly maps the 64B/66B code block stream to the corresponding time slot of at least one FlexO frame, and then forms a FlexO code block stream for transmission, which can form a simple transmission system, thereby providing a flexible bearer solution.

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

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

Optionally, as an embodiment, the acquiring module 210 is specifically configured to: receive a first client service; perform 64B/66B encoding on the first client service, and obtain a 64B/66B data code block; and the 64B/ The 66B data code block is rate adapted; the overhead code block is inserted into the rate adapted 64B/66B data code block to form the at least one 64B/66B code block stream.

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

Optionally, as an embodiment, the acquiring module 210 is specifically configured to: receive at least two second client services; perform 64B/66B encoding on the at least two second client services, and obtain at least two 64B/66B Data code block; performing rate adaptation on the at least two 64B/66B data code blocks; inserting overhead code blocks in at least two 64B/66B data code blocks after rate adaptation to form at least two 64B/66B a code block substream; 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 acquiring module 210 is specifically configured to: receive a FlexE service code block stream, and parse the FlexE service code block stream into at least one FlexE client service code block stream, where the FlexE client code code is The code block in the block stream is a 64B/66B code block; an overhead code block is inserted in the FlexE client service code block stream to form the at least one 64B/66B code block stream.

Optionally, as an embodiment, the acquiring module 210 is specifically configured to: receive a FlexE service code block stream, and use the FlexE service code block stream as the at least one 64B/66B code block stream.

Optionally, as an embodiment, the acquiring module 210 is specifically configured to: receive a FlexE service code block stream, delete an unused time slot in the FlexE service code block stream, and delete the FlexE service code after the unused time slot is deleted. The block stream acts as the at least one 64B/66B code block stream.

Figure 15 is a schematic block diagram of a transmission device 300 in accordance with one embodiment of the present application. The transmission device 300 is a device at the transmitting end. A transmission device 300 as shown in FIG. 15 may include a processor 310 and a memory 320 in which computer instructions are stored, and when the processor 320 executes the computer instructions, the transmission device 300 performs the following steps. :

Obtaining at least one 64B/66B code block stream, and the rate of each of the 64B/66B code block streams is a 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 to the at least one FlexO frame to form a FlexO code block stream;

Transmitting the FlexO code block stream.

When the processor 320 executes the computer instruction, the transmission device 300 can specifically perform the related embodiments of the foregoing data transmission method, and details are not described herein again.

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 can be used to perform the operations or processes of the above method embodiments, and the operations of the respective modules and devices in the transmission device 200 or the transmission device 300 and/or The functions are respectively implemented in order to implement the corresponding processes in the foregoing method embodiments, and are not described herein for brevity.

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

The transmission device of the embodiment of the present application receives the FlexO code block stream, parses out 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 compact transmission system, thereby providing a flexible bearer solution. .

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

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

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

FIG. 17 is a schematic block diagram of a transmission device 500 according to an embodiment of the present application. The transmission device 500 is a device at the receiving end. A transmission device 500 as shown in FIG. 17 may include a processor 510 and a memory 520 in which computer instructions are stored, and when the processor 520 executes the computer instructions, the transmission device 500 performs the following steps. :

Receiving a FlexO code block stream;

Parsing at least one 64B/66B code block stream from each of the FlexO frame time slots of the FlexO code block stream, each of the 64B/66B code blocks, according to a FlexO overhead of a FlexO frame in the FlexO code block stream The rate of the stream is a positive integer multiple of 5G.

When the processor 520 executes the computer instruction, the transmission device 500 can be specifically configured to perform the related embodiments of the foregoing data transmission method, and details are not described herein again.

Optionally, the transmission device 500 may further include 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 can be used to perform the operations or processes of the above method embodiments, and the operations of the respective modules and devices in the transmission device 400 or the transmission device 500 and/or The functions are respectively implemented in order to implement the corresponding processes in the foregoing method embodiments, and are not described herein for brevity.

FIG. 18 is a schematic block diagram of a transmission device 600 according to an embodiment of the present application. The transmission device 600 is a device at the transmitting end. The transmission device 600 has a crossover or scheduling capability, and its structure is a branch line separation structure. As shown in FIG. 16, the transmission device 600 may include three chips of a tributary board 610, a cross board 620, and a circuit board 630. The tributary board is configured to receive a service, perform at least one of code block type conversion (transcoding), data stream slicing, shim processing, 64B/66B encoding, rate adaptation, multiplexing, and demultiplexing, and the tributary board performs The processing is not limited to this. For example, the tributary board shown in FIG. 18 performs the code block type conversion and rate adaptation (completed by the transcoding adaptation module 611) for the Eth service, and then inserts the overhead code block to form an extended FlexE code block stream (by the class FlexE). Module 612 is completed) and then sent to class multiplexing module 613 (if the receiving device can be a demultiplexing module for demultiplexing, not shown) for multiplexing, although multiplexing may not be required. As another example, for TDM services, data stream slicing and rate adaptation are completed (by slice adaptation module 614), and overhead is inserted to form an extended FlexE code block stream (completed by class FlexE module 615), which is then sent to the class multiplexing module. 613 is multiplexed (and may not need to be multiplexed). For another example, for the FlexE service, after performing standard shim processing (completed by the Shim module 616), it can be directly sent to the next module (for example, the class multiplexing module 613, or directly to the cross board 620), or After the standard shim is terminated, the FlexE Client insertion overhead is formed to form an extended FlexE code block stream (completed by the class FlexE module 617) and sent to the next module. The cross-board is used to groom and adapt the service. The circuit board is used for at least one of multiplexing, demultiplexing, mapping, FlexO framing, and transmission through the PHY interface, and processing by the board 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 solution) The multiplexing module is used for demultiplexing, not shown in the figure).

It should be understood that the device of the corresponding receiving end is similar in structure to the transmitting device 600, except that the data is transmitted in the opposite direction, and details are not described herein again.

FIG. 19 is a schematic block diagram of a transmission device 700 according to an embodiment of the present application. Transmission device 700 is a transmitting device. The transmission device 700 is used for fixed line transmission, which is a transponder or a muxponder, without a cross module or a cross board, including a chip. As shown in FIG. 19, the transmission device 700 may include a transcoding adaptation module 701 and a FlexE-like module 702 for processing Eth services; a slice adaptation module 703 and a FlexE-like module 704 for processing TDM services; and a Shim module 705 and a FlexE-like module 706 for processing FlexE services; a class multiplexing module 707 for multiplexing (if the receiving device can be a demultiplexing-like module for demultiplexing, not shown in the figure); a mapping module 708, A mapping module 709, a FlexO framing module 710, a FlexO framing module 711, a PHY interface 712, and a PHY interface 713 are used to map the extended FlexE code block stream to FlexO and framing, and finally.

It should be understood that the device of the corresponding receiving end is similar in structure to the transmitting device 700, except that the data is transmitted in the opposite direction, and details are not described herein again.

It should be noted that the two device examples shown in FIG. 18 and FIG. 19 can perform the steps in the foregoing method embodiments, and details are not described herein again.

It should be understood that the processor mentioned in the embodiment of the present application may be a central processing unit (CPU), and may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits ( Application Specific Integrated Circuit (ASIC), Field Programmable Gate Array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general purpose processor may be a microprocessor or the processor or any conventional processor or the like.

It should also be understood that the memory referred to in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read only memory (PROM), an erasable programmable read only memory (Erasable PROM, EPROM), or an electric Erase programmable read only memory (EEPROM) or flash memory. The volatile memory can be a Random Access Memory (RAM) that acts as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (Synchronous DRAM). SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), Synchronous Connection Dynamic Random Access Memory (Synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (DR RAM).

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

It should be noted that the memories described herein are 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 an instruction is stored, and when the instruction is run on a computer, the computer is caused to execute the data transmission method of the foregoing method embodiment.

The embodiment of the present application further provides a computer program product comprising instructions, wherein when the computer runs the finger of the computer program product, the computer executes the data transmission method of the method embodiment.

The embodiment of the present application further provides a transmission system, including: a transmission device at the transmitting end of the embodiment of the present application and a transmission device at the receiving end of the application embodiment.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in 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 instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present application are generated in whole or in part. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.). The computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a high-density digital video disc (DVD)), or a semiconductor medium (for example, a solid state hard disk (Solid State Disk, SSD)) and so on.

The first, second, and various numerical numbers referred to herein are for convenience of description and are not intended to limit the scope of the application.

It should be understood that the term "and/or" herein is merely an association relationship describing an associated object, indicating that there may be three relationships, for example, A and/or B, which may indicate that A exists separately, and A and B exist simultaneously. There are three cases of B alone. In addition, the character "/" in this article generally indicates that the contextual object is an "or" relationship.

It should be understood that, in the various embodiments of the present application, the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application. The implementation process constitutes any limitation.

Those of ordinary skill in the art will appreciate that the elements and algorithm steps of the various examples described in connection with the embodiments disclosed herein can be implemented in electronic hardware or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the solution. A person skilled in the art can use different methods to implement the described functions for each particular application, but such implementation should not be considered to be beyond the scope of the present application.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

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

The foregoing is only a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto, and any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed in the present application. It should be covered by the scope of protection of this application. Therefore, the scope of protection of the present application should be determined by the scope of the claims.

Claims (27)

A data transmission method, comprising: Obtaining at least one 64B/66B code block stream, and the rate of each of the 64B/66B code block streams is a 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 to the at least one FlexO frame to form a FlexO code block stream; Transmitting the FlexO code block stream. The data transmission method according to claim 1, wherein the FlexO overhead comprises time slot allocation information, and the time slot allocation information is used to indicate that the at least one 64B/66B code block stream is mapped to the at least one The location of the time slot of a FlexO frame. The data transmission method according to claim 1 or 2, characterized in that the size of the time slot of the FlexO frame is 5G. The data transmission method according to any one of claims 1 to 3, wherein the acquiring at least one 64B/66B code block stream comprises: Receiving the first customer service; Performing 64B/66B encoding on the first client service to obtain a 64B/66B data code block; Rate adapting the 64B/66B data code block; An overhead code block is inserted in the rate-adapted 64B/66B data code block to form the at least one 64B/66B code block stream. The data transmission method according to claim 4, wherein the first client service comprises at least one of a packet service and a fixed bit rate CBR service. The data transmission method according to any one of claims 1 to 5, wherein the acquiring at least one 64B/66B code block stream comprises: Receiving at least two second customer services; Performing 64B/66B encoding on the at least two second client services to obtain at least two 64B/66B data code blocks; Rate adapting the at least two 64B/66B data code blocks; Inserting an overhead code block into at least two 64B/66B data code blocks after rate adaptation to form at least two 64B/66B code block substreams; The at least two 64B/66B code block substreams are multiplexed to obtain the at least one 64B/66B code block stream. The data transmission method according to any one of claims 1 to 6, wherein the acquiring at least one 64B/66B code block stream comprises: Receiving a FlexE service code block stream, parsing the FlexE service code block stream into at least one FlexE client service code block stream, where the code block in the FlexE client service code block stream is a 64B/66B code block; An overhead code block is inserted in the FlexE client service code block stream to form the at least one 64B/66B code block stream. The data transmission method according to any one of claims 1 to 7, wherein the acquiring at least one 64B/66B code block stream comprises: Receiving a FlexE service code block stream, and using the FlexE service code block stream as the at least one 64B/66B code block stream. The data transmission method according to any one of claims 1 to 8, wherein the acquiring at least one 64B/66B code block stream comprises: Receiving the FlexE service code block stream, deleting the unused time slots in the FlexE service code block stream, and deleting the unused FlexE service code block stream as the at least one 64B/66B code block stream. A transmission device, comprising: a processor and a memory, wherein the memory stores computer instructions, and when the processor executes the computer instructions, the transmission device performs the following steps: Obtaining at least one 64B/66B code block stream, and the rate of each of the 64B/66B code block streams is a 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 to the at least one FlexO frame to form a FlexO code block stream; Transmitting the FlexO code block stream. The transmission device according to claim 10, wherein the FlexO overhead comprises time slot allocation information, the time slot allocation information is used to indicate that the at least one 64B/66B code block stream is mapped to the at least one The location of the slot of the FlexO frame. The transmission device according to claim 10 or 11, wherein the size of the time slot of the FlexO frame is 5G. The transmission device according to any one of claims 10 to 12, wherein when the processor executes the computer instruction, the transmission device is specifically executed: Receiving the first customer service; Performing 64B/66B encoding on the first client service to obtain a 64B/66B data code block; Rate adapting the 64B/66B data code block; An overhead code block is inserted in the rate-adapted 64B/66B data code block to form the at least one 64B/66B code block stream. The transmission device according to claim 13, wherein the first client service comprises at least one of a packet service and a fixed bit rate CBR service. The transmission device according to any one of claims 10 to 14, wherein when the processor executes the computer instruction, the transmission device is specifically executed: Receiving at least two second customer services; Performing 64B/66B encoding on the at least two second client services to obtain at least two 64B/66B data code blocks; Rate adapting the at least two 64B/66B data code blocks; Inserting an overhead code block into at least two 64B/66B data code blocks after rate adaptation to form at least two 64B/66B code block substreams; The at least two 64B/66B code block substreams are multiplexed to obtain the at least one 64B/66B code block stream. The transmission device according to any one of claims 10 to 15, wherein when the processor executes the computer instruction, the transmission device is specifically executed: Receiving a FlexE service code block stream, parsing the FlexE service code block stream into at least one FlexE client service code block stream, where the code block in the FlexE client service code block stream is a 64B/66B code block; An overhead code block is inserted in the FlexE client service code block stream to form the at least one 64B/66B code block stream. The transmission device according to any one of claims 10 to 16, wherein when the processor executes the computer instruction, the transmission device is specifically executed: Receiving a FlexE service code block stream, and using the FlexE service code block stream as the at least one 64B/66B code block stream. The transmission device according to any one of claims 10 to 17, wherein when the processor executes the computer instruction, the transmission device is specifically executed: Receiving the FlexE service code block stream, deleting the unused time slots in the FlexE service code block stream, and deleting the unused FlexE service code block stream as the at least one 64B/66B code block stream. A data transmission method, comprising: Receiving a FlexO code block stream; Parsing at least one 64B/66B code block stream from each of the FlexO frame time slots of the FlexO code block stream, each of the 64B/66B code blocks, according to a FlexO overhead of a FlexO frame in the FlexO code block stream The rate of the stream is a positive integer multiple of 5G. The data transmission method according to claim 19, wherein said FlexO overhead comprises time slot allocation information, said time slot allocation information is used to indicate that said at least one 64B/66B code block stream is mapped to said FlexO The location of the time slot of the frame. The data transmission method according to claim 19 or 20, wherein the size of the time slot of the FlexO frame is 5G. The data transmission method according to any one of claims 19 to 21, wherein the data transmission method further comprises: The original service data is recovered according to the at least one 64B/66B code block stream. A transmission device, comprising: a processor and a memory, wherein the memory stores computer instructions, and when the processor executes the computer instructions, the transmission device performs the following steps: Receiving a FlexO code block stream; Parsing at least one 64B/66B code block stream from each of the FlexO frame time slots of the FlexO code block stream, each of the 64B/66B code blocks, according to a FlexO overhead of a FlexO frame in the FlexO code block stream The rate of the stream is a positive integer multiple of 5G. The transmission device according to claim 23, wherein said FlexO overhead comprises time slot allocation information, said time slot allocation information is used to indicate that said at least one 64B/66B code block stream is mapped to said FlexO frame The location of the time slot. The transmission device according to claim 23 or 24, characterized in that the size of the time slot of the FlexO frame is 5G. The transmission device according to any one of claims 23 to 25, wherein when the computer instruction is executed, the transmission device is further caused to perform the following steps: The original service data is recovered according to the at least one 64B/66B code block stream. A transmission system, comprising: the transmission device according to any one of claims 10 to 18, and the transmission device according to any one of claims 23 to 26.

Images