WO2023109424A1 - Procédé de transmission de données et dispositif associé - Google Patents

Procédé de transmission de données et dispositif associé 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)
Chinese (zh)
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/fr

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

La présente demande divulgue un procédé de transmission de données et un dispositif associé. Les premières données de service d'un premier service de granularité fine sont transportées par un surdébit de trame de base d'unité de granularité fine, et les premières données de service sont transmises sans avoir besoin d'occuper un sous-créneau supplémentaire de façon à pouvoir effectuer le transport et la transmission des données du service de granularité fine, éviter autant que possible le gaspillage de bande passante, et économiser efficacement la ressource de bande passante. Le procédé consiste à : obtenir des premières données de service d'un premier service de granularité fine, puis envoyer un premier surdébit de trame de base d'unité de granularité fine à un second dispositif de communication, les premières données de service étant transportées par le premier surdébit de trame de base de l'unité de granularité fine.
PCT/CN2022/132712 2021-12-13 2022-11-18 Procédé de transmission de données et dispositif associé WO2023109424A1 (fr)

Applications Claiming Priority (2)

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

Publications (1)

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

Family

ID=86723196

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/132712 WO2023109424A1 (fr) 2021-12-13 2022-11-18 Procédé de transmission de données et dispositif associé

Country Status (2)

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

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 (fr) Procédé et dispositif de transmission de données
CN109600188B (zh) 数据传输方法、传输设备和传输系统
US11316545B2 (en) Data transmission method, communications device, and storage medium
US11082199B2 (en) Data transmission method in optical network and optical network device
JP6736701B2 (ja) サービス送信方法及び装置、サービス受信方法及び装置、並びにネットワーク・システム
KR102383297B1 (ko) 서비스 주파수를 투명하게 전송하기 위한 방법 및 디바이스
US6731654B1 (en) Communication system overhead channel
WO2019128665A1 (fr) Procédé de transmission de données, dispositif de communication et support de stockage
WO2023109424A1 (fr) Procédé de transmission de données et dispositif associé
US20220021472A1 (en) CPRI Data Block Transmission Method and Apparatus
WO2019100982A1 (fr) Procédé et dispositif de transmission de données
WO2023035776A1 (fr) Procédé de communication, appareil correspondant et support de stockage
WO2021115215A1 (fr) Procédé de transmission de données, dispositif de communication et support d'enregistrement
JP7167345B2 (ja) データ伝送方法、通信機器、および記憶媒体
CN113472826A (zh) 一种业务承载、提取方法、数据交换方法及设备
WO2024032269A1 (fr) Procédé de communication, appareil associé et support de stockage lisible par ordinateur
WO2023141777A1 (fr) Procédé de communication et dispositif de réseau
WO2024032191A1 (fr) Procédé et dispositif de traitement de bloc de code de défaut
WO2023143577A1 (fr) Procédé, appareil et système de traitement de trame de données dans un réseau de transport optique
WO2023232097A1 (fr) Procédé et appareil de traitement de données de service
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