CN116264587A

CN116264587A - Data transmission method and related device

Info

Publication number: CN116264587A
Application number: CN202111519430.0A
Authority: CN
Inventors: 陈昀
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-12-13
Filing date: 2021-12-13
Publication date: 2023-06-16
Also published as: WO2023109424A1

Abstract

The application discloses a data transmission method and a related device, wherein first service data of a first small particle service are borne through small particle unit base frame overhead, and the first service data are transmitted without occupying extra sub-slots, so that the bearing and the transmission of the service data of the small particle service can be completed, the waste of bandwidth is avoided as much as possible, and the bandwidth resource is effectively saved. In the method, first service data of a first small particle service are acquired, and first small particle unit base frame overhead is sent to a second communication device and carries the first service data.

Description

Data transmission method and related device

Technical Field

The embodiment of the application relates to the technical field of communication, in particular to a data transmission method and a related device.

Background

Flexible ethernet (FlexE) technology is an interface technology that implements traffic isolation and network fragmentation, and has been rapidly developed in recent years and widely accepted by various standards organizations. The FlexE technology realizes decoupling of a medium access control (medium access control, MAC) layer and a physical link interface (PHY) layer by introducing a flexible ethernet protocol layer (english may also be referred to as FlexE Shim layer) on the basis of IEEE802.3, thereby realizing flexible rate matching. Flex Shim schedules and distributes data of a plurality of FlexE clients (clients) to a plurality of different sub-channels in a time slot mode based on a time division multiplexing (time division multiplexing, TDM) distribution mechanism, so that hard isolation of transmission pipeline bandwidths is realized, one service data stream can be distributed to one or a plurality of time slots (slots), and matching of various rate services is realized.

The existing FlexE interface technology solves the problem that the rate of an Ethernet port is fixed to a certain extent, and the Client cross technology solves the problem that the packet forwarding delay is too large. However, when the existing FlexE interface technology is based on sub-slot (sub-slot) to carry service data of small-particle service (for example, the rate is less than or equal to 10 Mbps), there is serious channel bandwidth waste.

Disclosure of Invention

The embodiment of the application provides a data transmission method and a related device, which solve the problem that bandwidth waste is serious when service bearing is carried based on sub-slots in the current FlexE technology.

In a first aspect, an embodiment of the present application provides a method for data transmission, where the method is applied to a first communication device. The first communication device may be an intermediate node or an edge node, which is not limited herein. In the method, first service data of a first small particle service are acquired, and first small particle unit base frame overhead is sent to a second communication device, wherein the first small particle unit base frame overhead carries the first service data. In the embodiment of the application, the first service data of the first small particle service is borne through the small particle unit base frame overhead, and the first service data is transmitted without occupying extra sub-slots, so that the bearing and the transmission of the service data of the small particle service can be completed, the bandwidth waste is avoided as much as possible, and the bandwidth resource is effectively saved.

In some possible embodiments, the first communication device may further send a small particle unit base frame payload to the second communication device, the small particle unit base frame payload for carrying second traffic data of a second small particle traffic, the first small particle traffic being different from the second small particle traffic.

In other possible embodiments, the first small particle unit base frame overhead includes a first general communication channel GCC field, where the first GCC field is used to carry the first traffic data.

In other possible implementations, the first GCC field includes at least one byte. Thus, at least one byte of the first GCC field is designated for carrying said first traffic data.

In other possible embodiments, before sending the first small particle unit base frame overhead, the method further comprises: and mapping the first service data to the at least one byte according to a first mapping relation, wherein the first mapping relation indicates the mapping relation between the at least one byte and a first client, and the first client corresponds to the first granular service. By the method, the first service data is mapped in the bytes, so that the data mapping mode is increased, and the first service data which needs to occupy different bandwidths can be carried through one or more bytes.

In other possible embodiments, sending the first small particle unit base frame overhead to the second communication device includes: and transmitting a small particle unit multiframe to the second communication device, wherein the small particle unit multiframe comprises a first small particle unit base frame and a second small particle unit base frame which are adjacent. Wherein the first small particle unit base frame includes the first small particle unit base frame overhead and the second small particle unit base frame includes a second small particle unit base frame overhead. The first GCC field of the first small grain unit base frame overhead and the second GCC field of the second small grain unit base frame overhead constitute a first GCC code block, the first GCC code block being designated for carrying the first small grain traffic.

In other possible embodiments, the first communication device may further map the first service data to the first GCC code block according to the second mapping relationship before sending the small particle unit multiframe. The second mapping relationship indicates a mapping relationship between the first GCC code block and a first client, where the first client corresponds to the first small-particle service.

In other possible embodiments, the first mapping relationship includes a mapping relationship between a first client ID and a byte identifier, where the first client ID is used to identify the first client and the byte identifier is used to identify the at least one byte.

In other possible embodiments, the second mapping relationship includes a mapping relationship between a first client ID and a code block identifier, where the first client ID is used to identify the first client, the code block identifier is used to identify the at least one code block, and the at least one code block includes the first GCC code block.

In other possible embodiments, the method further comprises: and acquiring first configuration information, wherein the first configuration information comprises the first mapping relation or the second mapping relation.

In other possible embodiments, before sending the small particle unit base frame payload to the second communication device, the first communication device may further map the second service data to at least one sub-slot of the small particle unit base frame payload according to the third mapping relationship. The third mapping relationship indicates a mapping relationship between a second client and at least one sub-slot, where the second client corresponds to a second small-granule service.

In a second aspect, embodiments of the present application provide another method for data transmission, where the method is applied to a second communication device. In the method, a first small particle unit base frame overhead sent by a first communication device is received, wherein the first small particle unit base frame overhead is used for bearing first service data of a first small particle service; and processing the first small particle unit base frame overhead.

In some possible embodiments, the second communication device may further receive a small particle unit base frame payload sent by the first communication device, where the small particle unit base frame payload carries second service data of a second small particle service, and the first small particle service is different from the second small particle service.

In other possible embodiments, the first small particle unit base frame overhead includes a first general communication channel GCC field, the first GCC field carrying the first traffic data.

In other possible implementations, at least one byte of the first GCC field is designated for carrying the first small particle traffic.

In other possible embodiments, the receiving the first small particle unit base frame overhead sent by the first communication device includes: and receiving a small particle unit multiframe sent by the first communication device, wherein the small particle unit multiframe comprises a first small particle unit base frame and a second small particle unit base frame which are adjacent. Wherein the first small particle unit base frame includes the first small particle unit base frame overhead and the second small particle unit base frame includes a second small particle unit base frame overhead. The first GCC field of the first small grain unit base frame overhead and the second GCC field of the second small grain unit base frame overhead constitute a first GCC code block, the first GCC code block being designated for carrying the first small grain traffic.

In other possible embodiments, the processing the first small particle unit base frame overhead includes: and exchanging the first business data from a first client to a second client, wherein the first client corresponds to the first small-particle business, and the second client corresponds to the first small-particle business.

In other possible embodiments, exchanging the first business data from a first client to a second client includes: extracting the first service data from the first GCC field based on a first mapping relationship indicating a mapping relationship between the first client and the first GCC field; and mapping the first service data to a third GCC field based on a second mapping relationship, wherein the second mapping relationship indicates the mapping relationship between the second client and the third GCC field.

In other possible embodiments, the first mapping relationship includes a mapping relationship between at least one byte of the first GCC field and the first client.

In other possible embodiments, the first mapping relationship includes a mapping relationship between a first GCC code block and the first client, the first GCC code block is composed of the first GCC field and a second GCC field, the second GCC field is included in a second small granule unit base frame overhead, the first small granule unit base frame overhead is included in a first small granule unit base frame, the second small granule unit base frame overhead is included in a second small granule unit base frame, and the first small granule unit base frame and the second small granule unit base frame are adjacent base frames in a small granule unit multiframe.

In other possible implementations, the second mapping relationship includes a mapping relationship between at least one byte of the third GCC field and the second client.

In other possible embodiments, the second mapping relationship includes a mapping relationship between a second GCC code block and the second client. The second GCC code block is composed of a third GCC field and a fourth GCC field, where the third GCC field is included in a third small-granule unit base frame overhead sent by the second communication device to the third communication device, the fourth GCC field is included in a fourth small-granule unit base frame overhead sent by the second communication device to the third communication device, and the third small-granule unit base frame and the fourth small-granule unit base frame are adjacent base frames in a small-granule unit multiframe.

In other possible embodiments, the processing the first small particle unit base frame overhead includes: and transmitting the first small particle unit base frame overhead.

In other possible embodiments, the processing the first small particle unit base frame overhead includes: extracting the first service data from the small particle unit base frame overhead; and carrying out two-layer or three-layer processing on the first service data.

In a third aspect, embodiments of the present application provide a first communication device. The first communication apparatus includes an acquisition unit and a transmission unit. The acquisition unit is used for acquiring first service data of the first small-particle service. The sending unit is configured to send a first small particle unit base frame overhead to the second communication device, where the first small particle unit base frame overhead carries the first service data.

In some possible implementations, the sending unit is further configured to send a small particle unit base frame payload to the second communication device, where the small particle unit base frame payload is used to carry service data of a second small particle service, and the first small particle service is different from the second small particle service.

In other possible implementations, at least one byte in the first GCC field is designated for carrying the first small particle traffic.

In other possible embodiments, the first communication device further comprises a first processing unit. The first processing unit is configured to map the first service data to the at least one byte according to a first mapping relationship before sending the first small particle unit base frame overhead. It should be noted that, the first mapping relationship indicates a mapping relationship between the at least one byte and a first client, where the first client corresponds to the first granular service.

In other possible embodiments, the sending unit is configured to send a small particle unit multiframe to the second communication device, where the small particle unit multiframe includes a first small particle unit base frame and a second small particle unit base frame that are adjacent. Wherein the first small particle unit base frame includes the first small particle unit base frame overhead and the second small particle unit base frame includes a second small particle unit base frame overhead. The first GCC field of the first small grain unit base frame overhead and the second GCC field of the second small grain unit base frame overhead constitute a first GCC code block, the first GCC code block being designated for carrying the first small grain traffic.

In other possible embodiments, the first communication device further comprises a second processing unit. The second processing unit is configured to map the first service data to the at least one code block according to a second mapping relationship before sending the small-granule unit multiframe, where the second mapping relationship indicates a mapping relationship between the at least one code block and a first client, and the first client corresponds to the first small-granule service.

In other possible embodiments, the second mapping relationship includes a mapping relationship between the first client ID and the code block identifier. Wherein the first client ID is used to identify the first client, the code block identification is used to identify the at least one code block, and the at least one code block includes the first GCC code block.

In other possible embodiments, the obtaining unit is further configured to obtain first configuration information, where the first configuration information includes the first mapping relationship or the second mapping relationship.

In other possible embodiments, the first communication device further comprises a third processing unit. The third processing unit is configured to map, before sending the small-granule unit base frame payload to the second communication device, the second service data to at least one sub-slot of the small-granule unit base frame payload according to a third mapping relationship. The third mapping relationship indicates a mapping relationship between a second client and the at least one sub-slot, where the second client corresponds to the second small-granule service.

In a fourth aspect, embodiments of the present application provide a second communication device. The second communication device includes an acquisition unit and a processing unit. The acquiring unit is configured to receive a first small-granule unit base frame overhead sent by the first communication device, where the first small-granule unit base frame overhead is used to carry first service data of a first small-granule service. And the second processing unit is used for processing the first small particle unit base frame overhead.

In other possible embodiments, the acquisition unit is further configured to: and receiving a small particle unit base frame payload sent by the first communication device, wherein the small particle unit base frame payload carries second service data of a second small particle service, and the first small particle service is different from the second small particle service.

In other possible embodiments, the obtaining unit is configured to: receiving a small particle unit multiframe sent by the first communication device, wherein the small particle unit multiframe comprises a first small particle unit base frame and a second small particle unit base frame which are adjacent, the first small particle unit base frame comprises the first small particle unit base frame overhead, the second small particle unit base frame comprises the second small particle unit base frame overhead, a first GCC code block is formed by a first GCC field of the first small particle unit base frame overhead and a second GCC field of the second small particle unit base frame overhead, and the first GCC code block is designated to bear the first small particle service.

In other possible embodiments, the processing unit is configured to: and exchanging the first business data from a first client to a second client, wherein the first client corresponds to the first small-particle business, and the second client corresponds to the first small-particle business.

In other possible embodiments, the processing unit is configured to: extracting the first service data from the first GCC field based on a first mapping relationship indicating a mapping relationship between the first client and the first GCC field; and mapping the first service data to a third GCC field based on a second mapping relationship, wherein the second mapping relationship indicates the mapping relationship between the second client and the third GCC field.

In other possible embodiments, the processing unit is configured to transparently pass the first small particle unit base frame overhead.

In other possible embodiments, the processing unit is configured to: extracting the first service data from the first small particle unit base frame overhead; and carrying out two-layer or three-layer processing on the first service data.

In other possible embodiments, the second communication device further includes a transmitting module; the sending module is used for forwarding the first service data.

In a fifth aspect, embodiments of the present application provide a data frame structure. The data frame structure includes a small particle unit base frame overhead and a small particle unit base frame payload. The small particle unit base frame overhead comprises a first field, wherein the first field is used for bearing first service data of a first small particle service, the small particle unit base frame payload is used for bearing second service data of a second small particle service, and the first small particle service is different from the second small particle service.

In some possible implementations, the small particle unit base frame overhead further includes a second field for carrying a version number of the data frame structure.

In other possible embodiments, the overhead field further includes a third field, where the third field is used to carry a service type of the first small particle service.

In other possible embodiments, the overhead field further includes a fourth field for carrying clock frequency information.

In other possible embodiments, the small particle unit base frame overhead further includes a fifth field, where the fifth field is used to carry a reserved field.

In other possible embodiments, the small particle unit base frame overhead further includes a sixth field, where the sixth field is used to carry overhead verification information.

In other possible embodiments, the small particle unit base frame overhead further includes a seventh field, where the seventh field is used to carry a sequence number.

In a sixth aspect, embodiments of the present application provide a communication system. The communication system includes a first communication device and a second communication device. The first communication device is configured to perform the method described in the first aspect and any optional embodiments. The second communication device is adapted to perform the method as described in the second aspect and any of the alternative embodiments described above. In addition, the first communication device may be understood with reference to any one of the first communication devices described in the third aspect, and the second communication device may be understood with reference to any one of the second communication devices described in the fourth aspect, which are not described herein.

In a seventh aspect, embodiments of the present application provide a computer readable storage medium, including a program or instructions, which when run on a computer, cause the computer to perform a method as in any one of the first aspect, or any one of the possible implementations of the second aspect, the second aspect.

In an eighth aspect, embodiments of the present application provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform a method as in any one of the first aspect, or any one of the possible implementations of the second aspect, the second aspect.

A ninth aspect of the present application provides a chip system, which may comprise a processor for supporting a first communication device to implement the functions as described in the first aspect, or any one of the possible implementation manners of the first aspect; alternatively, the second communication device is enabled to carry out the functions referred to in the method described in the second aspect or any one of the possible embodiments of the second aspect.

Optionally, in combination with the ninth aspect, in a first possible implementation manner, the chip system may further include a memory, where the memory is configured to hold program instructions and data necessary for the first communication device or the second communication device. The chip system can be composed of chips, and can also comprise chips and other discrete devices. The chip system may include, among other things, an application specific integrated circuit (application specific integrated circuit, ASIC), an off-the-shelf programmable gate array (field programmable gate array, FPGA), or other programmable logic device, etc. Further, the chip system may further include an interface circuit or the like.

From the above technical solutions, the embodiments of the present application have the following advantages:

in the embodiment of the application, the first service data of the first small particle service is borne through the small particle unit base frame overhead, and the first service data is transmitted without occupying extra sub-slots, so that the bearing and the transmission of the service data of the small particle service can be completed, the bandwidth waste is avoided as much as possible, and the bandwidth resource is effectively saved.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the description of the embodiments will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present application.

Figure 1 shows a FlexE generic architecture schematic based on a flexible ethernet protocol;

FIG. 2 shows a schematic diagram of a small particle unit base frame structure;

FIG. 3 shows a schematic diagram of a small particle cell multiframe structure;

FIG. 4A illustrates an overhead format diagram of a small granular unit base frame overhead;

FIG. 4B illustrates a schematic diagram of another overhead format of a small particle unit base frame overhead;

FIG. 4C illustrates a schematic diagram of another overhead format of a small particle unit base frame overhead;

FIG. 5 is a schematic diagram of data being carried in the GCC field in an embodiment of the present application;

FIG. 6 is a schematic diagram illustrating GCC overhead during a small particle cell multiframe period in an embodiment of the present application;

FIG. 7 illustrates a schematic diagram of a hybrid networking scenario;

FIG. 8 shows a schematic diagram of a system architecture;

fig. 9 is a schematic flow chart of a method for data transmission according to an embodiment of the present application;

FIG. 10 illustrates a mapping diagram provided in an embodiment of the present application;

fig. 11A shows a schematic configuration diagram of a GCC code block provided in an embodiment of the present application;

FIG. 11B illustrates another mapping scheme provided in an embodiment of the present application;

FIG. 12 is a schematic diagram showing the exchange of first service data in clients provided in an embodiment of the present application;

fig. 13 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 14 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 15 shows a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of another communication device according to an embodiment of the present application;

fig. 17A shows a schematic structural diagram of a first communication device according to an embodiment of the present application;

Fig. 17B illustrates a schematic structural diagram of another first communication device provided in an embodiment of the present application;

fig. 17C illustrates a schematic structural diagram of another first communication device provided in an embodiment of the present application;

fig. 17D shows a structural diagram of another first communication device provided in an embodiment of the present application;

fig. 18 shows a schematic structural diagram of another second communication device according to an embodiment of the present application.

Detailed Description

The following description of the technical solutions in the embodiments of the present application will be made clearly and completely with reference to the drawings in the embodiments of the present application, and it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims of this application and in the above-described figures, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the present application described herein may be capable of being practiced otherwise than as specifically illustrated and described herein. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. In this application, "at least one" means one or more, and "a plurality" means two or more. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a alone, a and B together, and B alone, wherein a, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b or c may represent: a, b, c, a and b, a and c, b and c or a and b and c, wherein a, b and c can be single or multiple. It is noted that "at least one" may also be interpreted as "one (a) or more (a)".

The optical internet forum (optical internet forum, OIF) promulgates FlexE standards, and the related art related FLEXEs referred to in this application can be found in the FlexE standards IA OIF-FlexE-01.0, IA OIF-FlexE-02.0 or IA OIF-FlexE02.1 established by OIF, the relevant specifications of which are incorporated by reference in their entirety. In addition, in the present application, the ethernet interface and the ethernet interface are often used interchangeably, and the flexible ethernet interface are often used interchangeably.

Figure 1 shows a FlexE generic architecture schematic based on a flexible ethernet protocol. As shown in fig. 1, the flexible ethernet protocol suite (flex ethernet Group, flexE Group) includes 4 PHYs. FlexE clients may represent Client data streams transmitted over a slot or slots of a FlexE Group. One FlexE Group may carry multiple FlexE clients thereon, one FlexE Client may correspond to one to multiple clients' traffic data streams (also referred to as MAC clients), and the FlexE Shim layer provides FlexE Client to MAC Client data adaptation and conversion. The FlexE can support mapping and transmission of any number of different FlexE clients on any set of PHYs, thereby implementing functions such as PHY bundling, channelization, and subrate. Multiple PHYs may be combined into one FlexE Group for carrying one or more FlexE client data streams distributed and mapped through the FlexE shimm layer. Taking 100GE PHY as an example, the FlexE shimm layer may divide each 100GE PHY in the FlexE Group into data-carrying channels of 20 slots (slots), where each slot corresponds to a bandwidth of 5Gbps.

The ITU-T series standard has been developed at the slice packet network (slicing packet network, SPN) channel layer or metropolitan area transport network (metro transportnetwork, MTN) channel layer technology, and ITU-T standards g.8310 and g.8312 specify that the bandwidth granularity of the SPN channel layer is 5Gbps. In the small particle units (fine granularity unit, FGU), further time slot division and multiplexing are performed on the bandwidth granularity of 5Gbps of the SPN channel layer, so that a small particle channel with the bandwidth granularity of 10Mbps is formed. The SPN channel layer is located in the physical coding sublayer (physical coding sublayer, PCS) of the standard IEEE802.3, and the coding mode adopts a coding format of transcoding 64bits in the PCS layer into 66bits (hereinafter referred to as 64B/66B). In this application, FGUs may also be referred to as small particle based frames, small particle unit based frames, basic unit frames, or single frames, small particles may also be referred to as fine particles, and will be described later using only small particle unit based frames as examples. The small particle unit base frame adopts a 64B/66B coding format corresponding to the SPN channel layer, encodes the small particle unit base frame Overhead (OH) and the small particle unit base frame payload containing a plurality of time slots, and encapsulates the encoded small particle unit base frame overhead and the small particle unit base frame payload into a code block sequence with a fixed length. Fig. 2 shows a schematic diagram of a small particle unit base frame structure. As shown in fig. 2, for the ethernet frame format defined by the compatible IEEE802.3, the small particle unit base frame is encapsulated with 1S code block, 195D code blocks, and 1T code block. Wherein the S code block is used to indicate the frame header of the small particle unit base frame. The data field of the D code Block (Block payload field as shown in fig. 2) is used to carry the small particle unit base frame payload. The T code block can be used to indicate the end of the small particle unit base frame. One code block contains 8 bytes, and 195D code blocks and 1T code block of the small granule unit base frame together carry 1567 bytes of data content, including 7 bytes of small granule unit base frame overhead and 1560 bytes of small granule unit base frame payload. The small particle unit base frame payload is divided into 24 sub-slots (sub-slots) of the same size, which are denoted by sub-slots 1 to sub-slot 24, respectively. Each sub-slot is 65 bytes and can carry 8 65bits of code blocks. The traffic data is compressed and transcoded 66B to 65B and then filled into sub-slot payloads.

In addition, the time slot division is performed on the bandwidth granularity 5Gbps of the SPN channel layer in a multiframe mode, and can be specifically understood by referring to the schematic diagram of the multiframe structure of the small particle unit shown in fig. 3. As shown in fig. 3, on the FlexE Client interface or the general ETH interface with the bandwidth granularity of 5Gbps, it may be divided into 480 sub-slots in the time domain for cyclic transmission. That is, in each time slot scheduling period (480 sub-time slots are one time slot scheduling period) of one FlexE client interface, 20 small granule unit base frames (for example, small granule unit base frame 1 to small granule unit base frame 20) are evenly distributed, that is, one small granule unit multiframe. Each small granule unit base frame contains 24 sub-slots. In a specific embodiment, each sub-slot payload may include 8 compressed code blocks of 66B, and for a small granule unit base frame, an S code block, a code block corresponding to the small granule unit base frame overhead (regarded as OH in the figure) and a T code block are added to encapsulate, and a small granule unit base frame may include 197 66B code blocks. For rate adaptation, an I code block may be added between small-granule unit base frames, or a part of the I code block may be replaced with an OAM code block transmitted in the FlxeE client interface. I code blocks, i.e., idle code blocks, are used for MAC layer rate adaptation. In a specific embodiment, the multiframe length should be less than or equal to 9600 bytes, as specified by the transport ethernet message. It should be appreciated that the above-described FlexE client interface with bandwidth granularity of 5Gbps is illustrated in fig. 3 with only 480 sub-slots and 20 small granule unit base frames as one small granule unit multiframe. In practical application, for FlexE client interfaces with different bandwidths, the number of sub-slots divided in the time domain can also be different, and in particular, the flexible configuration can be realized.

Fig. 4A shows a schematic diagram of an overhead format of a small granularity unit base frame overhead. As can be seen from fig. 4A, each small granule unit base frame contains a small granule unit base frame overhead of 7 bytes, i.e., a small granule unit base frame overhead of 56 bits. The small granule unit base frame overhead includes a 6bits multi-frame indication (multiframe indicator, MFI), a 2bits Flag, a 2bits RES, and a 44bits overhead information (OH information). The overhead information may include at least the following: s bits, C bits, change Request (CR) bits, change Answer (CA) bits, general communication channel (general communication channel, GCC) fields, client identification (client identifier, client ID), sub-slot identification (sub-slot ID), cyclic redundancy check (cyclic redundancy check, CRC) fields, and the like. The S bit is used for carrying the slot increase adjustment notification information, the C bit is used for carrying the slot validation indication information, the CR bit is used for carrying the slot adjustment response information, and the CRC field is used for carrying the cyclic redundancy check information. When the Flag area has different values, the corresponding bit positions can be provided for different channels.

Illustratively, in some possible examples, when the Flag has a value of 11, a corresponding bit position after the CA bit may be inserted into the GCC field, indicating that the bit position occupied by the GCC field is provided for use by the GCC channel, and may be understood with reference to the schematic diagram of another overhead format of the small particle unit base frame overhead shown in fig. 4B. In other possible embodiments, when the Flag has a value of 00, the corresponding bit position after the CA bit is provided for the client ID and the sub-slot ID to use, and may be specifically understood with reference to the schematic diagram of another overhead format of the small particle unit base frame overhead shown in fig. 4C.

The GCC field in the small grain unit base frame overhead in the above-mentioned one small grain unit base frame is a 33B length field for indicating transmission of data through the corresponding GCC channel. The information transmitted over the GCC channel is in ethernet packet format and follows the 64B/66B coding format in IEEE 802.3. Fig. 5 shows a schematic diagram of carrying data in the GCC field in an embodiment of the present application. As shown in fig. 5, the data after 64B/66B encoding is carried in the GCC field in sequence with the first 33bits (0-32 bits, including the synchronization header) and the second 33bits of the data, and is transmitted in the GCC channel according to the sequence carried in sequence. That is, it is understood that in one small granule unit multiframe, the small granule unit base frame indicated with an even number of multiframes (i.e., mfi=n, n is even) is transmitted 33bits before and 33bits after the small granule unit base frame indicated with an odd number of multiframes (i.e., mfi=n+1). Fig. 6 shows a schematic diagram of GCC overhead in one multiframe period in an embodiment of the present application. As shown in fig. 6, 10 code blocks of 64B/66B may be transmitted over an MTN interface with a bandwidth granularity of 5Gbps in one multiframe period. The effective bandwidth of the GCC channel in one multiframe period is 64 bits x 10/50.688 us=12.6 Mbps. Similarly, on a 10Gbps bandwidth MTN interface, 20 code blocks of 64B/66B can be transmitted in a multiframe period, and the effective bandwidth of the corresponding GCC channel is 12.6x2=25.2 Mbps.

It should be appreciated that the GCC channels mentioned above are mainly used for the transmission of management information, control plane protocols, link auto discovery and 1588v2 time protocol messages, etc. In addition, when the information is transmitted through the GCC channel, the information is mainly transmitted in the format of Ethernet frames or Ethernet packets, and network elements of the networking send and receive the control information hop by hop and need protocol layers to participate in processing.

When the FlexE technology is adopted for service transmission, the situation that communication equipment of a plurality of operators are in mixed networking docking is not avoided. Fig. 7 shows a schematic diagram of a hybrid networking scenario. As shown in fig. 7, when the device of the operator a traverses the network composed of the devices of the operator B, the network of the operator B is to be interconnected with the network of the operator a, and the controller of the operator a needs to traverse the network of the operator B to manage and control the device of the remote operator a. However, in this hybrid networking, service data of small-particle service in the carrier B, as well as management information and control information, needs to be transferred in the network of the carrier a with a bandwidth granularity of sub-slot (the bandwidth granularity may be about 10Mbps, for example). When using hybrid networking for service bearer, various small particle services with 10Mbps bandwidth are encountered, for example: there may also be smaller bandwidth (e.g., less than 10Mbps, even only tens of Kbps bandwidth) traffic, such as service phones, individual overhead (regenerator section overhead, RSOH) of segments such as F1, E1, D1-D3, J0, etc., multiplex segment overhead (multiplex section overhead, MSOH) of K1, K2, D4-12, E2, S1, etc., in the SDH frame, if a sub-slot is used to transmit traffic data of some small-particle traffic of less than 10Mbps, or if management information and control information of a third party device are transmitted across the network, it is difficult to avoid wasting bandwidth resources of the sub-slot, and it is not possible to match the traffic requirements precisely.

In order to solve the technical problems, the embodiment redefines a new data frame structure based on the existing FlexE interface or the common ethernet physical interface. I.e. the data frame structure may also be referred to as a small particle unit base frame for carrying traffic data streams of clients corresponding to different small particle traffic. In this application, each small particle unit base frame includes a small particle unit base frame overhead and a small particle unit base frame payload. In this application, two possible transmission modes are possible, using the GCC field described above to transmit the service data of the small-particle service (i.e., the first service data described later). One way is to map the first traffic data into the small granule unit base frame payload first, and then transmit the entire small granule unit base frame over the specified one or more code blocks in the GCC field of the small granule unit base frame overhead. Another way is to map the first traffic data into one or more bytes of the GCC field of the small granule unit base frame overhead or one or more GCC code blocks made up of GCC fields in multiple adjacent small granule unit base frame overheads. Specifically, the small particle unit base frame overhead includes a first field, where the first field is used to carry first service data of a first small particle service. The small particle unit base frame payload is used to carry traffic data for a second small particle traffic, the first small particle traffic being different from the second small particle traffic. The small particle unit base frame overhead may also include other fields for carrying different content, as an example, may be understood in conjunction with table 1 below.

TABLE 1

The first service data of the first small particle service can be transferred through the small particle unit base frame overhead in the data frame structure, and the first service data is transmitted without occupying extra sub-slots, so that the waste of bandwidth is avoided as much as possible. It should be noted that the first field may be the GCC field described above, which is not limited herein.

Based on this, the embodiment of the application provides a data transmission method, which can be applied to an application scenario of the system architecture shown in fig. 8. As shown in fig. 8, the system architecture may include a network device 1, a network device 2, a user device 1, and a user device 2. The network device 1 may be an intermediate node, in which case the network device 1 is connected to the user device 1 via other network devices. The network device 1 may be an edge node, in which case the network device 1 is directly connected to the user device 1. The network device 2 may be an intermediate node, in which case the network device 2 is connected to the user device 2 via other network devices. The network device 2 may also be an edge node, in which case the network device 2 is directly connected to the user device 2. The network device 1 comprises a FlexE interface 1 and the network device 2 comprises a FlexE interface 2. The FlexE interface 1 is connected to a FlexE interface 2. Each FlexE interface includes a transmitting port and a receiving port, and is different from a conventional ethernet interface in that one FlexE interface may carry multiple clients, and the FlexE interface as a logical interface may be formed by combining multiple physical interfaces. The flow of traffic data in the forward path shown in fig. 8 is shown by solid arrows in fig. 8, and the flow of traffic data in the reverse path is shown by dashed arrows in fig. 8. The transmission channel in the embodiment of the present application takes a forward channel as an example, and the flow direction of service data in the transmission channel is user equipment 1- > network equipment 2- > user equipment 2.

It should be understood that 2 network devices and 2 user devices are shown in fig. 8 by way of example only, and the system architecture may include any other number of network devices and user devices, which is not limited in this embodiment of the present application. The system architecture shown in fig. 8 is merely an example, and the application scenario of the system architecture provided in the present application is not limited to the scenario shown in fig. 8. The technical scheme provided by the application is suitable for all network scenes for carrying out data transmission by applying the FlexE technology.

For ease of understanding, fig. 9 provides a flowchart of a method for data transmission according to an embodiment of the present application. As shown in fig. 9, the method for data transmission may include the steps of:

901. the first communication device obtains first service data of a first small particle service.

In a specific embodiment, the first small particle traffic may be, for example, traffic having a bandwidth that is smaller than the bandwidth of the GCC channel. The bandwidths of the GCC channels described above may be understood with reference to what has been described in fig. 6, and will not be described in detail here. In addition, the first small particle traffic may include, but is not limited to, PDH traffic, SDH traffic, ETH traffic, IP traffic, public service telephones, individual open-segment marketing bytes in SDH frames, and the like.

The first communication device mentioned above may be an edge node or an intermediate node, which is not limited in this embodiment of the present application. When the first communication apparatus is an intermediate node, the overhead cross-correlation operations mentioned in the subsequent steps S01 to S04 may not be performed, but the first service data may be demapped from the data block transmitted from the node of the previous hop and repackaged.

902. The first communication device sends a first small particle unit base frame overhead to the second communication device, the first small particle unit base frame overhead carrying first traffic data.

In this example, after acquiring the first service data of the first small particle service, the first communication apparatus may map the first service data into a first small particle unit base frame overhead, and the first service data is carried by the first small particle unit base frame overhead. In this way, the first communication device sends the first small particle unit base frame overhead to the second communication device over the FlexE interface. In a specific implementation, the first communication device may also send a plurality of first data blocks to the second communication device, where the plurality of first data blocks includes the first small particle unit base frame overhead.

It should be noted that the described first small granule unit base frame overhead may be understood with reference to the content of the small granule unit base frame overhead described in fig. 4A to 6, which is not described herein.

In some possible embodiments, a first small particle unit base frame may be included in one small particle unit multiframe. For example, the first granule unit base frame may be the granule unit base frame 1 shown in fig. 3, or may be the granule unit base frame 2, etc., which is not limited herein. In the first small particle unit base frame, a first small particle unit base frame overhead may be included. And the first small particle unit base frame overhead may include a first GCC field that may be used to carry first traffic data.

In a specific implementation, the GCC field included in the small granule unit base frame overhead in each small granule unit base frame is a 33B length field, which can indicate that data such as management information or control information is transmitted through the GCC channel. Thus, in the case where N small particle unit base frames may be included in one small particle unit multiframe, the small particle unit multiframe may include M66B GCC fields, where m=n/2. Therefore, when the bandwidth of the GCC field is still remained, the GCC field may also be used to carry the first service data of the first small particle service, so that the first service data does not occupy the bandwidth resource of the sub-slot. For example, in the case where the management information and the control information occupy 8 bits, the remaining 25 bits of the GCC field may be used to carry the first service data.

In other alternative examples, the first GCC field includes at least one byte. At least one byte of the first GCC field is designated for carrying a first small particle service.

Alternatively, in one small particle unit multiframe, a second small particle unit base frame may be further included, where the second small particle unit base frame is adjacent to the first small particle unit base frame. For example, while the first small particle unit base frame may be the small particle unit base frame 1 shown in fig. 3 described above, the second small particle unit base frame may be the small particle unit base frame 2 or the like; alternatively, or in addition, when the first small particle unit base frame may be the small particle unit base frame 3 shown in fig. 3 described above, the second small particle unit base frame may be the small particle unit base frame 2 or the small particle unit base frame 4, etc., which is not limited herein. And are not described in a limiting manner herein. Also, the second small particle unit base frame includes a second small particle unit base frame overhead.

Thus, a first GCC code block may be composed of a first GCC field and a second GCC field of a second small particle unit base frame overhead, the first GCC code block being designated for carrying the first small particle traffic.

In other alternative examples, the first small particle business corresponds to a first client, and the first client includes first business data. The first small particle service can be carried in the byte through the corresponding relation between the byte and the first client, so that the first service data can be carried in the byte for transmission. Or, the first small particle service can be carried in the code block through the corresponding relation between the code block and the first client, so that the first service data can be carried in the code block for transmission. How the first traffic data is mapped into bytes or code blocks will be described below from different examples, respectively.

(1) Mapping first traffic data to bytes

In some alternative embodiments, before sending the first small particle unit base frame overhead, the first service data may be further mapped to the at least one byte according to a first mapping relationship, where the first mapping relationship indicates a mapping relationship between the at least one byte and a first client, and the first client corresponds to the first small particle service.

In this example, since the first GCC field includes at least one byte, the control management device may configure the at least one byte of the first GCC field and the first client to correspond to each other, resulting in a mapping relationship 1. Then, the control management apparatus transmits the mapping relation 1 to the first communication device, for example, by way of the configuration information a. Alternatively, the first communication device may actively acquire the configuration information a from the control management apparatus. Alternatively, the first communication device also stores the configuration information a locally, and obtains the configuration information a from the local. The manner of acquiring the mapping relation 1 is not particularly limited in the present application.

Thus, after the first communication apparatus acquires the configuration information a, the mapping relation 1 included therein can be obtained. Moreover, since the first small-granule service corresponds to the first client, the first client may include the first service data, and after obtaining the mapping relation 1, the first communication apparatus may be able to map the first service data into at least one byte of the first GCC field based on the mapping relation 1.

For example, fig. 10 is a schematic diagram of mapping provided in an embodiment of the present application. As can be seen from fig. 10, the first service data can be mapped in one or more bytes of 32 bytes in one basic unit of 8bits (i.e., one byte). For example, if the bandwidth occupied by the first service data is smaller than the bandwidth of one byte, the first service data may be carried in any one byte; alternatively, if the bandwidth occupied by the first service data is greater than the bandwidth occupied by one byte, a plurality of bytes may be bundled together to jointly carry the first small-particle service.

Note that the mentioned mapping relation 1 may indicate a mapping relation between at least one byte of the first GCC field and the first client. In addition, the configuration information a may further indicate a byte position and a byte number of the first GCC field occupied by the first service data.

In other possible embodiments, the first mapping relationship (i.e. the mapping relationship a described above) may specifically include a mapping relationship between the first client ID and the byte ID. The first client ID is used for identifying a first client, and the first client corresponds to the first small particle service. Byte identification is used to identify at least one byte.

In this example, one byte may correspond to one byte identifier, or a plurality of bytes may correspond to the same byte identifier, which is not limited in this application. In addition, since the first client ID may identify a first client corresponding to the first small particle service and the first client includes first service data, the byte identification may also be used to indicate at least one byte of the first GCC field. By configuring the mapping relationship between the first client ID and the byte identifier, the first communication device can learn which bytes of the first GCC field need to be mapped with the first service data.

For example, in a scenario where first traffic data of 4 clients currently needs to be transmitted, different client IDs (e.g., client ID 1 to client ID 4) are used for the 4 clients, respectively, and byte 1 is identified using byte identification A1, bytes 2 to 5 are identified using byte identification B1, bytes 6 to 8 are identified using byte identification C1, byte 9 is identified using byte identification D1, and so on. By configuring that a mapping relationship exists between the client ID 1 and the byte identifier A1, a mapping relationship exists between the client ID 2 and the byte identifier B1, a mapping relationship exists between the client ID 3 and the byte identifier C1, a mapping relationship exists between the client ID 4 and the byte identifier D1, and the like. Thus, the first service data of the client identified by the client ID 1 can be carried by the byte 1, the first service data of the client identified by the client ID 2 can be carried by the bytes 2 to 5, the first service data of the client identified by the client ID 3 can be carried by the bytes 6 to 8, and the first service data of the client identified by the client ID 4 can be carried by the byte 9.

(2) Mapping first traffic data to code blocks

In some alternative embodiments, before sending the first small particle unit base frame overhead, the first service data may be further mapped to the first GCC code block according to a second mapping relationship, where the second mapping relationship indicates a mapping relationship between the first GCC and the first client, and the first client corresponds to the first small particle service.

In this example, the first GCC code block may be understood with reference to the foregoing, and will not be described herein. The control management device may configure the first GCC code block and the first client to a corresponding relationship, to obtain a mapping relationship 2. Then, the control management apparatus transmits the mapping relationship 2 to the first communication device, for example, by way of the configuration information B. Alternatively, the first communication device may actively acquire the configuration information B from the control management apparatus. Alternatively, the first communication device also stores the configuration information B locally, and obtains the configuration information B from the local. The manner of acquiring the configuration information B is not particularly limited in this application.

Note that the configuration information B may be the same as the configuration information a. That is, the above-described mapping relation 1 may be carried in the configuration information a, or the above-described mapping relation 2 may be carried in the configuration information B. In addition, the mentioned mapping relation 2 may indicate a mapping relation between the first GCC code block and the first client. For example, the mapping relationship 2 includes a mapping relationship between at least one GCC code block and the first client, where the at least one GCC code block is used to carry small-particle service corresponding to the first client. For example, the at least one GCC code block may include the first GCC code block and may further include a second GCC code block. The configuration information B may further indicate the code block positions and the number of code blocks of all GCC code blocks occupied by the first small granule service corresponding to the first client. That is, according to the configuration information, the code block positions where the first GCC code block and the second GCC code block are located can be determined. The first configuration information includes a first mapping relationship or a second mapping relationship.

Thus, after the first communication apparatus acquires the configuration information B, the mapping relation 2 included therein can be obtained. Moreover, since the first small-granule service corresponds to the first client, the first client may include the first service data, and after obtaining the mapping relationship 2, the first communication apparatus may be able to map the first service data into the first GCC code block based on the mapping relationship 2. For example, fig. 11A is a schematic diagram illustrating the configuration of a GCC code block according to an embodiment of the present application. As can be seen from fig. 11A, in the MTN interface with the bandwidth granularity of 5Gbps, there are 10 GCC code blocks (e.g., blocks 0 to 9) of 66B in a multiframe period. Wherein, the management information and the control plane information between the 5 GCC code Block bearing devices from Block 0 to Block 4 can be specified; the GCC code Block corresponding to the Block 5 can be specified to bear time synchronization information; four GCC code blocks, block 6 through Block 9, may also be designated to carry the first small granule traffic. It should be understood that fig. 11A is merely a schematic description, and may be flexibly configured to specify which bytes in the first GCC field, or which GCC code blocks formed by GCC fields in the small granule unit base frame overhead, carry the first small granule service, which is not specifically limited in this application.

Illustratively, fig. 11B shows another mapping schematic provided in an embodiment of the present application. As can be seen from fig. 11B, the first service data can be mapped in one or more of the four GCC code blocks of Block 6 to Block 9 directly according to one code Block as a base unit. For example, if the bandwidth occupied by the first service data is smaller than the bandwidth of one GCC code block, the first service data may be carried in any GCC code block; or if the bandwidth occupied by the first service data is greater than the bandwidth of one code block, multiple GCC code blocks may be bundled together to jointly carry the first service data.

It should be understood that the one or more GCC code blocks mapping the first service data in blocks 6 through 9 shown in fig. 11B is only one schematic description, and the present application is not limited thereto.

In other specific embodiments, the second mapping may include a mapping between the first user identification client ID and the code block identification. The first client ID is used for identifying a first client, the first client comprises a code block identifier corresponding to a first small particle service, and the code block identifier is used for identifying at least one code block. The at least one code block includes the first GCC code block described above.

In this example, one code block may correspond to one code block identifier, or a plurality of code blocks may correspond to one code block identifier, which is not limited in this application. In addition, since the first client ID may identify a first client corresponding to the first small particle service, and the first client includes first service data. The code block identification may also be used to indicate at least one code block, and the at least one code block may further include a first GCC code block. Then, by configuring the mapping relationship between the first client ID and the code block identification, the first communication device is enabled to learn in which GCC code blocks the first service data needs to be mapped.

For example, in a scenario where first traffic data of 2 clients currently needs to be transmitted, different client IDs (such as client ID 1 and client ID 2) are used for the 2 clients, respectively, and code block identification A2 is used to identify code block 1, code block identification B2 is used to identify code blocks 2 to 5, and so on. It should be noted that each of code blocks 1 to 5 may be composed of GCC fields in the adjacent small granule unit base frame overhead. By configuring that there is a mapping relationship between the client ID 1 and the code block identifier A2, a mapping relationship between the client ID 2 and the code block identifier B2, and so on. In this way, the first service data of the client identified by the client ID 1 can be carried by the code block 1, and the first service data of the client identified by the client ID 2 can be carried by the code blocks 2 to 5.

It should be noted that the above-described client ID 1 to client ID 4, byte identifiers A1, B1, C1, D1, code block identifiers A2, B2, and the like are only illustrative descriptions, and are not limited in the embodiments of the present application.

In other possible examples, the first communication device transmitting the first small particle unit base frame overhead to the second communication device may also be implemented in the following manner. Namely: the first communication device transmits small particle unit multiframes to the second communication device. That is, after mapping the first service data to the first GCC code block based on the mapping relation 2, the first communication device may directly send the small particle unit multiframe to the second communication device, and further transmit the first service data to the second communication device in a manner of being carried in the first GCC code block.

It should be noted that the above description of the small particle unit multiframe can be understood by referring to the foregoing, and details are not repeated herein.

In other possible embodiments, the first communication device may further map the second service data to at least one sub-slot of the small particle unit base frame payload according to a third mapping relationship. The described third mapping relationship indicates a mapping relationship between a second client and at least one sub-slot, the second client corresponding to a second small particle service. The first communication device may then also send the small particle unit base frame payload to the second communication device. The small particle unit base frame payload is used for bearing second service data of a second small particle service, and the first small particle service is different from the second small particle service.

In this example, the second small particle traffic described refers to traffic having a bandwidth greater than or equal to the bandwidth of one sub-slot.

903. The second communication device receives a first small particle unit base frame overhead transmitted by the first communication device.

The second communication device may be an intermediate node or an edge node, which is not limited in the embodiment of the present application. After the first communication device sends the first small particle unit base frame overhead to the second communication device, the second communication device may receive the first small particle unit base frame overhead sent by the first communication device.

In other possible examples, the second communication device may also receive the small particle unit base frame payload transmitted by the first communication device. The small particle unit base frame payload is used to carry second traffic data for a second small particle traffic, the first small particle traffic being different from the second small particle traffic.

It should be noted that the small particle unit base frame payload may be understood with reference to the small particle unit base frame payload mentioned in the foregoing step 902, which is not described herein.

In other possible examples, the first small particle unit base frame overhead includes a first general communication channel GCC field, the first GCC field carrying the first traffic data.

In other possible examples, at least one byte of the first GCC field is designated for carrying the first small particle traffic. It should be noted that the first GCC field and the first small particle unit base frame overhead described above may be understood with reference to the foregoing description of step 902, which is not repeated herein.

In addition, in other possible embodiments, the second communication device receives the first small particle unit base frame overhead sent by the first communication device, where the first small particle unit base frame overhead is implemented by: the second communication device receives the small particle unit multiframe sent by the first communication device.

It should be noted that the described small particle unit multiframe includes adjacent first and second small particle unit base frames. The first small grain unit base frame includes a first small grain unit base frame overhead, the second small grain unit base frame includes a second small grain unit base frame overhead, a first GCC field of the first small grain unit base frame overhead and a second GCC field of the second small grain unit base frame overhead form a first GCC code block, the first GCC code block being designated for carrying the first small grain traffic. It is also specifically understood that reference is made to the foregoing step 902, and details thereof are not described herein.

904. The second communication device processes the first small particle unit base frame overhead.

When the second communication device is a different node, different processing may also be performed on the obtained first small particle unit base frame overhead. The process of how this first small particle unit base frame overhead is handled when the second communication device acts as a different node will be described in detail below from two possible ways.

(1) The second communication device is an intermediate node

When the second communication device is the intermediate node, after the first small particle unit base frame overhead is obtained, the first small particle unit base frame overhead can be forwarded to the downstream edge node or the intermediate node of the next hop, and the first service data is demapped by the downstream edge node or the intermediate node of the next hop. Or after the first small particle unit base frame overhead is obtained, the first service data can be demapped first and then forwarded to a downstream edge node or an intermediate node. The following will be described from different examples:

in other specific embodiments, the second communication device processes the first small particle unit base frame overhead, and may forward the first small particle unit base frame overhead by: the first business data is exchanged from a first client to a second client, wherein the first client corresponds to the first small particle business and the second client corresponds to the first small particle business.

In this example, exchanging first traffic data from a first client to a second client may be understood as exchanging the first traffic data from a receiving side client to a transmitting side client. For example, fig. 12 is a schematic diagram of exchanging first service data in a client provided in an embodiment of the present application. As shown in fig. 12, the second communication apparatus is configured with a first client on the receiving side and a second client on the transmitting side. The first client on the receiving side may be any one of clients A1, clients A2, …, and clients Am (m is a positive integer equal to or greater than 1), and the second client on the transmitting side may be any one of clients B1, clients B2, …, and clients Bm, for example. client A1 may be configured to exchange with client B1, for example. Similarly, client A2 may be configured to exchange with client B2, for example. For the rest of clients Am, the exchange relationship may be understood by referring to the exchange relationship described above, which is not described herein.

It should be noted that, the first client referred to herein is a client corresponding to when the second communication device receives the first small particle-based frame overhead from the first communication device. The second client is the client corresponding to when the second communication device sends the first small particle based frame overhead to the third communication device.

Illustratively, the second communication device exchanging the first traffic data from the first client in the second client may be implemented by:

s01, extracting first service data from a first GCC field according to a first mapping relation, wherein the first mapping relation indicates a mapping relation between a first client and the first GCC field.

S02, mapping the first service data to a third GCC field based on a second mapping relation, wherein the second mapping relation indicates the mapping relation between the second client and the third GCC field.

In this example, the first traffic data may be mapped from at least one byte of the first GCC field into at least one byte of the third GCC field based on the first mapping relationship and the second mapping relationship. Alternatively, the first service data may be mapped from the first GCC code block to the second GCC code block based on the first mapping relationship and the second mapping relationship. The following description describes various embodiments:

(1) byte-based switching scheme

In some examples, the first mapping may include a mapping between at least one byte of the first GCC field and the first client, and the second mapping may include a mapping between at least one byte of the third GCC field and the second client.

In this example, since the first small particle traffic corresponds to the first client, the second client also corresponds to the first small particle traffic. Also, the first GCC field corresponding to the first client may include at least one byte, and the third GCC field corresponding to the second client may also include at least one byte. Then, after the first service data is extracted from the first GCC field through the first mapping relationship, the first service data may be mapped into at least one byte of the third GCC field based on the second mapping relationship. In this way, the second communication device may further send a third small particle unit base frame overhead to the third communication device that includes the third GCC field.

(2) Exchange mode based on GCC code block

In some examples, the first mapping relationship includes a mapping relationship between a first GCC code block and a first client, the first GCC code block consisting of a first GCC field and a second GCC field. The second mapping relation comprises a mapping relation between a second GCC code block and a second client, wherein the second GCC code block consists of a third GCC field and a fourth GCC field.

In this example, the first GCC code block may be understood with reference to the content of the foregoing step 903, which is not described herein. The second GCC code block is composed of a third GCC field and a fourth GCC field, where the third GCC field is included in a third small-granule unit base frame overhead sent by the second communication device to the third communication device, and the fourth GCC field is included in a fourth small-granule unit base frame overhead sent by the second communication device to the third communication device. And the third and fourth small particle unit base frames are adjacent small particle unit base frames in the small particle unit multiframe.

Since the first small particle traffic corresponds to the first client, the second client also corresponds to the first small particle traffic. Moreover, a first GCC code block corresponds to a first client, and a second GCC code block corresponds to a second client. Then, after the first service data is extracted from the first GCC code block, the first service data may be mapped into the second GCC code block based on the second mapping relationship. In this way, the second communication device may further send a third small particle unit base frame overhead including the third GCC field and a fourth small particle unit overhead including the fourth GCC field to the third communication device, so that the first service data may be forwarded.

The first mapping relationship and the second mapping relationship mentioned in the above (1) and (2) may be configured by the control management device, and then the first mapping relationship and the second mapping relationship may be issued to the second communication device, for example, by means of configuration information. Alternatively, the second communication device may obtain the first mapping relationship and the second mapping relationship in other manners, which is not limited herein.

The above-mentioned process of processing the first small-granule unit base frame overhead by the second communication device is described mainly from the perspective of the cross technology, so that in the scene of hybrid networking, the management problem of the docking management protocol equipment is not needed, the first service data can be effectively and transparently transmitted, and the network resources are saved. In other specific embodiments, the second communication device processes the first small particle unit base frame overhead, and may perform forwarding in addition to forwarding by the above-described cross processing manner, by: the first small particle unit base frame overhead is transmitted transparently, and the first traffic data is specified to be carried in at least one byte or at least one code block in a general communication channel GCC field of the first small particle unit base frame overhead.

In this example, after acquiring the first small particle unit base frame overhead, the second communication device does not need to parse the first service data from the byte of the first GCC field of the first small particle unit base frame overhead or the first GCC code block, but may directly transmit the first small particle unit base frame overhead through a time slot used when transmitting the large particle service, so that the first service data is transmitted to an intermediate node or an edge node of the next hop, and so on.

In other specific embodiments, after acquiring the first small particle unit base frame overhead, the second communication device may perform the following steps in addition to forwarding by the above-mentioned exchange manner and directly and transparently transmitting the first small particle unit base frame overhead: and extracting the first service data from the first small particle unit base frame overhead.

Illustratively, the first traffic data may be demapped from at least one byte of the first GCC field based on the first mapping relationship. Alternatively, the first traffic data may be demapped from the first GCC code block based on the first mapping relationship. The first mapping relationship described may be understood with reference to the first mapping relationship mentioned in the foregoing step S01, which is not described herein.

Alternatively, the first service data may be demapped from at least one byte of the third GCC field based on the second mapping relationship. Alternatively, the first traffic data may be demapped from the second GCC code block based on the second mapping relationship. The second mapping relationship described may be understood with reference to the second mapping relationship mentioned in the foregoing step S02, which is not described herein.

S12, carrying out two-layer or three-layer processing on the first service data.

S12, forwarding the service message obtained after the two-layer or three-layer processing.

In this example, after the first service data is directly demapped from the first small particle unit base frame overhead, the service packet obtained after the processing may be forwarded to the edge node after the two-layer or three-layer encapsulation processing is performed on the first service data.

(2) The second communication device is an edge node

When the second communication device is an edge node, the first service data can be extracted from the first small particle unit base frame overhead after the first small particle unit base frame overhead is acquired; and performing two-layer or three-layer processing on the first service data to reconstruct the message.

In other examples, the edge node may also demap the first service data from at least one byte of the third GCC field based on the second mapping relationship when acquiring the third small particle unit base frame overhead or the fourth small particle unit base frame overhead sent by the intermediate node. Alternatively, the first traffic data may be demapped from the second GCC code block based on the second mapping relationship. The second mapping relationship described may be understood with reference to the second mapping relationship mentioned in the foregoing step S02, which is not described herein.

Furthermore, the terms extracted, acquired, demapped, etc. mentioned in this application may in some examples be interchanged.

In the embodiment of the application, the first service data of the first small particle service is borne through the small particle unit base frame overhead, and the first service data is transmitted without occupying extra sub-slots, so that the bearing and the transmission of the service data of the small particle service can be completed, the bandwidth waste is avoided as much as possible, and the bandwidth resource is effectively saved. And the first service data can be transmitted to the next node in a transparent way by means of overhead crossing technology and the like, so that additional network resources are not required to be increased.

The foregoing describes, mainly from an interaction perspective, a method for data transmission provided in the embodiments of the present application. A communication device 1300 according to an embodiment of the present application is described below with reference to fig. 13. The communications apparatus 1300 can be employed in a network architecture as shown in fig. 8. For example, the communication apparatus 1300 may be, for example, the network device 1 (TX) or the network device 2 (RX) shown in fig. 8 of the present application, and the communication apparatus 1300 may also be the first communication apparatus or the second communication apparatus of the present application. The first communication device and the second communication device of the present application may be an integral network device, or may be a single board in the network device 1, for example, an interface board, a line card, a dummy board, or a centralized cross board, or may be a chip that performs related operations, or the like. The communications apparatus 1300 is configured to perform the method of the embodiments described above with respect to any of fig. 9-12. The communication apparatus 1300 includes a transceiving unit 1301 and a processing unit 1302. The transceiver unit 1301 is configured to perform a transceiver operation, and the processing unit is configured to perform an operation other than the transceiver operation. For example, when the communication apparatus 1300 performs the method shown in fig. 9 as the first communication apparatus, the processing unit 1302 is configured to map the first service data to at least one byte according to the first mapping relationship, or map the first service data to the first GCC code block according to the second mapping relationship; the transceiving unit 1301 may be configured to transmit the first small particle unit base frame overhead.

Another communication device 1400 provided in an embodiment of the present application is described below with reference to fig. 14. The communication device 1400 may be employed in the network architecture shown in fig. 14. For example, the communication apparatus 1400 may be, for example, the network device 1 (TX) or the network device 2 (RX) of the present application, and the communication apparatus 1400 may also be the first communication apparatus or the second communication apparatus of the present application. The first communication device and the second communication device of the present application may be an integral network device, or may be a single board in the network device 1, for example, an interface board, a line card, a dummy board, or a centralized cross board, or may be a chip that performs related operations, or the like. The communication device 1400 is configured to perform the method of the embodiments described above with respect to any of fig. 9-12. The communication device 1400 includes a communication interface 1401 and a processor 1402 coupled to the communication interface. The communication interface 1401 is used to perform a transceiving operation, and the processor 1402 is used to perform an operation other than transceiving. For example, when the communication apparatus 1400 performs the method shown in fig. 9 as a first communication apparatus, the processor 1402 is configured to map the first service data to at least one byte according to a first mapping relationship or to map the first service data to a first GCC code block according to a second mapping relationship; the communication interface 1401 may be used to transmit a first small particle unit base frame overhead.

Another communication device 1500 provided in an embodiment of the present application is described below with reference to fig. 15. The communication apparatus 1500 may be applied in the network architecture shown in fig. 8. For example, the communication apparatus 1500 may be, for example, the network device 1 (TX) or the network device 2 (RX) of the present application, and the communication apparatus 1500 may also be the first communication apparatus or the second communication apparatus of the present application. The first communication device and the second communication device of the present application may be an integral network device, or may be a single board in the network device 1, for example, an interface board, a line card, a dummy board, or a centralized cross board, or may be a chip that performs related operations, or the like. The communication device 1500 is used to perform the method of the embodiment corresponding to any of the foregoing figures 9-12. The communication device 1500 includes a memory 1501 and a processor 1502 coupled to the memory. The memory 1501 has stored therein instructions that are read by the processor 1502 to cause the communication device 1500 to perform the method of the embodiment corresponding to any of the figures 9-12.

Another communication device 1600 provided in an embodiment of the present application is described below with reference to fig. 16. The communication device 1600 may be applied in the network architecture shown in fig. 8. For example, the communication apparatus 1600 may be, for example, the network device 1 (TX) or the network device 2 (RX) of the present application, and the communication apparatus 1600 may also be the first communication apparatus or the second communication apparatus of the present application. The first communication device and the second communication device of the present application may be an integral network device, or may be a single board in the network device 1, for example, an interface board, a line card, a dummy board, or a centralized cross board, or may be a chip that performs related operations, or the like. The communication device 1600 is configured to perform the method of the embodiments described above with respect to any of fig. 9-12. As shown in fig. 16, the communication device 1000 includes a processor 1610, a memory 1620 coupled to the processor, and a communication interface 1630. In a particular embodiment, memory 1620 has stored therein computer readable instructions comprising a plurality of software modules, such as a transmit module 1621, a process module 1622, and a receive module 1623. Processor 1610, after executing the various software modules, may perform the corresponding operations as directed by the various software modules. In this embodiment, the operations performed by one software module actually refer to operations performed by the processor 1610 according to instructions of the software module. For example, when the network device 1 performs the method shown in fig. 9 as the first communication apparatus, the transmitting module 1621 is configured to transmit the first small particle unit base frame overhead, and the processing module 1622 is configured to map the first service data to at least one byte according to the first mapping relationship or to map the first service data to the first GCC code block according to the second mapping relationship. Further, after processor 1610 executes the computer-readable instructions in memory 1620, it may perform all of the operations herein that may be performed by the first communications device as directed by the computer-readable instructions. For example, when the communication device 1600 is used as the first communication device, the communication device 1600 may perform the method performed by the first communication device in the embodiment corresponding to any of the figures 9-12.

The processors referred to in this application may be central processing units (central processing unit, CPU), network processors (network processor, NP) or a combination of CPU and NP. The processor may also be an application-specific integrated circuit (ASIC), a programmable logic device (programmable logic device, PLD), or a combination thereof. The PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), general-purpose array logic (generic array logic, GAL), or any combination thereof. The processor 1010 may refer to one processor or may include multiple processors. The memory mentioned in the present application may include volatile memory (RAM), such as random-access memory (RAM); the memory may also include a nonvolatile memory (non-volatile memory), such as a read-only memory (ROM), a flash memory (flash memory), a hard disk (HDD) or a Solid State Drive (SSD); the memory may also comprise a combination of the above types of memories. The memory may be one memory or may include a plurality of memories.

The foregoing mainly describes a schematic structural diagram of a communication device provided in an embodiment of the present application. It will be appreciated that the first communication device and the second communication device described above, in order to implement the above-described functions, comprise corresponding hardware structures and/or software modules that perform the respective functions. Those skilled in the art will readily appreciate that the functions described in connection with the embodiments disclosed herein can be implemented as hardware or a combination of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. 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.

From the viewpoint of functional units, the present application may divide the functional units of the first communication apparatus and the second communication apparatus according to the above-described method embodiment, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated in one functional unit. The integrated functional units may be implemented in hardware or in software.

For example, in the case of dividing each functional unit in an integrated manner, referring to fig. 17A, a schematic structural diagram of a first communication device is provided for an embodiment of the present application. The first communication device described may include: an acquisition unit 1701 and a transmission unit 1702.

The acquiring unit 1701 is configured to acquire first service data of a first small particle service. It may be specifically understood with reference to the foregoing content of step 901 in fig. 9, which is not described herein.

A sending unit 1702 configured to send a first small granule unit base frame overhead to a second communication device, where the first small granule unit base frame overhead carries first service data. It is specifically understood with reference to the foregoing content of step 902 in fig. 9, which is not described herein.

In some possible embodiments, the sending unit 1702 is further configured to send a small particle unit base frame payload to the second communication device, where the small particle unit base frame payload is used to carry service data of a second small particle service, and the first small particle service is different from the second small particle service. It is specifically understood with reference to the foregoing content of step 902 in fig. 9, which is not described herein.

In other possible embodiments, the first small particle unit base frame overhead includes a first general communication channel GCC field for carrying the first traffic data. It is specifically understood with reference to the foregoing content of step 902 in fig. 9, which is not described herein.

In other possible implementations, at least one byte in the first GCC field is designated for carrying the first small particle traffic. It is specifically understood with reference to the foregoing content of step 902 in fig. 9, which is not described herein.

Fig. 17B shows another schematic configuration of the first communication apparatus on the basis of the first communication apparatus shown in fig. 17A described above. As shown in fig. 17B, the first communication apparatus may include a first processing unit 1703 in addition to the acquisition unit 1701 and the transmission unit 1702.

The first processing unit 1703 is configured to map the first service data to at least one byte according to a first mapping relationship before the sending unit 1702 sends the first small granule unit base frame overhead. It should be noted that the first mapping relationship indicates a mapping relationship between at least one byte and a first client, and the first client corresponds to the first granular service.

In other possible embodiments, the first mapping relationship includes a mapping relationship between a first client ID and a byte identification, wherein the first client ID is used to identify the first client, and the byte identification is used to identify the at least one byte.

In other possible embodiments, the sending unit 1702 is configured to:

And transmitting a small particle unit multiframe to the second communication device, wherein the small particle unit multiframe comprises a first small particle unit base frame and a second small particle unit base frame which are adjacent, the first small particle unit base frame comprises a first small particle unit base frame overhead, the second small particle unit base frame comprises a second small particle unit base frame overhead, a first GCC code block is formed by a first GCC field of the first small particle unit base frame overhead and a second GCC field of the second small particle unit base frame overhead, and the first GCC code block is designated to bear the first small particle service.

Fig. 17C shows another schematic configuration of the first communication apparatus on the basis of the first communication apparatus shown in fig. 17A described above. As shown in fig. 17C, the first communication apparatus may include a second processing unit 1704 in addition to the acquisition unit 1701 and the transmission unit 1702.

Or, the second processing unit 1704 is configured to map the first service data to at least one code block according to the second mapping relationship before the sending unit 1702 sends the multiframe of the small granule unit. The second mapping relationship indicates a mapping relationship between at least one code block and a first client, and the first client corresponds to a first small-particle service. It is specifically understood with reference to the foregoing content of step 902 in fig. 9, which is not described herein.

In other possible embodiments, the second mapping relationship includes a mapping relationship between the first client ID and the code block identification. Wherein the first client ID is used to identify the first client and the code block identification is used to identify at least one code block, the at least one code block comprising a first GCC code block. It is specifically understood with reference to the foregoing content of step 902 in fig. 9, which is not described herein.

In other possible embodiments, the obtaining unit 1701 is further configured to obtain first configuration information, where the first configuration information includes the first mapping relationship or the second mapping relationship. It is specifically understood with reference to the foregoing content of step 902 in fig. 9, which is not described herein.

Fig. 17D shows another schematic configuration of the first communication device on the basis of the first communication device shown in any one of fig. 17A to 17C described above. As shown in fig. 17D, the first communication apparatus may include a third processing unit 1705 in addition to the acquisition unit 1701 and the transmission unit 1702.

A third processing unit 1705, configured to map the second service data to at least one sub-slot of the small granule unit base frame payload according to a third mapping relationship before the sending unit 1702 sends the small granule unit base frame payload to the second communication device. The third mapping relationship indicates a mapping relationship between a second client and at least one sub-slot, where the second client corresponds to a second small-granule service.

The above-described fig. 17A to 17D describe the first communication device mainly from the viewpoint of the functional module. The second communication device will be described below from the point of view of the functional module. For example, in the case of dividing each functional unit in an integrated manner, referring to fig. 18, a schematic structural diagram of a second communication device is provided in an embodiment of the present application. The second communication device described may include: an acquisition unit 1801 and a processing unit 1802.

The acquiring unit 1801 is configured to receive a first small-granule unit base frame overhead sent by the first communication device, where the first small-granule unit base frame overhead is used to carry first service data of a first small-granule service. It is specifically understood that reference is made to the foregoing content of step 903 in fig. 9, and no further description is given here.

A processing unit 1802, configured to process a first small granule unit base frame overhead. It may be specifically understood with reference to the foregoing content of step 904 in fig. 9, which is not described herein.

In other possible embodiments, the acquiring unit 1801 is further configured to receive a small particle unit base frame payload sent by the first communication device, where the small particle unit base frame payload carries second service data of a second small particle service, and the first small particle service is different from the second small particle service.

In other possible embodiments, the first small particle unit base frame overhead includes a first general communication channel GCC field, the first GCC field carrying first traffic data.

In other possible embodiments, the acquiring unit 1801 is configured to receive a small particle unit multiframe sent by the first communications device, where the small particle unit multiframe includes a first small particle unit base frame and a second small particle unit base frame that are adjacent to each other. Wherein the first small grain unit base frame includes a first small grain unit base frame overhead and the second small grain unit base frame includes a second small grain unit base frame overhead. The first GCC field of the first small particle unit base frame overhead and the second GCC field of the second small particle unit base frame overhead constitute a first GCC code block, the first GCC code block being designated for carrying the first small particle traffic.

In other possible implementations, the processing unit 1802 is configured to: the first business data is exchanged from a first client to a second client, wherein the first client corresponds to the first small particle business and the second client corresponds to the first small particle business.

In other possible implementations, the processing unit 1802 is configured to: extracting first service data from a first GCC field based on a first mapping relationship, wherein the first mapping relationship indicates a mapping relationship between a first client and the first GCC field; and mapping the first service data to a third GCC field based on a second mapping relationship, wherein the second mapping relationship indicates the mapping relationship between the second client and the third GCC field.

In other possible implementations, the first mapping relationship includes a mapping relationship between at least one byte of the first GCC field and the first client.

In other possible embodiments, the first mapping relationship includes a mapping relationship between a first GCC code block and a first client, the first GCC code block is composed of a first GCC field and a second GCC field, the second GCC field is included in a second small granule unit base frame overhead, the first small granule unit base frame overhead is included in a first small granule unit base frame, the second small granule unit base frame overhead is included in a second small granule unit base frame, and the first small granule unit base frame and the second small granule unit base frame are adjacent base frames in a small granule unit multiframe.

In other possible embodiments, the second mapping relationship includes a mapping relationship between at least one byte of the third GCC field and the second client.

In other possible embodiments, the second mapping relationship includes a mapping relationship between a second GCC code block and a second client. The second GCC code block is composed of a third GCC field and a fourth GCC field, the third GCC field is included in a third small-granule unit base frame overhead sent by the second communication device to the third communication device, the fourth GCC field is included in a fourth small-granule unit base frame overhead sent by the second communication device to the third communication device, and the third small-granule unit base frame and the fourth small-granule unit base frame are adjacent base frames in a small-granule unit multiframe.

In other possible implementations, the processing unit 1802 is configured to pass through the first small particle unit base frame overhead.

In other possible embodiments, the obtaining unit 1801 is further configured to obtain first configuration information, where the first configuration information includes the first mapping relationship or the second mapping relationship.

In other possible implementations, the processing unit 1802 is configured to: extracting first service data from the first small particle unit base frame overhead; and carrying out two-layer or three-layer processing on the first service data.

The embodiment of the application also provides a communication system, which comprises a first communication device and a second communication device, wherein the first communication device or the second communication device can be any one of the communication devices in fig. 13-16, and is used for executing the method in any one of the embodiments corresponding to the pair of fig. 9-12. Alternatively, the first communication device may be any one of the first communication devices of fig. 17A to 17B, and the second communication device may be any one of the second communication devices of fig. 18, for executing the method in any one of the embodiments corresponding to the pair of fig. 9 to 12. The communication system may further comprise a control management device as described herein.

The present application also provides a computer program product comprising a computer program which, when run on a computer, causes the computer to perform the method performed by the first communication device, the second communication device or the control management apparatus in any of the embodiments corresponding to fig. 9 to 12.

The present application provides a computer readable storage medium comprising computer instructions which, when run on a computer, cause the computer to perform the method performed by the first communication device, the second communication device or the control management apparatus in any of the embodiments corresponding to fig. 9 to 12.

Those of ordinary skill in the art will appreciate that the modules and method operations of the examples described in connection with the embodiments disclosed herein can be implemented as electronic hardware, or as a combination 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 solution. The skilled person may use different methods for each specific application to achieve the described functionality.

It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system, apparatus and module may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

In the above embodiments, it may be implemented in whole or in part by hardware, firmware, or any combination thereof. When software is involved in a particular implementation, it may be embodied 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, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another, for example, by wired (e.g., coaxial cable, optical fiber, digital Subscriber Line (DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid State Disk (SSD)), etc.

The foregoing has described in detail the technical solutions provided herein, and specific examples have been used to illustrate the principles and embodiments of the present application, where the above examples are only used to help understand the methods and core ideas of the present application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.

Claims

1. A method of data transmission performed by a first communication device, comprising:

acquiring first service data of a first small particle service;

and sending a first small particle unit base frame overhead to a second communication device, wherein the first small particle unit base frame overhead carries the first service data.

2. The method according to claim 1, wherein the method further comprises:

and sending a small particle unit base frame payload to the second communication device, wherein the small particle unit base frame payload is used for bearing second service data of a second small particle service, and the first small particle service is different from the second small particle service.

3. The method according to claim 1 or 2, wherein the first small particle unit base frame overhead comprises a first general communication channel, GCC, field for carrying the first traffic data.

4. A method according to claim 3, characterized in that at least one byte of the first GCC field is designated for carrying the first small particle traffic.

5. The method of claim 4, wherein prior to transmitting the first small particle unit base frame overhead, the method further comprises:

and mapping the first service data to the at least one byte according to a first mapping relation, wherein the first mapping relation indicates the mapping relation between the at least one byte and a first client, and the first client corresponds to the first small-particle service.

6. The method of claim 5, wherein the first mapping comprises a mapping between a first client identification, clientID, for identifying the first client, and a byte identification, for identifying the at least one byte.

7. The method of claim 3, wherein transmitting the first small particle unit base frame overhead to the second communication device comprises:

Transmitting a small particle unit multiframe to the second communication device, wherein the small particle unit multiframe comprises a first small particle unit base frame and a second small particle unit base frame which are adjacent, the first small particle unit base frame comprises the first small particle unit base frame overhead, the second small particle unit base frame comprises the second small particle unit base frame overhead, the first GCC field of the first small particle unit base frame overhead and the second GCC field of the second small particle unit base frame overhead form a first GCC code block, and the first GCC code block is designated to bear the first small particle service.

8. The method of claim 7, wherein prior to transmitting the small particle unit multiframe, the method further comprises:

and mapping the first service data to the first GCC code block according to a second mapping relation, wherein the second mapping relation indicates the mapping relation between the first GCC code block and a first client, and the first client corresponds to the first small-particle service.

9. The method of claim 8, wherein the second mapping relationship comprises a mapping relationship between a first client ID and a code block identification, wherein the client ID is used to identify the first client, the code block identification is used to identify at least one code block, and the at least one code block comprises the first GCC code block.

10. The method according to any one of claims 5-6, further comprising:

and acquiring first configuration information, wherein the first configuration information comprises the first mapping relation.

11. The method according to any one of claims 7-9, further comprising:

and acquiring first configuration information, wherein the first configuration information further comprises the second mapping relation.

12. The method according to any of claims 2-11, wherein prior to transmitting a small particle unit base frame payload to the second communication device, the method further comprises:

and mapping the second service data to at least one sub-time slot of the small particle unit base frame payload according to a third mapping relation, wherein the third mapping relation indicates a mapping relation between a second client and the at least one sub-time slot, and the second client corresponds to the second small particle service.

13. A method of data transmission, for use in a second communication device, comprising:

receiving first small particle unit base frame overhead sent by a first communication device, wherein the first small particle unit base frame overhead carries first service data of a first small particle service;

And processing the first small particle unit base frame overhead.

14. The method of claim 13, wherein the method further comprises:

and receiving a small particle unit base frame payload sent by the first communication device, wherein the small particle unit base frame payload carries second service data of a second small particle service, and the first small particle service is different from the second small particle service.

15. The method according to claim 13 or 14, wherein the first small particle unit base frame overhead comprises a first general communication channel, GCC, field carrying the first traffic data.

16. The method of claim 15, wherein at least one byte of the first GCC field is designated for carrying the first small particle traffic.

17. The method of claim 15, wherein said receiving a first small particle unit base frame overhead transmitted by said first communication device comprises:

receiving a small particle unit multiframe sent by the first communication device, wherein the small particle unit multiframe comprises a first small particle unit base frame and a second small particle unit base frame which are adjacent, the first small particle unit base frame comprises the first small particle unit base frame overhead, the second small particle unit base frame comprises the second small particle unit base frame overhead, a first GCC code block is formed by a first GCC field of the first small particle unit base frame overhead and a second GCC field of the second small particle unit base frame overhead, and the first GCC code block is designated to bear the first small particle service.

18. The method according to any of claims 13-17, wherein said processing said first small particle unit base frame overhead comprises:

and exchanging the first business data from a first client to a second client, wherein the first client corresponds to the first small-particle business, and the second client corresponds to the first small-particle business.

19. The method of claim 18, wherein exchanging the first business data from a first client at a second client comprises:

extracting the first service data from the first GCC field based on a first mapping relationship indicating a mapping relationship between the first client and the first GCC field;

and mapping the first service data to a third GCC field based on a second mapping relationship, wherein the second mapping relationship indicates the mapping relationship between the second client and the third GCC field.

20. The method of claim 19, wherein the first mapping relationship comprises a mapping relationship between at least one byte of the first GCC field and the first client.

21. The method of claim 19, wherein the first mapping relationship comprises a mapping relationship between a first GCC code block and the first client, the first GCC code block being comprised of the first GCC field and a second GCC field, the second GCC field being included in a second small grain unit base frame overhead, the first small grain unit base frame overhead being included in a first small grain unit base frame, the second small grain unit base frame overhead being included in a second small grain unit base frame, the first small grain unit base frame and the second small grain unit base frame being adjacent base frames in a small grain unit multiframe.

22. The method of claim 19 or 20, wherein the second mapping relationship comprises a mapping relationship between at least one byte of the third GCC field and the second client.

23. The method of claim 19 or 21, wherein the second mapping relationship comprises a mapping relationship between a second GCC code block and the second client, wherein the second GCC code block is composed of a third GCC field included in a third small grain unit base frame overhead transmitted by the second communication device to a third communication device and a fourth GCC field included in a fourth small grain unit base frame overhead transmitted by the second communication device to a third communication device, wherein the third small grain unit base frame and the fourth small grain unit base frame are adjacent base frames in a small grain unit multiframe.

24. The method according to any of claims 13-17, wherein said processing said first small particle unit base frame overhead comprises:

and transmitting the first small particle unit base frame overhead.

25. The method according to any one of claims 19-23, further comprising:

And acquiring first configuration information, wherein the first configuration information comprises the first mapping relation or the second mapping relation.

26. The method according to any of claims 13-17, wherein said processing said first small particle unit base frame overhead comprises:

extracting the first service data from the first small particle unit base frame overhead;

and carrying out two-layer or three-layer processing on the first service data.

27. A first communication device, comprising:

an acquisition unit, configured to acquire first service data of a first small-particle service;

and the sending unit is used for sending the first small particle unit base frame overhead to the second communication device, and the first small particle unit base frame overhead carries the first service data.

28. The first communications device of claim 27, wherein the transmitting unit is further configured to:

29. The first communication device according to claim 27 or 28, wherein the first small particle unit base frame overhead comprises a first general communication channel, GCC, field for carrying the first traffic data.

30. The first communications apparatus of claim 29, wherein at least one byte in the first GCC field is designated for carrying the first small particle service.

31. The first communication device of claim 30, further comprising a first processing unit;

the first processing unit is configured to map, before sending the first small-granule unit base frame overhead, the first service data to the at least one byte according to a first mapping relationship, where the first mapping relationship indicates a mapping relationship between the at least one byte and a first client, and the first client corresponds to the first granule service.

32. The first communications apparatus of claim 31, wherein the first mapping comprises a mapping between a first client ID and a byte identification, wherein the first client ID is used to identify the first client and the byte identification is used to identify the at least one byte.

33. The first communication apparatus according to claim 29, wherein the transmitting unit is configured to:

34. The first communication device of claim 33, wherein the first communication device further comprises a second processing unit; the second processing unit is used for:

before sending the small-granule unit multiframe, mapping the first service data to the at least one code block according to a second mapping relation, wherein the second mapping relation indicates a mapping relation between the at least one code block and a first client, and the first client corresponds to the first small-granule service.

35. The first communications apparatus of claim 34, wherein the second mapping comprises a mapping between a first clientID and a code block identification, wherein the first clientID is used to identify the first clientand the code block identification is used to identify the at least one code block comprising the first GCC code block.

36. The first communication device according to claim 31 or 32, wherein,

the obtaining unit is further configured to obtain first configuration information, where the first configuration information includes the first mapping relationship.

37. The first communication device according to claim 34 or 35, wherein,

The obtaining unit is further configured to obtain first configuration information, where the first configuration information includes the second mapping relationship.

38. The first communication device according to any of claims 28-37, wherein the first communication device further comprises a third processing unit;

the third processing unit is configured to map, before sending a small-granule unit base frame payload to the second communication device, the second service data to at least one sub-slot of the small-granule unit base frame payload according to a third mapping relationship, where the third mapping relationship indicates a mapping relationship between a second client and the at least one sub-slot, and the second client corresponds to the second small-granule service.

39. A second communication device, comprising:

the device comprises an acquisition unit, a first communication unit and a second communication unit, wherein the acquisition unit is used for receiving first small particle unit base frame overhead sent by the first communication unit, and the first small particle unit base frame overhead is used for bearing first service data of a first small particle service;

and the processing unit is used for processing the first small particle unit base frame overhead.

40. The second communication device of claim 39, wherein,

The acquiring unit is further configured to receive a small particle unit base frame payload sent by the first communication device, where the small particle unit base frame payload carries second service data of a second small particle service, and the first small particle service is different from the second small particle service.

41. The second communications apparatus of claim 39 or 40, wherein the first small particle unit base frame overhead comprises a first common communications channel, GCC, field, the first GCC field carrying the first traffic data.

42. The second communications apparatus of claim 41, wherein at least one byte of the first GCC field is designated to carry the first small particle traffic.

43. The second communication device of claim 41, wherein,

the acquisition unit is configured to receive a small particle unit multiframe sent by the first communication device, where the small particle unit multiframe includes a first small particle unit base frame and a second small particle unit base frame that are adjacent to each other, the first small particle unit base frame includes the first small particle unit base frame overhead, the second small particle unit base frame includes the second small particle unit base frame overhead, and the first GCC field of the first small particle unit base frame overhead and the second GCC field of the second small particle unit base frame overhead form a first GCC code block, where the first GCC code block is specified to carry the first small particle service.

44. The second communication device according to any of claims 39-43, wherein the processing unit is configured to:

45. The second communication device of claim 44, wherein the processing unit is configured to:

46. The second communications apparatus of claim 45, wherein the first mapping relationship comprises a mapping relationship between at least one byte of the first GCC field and the first client.

47. The second communications apparatus of claim 45, wherein the first mapping relationship comprises a mapping relationship between a first GCC code block and the first client, the first GCC code block is comprised of the first GCC field and a second GCC field, the second GCC field is included in a second small grain unit base frame overhead, the first small grain unit base frame overhead is included in a first small grain unit base frame, the second small grain unit base frame overhead is included in a second small grain unit base frame, and the first small grain unit base frame and the second small grain unit base frame are adjacent base frames in a small grain unit multiframe.

48. The second communications apparatus of claim 45 or 46, wherein the second mapping relationship comprises a mapping relationship between at least one byte of the third GCC field and the second client.

49. The second communications device of claim 45 or 47, wherein the second mapping relationship comprises a mapping relationship between a second GCC code block and the second client, wherein the second GCC code block consists of a third GCC field included in a third small grain unit base frame overhead transmitted by the second communications device to a third communications device and a fourth GCC field included in a fourth small grain unit base frame overhead transmitted by the second communications device to a third communications device, the third small grain unit base frame and the fourth small grain unit base frame being adjacent base frames in a small grain unit multiframe.

50. The second communication device according to any of claims 39-43, wherein the processing unit is configured to:

and transmitting the first small particle unit base frame overhead.

51. The second communication device according to any of claims 45-49, wherein the obtaining unit is further configured to obtain first configuration information, the first configuration information including the first mapping relation or the second mapping relation.

52. The second communication device according to any of claims 39-43, wherein the processing unit is configured to:

and carrying out two-layer or three-layer processing on the first service data.

53. A first communication device, comprising:

a memory for storing computer readable instructions;

further comprising a processor coupled to the memory for executing computer readable instructions in the memory to cause the first communication device to perform the method of any of claims 1-12.

54. A second communication device, comprising:

a memory for storing computer readable instructions;

further comprising a processor coupled to the memory for executing computer readable instructions in the memory to cause the second communication device to perform the method of any of claims 13-26.

55. A computer readable storage medium comprising a program or instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 26.

56. A computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of any one of claims 1 to 26.

57. A communication system comprising the first communication device of any one of claims 27 to 38 and the second communication device of any one of claims 39 to 52.