WO2023109424A1 - 一种数据传输的方法以及相关装置 - Google Patents

一种数据传输的方法以及相关装置 Download PDF

Info

Publication number
WO2023109424A1
WO2023109424A1 PCT/CN2022/132712 CN2022132712W WO2023109424A1 WO 2023109424 A1 WO2023109424 A1 WO 2023109424A1 CN 2022132712 W CN2022132712 W CN 2022132712W WO 2023109424 A1 WO2023109424 A1 WO 2023109424A1
Authority
WO
WIPO (PCT)
Prior art keywords
small
unit
gcc
communication device
basic frame
Prior art date
Application number
PCT/CN2022/132712
Other languages
English (en)
French (fr)
Inventor
陈昀
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2023109424A1 publication Critical patent/WO2023109424A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]

Definitions

  • the embodiments of the present application relate to the field of communication technologies, and in particular, to a data transmission method and a related device.
  • Flexible Ethernet (Flex Ethernet, FlexE) technology is an interface technology to realize service isolation and network fragmentation. It has developed rapidly in recent years and has been widely accepted by major standard organizations. FlexE technology introduces the flexible Ethernet protocol layer (English can also be called the FlexE Shim layer) on the basis of IEEE802.3 to realize the medium access control (medium access control, MAC) layer and the physical link interface layer (physical, PHY) decoupling for flexible rate matching.
  • Flex Shim Based on the time division multiplexing (TDM) distribution mechanism, Flex Shim schedules and distributes the data of multiple FlexE clients (clients) to multiple different sub-channels according to time slots, so as to realize the hard isolation of transmission pipeline bandwidth.
  • the data flow can be allocated to one or more time slots (slot), which realizes the matching of various rate services.
  • the existing FlexE interface technology solves the problem of constant Ethernet port rate to a certain extent, and the Client crossover technology solves the problem of too large packet forwarding delay.
  • the existing FlexE interface technology carries service data of small-grained services (for example, the rate is less than or equal to 10 Mbps) based on sub-slots, there is a serious waste of channel bandwidth.
  • the embodiment of the present application provides a data transmission method and a related device, which solve the serious problem of bandwidth waste when carrying out services based on sub-slots in the current FlexE technology.
  • the embodiment of the present application provides a data transmission method, and 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 here.
  • the first service data of the first small-grained service is obtained, and the first small-granular unit basic frame overhead is sent to the second communication device, and the first small-granular unit basic frame overhead carries the first service data .
  • the first service data of the first small-grain service is carried by the basic frame overhead of the small-grain unit, and the service of the small-grain service can be completed without occupying an additional sub-slot to transmit the first service data
  • the bearing and transmission of data avoids the waste of bandwidth as much as possible and effectively saves bandwidth resources.
  • the first communication device may also send the payload of the basic frame of the small particle unit to the second communication device, and the payload of the basic frame of the small particle unit is used to carry the second service data of the second small particle service , the first small-grain service is different from the second small-grain service.
  • the basic frame overhead of the first small particle unit includes a first general communication channel (GCC) field, and the first GCC field is used to carry the first service data.
  • GCC general communication channel
  • the first GCC field includes at least one byte. Therefore, at least one byte of the first GCC field is designated for carrying the first service data.
  • the method before sending the basic frame overhead of the first small granular unit, the method further includes: mapping the first service data to the at least one byte according to a first mapping relationship, so The first mapping relationship indicates a mapping relationship between the at least one byte and a first client client, and the first client corresponds to the first granular service.
  • the first service data is mapped into bytes, which not only increases the way of data mapping, but also enables one or more bytes to bear the first service data that needs to occupy different bandwidths.
  • sending the first small granular unit basic frame overhead to the second communication device includes: sending a small granular unit multiframe to the second communication device, where the small granular unit multiframe includes adjacent The first small-grain unit base frame and the second small-grain unit base frame of .
  • the first basic frame of the small particle unit includes the overhead of the first basic frame of the small particle unit
  • the second basic frame of the small particle unit includes the overhead of the second basic frame of the small particle unit.
  • the first GCC field of the basic frame overhead of the first small granular unit and the second GCC field of the basic frame overhead of the second small granular unit form a first GCC code block, and the first GCC code block is designated for to carry the first small-grain service.
  • the first communication device may further map the first service data to the first GCC code block according to the second mapping relationship.
  • the second mapping relationship indicates the mapping relationship between the first GCC code block and the first client, and the first client corresponds to the first small-grained service.
  • the first mapping relationship includes a mapping relationship between a first client identifier client ID and a byte identifier, where the first client ID is used to identify the first client, so The byte identifier is used to identify the at least one byte.
  • 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, and the code block ID The 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.
  • the method further includes: acquiring first configuration information, where the first configuration information includes the first mapping relationship or the second mapping relationship.
  • the first communication device may also map the second service data to the payload of the basic frame of the small particle unit according to the third mapping relationship at least one subslot of .
  • the described third mapping relationship indicates the mapping relationship between the second client client and at least one sub-slot, and the second client corresponds to the second small-grained service.
  • the embodiment of the present application provides another data transmission method, which is applied to a second communication device.
  • the method receiving the first basic frame overhead of the first small granular unit sent by the first communication device, the first basic frame overhead of the small granular unit is used to bear the first service data of the first small granular service; A small granular unit is processed based on frame overhead.
  • the second communication device may also receive the payload of the basic frame of the small particle unit sent by the first communication device, where the payload of the basic frame of the small particle unit carries the second service data of the second small particle service,
  • the first small-grain service is different from the second small-grain service.
  • the first small particle unit basic frame overhead includes a first general communication channel (GCC) field, and the first GCC field carries the first service data.
  • GCC general communication channel
  • At least one byte of the first GCC field is designated to bear the first small-grained service.
  • the receiving the first small-grain unit basic frame overhead sent by the first communication device includes: receiving the small-grain unit multi-frame sent by the first communication device, and the small-grain unit multi-frame
  • the frames include adjacent first and second small particle unit basic frames.
  • the first basic frame of the small particle unit includes the overhead of the first basic frame of the small particle unit
  • the second basic frame of the small particle unit includes the overhead of the second basic frame of the small particle unit.
  • the first GCC field of the basic frame overhead of the first small granular unit and the second GCC field of the basic frame overhead of the second small granular unit form a first GCC code block, and the first GCC code block is designated for to carry the first small-grain service.
  • the processing the basic frame overhead of the first small granular unit includes: exchanging the first service data from the first client to the second client, wherein the first The client corresponds to the first small-grain service, and the second client corresponds to the first small-grain service.
  • exchanging the first service data from the first client to the second client includes: extracting the first service data from the first GCC field based on the first mapping relationship, so The first mapping relationship indicates the mapping relationship between the first client and the first GCC field; based on the second mapping relationship, the first business data is mapped to the third GCC field, and the second mapping relationship Indicates the mapping relationship between the second client and the third GCC field.
  • the first mapping relationship includes a mapping relationship between at least one byte of the first GCC field and the first client.
  • the first mapping relationship includes a mapping relationship between the first GCC code block and the first client, and the first GCC code block consists of the first GCC field and the second Composed of GCC fields, the second GCC field is included in the basic frame overhead of the second small granular unit, the basic frame overhead of the first small granular unit is included in the basic frame of the first small granular unit, and the second small granular unit The basic frame overhead is included in the second small granular unit basic frame, and the first small granular unit basic frame and the second small granular unit basic frame are adjacent basic frames in the small granular unit multiframe.
  • the second mapping relationship includes a mapping relationship between at least one byte of the third GCC field and the second client.
  • the second mapping relationship includes a mapping relationship between the second GCC code block and the second client.
  • the second GCC code block is composed of the third GCC field and the fourth GCC field
  • the third GCC field contains the third small particle unit basis sent by the second communication device to the third communication device.
  • the fourth GCC field is included in the fourth small granular unit basic frame overhead sent by the second communication device to the third communication device, the third small granular unit basic frame and the fourth small granular unit basic frame
  • the granular unit base frame is the adjacent base frame in the small granular unit multiframe.
  • the processing the basic frame overhead of the first small granular unit includes: transparently transmitting the basic frame overhead of the first small granular unit.
  • the method further includes: acquiring first configuration information, where the first configuration information includes the first mapping relationship or the second mapping relationship.
  • the processing the basic frame overhead of the first small granular unit includes: extracting the first service data from the basic frame overhead of the small granular unit; 1. Business data is processed at Layer 2 or Layer 3.
  • the embodiment of the present application provides a first communication device.
  • the first communication device includes an acquiring unit and a sending unit.
  • the obtaining unit is configured to obtain the first service data of the first small-grain service.
  • the sending unit is configured to send a first basic frame overhead of a small granular unit to the second communication device, where the first basic frame overhead of a small granular unit bears the first service data.
  • the sending unit is further configured to send the payload of the basic frame of the small particle unit to the second communication device, and the payload of the basic frame of the small particle unit is used to carry the service of the second small particle service data, the first small-grain service is different from the second small-grain service.
  • the basic frame overhead of the first small particle unit includes a first general communication channel (GCC) field, and the first GCC field is used to bear the first service data.
  • GCC general communication channel
  • At least one byte in the first GCC field is designated to bear the first small-grained service.
  • the first communication device further includes 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 basic frame overhead of the first small granular unit.
  • the first mapping relationship indicates a mapping relationship between the at least one byte and a first client client, and the first client corresponds to the first granular service.
  • the first mapping relationship includes a mapping relationship between a first client identifier client ID and a byte identifier, where the first client ID is used to identify the first client, so The byte identifier is used to identify the at least one byte.
  • the sending unit is configured to send a small particle unit multiframe to the second communication device, where the small particle unit multiframe includes adjacent first small particle unit basic frames and second small particle unit basic frames frame.
  • the first basic frame of the small particle unit includes the overhead of the first basic frame of the small particle unit
  • the second basic frame of the small particle unit includes the overhead of the second basic frame of the small particle unit.
  • the first GCC field of the basic frame overhead of the first small granular unit and the second GCC field of the basic frame overhead of the second small granular unit form a first GCC code block
  • the first GCC code block is designated for to carry the first small-grain service.
  • the first communication device further includes 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-grain unit multiframe, where the second mapping relationship indicates the A mapping relationship between at least one code block and a first client client, where the first client corresponds to the first small-grained service.
  • the second mapping relationship includes a mapping relationship between the first client ID and the code block identifier.
  • 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
  • the at least one code block includes the first GCC code block.
  • the acquiring unit is further configured to acquire first configuration information, where the first configuration information includes the first mapping relationship or the second mapping relationship.
  • the first communication device further includes a third processing unit.
  • the third processing unit is configured to map the second service data to at least the basic frame payload of the small granular unit according to a third mapping relationship before sending the basic payload of the basic frame of the small granular unit to the second communication device. a subslot.
  • the third mapping relationship indicates the mapping relationship between the second client client and the at least one sub-slot, and the second client corresponds to the second small-grained service.
  • the embodiment of the present application provides a second communication device.
  • the second communication device includes an acquisition unit and a processing unit.
  • the obtaining unit is configured to receive the first basic frame overhead of the small granular unit sent by the first communication device, and the first basic frame overhead of the small granular unit is used to bear the first service data of the first small granular service.
  • the second processing unit is configured to process the basic frame overhead of the first small granular unit.
  • the obtaining unit is further configured to: receive the payload of the basic frame of the small particle unit sent by the first communication device, and the payload of the basic frame of the small particle unit carries the payload of the second small particle service For the second service data, the first small-grain service is different from the second small-grain service.
  • the first small particle unit basic frame overhead includes a first general communication channel (GCC) field, and the first GCC field carries the first service data.
  • GCC general communication channel
  • At least one byte of the first GCC field is designated to bear the first small-grained service.
  • the obtaining unit is configured to: receive the multiframe of the small particle unit sent by the first communication device, and the multiframe of the small particle unit includes the adjacent first basic frame of the small particle unit and The second small-grain unit base frame, the first small-grain unit base frame includes the overhead of the first small-grain unit base frame, the second small-grain unit base frame includes the second small-grain unit base frame overhead, the The first GCC field of the basic frame overhead of the first small granular unit and the second GCC field of the basic frame overhead of the second small granular unit form a first GCC code block, and the first GCC code block is designated for carrying The first small particle business.
  • the processing unit is configured to: exchange the first service data from the first client to the second client, where the first client corresponds to the first small-grain service, The second client corresponds to the first small-grain service.
  • the processing unit is configured to: extract the first service data from the first GCC field based on a first mapping relationship, where the first mapping relationship indicates that the first client and A mapping relationship between the first GCC fields; based on a second mapping relationship, the first service data is mapped to a third GCC field, and the second mapping relationship indicates the second client and the third GCC Mapping relationship between fields.
  • the first mapping relationship includes a mapping relationship between at least one byte of the first GCC field and the first client.
  • the first mapping relationship includes a mapping relationship between the first GCC code block and the first client, and the first GCC code block consists of the first GCC field and the second Composed of GCC fields, the second GCC field is included in the basic frame overhead of the second small granular unit, the basic frame overhead of the first small granular unit is included in the basic frame of the first small granular unit, and the second small granular unit The basic frame overhead is included in the second small granular unit basic frame, and the first small granular unit basic frame and the second small granular unit basic frame are adjacent basic frames in the small granular unit multiframe.
  • the second mapping relationship includes a mapping relationship between at least one byte of the third GCC field and the second client.
  • the second mapping relationship includes a mapping relationship between the second GCC code block and the second client.
  • the second GCC code block is composed of the third GCC field and the fourth GCC field
  • the third GCC field contains the third small particle unit basis sent by the second communication device to the third communication device.
  • the fourth GCC field is included in the fourth small granular unit basic frame overhead sent by the second communication device to the third communication device, the third small granular unit basic frame and the fourth small granular unit basic frame
  • the granular unit base frame is the adjacent base frame in the small granular unit multiframe.
  • the processing unit is configured to transparently transmit the basic frame overhead of the first small granular unit.
  • the acquiring unit is further configured to acquire first configuration information, where the first configuration information includes the first mapping relationship or the second mapping relationship.
  • the processing unit is configured to: extract the first service data from the basic frame overhead of the first small granular unit; perform layer-2 or layer-3 processing on the first service data .
  • the second communication device further includes a sending module; the sending module is configured to forward the first service data.
  • the embodiment of the present application provides a data frame structure.
  • the data frame structure includes the basic frame overhead of the small granular unit and the payload of the basic frame of the small granular unit.
  • the small particle unit basic frame overhead includes a first field, the first field is used to carry the first service data of the first small particle service, and the small particle unit basic frame payload is used to carry the second small particle service For the second service data, the first small-grain service is different from the second small-grain service.
  • the basic frame overhead of the small granular unit further includes a second field, and the second field is used to carry a version number of the data frame structure.
  • the overhead field further includes a third field, where the third field is used to bear the service type of the first small-grained service.
  • the overhead field further includes a fourth field, where the fourth field is used to carry clock frequency information.
  • the basic frame overhead of the small granular unit further includes a fifth field, and the fifth field is used to carry a reserved field.
  • the basic frame overhead of the small particle unit further includes a sixth field, and the sixth field is used to carry overhead check information.
  • the basic frame overhead of the small particle unit further includes a seventh field, and the seventh field is used to carry a sequence number.
  • the embodiment of the present application provides a communication system.
  • the communication system includes a first communication device and a second communication device.
  • the first communication device is configured to execute the method described in the foregoing first aspect and any optional implementation manner.
  • the second communication device is configured to execute the method described in the above second aspect and any optional implementation manner.
  • the first communication device can be understood with reference to any first communication device described in the third aspect above, and the second communication device can be understood with reference to any second communication device described in the fourth aspect above. repeat.
  • the embodiment of the present application provides a computer-readable storage medium, including programs or instructions, which, when run on a computer, cause the computer to execute any one of the first aspect, the first aspect, or the second aspect 1.
  • the embodiment of the present application provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute any one of the first aspect and the first aspect, or the second aspect or the second aspect.
  • the ninth aspect of the present application provides a chip system, which may include a processor, configured to support the first communication device to implement the above-mentioned first aspect, or the method described in any possible implementation manner of the first aspect.
  • the chip system may further include a memory, and the memory is configured to store necessary program instructions and data of the first communication device or the second communication device.
  • the system-on-a-chip may consist of chips, or may include chips and other discrete devices.
  • the chip system may include application specific integrated circuit (application specific integrated circuit, ASIC), off-the-shelf programmable gate array (field programmable gate array, FPGA) or other programmable logic devices. Further, the chip system may also include an interface circuit and the like.
  • the first service data of the first small-grain service is carried by the basic frame overhead of the small-grain unit, and the service data of the small-grain service can be completed without occupying an additional sub-slot to transmit the first service data Bearing and transmission, avoiding bandwidth waste as far as possible, effectively saving bandwidth resources.
  • Figure 1 shows a schematic diagram of the general architecture of FlexE based on the flexible Ethernet protocol
  • Fig. 2 shows a schematic diagram of a basic frame structure of a small particle unit
  • Fig. 3 shows a schematic diagram of a small particle unit multiframe structure
  • FIG. 4A shows a schematic diagram of an overhead format of a basic frame overhead of a small granular unit
  • FIG. 4B shows a schematic diagram of another overhead format of a basic frame overhead of a small granular unit
  • FIG. 4C shows a schematic diagram of another overhead format of a basic frame overhead of a small granular unit
  • FIG. 5 shows a schematic diagram of carrying data in the GCC field in the embodiment of the present application
  • FIG. 6 shows a schematic diagram of the GCC overhead in a multi-frame period of a small particle unit in the embodiment of the present application
  • FIG. 7 shows a schematic diagram of a hybrid networking scenario
  • FIG. 8 shows a schematic diagram of a system architecture
  • FIG. 9 shows a schematic flowchart of a data transmission method provided by an embodiment of the present application.
  • FIG. 10 shows a schematic diagram of a mapping provided in the embodiment of the present application.
  • Figure 11A shows a schematic diagram of the configuration of the GCC code block provided in the embodiment of the present application.
  • FIG. 11B shows another schematic diagram of mapping provided in the embodiment of the present application.
  • Fig. 12 shows a schematic diagram of exchanging the first service data in the client provided in the embodiment of the present application
  • FIG. 13 shows a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • FIG. 14 shows a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 15 shows a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 16 shows a schematic structural diagram of another communication device provided by an embodiment of the present application.
  • FIG. 17A shows a schematic structural diagram of a first communication device provided by an embodiment of the present application.
  • FIG. 17B shows a schematic structural diagram of another first communication device provided by the embodiment of the present application.
  • FIG. 17C shows a schematic structural diagram of another first communication device provided by the embodiment of the present application.
  • FIG. 17D shows the structure of another first communication device provided by the embodiment of the present application.
  • FIG. 18 shows a schematic structural diagram of another second communication device provided by an embodiment of the present application.
  • the embodiment of the present application provides a data transmission method and a related device, which solve the serious problem of bandwidth waste when carrying out services based on sub-slots in the current FlexE technology.
  • At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items.
  • at least one item (piece) of a, b or c can 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 It can be single or multiple.
  • at least one item (item) can also be interpreted as “one item (item) or multiple items (item)”.
  • the Optical Internet Forum (optical internet forum, OIF) released the FlexE standard.
  • OIF optical internet forum
  • the FlexE standard IA OIF-FLEXE-01.0, IA OIF-FLEXE-02.0 or IA OIF formulated by OIF - Relevant instructions for FLEXE02.1 the above-mentioned standard is incorporated in this application by reference in its entirety.
  • the Ethernet interface and the Ethernet interface are often used interchangeably, and the flexible Ethernet interface and the flexible Ethernet interface are often used interchangeably.
  • Fig. 1 shows a schematic diagram of the general architecture of FlexE based on the flexible Ethernet protocol.
  • a flexible Ethernet protocol group (flex ethernet group, FlexE Group) includes 4 PHYs.
  • FlexE Client can represent the client data flow transmitted on one time slot or multiple time slots of FlexE Group.
  • One FlexE Group can carry multiple FlexE Clients, one FlexE Client can correspond to one business data flow to multiple clients (also called MAC Client), and the FlexE Shim layer provides data adaptation and conversion from FlexE Client to MAC Client.
  • FlexE can support the mapping and transmission of any number of different FlexE Clients on any set of PHYs, so as to realize functions such as PHY bundling, channelization, and sub-rate.
  • the FlexE Shim layer can divide each 100GE PHY in the FlexE Group into 20 slots (slots) of data bearing channels, and the corresponding bandwidth of each slot is 5Gbps.
  • SPN slicing packet network
  • MTN metro transport network
  • G.8310 and G.8312 The bandwidth granularity of the SPN channel layer is specified as 5Gbps.
  • FGU fine granularity unit
  • the SPN channel layer bandwidth granularity of 5Gbps is further divided and multiplexed into time slots to form a small granularity channel with a bandwidth granularity of 10Mbps.
  • the SPN channel layer is located in the physical coding sublayer (PCS) layer of the standard IEEE 802.3, and its coding method adopts the coding format in which 64 bits in the PCS layer are transcoded into 66 bits (subsequently referred to as 64B/66B).
  • PCS physical coding sublayer
  • FGU can also be called a small-grain base frame, a small-grain unit base frame, a basic unit frame or a single frame, and a small grain can also be called a fine grain, and only the small-grain unit base frame is used as an example for illustration .
  • the base frame of the small granular unit adopts the 64B/66B coding format corresponding to the SPN channel layer, and encodes the overhead (overhead, OH) of the basic frame of the small granular unit and the payload of the basic frame of the small granular unit including multiple time slots, and Encapsulate the encoded small granular unit basic frame overhead and small granular unit basic frame payload into a fixed-length code block sequence.
  • Fig. 2 shows a schematic diagram of a basic frame structure of a small particle unit. As shown in Figure 2, in order to be compatible with the Ethernet frame format defined by IEEE802.3, the basic frame of the small particle unit is encapsulated with 1 S code block, 195 D code blocks and 1 T code block.
  • the S code block is used to indicate the frame header of the basic frame of the small particle unit.
  • the data field of the D code block (the Block payload field shown in FIG. 2 ) is used to carry the payload of the basic frame of the small particle unit.
  • the T code block can be used to indicate the frame end of the basic frame of the small granular unit.
  • a code block contains 8 bytes.
  • the 195 D code blocks and 1 T code block of the small particle unit base frame jointly carry 1567 bytes of data content, including 7 bytes of small particle unit base frame overhead and 1560 The small granular unit of byte base frame payload.
  • the small granular unit base frame payload is divided into 24 sub-slots of the same size, which are represented by sub-slot 1 to sub-slot 24 in the figure.
  • Each sub-slot is 65 bytes and can carry 8 code blocks of 65 bits. After the service data is compressed and transcoded from 66B to 65B, it is filled into the sub-slot payload.
  • the bandwidth granularity 5Gbps of the SPN channel layer is divided into time slots in a multi-frame manner, which can be understood specifically with reference to the schematic diagram of the multi-frame structure of a small granular unit shown in FIG. 3 .
  • the FlexE Client interface or common ETH interface with a bandwidth granularity of 5Gbps can be divided into 480 sub-slots in the time domain for cyclic transmission. That is, in each time slot scheduling cycle of a FlexE client interface (480 sub-slots are a time slot scheduling cycle), 20 small granular unit basic frames are evenly distributed (for example: small granular unit basic frame 1 to small granular unit basic frame Frame 20), that is, a small granular unit multiframe.
  • Each small granular unit base frame contains 24 sub-slots.
  • each sub-slot payload can contain 8 compressed code blocks of 66B, and for a small granular unit basic frame, plus S code blocks and code blocks corresponding to the small granular unit basic frame overhead ( In the figure, it is regarded as OH) and T code blocks for encapsulation, and a small particle unit basic frame can contain 197 66B code blocks.
  • I code blocks can be added between small particle unit basic frames, and part of I code blocks can also be replaced by OAM code blocks transmitted in the FlxeE client interface.
  • the I code block is an idle (idle) code block, which is used for MAC layer rate adaptation.
  • the length of the multiframe should be less than or equal to 9600 bytes.
  • the FlexE client interface with a bandwidth granularity of 5 Gbps is illustrated by taking 480 sub-slots and 20 small-grain unit basic frames as a small-grain unit multiframe as an example in the above-mentioned FIG. 3 .
  • the number of sub-slots divided in the time domain can also be different, which can be configured flexibly.
  • FIG. 4A shows a schematic diagram of an overhead format of a basic frame overhead of a small granular unit. It can be seen from FIG. 4A that each basic frame of the small granular unit includes 7 bytes of the basic frame overhead of the small granular unit, that is, the basic frame overhead of the small granular unit is 56 bits.
  • the basic frame overhead of the small granular unit includes a 6-bit multiframe indicator (multiframe indicator, MFI), a 2-bit Flag, a 2-bit RES, and 44-bit overhead information (OH information).
  • the overhead information may at least include the following content: S bit, C bit, change request (change request, CR) bit, change response (change answer, CA) bit, general communication channel (general communication channel, GCC) field, client identifier (client identifier, client ID), sub-slot identifier (sub-slot identifier, sub-slot ID), and cyclic redundancy check (cyclic redundancy check, CRC) fields, etc.
  • S bits are used to carry the time slot increase adjustment notification information
  • the C bits are used to carry the time slot validation indication information
  • the CR bits are used to carry the time slot adjustment response information
  • the CRC field is used to carry the cyclic redundancy code check information. test information.
  • the values of the Flag area are different, it indicates that the corresponding bit position can be used by different channels.
  • the corresponding bit position after the CA bit can be inserted into the GCC field, indicating that the bit position occupied by the GCC field is provided for use by the GCC channel, specifically It can be understood with reference to the schematic diagram of another overhead format of the basic frame overhead of the small granular unit shown in FIG. 4B .
  • the corresponding bit position after the CA bit can be provided to the client ID and sub-slot ID, for details, refer to the small particle unit shown in Figure 4C Understand the schematic diagram of another overhead format of the basic frame overhead.
  • the above-mentioned GCC field in the overhead of the small granular unit basic frame in a small granular unit basic frame is a field with a length of 33B, which is used to indicate that data is transmitted through the corresponding GCC channel.
  • the information transmitted through the GCC channel adopts the Ethernet packet format and follows the 64B/66B encoding format in IEEE 802.3.
  • Fig. 5 shows a schematic diagram of carrying data in the GCC field in the embodiment of the present application. As shown in Figure 5, for the data encoded by 64B/66B, the first 33 bits of the data (bits 0 to 32, including the synchronization header) and the last 33 bits of the data are carried in the GCC field successively, and are carried in the GCC channel in the order of carrying transmission.
  • FIG. 6 shows a schematic diagram of GCC overhead in a multiframe period in the embodiment of the present application.
  • 10 64B/66B code blocks can be transmitted on the MTN interface with a bandwidth granularity of 5Gbps.
  • the GCC channel mentioned above is mainly used for the transmission of management information, control plane protocol, automatic link discovery, and 1588v2 time protocol messages.
  • information through the GCC channel it is mainly transmitted in the format of Ethernet frame or Ethernet packet.
  • the network elements of the network send and receive management and control information hop by hop, and the protocol layer needs to participate in the processing.
  • FIG. 7 shows a schematic diagram of a hybrid networking scenario.
  • the equipment of operator A traverses a network composed of equipment of operator B
  • the network of operator B needs to be interconnected with the network of operator A
  • the controller of operator A needs to traverse Only the network of operator B can manage and control the equipment of remote operator A.
  • this hybrid network it is necessary to deploy sub-slots with a bandwidth granularity of about 10 Mbps in the network of operator A to transmit service data and management information of small-grained services in operator B and control information.
  • plesiochronous digital hierarchy (PDH) service plesiochronous digital hierarchy (PDH) service, synchronous digital hierarchy (SDH) services, Ethernet (ethernet, ETH) services or Internet Protocol (Internet Protocol, IP) services, etc.
  • PDH plesiochronous digital hierarchy
  • SDH synchronous digital hierarchy
  • Ethernet ethernet, ETH
  • Internet Protocol Internet Protocol, IP
  • Individual header bytes in the SDH frame such as F1, E1, D1-D3, J0 and other regenerator section overheads (regenerator section overhead, RSOH), K1, K2, D4-12, E2, S1 and other multiplex section overheads ( multiplex section overhead, MSOH), etc.
  • a sub-slot is used to transmit business data of some small-grained services less than 10Mbps, or to transmit management information and control information of third-party equipment across the network, it will inevitably cause the sub-slot to be damaged. The waste of bandwidth resources cannot accurately match business needs.
  • the embodiment of the present application redefines a new data frame structure on the basis of the existing FlexE interface or common Ethernet physical interface. That is, the data frame structure may also be called a small-grain unit basic frame, and is used to carry the service data flow of the client corresponding to different small-grain services.
  • each basic frame of the small granular unit includes the basic frame overhead of the small granular unit and the payload of the basic frame of the small granular unit.
  • the GCC field described above is used to transmit the service data of the small-grained service (that is, the first service data described later), and there are two possible transmission modes.
  • one way is to first map the first service data into the payload of the small granular unit basic frame, and then pass the entire small granular unit basic frame through the specified one or more in the GCC field of the small granular unit basic frame overhead. code blocks for transmission.
  • Another way is to map the first service data to one or more bytes of the GCC field of the basic frame overhead of the small granular unit, or one or more bytes consisting of the GCC fields in the basic frame overhead of the small granular unit Transmission in multiple GCC code blocks.
  • the basic frame overhead of the small particle unit includes a first field, and the first field is used to carry the first service data of the first small particle service.
  • the payload of the basic frame of the small granular unit is used to carry the service data of the second small granular service, and the first small granular service is different from the second small granular service.
  • the basic frame overhead of the small granular unit may also include other fields for carrying different contents. As an example, it may be understood in conjunction with Table 1 below.
  • the first service data of the first small-grain service can be transmitted through the basic frame overhead of the small-grain unit in the data frame structure, without occupying an additional sub-slot to transmit the first service data, avoiding bandwidth waste as much as possible.
  • the described first field may be the aforementioned GCC field, which is not limited here.
  • the embodiment of the present application provides a data transmission method, which can be applied to the application scenario of the system architecture 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, and at this time, the network device 1 is connected to the user equipment 1 through other network devices.
  • the network device 1 may be an edge node, and at this time the network device 1 is directly connected to the user equipment 1 .
  • the network device 2 may be an intermediate node. In this case, the network device 2 is connected to the user equipment 2 through 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 equipment 2 .
  • Network device 1 includes a FlexE interface 1
  • network device 2 includes a FlexE interface 2 .
  • FlexE port 1 is connected to FlexE port 2.
  • Each FlexE interface includes a sending port and a receiving port.
  • the difference from a traditional Ethernet interface is that a FlexE interface can carry multiple clients, and a FlexE interface as a logical interface can be composed of multiple physical interfaces.
  • the flow of service data in the forward channel shown in FIG. 8 is shown by the solid arrow in FIG. 8
  • the flow of service data in the reverse channel is shown by the dotted arrow in FIG. 8 .
  • the transmission channel in the embodiment of the present application takes the forward channel as an example, and the flow direction of service data in the transmission channel is user equipment 1 -> network equipment 1 -> network equipment 2 -> user equipment 2.
  • FIG. 8 only exemplarily shows 2 network devices and 2 user equipments, and the system structure may also include any other number of network devices and user equipments, which is not limited in this embodiment of the present application.
  • the system architecture shown in FIG. 8 is only for illustration, and the application scenarios of the system architecture provided in the present application are not limited to the scenarios shown in FIG. 8 .
  • the technical solutions provided in this application are applicable to all network scenarios where the FlexE technology is used for data transmission.
  • FIG. 9 is a schematic flowchart of a method for data transmission provided in this embodiment of the present application. As shown in Figure 9, the method for data transmission may include the following steps:
  • the first communication device acquires first service data of a first small-grain service.
  • the first small-grained service may be, for example, a service with a bandwidth smaller than that of a GCC channel.
  • the described bandwidth of the GCC channel can be understood with reference to the content described in the foregoing FIG. 6 , and details are not described here.
  • the first small-grained services may include but not limited to PDH services, SDH services, ETH services, IP services, business calls, individual opening 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.
  • the first communication device is an intermediate node, the overhead cross-correlation operation mentioned in subsequent steps S01-S04 may not be performed, but the first service may be demapped from the data block sent by the previous hop node data, and repackage the first service data.
  • the first communication device sends a first small-grain unit basic frame overhead to a second communication device, where the first small-granular unit basic frame overhead carries the first service data.
  • the first communication device may map the first service data to the basic frame overhead of the first small-granular unit, and the first small-granular unit The basic frame overhead carries the first service data.
  • the first communication device sends the basic frame overhead of the first small particle unit to the second communication device through the FlexE interface.
  • the first communication device may also send a plurality of first data blocks to the second communication device, and the plurality of first data blocks include the basic frame overhead of the first small granular unit.
  • a small particle unit multiframe may include a first small particle unit basic frame.
  • the first small particle unit base frame may be the small particle unit base frame 1 shown in FIG. 3 , or the small particle unit base frame 2 , etc., which are not limited here.
  • overhead of the first basic frame of the small particle unit may be included.
  • the basic frame overhead of the first small particle unit may include a first GCC field, and the first GCC field may be used to bear the first service data.
  • the first GCC field includes at least one byte. At least one byte of the first GCC field is designated for carrying the first small-grained service.
  • a second small particle unit basic frame may also be included in a small particle unit multiframe, and the second small particle unit basic frame is adjacent to the above-mentioned first small particle unit basic frame.
  • the first small particle unit base frame can be the aforementioned small particle unit base frame 1 shown in FIG. 3
  • the second small particle unit base frame can be the small particle unit base frame 2, etc.; or, or,
  • the first small particle unit base frame can be the small particle unit base frame 3 shown in the aforementioned FIG. 3
  • the second small particle unit base frame can be the small particle unit base frame 2 or the small particle unit base frame 4, etc. , is not limited here. No limitation is given here.
  • the second small-grain unit basic frame includes the overhead of the second small-grain unit basic frame.
  • the first GCC code block may be composed of the first GCC field and the second GCC field of the basic frame overhead of the second small granular unit, and the first GCC code block is designated to bear the first small granular service.
  • the first small-grain service corresponds to the first client, and the first client includes the first service data.
  • the first small-grained service can be carried in the byte, so as to realize the transmission of the first service data carried in the byte.
  • the first small-grained service may be carried in the code block through the corresponding relationship between the code block and the first client, so as to realize the transmission of the first service data carried in the code block. How to map the first service data into bytes or code blocks will be described below from different examples.
  • the first service data before sending the basic frame overhead of the first small particle unit, may be mapped to at least one byte according to the first mapping relationship, and the first mapping relationship indicates at least one byte and In the mapping relationship between the first client clients, the first client corresponds to the first small-grain service.
  • the control management device may configure a corresponding relationship between at least one byte of the first GCC field and the first client to obtain a mapping relationship 1. Then, the control management device sends the mapping relationship 1 to the first communication apparatus, for example, by means of configuration information A.
  • the configuration information A may also be acquired actively by the first communication means from the control management device.
  • the first communication device also stores the configuration information A locally, and acquires the configuration information A locally.
  • the method for obtaining the mapping relationship 1 is not limited in this application.
  • the first communication device after the first communication device obtains the configuration information A, it can obtain the mapping relationship 1 included therein. Moreover, since the first small-grained service corresponds to the first client, and the first client can include the first service data, then after the first communication device obtains the mapping relationship 1, it can map the first service data based on the mapping relationship 1 into at least one byte of the first GCC field.
  • FIG. 10 is a schematic diagram of a mapping provided in the embodiment of the present application. It can be seen from FIG. 10 that the first service data can be mapped into one or more bytes of 32 bytes by taking 8 bits (that is, one byte) as a basic unit. Exemplarily, if the bandwidth occupied by the first service data is less than the bandwidth of one byte, the first service data can be carried in any byte; or, if the bandwidth occupied by the first service data is greater than the bandwidth of one byte , or multiple bytes may be bundled together to jointly carry the first small-grained service.
  • mapping relationship 1 may indicate a mapping relationship between at least one byte of the first GCC field and the first client.
  • configuration information A may also indicate the byte position and the number of bytes of the first GCC field occupied by the first service data.
  • the first mapping relationship (that is, the above-mentioned mapping relationship A) may specifically include a mapping relationship between the first client identifier client ID and the byte identifier.
  • the first client ID is used to identify the first client, and the first client corresponds to the first small-grain service.
  • a byte identifier is used to identify at least one byte.
  • one byte may correspond to one byte identifier, or multiple bytes may correspond to the same byte identifier, which is not limited in this application.
  • the byte identifier can 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 know which bytes in the first GCC field the first service data needs to be mapped to.
  • client IDs such as client ID 1 to client ID 4
  • client ID 1 to client ID 4 use different client IDs (such as client ID 1 to client ID 4) to identify these 4 clients, and use the byte identifier A1 Identify byte 1, use byte identifier B1 to identify byte 2 to byte 5, use byte identifier C1 to identify byte 6 to byte 8, use byte identifier D1 to identify byte 9, and so on.
  • mapping relationship between client ID 1 and byte identifier A1, the mapping relationship between client ID 2 and byte identifier B1, the mapping relationship between client ID 3 and byte identifier C1, and the mapping relationship between client ID 4 and byte identifier There is a mapping relationship between section identifiers D1 and so on.
  • the first business data of the client identified by the client ID 1 can be carried by byte 1
  • the first business data of the client identified by the client ID 2 can be carried by byte 2 to byte 5
  • the first business data of the client identified by the client ID 2 can be carried by byte 6
  • Byte 8 carries the first service data of the client identified by client ID 3
  • byte 9 carries the first service data of the client identified by client ID 4.
  • the first service data before sending the basic frame overhead of the first small particle unit, may also be mapped to the first GCC code block according to the second mapping relationship, and the second mapping relationship indicates that the first GCC and In the mapping relationship between the first client clients, the first client corresponds to the first small-grain service.
  • the first GCC code block can be understood with reference to the aforementioned content, and details are not described here.
  • the control and management device may configure a corresponding relationship between the first GCC code block and the first client to obtain the mapping relationship 2. Then, the control management device sends the mapping relationship 2 to the first communication device, for example, by means of configuration information B.
  • the configuration information B may also be acquired actively by the first communication means from the control management device.
  • the first communication device also stores the configuration information B locally, and acquires the configuration information B locally.
  • the method for obtaining the configuration information B is not limited in this application.
  • configuration information B may be the same as configuration information A. That is to say, the above-mentioned mapping relationship 1 may also be carried in the configuration information A, or the above-mentioned mapping relationship 2 may also be carried in the configuration information B.
  • the mentioned mapping relationship 2 may indicate the mapping relationship between the first GCC code block and the first client.
  • the mapping relationship 2 includes a mapping relationship between at least one GCC code block and the first client, and the at least one GCC code block is used to carry a small-grained service corresponding to the first client.
  • the at least one GCC code block includes the first GCC code block, and may further include a second GCC code block.
  • the configuration information B may also indicate code block positions and code block numbers of all GCC code blocks occupied by the first small-grained 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.
  • FIG. 11A is a schematic configuration diagram of a GCC code block provided in the embodiment of the present application. It can be seen from FIG. 11A that in an MTN interface with a bandwidth granularity of 5Gbps, there are ten 66B GCC code blocks (such as Block 0 to Block 9) in one multiframe period.
  • FIG. 11B shows another schematic diagram of mapping provided in the embodiment of the present application. It can be seen from FIG. 11B that the first service data can be mapped to one or more code blocks of the four GCC code blocks Block 6 to Block 9 directly according to a code block as a basic unit. Exemplarily, if the bandwidth occupied by the first service data is less than the bandwidth of a GCC code block, the first service data can be carried in any GCC code block; or, if the bandwidth occupied by the first service data is greater than the bandwidth of a code block When the bandwidth is limited, multiple GCC code blocks can also be bundled together to jointly bear the first service data.
  • mapping of the first service data to one or more GCC code blocks in Block 6 to Block 9 shown in FIG. 11B is only a schematic description, and the specific application does not make a limited description.
  • the second mapping relationship may include a mapping relationship between the first user identifier client ID and the code block identifier.
  • the first client ID is used to identify the first client
  • the first client includes corresponding to the first small-grained service
  • the code block identifier is used to identify at least one code block.
  • the at least one code block includes the aforementioned first GCC code block.
  • one code block may correspond to one code block identifier, or multiple code blocks may correspond to one code block identifier, which is not limited in this application.
  • the first client ID can identify the first client corresponding to the first small-grained service, and the first client includes the first service data.
  • the code block identifier may also be used to indicate at least one code block, and the at least one code block further includes the first GCC code block. Then, by configuring the mapping relationship between the first client ID and the code block identifier, the first communication device can know which GCC code blocks need to be specified for mapping the first service data.
  • each of the code blocks 1 to 5 may be composed of GCC fields in the basic frame overhead of adjacent small granular units.
  • client ID 1-client ID 4 described above, byte identifiers A1, B1, C1, D1, code block identifiers A2, B2, etc., are only schematic descriptions, and are not described in this application embodiment. Do limited.
  • the first communication device sends the first small granular unit basic frame overhead to the second communication device, which may also be implemented in the following manner. That is: the first communication device sends the multiframe of the small granularity unit to the second communication device. That is to say, after the first communication device maps the first service data to the first GCC code block based on the mapping relationship 2, it can directly send the multi-frame of the small particle unit to the second communication device, and then carry the first service data in the The manner of the first GCC code block is transmitted to the second communication device.
  • the first communication device may also map the second service data to at least one sub-slot of the payload of the basic frame of the small particle unit according to the third mapping relationship.
  • the described third mapping relationship indicates the mapping relationship between the second client client and at least one sub-slot, and the second client corresponds to the second small-grained service.
  • the first communication device may also send the payload of the basic frame of the small particle unit to the second communication device.
  • the basic frame payload of the small granular unit is used to bear the second service data of the second small granular service, and the first small granular service is different from the second small granular service.
  • the described second small-grained service refers to a service whose bandwidth is greater than or equal to the bandwidth of one sub-slot.
  • the second communication device receives the first small granular unit basic frame overhead sent by the first communication device.
  • the described second communication device may be an intermediate node or an edge node, which is not limited in this embodiment of the present application.
  • the second communication device can receive the first basic frame overhead of the small granular unit sent by the first communication device.
  • the second communication device may also receive the payload of the small particle unit basic frame sent by the first communication device.
  • the payload of the basic frame of the small granular unit is used to bear the second service data of the second small granular service, and the first small granular service is different from the second small granular service.
  • the described payload of the basic frame of the small granular unit can be understood with reference to the payload of the basic frame of the small granular unit mentioned in the foregoing step 902 , and details are not described here.
  • the basic frame overhead of the first small granular unit includes a first general communication channel (GCC) field, and the first GCC field carries the first service data.
  • GCC general communication channel
  • At least one byte of the first GCC field is designated for carrying the first small-grained service. It should be noted that the described first GCC field and the first small particle unit base frame overhead can be understood with reference to the content mentioned in the foregoing step 902 , and details are not described here.
  • the second communication device receives the first small particle unit basic frame overhead sent by the first communication device, which may be implemented in the following manner: the second communication device receives The small granular unit multiframe.
  • the multi-frame of the small-grain unit includes adjacent first and second basic frames of the small-grain unit.
  • the first small granular unit base frame includes the first small granular unit basic frame overhead
  • the second small granular unit basic frame overhead includes the second small granular unit basic frame overhead
  • the first GCC field and the second small granular unit basic frame overhead The second GCC field of the basic frame overhead of the small granular unit forms the first GCC code block
  • the first GCC code block is designated to bear the first small granular service.
  • the second communication device processes the basic frame overhead of the first small granular unit.
  • the second communication device is an intermediate node
  • the second communication device when it is an intermediate node, after obtaining the basic frame overhead of the first small granular unit, it can also forward the basic frame overhead of the first small granular unit to the downstream edge node or the next-hop intermediate node, and the downstream The edge node or the intermediate node of the next hop demaps the first service data.
  • the first service data may also be demapped first, and then forwarded to a downstream edge node or intermediate node. The following will illustrate from different examples:
  • the second communication device processes the basic frame overhead of the first small granular unit, and forwards it through the following steps, namely: exchanging the first service data from the first client to the second client, wherein , the first client corresponds to the first small-grain service, and the second client corresponds to the first small-grain service.
  • exchanging the first service data from the first client to the second client can be understood as exchanging the first service data from the client on the receiving side to the client on the sending side.
  • FIG. 12 is a schematic diagram of exchanging the first service data in the client provided in the embodiment of the present application.
  • the second communication device is configured with a first client on the receiving side and a second client on the sending side.
  • the first client on the receiving side can be, for example, any client in client A1, client A2, ..., or client Am (m is a positive integer greater than or equal to 1)
  • the second client on the sending side can be, for example, client B1, Any one of client B2, ..., or client Bm.
  • client A1 can for example be configured to exchange with client B1.
  • client A2 for example, can be configured to exchange with client B2.
  • client Am For the rest of client Am, their exchange relationship can also be understood with reference to the above exchange relationship, so I won’t go into details here.
  • the first client mentioned here is the client corresponding to when the second communication device receives the first small granular base frame overhead from the first communication device.
  • the second client is the client corresponding to when the second communication device sends the first small granular basic frame overhead to the third communication device.
  • the second communication device exchanges the first service data from the first client to the second client, which may be implemented in the following manner, namely:
  • mapping relationship Based on the second mapping relationship, map the first service data to the third GCC field, where the second mapping relationship indicates a mapping relationship between the second client and the third GCC field.
  • the first service data may be mapped from at least one byte of the first GCC field to at least one byte of the third GCC field based on the first mapping relationship and the second mapping relationship.
  • the first service data may also 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 first mapping relationship may include a mapping relationship between at least one byte of the first GCC field and the first client
  • the second mapping relationship may include at least one byte of the third GCC field and the second client mapping relationship between them.
  • the second client since the first small-grain service corresponds to the first client, the second client also corresponds to the first small-grain service.
  • the first GCC field corresponding to the first client may include at least one byte
  • the third GCC field corresponding to the second client may also include at least one byte. Then, after the first service data can be extracted from the first GCC field through the first mapping relationship, the first service data can be mapped to at least one byte of the third GCC field based on the second mapping relationship.
  • the second communication device may further send the third small particle unit basic frame overhead including the third GCC field to the third communication device.
  • the first mapping relationship includes a mapping relationship between the first GCC code block and the first client, and the first GCC code block is composed of the first GCC field and the second GCC field.
  • the second mapping relationship includes a mapping relationship between the second GCC code block and the second client, where the second GCC code block is composed of a third GCC field and a fourth GCC field.
  • the first GCC code block can be understood with reference to the content of the foregoing step 903, and details are not described here.
  • the second GCC code block is composed of a third GCC field and a fourth GCC field, wherein the third GCC field is included in the third small particle unit basic frame overhead sent by the second communication device to the third communication device, and the third The four GCC fields are included in the fourth small granular unit basic frame overhead sent by the second communication device to the third communication device.
  • the third small particle unit basic frame and the fourth small particle unit basic frame are adjacent small particle unit basic frames in the small particle unit multiframe.
  • the second client Since the first small-grain service corresponds to the first client, the second client also corresponds to the first small-grain service. Moreover, the first GCC code block corresponds to the first client, and the second GCC code block corresponds to the second client. Then, after extracting the first service data from the first GCC code block, the first service data can be mapped to the second GCC code block based on the second mapping relationship. In this way, the second communication device may further send the third small granular unit base frame overhead including the third GCC field to the third communication device, and send the fourth small granular unit basic frame overhead including the fourth GCC field, so that the first A piece of business data is forwarded.
  • first mapping relationship and the second mapping relationship mentioned in the above 1 and 2 may also be configured by the control and management device, for example, the first mapping relationship and the second mapping relationship may be issued by means of configuration information. to the second communication device. Alternatively, the second communication device may also obtain the first mapping relationship and the second mapping relationship in other ways, which are not limited here.
  • the above mainly describes the process of the second communication device processing the basic frame overhead of the first small granular unit from the perspective of cross-connection technology, so that in the hybrid networking scenario, there is no need to manage the problem of docking management protocol equipment, and it can effectively
  • the first service data is transparently transmitted to save network resources.
  • the second communication device processes the basic frame overhead of the first small granular unit.
  • the forwarding may also be performed in the following way, that is: transparently transmit the first Small granular unit basic frame overhead, the first service data is specified to be carried in at least one byte or at least one code block in the general communication channel GCC field of the first small granular unit basic frame overhead.
  • the second communication device after obtaining the basic frame overhead of the first small granular unit, the second communication device does not need to transfer the first service data from the byte of the first GCC field of the basic frame overhead of the first small granular unit, or the second It is analyzed in a GCC code block, but the time slot used when transmitting large-grained services can directly transparently transmit the basic frame overhead of the first small-granularity unit, so that the first service data is transmitted to the intermediate node or edge of the next hop node etc.
  • the second communication device obtains the basic frame overhead of the first small granular unit, in addition to forwarding through the above exchange and directly transparently transmitting the basic frame overhead of the first small granular unit
  • the following steps may also be performed: extracting the first service data from the basic frame overhead of the first small granular unit.
  • the first service data may be demapped from at least one byte of the first GCC field based on the first mapping relationship.
  • the first service data may be demapped from the first GCC code block based on the first mapping relationship.
  • the described first mapping relationship can be understood with reference to the first mapping relationship mentioned in the aforementioned step S01 , which will not be described in detail here.
  • the first service data may also be demapped from at least one byte of the third GCC field based on the second mapping relationship.
  • the first service data may be demapped from the second GCC code block based on the second mapping relationship.
  • the described second mapping relationship can be understood with reference to the second mapping relationship mentioned in the aforementioned step S02 , which will not be described in detail here.
  • the processed service data can be The message is forwarded to the edge node.
  • the second communication device is an edge node
  • the first service data may be extracted from the basic frame overhead of the first small granular unit; and the first service data Do layer 2 or layer 3 processing to reassemble the message.
  • the edge node when it obtains the basic frame overhead of the third small granular unit or the basic frame overhead of the fourth small granular unit sent by the intermediate node, it may also transfer the first service data from the first Three GCC fields are demapped out of at least one byte.
  • the first service data may be demapped from the second GCC code block based on the second mapping relationship.
  • the described second mapping relationship can be understood with reference to the second mapping relationship mentioned in the aforementioned step S02 , which will not be described in detail here.
  • the first service data of the first small-grain service is carried by the basic frame overhead of the small-grain unit, and the service of the small-grain service can be completed without occupying an additional sub-slot to transmit the first service data
  • the bearing and transmission of data avoids the waste of bandwidth as much as possible and effectively saves bandwidth resources.
  • the first service data can also be transparently transmitted to the next node by means of overhead crossover technology and the like, without adding additional network resources.
  • a communication device 1300 provided in the embodiment of the present application is introduced below with reference to FIG. 13 .
  • the communication device 1300 may be applied in the network architecture shown in FIG. 8 .
  • the communication device 1300 may be the network device 1 (TX) or the network device 2 (RX) shown in FIG. 8 of the present application, and the communication device 1300 may also be the first communication device or the second communication device of the present application .
  • the first communication device and the second communication device of the present application may be the overall network equipment, or a single board in the network equipment 1, such as an interface board or a line card or a dumb board or a centralized cross-connect board, or it may be a board that performs related operations chips etc.
  • the communication device 1300 is configured to execute the method in the embodiment corresponding to any one of the preceding figures 9 to 12 .
  • the communication device 1300 includes a transceiver unit 1301 and a processing unit 1302 .
  • the transceiving unit 1301 is used to perform transceiving operations, and the processing unit is used to perform operations other than transceiving. For example, when the communication device 1300 performs the method shown in FIG.
  • 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 at least one byte according to the second mapping relationship.
  • a service data is mapped to the first GCC code block; the transceiver unit 1301 can be used to send the basic frame overhead of the first small granular unit.
  • the communication device 1400 may be applied in the network architecture shown in FIG. 14 .
  • the communication device 1400 may be the network device 1 (TX) or the network device 2 (RX) of the present application, and the communication device 1400 may also be the first communication device or the second communication device of the present application.
  • the first communication device and the second communication device of the present application may be the overall network equipment, or a single board in the network equipment 1, such as an interface board or a line card or a dumb board or a centralized cross-connect board, or it may be a board that performs related operations chips etc.
  • the communication device 1400 is configured to execute the method in the embodiment corresponding to any one of the aforementioned figures 9 to 12 .
  • the communication device 1400 includes a communication interface 1401 and a processor 1402 connected to the communication interface.
  • the communication interface 1401 is used to perform transceiving operations, and the processor 1402 is used to perform operations other than transceiving.
  • the processor 1402 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 at least one byte according to the second mapping relationship.
  • a service data is mapped to the first GCC code block; the communication interface 1401 can be used to send the basic frame overhead of the first small granular unit.
  • the communication device 1500 may be applied in the network architecture shown in FIG. 8 .
  • the communication device 1500 may be the network device 1 (TX) or the network device 2 (RX) of the present application, and the communication device 1500 may also be the first communication device or the second communication device of the present application.
  • the first communication device and the second communication device of the present application may be the overall network equipment, or a single board in the network equipment 1, such as an interface board or a line card or a dumb board or a centralized cross-connect board, or it may be a board that performs related operations chips etc.
  • the communication device 1500 is configured to execute the method in the embodiment corresponding to any one of the preceding figures 9 to 12 .
  • the communication device 1500 includes a memory 1501 and a processor 1502 connected to the memory. Instructions are stored in the memory 1501, and the processor 1502 reads the instructions, so that the communication device 1500 executes the method of the embodiment corresponding to any one of Fig. 9 to Fig. 12 .
  • the communication device 1600 may be applied in the network architecture shown in FIG. 8 .
  • the communication device 1600 may be the network device 1 (TX) or the network device 2 (RX) of the present application, and the communication device 1600 may also be the first communication device or the second communication device of the present application.
  • the first communication device and the second communication device of the present application may be the overall network equipment, or a single board in the network equipment 1, such as an interface board or a line card or a dumb board or a centralized cross-connect board, or it may be a board that performs related operations chips etc.
  • the communication device 1600 is configured to execute the method in the embodiment corresponding to any one of the aforementioned figures 9 to 12 .
  • the communication device 1000 includes a processor 1610 , a memory 1620 coupled to the processor, and a communication interface 1630 .
  • computer-readable instructions are stored in the memory 1620 , and the computer-readable instructions include a plurality of software modules, such as a sending module 1621 , a processing module 1622 and a receiving module 1623 .
  • the processor 1610 may perform corresponding operations according to the instructions of each software module. In this embodiment, an operation performed by a software module actually refers to an operation performed by the processor 1610 according to an instruction of the software module.
  • the sending module 1621 is used to send the basic frame overhead of the first small granular unit
  • the processing module 1622 is used to send the first service data according to the first mapping relationship Map to at least one byte, or map the first service data to the first GCC code block according to the second mapping relationship.
  • the processor 1610 executes the computer-readable instructions in the memory 1620, it can perform all the operations that can be performed by the first communication device in this application according to the instructions of the computer-readable instructions.
  • the communication device 1600 may execute the method performed by the first communication device in the embodiment corresponding to any one of Figures 9 to 12 .
  • the processor mentioned in this application may be a central processing unit (central processing unit, CPU), a network processor (network processor, NP) or a combination of CPU and NP.
  • the processor can also be an application-specific integrated circuit (application-specific integrated circuit, ASIC), a programmable logic device (programmable logic device, PLD) or a combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the aforementioned PLD may be a complex programmable logic device (complex programmable logic device, CPLD), a field-programmable gate array (field-programmable gate array, FPGA), a general array logic (generic array logic, GAL) or any combination thereof.
  • Processor 1010 may refer to one processor, or may include multiple processors.
  • the memory mentioned in this application can include volatile memory (volatile memory), such as random-access memory (random-access memory, RAM); Memory also can include non-volatile memory (non-volatile memory), such as Read-only memory (read-only memory, ROM), flash memory (flash memory), hard disk (hard disk drive, HDD) or solid-state drive (solid-state drive, SSD); memory can also comprise the combination of memory of above-mentioned kind .
  • volatile memory such as random-access memory (random-access memory, RAM
  • Memory also can include non-volatile memory (non-volatile memory), such as Read-only memory (read-only memory, ROM), flash memory (flash memory), hard disk (hard disk drive, HDD) or solid-state drive (solid-state drive, SSD); memory can also comprise the combination of memory of above-mentioned kind .
  • a storage may refer to one storage, or may include multiple storages.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed by hardware or computer software drives hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may use different methods to implement the described functions for each specific application, but such implementation should not be regarded as exceeding the scope of the present application.
  • this application can divide the functional units of the first communication device and the second communication device according to the above method embodiments, for example, each functional unit can be divided corresponding to each function, or two or more than two functions are integrated in one functional unit.
  • the above-mentioned integrated functional units can be implemented in the form of hardware or in the form of software functional units.
  • FIG. 17A provides a schematic structural diagram of a first communication device according to an embodiment of the present application.
  • the described first communication apparatus may include: an acquiring unit 1701 and a sending unit 1702 .
  • the obtaining unit 1701 is configured to obtain the first service data of the first small-grain service. For details, it can be understood with reference to the content of step 901 in the foregoing FIG. 9 , and details are not described here.
  • the sending unit 1702 is configured to send the first basic frame overhead of the small granular unit to the second communication device, where the first basic frame overhead of the small granular unit carries the first service data.
  • the first basic frame overhead of the small granular unit carries the first service data.
  • the sending unit 1702 is further configured to send the payload of the basic frame of the small particle unit to the second communication device, where the payload of the basic frame of the small particle unit is used to carry the service data of the second small particle service, and the first The small-grain business is different from the second-smallest business.
  • the payload of the basic frame of the small particle unit is used to carry the service data of the second small particle service, and the first The small-grain business is different from the second-smallest business.
  • the basic frame overhead of the first small particle unit includes a first general communication channel GCC field, and the first GCC field is used to bear the first service data.
  • GCC field is used to bear the first service data.
  • At least one byte in the first GCC field is designated to bear the first small-grained service.
  • FIG. 17B shows another schematic structural diagram of the first communication device.
  • the first communication device may further include a first processing unit 1703 in addition to the acquiring unit 1701 and the sending unit 1702 .
  • the first processing unit 1703 is configured to map the first service data to at least one byte according to the first mapping relationship before the sending unit 1702 sends the basic frame overhead of the first small granular unit.
  • the first mapping relationship indicates a mapping relationship between at least one byte and the first client client, and the first client corresponds to the first granular service.
  • the first mapping relationship includes a mapping relationship between the first client identifier client ID and the byte identifier, wherein the first client ID is used to identify the first client, and the byte identifier is used to identify at least one byte.
  • the sending unit 1702 is configured to:
  • the small particle unit multiframe includes the adjacent first small particle unit basic frame and the second small particle unit basic frame
  • the first small particle unit basic frame includes the first small particle unit Base frame overhead
  • the base frame of the second small granular unit includes the basic frame overhead of the second small granular unit
  • the first GCC field of the first small granular unit basic frame overhead and the second GCC field of the second small granular unit basic frame overhead constitute the second A GCC code block, where the first GCC code block is designated to bear the first small-grained service.
  • FIG. 17C shows another schematic structural diagram of the first communication device.
  • the first communication device may further include a second processing unit 1704 in addition to the acquiring unit 1701 and the sending unit 1702 .
  • 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 sending small granularity unit.
  • the second mapping relationship indicates the mapping relationship between at least one code block and the first client client, and the first client corresponds to the first small-grained service.
  • the second mapping relationship includes a mapping relationship between the first client ID and the code block identifier.
  • the first client ID is used to identify the first client
  • the code block identifier is used to identify at least one code block
  • at least one code block includes the first GCC code block.
  • the acquiring unit 1701 is further configured to acquire first configuration information, where the first configuration information includes a first mapping relationship or a second mapping relationship.
  • first configuration information includes a first mapping relationship or a second mapping relationship.
  • FIG. 17D shows another schematic structural diagram of the first communication device.
  • the first communication device may further include a third processing unit 1705 in addition to the acquiring unit 1701 and the sending unit 1702 .
  • the third processing unit 1705 is configured to map the second service data to at least one of the basic frame payload of the small particle unit according to the third mapping relationship before the sending unit 1702 sends the payload of the basic frame frame of the small particle unit to the second communication device subslot.
  • the third mapping relationship indicates the mapping relationship between the second client client and at least one sub-slot, and the second client corresponds to the second small-grained service.
  • FIG. 17A to FIG. 17D mainly describe the first communication device from the perspective of functional modules.
  • the second communication device will be described below from the perspective of functional modules.
  • FIG. 18 provides a schematic structural diagram of a second communication device according to an embodiment of the present application.
  • the described second communication apparatus may include: an acquiring unit 1801 and a processing unit 1802 .
  • the acquiring unit 1801 is configured to receive the first small granular unit basic frame overhead sent by the first communication device, and the first small granular unit basic frame overhead is used to bear the first service data of the first small granular service.
  • the first small granular unit basic frame overhead is used to bear the first service data of the first small granular service.
  • the processing unit 1802 is configured to process the basic frame overhead of the first small granular unit. For details, it can be understood with reference to the content of step 904 in FIG. 9 , which will not be repeated here.
  • the obtaining unit 1801 is further configured to receive the payload of the basic frame of the small particle unit sent by the first communication device, the payload of the basic frame of the small particle unit carries the second service data of the second small particle service, The first small-grain service is different from the second small-grain service.
  • the basic frame overhead of the first small particle unit includes a first general communication channel (GCC) field, and the first GCC field carries the first service data.
  • GCC general communication channel
  • At least one byte of the first GCC field is designated for carrying the first small-grained service.
  • the obtaining unit 1801 is configured to receive the multi-frame of the small particle unit sent by the first communication device, the multi-frame of the small particle unit includes the adjacent first basic frame of the small particle unit and the second small particle unit base frame.
  • the first basic frame of the small particle unit includes the overhead of the first basic frame of the small particle unit
  • the second basic frame of the small particle unit includes the overhead of the second basic frame of the small particle unit.
  • the first GCC field of the basic frame overhead of the first small granular unit and the second GCC field of the basic frame overhead of the second small granular unit form the first GCC code block, and the first GCC code block is designated to bear the first small granular service.
  • the processing unit 1802 is configured to: exchange the first service data from the first client to the second client, where the first client corresponds to the first small-grain service, and the second client corresponds to the first small-grained service. Particle business correspondence.
  • the processing unit 1802 is configured to: extract the first service data from the first GCC field based on the first mapping relationship, where the first mapping relationship indicates the mapping relationship between the first client and the first GCC field ; Based on the second mapping relationship, the first service data is mapped to the third GCC field, and the second mapping relationship indicates the mapping relationship between the second client and the third GCC field.
  • the first mapping relationship includes a mapping relationship between at least one byte of the first GCC field and the first client.
  • the first mapping relationship includes a mapping relationship between the first GCC code block and the first client, the first GCC code block is composed of a first GCC field and a second GCC field, and the second GCC field Included in the second small-grain unit base frame overhead, the first small-grain unit base frame overhead is included in the first small-grain unit base frame overhead, and the second small-grain unit base frame overhead is included in the second small-grain unit base frame,
  • the first small-grain unit base frame and the second small-grain unit base frame are adjacent base frames in the small-grain unit multiframe.
  • the second mapping relationship includes a mapping relationship between at least one byte of the third GCC field and the second client.
  • the second mapping relationship includes a mapping relationship between the 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
  • the third GCC field is included in the third small particle unit basic frame overhead sent by the second communication device to the third communication device
  • the fourth GCC field Included in the fourth small particle unit base frame overhead sent by the second communication device to the third communication device, the third small particle unit base frame and the fourth small particle unit base frame are adjacent base frames in the small particle unit multiframe .
  • the processing unit 1802 is configured to transparently transmit the basic frame overhead of the first small granular unit.
  • the acquiring unit 1801 is further configured to acquire first configuration information, where the first configuration information includes a first mapping relationship or a second mapping relationship.
  • the processing unit 1802 is configured to: extract the first service data from the basic frame overhead of the first small granular unit; and perform Layer 2 or Layer 3 processing on the first service data.
  • the embodiment of the present application also provides a communication system, including a first communication device and a second communication device, wherein the first communication device or the second communication device may be the communication device in any one of Figures 13-16, for Execute the method in any one of the embodiments corresponding to FIG. 9 to FIG. 12 .
  • the first communication device may also be the first communication device in any one of the above-mentioned Figures 17A to 17B
  • the second communication device may also be the second communication device in the aforementioned Figure 18, which is used to perform the corresponding operations in Figures 9 to 12
  • the communication system may further include the control management device described in this application.
  • the present application also provides a computer program product, including a computer program, which, when running on a computer, enables the computer to execute any one of the embodiments corresponding to FIGS. 9 to 12 by the first communication device and the second communication device. Or control the method performed by the management device.
  • the present application also provides a computer program product, including a computer program, which, when running on a computer, enables the computer to execute any one of the embodiments corresponding to FIGS. 9 to 12 by the first communication device and the second communication device. Or control the method performed by the management device.
  • the present application provides a computer-readable storage medium, including computer instructions.
  • the computer can execute any one of the embodiments corresponding to FIG. 9 to FIG. 12 by the first communication device and the second communication device. Or control the method performed by the management device.
  • modules and method operations of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are executed by hardware or software depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functions using different methods for each particular application.
  • all or part of the implementation may be implemented by hardware, firmware or any combination thereof.
  • software When software is involved in the specific implementation process, it may be fully or partially embodied in the form of computer program products.
  • the computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on the computer, the processes or functions according to the embodiments of the present application will be generated in whole or in part.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable devices.
  • the computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website, computer, server or data center Transmission to another website site, computer, server, or data center by wired (eg, coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer, or a data storage device such as a server or a data center integrated with one or more available media.
  • the available medium may be a magnetic medium (for example, a floppy disk, a hard disk, or a magnetic tape), an optical medium (for example, DVD), or a semiconductor medium (for example, a Solid State Disk (SSD)).
  • SSD Solid State Disk

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请公开了一种数据传输的方法以及相关装置，通过小颗粒单元基帧开销承载第一小颗粒业务的第一业务数据，无需占用额外的子时隙sub-slot来传输该第一业务数据，即可完成对小颗粒业务的业务数据的承载和传送，尽量避免了带宽浪费，有效地节约了带宽资源。该方法中，获取第一小颗粒业务的第一业务数据，并向第二通信装置发送第一小颗粒单元基帧开销，第一小颗粒单元基帧开销承载第一业务数据。

Description

一种数据传输的方法以及相关装置
本申请要求于2021年12月13日提交的申请号为CN202111519430.0、发明名称为“一种数据传输的方法以及相关装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域，具体涉及一种数据传输的方法以及相关装置。
背景技术
灵活以太网(flex ethernet，FlexE)技术是实现业务隔离和网络分片的一种接口技术，近几年发展迅速，被各大标准组织广泛接纳。FlexE技术通过在IEEE802.3基础上引入灵活以太网协议层(英文也可以称之为FlexE Shim层)，实现媒体访问控制(medium access control，MAC)层与物理链路接口层(physical，PHY)的解耦，从而实现灵活的速率匹配。Flex Shim基于时分复用(time division multiplexing，TDM)分发机制，将多个FlexE客户(client)的数据按照时隙方式调度并分发至多个不同的子通道，实现传输管道带宽的硬隔离，一个业务数据流可以分配到一个或多个时隙(slot)中，实现了对各种速率业务的匹配。
现有FlexE接口技术在一定程度上解决了以太网端口速率固定不变的问题，Client交叉技术解决了分组转发时延太大的问题。但是，现有FlexE接口技术基于子时隙(sub-slot)承载小颗粒业务(例如速率小于或等于10Mbps)的业务数据时，存在较为严重的通道带宽浪费。
发明内容
本申请实施例提供了一种数据传输的方法以及相关装置，解决当前FlexE技术中基于子时隙进行业务承载时，带宽浪费较为严重的问题。
第一方面，本申请实施例提供了一种数据传输的方法，该方法应用于第一通信装置中。第一通信装置可以是中间节点，也可以是边缘节点，此处不做限定。在该方法中，获取第一小颗粒业务的第一业务数据，并向第二通信装置发送第一小颗粒单元基帧开销，所述第一小颗粒单元基帧开销承载所述第一业务数据。在本申请实施例中，通过小颗粒单元基帧开销承载第一小颗粒业务的第一业务数据，无需占用额外的sub-slot来传输该第一业务数据，即可完成对小颗粒业务的业务数据的承载和传送，尽量避免了带宽浪费，有效地节约了带宽资源。
在一些可能的实施方式中，第一通信装置还可以向第二通信装置发送小颗粒单元基帧净荷，所述小颗粒单元基帧净荷用于承载第二小颗粒业务的第二业务数据，所述第一小颗粒业务与所述第二小颗粒业务不相同。
在另一些可能的实施方式中，所述第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，所述第一GCC字段用于承载所述第一业务数据。
在另一些可能的实施方式中，所述第一GCC字段包括至少一个字节。因此，第一GCC字段的至少一个字节被指定用于承载所述第一业务数据。
在另一些可能的实施方式中，在发送所述第一小颗粒单元基帧开销之前，该方法还包括：根据第一映射关系将所述第一业务数据映射到所述至少一个字节,所述第一映射关系指示所述至少一个字节和第一客户client之间的映射关系,所述第一client与所述第一颗粒业务对应。通过上述方式，将第一业务数据映射在字节中，既增加了数据映射的方式，也能够通过一个或多个字节承载需要占用不同带宽的第一业务数据。
在另一些可能的实施方式中，向第二通信装置发送第一小颗粒单元基帧开销，包括：向所述第二通信装置发送小颗粒单元复帧，所述小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧。其中，所述第一小颗粒单元基帧包括所述第一小颗粒单元基帧开销，所述第二小颗粒单元基帧包括第二小颗粒单元基帧开销。所述第一小颗粒单元基帧开销的所述第一GCC字段和所述第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，所述第一GCC码块被指定用于承载所述第一小颗粒业务。
在另一些可能的实施方式中，在发送小颗粒单元复帧之前，第一通信装置还可以根据第二映射关系将第一业务数据映射到第一GCC码块。其中，第二映射关系指示第一GCC码块和第一client之间的映射关系，第一client与第一小颗粒业务对应。
在另一些可能的实施方式中，所述第一映射关系包括第一客户标识client ID和字节标识之间的映射关系，其中，所述第一client ID用于标识所述第一client，所述字节标识用于标识所述至少一个字节。
在另一些可能的实施方式中，所述第二映射关系包括第一client ID和码块标识之间的映射关系，其中，所述第一client ID用于标识所述第一client，所述码块标识用于标识所述至少一个码块，所述至少一个码块包括所述第一GCC码块。
在另一些可能的实施方式中，该方法还包括：获取第一配置信息，所述第一配置信息包括所述第一映射关系或第二映射关系。
在另一些可能的实施方式中，向第二通信装置发送小颗粒单元基帧净荷之前，第一通信装置还可以根据第三映射关系，将第二业务数据映射到小颗粒单元基帧净荷的至少一个子时隙。其中，所描述的第三映射关系指示第二客户client和至少一个子时隙之间的映射关系，第二client与第二小颗粒业务对应。
第二方面，本申请实施例提供了另一种数据传输的方法，该方法应用于第二通信装置中。在该方法中，接收第一通信装置发送的第一小颗粒单元基帧开销，所述第一小颗粒单元基帧开销用于承载第一小颗粒业务的第一业务数据；并对所述第一小颗粒单元基帧开销进行处理。
在一些可能的实施方式中，第二通信装置还可以接收第一通信装置发送的小颗粒单元基帧净荷，所述小颗粒单元基帧净荷承载第二小颗粒业务的第二业务数据，所述第一小颗粒业务与所述第二小颗粒业务不相同。
在另一些可能的实施方式中，所述第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，所述第一GCC字段承载所述第一业务数据。
在另一些可能的实施方式中，所述第一GCC字段的至少一个字节被指定用于承载所述第 一小颗粒业务。
在另一些可能的实施方式中，所述接收第一通信装置发送的第一小颗粒单元基帧开销，包括：接收所述第一通信装置发送的小颗粒单元复帧，所述小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧。其中，所述第一小颗粒单元基帧包括所述第一小颗粒单元基帧开销，所述第二小颗粒单元基帧包括第二小颗粒单元基帧开销。所述第一小颗粒单元基帧开销的所述第一GCC字段和所述第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，所述第一GCC码块被指定用于承载所述第一小颗粒业务。
在另一些可能的实施方式中，所述对所述第一小颗粒单元基帧开销进行处理，包括：将所述第一业务数据从第一client交换在第二client，其中，所述第一client与所述第一小颗粒业务对应，所述第二client与所述第一小颗粒业务对应。
在另一些可能的实施方式中，将所述第一业务数据从第一client交换在第二client，包括：基于第一映射关系，从所述第一GCC字段提取所述第一业务数据，所述第一映射关系指示所述第一client与所述第一GCC字段之间的映射关系；基于第二映射关系，将所述第一业务数据映射到第三GCC字段，所述第二映射关系指示所述第二client与所述第三GCC字段之间的映射关系。
在另一些可能的实施方式中，所述第一映射关系包括所述第一GCC字段的至少一个字节与所述第一client之间的映射关系。
在另一些可能的实施方式中，所述第一映射关系包括第一GCC码块与所述第一client之间的映射关系，所述第一GCC码块由所述第一GCC字段和第二GCC字段组成，所述第二GCC字段包含在第二小颗粒单元基帧开销中，所述第一小颗粒单元基帧开销包括在第一小颗粒单元基帧中，所述第二小颗粒单元基帧开销包括在第二小颗粒单元基帧中，所述第一小颗粒单元基帧和所述第二小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
在另一些可能的实施方式中，所述第二映射关系包括所述第三GCC字段的至少一个字节与所述第二client之间的映射关系。
在另一些可能的实施方式中，所述第二映射关系包括第二GCC码块与所述第二client之间的映射关系。其中，所述第二GCC码块由所述第三GCC字段和第四GCC字段组成，所述第三GCC字段包含在所述第二通信装置向第三通信装置发送的第三小颗粒单元基帧开销中，所述第四GCC字段包含在所述第二通信装置向第三通信装置发送的第四小颗粒单元基帧开销中，所述第三小颗粒单元基帧和所述第四小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
在另一些可能的实施方式中，所述对所述第一小颗粒单元基帧开销进行处理，包括：透传所述第一小颗粒单元基帧开销。
在另一些可能的实施方式中，所述方法还包括：获取第一配置信息，所述第一配置信息包括所述第一映射关系或所述第二映射关系。
在另一些可能的实施方式中，所述对所述第一小颗粒单元基帧开销进行处理，包括：从所述一小颗粒单元基帧开销提取出所述第一业务数据；对所述第一业务数据进行二层或三层处理。
第三方面，本申请实施例提供了一种第一通信装置。该第一通信装置包括获取单元和发送单元。其中，获取单元，用于获取第一小颗粒业务的第一业务数据。发送单元用于向第二通信装置发送第一小颗粒单元基帧开销，所述第一小颗粒单元基帧开销承载所述第一业务数据。
在一些可能的实施方式中，所述发送单元还用于向所述第二通信装置发送小颗粒单元基帧净荷，所述小颗粒单元基帧净荷用于承载第二小颗粒业务的业务数据，所述第一小颗粒业务与所述第二小颗粒业务不相同。
在另一些可能的实施方式中，所述第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，所述第一GCC字段用于承载所述第一业务数据。
在另一些可能的实施方式中，所述第一GCC字段中的至少一个字节被指定用于承载所述第一小颗粒业务。
在另一些可能的实施方式中，所述第一通信装置还包括第一处理单元。该第一处理单元用于在发送所述第一小颗粒单元基帧开销之前，根据第一映射关系将所述第一业务数据映射到所述至少一个字节。需说明，所述第一映射关系指示所述至少一个字节和第一客户client之间的映射关系，所述第一client与所述第一颗粒业务对应。
在另一些可能的实施方式中，所述第一映射关系包括第一客户标识client ID和字节标识之间的映射关系，其中，所述第一client ID用于标识所述第一client，所述字节标识用于标识所述至少一个字节。
在另一些可能的实施方式中，发送单元用于向第二通信装置发送小颗粒单元复帧，所述小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧。其中，所述第一小颗粒单元基帧包括所述第一小颗粒单元基帧开销，所述第二小颗粒单元基帧包括第二小颗粒单元基帧开销。所述第一小颗粒单元基帧开销的所述第一GCC字段和所述第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，所述第一GCC码块被指定用于承载所述第一小颗粒业务。
在另一些可能的实施方式中，所述第一通信装置还包括第二处理单元。该第二处理单元用于在发送所述小颗粒单元复帧之前，根据第二映射关系将所述第一业务数据映射到所述至少一个码块，其中，所述第二映射关系指示所述至少一个码块和第一客户client之间的映射关系，所述第一client与所述第一小颗粒业务对应。
在另一些可能的实施方式中，所述第二映射关系包括第一client ID和码块标识之间的映射关系。其中，所述第一client ID用于标识所述第一client，所述码块标识用于标识所述至少一个码块，所述至少一个码块包括所述第一GCC码块。
在另一些可能的实施方式中，所述获取单元还用于获取第一配置信息，所述第一配置信息包括所述第一映射关系或第二映射关系。
在另一些可能的实施方式中，所述第一通信装置还包括第三处理单元。该第三处理单元用于在向所述第二通信装置发送小颗粒单元基帧净荷之前，根据第三映射关系将所述第二业务数据映射到所述小颗粒单元基帧净荷的至少一个子时隙。其中，所述第三映射关系指示第二客户client和所述至少一个子时隙之间的映射关系，所述第二client与所述第二 小颗粒业务对应。
第四方面，本申请实施例提供了一种第二通信装置。该第二通信装置包括获取单元和处理单元。其中，获取单元，用于接收第一通信装置发送的第一小颗粒单元基帧开销，所述第一小颗粒单元基帧开销用于承载第一小颗粒业务的第一业务数据。第二处理单元，用于对所述第一小颗粒单元基帧开销进行处理。
在另一些可能的实施方式中，所述获取单元还用于：接收所述第一通信装置发送的小颗粒单元基帧净荷，所述小颗粒单元基帧净荷承载第二小颗粒业务的第二业务数据，所述第一小颗粒业务与所述第二小颗粒业务不相同。
在另一些可能的实施方式中，所述第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，所述第一GCC字段承载所述第一业务数据。
在另一些可能的实施方式中，所述第一GCC字段的至少一个字节被指定用于承载所述第一小颗粒业务。
在另一些可能的实施方式中，所述获取单元用于：接收所述第一通信装置发送的小颗粒单元复帧，所述小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧，所述第一小颗粒单元基帧包括所述第一小颗粒单元基帧开销，所述第二小颗粒单元基帧包括第二小颗粒单元基帧开销，所述第一小颗粒单元基帧开销的所述第一GCC字段和所述第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，所述第一GCC码块被指定用于承载所述第一小颗粒业务。
在另一些可能的实施方式中，所述处理单元用于：将所述第一业务数据从第一client交换在第二client，其中，所述第一client与所述第一小颗粒业务对应，所述第二client与所述第一小颗粒业务对应。
在另一些可能的实施方式中，所述处理单元用于：基于第一映射关系，从所述第一GCC字段提取所述第一业务数据，所述第一映射关系指示所述第一client与所述第一GCC字段之间的映射关系；基于第二映射关系，将所述第一业务数据映射到第三GCC字段，所述第二映射关系指示所述第二client与所述第三GCC字段之间的映射关系。
在另一些可能的实施方式中，所述第一映射关系包括所述第一GCC字段的至少一个字节与所述第一client之间的映射关系。
在另一些可能的实施方式中，所述第一映射关系包括第一GCC码块与所述第一client之间的映射关系，所述第一GCC码块由所述第一GCC字段和第二GCC字段组成，所述第二GCC字段包含在第二小颗粒单元基帧开销中，所述第一小颗粒单元基帧开销包括在第一小颗粒单元基帧中，所述第二小颗粒单元基帧开销包括在第二小颗粒单元基帧中，所述第一小颗粒单元基帧和所述第二小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
在另一些可能的实施方式中，所述第二映射关系包括所述第三GCC字段的至少一个字节与所述第二client之间的映射关系。
在另一些可能的实施方式中，所述第二映射关系包括第二GCC码块与所述第二client之间的映射关系。其中，所述第二GCC码块由所述第三GCC字段和第四GCC字段组成，所述第 三GCC字段包含在所述第二通信装置向第三通信装置发送的第三小颗粒单元基帧开销中，所述第四GCC字段包含在所述第二通信装置向第三通信装置发送的第四小颗粒单元基帧开销中，所述第三小颗粒单元基帧和所述第四小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
在另一些可能的实施方式中，所述处理单元用于透传所述第一小颗粒单元基帧开销。
在另一些可能的实施方式中，所述获取单元还用于获取第一配置信息，所述第一配置信息包括所述第一映射关系或所述第二映射关系。
在另一些可能的实施方式中，所述处理单元用于：从所述第一小颗粒单元基帧开销提取出所述第一业务数据；对所述第一业务数据进行二层或三层处理。
在另一些可能的实施方式中，所述第二通信装置还包括发送模块；所述发送模块用于转发所述第一业务数据。
第五方面，本申请实施例提供了一种数据帧结构。该数据帧结构包括小颗粒单元基帧开销和小颗粒单元基帧净荷。所述小颗粒单元基帧开销包括第一字段，所述第一字段用于承载第一小颗粒业务的第一业务数据，所述小颗粒单元基帧净荷用于承载第二小颗粒业务的第二业务数据，所述第一小颗粒业务与所述第二小颗粒业务不相同。
在一些可能的实施方式中，所述小颗粒单元基帧开销还包括第二字段，所述第二字段用于承载所述数据帧结构的版本号。
在另一些可能的实施方式中，所述开销字段还包括第三字段，所述第三字段用于承载所述第一小颗粒业务的业务类型。
在另一些可能的实施方式中，所述开销字段还包括第四字段，所述第四字段用于承载时钟频率信息。
在另一些可能的实施方式中，所述小颗粒单元基帧开销还包括第五字段，所述第五字段用于承载预留字段。
在另一些可能的实施方式中，所述小颗粒单元基帧开销还包括第六字段，所述第六字段用于承载开销校验信息。
在另一些可能的实施方式中，所述小颗粒单元基帧开销还包括第七字段，所述第七字段用于承载序列号。
第六方面，本申请实施例提供了一种通信***。该通信***包括第一通信装置和第二通信装置。需说明，第一通信装置用于执行上述第一方面以及任一种可选的实施方式中所述的方法。第二通信装置用于执行上述第二方面以及任一种可选的实施方式中所述的方法。另外，第一通信装置可以参照上述第三方面所描述的任一第一通信装置进行理解，第二通信装置可以参照上述第四方面所描述的任一第二通信装置进行理解，此处不做赘述。
第七方面，本申请实施例提供了一种计算机可读存储介质，包括程序或指令，当其在计算机上运行时，使得计算机执行如第一方面、第一方面任意一种，或者第二方面、第二方面任意一种可能实现方式的方法。
第八方面，本申请实施例提供了一种包含指令的计算机程序产品，当其在计算机上运 行时，使得计算机执行如第一方面、第一方面任意一种，或者第二方面、第二方面任意一种可能实现方式的方法。
本申请第九方面提供一种芯片***，该芯片***可以包括处理器，用于支持第一通信装置实现上述第一方面、或者第一方面任意一种可能的实施方式中所描述的方法中所涉及的功能；或者，支持第二通信装置实现上述第二方面、或者第二方面任意一种可能的实施方式中所描述的方法中所涉及的功能。
可选地，结合上述第九方面，在第一种可能的实施方式中，芯片***还可以包括存储器，存储器，用于保存第一通信装置或者第二通信装置必要的程序指令和数据。该芯片***，可以由芯片构成，也可以包含芯片和其他分立器件。其中，芯片***可以包括专用集成电路(application specific integrated circuit，ASIC)、现成可编程门阵列(field programmable gate array，FPGA)或者其他可编程逻辑器件等。进一步，芯片***还可以包括接口电路等。
从以上技术方案可以看出，本申请实施例具有以下优点：
本申请实施例中，通过小颗粒单元基帧开销承载第一小颗粒业务的第一业务数据，无需占用额外的sub-slot来传输该第一业务数据，即可完成对小颗粒业务的业务数据的承载和传送，尽量避免了带宽浪费，有效地节约了带宽资源。
附图说明
为了更清楚地说明本申请实施例的技术方案，下面将对实施例描述中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本申请的一些实施例。
图1示出了基于灵活以太网协议的FlexE通用架构示意图；
图2示出了一种小颗粒单元基帧结构的示意图；
图3示出一种小颗粒单元复帧结构的示意图；
图4A示出了一种小颗粒单元基帧开销的开销格式示意图；
图4B示出了一种小颗粒单元基帧开销的另一种开销格式的示意图；
图4C示出了一种小颗粒单元基帧开销的另一种开销格式的示意图；
图5示出了本申请实施例中将数据承载于GCC字段的示意图；
图6示出了本申请实施例中一个小颗粒单元复帧周期内的GCC开销情况的示意图；
图7示出了一种混合组网的场景示意图；
图8示出了一种***架构的示意图；
图9示出了本申请实施例提供了一种数据传输的方法流程示意图；
图10示出了本申请实施例中提供的一种映射示意图；
图11A示出了本申请实施例中提供的GCC码块的配置示意图；
图11B示出了本申请实施例中提供的另一种映射示意图；
图12示出了本申请实施例中提供的第一业务数据在client中交换的示意图；
图13示出了本申请实施例提供的一种通信装置的结构示意图；
图14示出了本申请实施例提供的另一种通信装置的结构示意图；
图15示出了本申请实施例提供的另一种通信装置的结构示意图；
图16示出了本申请实施例提供的另一种通信装置的结构示意图；
图17A示出了本申请实施例提供的一种第一通信装置的结构示意图；
图17B示出了本申请实施例提供的另一种第一通信装置的结构示意图；
图17C示出了本申请实施例提供的另一种第一通信装置的结构示意图；
图17D示出了本申请实施例提供的另一种第一通信装置的结构示；
图18示出了本申请实施例提供的另一种第二通信装置的结构示意图。
具体实施方式
本申请实施例提供了一种数据传输的方法以及相关装置，解决当前FlexE技术中基于子时隙进行业务承载时，带宽浪费较为严重的问题。
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”、“第三”、“第四”等(如果存在)是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便这里描述的本申请的实施例如能够以除了在这里图示或描述的那些以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含。在本申请中，“至少一个”是指一个或者多个，“多个”是指两个或两个以上。“和/或”，描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B的情况，其中A，B可以是单数或者复数。字符“/”一般表示前后关联对象是一种“或”的关系。“以下至少一项(个)”或其类似表达，是指的这些项中的任意组合，包括单项(个)或复数项(个)的任意组合。例如，a，b或c中的至少一项(个)，可以表示：a，b，c，a和b，a和c，b和c或a和b和c，其中a、b和c可以是单个，也可以是多个。值得注意的是，“至少一项(个)”还可以解释成“一项(个)或多项(个)”。
光互联网论坛(optical internet forum，OIF)发布了FlexE标准，本申请所涉及的相关FlexE的现有技术可以参见OIF所制定的FlexE标准IA OIF-FLEXE-01.0，IA OIF-FLEXE-02.0或者IA OIF-FLEXE02.1的相关说明，上述标准以全文引用的方式并入本申请中。另外，在本申请中，以太网接口和以太接口经常交替使用，灵活以太接口和灵活以太网接口经常交替使用。
图1示出了基于灵活以太网协议的FlexE通用架构示意图。如图1所示，灵活以太网协议组(flex ethernet group，FlexE Group)包括4个PHY。FlexE Client可以表示出在FlexE Group的一个时隙或多个时隙上传输的客户数据流。一个FlexE Group上可承载多个FlexE Client，一个FlexE Client可对应一个到多个客户的业务数据流(也可以称为MAC Client)，FlexE Shim层提供FlexE Client到MAC Client的数据适配和转换。FlexE可以支持任意多个不同FlexE Client在任意一组PHY上的映射和传输，从而实现PHY捆绑、通道化及子速率等功能。多路PHY可以组合成一个FlexE Group，用于承载通过FlexE Shim 层分发、映射来的一路或者多路FlexE client数据流。以100GE PHY为例，FlexE Shim层可以把FlexE Group中的每个100GE PHY划分为20个时隙(slot)的数据承载通道，每个slot对应的带宽为5Gbps。
在切片分组网(slicing packet network，SPN)通道层或城域传送网(metro transport network，MTN)通道层技术已经形成了ITU-T系列标准，并且ITU-T标准G.8310和标准G.8312规范了SPN通道层的带宽粒度为5Gbps。在小颗粒单元(fine granularity unit，FGU)中，对SPN通道层的带宽粒度5Gbps作了进一步的时隙划分及复用，形成带宽粒度为10Mbps的小颗粒通道。SPN通道层位于标准IEEE 802.3的物理编码子层(physical coding sublayer，PCS)层，其编码方式采用了PCS层中的64bits转码成66bits(后续称为64B/66B)的编码格式。在本申请中，FGU也可以称为小颗粒基帧、小颗粒单元基帧、基本单元帧或者单帧，小颗粒也可以称之为细颗粒，后续仅使用小颗粒单元基帧为例进行说明。小颗粒单元基帧采用了与SPN通道层相应的64B/66B的编码格式，对小颗粒单元基帧开销(overhead，OH)和包含多个时隙的小颗粒单元基帧净荷进行编码，并将编码后的小颗粒单元基帧开销和小颗粒单元基帧净荷封装到固定长度的码块序列中。图2示出了一种小颗粒单元基帧结构的示意图。如图2所示，为兼容IEEE802.3定义的以太网帧格式，该小颗粒单元基帧采用1个S码块、195个D码块以及1个T码块进行封装。其中，S码块用于指示小颗粒单元基帧的帧头。D码块的数据字段(如图2示出的Block payload域)用于承载小颗粒单元基帧净荷。T码块能够用于指示该小颗粒单元基帧的帧尾。一个码块包含8字节，该小颗粒单元基帧的195个D码块和1个T码块共同承载了1567字节的数据内容，包含了7字节的小颗粒单元基帧开销和1560字节的小颗粒单元基帧净荷。小颗粒单元基帧净荷被划分为相同大小的24个子时隙(sub-slot)，图中分别用sub-slot 1至sub-slot 24来表示。每个子时隙为65字节，可以承载8个65bits的码块。业务数据经过66B到65B的压缩转码后，被填充到子时隙净荷中。
另外，通过复帧方式对SPN通道层的带宽粒度5Gbps进行时隙划分，具体可以参照图3示出的小颗粒单元复帧结构的示意图进行理解。如图3所示，在带宽粒度为5Gbps的FlexE Client接口或普通ETH接口，其在时域上可以划分为480个子时隙进行循环传输。即在一个FlexE client接口的每个时隙调度周期(480个子时隙为一个时隙调度周期)内，平均分布20个小颗粒单元基帧(如：小颗粒单元基帧1至小颗粒单元基帧20)，即一个小颗粒单元复帧。每个小颗粒单元基帧包含24个子时隙。一个具体的实施例中，每个子时隙净荷可以包含8个66B的压缩码块，对于一个小颗粒单元基帧来说，加上S码块、小颗粒单元基帧开销对应的码块(图中视为OH)以及T码块进行封装，一个小颗粒单元基帧内可以包含197个66B码块。其中，为了速率适配，可以在小颗粒单元基帧之间增加I码块，也可以将部分I码块替换FlxeE client接口中传输的OAM码块。I码块即空闲(idle)码块，用作MAC层速率适配。在一个具体的实施方式中，根据传输以太网报文的规定，复帧长度应小于等于9600字节。应理解，上述图3中仅仅以480个子时隙、20个小颗粒单元基帧作为一个小颗粒单元复帧为例说明带宽粒度为5Gbps的FlexE client接口。在实际应用中，对于不同带宽的FlexE client接口，其在时域上划分的子时隙个数也可以不同，具体可以 灵活配置。
图4A示出了一种小颗粒单元基帧开销的开销格式示意图。从图4A可以看出，每个小颗粒单元基帧包含了7字节的小颗粒单元基帧开销，即56bits的小颗粒单元基帧开销。该小颗粒单元基帧开销包括6bits的复帧指示(multiframe indicator，MFI)、2bits的Flag、2bits的RES和44bits的开销信息(OH information)。其中，在开销信息中可以至少包含以下内容：S比特位、C比特位、变更请求(change request，CR)比特位、变更应答(change answer，CA)比特位、通用通信信道(general communication channel，GCC)字段、客户标识(client identifier，client ID)、子时隙标识(sub-slot identifier，sub-slot ID)以及循环冗余码校验(cyclic redundancy check，CRC)字段等。上述的S比特位用于承载时隙增大调整通告信息，C比特位用于承载时隙生效指示信息，CR比特位用于承载时隙调整应答信息，CRC字段用于承载循环冗余码校验信息。在Flag区的取值不同时，表明相应的比特位置可以提供给不同的通道使用。
示例性地，在一些可能的示例中，当Flag的取值为11时，CA比特位之后相应的比特位置可以***GCC字段，指示出该GCC字段所占用的比特位置提供给GCC通道使用，具体可以参照图4B示出的小颗粒单元基帧开销的另一种开销格式的示意图进行理解。在另一些可能的实施方式中，当Flag的取值为00时，代表CA比特位之后相应的比特位置可以提供给client ID和sub-slot ID使用，具体可以参照图4C示出的小颗粒单元基帧开销的另一种开销格式的示意图进行理解。
上述所提及一个小颗粒单元基帧中的小颗粒单元基帧开销中的GCC字段为一个33B长度的字段，用于指示通过对应的GCC通道传输数据。通过GCC通道传输信息采用以太网分组格式并沿用IEEE 802.3中的64B/66B编码格式。图5示出了本申请实施例中将数据承载于GCC字段的示意图。如图5所示，经过64B/66B编码后的数据，将数据前33bits(第0～32位，包含同步头)和后33bits先后承载于GCC字段中，并按照先后承载的顺序在GCC通道中传输。也就是理解成，在一个小颗粒单元复帧中，使用偶数的复帧指示(即MFI＝n，n为偶数)的小颗粒单元基帧发送前33bits，在奇数复帧指示(即MFI＝n+1，)的小颗粒单元基帧中发后33bits。图6示出了本申请实施例中一个复帧周期内的GCC开销情况的示意图。如图6所示，在一个复帧周期内，在带宽粒度为5Gbps的MTN接口上可以传输10个64B/66B的码块。一个复帧周期内GCC通道的有效带宽是64bit*10/50.688us＝12.6Mbps。以此类推，一个10Gbps带宽MTN接口上，在一个复帧周期内可以传输20个64B/66B的码块，相应的GCC通道的有效带宽为12.6*2＝25.2Mbps。
应理解，上述所提及的GCC通道，主要用于管理信息、控制面协议、链路自动发现和1588v2时间协议报文等传送。另外，通过GCC通道传输信息时主要是采用以太网帧或者以太网包的格式进行传送，组网的网元逐跳发送和接收管控信息且需要协议层参与处理。
在采用上述提及的FlexE技术进行业务传输时，不免存在多个运营商的通信设备处于混合组网对接的场景。图7示出了一种混合组网的场景示意图。如图7所示，运营商A的设备穿越由运营商B中的设备组成的网络时，该运营商B的网络要和运营商A的网络互连，并且运营商A中的控制器需要穿越运营商B中的网络，才可以实现对远端的运营商A的设备进行管理和 控制。然而，在该混合组网中，需要在运营商A的网络中，部署带宽粒度为sub-slot(带宽粒度例如可以约为10Mbps)传递运营商B中的小颗粒业务的业务数据，以及管理信息和控制信息。在采用混合组网进行业务承载时，会遇到各种各样的10Mbps带宽的小颗粒业务，例如：准同步数字序列(plesiochronous digital hierarchy，PDH)业务、同步数字序列(synchronous digital hierarchy，SDH)业务、以太网(ethernet，ETH)业务或者网际互连协议(internet protocol，IP)业务等，也可能还存在更小带宽(例如小于10Mbps，甚至只有几十Kbps带宽)的业务，例如公务电话、SDH帧中的个别开段销字节(如F1、E1、D1-D3、J0等再生段开销(regenerator section overhead，RSOH)、K1、K2、D4-12、E2、S1等复用段开销(multiplex section overhead，MSOH)等。若使用一个sub-slot来传输一些小于10Mbps的小颗粒业务的业务数据，或者传输第三方设备跨越网络时的管理信息和控制信息时难免会造成该sub-slot的带宽资源的浪费，无法精准的匹配业务需求。
为了解决上述技术问题，本申请实施例在现有FlexE接口或者普通以太网物理接口的基础上，重新定义了一种新的数据帧结构。即该数据帧结构也可以称为小颗粒单元基帧，用于承载不同小颗粒业务对应的client的业务数据流。在本申请中，每个小颗粒单元基帧包括小颗粒单元基帧开销和小颗粒单元基帧净荷。在本申请中，采用前述所描述的GCC字段来传输小颗粒业务的业务数据(即后续所描述的第一业务数据)，可以有两种可能的传输方式。其中，一种方式是将第一业务数据先映射到该小颗粒单元基帧净荷中，然后将整个小颗粒单元基帧通过小颗粒单元基帧开销的GCC字段中的指定的一个或多个码块进行传输。另一种方式是将第一业务数据映射到小颗粒单元基帧开销的GCC字段的一个或多个字节、或者由多个相邻的小颗粒单元基帧开销中的GCC字段组成的一个或多个GCC码块中进行传输。具体地，其中，小颗粒单元基帧开销包括第一字段，第一字段用于承载第一小颗粒业务的第一业务数据。小颗粒单元基帧净荷用于承载第二小颗粒业务的业务数据，第一小颗粒业务与第二小颗粒业务不相同。该小颗粒单元基帧开销还可以包括其他的字段，用于承载不同的内容，作为一个示例，可以结合下述表1进行理解。
表1
Figure PCTCN2022132712-appb-000001
通过该数据帧结构中的小颗粒单元基帧开销可以传递第一小颗粒业务的第一业务数据，无需占用额外的sub-slot来传输该第一业务数据，尽量避免了带宽浪费。需说明，所描述的第一字段可以是前述所描述的GCC字段，此处不做限定说明。
基于此，本申请实施例提供了一种数据传输的方法，该方法可以应用于图8示出的***架构的应用场景中。如图8所示，该***架构可以包括网络设备1、网络设备2、用户设备1和用户设备2。网络设备1可以是中间节点，此时网络设备1通过其他网络设备与用户设备1连接。网络设备1可以是边缘节点，此时网络设备1直接与用户设备1连接。网络设备2可以是中间节点，此时网络设备2通过其他网络设备与用户设备2连接。网络设备2也可以是边缘节点，此时网络设备2直接与用户设备2连接。网络设备1包括FlexE接口1，网络设备2包括FlexE接口2。FlexE接口1与FlexE接口2相连。每个FlexE接口均包括发送端口和接收端口，与传统以太网接口的区别在于一个FlexE接口可以承载多个client，且作为逻辑接口的FlexE接口可以由多个物理接口组合而成。图8中所示的正向通道中业务数据的流向如图8中实线箭头所示，反向通道中业务数据的流向如图8中虚线箭头所示。本申请实施例的传输通道以正向通道为例，传输通道中业务数据的流向为用户设备1->网络设备1->网络设备2->用户设备2。
应理解，图8中仅示例性的示出了2个网络设备和2个用户设备，该***结构还可以包括任意其它数量的网络设备和用户设备，本申请实施例对此不做限定。图8中所示的***架构仅是举例说明，本申请提供的***架构的应用场景不限于图8所示的场景。本申请提供的技术方案适用于所有应用FlexE技术进行数据传输的网络场景。
为了便于理解，图9为本申请实施例提供了一种数据传输的方法流程示意图。如图9所示，该数据传输的方法可以包括如下步骤：
901、第一通信装置获取第一小颗粒业务的第一业务数据。
在一个具体的实施方式中，第一小颗粒业务例如可以是带宽小于GCC通道的带宽的业务。所描述的GCC通道的带宽，可以参照前述图6中所描述的内容进行理解，此处不做赘述。另外，第一小颗粒业务可以包括但不限于PDH业务、SDH业务、ETH业务、IP业务、公务电话、SDH帧中的个别开段销字节等。
上述提及的第一通信装置可以为边缘节点，也可以为中间节点，在本申请实施例中不做限定说明。在该第一通信装置为中间节点时，可以不执行后续步骤S01～S04中提及的开销交叉相关的操作，而是可以从上一跳的节点发送的数据块中解映射出该第一业务数据，并重新封装该第一业务数据。
902、第一通信装置向第二通信装置发送第一小颗粒单元基帧开销，第一小颗粒单元基帧开销承载第一业务数据。
在该示例中，第一通信装置在获取到第一小颗粒业务的第一业务数据后，可以将该第一业务数据映射到第一小颗粒单元基帧开销中，由该第一小颗粒单元基帧开销承载该第一业务数据。这样，第一通信装置通过FlexE接口，向第二通信装置发送该第一小颗粒单元基帧开销。在一中具体的实现方式中，第一通信装置也可以向第二通信装置发送多个第一数据块，该多个第一数据块中包括该第一小颗粒单元基帧开销。
需说明，所描述的第一小颗粒单元基帧开销可以参照前述图4A至图6中所描述的小颗粒单元基帧开销的内容进行理解，此处不做赘述。
在一些可能的实施方式中，一个小颗粒单元复帧中，可以包括第一小颗粒单元基帧。 举例来说，第一小颗粒单元基帧可以是前述图3中示出的小颗粒单元基帧1，也可以是小颗粒单元基帧2等等，此处不做限定说明。在该第一小颗粒单元基帧中，可以包括第一小颗粒单元基帧开销。而且该第一小颗粒单元基帧开销可以包括第一GCC字段，该第一GCC字段可以用于承载第一业务数据。
需说明，在一种具体的实现方式中，每个小颗粒单元基帧中的小颗粒单元基帧开销所包含的GCC字段是一个33B长度的字段，能够指示通过GCC通道来传输管理信息或者控制信息等数据。因此，在一个小颗粒单元复帧中可以包含N个小颗粒单元基帧的情况下，该小颗粒单元复帧可以包括M个66B的GCC字段，其中M＝N/2。因此，在GCC字段的带宽还有剩余的时候，还可以用来承载第一小颗粒业务的第一业务数据，使得该第一业务数据不占用子时隙的带宽资源。例如说，管理信息和控制信息占用8bit的情况下，可以将GCC字段剩余的25bit用来承载第一业务数据。
在另一些可选的示例中，第一GCC字段包括至少一个字节。该第一GCC字段的至少一个字节被指定用于承载第一小颗粒业务。
或者，在一个小颗粒单元复帧中，还可以包括第二小颗粒单元基帧，第二小颗粒单元基帧与上述的第一小颗粒单元基帧相邻。譬如说，当第一小颗粒单元基帧可以为前述图3中示出的小颗粒单元基帧1时，该第二小颗粒单元基帧可以是小颗粒单元基帧2等；或者，或者，当第一小颗粒单元基帧可以为前述图3中示出的小颗粒单元基帧3时，该第二小颗粒单元基帧可以是小颗粒单元基帧2或者小颗粒单元基帧4等等，此处不做限定。此处不做限定说明。而且，第二小颗粒单元基帧包括第二小颗粒单元基帧开销。
这样，可以由第一GCC字段和第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，第一GCC码块被指定用于承载第一小颗粒业务。
在另一些可选的示例中，第一小颗粒业务与第一client对应，而且第一client包括第一业务数据。可以通过字节与第一client间的对应关系，将第一小颗粒业务承载在字节中，进而实现将第一业务数据承载在字节中传输。或者，也可以通过码块与第一client间的对应关系，将第一小颗粒业务承载在码块中，进而实现将第一业务数据承载在码块中传输。下面将分别从不同的示例中描述如何将第一业务数据映射到字节或码块中。
(1)将第一业务数据映射到字节
在一些可选的实施方式中，在发送第一小颗粒单元基帧开销之前，还可以根据第一映射关系将第一业务数据映射到至少一个字节,第一映射关系指示至少一个字节和第一客户client之间的映射关系，第一client与第一小颗粒业务对应。
在该示例中，由于第一GCC字段包括至少一个字节，那么控制管理设备可以将第一GCC字段的至少一个字节和第一client配置对应关系，得到映射关系1。然后，控制管理设备例如通过配置信息A的方式将映射关系1发送到第一通信装置。或者，也可以由第一通信装置主动地从该控制管理设备中获取配置信息A。或者，第一通信装置在本地也存储有该配置信息A，从本地中获取该配置信息A。具体本申请中不限定获取映射关系1的方式。
这样，在第一通信装置获取到配置信息A后，可以得到其中包括的映射关系1。而且，由于第一小颗粒业务与第一client对应，第一client可以包括第一业务数据，那么第一 通信装置在获得映射关系1后，便可以基于该映射关系1能够将第一业务数据映射到第一GCC字段的至少一个字节中。
举例来说，图10为本申请实施例中提供的一种映射示意图。从图10可以看出，可以以8bits(即一个字节)为一个基础单位，将第一业务数据映射在32个字节的一个或多个字节中。示例性地，若第一业务数据占用的带宽小于一个字节的带宽，可以将第一业务数据承载在任意一个字节中；或者，若第一业务数据占用的带宽大于一个字节的带宽时，也可以使用多个字节捆绑在一起，共同承载该第一小颗粒业务。
需说明，所提及的映射关系1可以指示第一GCC字段的至少一个字节与第一client之间的映射关系。另外，该配置信息A还可以指示出该第一业务数据所占用第一GCC字段的字节位置和字节个数。
在另一些可能的实施方式中，第一映射关系(即上述的映射关系A)具体可以包括第一客户标识client ID和字节标识之间的映射关系。其中，第一client ID用于标识第一client，该第一client与第一小颗粒业务对应。字节标识用于标识至少一个字节。
在该示例中，可以是一个字节对应一个字节标识，也可以是多个字节对应同一个字节标识，本申请不做限定说明。另外，由于第一client ID可以标识出与第一小颗粒业务对应的第一client，并且第一client包括第一业务数据，字节标识也可以用来指示第一GCC字段的至少一个字节。通过配置第一client ID与字节标识之间的映射关系，使得第一通信装置能够获知需要将该第一业务数据指定映射在第一GCC字段的哪些字节中。
举例来说，在当前需要传输4个client的第一业务数据的情景中，分别对这4个client使用不同的client ID(如client ID 1至client ID 4)来标识，并且使用字节标识A1标识字节1、使用字节标识B1标识字节2～字节5、使用字节标识C1标识字节6～字节8、使用字节标识D1标识字节9等等。通过配置client ID 1与字节标识A1之间存在映射关系、client ID 2与字节标识B1之间存在映射关系、client ID 3与字节标识C1之间存在映射关系、以及client ID 4与字节标识D1之间存在映射关系等等。这样，便可以通过字节1承载该client ID 1所标识的client的第一业务数据，通过字节2～字节5承载该client ID 2所标识的client的第一业务数据，通过字节6～字节8承载client ID 3所标识的client的第一业务数据，以及通过字节9承载client ID 4所标识的client的第一业务数据。
(2)、将第一业务数据映射到码块
在一些可选的实施方式中，在发送第一小颗粒单元基帧开销之前，还可以根据第二映射关系将第一业务数据映射到第一GCC码块,第二映射关系指示第一GCC和第一客户client之间的映射关系，第一client与第一小颗粒业务对应。
在该示例中，第一GCC码块可以参照前述提及的内容进行理解，此处不做赘述。控制管理设备可以将第一GCC码块和第一client配置对应关系，得到映射关系2。然后，控制管理设备例如通过配置信息B的方式将映射关系2发送到第一通信装置。或者，也可以由第一通信装置主动地从该控制管理设备中获取配置信息B。或者，第一通信装置在本地也存储有该配置信息B，从本地中获取配置信息B。具体本申请中不限定获取配置信息B的方式。
需说明，配置信息B可以与配置信息A相同。也就是说，也可以在配置信息A中携带上述的映射关系1，或者，也可以在配置信息B中携带上述的映射关系2。另外，所提及的映射关系2可以指示第一GCC码块与第一client之间的映射关系。举例来说，映射关系2包括至少一个GCC码块与所述第一client之间的映射关系，所述至少一个GCC码块用于承载所述第一client对应的小颗粒业务。例如，所述至少一个GCC码块包括所述第一GCC码块，还可以包括第二GCC码块。该配置信息B还可以指示出所述第一client所对应的第一小颗粒业务所占用所有GCC码块的码块位置和码块个数。即根据该配置信息，可以确定第一GCC码块和第二GCC码块所在的码块位置。该第一配置信息包括第一映射关系或第二映射关系。
这样，在第一通信装置获取到配置信息B后，可以得到其中包括的映射关系2。而且，由于第一小颗粒业务与第一client对应，第一client可以包括第一业务数据，那么第一通信装置在获得映射关系2后，便可以基于该映射关系2能够将第一业务数据映射到第一GCC码块中。举例来说，图11A为本申请实施例中提供的GCC码块的配置示意图。从图11A可以看出，在带宽粒度为5Gbps的MTN接口中，在一个复帧周期内共有10个66B的GCC码块(如Block 0至Block 9)。其中，可以指定Block 0至Block 4这5个GCC码块承载设备之间的管理信息和控制面信息；也可以指定Block 5对应的GCC码块承载时间同步信息；也可以指定Block 6至Block 9这四个GCC码块承载第一小颗粒业务。应理解，上述图11A仅仅是一个示意性的描述，对于指定该第一GCC字段中的哪些字节，或者哪些小颗粒单元基帧开销中的GCC字段组成的GCC码块承载第一小颗粒业务，可以灵活地配置，本申请具体不做限定。
示例性地，图11B示出了本申请实施例中提供的另一种映射示意图。从图11B可以看出，可以直接按照一个码块作为基础单元，将第一业务数据映射在Block 6至Block 9这四个GCC码块的一个或多个码块中。示例性地，若第一业务数据占用的带宽小于一个GCC码块的带宽，可以将第一业务数据承载在任意一个GCC码块中；或者，若第一业务数据占用的带宽大于一个码块的带宽时，也可以使用多个GCC码块捆绑在一起，共同承载该第一业务数据。
应理解，图11B中示出的将第一业务数据映射在Block 6至Block 9中的一个或多个GCC码块仅仅是一个示意性的描述，具体本申请不做限定说明。
在另一些具体的实施方式中，第二映射关系可以包括第一用户标识client ID和码块标识之间的映射关系。其中，第一client ID用于标识第一client，该第一client包括与第一小颗粒业务对应，码块标识用于标识至少一个码块。这至少一个码块中包括前述所描述的第一GCC码块。
该示例中，可以是一个码块对应一个码块标识，也可以是多个码块对应一个码块标识，在本申请中不做限定说明。另外，由于第一client ID可以标识出与第一小颗粒业务对应的第一client，而且第一client包括第一业务数据。码块标识也可以用来指示至少一个码块，而且这至少一个码块中还包括第一GCC码块。那么，通过配置第一client ID与码块标识之间的映射关系，使得第一通信装置能够获知需要将该第一业务数据指定映射在哪 些GCC码块中。
举例来说，在当前需要传输2个client的第一业务数据的情景中，分别对这2个client使用不同的client ID(如client ID 1和client ID 2)来标识，并且使用码块标识A2标识码块1、使用码块标识B2标识码块2～码块5等等。需说明，码块1至码块5中的每个码块，都可以由相邻的小颗粒单元基帧开销中的GCC字段组成。通过配置client ID 1与码块标识A2之间存在映射关系、client ID 2与码块标识B2之间存在映射关系等等。这样，便可以通过码块1承载该client ID 1所标识的client的第一业务数据，通过码块2～码块5承载该client ID 2所标识的client的第一业务数据。
需说明，上述所描述的client ID 1～client ID 4，字节标识A1、B1、C1、D1，码块标识A2、B2等等，仅仅是一个示意性的描述，在本申请实施例中不做限定。
在另一些可能的示例中，第一通信装置向第二通信装置发送第一小颗粒单元基帧开销，也可以通过以下方式来实现。即：第一通信装置向第二通信装置发送小颗粒单元复帧。也就是说，第一通信装置在基于映射关系2将第一业务数据映射到第一GCC码块后，可以直接向第二通信装置发送小颗粒单元复帧，进而将第一业务数据以承载在第一GCC码块的方式，传输到第二通信装置中。
需说明，所提及的小颗粒单元复帧可以参照前述的内容进行理解，此处不做赘述。
在另一些可能的实施方式中，第一通信装置还可以根据第三映射关系，将第二业务数据映射到小颗粒单元基帧净荷的至少一个子时隙。所描述的第三映射关系指示第二客户client和至少一个子时隙之间的映射关系，第二client与第二小颗粒业务对应。然后，第一通信装置还可以向第二通信装置发送小颗粒单元基帧净荷。其中，该小颗粒单元基帧净荷用于承载第二小颗粒业务的第二业务数据，第一小颗粒业务与第二小颗粒业务不相同。
该示例中，所描述的第二小颗粒业务是指带宽大于或等于一个sub-slot的带宽的业务。
903、第二通信装置接收第一通信装置发送的第一小颗粒单元基帧开销。
所描述的第二通信装置可以是中间节点，也可以是边缘节点，本申请实施例中不做限定。在第一通信装置向第二通信装置发送第一小颗粒单元基帧开销后，第二通信装置便可以接收到第一通信装置发送的第一小颗粒单元基帧开销了。
在另一些可能的示例中，第二通信装置还可以接收第一通信装置发送的小颗粒单元基帧净荷。小颗粒单元基帧净荷用于承载第二小颗粒业务的第二业务数据，第一小颗粒业务和第二小颗粒业务不相同。
需说明，所描的小颗粒单元基帧净荷可以参照前述步骤902中所提及的小颗粒单元基帧净荷进行理解，此处不做赘述。
在另一些可能的示例中，第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，第一GCC字段承载第一业务数据。
在另一些可能的示例中，第一GCC字段的至少一个字节被指定用于承载第一小颗粒业务。需说明，所描述的第一GCC字段、第一小颗粒单元基帧开销可以参照前述步骤902中所提及的内容进行理解，此处不做赘述。
另外，在另一些可能的实施方式中，第二通信装置接收第一通信装置发送的第一小颗粒单元基帧开销，可以通过以下方式来实现，即：第二通信装置接收第一通信装置发送的小颗粒单元复帧。
需说明，所描述的小颗粒单元复帧，小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧。第一小颗粒单元基帧包括第一小颗粒单元基帧开销，第二小颗粒单元基帧包括第二小颗粒单元基帧开销，第一小颗粒单元基帧开销的第一GCC字段和第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，第一GCC码块被指定用于承载第一小颗粒业务。具体也可以参照前述步骤902的内容进行理解，此处不做赘述。
904、第二通信装置对第一小颗粒单元基帧开销进行处理。
在第二通信装置为不同的节点时，还可以对所获取到的第一小颗粒单元基帧开销执行不同的处理。下面将从两种可能的方式详细地描述第二通信装置作为不同的节点时，如何对该第一小颗粒单元基帧开销进行处理的过程。
(1)、第二通信装置为中间节点
在第二通信装置为中间节点的时候，获取到第一小颗粒单元基帧开销后，还可以向下游的边缘节点或者下一跳的中间节点转发第一小颗粒单元基帧开销，由下游的边缘节点或下一跳的中间节点解映射出第一业务数据。或者，在获取到第一小颗粒单元基帧开销后，也可以先解映射出第一业务数据后，再转发到下游的边缘节点或中间节点。下面将从不同的示例进行说明：
在另一些具体的实施方式中，第二通信装置对第一小颗粒单元基帧开销进行处理，可以通过如下步骤进行转发，即：将第一业务数据从第一client交换在第二client，其中，第一client与第一小颗粒业务对应，第二client与第一小颗粒业务对应。
在该示例中，将第一业务数据从第一client交换在第二client，可以理解成将该第一业务数据从接收侧client交换到发送侧的client。举例来说，图12为本申请实施例中提供的第一业务数据在client中交换的示意图。如图12所示，该第二通信装置配置有接收侧的第一client和发送侧的第二client。其中，接收侧的第一client例如可以是client A1、client A2、…、或client Am(m为大于等于1的正整数)中的任意一个client，发送侧的第二client例如可以是client B1、client B2、…、或client Bm中的任意一个client。client A1例如可以配置为与client B1进行交换。类似地，client A2例如可以配置为与client B2进行交换。针对其余的client Am，其交换关系也可以参照上述的交换关系进行理解，此处不做赘述。
需说明，此处所提及的第一client是由第二通信装置从第一通信装置中接收第一小颗粒基帧开销时所对应的client。第二client是由第二通信装置向第三通信装置发送第一小颗粒基帧开销时所对应的client。
示例性地，第二通信装置将第一业务数据从第一client交换在第二client中，可以通过以下方式来实现，即：
S01、根据第一映射关系，从第一GCC字段提取第一业务数据，第一映射关系指示第一client与第一GCC字段之间的映射关系。
S02、基于第二映射关系，将第一业务数据映射到第三GCC字段，第二映射关系指示第二client与第三GCC字段之间的映射关系。
该示例中，可以基于第一映射关系和第二映射关系将第一业务数据，从第一GCC字段的至少一个字节映射到第三GCC字段的至少一个字节中。或者，也可以基于第一映射关系和第二映射关系将第一业务数据，从第一GCC码块映射到第二GCC码块中。下面分别以不同的实施例进行介绍：
①、基于字节的交换方式
在一些示例中，第一映射关系可以包括第一GCC字段的至少一个字节与第一client之间的映射关系，第二映射关系可以包括第三GCC字段的至少一个字节与第二client之间的映射关系。
在该示例中，由于第一小颗粒业务与第一client对应，第二client也与第一小颗粒业务对应。而且，与第一client对应的第一GCC字段可以包括至少一个字节，与第二client对应的第三GCC字段也可以包括至少一个字节。那么，可以通过第一映射关系将第一业务数据从第一GCC字段中提取出来后，可以基于该第二映射关系将第一业务数据映射到第三GCC字段的至少一个字节中。这样，第二通信装置可以进一步向第三通信装置发送包含有该第三GCC字段的第三小颗粒单元基帧开销。
②、基于GCC码块的交换方式
在一些示例中，第一映射关系包括第一GCC码块与第一client之间的映射关系，第一GCC码块由第一GCC字段和第二GCC字段组成。第二映射关系包括第二GCC码块与第二client之间的映射关系，其中，第二GCC码块由第三GCC字段和第四GCC字段组成。
在该示例中，第一GCC码块可以参照前述步骤903的内容进行理解，此处不做赘述。需说明，第二GCC码块由第三GCC字段和第四GCC字段组成，其中，第三GCC字段包含在第二通信装置向第三通信装置发送的第三小颗粒单元基帧开销中，第四GCC字段包含在第二通信装置向第三通信装置发送的第四小颗粒单元基帧开销中。而且，第三小颗粒单元基帧和第四小颗粒单元基帧为小颗粒单元复帧中相邻的小颗粒单元基帧。
由于第一小颗粒业务与第一client对应，第二client也与第一小颗粒业务对应。而且，第一GCC码块与第一client对应，第二GCC码块与第二client对应。那么，可以通过将第一业务数据从第一GCC码块中提取出来后，可以基于该第二映射关系将第一业务数据映射到第二GCC码块中。这样，第二通信装置可以进一步向第三通信装置发送包含有该第三GCC字段的第三小颗粒单元基帧开销，以及发送含有第四GCC字段的第四小颗粒单元开销，便可以将第一业务数据转发出去了。
需说明，上述①和②中提及的第一映射关系和第二映射关系，也可以由控制管理设备配置好之后，例如通过配置信息的方式将该第一映射关系和第二映射关系下发至第二通信装置中。或者，第二通信装置也可以通过其他的方式获取到该第一映射关系和第二映射关系，此处不做限定说明。
上述主要从交叉技术的角度，描述了第二通信装置对第一小颗粒单元基帧开销进行处理的过程，使得在混合组网的场景中，不需要对接管理协议设备的管理问题，可以有效地 将第一业务数据透明地传输，节省网络资源。在另一些具体的实施方式中，第二通信装置对第一小颗粒单元基帧开销进行处理，除了通过上述交叉处理的方式进行转发以外，还可以通过如下方式进行转发，即：透传第一小颗粒单元基帧开销，第一业务数据被指定承载在第一小颗粒单元基帧开销的通用通信信道GCC字段中的至少一个字节或至少一个码块中。
在该示例中，第二通信装置在获取到第一小颗粒单元基帧开销后，不需要把第一业务数据从第一小颗粒单元基帧开销的第一GCC字段的字节，或这第一GCC码块中解析出，而是可以通过传输大颗粒业务时所使用的时隙，直接透传第一小颗粒单元基帧开销，使得第一业务数据传输到下一跳的中间节点或者边缘节点等。
在另一些具体的实施方式中，第二通信装置也可以在获取到第一小颗粒单元基帧开销之后，除了通过上述交换的方式进行转发、以及直接透传第一小颗粒单元基帧开销的方式以外，还可以执行如下步骤：从第一小颗粒单元基帧开销提取出第一业务数据。
示例性地，可以基于第一映射关系将第一业务数据，从第一GCC字段的至少一个字节中解映射出。或者，可以基于第一映射关系将第一业务数据，从第一GCC码块中解映射出。所描述的第一映射关系可以参照前述步骤S01中所提及的第一映射关系进行理解，此处不做赘述。
或者，也可以基于第二映射关系将第一业务数据，从第三GCC字段的至少一个字节中解映射出。或者，可以基于第二映射关系将第一业务数据，从第二GCC码块中解映射出。所描述的第二映射关系可以参照前述步骤S02中所提及的第二映射关系进行理解，此处不做赘述。
S12、对第一业务数据进行二层或三层处理。
S12、转发二层或三层处理后得到的业务报文。
在该示例中，在直接从第一小颗粒单元基帧开销中解映射出第一业务数据后，通过对第一业务数据进行二层或三层的封装处理后，可以将处理后得到的业务报文转发到边缘节点。
(2)、第二通信装置为边缘节点
在第二通信装置为边缘节点的时候，还可以在获取到第一小颗粒单元基帧开销后，从该第一小颗粒单元基帧开销中提取出第一业务数据；并对第一业务数据进行二层或三层处理以重组报文。
在另一些示例中，边缘节点在获取到中间节点发送的第三小颗粒单元基帧开销或第四小颗粒单元基帧开销的时候，也可以基于第二映射关系将第一业务数据，从第三GCC字段的至少一个字节中解映射出。或者，可以基于第二映射关系将第一业务数据，从第二GCC码块中解映射出。所描述的第二映射关系可以参照前述步骤S02中所提及的第二映射关系进行理解，此处不做赘述。
此外，本申请中提到的提取、获取、解映射等词汇，在一些示例中可以相互替换。
在本申请实施例中，通过小颗粒单元基帧开销承载第一小颗粒业务的第一业务数据，无需占用额外的sub-slot来传输该第一业务数据，即可完成对小颗粒业务的业务数据的承 载和传送，尽量避免了带宽浪费，有效地节约了带宽资源。而且，还可以通过开销交叉技术等方式，将第一业务数据透传到下一节点，不需要额外增加网络资源。
上述主要从交互的角度描述了本申请实施例提供的一种数据传输的方法。下面结合图13，对本申请实施例所提供的一种通信装置1300进行介绍。通信装置1300可以应用于图8所示的网络架构中。举例来说，通信装置1300例如可以是本申请图8所示出的网络设备1(TX)或者网络设备2(RX)，通信装置1300还可以是本申请的第一通信装置或第二通信装置。本申请的第一通信装置和第二通信装置可以是整体的网络设备，也可以是网络设备1中的单板，例如接口板或者线卡或哑板或集中交叉板，也可以是执行相关操作的芯片等。通信装置1300用于执行前述图9-图12任一附图所对应的实施例的方法。通信装置1300包括收发单元1301和处理单元1302。收发单元1301用于执行收发操作，处理单元用于执行收发以外的操作。例如，当通信装置1300作为第一通信装置执行图9所示的方法时，处理单元1302用于根据第一映射关系将第一业务数据映射到至少一个字节，或根据第二映射关系将第一业务数据映射到第一GCC码块；收发单元1301可以用于发送第一小颗粒单元基帧开销。
下面结合图14，对本申请实施例所提供的另一种通信装置1400进行介绍。通信装置1400可以应用于图14所示的网络架构中。举例来说，通信装置1400例如可以是本申请网络设备1(TX)或者网络设备2(RX)，通信装置1400还可以是本申请的第一通信装置或第二通信装置。本申请的第一通信装置和第二通信装置可以是整体的网络设备，也可以是网络设备1中的单板，例如接口板或者线卡或哑板或集中交叉板，也可以是执行相关操作的芯片等。通信装置1400用于执行前述图9-图12任一附图所对应的实施例的方法。通信装置1400包括通信接口1401以及与通信接口相连的处理器1402。通信接口1401用于执行收发操作，处理器1402用于执行收发以外的操作。例如，当通信装置1400作为第一通信装置执行图9所示的方法时，处理器1402用于根据第一映射关系将第一业务数据映射到至少一个字节，或根据第二映射关系将第一业务数据映射到第一GCC码块；通信接口1401可以用于发送第一小颗粒单元基帧开销。
下面结合图15，对本申请实施例提供的另一种通信装置1500进行介绍。通信装置1500可以应用于图8所示的网络架构中。举例来说，通信装置1500例如可以是本申请网络设备1(TX)或者网络设备2(RX)，通信装置1500还可以是本申请的第一通信装置或第二通信装置。本申请的第一通信装置和第二通信装置可以是整体的网络设备，也可以是网络设备1中的单板，例如接口板或者线卡或哑板或集中交叉板，也可以是执行相关操作的芯片等。通信装置1500用于执行前述图9-图12任一附图所对应的实施例的方法。通信装置1500包括存储器1501和与存储器相连的处理器1502。存储器1501中存储有指令，处理器1502读取指令，使得通信装置1500执行图9-图12任一附图所对应的实施例的方法。
下面结合图16，对本申请实施例提供的另一种通信装置1600进行介绍。通信装置1600可以应用于图8所示的网络架构中。举例来说，通信装置1600例如可以是本申请网络设备1(TX)或者网络设备2(RX)，通信装置1600还可以是本申请的第一通信装置或第二通信装置。本申请的第一通信装置和第二通信装置可以是整体的网络设备，也可以是网络设备 1中的单板，例如接口板或者线卡或哑板或集中交叉板，也可以是执行相关操作的芯片等。通信装置1600用于执行前述图9-图12任一附图所对应的实施例的方法。如图16所示，通信装置1000包括处理器1610，与处理器耦合连接的存储器1620以及通信接口1630。在一个具体的实施方式中，存储器1620中存储有计算机可读指令，计算机可读指令包括多个软件模块，例如发送模块1621，处理模块1622和接收模块1623。处理器1610执行各个软件模块后可以按照各个软件模块的指示进行相应的操作。在本实施例中，一个软件模块所执行的操作实际上是指处理器1610根据软件模块的指示而执行的操作。例如，当网络设备1作为第一通信装置执行图9所示的方法时，发送模块1621用于发送第一小颗粒单元基帧开销，处理模块1622用于根据第一映射关系将第一业务数据映射到至少一个字节，或根据第二映射关系将第一业务数据映射到第一GCC码块。此外，处理器1610执行存储器1620中的计算机可读指令后，可以按照计算机可读指令的指示，执行本申请中由第一通信装置可以执行的全部操作。例如，当通信装置1600作为第一通信装置时，通信装置1600可以执行图9-图12任一附图所对应的实施例中由第一通信装置所执行的方法。
在本申请中所提到的处理器可以是中央处理器(central processing unit，CPU)，网络处理器(network processor，NP)或者CPU和NP的组合。处理器还可以是专用集成电路(application-specific integrated circuit，ASIC)，可编程逻辑器件(programmable logic device，PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(complex programmable logic device，CPLD)，现场可编程逻辑门阵列(field-programmable gate array，FPGA)，通用阵列逻辑(generic array logic，GAL)或其任意组合。处理器1010可以是指一个处理器，也可以包括多个处理器。本申请中所提到的存储器可以包括易失性存储器(volatile memory)，例如随机存取存储器(random-access memory，RAM)；存储器也可以包括非易失性存储器(non-volatile memory)，例如只读存储器(read-only memory，ROM)，快闪存储器(flash memory)，硬盘(hard disk drive，HDD)或固态硬盘(solid-state drive，SSD)；存储器还可以包括上述种类的存储器的组合。存储器可以是指一个存储器，也可以包括多个存储器。
上述主要描述了本申请实施例提供的通信装置的结构示意图。可以理解的是，上述的第一通信装置和第二通信装置为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的功能，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
从功能单元的角度，本申请可以根据上述方法实施例对第一通信装置和第二通信装置进行功能单元的划分，例如，可以对应各个功能划分各个功能单元，也可以将两个或两个以上的功能集成在一个功能单元中。上述集成的功能单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。
比如，以采用集成的方式划分各个功能单元的情况下，参见图17A，为本申请实施例 提供了一种第一通信装置的结构示意图。所描述的第一通信装置可以包括：获取单元1701和发送单元1702。
其中，获取单元1701，用于获取第一小颗粒业务的第一业务数据。具体可以参照前述图9中的步骤901的内容进行理解，此处不做赘述。
发送单元1702，用于向第二通信装置发送第一小颗粒单元基帧开销，第一小颗粒单元基帧开销承载第一业务数据。具体可以参照前述图9中的步骤902的内容进行理解，此处不做赘述。
在一些可能的实施方式中，发送单元1702，还用于向第二通信装置发送小颗粒单元基帧净荷，小颗粒单元基帧净荷用于承载第二小颗粒业务的业务数据，第一小颗粒业务与第二小颗粒业务不相同。具体可以参照前述图9中的步骤902的内容进行理解，此处不做赘述。
在另一些可能的实施方式中，第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，第一GCC字段用于承载第一业务数据。具体可以参照前述图9中的步骤902的内容进行理解，此处不做赘述。
在另一些可能的实施方式中，第一GCC字段中的至少一个字节被指定用于承载第一小颗粒业务。具体可以参照前述图9中的步骤902的内容进行理解，此处不做赘述。
在上述图17A示出的第一通信装置的基础上，图17B示出了第一通信装置的另一种结构示意图。如图17B所示，第一通信装置除了包括获取单元1701和发送单元1702以外，还可以包括第一处理单元1703。
其中，该第一处理单元1703，用于在发送单元1702发送第一小颗粒单元基帧开销之前，根据第一映射关系将第一业务数据映射到至少一个字节。需说明，第一映射关系指示至少一个字节和第一客户client之间的映射关系，第一client与第一颗粒业务对应。
在另一些可能的实施方式中，第一映射关系包括第一客户标识client ID和字节标识之间的映射关系，其中，第一client ID用于标识第一client，字节标识用于标识至少一个字节。
在另一些可能的实施方式中，发送单元1702用于：
向第二通信装置发送小颗粒单元复帧，小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧，第一小颗粒单元基帧包括第一小颗粒单元基帧开销，第二小颗粒单元基帧包括第二小颗粒单元基帧开销，第一小颗粒单元基帧开销的第一GCC字段和第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，第一GCC码块被指定用于承载第一小颗粒业务。
在上述图17A示出的第一通信装置的基础上，图17C示出了第一通信装置的另一种结构示意图。如图17C所示，第一通信装置除了包括获取单元1701和发送单元1702以外，还可以包括第二处理单元1704。
或者，第二处理单元1704，用于在发送单元1702发送在发送小颗粒单元复帧之前，根据第二映射关系将第一业务数据映射到至少一个码块。其中，第二映射关系指示至少一个码块和第一客户client之间的映射关系，第一client与第一小颗粒业务对应。具体可 以参照前述图9中的步骤902的内容进行理解，此处不做赘述。
在另一些可能的实施方式中，第二映射关系包括第一client ID和码块标识之间的映射关系。其中，第一client ID用于标识第一client，码块标识用于标识至少一个码块，至少一个码块包括第一GCC码块。具体可以参照前述图9中的步骤902的内容进行理解，此处不做赘述。
在另一些可能的实施方式中，获取单元1701还用于获取第一配置信息，第一配置信息包括第一映射关系或第二映射关系。具体可以参照前述图9中的步骤902的内容进行理解，此处不做赘述。
在上述图17A至图17C中任一项示出的第一通信装置的基础上，图17D示出了第一通信装置的另一种结构示意图。如图17D所示，第一通信装置除了包括获取单元1701和发送单元1702以外，还可以包括第三处理单元1705。
第三处理单元1705，用于在发送单元1702向第二通信装置发送小颗粒单元基帧净荷之前，根据第三映射关系，将第二业务数据映射到小颗粒单元基帧净荷的至少一个子时隙。其中，第三映射关系指示第二客户client和至少一个子时隙之间的映射关系，第二client与第二小颗粒业务对应。
上述图17A至图17D主要从功能模块的角度描述了第一通信装置。下面将从功能模块的角度描述第二通信装置。比如，以采用集成的方式划分各个功能单元的情况下，参见图18，为本申请实施例提供了一种第二通信装置的结构示意图。所描述的第二通信装置可以包括：获取单元1801和处理单元1802。
其中，获取单元1801，用于接收第一通信装置发送的第一小颗粒单元基帧开销，第一小颗粒单元基帧开销用于承载第一小颗粒业务的第一业务数据。具体可以参照前述图9中的步骤903的内容进行理解，此处不做赘述。
处理单元1802，用于对第一小颗粒单元基帧开销进行处理。具体可以参照前述图9中的步骤904的内容进行理解，此处不做赘述。
在另一些可能的实施方式中，获取单元1801，还用于接收第一通信装置发送的小颗粒单元基帧净荷，小颗粒单元基帧净荷承载第二小颗粒业务的第二业务数据，第一小颗粒业务与第二小颗粒业务不相同。
在另一些可能的实施方式中，第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，第一GCC字段承载第一业务数据。
在另一些可能的实施方式中，第一GCC字段的至少一个字节被指定用于承载第一小颗粒业务。
在另一些可能的实施方式中，获取单元1801，用于接收第一通信装置发送的小颗粒单元复帧，小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧。其中，第一小颗粒单元基帧包括第一小颗粒单元基帧开销，第二小颗粒单元基帧包括第二小颗粒单元基帧开销。第一小颗粒单元基帧开销的第一GCC字段和第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，第一GCC码块被指定用于承载第一小颗粒业务。
在另一些可能的实施方式中，处理单元1802用于：将第一业务数据从第一client交换在第二client，其中，第一client与第一小颗粒业务对应，第二client与第一小颗粒业务对应。
在另一些可能的实施方式中，处理单元1802用于：基于第一映射关系，从第一GCC字段提取第一业务数据，第一映射关系指示第一client与第一GCC字段之间的映射关系；基于第二映射关系，将第一业务数据映射到第三GCC字段，第二映射关系指示第二client与第三GCC字段之间的映射关系。
在另一些可能的实施方式中，第一映射关系包括第一GCC字段的至少一个字节与第一client之间的映射关系。
在另一些可能的实施方式中，第一映射关系包括第一GCC码块与第一client之间的映射关系，第一GCC码块由第一GCC字段和第二GCC字段组成，第二GCC字段包含在第二小颗粒单元基帧开销中，第一小颗粒单元基帧开销包括在第一小颗粒单元基帧中，第二小颗粒单元基帧开销包括在第二小颗粒单元基帧中，第一小颗粒单元基帧和第二小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
在另一些可能的实施方式中，第二映射关系包括第三GCC字段的至少一个字节与第二client之间的映射关系。
在另一些可能的实施方式中，第二映射关系包括第二GCC码块与第二client之间的映射关系。其中，第二GCC码块由第三GCC字段和第四GCC字段组成，第三GCC字段包含在第二通信装置向第三通信装置发送的第三小颗粒单元基帧开销中，第四GCC字段包含在第二通信装置向第三通信装置发送的第四小颗粒单元基帧开销中，第三小颗粒单元基帧和第四小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
在另一些可能的实施方式中，处理单元1802用于透传第一小颗粒单元基帧开销。
在另一些可能的实施方式中，获取单元1801还用于获取第一配置信息，第一配置信息包括第一映射关系或第二映射关系。
在另一些可能的实施方式中，处理单元1802用于：从第一小颗粒单元基帧开销提取出第一业务数据；对第一业务数据进行二层或三层处理。
本申请实施例还提供了一种通信***，包括第一通信装置和第二通信装置，其中，第一通信装置或者第二通信装置可以是图13-图16任一项的通信装置，用于执行图9至图12对对应的任意一个实施例中的方法。或者，第一通信装置也可以是前述图17A至图17B任一的第一通信装置，第二通信装置也可以是前述图18的第二通信装置，用于执行图9至图12对对应的任意一个实施例中的方法。所述通信***还可以包括本申请所述的控制管理设备。
本申请还提供了一种计算机程序产品，包括计算机程序，当其在计算机上运行时，使得计算机可以执行执行图9至图12对应的任意一个实施例中由第一通信装置，第二通信装置或控制管理设备所执行的方法。
本申请还提供了一种计算机程序产品，包括计算机程序，当其在计算机上运行时，使得计算机可以执行执行图9至图12对应的任意一个实施例中由第一通信装置，第二通信装 置或控制管理设备所执行的方法。
本申请提供了一种计算机可读存储介质，包括计算机指令，当其在计算机上运行时，使得计算机可以执行图9至图12对应的任意一个实施例中由第一通信装置，第二通信装置或控制管理设备所执行的方法。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的模块及方法操作，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的***、装置和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，可以全部或部分地通过硬件、固件或者其任意组合来实现。当具体实现过程中涉及软件时，可以全部或部分地体现为计算机程序产品的形式。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
以上对本申请所提供的技术方案进行了详细介绍，本申请中应用了具体个例对本申请的原理及实施方式进行了阐述，以上实施例的说明只是用于帮助理解本申请的方法及其核心思想；同时，对于本领域的一般技术人员，依据本申请的思想，在具体实施方式及应用范围上均会有改变之处，综上所述，本说明书内容不应理解为对本申请的限制。

Claims (57)

  1. 一种数据传输的方法，其特征在于，由第一通信装置执行，包括：
    获取第一小颗粒业务的第一业务数据；
    向第二通信装置发送第一小颗粒单元基帧开销，所述第一小颗粒单元基帧开销承载所述第一业务数据。
  2. 根据权利要求1所述的方法，其特征在于，所述方法还包括：
    向所述第二通信装置发送小颗粒单元基帧净荷，所述小颗粒单元基帧净荷用于承载第二小颗粒业务的第二业务数据，所述第一小颗粒业务与所述第二小颗粒业务不相同。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，所述第一GCC字段用于承载所述第一业务数据。
  4. 根据权利要求3所述的方法，其特征在于，所述第一GCC字段的至少一个字节被指定用于承载所述第一小颗粒业务。
  5. 根据权利要求4所述的方法，其特征在于，在发送所述第一小颗粒单元基帧开销之前，所述方法还包括：
    根据第一映射关系将所述第一业务数据映射到所述至少一个字节,所述第一映射关系指示所述至少一个字节和第一客户client之间的映射关系，所述第一client与所述第一小颗粒业务对应。
  6. 根据权利要求5所述的方法，其特征在于，所述第一映射关系包括第一客户标识client ID和字节标识之间的映射关系，其中，所述第一client ID用于标识所述第一client，所述字节标识用于标识所述至少一个字节。
  7. 根据权利要求3所述的方法，其特征在于，向第二通信装置发送第一小颗粒单元基帧开销，包括：
    向所述第二通信装置发送小颗粒单元复帧，所述小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧，所述第一小颗粒单元基帧包括所述第一小颗粒单元基帧开销，所述第二小颗粒单元基帧包括第二小颗粒单元基帧开销，所述第一小颗粒单元基帧开销的所述第一GCC字段和所述第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，所述第一GCC码块被指定用于承载所述第一小颗粒业务。
  8. 根据权利要求7所述的方法，其特征在于，在发送所述小颗粒单元复帧之前，所述方法还包括：
    根据第二映射关系将所述第一业务数据映射到所述第一GCC码块，其中，所述第二映射 关系指示所述第一GCC码块和第一客户client之间的映射关系，所述第一client与所述第一小颗粒业务对应。
  9. 根据权利要求8所述的方法，其特征在于，所述第二映射关系包括第一client ID和码块标识之间的映射关系，其中，所述client ID用于标识所述第一client，所述码块标识用于标识至少一个码块，所述至少一个码块包括所述第一GCC码块。
  10. 根据权利要求5-6中任一项所述的方法，其特征在于，所述方法还包括：
    获取第一配置信息，所述第一配置信息包括所述第一映射关系。
  11. 根据权利要求7-9中任一项所述的方法，其特征在于，所述方法还包括：
    获取第一配置信息，所述第一配置信息还包括所述第二映射关系。
  12. 根据权利要求2-11任一项所述的方法，其特征在于，向所述第二通信装置发送小颗粒单元基帧净荷之前，所述方法还包括：
    根据第三映射关系，将所述第二业务数据映射到所述小颗粒单元基帧净荷的至少一个子时隙，其中，所述第三映射关系指示第二客户client和所述至少一个子时隙之间的映射关系，所述第二client与所述第二小颗粒业务对应。
  13. 一种数据传输的方法，其特征在于，应用于第二通信装置，包括：
    接收第一通信装置发送的第一小颗粒单元基帧开销，所述第一小颗粒单元基帧开销承载第一小颗粒业务的第一业务数据；
    对所述第一小颗粒单元基帧开销进行处理。
  14. 根据权利要求13所述的方法，其特征在于，所述方法还包括：
    接收所述第一通信装置发送的小颗粒单元基帧净荷，所述小颗粒单元基帧净荷承载第二小颗粒业务的第二业务数据，所述第一小颗粒业务与所述第二小颗粒业务不相同。
  15. 根据权利要求13或14所述的方法，其特征在于，所述第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，所述第一GCC字段承载所述第一业务数据。
  16. 根据权利要求15所述的方法，其特征在于，所述第一GCC字段的至少一个字节被指定用于承载所述第一小颗粒业务。
  17. 根据权利要求15所述的方法，其特征在于，所述接收所述第一通信装置发送的第一小颗粒单元基帧开销,包括：
    接收所述第一通信装置发送的小颗粒单元复帧，所述小颗粒单元复帧包括相邻的第一 小颗粒单元基帧和第二小颗粒单元基帧，所述第一小颗粒单元基帧包括所述第一小颗粒单元基帧开销，所述第二小颗粒单元基帧包括第二小颗粒单元基帧开销，所述第一小颗粒单元基帧开销的所述第一GCC字段和所述第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，所述第一GCC码块被指定用于承载所述第一小颗粒业务。
  18. 根据权利要求13-17任一项所述的方法，其特征在于，所述对所述第一小颗粒单元基帧开销进行处理，包括：
    将所述第一业务数据从第一client交换在第二client，其中，所述第一client与所述第一小颗粒业务对应，所述第二client与所述第一小颗粒业务对应。
  19. 根据权利要求18所述的方法，其特征在于，将所述第一业务数据从第一client交换在第二client，包括：
    基于第一映射关系，从所述第一GCC字段提取所述第一业务数据，所述第一映射关系指示所述第一client与所述第一GCC字段之间的映射关系；
    基于第二映射关系，将所述第一业务数据映射到第三GCC字段，所述第二映射关系指示所述第二client与所述第三GCC字段之间的映射关系。
  20. 根据权利要求19所述的方法，其特征在于，所述第一映射关系包括所述第一GCC字段的至少一个字节与所述第一client之间的映射关系。
  21. 根据权利要求19所述的方法，其特征在于，所述第一映射关系包括第一GCC码块与所述第一client之间的映射关系，所述第一GCC码块由所述第一GCC字段和第二GCC字段组成，所述第二GCC字段包含在第二小颗粒单元基帧开销中，所述第一小颗粒单元基帧开销包括在第一小颗粒单元基帧中，所述第二小颗粒单元基帧开销包括在第二小颗粒单元基帧中，所述第一小颗粒单元基帧和所述第二小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
  22. 根据权利要求19或20所述的方法，其特征在于，所述第二映射关系包括所述第三GCC字段的至少一个字节与所述第二client之间的映射关系。
  23. 根据权利要求19或21所述的方法，其特征在于，所述第二映射关系包括第二GCC码块与所述第二client之间的映射关系，其中，所述第二GCC码块由所述第三GCC字段和第四GCC字段组成，所述第三GCC字段包含在所述第二通信装置向第三通信装置发送的第三小颗粒单元基帧开销中，所述第四GCC字段包含在所述第二通信装置向第三通信装置发送的第四小颗粒单元基帧开销中，所述第三小颗粒单元基帧和所述第四小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
  24. 根据权利要求13-17中任一项所述的方法，其特征在于，所述对所述第一小颗粒单 元基帧开销进行处理，包括：
    透传所述第一小颗粒单元基帧开销。
  25. 根据权利要求19-23中任一项所述的方法，其特征在于，所述方法还包括：
    获取第一配置信息，所述第一配置信息包括所述第一映射关系或所述第二映射关系。
  26. 根据权利要求13-17中任一项所述的方法，其特征在于，所述对所述第一小颗粒单元基帧开销进行处理，包括：
    从所述第一小颗粒单元基帧开销提取出所述第一业务数据；
    对所述第一业务数据进行二层或三层处理。
  27. 一种第一通信装置，其特征在于，包括：
    获取单元，用于获取第一小颗粒业务的第一业务数据；
    发送单元，用于向第二通信装置发送第一小颗粒单元基帧开销，所述第一小颗粒单元基帧开销承载所述第一业务数据。
  28. 根据权利要求27所述的第一通信装置，其特征在于，所述发送单元还用于：
    向所述第二通信装置发送小颗粒单元基帧净荷，所述小颗粒单元基帧净荷用于承载第二小颗粒业务的第二业务数据，所述第一小颗粒业务与所述第二小颗粒业务不相同。
  29. 根据权利要求27或28所述的第一通信装置，其特征在于，所述第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，所述第一GCC字段用于承载所述第一业务数据。
  30. 根据权利要求29所述的第一通信装置，其特征在于，所述第一GCC字段中的至少一个字节被指定用于承载所述第一小颗粒业务。
  31. 根据权利要求30所述的第一通信装置，其特征在于，所述第一通信装置还包括第一处理单元；
    所述第一处理单元，用于在发送所述第一小颗粒单元基帧开销之前，根据第一映射关系将所述第一业务数据映射到所述至少一个字节，所述第一映射关系指示所述至少一个字节和第一客户client之间的映射关系，所述第一client与所述第一颗粒业务对应。
  32. 根据权利要求31所述的第一通信装置，其特征在于，所述第一映射关系包括第一客户标识client ID和字节标识之间的映射关系，其中，所述第一client ID用于标识所述第一client，所述字节标识用于标识所述至少一个字节。
  33. 根据权利要求29所述的第一通信装置，其特征在于，所述发送单元用于：
    向所述第二通信装置发送小颗粒单元复帧，所述小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧，所述第一小颗粒单元基帧包括所述第一小颗粒单元基帧开销，所述第二小颗粒单元基帧包括第二小颗粒单元基帧开销，所述第一小颗粒单元基帧开销的所述第一GCC字段和所述第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，所述第一GCC码块被指定用于承载所述第一小颗粒业务。
  34. 根据权利要求33所述的第一通信装置，其特征在于，所述第一通信装置还包括第二处理单元；所述第二处理单元用于：
    在发送所述小颗粒单元复帧之前，根据第二映射关系将所述第一业务数据映射到所述至少一个码块，其中，所述第二映射关系指示所述至少一个码块和第一客户client之间的映射关系，所述第一client与所述第一小颗粒业务对应。
  35. 根据权利要求34所述的第一通信装置，其特征在于，所述第二映射关系包括第一client ID和码块标识之间的映射关系，其中，所述第一client ID用于标识所述第一client，所述码块标识用于标识所述至少一个码块，所述至少一个码块包括所述第一GCC码块。
  36. 根据权利要求31或32所述的第一通信装置，其特征在于，
    所述获取单元，还用于获取第一配置信息，所述第一配置信息包括所述第一映射关系。
  37. 根据权利要求34或35所述的第一通信装置，其特征在于，
    所述获取单元，还用于获取第一配置信息，所述第一配置信息包括所述第二映射关系。
  38. 根据权利要求28-37中任一项所述的第一通信装置，其特征在于，所述第一通信装置还包括第三处理单元；
    所述第三处理单元，用于在向所述第二通信装置发送小颗粒单元基帧净荷之前，根据第三映射关系，将所述第二业务数据映射到所述小颗粒单元基帧净荷的至少一个子时隙，其中，所述第三映射关系指示第二客户client和所述至少一个子时隙之间的映射关系，所述第二client与所述第二小颗粒业务对应。
  39. 一种第二通信装置，其特征在于，包括:
    获取单元，用于接收第一通信装置发送的第一小颗粒单元基帧开销，所述第一小颗粒单元基帧开销用于承载第一小颗粒业务的第一业务数据；
    处理单元，用于对所述第一小颗粒单元基帧开销进行处理。
  40. 根据权利要求39所述的第二通信装置，其特征在于，
    所述获取单元，还用于接收所述第一通信装置发送的小颗粒单元基帧净荷，所述小颗粒单元基帧净荷承载第二小颗粒业务的第二业务数据，所述第一小颗粒业务与所述第二小 颗粒业务不相同。
  41. 根据权利要求39或40所述的第二通信装置，其特征在于，所述第一小颗粒单元基帧开销包括第一通用通信信道GCC字段，所述第一GCC字段承载所述第一业务数据。
  42. 根据权利要求41所述的第二通信装置，其特征在于，所述第一GCC字段的至少一个字节被指定用于承载所述第一小颗粒业务。
  43. 根据权利要求41所述的第二通信装置，其特征在于，
    所述获取单元，用于接收所述第一通信装置发送的小颗粒单元复帧，所述小颗粒单元复帧包括相邻的第一小颗粒单元基帧和第二小颗粒单元基帧，所述第一小颗粒单元基帧包括所述第一小颗粒单元基帧开销，所述第二小颗粒单元基帧包括第二小颗粒单元基帧开销，所述第一小颗粒单元基帧开销的所述第一GCC字段和所述第二小颗粒单元基帧开销的第二GCC字段组成第一GCC码块，所述第一GCC码块被指定用于承载所述第一小颗粒业务。
  44. 根据权利要求39-43中任一项所述的第二通信装置，其特征在于，所述处理单元用于：
    将所述第一业务数据从第一client交换在第二client，其中，所述第一client与所述第一小颗粒业务对应，所述第二client与所述第一小颗粒业务对应。
  45. 根据权利要求44所述的第二通信装置，其特征在于，所述处理单元用于：
    基于第一映射关系，从所述第一GCC字段提取所述第一业务数据，所述第一映射关系指示所述第一client与所述第一GCC字段之间的映射关系；
    基于第二映射关系，将所述第一业务数据映射到第三GCC字段，所述第二映射关系指示所述第二client与所述第三GCC字段之间的映射关系。
  46. 根据权利要求45所述的第二通信装置，其特征在于，所述第一映射关系包括所述第一GCC字段的至少一个字节与所述第一client之间的映射关系。
  47. 根据权利要求45所述的第二通信装置，其特征在于，所述第一映射关系包括第一GCC码块与所述第一client之间的映射关系，所述第一GCC码块由所述第一GCC字段和第二GCC字段组成，所述第二GCC字段包含在第二小颗粒单元基帧开销中，所述第一小颗粒单元基帧开销包括在第一小颗粒单元基帧中，所述第二小颗粒单元基帧开销包括在第二小颗粒单元基帧中，所述第一小颗粒单元基帧和所述第二小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
  48. 根据权利要求45或46所述的第二通信装置，其特征在于，所述第二映射关系包括所 述第三GCC字段的至少一个字节与所述第二client之间的映射关系。
  49. 根据权利要求45或47所述的第二通信装置，其特征在于，所述第二映射关系包括第二GCC码块与所述第二client之间的映射关系，其中，所述第二GCC码块由所述第三GCC字段和第四GCC字段组成，所述第三GCC字段包含在所述第二通信装置向第三通信装置发送的第三小颗粒单元基帧开销中，所述第四GCC字段包含在所述第二通信装置向第三通信装置发送的第四小颗粒单元基帧开销中，所述第三小颗粒单元基帧和所述第四小颗粒单元基帧为小颗粒单元复帧中相邻的基帧。
  50. 根据权利要求39-43中任一项所述的第二通信装置，其特征在于，所述处理单元用于：
    透传所述第一小颗粒单元基帧开销。
  51. 根据权利要求45-49中任一项所述的第二通信装置，其特征在于，所述获取单元还用于获取第一配置信息，所述第一配置信息包括所述第一映射关系或所述第二映射关系。
  52. 根据权利要求39-43中任一项所述的第二通信装置，其特征在于，所述处理单元用于：
    从所述第一小颗粒单元基帧开销提取出所述第一业务数据；
    对所述第一业务数据进行二层或三层处理。
  53. 一种第一通信装置，其特征在于，包括：
    存储器，用于存储计算机可读指令；
    还包括，与所述存储器耦合的处理器，用于执行所述存储器中的计算机可读指令，使得所述第一通信装置执行如权利要求1-12中任一项所述的方法。
  54. 一种第二通信装置，其特征在于，包括：
    存储器，用于存储计算机可读指令；
    还包括，与所述存储器耦合的处理器，用于执行所述存储器中的计算机可读指令，使得所述第二通信装置执行如权利要求13-26中任一项所述的方法。
  55. 一种计算机可读存储介质，其特征在于，包括程序或指令，当所述程序或所述指令在计算机上运行时，使得所述计算机执行如权利要求1至26中任一项所述的方法。
  56. 一种包含指令的计算机程序产品，其特征在于，当所述指令在计算机上运行时，使得计算机执行如权利要求1至26中任一项所述的方法。
  57. 一种通信***，其特征在于，所述通信***包括权利要求27至38中任一项所述的第一通信装置，以及权利要求39至52中任一项所述的第二通信装置。
PCT/CN2022/132712 2021-12-13 2022-11-18 一种数据传输的方法以及相关装置 WO2023109424A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202111519430.0A CN116264587A (zh) 2021-12-13 2021-12-13 一种数据传输的方法以及相关装置
CN202111519430.0 2021-12-13

Publications (1)

Publication Number Publication Date
WO2023109424A1 true WO2023109424A1 (zh) 2023-06-22

Family

ID=86723196

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/132712 WO2023109424A1 (zh) 2021-12-13 2022-11-18 一种数据传输的方法以及相关装置

Country Status (2)

Country Link
CN (1) CN116264587A (zh)
WO (1) WO2023109424A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116737172B (zh) * 2023-08-11 2023-12-12 杭州初灵信息技术股份有限公司 一种小颗粒数据包的解析***和方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865887A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 光传送网中的数据传输方法及装置
CN112398734A (zh) * 2019-08-14 2021-02-23 华为技术有限公司 一种业务传输的方法、装置和***
CN112511260A (zh) * 2020-02-28 2021-03-16 中兴通讯股份有限公司 光传送网中业务处理方法、处理装置和电子设备
CN112994843A (zh) * 2021-02-08 2021-06-18 中兴通讯股份有限公司 以太网帧定帧方法和装置
CN113630206A (zh) * 2020-05-08 2021-11-09 中兴通讯股份有限公司 业务处理方法、装置、网络设备和存储介质
CN113784437A (zh) * 2020-06-10 2021-12-10 烽火通信科技股份有限公司 一种FlexE承载小颗粒业务的实现方法和装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865887A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 光传送网中的数据传输方法及装置
CN112398734A (zh) * 2019-08-14 2021-02-23 华为技术有限公司 一种业务传输的方法、装置和***
CN112511260A (zh) * 2020-02-28 2021-03-16 中兴通讯股份有限公司 光传送网中业务处理方法、处理装置和电子设备
CN113630206A (zh) * 2020-05-08 2021-11-09 中兴通讯股份有限公司 业务处理方法、装置、网络设备和存储介质
CN113784437A (zh) * 2020-06-10 2021-12-10 烽火通信科技股份有限公司 一种FlexE承载小颗粒业务的实现方法和装置
CN112994843A (zh) * 2021-02-08 2021-06-18 中兴通讯股份有限公司 以太网帧定帧方法和装置

Also Published As

Publication number Publication date
CN116264587A (zh) 2023-06-16

Similar Documents

Publication Publication Date Title
EP4178297A1 (en) Data transmission method, and device
US11316545B2 (en) Data transmission method, communications device, and storage medium
US11082199B2 (en) Data transmission method in optical network and optical network device
WO2019062227A1 (zh) 数据传输方法、传输设备和传输***
EP3468075B1 (en) Method, apparatus, and network system for sending and receiving services
KR102383297B1 (ko) 서비스 주파수를 투명하게 전송하기 위한 방법 및 디바이스
EP3909209B1 (en) Ethernet signal format using 256b/257b block encoding
US6731654B1 (en) Communication system overhead channel
WO2019128665A1 (zh) 一种数据传输方法、通信设备及存储介质
WO2023109424A1 (zh) 一种数据传输的方法以及相关装置
US20220021472A1 (en) CPRI Data Block Transmission Method and Apparatus
WO2019100982A1 (zh) 数据传输方法和设备
WO2023035776A1 (zh) 一种通信方法、相关装置以及存储介质
US7583599B1 (en) Transporting stream client signals via packet interface using GFP mapping
WO2021115215A1 (zh) 一种数据传输方法、通信设备及存储介质
JP7167345B2 (ja) データ伝送方法、通信機器、および記憶媒体
CN113472826A (zh) 一种业务承载、提取方法、数据交换方法及设备
WO2024032269A1 (zh) 通信方法、相关装置及计算机可读存储介质
WO2023141777A1 (zh) 通信方法及网络设备
WO2024032191A1 (zh) 一种故障码块处理方法及装置
WO2023143577A1 (zh) 一种光传送网中的数据帧的处理方法、装置和***
WO2023232097A1 (zh) 业务数据处理方法和装置
CN115603879A (zh) 一种数据传输方法及装置
CN118055076A (zh) 一种报文处理方法、信息处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22906176

Country of ref document: EP

Kind code of ref document: A1