WO2022022263A1 - 一种传输数据的方法和设备 - Google Patents

一种传输数据的方法和设备 Download PDF

Info

Publication number
WO2022022263A1
WO2022022263A1 PCT/CN2021/105642 CN2021105642W WO2022022263A1 WO 2022022263 A1 WO2022022263 A1 WO 2022022263A1 CN 2021105642 W CN2021105642 W CN 2021105642W WO 2022022263 A1 WO2022022263 A1 WO 2022022263A1
Authority
WO
WIPO (PCT)
Prior art keywords
sub
client
interface
slot
flexe
Prior art date
Application number
PCT/CN2021/105642
Other languages
English (en)
French (fr)
Inventor
祁云磊
钟其文
朱志刚
刘凯
陈井凤
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to BR112023001387A priority Critical patent/BR112023001387A2/pt
Priority to KR1020237005664A priority patent/KR20230041057A/ko
Priority to CA3187237A priority patent/CA3187237A1/en
Priority to EP21849396.3A priority patent/EP4178297A4/en
Priority to MX2023001056A priority patent/MX2023001056A/es
Priority to JP2023504859A priority patent/JP2023535750A/ja
Publication of WO2022022263A1 publication Critical patent/WO2022022263A1/zh
Priority to US18/155,804 priority patent/US20230155756A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0044—Arrangements for allocating sub-channels of the transmission path allocation of payload
    • 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/03—Protocol definition or specification 
    • 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
    • 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
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/60—Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet

Definitions

  • Embodiments of the present invention relate to the field of communication technologies, in particular, to a method and device for transmitting data, and more particularly, to a method and device for transmitting data in an Ethernet interface or a flexible Ethernet interface.
  • Flex Ethernet (English: Flex Ethernet, FlexE) technology is an interface technology that realizes service isolation and network fragmentation. It has developed rapidly in recent years and has been widely accepted by major standards organizations. Optical Internet Forum (Optical Internet Forum, OIF) released the FlexE standard. FlexE technology implements the media access control (English: Medium Access Control, MAC) layer and the physical link interface layer (also called the FlexE Shim layer in English) by introducing the flexible Ethernet protocol layer (also called the FlexE Shim layer in English) on the basis of IEEE802.3. It can be called the decoupling of PHY) to achieve flexible rate matching.
  • media access control English: Medium Access Control, MAC
  • the physical link interface layer also called the FlexE Shim layer in English
  • Flex Shim schedules and distributes the data of multiple FlexE clients (English: client) to multiple different sub-channels in a time-slot manner to achieve a hard transmission pipeline bandwidth. Isolation, a service data stream can be allocated to one or more time slots, which realizes the matching of various rate services.
  • TDM Time Division Multiplexing
  • the existing FlexE interface technology solves the problem of fixed Ethernet port rate to a certain extent, and the client cross-connect technology solves the problem of too large packet forwarding delay.
  • the existing technology carries low-rate (such as 10Mbps) services, There is a serious waste of channel bandwidth.
  • the present application provides a data transmission method, a communication device, a network device, a communication system, a storage medium, and a computer program product, which solve the problem of serious bandwidth waste when currently carrying services based on the FlexE technology.
  • the utilization rate of channel bandwidth can be greatly improved, especially when carrying low-rate services (eg, M-level low-rate services), the utilization rate of channel bandwidth can be significantly improved, and bandwidth waste can be avoided.
  • the present application newly defines a frame structure of a small-granularity service frame, so that the Ethernet (English: Ethernet, ETH) interface can be used to transmit service data in a time-division multiplexing manner, so that even if the standard FlexE is not supported
  • the ordinary Ethernet interface in the mode can also effectively use the bandwidth of the Ethernet interface to achieve bandwidth isolation.
  • the present application provides a method for transmitting data, characterized in that it is implemented by a first communication device, and the method includes: generating a first data stream, where the first data stream includes a plurality of data code blocks;
  • the plurality of data code blocks include a plurality of first base frames, each first base frame includes a base frame payload, and the base frame payload includes a base frame overhead and a plurality of sub-client (sub-client) sub-slot nets.
  • the multiple sub-client sub-slot payloads include multiple first sub-client sub-slot payloads, and the multiple first sub-client sub-slot payloads include the first sub-client interface.
  • the first data stream is sent through the first interface.
  • the first interface is logically divided into Z sub-client interfaces, and the Z sub-client interfaces include the first sub-client interface.
  • the first interface is a flexible Ethernet user FlexE client interface.
  • the first interface is an Ethernet interface.
  • the first interface is a first flexible Ethernet user FlexE client interface
  • the first communication device further includes a first flexE interface on the sending side
  • the first data stream is sent through the first interface
  • the first data stream is sent through the first flexE interface, wherein the first FlexE interface is logically divided into Multiple FlexE client interfaces, the multiple FlexE client interfaces include the first FlexE client interface.
  • each first base frame further includes a first code block and a second code block
  • the first code block is used to indicate the frame header of the first base frame
  • the second code block is used to indicate the frame header of the first base frame. to indicate the end of the first base frame.
  • the first code block is an S code block
  • the second code block is a T code block
  • the first code block includes a first indication field and a first data field, the first indication field is used to indicate the frame header, and the first data field is used to carry the base frame payload part of the data.
  • the second code block includes a second indication field and a second data field, the second indication field is used to indicate the frame trailer, and the second data field is used to carry the base frame payload part of the data.
  • the formats of the first code block and the second code block conform to the code block format defined by the IEEE 802.3 standard of the Institute of Electronic Engineers.
  • the base frame overhead includes one or more pieces of information:
  • the first interface is divided into M sub-slots in the time domain, where M is an integer greater than 1.
  • the slot bandwidth of each of the M sub-slots is P, where P ⁇ 5 gigabits/second Gbp/s,.
  • the M sub-slots are evenly distributed in X first base frames, each time M/X sub-slots are scheduled, a base frame encapsulation is performed, and each of the base frame payloads includes M/X subs.
  • -client subslot payload, X is an integer greater than 1.
  • the transmission rate of the first interface is N Gbps/s, and N is greater than or equal to 1.
  • the method further includes:
  • the first sub-client sub-slot mapping table sent by the second communication device, where the first sub-client sub-slot mapping table is used to indicate the relationship between the M sub-slots and the Z sub-client interfaces
  • the first mapping relationship, each of the sub-client interfaces maps at least one sub-slot in the M sub-slots;
  • the first sub-client sub-slot mapping table indicates the first mapping relationship by mapping Z sub-user identifiers sub-client IDs and M sub-slot identifiers sub-slot IDs, wherein the The Z sub-client IDs are respectively used to indicate the Z sub-client interfaces, and the M sub-slot IDs are respectively used to indicate the M sub-slots.
  • the second communication apparatus is a control and management device.
  • the second communication device is a forwarding device.
  • the first sub-client sub-slot mapping table is carried in the base frame overhead; or, the first sub-client sub-slot mapping table is carried in the M sub-slots. in the specified subslot.
  • the first data stream is used to bear Ethernet services.
  • the generating the first data stream includes:
  • the multiple Ethernet service slices are encapsulated in the base frame payload as the multiple sub-user sub-client sub-slot payloads.
  • the first Ethernet service data stream includes at least one OAM code block.
  • the first Ethernet service data stream includes multiple 64B/66B code blocks or multiple 64B/65B code blocks or multiple 256B/257B code blocks.
  • the first data stream is used to carry a fixed bit stream (English: constant bit rate, CBR) service.
  • a fixed bit stream English: constant bit rate, CBR
  • the generating the first data stream includes:
  • each of the CBR service slices includes the CBR service slice data and encapsulation information
  • the slicing granularity of each CBR service slice is i bits, the contents of the multiple CBR service frames are not identified when slicing the first CBR service data stream, and i is an integer.
  • the slice granularity of each CBR service slice is j complete CBR service frames, and j is an integer greater than or equal to 1.
  • the CBR service slice includes a first field for carrying the CBR service slice data.
  • the encapsulation information includes a second field, and the second field is used to carry clock frequency information.
  • the encapsulation information includes a third field, where the third field is used to carry operation, management and maintenance (English: operation, administration and maintenance, OAM) information.
  • OAM operation, administration and maintenance
  • the encapsulation information includes a fourth field, where the fourth field is used to carry the sequence number of the CBR service slice.
  • sequence number of the CBR service slice is used for slice reassembly.
  • the encapsulation information includes a fifth field, and the fifth field is used to carry payload length information, and the payload length information is the valid value of the CBR service slice data carried in each of the CBR service slices. length.
  • the encapsulation information includes a sixth field, and the sixth field is a padding field.
  • the encapsulation information includes a seventh field, where the seventh field is used to carry verification information.
  • obtaining the multiple sub-user sub-client sub-slot payloads according to the multiple CBR service slices including:
  • the second data stream includes multiple 64B/66B code blocks or multiple 64B/65B code blocks or multiple 256B/257B code blocks.
  • the first data stream includes multiple OAM code blocks for carrying OAM information.
  • obtaining the multiple sub-user sub-client sub-slot payloads according to the multiple CBR service slices including:
  • Each of the CBR service slices is directly used as a sub-user sub-client sub-slot payload.
  • the first data stream includes multiple 64B/66B code blocks or multiple 64B/65B code blocks or multiple 256B/257B code blocks.
  • the first sub-client interface is mapped to W sub-slots of the first interface, and the generating the first data stream includes:
  • the multiple first sub-client sub-slot payloads are respectively mapped to the W sub-slots, where W is an integer greater than 1.
  • the multiple first sub-client sub-slot payloads are respectively mapped to the W sub-slots, including:
  • the W sub-slots are scheduled in sequence.
  • the first communication device includes a second sub-client interface on the receiving side, and the generating the first data stream includes:
  • the multiple second sub-client sub-slot payloads are processed to obtain the multiple second sub-client sub-slot payloads.
  • the multiple first sub-client sub-slot payloads are encapsulated in the base frame payload.
  • acquiring multiple second sub-client sub-slot payloads of the second sub-client interface including:
  • the second interface is divided into A sub-slots in the time domain, the second interface is logically divided into B sub-client interfaces, and the B sub-client interfaces include the second sub-client interface interface, and the second sub-slot time slot table is used to indicate the second mapping relationship between the A sub-slots and the B sub-client interfaces.
  • a and B are both integers. For the value of A, reference may be made to the relevant description of the value of M in this application.
  • the second interface is an Ethernet interface.
  • the second interface is a second FlexE Cilent interface.
  • the first communication apparatus further includes a second FlexE interface on the receiving side, and the acquiring the third data stream includes:
  • the second FlexE interface is logically divided into multiple FlexE client interfaces, and the multiple FlexE client interfaces include the second FlexE client interface;
  • the present application provides a first communication device, characterized in that it includes:
  • the present application provides a computer-readable storage medium, which is characterized in that it includes a program or an instruction that, when executed on a computer, causes the computer to execute the first aspect and any optional implementation manner method described in.
  • the present application provides a communication system, including a first communication device and a second communication device in the claims, the first communication device is configured to execute the first aspect and any one of the optional implementation manners. Methods.
  • the present application provides a program product, which is characterized in that it includes a program or an instruction that, when running on a computer, causes the computer to execute the first aspect and any of the optional implementation manners. Methods.
  • Figure 1 is a schematic diagram of the general architecture of FlexE based on the flexible Ethernet protocol
  • FIG. 2 is a schematic diagram of the time slot allocation of a FlexE Group spanning 4 physical link interfaces (aggregating 4 PHYs);
  • FIG. 3 is a schematic diagram of an application scenario of the FlexE communication system involved in the application.
  • FIG. 4 is a schematic diagram of a process of transmitting data using the FlexE technology involved in the application
  • Figure 5 is a schematic structural diagram of the overhead frame and overhead multiframe of the 100GE interface given in the OIF IA-FLEXE-02.1 standard;
  • Figure 6 is a schematic diagram of time slot allocation of multiple FlexE Clients when N 100G PHYs are bundled;
  • FIG. 7 is a schematic diagram of a base frame encapsulation process provided by the present application.
  • Fig. 8 is the code block format defined by IEEE802.3
  • FIG. 9 is a schematic diagram of a data structure based on sub-client interface transmission provided by the present application.
  • FIG. 10 is a schematic diagram of a format of a multiframe encapsulation provided by the application.
  • FIG. 11 is a schematic diagram illustrating the format of a multiframe provided by the application.
  • FIG. 12 is a schematic flowchart of a method for obtaining the sub-client sub-slot payload of an Ethernet service provided by the present application
  • FIG. 13 is a schematic flowchart of a method for obtaining a sub-client sub-slot payload of a CBR service provided by the present application
  • FIG. 14 is a schematic flowchart of a specific method for obtaining the sub-client sub-slot payload of a CBR service provided by the present application;
  • FIG. 15 is a schematic flowchart of another specific method for obtaining the sub-client sub-slot payload of a CBR service provided by the present application.
  • 16 is a schematic diagram of a method for transmitting data provided by the application.
  • 17 is a schematic diagram of a method for configuring a sub-client sub-slot mapping table provided by this application.
  • FIG. 18 is a schematic diagram of another method for configuring a sub-client sub-slot mapping table provided by the present application.
  • 19 is a schematic diagram of a method for sending a sub-client service data stream provided by the present application.
  • 20 is a schematic diagram of a method for transmitting Ethernet services based on a flexE interface provided by this application;
  • 21 is a schematic diagram of a method for transmitting a CBR service based on a flexE interface provided by this application;
  • 22 provides a schematic diagram of the first method for transmitting an Ethernet service based on an Ethernet interface for the application
  • FIG. 23 is a schematic diagram of a method for transmitting a CBR service based on an Ethernet interface provided by the application;
  • 24 is a schematic structural diagram of a communication device provided by the application.
  • 25 is a schematic structural diagram of a communication device provided by the application.
  • 26 is a schematic structural diagram of a communication device provided by the application.
  • FIG. 27 is a schematic structural diagram of a communication device provided by this application.
  • ordinal numbers such as “1”, “2”, “3”, “4", “first”, “second”, “third” and “fourth” are used to distinguish different objects , not used to limit the order of multiple objects.
  • the terms “including” and “having” are not exclusive.
  • a process, method, system, product or device comprising a series of steps or units is not limited to the listed steps or units, and may also include unlisted steps or units.
  • 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 exemplarily shows a schematic diagram of the general architecture of FlexE based on the flexible Ethernet protocol.
  • the FlexE Group includes 4 PHYs.
  • a FlexE Client represents a client data stream transmitted in a specified timeslot (one timeslot or multiple timeslots) on a FlexE Group.
  • a FlexE Group can carry multiple FlexE Clients, and a FlexE Client can correspond to one or more user service data streams.
  • 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, thereby realizing PHY bundling, channelization, and sub-rate functions.
  • FlexE group also called FlexE Group in English
  • FlexE Shim layer can divide each 100GE PHY in the FlexE Group into 20 data-carrying channels of time slots (slots), and the bandwidth corresponding to each slot is 5Gbps.
  • FIG. 2 schematically shows a schematic diagram of the time slot allocation of a FlexE Group across 4 physical link interfaces (aggregating 4 PHYs).
  • each PHY has 20 time slots, so the FlexE Group has 20*4 time slots.
  • the FlexE Group in Figure 1 includes four PHYs as an example. The four PHYs are PHY A 1201, PHY B 1202, PHY C 1203, and PHY D 1204.
  • a time slot allocation table corresponding to a FlexE Group also called a calendar in English
  • a time slot mapping table corresponding to a single physical link included in a FlexE Group may be called a sub-slot allocation table (may be called a sub-calendar in English).
  • a FlexE calendar can consist of one or more sub-calendars.
  • Each sub-calendar can indicate how the 20 time slots (slots) on the single physical link are allocated to the corresponding FlexE client. That is to say, each sub-calendar can indicate the corresponding relationship between the time slot and the FlexE client on the single physical link.
  • each PHY can correspond to 20 time slots, which are represented by slot 0 to slot 19 in the figure.
  • FIG. 2 shows a schematic diagram of 20 time slots corresponding to each PHY in PHY A 1201, PHY B 1202, PHY C 1203, and PHY D 1204, respectively.
  • FIG. 3 shows a schematic diagram of an application scenario of the FlexE communication system involved in the present application.
  • the FlexE communication system 100 includes a network device 1 , a network device 2 , a user equipment 1 and a user equipment 2 .
  • the network device 1 may be an intermediate node, at which 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, in which case the network device 1 is directly connected with the user equipment 1 .
  • the network device 1 may be an intermediate node, and in this case, the network device 1 is connected to the user equipment 1 through other network devices.
  • the network device 1 may also be an edge node, and in this case, the network device 1 is directly connected to the user equipment 1 .
  • the network device 2 may be an intermediate node, and at this time, 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, and in this case, the network device 2 is directly connected to the user equipment 2 .
  • Network device 1 includes FlexE interface 1
  • network device 2 includes FlexE interface 2 .
  • FlexE interface 1 is adjacent to FlexE interface 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 direction of the service data in the forward channel shown in FIG. 3 is shown by the solid line arrow in FIG.
  • the transmission channel in the embodiment of the present invention 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. 3 only exemplarily shows two network devices and two user equipments, and the network may include any other number of network devices and user equipments, which is not limited in this embodiment of the present application.
  • the FlexE communication system shown in FIG. 3 is only for illustration, and the application scenario of the FlexE communication system provided by the present application is not limited to the scenario shown in FIG. 3 .
  • the technical solutions provided in this application are applicable to all network scenarios in which the FlexE technology is used for data transmission.
  • PHY1, PHY2, PHY3 and PHY4 are bound into a FlexE group.
  • the network device 1 and the network device 2 are connected through the FlexE group interface, that is, through the FlexE interface 1 and the FlexE interface 2.
  • the above-mentioned FlexE group interface may also be called a FlexE interface.
  • a FlexE group interface is a logical interface bound by a group of physical interfaces.
  • the FlexE group interface carries a total of 6 clients, namely client1 to client6. Among them, the data mapping of client1 and client2 is transmitted on PHY1; the data mapping of client3 is transmitted on PHY2 and PHY3; the data mapping of client4 is transmitted on PHY3; the data mapping of client5 and client6 is transmitted on PHY4.
  • Different FlexE clients are mapped and transmitted on the FlexE group to realize the bundling function. in:
  • FlexE group It can also be called a bundled group.
  • the multiple PHYs included in each FlexE group are logically bundled.
  • the so-called logical binding relationship means that there may be no physical connection relationship between different PHYs. Therefore, multiple PHYs in a FlexE group can be physically independent.
  • the network device in FlexE can identify which PHYs are included in a FlexE group through the PHY number, so as to realize the logical bundling of multiple PHYs.
  • the number of each PHY can be identified by a number between 1 and 254, and 0 and 255 are reserved numbers.
  • a PHY number corresponds to an interface on a network device. The same number should be used between two adjacent network devices to identify the same PHY.
  • the numbers of the individual PHYs included in a FlexE group do not have to be consecutive. Normally, there is one FlexE group between two network devices, but this application does not limit that there is only one FlexE group between two network devices, that is, there may also be multiple FlexE groups between two network devices.
  • One PHY can be used to carry at least one client, and one client can transmit on at least one PHY.
  • FlexE client Corresponds to various user interfaces or bandwidths of the network. FlexE client can be flexibly configured according to bandwidth requirements, and supports Ethernet MAC data streams of various rates (such as 10G, 40G, n*25G data streams, and even non-standard rate data streams). The data stream is passed to the FlexE shim layer. Clients sent through the same FlexE group need to share the same clock, and these clients need to be adapted according to the assigned slot rate.
  • the FlexE client interface described in this application is used to transmit the business data stream of the corresponding FlexE client.
  • the FlexE client interface is a logical interface. Each FlexE interface can be logically divided into one or more FlexE client interfaces, each FlexE interface can be divided into multiple time slots in the time domain, and each FlexE client interface occupies at least one of the multiple time slots time slot.
  • FlexE shim As an additional logical layer inserted between the MAC and PHY (PCS sublayer) of the traditional Ethernet architecture, it is the core architecture for implementing FlexE technology based on the calendar's time slot distribution mechanism.
  • the main function of FlexE shim is to slice data according to the same clock, and encapsulate the sliced data into pre-divided time slots. Then, according to the preconfigured time slot allocation table, the divided time slots are mapped to the PHYs in the FlexE group for transmission. Among them, each time slot is mapped to one PHY in the FlexE group.
  • Calender Time slot allocation table, also known as time slot table.
  • a FlexE Group corresponds to a calendar, and a time slot mapping table corresponding to a single physical link (PHY) included in a FlexE Group may be called a sub-slot allocation table (English: sub-calendar).
  • a FlexE calendar can consist of one or more sub-calendars. Each sub-calendar can indicate how the 20 time slots (can be written as slot in English) on the single physical link are allocated to the corresponding FlexE client. That is to say, each sub-calendar can indicate the corresponding relationship between the time slot and the FlexE client on the single physical link.
  • two Calenders are specified in each FlexE overhead frame, namely the current main slot table (Calender A) and the backup slot table (Calender B).
  • FlexE constructs a fixed frame format for physical interface transmission and divides time slots for TDM.
  • the FlexE shim layer reflects the time slot mapping relationship between the client and the FlexE group and the calendar working mechanism by defining overhead frames and overhead multiframes.
  • the above-mentioned overhead frame may also be called a flexible Ethernet overhead frame (English: FlexE overhead frame), and the above-mentioned overhead multiframe may also be called a flexible Ethernet overhead multiframe (English: FlexE overhead Multiframe).
  • the FlexE shim layer provides an in-band management channel through overhead, supports the transfer of configuration and management information between the two connected FlexE interfaces, and realizes the establishment of automatic link negotiation.
  • the data on each PHY of FlexE is aligned by periodically inserting code blocks of the FlexE overhead frame (OH) frame.
  • OH FlexE overhead frame
  • a 66B overhead code can be inserted every 1023x 20 66B payload data blocks.
  • Block FlexE OH According to the FlexE Implementation Agreement, a FlexE Group will send a 64B/66B code block of a FlexE overhead frame to the remote PHY every predetermined time interval on each PHY, and 8 64B/66B blocks of FlexE overhead frames sent in sequence.
  • the 66B code block constitutes a FlexE overhead frame.
  • FIG. 5 shows a schematic structural diagram of the overhead frame and overhead multiframe of the 100GE interface given in the OIF IA-FLEXE-02.1 standard.
  • An overhead frame has 8 overhead blocks (English: overhead block), and the above-mentioned overhead blocks may also be called overhead time slots (English: overhead slot).
  • Each overhead block is a 64B/66B encoded code block, which occurs once every 1023*20blokcs, but the fields contained in each overhead block are different.
  • the first overhead block contains the control character "0x4B" and the "O code” character of "0x5".
  • the control character and the "O code” are passed between the docked FlexE interfaces.
  • a character match determines the first overhead frame.
  • 32 overhead frames form an overhead multiframe.
  • each PHY includes 20 5G time slots, and there are N*20 5G time slots when N PHYs are bundled.
  • the bandwidth allocated by each FlexE Client must be an integer of 5G times, the minimum bandwidth is 5G, that is, at least one time slot is allocated.
  • the timeslot bandwidth of each timeslot is 5G
  • FlexE client#1 allocates x timeslots
  • FlexE client#2 allocates y timeslots
  • ... FlexE#M allocates z timeslots.
  • there are many low-speed services in the current application layer such as the related services of bank automatic teller machines (English: automatic teller machine, ATM), which require very low bandwidth, which may only require 100Mbps.
  • bank automatic teller machines International: automatic teller machine, ATM
  • the present application redefines a sub-client interface with a smaller granularity on the basis of the existing FlexE interface or the common Ethernet physical interface.
  • the interface rate of each sub-client interface can be flexibly set according to the requirements of different low-rate services, so as to avoid wasting bandwidth as much as possible.
  • the present application also provides a sub-slot crossover technology. On the basis of fully utilizing the bandwidth, forwarding is performed inside the device based on the time slot crossover technology, which can effectively reduce the forwarding delay.
  • Sub-slots can also be referred to as low-order time slots. Compared with the time slot (also called large time slot or high-order time slot) configured on the existing FlexE Client interface or the large bandwidth of the common ETH interface. For a standard FlexE Client interface or a common ETH interface, each FlexE Client interface or ETH interface is divided into M sub-slots in the time domain, and each sub-user interface occupies at least one sub-slot bandwidth for data transmission.
  • FlexE sub-shim based on the sub-slot distribution mechanism, slices the data of the same sub-client, and encapsulates the switched data as sub-slot payload in pre-divided sub-slots. Then, according to the pre-acquired sub-client sub-slot mapping table, map each divided sub-slot to the corresponding FlexE Client interface. Among them, each sub-slot is mapped to a FlexE client interface.
  • Sub-users sub-clients, corresponding to various sub-user interfaces or bandwidths of the network.
  • FlexE sub-client can be flexibly configured according to bandwidth requirements, and supports Ethernet MAC data streams of various rates (such as 10G, 40G, n*25G data streams, and even non-standard rate data streams), such as 64B/66B or 64B/ 65B transcoding or 256B/257B transcoding to pass the data stream to the FlexE sub-shim layer.
  • Sub-user interface sub-Client interface.
  • the sub-user interface may also be referred to as a sub-slot interface, a lower-order slot interface sub, a sub-slot channel, or a lower-order slot channel.
  • the sub-user interface is a concept relative to the existing FlexE Client interface or ordinary Ethernet interface.
  • Each FlexE Client interface or common Ethernet interface is logically divided into multiple sub-user interfaces, and is divided into multiple sub-slots in the time domain, each sub-user interface occupies at least one sub-slot for data transmission, and each sub-slot
  • the granularity of the time slot bandwidth is usually less than 5Gbps, for example, it can be any value between 10Mbps and 100Mbps, so as to carry more low-rate services and effectively utilize the bandwidth.
  • the sub-client sub-slot payload is the data obtained by slicing the same sub-client data.
  • Each slice is encapsulated in a pre-divided sub-slot as a sub-client sub-slot payload.
  • Sub-Client sub-slot mapping table It can also be referred to as a low-order channel time slot allocation table, a Sub-Client sub-slot allocation table, and a low-order channel time slot mapping table. It is used to identify the number of timeslots and timeslot positions allocated to each Sub-Client sub-interface.
  • Base frame a data structure provided by this application, which is used to carry service data streams of different sub-clients.
  • Each base frame includes base frame payload.
  • the payload of the base frame includes the overhead of the base frame and the payload of the lower-order slot (ie, the payload of the sub-client sub-slot).
  • each low-order slot payload has the same length, eg, may be Y bits.
  • Each lower order slot payload can be multiple 64B/66B code blocks.
  • the payload of each low-order time slot may be multiple 64B/65B code blocks or 256B/257B code blocks, wherein the multiple 64B/65B code blocks or 256B/257B code blocks may be It is obtained by transcoding and compressing multiple 64B/66B code blocks encoded by PCS by using a transcoding algorithm, and the forwarding algorithm may be, for example, 64B/65B transcoding or 256B/257B transcoding.
  • the base frame overhead is used to transmit overhead information, and the overhead information may include but is not limited to one or more of the following information:
  • the sequence number of the base frame can be used to identify the position of the base frame in the entire multiframe, and the subslot number loaded in the base frame can be known according to the position information.
  • the Sub-Client sub-slot mapping table can be used to identify the number of timeslots and timeslot positions allocated to each low-order channel.
  • the time slot adjustment request is used to send a time slot adjustment request, for example, to adjust the time slot of a sub-client
  • the time slot adjustment response is a response to receiving the time slot adjustment request
  • the time slot effective indication is used to indicate that the time slot adjustment is effective.
  • the management message channel can be used to transmit network element management messages, and can also be used to transmit Sub-Client sub-slot mapping table information.
  • the overhead check information is used to check the base frame overhead, and the check algorithm may be, but not limited to, select error detection algorithms such as CRC or BIP.
  • the sub-client sub-slot payload is used to carry data of different Sub-Client interfaces according to the Sub-Client sub-slot mapping table.
  • Each base frame also includes a code block for defining the base frame header and a code block for defining the base frame trailer.
  • FIG. 7 shows a schematic diagram of a specific base frame encapsulation format provided by the present application, but those skilled in the art can understand that FIG. 7 should not be construed as a limitation on the base frame encapsulation format.
  • the base frame is encapsulated with /S/ code block, /D/ code block and /T/ code block.
  • the /S/ code block is used to indicate the frame header of the base frame.
  • the /T/ code block is used to indicate the end of the base frame.
  • the data field of the /D/ code block (the Block payload field shown in Figure 7 or Figure 8) is used to carry the base frame payload.
  • the /I/ code block may be used for rate adaptation of the base frame.
  • the format of each code block in the base frame may, for example, comply with the code block format defined by IEEE802.3 as shown in FIG. 8 .
  • some or all of the data fields (block payload, BP) in the /S/ code block and/or /T/ code block and the data fields of the /D/ code block jointly carry the base frame payload, wherein
  • the BP in the S code block is an optional field segment
  • the T code can be any one of the seven code blocks T0-T7.
  • FIG. 9 is a schematic diagram of a data structure transmitted by a sub-user interface provided by the present application.
  • M sub-slots are divided for cyclic transmission in a FlexE Client interface or a common ETH interface with a bandwidth of N*5G. That is, each cyclic period is M sub-slots, and the cyclic period may also be referred to as a sub-user interface sub-slot scheduling period or a sub-user interface timeslot scheduling period.
  • X base frames are evenly distributed on the M sub-slots, and (M/X) low-order time slots are loaded in the payload of each base frame. Every X base frame can also be defined as a multiframe. In each cycle period, one multiframe is transmitted. In a specific implementation, according to the regulations for transmitting Ethernet packets, the length of the multiframe should be less than or equal to 9600 bytes.
  • each FlexE interface can be logically divided into multiple FlexE Client interfaces.
  • a FlexE Client interface can be logically divided into multiple FlexE sub-client interfaces, and a FlexE Client interface can be divided into M sub-slots in the time domain.
  • M can be flexibly configured for the bandwidths of different FlexE sub-client interfaces.
  • each time slot scheduling period of a FlexE Client interface (480 sub-slots are one time slot scheduling period), 20 base frames are evenly distributed, that is, a multi-frame.
  • the English name of the base frame is fgDu.
  • Each base frame contains 24 subslots.
  • each sub-slot payload may contain 8 66b compressed code blocks.
  • the base frame can contain 197 66B code blocks.
  • /I/ code blocks can be added between base frames, or some /I/ code blocks can be replaced by OAM code blocks transmitted in the FlxeE client interface. .
  • the /I/ code block is an idle code block, which is used for MAC layer rate adaptation.
  • FIG. 11 shows a schematic diagram of a format description of a multiframe provided by the present application.
  • FIG. 11 can be used to further illustrate the multiframe structure shown in FIG. 10 .
  • Small particle slot 1 to small particle slot 480 described in FIG. 11 correspond to sub-slot 1 to sub-slot 480, respectively.
  • a multiframe includes 480 sub-slots, each base frame includes 24 sub-slots, and each sub-slot includes 8 66B compressed code blocks, that is, 8 65B code blocks.
  • the code block compression process is shown in Figure 11. After OAM code blocks are periodically inserted into the 66B code block stream, code block compression is performed. After compression, each sub-slot includes 8 65B code blocks.
  • some fields in the base frame overhead may be used to carry data. For example, if the base frame overhead requires only 56 bits, the remaining 8 bits of each base frame overhead can be used to carry data.
  • the first field in the code block used to identify the frame end may be used to indicate the frame end
  • the second field may be used to carry data.
  • the controller in the T code block shown in FIG. 11 indicates the end of the frame
  • the following describes a method 100 for obtaining an Ethernet service sub-client sub-slot payload provided by the present application with reference to FIG. 12 .
  • the method includes: obtaining an Ethernet service data stream from a PCS; Slicing is performed to obtain multiple Ethernet service slices; and the multiple Ethernet service slices are used as the payload of the multiple sub-user sub-client sub-slots.
  • Slicing is performed to obtain multiple Ethernet service slices; and the multiple Ethernet service slices are used as the payload of the multiple sub-user sub-client sub-slots.
  • how to obtain the Ethernet service data stream is described in conjunction with S101-S103 in FIG. 12 , and how to slice the Ethernet service data stream for the multiple sub-user sub-client sub-slots described in conjunction with S104 payload.
  • S101 The PCS encodes the MAC layer Ethernet packet.
  • each low-order channel that is, each sub-client interface
  • the MAC layer implements the encapsulation and verification processing of service packets
  • the PCS performs 64B/66B encoding on the MAC layer packets, that is, the Ethernet service data stream, according to the 802.3 encoding method.
  • the encoded code block stream includes S code block, D code block, T code block, and I code block (ie IDLE code block, also called idle code block).
  • the code block format follows the standard code block format defined by IEEE802.3. .
  • S102 Insert a low-order channel layer OAM code block into the code block stream encoded by the PCS to obtain the Ethernet service data stream.
  • the OAM code block is used to transmit OAM information.
  • adjacent /I/ code blocks can be selected to be inserted into the OAM code blocks after a period of time (such as 3.3ms) or a certain number of code blocks (such as 500).
  • the OAM information may be, for example, an OAM message, and reference may be made to the MTN channel layer OAM format defined by the ITU G.MTN standard.
  • the compressed code block stream includes multiple 64B/65B code blocks. In a specific implementation, the compressed code block stream includes multiple 256B/257B code blocks.
  • Transcoding and compressing the code block stream can improve the data carrying efficiency of the low-order channel, and the transcoding algorithm can be 256B/257B transcoding.
  • FIG. 12 only shows the 64B/65B transcoding, and the 256B/257B transcoding is similar to the original, and will not be repeated here.
  • S104 Slice the Ethernet service data stream (or may also be referred to as a code block stream) according to the payload length (Y bits) of each sub-client sub-slot.
  • the payload length of each sub-client sub-slot can be Z 64B/66B code blocks. If transcoding is done, it can also be Z transcoded 64B/65B code blocks or Z 256B/257B code blocks. Both Y and Z are integers.
  • Each slice obtained through the slice operation of S104 will be encapsulated into the base frame Payload as a sub-client sub-slot payload.
  • the base frame payload and the related format of the base frame see the above description, and will not be repeated here.
  • a method 200 for obtaining a sub-client sub-slot payload of a fixed bit rate (English: constant bit rate, CBR) provided by the present application will be introduced below with reference to FIG. 13 .
  • the first CBR service data stream includes multiple CBR service frames.
  • Bit transparent slicing mode does not identify the content of the service frame, and performs slicing according to a fixed number of bits (eg i bits).
  • Mode two frame slice mode.
  • the service frame format needs to be identified, and slicing is performed according to a fixed number of frames (eg, j frames).
  • each of the CBR service slices includes the CBR service slice data and encapsulation information.
  • each CBR service slice includes multiple fields, which are respectively used to carry CBR service slice data and encapsulation information.
  • the CBR service slice includes a first field for carrying the CBR service slice data.
  • the encapsulation information includes any one or more fields from the second field to the seventh field, which are used to carry different encapsulation information.
  • the clock frequency information may include, for example, information such as a time stamp, which is used to transmit the clock information of the service.
  • the third field is used to carry the operation, management and maintenance of OAM information.
  • the fourth field is used to carry the sequence number of the CBR service slice; the sequence number of the CBR service slice can, for example, be used for slice reassembly, and the sequence number of the CBR service slice can also be used for slice loss detection or lossless protection.
  • the fifth field is used to carry payload length information
  • the payload length information is the effective length of the CBR service slice data carried in each of the CBR service slices.
  • the sixth field is a padding field.
  • the padding field can be used for data padding.
  • the seventh field where the seventh field is used to carry verification information.
  • the verification information can be used to perform error checking on slice data, but the present application is not limited to including verification information in the slice, and the verification function can also be performed in other ways, such as using OAM to perform verification.
  • the multiple CBR service slices can be directly used as the multiple sub-client sub-slot payloads, that is, the length of each CBR service slice obtained after encapsulation and the length of each sub-client
  • the client subslot payload remains the same, eg, all Y bits.
  • a specific example will be given to illustrate this manner below with reference to FIG. 14 .
  • obtaining the multiple sub-user sub-client sub-slot payloads according to the multiple CBR service slices includes:
  • FIG. 14 shows a schematic diagram of a method for obtaining a sub-client sub-slot payload of a CBR service provided by the present application, and the method 1400 can be used to implement the method 200 specifically.
  • the method includes:
  • S1402. Encapsulate the data of each service slice.
  • the encapsulated slice length is the same as the payload length of the low-order time slot (eg, Y bits).
  • Package information includes one or more of the following:
  • OAM information (optional) for CBR low-order path layer fault detection and protection operations.
  • Clock frequency information used to transmit the clock information (such as time stamp) of the service.
  • the payload length and padding are optional. If the encapsulated service slice is smaller than the payload length of the low-order timeslot, data padding is required and the effective payload length is marked.
  • the check field which is optional, is used to perform bit error check on slice data. This check function can also be checked by OAM.
  • FIG. 15 shows a schematic diagram of a method for obtaining the sub-client sub-slot payload of a CBR service provided by the present application, and the method 1500 can be used to specifically implement the method 200 .
  • the method 1500 includes:
  • the slicing mode adopts the mode 1 or mode 2 described above.
  • S1502. Encapsulate the slice data block.
  • Package information includes one or more of the following:
  • OAM information (optional) for CBR low-order path layer fault detection and protection operations.
  • Clock frequency information used to transmit the clock information (such as time stamp) of the service.
  • the payload length and padding are optional. If the encapsulated service slice is smaller than the payload length of the low-order timeslot, data padding is required and the effective payload length is marked.
  • the check field which is optional, is used to perform bit error check on slice data. This check function can also be checked by OAM.
  • the OAM information may be, for example, an OAM message, and reference may be made to the MTN channel layer OAM format defined by the ITU G.MTN standard.
  • the compressed code block stream includes multiple 64B/65B code blocks. In a specific implementation, the compressed code block stream includes multiple 256B/257B code blocks.
  • Transcoding and compressing the code block stream can improve the data carrying efficiency of the low-order channel, and the transcoding algorithm can be 256B/257B transcoding.
  • FIG. 12 only shows the 64B/65B transcoding, and the 256B/257B transcoding is similar to the original, and will not be repeated here.
  • each sub-client sub-slot can be Z 64B/66B code blocks. If transcoding is done before slicing, it can also be Z transcoded 64B/65B code blocks or Z 256B/257B code blocks Transcode. Both Y and Z are integers.
  • Each slice obtained through the slice operation of S1056 will be encapsulated into the base frame Payload as a sub-client sub-slot payload.
  • the base frame payload and the related format of the base frame see the above description, and will not be repeated here.
  • the above describes the encapsulation format and encapsulation process of the base frame provided by the present application, and also introduces the method for obtaining the sub-client sub-slot payload of the Ethernet service or the sub-client sub-slot payload of the CBR service.
  • a method 1600 for transmitting data provided in this application will be introduced with reference to FIG. 16 .
  • the method is performed by a first communication device, the first communication device includes a first interface, and the method includes:
  • the plurality of data code blocks include a plurality of first base frames, each first base frame includes a base frame payload, and the base frame payload includes a base frame overhead and a plurality of sub-user sub-client sub-times slot payload, the multiple sub-client sub-slot payloads include multiple first sub-client sub-slot payloads, and the multiple first sub-client sub-slot payloads include the first sub-client Interface business data.
  • the first interface is divided into M sub-slots in the time domain.
  • M is an integer greater than 1.
  • the time slot bandwidth of each sub-slot in the M sub-slots is P, preferably P ⁇ 5 gigabits/second Gbp/s, more preferably P is less than or equal to 1 Gbp/s s, more preferably, P is less than or equal to 500Mbp/s.
  • P is preferably less than or equal to 100 Mbp/s.
  • the first interface is logically divided into Z sub-client interfaces, and the Z sub-client interfaces include the first sub-client interface.
  • the first interface is a first flexible Ethernet user FlexE client interface.
  • the first communication device further includes a first flexE interface on the sending side, and S1602 specifically includes:
  • the first data stream is sent through the first flexE interface, wherein the first FlexE interface is logically divided into Multiple FlexE client interfaces, the multiple FlexE client interfaces include the first FlexE client interface.
  • the first interface is the first FlexE client interface
  • the first interface is an Ethernet interface.
  • the first data stream is used to carry Ethernet services.
  • generating the first data stream in S1601 includes:
  • the multiple Ethernet service slices are encapsulated in the base frame payload as the multiple sub-user sub-client sub-slot payloads.
  • the first data flow is used to bear the CBR service.
  • the first data stream is generated in S1601, including:
  • the method 1600 further includes: slicing a first CBR service data stream to obtain multiple CBR service slice data, where the first CBR service data stream includes multiple CBR service frames;
  • each of the CBR service slices includes the CBR service slice data and encapsulation information
  • the slicing granularity of each CBR service slice is i bits, and the content of the multiple CBR service frames is not identified when slicing the first CBR service data stream, where i is Integer.
  • the slice granularity of each CBR service slice is j complete CBR service frames, and j is an integer greater than or equal to 1.
  • the CBR service slice includes a first field for carrying the CBR service slice data.
  • the encapsulation information includes a second field, and the second field is used to carry clock frequency information.
  • the encapsulation information includes a third field, and the third field is used for carrying operation, management and maintenance of OAM information.
  • the encapsulation information includes a fourth field, where the fourth field is used to carry the sequence number of the CBR service slice.
  • the sequence number of the CBR service slice is used for slice reassembly.
  • the encapsulation information includes a fifth field, and the fifth field is used to carry payload length information, and the payload length information is the CBR service carried in each of the CBR service slices Valid length of slice data.
  • the encapsulation information includes a sixth field, and the sixth field is a padding field.
  • the encapsulation information includes a seventh field, and the seventh field is used to carry verification information.
  • obtaining the multiple sub-user sub-client sub-slot payloads according to the multiple CBR service slices includes:
  • the second data stream includes multiple 64B/66B code blocks or multiple 64B/65B code blocks or multiple 256B/257B code blocks.
  • the first data stream includes multiple OAM code blocks for carrying OAM information.
  • obtaining the multiple sub-user sub-client sub-slot payloads according to the multiple CBR service slices includes:
  • Each of the CBR service slices is directly used as a sub-user sub-client sub-slot payload.
  • the first data stream includes multiple 64B/66B code blocks or multiple 64B/65B code blocks or multiple 256B/257B code blocks.
  • the method further includes: the first communication device receives a first sub-client sub-slot mapping table sent by the second communication device, the first sub-client sub-slot mapping table is used to indicate the first mapping relationship between the M sub-slots and the Z sub-client interfaces, and each of the sub-client interfaces maps at least one sub-slot in the M sub-slots;
  • the first sub-client sub-slot mapping table indicates the first mapping relationship by mapping Z sub-user identifiers sub-client IDs and M sub-slot identifiers sub-slot IDs,
  • the Z sub-client IDs are respectively used to indicate the Z sub-client interfaces
  • the M sub-slot IDs are respectively used to indicate the M sub-slots.
  • the second communication device may be a control and management device or a forwarding device that performs data communication with the first communication device.
  • the control and management device may be, for example, a network management device or a controller.
  • the forwarding apparatus may be a forwarding apparatus, such as a router, a switch, a firewall, a packet transmission network PTN device, etc., and may also be a single board in a network device.
  • the first sub-client sub-slot mapping table is carried in the base frame overhead.
  • the first sub-client sub-slot mapping table is carried in a designated sub-slot of the M sub-slots.
  • the sub-client sub-slot mapping table provided by this application includes a sub-slot number and a sub-client number, each sub-client can map multiple sub-slots, and the above mapping can also be understood for configuration or occupation. That is, each sub-client sends data through multiple mapped sub-slots. The transmitting end and the receiving end of the communication send and restore (or call demapping) the data transmitted in the corresponding sub-slots according to the same sub-client sub-slot mapping table.
  • the method flow for acquiring the first sub-client sub-slot mapping table by the first communication apparatus is exemplarily described below.
  • FIG. 17 shows a schematic diagram of a method for configuring a sub-client sub-slot mapping table based on a control and management device provided by the present application. As shown in FIG. 17 , both the receiving end and the sending end of the communication are configured by the control and management device respectively.
  • FIG. 18 shows a schematic diagram of a method for configuring a sub-client sub-slot mapping table based on a data path provided by the present application.
  • the control and management device only configures the sub-client sub-slot mapping table of the sender, and the sender transmits it to the receiver through the data path.
  • the data path can be transmitted using the time slot table transmission channel defined in the base frame overhead.
  • the sub-client sub-slot mapping table may also specify a specific sub-slot among the M sub-slots for transmission. If it is a FlexE interface, the sub-client sub-slot mapping table can also be passed through the FlexE overhead. This application does not specifically limit the transmission method of the sub-client sub-slot mapping table with the data path.
  • the first communication device may be a transmitting end device or a receiving end device.
  • the first communication device is used as the receiving end device.
  • the first sub-client interface is mapped to W sub-slots of the first interface, and the generating the first data stream includes:
  • the multiple first sub-client sub-slot payloads are respectively mapped to the W sub-slots, where W is an integer greater than 1.
  • the multiple first sub-client sub-slot payloads are respectively mapped to the W sub-slots, including:
  • the W sub-slots are scheduled in sequence.
  • the mapping relationship between the first sub-client interface and the W sub-slots may be determined according to the first sub-client sub-slot mapping table.
  • the first communication device includes a second sub-client interface on the receiving side, and the generating the first data stream includes:
  • the multiple second sub-client sub-slot payloads are processed to obtain the multiple second sub-client sub-slot payloads.
  • the multiple first sub-client sub-slot payloads are encapsulated in the base frame payload.
  • acquiring multiple second sub-client sub-slot payloads of the second sub-client interface includes:
  • the second interface is divided into A sub-slots in the time domain, the second interface is logically divided into B sub-client interfaces, and the B sub-client interfaces include the second sub-client interface interface, and the second sub-slot time slot table is used to indicate the second mapping relationship between the A sub-slots and the B sub-client interfaces.
  • a and B are both integers.
  • the third data stream corresponds to the high-order channel in the intermediate time slot crossover device NE2 in Fig. 20 to Fig. 23 , that is, the data stream obtained from a client interface or an Ethernet interface.
  • the second interface is an Ethernet interface.
  • the second interface is a second FlexE Cilent interface.
  • the first communication apparatus further includes a second FlexE interface on the receiving side, and the acquiring the third data stream includes:
  • the second FlexE interface is logically divided into multiple FlexE client interfaces, and the multiple FlexE client interfaces include the second FlexE client interface;
  • the plurality of second base frames include the plurality of second sub-client sub-slot payloads therein.
  • the second FlexE interface may be, for example, the FlexE interface on the receiving side shown in FIG. 20 or FIG. 21 .
  • the fourth data stream is the data stream obtained by the FlexE interface on the receiving side.
  • the third data stream shown may be, for example, the data stream corresponding to the high-order channel client-1 shown in FIG. 21 or FIG. 22 .
  • the following describes a specific method 1900 for sending the first data stream through the first interface in the method 1600 provided by the present application with reference to FIG. 19 .
  • S1901 Schedule M sub-slots in sequence.
  • the first interface Flexible Message Service Interface or common ETH interface
  • the TDM time slot scheduler uses the M sub-slots divided by the first interface as a time slot scheduling period, and performs cyclic scheduling.
  • S1902 According to the sequence of sub-slot scheduling, map the payloads of multiple different sub-client sub-slots included in the first data stream to corresponding sub-slots based on the first sub-client sub-slot mapping table. The sub-slot corresponding to the sub-client interface.
  • S1903 Base frame encapsulation.
  • X base frames are evenly distributed in every M sub-slots. Then, every time M/X sub-slots are scheduled, base frame encapsulation is performed once.
  • base frame encapsulation refer to the specific description above, which will not be repeated here.
  • the first interface can be an Ethernet interface or a flexible Ethernet interface, which can be used to carry a common Ethernet service or a CBR service, and the application scenarios of the technical solution are very wide.
  • FIG. 20 shows a schematic flowchart of a method for transmitting Ethernet services based on a flexE interface.
  • Fig. 21 shows a schematic flowchart of a method for transmitting a CBR service based on a flexE interface.
  • FIG. 22 shows a schematic flowchart of a method for transmitting Ethernet services based on an Ethernet interface.
  • Fig. 23 shows a schematic diagram of a method for transmitting a CBR service based on an Ethernet interface.
  • the first communication device described in this application may be the source service access device NE1 shown in any of Figures 20-24, the intermediate time slot crossover device NE2, or the sink service transmission Device NE3.
  • the first communication device may also be a single board in the source-end service access device NE1, the intermediate time slot cross device NE2 or the sink-end service sending device NE3, configured to execute one of the methods corresponding to FIG. 20 to FIG. 23 or multiple operations.
  • a network for communication based on flexE includes three types of devices, namely: a source service access device NE1, an intermediate time slot crossover device NE2, and a sink service transmission device NE3.
  • Source service access device NE1 The receiving side is an Ethernet interface, and the sending side is a FlexE port. After receiving Ethernet packets, the port on the receiving side first completes service processing at the packet layer (such as VLAN, IP, MPLS, SR, etc.), and then maps different service flows to the corresponding lower-order channels according to the Ethernet time slot mapping process.
  • the sub-Client interface described in the application, sub-client1-1...sub-client 1-m shown in Figure 20 is loaded into the high-order channel (that is, the FlexE Client interface described in this application, corresponding to Client 1-1...Client1-n) shown in Figure 20, and finally sent out from the FlexE interface.
  • the above process can refer to the relevant description in the method 100 corresponding to FIG.
  • the TDM time slot scheduler maps the payload of each sub-client sub-slot to the sub-slot corresponding to each sub-client, and then encapsulates the corresponding base frame and sends it from the corresponding Flex-client interface.
  • the mapping process between each Flex-client interface and the corresponding FlexE interface belongs to the existing implementation and will not be repeated here.
  • Both the receiving side and the transmitting side are FlexE interfaces.
  • the low-order channel is demapped according to the sub-client sub-slot table.
  • the low-order exit channel that is, the FlexE Client interface described in this application, corresponding to Fig. Client 2-1...Client2-n
  • the low-order time slot crossing is based on the second sub-client interface on the receiving side (for example, sub-client 1-1 in the NE2 device in FIG. 20 ) and the first sub-client interface on the transmitting side (for example, , the sub-slot cross-relationship between sub-clients 2-1) shown in FIG. 20, the multiple second sub-client sub-slot payloads in the second sub-client interface are processed to obtain the described The multiple first sub-client sub-slot payloads of the first sub-client interface are then encapsulated in the base frame.
  • Sink service sending device NE3 the receiving side is a FlexE port, and the sending side is an Ethernet port. First, demap the low-order channel time slot from the received FlexE high-order channel according to the sub-client sub-slot mapping table, and then restore it to an Ethernet packet according to the Ethernet time slot demapping process. Sent from the Ethernet port on the sending side.
  • the flexE-based communication network includes three types of devices, namely: a source service access device NE1, an intermediate time slot crossover device NE2, and a sink service transmission device NE3.
  • Source-end service access device NE1 The receiving side is a CBR service interface such as E1/E3/T1/T3/STM-N/FC, and the sending side is a FlexE interface. After receiving the CBR service bit stream, the port on the receiving side obtains the CBR service sub-cient sub-slot payload according to any of the methods described in Figure 13 or Figure 14 or Figure 15, and obtains multiple CBR service sub-cient sub-times.
  • CBR service interface such as E1/E3/T1/T3/STM-N/FC
  • FlexE interface FlexE interface
  • the different CBR service flows corresponding to the slot payload are respectively mapped to the corresponding lower-order channels (that is, the sub-Client interface described in this application, the sub-client1-1...sub-client 1-m shown in Figure 21) , and then loaded into the higher-order channel (that is, the FlexE Client interface described in this application, corresponding to Client 1-1...Client1-n shown in Figure 20) and sent from the FlexE interface.
  • the TDM timeslot scheduler can map the sub-Client sub-slot payload of each CBR service to each sub-client.
  • the corresponding base frame is encapsulated and sent from the corresponding Flex-client interface.
  • the mapping process between each Flex-client interface and the corresponding FlexE interface belongs to the existing implementation and will not be repeated here.
  • Intermediate time slot crossover device the same as the middle time slot crossover device shown in Figure 20. It will not be repeated here.
  • the receiving side is a FlexE interface port
  • the sending side is a CBR service interface such as 1/E3/T1/T3/STM-N/FC.
  • the method for transmitting Ethernet services based on the Ethernet interface is briefly introduced below with reference to FIG. 22 .
  • the network for communication based on flexE includes three types of devices, namely: a source service access device NE1, an intermediate time slot cross device NE2, and a sink service transmission device NE3.
  • the main difference between Figure 22 and Figure 20 is that the network-side interface is an ordinary Ethernet interface instead of a FlexE interface.
  • Source service access device NE1 the receiving side is an Ethernet interface, and the transmitting side is an Ethernet interface.
  • the receiving port After receiving the Ethernet packet, the receiving port first completes the packet layer service processing (such as VLAN, IP, MPLS, SR, etc.), and obtains the sub-slot payloads of multiple sub-clients according to the method corresponding to FIG. 12 . Then, based on the method shown in FIG. 19 , the sub-slot payloads of the multiple sub-clients are mapped according to the sub-client sub-slot mapping table. After the base frame is encapsulated, the payload is sent from the corresponding Ethernet interface. .
  • the packet layer service processing such as VLAN, IP, MPLS, SR, etc.
  • Intermediate time slot crossover device NE2 both the receiving side and the sending slave are Ethernet interfaces.
  • the low-order time slot crossing is based on the second sub-client interface on the receiving side (for example, sub-client 1-1 in the NE2 device in Figure 22) and the first sub-client interface on the transmitting side (for example, , the sub-slot cross-relationship between sub-clients 2-1) shown in Figure 22, the multiple second sub-client sub-slot payloads in the second sub-client interface are processed to obtain the described The multiple first sub-client sub-slot payloads of the first sub-client interface are then encapsulated in the base frame.
  • Sink service sending device NE3 the receiving side is an Ethernet interface, and the sending side is an Ethernet interface.
  • the low-order channel time slot is demapped from the Ethernet interface on the receiving side according to the sub-client sub-slot mapping table, and then restored to an Ethernet packet according to the Ethernet time slot demapping process. side Ethernet port.
  • the method for transmitting CBR services based on an Ethernet interface is briefly introduced below with reference to FIG. 23 .
  • the network for communication based on flexE includes three types of devices, namely: a source service access device NE1, an intermediate time slot cross device NE2, and a sink service transmission device NE3.
  • Source-end service access equipment The receiving side is E1/E3/T1/T3/STM-N/FC and other CBR service interfaces, and the transmitting side is an Ethernet interface.
  • the port on the receiving side obtains the CBR service sub-cient sub-slot payload according to any of the methods described in Figure 13 or Figure 14 or Figure 15, and obtains multiple CBR service sub-cient sub-times.
  • the different CBR service flows corresponding to the slot payload are respectively mapped to the corresponding lower-order channels (that is, the sub-Client interface described in this application, the sub-client1-1...sub-client 1-m shown in Figure 23) middle.
  • the sub-slot payloads of the multiple sub-clients are mapped according to the sub-client sub-slot mapping table. After the base frame is encapsulated, the payload is sent from the corresponding Ethernet interface. .
  • Intermediate time slot crossover device the same as the middle time slot crossover device in FIG. 22 . It will not be repeated here.
  • the receiving side is a flexible Ethernet interface
  • the sending side is a CBR service interface such as 1/E3/T1/T3/STM-N/FC.
  • the low-order channel time slots are demapped from the Ethernet interface on the receiving side according to the sub-client sub-slot mapping table, and then restored to the CBR service bit stream according to the CBR time slot demapping process. .
  • the communication apparatus 700 may be applied to the network architecture shown in FIG. 3 .
  • the communication device 700 may be, for example, the network device 1 (TX) or the network device 2 (RX) described in this application, and the communication device 700 may also be the first communication device or the second communication device described in this application.
  • the first communication device and the second communication device described in this application may be an integral network device, or may be a single board in the network device 1, such as an interface board, a line card, a dumb board, or a centralized cross-connect board.
  • the communication apparatus 800 may also be the control management device described in this application, and performs various operations performed by the control management device.
  • the communication apparatus 700 is configured to execute the method of the embodiment corresponding to any one of the foregoing FIG. 6 to FIG. 23 .
  • the communication device 700 includes a transceiving unit 701 and a processing unit 702 .
  • the transceiving unit 701 is used for performing transceiving operations, and the processing unit is used for performing operations other than transceiving.
  • the processing unit 702 is configured to generate the first data stream, and the transceiver unit 701 can be configured to send the first data stream.
  • the communication apparatus 800 may be applied to the network architecture shown in FIG. 3 .
  • the communication device 800 may be, for example, the network device 1 (TX) or the network device 2 (RX) described in this application, and the communication device 800 may also be the first communication device or the second communication device described in this application.
  • the communication apparatus 800 may also be the control management device described in this application, and performs various operations performed by the control management device.
  • the first communication device and the second communication device described in this application may be an integral network device, or may be a single board in the network device 1, such as an interface board, a line card, a dumb board, or a centralized cross-connect board.
  • the communication device 800 is configured to execute the method of the embodiment corresponding to any one of the foregoing FIG. 6-FIG. 23 .
  • the network device 800 includes a communication interface 801 and a processor 802 connected to the communication interface.
  • the communication interface 801 is used for performing transceiving operations, and the processor 802 is used for performing operations other than transceiving.
  • the processor 802 is configured to generate the first data stream, and the communication interface 801 can be configured to send the first data stream.
  • the communication apparatus 900 may be applied to the network architecture shown in FIG. 3 .
  • the communication device 900 may be, for example, the network device 1 (TX) or the network device 2 (RX) described in this application, and the communication device 900 may also be the first communication device or the second communication device described in this application.
  • the communication apparatus 900 may also be the control management device described in this application, and perform various operations performed by the control management device.
  • the first communication device and the second communication device described in this application may be an integral network device, or may be a single board in the network device 1, such as an interface board, a line card, a dumb board, or a centralized cross-connect board.
  • the communication apparatus 900 is configured to execute the method of the embodiment corresponding to any one of the foregoing FIG. 6 to FIG. 23 .
  • the communication device 900 includes a memory 901 and a processor 902 connected to the memory.
  • the memory 901 stores instructions, and the processor 902 reads the instructions, so that the communication device 900 executes the method of the embodiment corresponding to any one of FIG. 6 to FIG. 23 .
  • the communication apparatus 800 may be applied to the network architecture shown in FIG. 3 .
  • the communication device 800 may be, for example, the network device 1 (TX) or the network device 2 (RX) described in this application, and the communication device 1000 may also be the first communication device or the second communication device described in this application.
  • the communication apparatus 1000 may also be the control management device described in this application, and perform various operations performed by the control management device.
  • the first communication device and the second communication device described in this application may be an integral network device, or may be a single board in the network device 1, such as an interface board, a line card, a dumb board, or a centralized cross-connect board.
  • the communication device 800 is configured to execute the method of the embodiment corresponding to any one of the foregoing FIG. 6-FIG. 23 .
  • the communication device 1000 includes a processor 1010 , a memory 1020 coupled to the processor, and a communication interface 1030 .
  • the memory 1020 stores computer-readable instructions
  • the computer-readable instructions include a plurality of software modules, such as a sending module 1021 , a processing module 1022 and a receiving module 1023 .
  • the processor 1010 can 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 1010 according to the instruction of the software module.
  • the sending module 1021 is configured to send the first data stream
  • the processing module 1022 is configured to generate the first data stream.
  • all operations that can be performed by the first communication apparatus in this application can be performed according to the instructions of the computer-readable instructions.
  • the communication device 1000 may execute the method executed by the first communication device in the embodiment corresponding to any one of FIGS. 6-23 .
  • the processor mentioned in this application may be a central processing unit (English: central processing unit, abbreviation: CPU), a network processor (English: network processor, abbreviation: NP) or a combination of CPU and NP.
  • the processor may also be an application-specific integrated circuit (English: application-specific integrated circuit, abbreviation: ASIC), a programmable logic device (English: programmable logic device, abbreviation: PLD) or a combination thereof.
  • the above-mentioned PLD can be a complex programmable logic device (English: complex programmable logic device, abbreviation: CPLD), field programmable logic gate array (English: field-programmable gate array, abbreviation: FPGA), general array logic (English: generic array logic, abbreviation: GAL) or any combination thereof.
  • the processor 1010 may refer to one processor, or may include multiple processors.
  • the memory mentioned in this application may include volatile memory (English: volatile memory), such as random-access memory (English: random-access memory, abbreviation: RAM); the memory may also include non-volatile memory (English: random-access memory, abbreviation: RAM); : non-volatile memory), such as read-only memory (English: read-only memory, abbreviation: ROM), flash memory (English: flash memory), hard disk (English: hard disk drive, abbreviation: HDD) or solid-state hard disk ( English: solid-state drive, abbreviation: SSD); the memory may also include a combination of the above-mentioned types of memory.
  • the memory may refer to one memory, or may include multiple memories.
  • An embodiment of the present application further 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 described in any one of FIG. 24 to FIG. 27, using The method in any one of the embodiments corresponding to FIG. 6 to FIG. 23 is performed.
  • 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 run on a computer, enables the computer to execute any one of the embodiments corresponding to FIG. 6 to FIG. 23 by the first communication device, the second communication device or Controls the method performed by the management device.
  • the present application also provides a computer program product, including a computer program, which, when run on a computer, enables the computer to execute any one of the embodiments corresponding to FIG. 6 to FIG. 23 by the first communication device, the second communication device or Controls the method performed by the management device.
  • the present application provides a computer-readable storage medium, including computer instructions, which, when executed on a computer, enable the computer to execute the first communication device, the second communication device in any one of the embodiments corresponding to FIG. 6 to FIG. 23 . Or control the method performed by the management device.
  • the above-mentioned embodiments it may be implemented in whole or in part by hardware, firmware or any combination thereof.
  • software When software is involved in the specific implementation process, it can be embodied in the form of a computer program product in whole or in part.
  • the computer program product includes one or more computer instructions.
  • the computer When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • 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 downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center is by wire (eg, coaxial cable, fiber optic, 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, data center, etc. that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVD), or semiconductor media (eg, Solid State Disk (SSD)), and the like.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Time-Division Multiplex Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

本申请提供一种传输数据的方法，通信装置，网络设备，通信系统，存储介质以及计算机程序产品，解决当前基于FlexE技术进行业务承载时，带宽浪费较为严重的问题。本申请新定义了一种小颗粒业务帧的帧结构，从而可以使用以太网（英文：Ethernet，ETH）接口以时分复用的方式传输业务数据，由此，即便是不支持标准FlexE模式的普通以太网接口，也可以有效利用以太网接口带宽，实现带宽隔离。采用本申请的技术方案，能够极大提升通道带宽的利用率，尤其是在承载低速率业务时，能够显著提升通道带宽利用率，避免带宽浪费。

Description

一种传输数据的方法和设备
本申请要求于2020年07月25日提交的申请号为202010726636.X、发明名称为“一种传输数据的方法和设备”的中国专利申请以及于2020年07月31日提交的申请号为202010761609.6、发明名称为“一种传输数据的方法和设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及通信技术领域，具体地，涉及一种传输数据的方法和设备，更为具体地，还涉及一种以太网接口或灵活以太网接口中传输数据的方法和设备。
背景技术
灵活以太网(英文：Flex Ethernet，FlexE)技术是实现业务隔离和网络分片的一种接口技术，近几年发展迅速，被各大标准组织广泛接纳。光互联网论坛(Optical Internet Forum,OIF)发布了FlexE标准。FlexE技术通过在IEEE802.3基础上引入灵活以太网协议层(英文也可以称之为FlexE Shim层)，实现媒体访问控制(英文：Medium Access Control，MAC)层与物理链路接口层(英文也可以称之为PHY)的解耦，从而实现灵活的速率匹配。Flex Shim基于时分复用(英文：Time Division Multiplexing，TDM)分发机制，将多个FlexE客户(英文：client)的数据按照时隙方式调度并分发至多个不同的子通道，实现传输管道带宽的硬隔离，一个业务数据流可以分配到一个或多个时隙中，实现了对各种速率业务的匹配。
现有FlexE接口技术在一定程度上解决了以太网端口速率固定不变的问题，Client交叉技术解决了分组转发时延太大的问题，但是现有技术对于低速率(比如10Mbps)业务承载时，存在较为严重的通道带宽浪费。
发明内容
本申请提供一种传输数据的方法，通信装置，网络设备，通信系统，存储介质以及计算机程序产品，解决当前基于FlexE技术进行业务承载时，带宽浪费较为严重的问题。采用本申请的技术方案，能够极大提升通道带宽的利用率，尤其是在承载低速率业务(例如M级低速率业务)时，能够显著提升通道带宽利用率，避免带宽浪费。进一步地，本申请新定义了一种小颗粒业务帧的帧结构，从而可以使用以太网(英文：Ethernet，ETH)接口以时分复用的方式传输业务数据，由此，即便是不支持标准FlexE模式的普通以太网接口，也可以有效利用以太网接口带宽，实现带宽隔离。
第一方面，本申请提供了一种传输数据的方法，其特征在于，由第一通信装置实施，所述方法包括：生成第一数据流，所述第一数据流包括多个数据码块；
所述多个数据码块包括多个第一基帧，每个第一基帧包括基帧净荷，所述基帧净荷包括基帧开销和多个子用户(sub-client)子时隙净荷，所述多个sub-client子时隙净荷包括多个第一sub-client子时隙净荷，所述多个第一sub-client子时隙净荷包括第一sub-client接口的业务数据；
通过所述第一接口发送所述第一数据流。
可选地，所述第一接口在逻辑上被划分为Z个sub-client接口，所述Z个sub-client接口包括所述第一sub-client接口。
可选地，所述第一接口为灵活以太用户FlexE client接口。
可选地，所述第一接口为以太接口。
可选地，所述第一接口为第一灵活以太用户FlexE client接口，所述第一通信装置还包括发送侧的第一flexE接口，所述通过所述第一接口发送所述第一数据流，包括：
根据所述第一FlexE client接口和所述第一flexE接口的时隙映射关系，通过所述第一flexE接口发送所述第一数据流，其中，所述第一FlexE接口从逻辑上被划分为多个FlexE client接口，所述多个FlexE client 接口包括所述第一FlexE client接口。
可选地，所述每个第一基帧还包括第一码块和第二码块，所述第一码块用于指示所述第一基帧的帧头，所述第二码块用于指示所述第一基帧的帧尾。
可选地，所述第一码块为S码块，所述第二码块为T码块。
可选地，所述第一码块包括第一指示字段和第一数据字段，所述第一指示字段用于指示所述帧头，所述第一数据字段用于承载所述基帧净荷的部分数据。
可选地，所述第二码块包括第二指示字段和第二数据字段，所述第二指示字段用于指示所述帧尾，所述第二数据字段用于承载所述基帧净荷的部分数据。
可选地，所述第一码块和所述第二码块的格式遵从电子工程师学会IEEE 802.3标准所定义的码块格式。
可选地，所述基帧开销包括一项或多项信息：
基帧的序列号；
sub-client子时隙映射表；
时隙调整请求；
时隙调整响应；
时隙生效指示；
管理通道信息；或
基帧开销校验信息。
可选地，所述第一接口在时域上被划分为M个子时隙，M是大于1的整数。
可选地，所述M个子时隙中的每个子时隙的时隙带宽为P，P<5吉比特/秒Gbp/s，。
可选地，所述M个子时隙平均分布在X个第一基帧中，每调度M/X个子时隙，执行一次基帧封装，每个所述基帧净荷包括M/X个sub-client子时隙净荷，X大于1的整数。
可选地，所述第一接口的传输速率为N Gbp/s，N大于等于1。
可选地，所述方法还包括：
接收第二通信装置发送的第一sub-client子时隙映射表，所述第一sub-client子时隙映射表用于指示所述M个子时隙和所述Z个sub-client接口之间的第一映射关系，每个所述sub-client接口映射所述M个子时隙中的至少一个子时隙；
保存所述第一sub-client子时隙映射表。
可选地，所述第一sub-client子时隙映射表通过Z个子用户标识sub-client ID和M个子时隙标识sub-slot ID的映射来指示所述第一映射关系，其中，所述Z个sub-client ID分别用于指示所述Z个sub-client接口，所述M个sub-slot ID分别用于指示所述M个子时隙。
可选地，所述第二通信装置为控制管理设备。
可选地，所述第二通信装置为转发装置。
可选地，所述第一sub-client子时隙映射表被承载在所述基帧开销中；或者，所述第一sub-client子时隙映射表被承载在所述M个子时隙的指定子时隙中。
可选地，所述第一数据流用于承载以太网业务。
可选地，所述生成第一数据流，包括：
从物理编码子层(英文：physical coding sublayer,PCS)获取第一以太业务数据流；
对所述第一以太业务数据流进行切片，得到多个以太业务切片；
将所述多个以太业务切片作为所述多个子用户sub-client子时隙净荷，封装在所述基帧净荷中。
可选地，所述第一以太业务数据流包括至少一个OAM码块。
可选地，所述第一以太业务数据流包括多个64B/66B码块或多个64B/65B码块或多个256B/257B码块。
可选地，所述第一数据流用于承载固定比特流(英文：constant bit rate，CBR)业务。
可选地，所述生成第一数据流，包括：
对第一CBR业务数据流进行切片，得到多个CBR业务切片数据,所述第一CBR业务数据流包括多个CBR业务帧；
对所述多个CRB业务切片数据分别进行切片封装，得到多个CBR业务切片，每个所述CBR业务切片包括所述CBR业务切片数据以及封装信息；
根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷；
将所述多个子用户sub-client子时隙净荷封装在所述基帧净荷中。
可选地，每个所述CBR业务切片的切片粒度为i比特bits，在对所述第一CBR业务数据流进行切片时不识别所述多个CBR业务帧的内容，i为整数。
可选地，每个所述CBR业务切片的切片粒度为j个完整的CBR业务帧，j为大于等于1的整数。
可选地，所述CBR业务切片包括第一字段，用于承载所述CBR业务切片数据。
可选地，所述封装信息包括第二字段，所述第二字段用于承载时钟频率信息。
可选地，所述封装信息包括第三字段，所述第三字段用于承载操作，管理和维护(英文：operation,administration and maintenance，OAM)信息。
可选地，所述封装信息包括第四字段，所述第四字段用于承载CBR业务切片的序列号。
可选地，所述CBR业务切片的序列号用于切片重组。
可选地，所述封装信息包括第五字段，所述第五字段用于承载净荷长度信息，所述净荷长度信息为每个所述CBR业务切片中所承载的CBR业务切片数据的有效长度。
可选地，所述封装信息包括第六字段，所述第六字段为填充字段。
可选地，所述封装信息包括第七字段，所述第七字段用于承载校验信息。
可选地，根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷，包括：
对所述多个CBR业务切片进行以太网报文封装，得到第二数据流，所述第二数据流包括多个码块；
对所述第二数据流按照所述每个子用户sub-client子时隙净荷的长度进行切片，获得所述多个子用户sub-client子时隙净荷。
可选地，所述第二数据流包括多个64B/66B码块或多个64B/65B码块或多个256B/257B码块。
可选地，所述第一数据流包括多个OAM码块，用于承载OAM信息。
可选地，根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷，包括：
将每个所述CBR业务切片直接作为一个子用户sub-client子时隙净荷。
可选地，所述第一数据流包括多个64B/66B码块或多个64B/65B码块或多个256B/257B码块。
可选地，所述第一sub-client接口映射到所述第一接口的W个子时隙，所述生成第一数据流包括：
将所述多个第一sub-client子时隙净荷分别映射到所述W个子时隙，W为大于1的整数。
可选地，将所述多个第一sub-client子时隙净荷分别映射到所述W个子时隙，包括：
根据所述第一sub-client接口和所述W个子时隙的映射关系，基于所述第一接口的时隙调度周期，按顺序调度所述W个子时隙。
可选地，所述第一通信装置包括接收侧的第二sub-client接口，所述生成第一数据流，包括：
获取所述第二sub-client接口的多个第二sub-client子时隙净荷，
基于所述第二sub-client接口和所述第一sub-client接口之间的子时隙交叉关系，对所述多个第二sub-client子时隙净荷进行处理，得到所述多个第一sub-client子时隙净荷；
将所述多个第一sub-client子时隙净荷，封装在所述基帧净荷中。
可选地，获取所述第二sub-client接口的多个第二sub-client子时隙净荷，包括：
获取接收侧的第二接口的第三数据流,按照第二sub-client子时隙映射表，从所述第三数据流中解映射出所述多个第二sub-client子时隙净荷，所述第二接口在时域上被划分为A个子时隙，所述第二接口逻辑上划分为B个sub-client接口，所述B个sub-client接口包括所述第二sub-client接口，所述第二子时隙时隙表用于指示所述A个子时隙和所述B个sub-client接口的第二映射关系。A和B均为整数。A的取值可以参考本申请M的取值的相关说明。
可选地，所述第二接口为以太接口。
可选地，所述第二接口为第二FlexE Cilent接口。
可选地，所述第一通信装置还包括接收侧的第二FlexE接口，所述获取所述第三数据流，包括：
获取所述第二FlexE接口的第四数据流，所述第二FlexE接口从逻辑上被划分为多个FlexE client接口，所述多个FlexE client接口包括所述第二FlexE client接口；
根据所述第二FlexE client接口和所述第二flexE接口的时隙映射关系，从所述第四数据流中解映射出所述第三数据流，所述第三数据流包括多个第二基帧，所述多个第二基帧包括所述多个第二sub-client子时隙净荷。
第二方面，本申请提供了一种第一通信装置，其特征在于，包括：
存储器，存储有指令；
与所述存储器相连的处理器，所述处理器执行所述指令时，使得所述第一通信装置执行所述第一方面以及任一种可选的实施方式中所述的方法。
第三方面，本申请提供了一种计算机可读存储介质，其特征在于，包括程序或指令，当其在计算机上运行时，使得计算机执行所述第一方面以及任一种可选的实施方式中所述的方法。
第四方面，本申请提供了一种通信系统，包括权利要求第一通信装置和第二通信装置，第一通信装置用于执行所述第一方面以及任一种可选的实施方式中所述的方法。
第五方面，本申请提供了一种程序产品，其特征在于，包括程序或指令，当其在计算机上运行时，使得计算机执行所述第一方面以及任一种可选的实施方式中所述的方法。
附图说明
图1为基于灵活以太网协议的FlexE通用架构示意图；
图2为跨4个物理链路接口(聚合4个PHY)的FlexE Group的时隙分配情况的示意图；
图3为本申请涉及的FlexE通信系统的应用场景示意图；
图4为本申请所涉及的采用FlexE技术传输数据的过程的示意图；
图5为OIF IA-FLEXE-02.1标准中给出的100GE接口的开销帧和开销复帧的结构示意图；
图6为N个100G PHY捆绑时，多个FlexE Clients的时隙分配示意图；
图7为本申请提供的一种基帧封装过程示意图；
图8为IEEE802.3定义的码块格式；
图9为本申请提供的一种基于子客户接口传输数据结构示意图；
图10为本申请提供的一种复帧封装的格式示意图；
图11为本申请提供的一种复帧的格式说明示意图；
图12本申请提供的一种获取以太网业务sub-client子时隙净荷的方法流程示意图；
图13为本申请提供的一种获取CBR业务sub-client子时隙净荷的方法流程示意图；
图14为本申请提供的一种具体的用于获取CBR业务sub-client子时隙净荷的方法流程示意图；
图15为本申请提供的另一种具体的用于获取CBR业务sub-client子时隙净荷的方法流程示意图；
图16为本申请提供的一种传输数据的方法示意图；
图17为本申请提供的一种配置sub-client子时隙映射表的方法示意图；
图18为本申请提供的另一种配置sub-client子时隙映射表的方法示意图；
图19为本申请提供的一种发送sub-client业务数据流的方法示意图；
图20为本申请提供的一种基于flexE接口传输以太业务的方法示意图；
图21为本申请提供的一种基于flexE接口传输CBR业务的方法示意图；
图22为本申请提供第一种基于以太接口传输以太业务的方法示意图；
图23为本申请提供的一种基于以太接口传输CBR业务的方法示意图；
图24为本申请提供的一种通信装置的结构示意图；
图25为本申请提供的一种通信装置的结构示意图；
图26为本申请提供的一种通信装置的结构示意图；
图27为本申请提供的一种通信装置的结构示意图。
具体实施方式
本申请中的“1”、“2”、“3”、“4”、“第一”、“第二”、“第三”和“第四”等序数词是用于对不同对象进行区分，不用于限定多个对象的顺序。此外，术语“包括”和“具有”不是排他的。例如，包括了一系列步骤或单元的过程、方法、系统、产品或设备没有限定于已列出的步骤或单元，还可以包括没有列出的步骤或单元。
本申请中，以太网接口和以太接口经常交替使用，灵活以太接口和灵活以太网接口经常交替使用。
本申请所涉及的相关FlexE的现有技术可以参见OIF所制定的FlexE标准IA OIF-FLEXE-01.0，IA OIF-FLEXE-02.0或者IA OIF-FLEXE02.1的相关说明，上述标准以全文引用的方式并入本申请中。
图1示例性示出了基于灵活以太网协议的FlexE通用架构示意图。如图1所示，FlexE Group包括4个PHY。FlexE Client代表在FlexE Group上指定时隙(一个时隙或多个时隙)传输的客户数据流，一个FlexE Group上可承载多个FlexE Client，一个FlexE Client可对应一个到多个用户业务数据流(也可以称为MAC Client)，FlexE Shim层提供FlexE Client到MAC Client的数据适配和转换。FlexE可以支持任意多个不同FlexE Client在任意一组PHY上的映射和传输，从而实现PHY捆绑、通道化及子速率等功能。多路PHY组合在一起成为一个FlexE组(英文也可以称为FlexE Group)，用于承载通过FlexE Shim层分发、映射来的一路或者多路FlexE client数据流。以100GE PHY为例，FlexE Shim层可以把FlexE Group中的每个100GE PHY划分为20个时隙(slot)的数据承载通道，每个slot对应的带宽为5Gbps。
图2示意性示出了跨4个物理链路接口(聚合4个PHY)的FlexE Group的时隙分配情况的示意图。如图2所示，每个PHY均拥有20个时隙，因此该FlexE Group拥有20*4个时隙。如图2所示，以图1中的FlexE Group包括4个PHY为例介绍，4个PHY分别为PHY A 1201、PHY B 1202、PHY C 1203和PHY D 1204。FlexE Group对应时隙分配表(英文也可以称为calendar)；一个FlexE Group中包括的单个物理链路对应的时隙映射表可以称为子时隙分配表(英文可以称为sub-calendar)。FlexE calendar可以由一个或多个sub-calendar组成。每个sub-calendar可以指示该单个物理链路上20个时隙(slot)如何分配给相应的FlexE client。也就是说，每个sub-calendar可以指示该单个物理链路上时隙与FlexE client的对应关系。如图2所示，每个PHY可以对应20个时隙，图中分别用slot 0至slot 19来表示。图2分别示出了PHY A 1201、PHY B 1202、PHY C 1203和PHY D 1204中每个PHY对应的20个时隙的示意图。
图3示出了本申请涉及的FlexE通信系统的应用场景示意图。如图3所示，FlexE通信系统100包括网络设备1、网络设备2、用户设备1和用户设备2。网络设备1可以是中间节点，此时网络设备1通过其 他网络设备与用户设备1连接。网络设备1可以是边缘节点，此时网络设备1直接与用户设备1连接。网络设备1可以是中间节点，此时网络设备1通过其他网络设备与用户设备1连接。网络设备1也可以是边缘节点，此时网络设备1直接与用户设备1连接。网络设备2可以是中间节点，此时网络设备2通过其他网络设备与用户设备2连接。网络设备2也可以是边缘节点，此时网络设备2直接与用户设备2连接。网络设备1包括FlexE接口1，网络设备2包括FlexE接口2。FlexE接口1与FlexE接口2相邻。每个FlexE接口均包括发送端口和接收端口，与传统以太网接口的区别在于一个FlexE接口可以承载多个Client，且作为逻辑接口的FlexE接口可以由多个物理接口组合而成。图3中所示的正向通道中业务数据的流向如图3中实线箭头所示，反向通道中业务数据的流向如图3中虚线箭头所示。本发明实施例的传输通道以正向通道为例，传输通道中业务数据的流向为用户设备1->网络设备1->网络设备2->用户设备2。
应理解，图3中仅示例性的示出了2个网络设备和2个用户设备，该网络可以包括任意其它数量的网络设备和用户设备，本申请实施例对此不做限定。图3中所示的FlexE通信系统仅是举例说明，本申请提供的FlexE通信系统的应用场景不限于图3所示的场景。本申请提供的技术方案适用于所有应用FlexE技术进行数据传输的网络场景。
下面结合图4进一步描述图3中所示网络设备1和网络设备2采用FlexE技术传输数据的过程。
如图4所示，PHY1、PHY2、PHY3和PHY4绑定成为一个FlexE group。网络设备1和网络设备2之间通过FlexE group接口连接，即通过FlexE接口1与FlexE接口2连接。上述FlexE group接口也可以被称之为FlexE接口。FlexE group接口是由一组物理接口绑定而成的逻辑接口。该FlexE group接口共承载有6个client，分别为client1至client6。其中，client1和client2的数据映射在PHY1上传输；client3的数据映射在PHY2和PHY3上传输；client4的数据映射在PHY3上传输；client5和client6的数据映射在PHY4上传输。不同FlexE client在FlexE group上进行映射和传输，实现捆绑功能。其中：
FlexE group：也可称之为捆绑组。每个FlexE group包括的多个PHY具有逻辑上的捆绑关系。所谓的逻辑上捆绑关系，指的是不同的PHY之间可以不存在物理连接关系，因此，FlexE group中的多个PHY在物理上可以是独立的。FlexE中的网络设备可以通过PHY的编号来标识一个FlexE group中包含哪些PHY，来实现多个PHY的逻辑捆绑。例如，每个PHY的编号可用1～254之间的一个数字来标识，0和255为保留数字。一个PHY的编号可对应网络设备上的一个接口。相邻的两个网络设备之间需采用相同的编号来标识同一个PHY。一个FlexE group中包括的各个PHY的编号不必是连续的。通常情况下，两个网络设备之间具有一个FlexE group，但本申请并不限定两个网络设备之间仅存在一个FlexE group，即两个网络设备之间也可以具有多个FlexE group。一个PHY可用于承载至少一个client，一个client可在至少一个PHY上传输。
FlexE client:对应于网络的各种用户接口或带宽。FlexE client可根据带宽需求灵活配置，支持各种速率的以太网MAC数据流(如10G、40G、n*25G数据流，甚至非标准速率数据流)，例如可以通过64B/66B的编码的方式将数据流传递至FlexE shim层。通过同一FlexE group发送的客户需要共用同一时钟，且这些客户需要按照分配的时隙速率进行适配。本申请中所述的FlexE client接口用于传输相应的FlexE client的业务数据流。FlexE client接口是一个逻辑接口。每个FlexE接口在逻辑上可以划分为一个或多个FlexE client接口，每个FlexE接口在时域上可以划分为多个时隙，每个FlexE client接口占用所述多个时隙中的至少一个时隙。
FlexE shim:作为插入传统以太架构的MAC与PHY(PCS子层)中间的一个额外逻辑层，是基于calendar的时隙分发机制实现FlexE技术的核心架构。FlexE shim的主要作用是根据相同的时钟对数据进行切片，并将切片后的数据封装至预先划分的时隙(slot)中。然后，根据预先配置的时隙分配表，将划分好的各时隙映射至FlexE group中的PHY上进行传输。其中，每个时隙映射于FlexE group中的一个PHY。
Calender：时隙分配表，也可以称之为时隙表。FlexE Group对应calendar，一个FlexE Group中包括的 单个物理链路(PHY)对应的时隙映射表可以称为子时隙分配表(英文：sub-calendar)。FlexE calendar可以由一个或多个sub-calendar组成。每个sub-calendar可以指示该单个物理链路上20个时隙(英文可以写为slot)如何分配给相应的FlexE client。也就是说，每个sub-calendar可以指示该单个物理链路上时隙与FlexE client的对应关系。当前标准中定义，每个FlexE开销帧中指定两个Calender，分别是当前的主用时隙表(Calender A)和备用时隙表(Calender B)。
FlexE对物理接口传输构建固定帧格式，并进行TDM的时隙划分。如前所述，FlexE shim层通过定义开销帧和开销复帧的方式体现client与FlexE group中的时隙映射关系以及calendar工作机制。需要说明的是，上述的开销帧，也可以称之为灵活以太开销帧(英文：FlexE overhead frame)，上述的开销复帧也可以称之为灵活以太开销复帧(英文：FlexE overhead Multiframe)。FlexE shim层通过开销提供带内管理通道，支持在对接的两个FlexE接口之间传递配置、管理信息，实现链路的自动协商建立。
FlexE的每个PHY上的数据通过周期性插入FlexE开销(overhead frame，OH)帧的码块来实现对齐，比如可以是每隔1023x 20个66B的净荷数据码块插入1个66B的开销码块FlexE OH。根据FlexE Implementation Agreement协议，一个FlexE Group在每个PHY上每隔预定时间间隔上就会发出一个FlexE开销帧的64B/66B码块至远端的PHY，8个依次发送的FlexE开销帧的64B/66B码块构成了一个FlexE开销帧。FlexE定义开销帧上的一些字段承载时隙分配表，并通过FlexE开销帧把时隙分配表同步至远端的通信设备上的PHY，以保证双端的通信设备使用相同的时隙分配表接收和发送FlexE客户对应的数据流。具体而言，如图5所示，图5中示出了OIF IA-FLEXE-02.1标准中给出的100GE接口的开销帧和开销复帧的结构示意图。一个开销帧有8个开销块(英文：overhead block)，上述开销块也可以称之为开销时隙(英文：overhead slot)。每个开销块是一个64B/66B编码的码块，每间隔1023*20blokcs出现一次，但每个开销块所包含的字段是不同的。开销帧中，第一个开销块中包含“0X4B”的控制字符和“0x5”的“O码”字符，在数据传输过程中，对接的FlexE接口之间通过所述控制字符和“O码”字符匹配确定第一个开销帧。32个开销帧组成一个开销复帧。
在上文中，结合图1至图5介绍了基于灵活以太网协议的FlexE通用架构以及基于现有的FlexE技术传输数据的过程。当前OIF FlexE标准定义了50G/100G/200G/400G接口框架，不同速率的FlexE Client接口在一个时隙循环周期内分配N个时隙，每个时隙的时隙带宽为5Gbps(下文简称5G)粒度，因此，N＝接口速率/5Gbps。以100G PHY为例，如图6所示，每个PHY包括20个5G时隙，N个PHY捆绑时共有N*20个5G时隙，因此，每个FlexE Client分配的带宽必须为5G的整数倍，最小带宽为5G，即至少分配一个时隙。图6中，每个时隙的时隙带宽均为5G，FlexE client#1分配x个时隙，FlexE client#2分配y个时隙,…FlexE#M分配z个时隙。但是，当前应用层存在许多低速率业务，例如银行自动柜员机(英文：automatic teller machine，ATM)的相关业务，对于带宽的需求很低，可能只需要100Mbps，此时，即便采用最小的5GFlexE Client通道(仅占用1个时隙)承载该业务，也会存在4.9G带宽的浪费，无法精准的匹配业务需求。
为了解决上述技术问题，本申请在现有FlexE接口或普通以太网物理接口的基础上，重新定义了更小粒度的子用户sub-client接口。可以根据不同低速率业务的需求，灵活设置每个sub-client接口的接口速率，从而尽量避免带宽浪费。进一步地，本申请还提供了一种子时隙交叉技术，在充分利用带宽的基础上，在设备内部基于时隙交叉技术进行转发，可以有效降低转发时延。
在介绍本申请提供的各技术方案之前，为了便于对本申请技术方案的理解，对本申请涉及的一些技术术语进行简单的介绍和说明。
子时隙：子时隙也可以称之为低阶时隙。相对于现有FlexE Client接口所配置的时隙(也可以称之为大时隙或者高阶时隙)或者普通ETH接口的大带宽而言。对于标准的FlexE Client接口或普通的ETH接口，在每个FlexE Client接口或ETH接口在时域上划分为M个子时隙，每个子用户接口占用至少一个 子时隙的带宽进行数据传输。
FlexE sub-shim，基于子时隙分发机制，对相同的sub-client的数据进行切片，并将切换后的数据作为子时隙净荷封装在预先划分的子时隙(sub-slot)中。然后根据预先获取的sub-client子时隙映射表，将划分好的各子时隙映射至对应的FlexE Client接口中。其中，每个子时隙映射于一个FlexE client接口。
子用户：sub-client，对应于网络的各种子用户接口或带宽。FlexE sub-client可根据带宽需求灵活配置，支持各种速率的以太网MAC数据流(如10G、40G、n*25G数据流，甚至非标准速率数据流)，例如可以通过64B/66B或者64B/65B转码或者256B/257B转码的方式将数据流传递至FlexE sub-shim层。
子用户接口：sub-Client接口。子用户接口也可以称之为子时隙接口、低阶时隙接口子、子时隙通道或低阶时隙通道。子用户接口是相对于现有的FlexE Client接口或者普通以太接口而言的概念。每个FlexE Client接口或者普通以太接口在逻辑上被划分为多个子用户接口，在时域上被划分为多个子时隙，每个子用户接口占用至少一个子时隙进行数据传输，每个子时隙的时隙带宽粒度通常小于5Gbps，例如可以是10Mbps-100Mbps之间的任意数值，以承载更多低速率业务，有效利用带宽。
sub-client子时隙净荷，是相同的sub-Client的数据进行切片所得到的数据。每个切片作为一个sub-client子时隙净荷封装在预先划分的子时隙(sub-slot)中。
Sub-Client子时隙映射表：也可以称之为低阶通道时隙分配表，Sub-Client子时隙分配表，低阶通道时隙映射表。用于标识每个Sub-Client子接口分配的时隙数量和时隙位置。
基帧：本申请提供的一种数据结构，用于承载不同sub-client的业务数据流。每个基帧包括基帧净荷。基帧净荷包括基帧开销和低阶时隙净荷(即sub-client子时隙净荷)。在本申请中，每个低阶时隙净荷具有相同的长度，例如可以Y比特。每个低阶时隙净荷可以是多个64B/66B码块。为了进一步提高数据的传输效率，每个低阶时隙净荷可以是多个64B/65B码块或者256B/257B码块，其中，所述多个64B/65B码块或者256B/257B码块可以是利用转码算法对PCS编码的多个64B/66B码块进行转码压缩得到，转发算法例如可以是64B/65B转码或者256B/257B转码。所述基帧开销用于传输开销信息，开销信息可以包括但不限于以下一项或多项信息：
基帧的序列号；
sub-client子时隙映射表；
时隙调整请求；
时隙调整响应；
时隙生效指示；
管理通道信息；
开销校验信息。
其中,基帧序列号，可以用于标识基帧在整个复帧中的位置，根据该位置信息可以知道基帧所装载的子时隙编号。Sub-Client子时隙映射表，可以用于标识每个低阶通道所分配的时隙数量和时隙位置。时隙调整请求用于发送时隙调整请求，例如用于调整sub-client的时隙，时隙调整响应是对于收到时隙调整请求的响应，时隙生效指示用于指示时隙调整生效。管理消息通道，可以用于传输网元管理消息，也可以用于传输Sub-Client子时隙映射表信息。开销校验信息，用于对基帧开销进行校验，校验算法可以但不限于选择CRC或BIP等误码检测算法。sub-client子时隙净荷用于根据Sub-Client子时隙映射表承载不同Sub-Client接口的数据。每个基帧还包括用于界定基帧帧头的码块以及用于界定基帧帧尾的码块。
图7示出了本申请提供的一种具体的基帧的封装格式示意图，但是本领域技术人员可以理解，图7不应理解为对基帧封装格式的限定。如图7所示，为兼容IEEE 802.3定义的以太网帧格式，基帧采用/S/码块、/D/码块和/T/码块进行封装。其中，/S/码块用于指示基帧的帧头。/T/码块用于指示基帧的帧尾。/D/码块的数据字段(如图7或图8所示的Block payload域)用于承载基帧净荷。可以用/I/码块用于对基 帧进行速率适配。一个具体的实施方式中，基帧中每个码块的格式例如可以遵从如图8所示的IEEE802.3定义的码块格式。一个具体的实施方式中，/S/码块和/或/T/码块中的部分或全部数据字段(block payload，BP)和/D/码块的数据字段共同承载基帧净荷，其中S码块中BP为可选域段，T码可以是T0-T7七个码块中的任意一种。
图9为本申请提供的一种子用户接口传输的数据结构示意图。如图9所示，在带宽为N*5G的FlexE Client接口或普通ETH接口内划分M个子时隙进行循环传输。即每个循环周期为M个子时隙，该循环周期也可以称之为子用户接口的子时隙调度周期或子用户接口的时隙调度周期。一个具体的实施方式中，在所述M个子时隙上平均分布X个基帧，每个基帧净荷中装载(M/X)个低阶时隙。每X个基帧也可以定义为一个复帧。在每个循环周期内，传输一个复帧。在一个具体的实施方式中，根据传输以太网报文的规定，复帧长度应小于等于9600字节。
在本申请中，每个FlexE接口在逻辑可以划分为多个FlexE Client接口。一个FlexE Client接口在逻辑上可以划分为多个FlexE sub-client接口，一个FlexE Client接口在时域上可以划分为M个子时隙。对于不同带宽的FlexE Client接口，不同的FlexE sub-client接口的带宽，M可以灵活配置。例如，图10示出了本申请提供的一种复帧封装的格式示意图。结合图10，对于每个5G的FlexE Client接口，其在时域上可以划分为480个子时隙(即M＝480)。在一个FlexE Client接口的每个时隙调度周期(480个子时隙为一个时隙调度周期)内，平均分布20个基帧，即一个复帧。在本申请中，将基帧的英文命名为fgDu。每个基帧包含24个子时隙。一个具体的实施例中，每个子时隙净荷可以包含8个66b压缩码块，对于一个基帧来说，加上/S/,/OH/码块，/T/码块进行封装，一个基帧内可以包含197个66B码块。其中，为了速率适配，可以在基帧之间增加/I/码块，也可以将部分/I/码块替换FlxeE client接口中传输的OAM码块。。/I/码块即空闲(idle)码块，用作MAC层速率适配。
作为一个具体的实施方式，图11示出了本申请提供的一种复帧的格式说明示意图。图11可以用于对图10所示的复帧结构做进一步的说明。图11中所述的小颗粒时隙1至小颗粒时隙480分别对应于子时隙1至子时隙480。
如图11所示，一个复帧包括480个子时隙，每个基帧包括24个子时隙，每个子时隙包括8个66B压缩码块，即8个65B码块。码块压缩过程如图11所示，在66B码块流中周期性的插入OAM码块之后，进行码块压缩，压缩之后，每个子时隙包括8个65B码块。一种具体的实施方式中，可以将基帧开销中部分字段用于承载数据。例如，如果基帧开销只需要56比特，则每个基帧开销剩余的8bit可以用于承载数据。一种具体实施方式中，可以将用于标识帧尾的码块中的第一字段用于指示帧尾，第二字段用于承载数据。例如，图11中所示的T码块中控制符指示帧尾，T码块中的BP域可以用于承载数据，即T码块中的56bit可以用于承载数据。因此，作为举例，如图11所示，基帧中用于承载业务数据的bits＝24*(8*65b)＝12480b＝8b(OH中剩余的8bits)+194*64b+56b(T码块中的56bits)。
下面结合图12对本申请提供的一种获取以太网业务sub-client子时隙净荷的方法100进行介绍，该方法包括：从PCS获取以太网业务数据流；对所述第一以太业务数据流进行切片，得到多个以太业务切片；以及将所述多个以太业务切片作为所述多个子用户sub-client子时隙净荷。作为一个具体的示例，结合图12中S101-S103具体说明如何获取所述以太网业务数据流，结合S104说明如何对以太业务数据流进行切片以说的所述多个子用户sub-client子时隙净荷。
S101：PCS对MAC层以太报文进行编码。
作为一个具体的实施方式，如图12所示，参考IEEE802.3定义的以太网分层模型，将每个低阶通道，即每个sub-client接口，视为一个独立的端口划分成MAC层和PCS。MAC层实现业务报文的封装和校验处理，PCS按照802.3编码方式对MAC层报文，即以太网业务数据流进行64B/66B编码。编码后的码块流包括S码块，D码块，T码块，I码块(即IDLE码块，也称之为空闲码块)，码块格式遵从IEEE802.3定 义的标准码块格式。
S102：在PCS编码后的码块流中插入低阶通道层OAM码块，得到所述以太网业务数据流。其中，OAM码块用于传输OAM信息。例如可以按照间隔一段时间(如3.3ms)或间隔一定数量(如500)的码块后选择邻近的/I/码块插入OAM码块
一个具体的实施方式中，OAM信息例如可以是OAM消息，可以参考ITU G.MTN标准定义的MTN通道层OAM格式。
S103：可选地，对插入OAM消息后的64B/66B码块流进行转码压缩。
一个具体的实施方式中，压缩后的码块流包括多个64B/65B码块。一个具体的实施方式中，压缩后的码块流包括多个256B/257B码块。
对码块流进行转码压缩，可以提升低阶通道的数据承载效率，转码算法可以采用或256B/257B转码。图12中仅示出了64B/65B转码，对于256B/257B转码原来类似，不再赘述。
S104:对以太网业务数据流(或者也可称之为码块流)按照每sub-client子时隙净荷长度(Y比特)进行切片。每sub-client子时隙净荷长度可以是Z个64B/66B码块，如果做了转码压缩，也可以为Z个转码后的64B/65B码块或Z个256B/257B转码。Y和Z均为整数。
经过S104的切片操作所得到的每个切片将作为一个sub-client子时隙净荷封装到基帧Payload中。基帧payload以及基帧的相关格式参见上文说明，此处不再赘述。
下面结合图13对本申请提供的一种获取固定比特率(英文：constant bit rate,CBR)的sub-client子时隙净荷的方法200进行介绍。
S201.对CBR业务数据流进行切片，得到多个CBR业务切片数据。其中，所述第一CBR业务数据流包括多个CBR业务帧.
对CBR业务数据流进行切片时，包括但不限于采用以下两种模式：
模式一、比特透明切片模式。
比特透明切片模式，不识别业务帧内容，按照固定的比特数(如i个比特)进行切片。
模式二、帧切片模式。
帧切片模式，需要识别业务帧格式，按照固定的帧数量(如j个帧)进行切片。
S202.对所述多个CRB业务切片数据分别进行切片封装，得到多个CBR业务切片，每个所述CBR业务切片包括所述CBR业务切片数据以及封装信息。
在一个具体的实施方式中，每个CBR业务切片包括多个字段，分别用于承载CBR业务切片数据以及封装信息。
一个具体的实施方式中，所述CBR业务切片包括第一字段，用于承载所述CBR业务切片数据。
一个具体的实施方式中，所述封装信息包括第二字段到第七字段的任意一个或多个字段，用于承载不同的封装信息。
第二字段，所述第二字段用于承载时钟频率信息。该时钟频率信息例如可以包括时间戳等信息，用于传递业务的时钟信息。
第三字段，所述第三字段用于承载操作，管理和维护OAM信息。
第四字段，所述第四字段用于承载CBR业务切片的序列号；所述CBR业务切片的序列号例如可以用于切片重组，所述CBR业务切片的序列号还可以用于切片的丢失检测或无损保护。
第五字段，所述第五字段用于承载净荷长度信息，所述净荷长度信息为每个所述CBR业务切片中所承载的CBR业务切片数据的有效长度。
第六字段，所述第六字段为填充字段。但业务切片封装后小于子时隙净荷的长度时，可以才赢填充字段进行数据填充。
第七字段，所述第七字段用于承载校验信息。校验信息可以用于对切片数据进行误码校验，但是本申请不限于必须在切片中包括校验信息，该校验功能也可以通过其他方式进行，例如采用OAM进行校验。
S203.根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷。
在一个具体的实施方式中，可以将所述多个CBR业务切片，直接作为所述多个sub-client子时隙净荷，即封装后得到的每个CBR业务切片的长度和每个sub-client子时隙净荷保持相同，例如，都是Y比特。下面将结合图14对该方式进行具体的举例说明。
在另一个具体的实施方式中，根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷，包括：
对所述多个CBR业务切片进行以太网报文封装，得到第二数据流，所述第二数据流包括多个码块；
对所述第二数据流按照所述每个子用户sub-client子时隙净荷的长度进行切片，获得所述多个子用户sub-client子时隙净荷。下面将结合图15对该实施方式进行具体的举例说明。
图14示出了本申请提供的一种获取CBR业务sub-client子时隙净荷的方法示意图，该方法1400可以用于具体实现方法200。该方法包括：
S1401.将CBR业务数据进行切片。得到多个CBR业务切片数据，对应于图14中所示的切片。切片模式采用上文介绍的模式一或者模式二。
S1402.对每个业务切片数据进行封装。封装后的切片长度和低阶时隙净荷长度相同(如Y比特)。封装信息包括以下一项或多项信息：
OAM信息(可选)，用于CBR低阶通道层故障检测和保护操作。
序列号(可选)。
时钟频率信息，用于传递业务的时钟信息(如时戳)。
净荷长度和填充，为可选项，如果业务切片封装后小于低阶时隙净荷长度，则需要进行数据填充，并标识有效净荷长度。
校验字段，为可选项，用于对切片数据进行误码校验，该校验功能也可以选择通过OAM进行校验。
S1403.将切片后的数据作为一个sub-client子时隙净荷。
图15示出了本申请提供的一种获取CBR业务的sub-client子时隙净荷的方法示意图，该方法1500可以用于具体实现方法200。该方法1500包括：
S1501.将CBR业务数据进行切片，得到多个CBR业务切片数据，对应于图15中所示的业务切片。切片模式采用上文介绍的模式一或者模式二。
S1502.对切片数据块进行封装。
封装信息包括以下一项或多项信息：
OAM信息(可选)，用于CBR低阶通道层故障检测和保护操作。
序列号(可选)。
时钟频率信息，用于传递业务的时钟信息(如时戳)。
净荷长度和填充，为可选项，如果业务切片封装后小于低阶时隙净荷长度，则需要进行数据填充，并标识有效净荷长度。
校验字段，为可选项，用于对切片数据进行误码校验，该校验功能也可以选择通过OAM进行校验。
S1503.将封装后的CBR业务切片封装为以太网报文，添加帧边界(例如，图15所示的/S/码块和/T/码块)和帧间隙封装(例如，图15所示的/I/码块)，获得编码后的以太网码块流。其中每个封装后的CBR业务切片作为以太网数据流的数据码块。该步骤的具体操作与现有以太网报文处理类似，此处不再赘述。
S1504.在PCS编码后的以太网码块流中插入低阶通道层OAM码块。其中，OAM码块用于传输OAM信 息。
一个具体的实施方式中，OAM信息例如可以是OAM消息，可以参考ITU G.MTN标准定义的MTN通道层OAM格式。
S1505.可选地，对插入OAM消息后的64B/66B码块流进行转码压缩。
一个具体的实施方式中，压缩后的码块流包括多个64B/65B码块。一个具体的实施方式中，压缩后的码块流包括多个256B/257B码块。
对码块流进行转码压缩，可以提升低阶通道的数据承载效率，转码算法可以采用或256B/257B转码。图12中仅示出了64B/65B转码，对于256B/257B转码原来类似，不再赘述。
S1506.对插入了OAM码块的以太网业务数据流(或者也可称之为码块流)按照每sub-client子时隙净荷长度(Y比特)进行切片。每sub-client子时隙净荷长度可以是Z个64B/66B码块，如果在切片之前做了转码压缩，也可以为Z个转码后的64B/65B码块或Z个256B/257B转码。Y和Z均为整数。
经过S1056的切片操作所得到的每个切片将作为一个sub-client子时隙净荷封装到基帧Payload中。基帧payload以及基帧的相关格式参见上文说明，此处不再赘述。
上面介绍了本申请提供的基帧的封装格式和封装过程，同时介绍了获取以太网业务的sub-client子时隙净荷或者CBR业务的sub-client子时隙净荷的方法。在此基础上，结合附图16对本申请中所提供的一种传输数据的方法1600进行介绍。该方法由第一通信装置执行，该第一通信装置包括第一接口，该方法包括：
S1601.生成第一数据流，所述第一数据流包括多个数据码块。
具体来说，所述多个数据码块包括多个第一基帧，每个第一基帧包括基帧净荷，所述基帧净荷包括基帧开销和多个子用户sub-client子时隙净荷，所述多个sub-client子时隙净荷包括多个第一sub-client子时隙净荷，所述多个第一sub-client子时隙净荷包括第一sub-client接口的业务数据。
S1602.通过所述第一接口发送所述第一数据流。
在S1602中，每个基帧的封装格式以及封装过程，参见上文中的具体表述，此处不再赘述。
在一个具体的实施方式中，所述第一接口在时域上被划分为M个子时隙。M为大于1的整数。为了承载更多的低速率业务，所述M个子时隙中的每个子时隙的时隙带宽为P优选为P<5吉比特/秒Gbp/s，更为优选的是P小于等于1Gbp/s,更为优选的是，P小于等于500Mbp/s。为了承载例如ATM机的业务，P优选小于等于100Mbp/s。关于M的具体取值可以参见上文的说明，此处不再赘述。
在一个具体的实施方式中，所述第一接口在逻辑上被划分为Z个sub-client接口，所述Z个sub-client接口包括所述第一sub-client接口。
在一个具体的实施方式中，所述第一接口为第一灵活以太用户FlexE client接口。所述第一通信装置还包括发送侧的第一flexE接口，S1602具体包括：
根据所述第一FlexE client接口和所述第一flexE接口的时隙映射关系，通过所述第一flexE接口发送所述第一数据流，其中，所述第一FlexE接口从逻辑上被划分为多个FlexE client接口，所述多个FlexE client接口包括所述第一FlexE client接口。
在一个具体的实施方式中，当所述第一接口为第一FlexE client接口时，
在一个具体的实施方式中，所述第一接口为以太接口。
在一个具体的实施方式中，所述第一数据流用于承载以太网业务。
在一个具体的实施方式中，当时所述第一数据流用于承载以太网业务时，S1601中生成第一数据流包括：
从PCS获取第一以太业务数据流；
对所述第一以太业务数据流进行切片，得到多个以太业务切片；
将所述多个以太业务切片作为所述多个子用户sub-client子时隙净荷，封装在所述基帧净荷中。
上述步骤的具体实现可以结合图12，参见上文方法100的具体说明。此处不再赘述。
在一个具体的实施方式中，所述第一数据流用于承载CBR业务。
当所述第一数据流用于承载CBR业务时，S1601中生成第一数据流，包括：
在一个具体的实施方式中，所述方法1600还包括：对第一CBR业务数据流进行切片，得到多个CBR业务切片数据,所述第一CBR业务数据流包括多个CBR业务帧；
对所述多个CRB业务切片数据分别进行切片封装，得到多个CBR业务切片，每个所述CBR业务切片包括所述CBR业务切片数据以及封装信息；
根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷；
将所述多个子用户sub-client子时隙净荷封装在所述基帧净荷中。
在一个具体的实施方式中，每个所述CBR业务切片的切片粒度为i比特bits，在对所述第一CBR业务数据流进行切片时不识别所述多个CBR业务帧的内容，i为整数。
在一个具体的实施方式中，每个所述CBR业务切片的切片粒度为j个完整的CBR业务帧，j为大于等于1的整数。
在一个具体的实施方式中，所述CBR业务切片包括第一字段，用于承载所述CBR业务切片数据。
在一个具体的实施方式中，所述封装信息包括第二字段，所述第二字段用于承载时钟频率信息。
在一个具体的实施方式中，所述封装信息包括第三字段，所述第三字段用于承载操作，管理和维护OAM信息。
在一个具体的实施方式中，所述封装信息包括第四字段，所述第四字段用于承载CBR业务切片的序列号。
在一个具体的实施方式中，所述CBR业务切片的序列号用于切片重组。
在一个具体的实施方式中，所述封装信息包括第五字段，所述第五字段用于承载净荷长度信息，所述净荷长度信息为每个所述CBR业务切片中所承载的CBR业务切片数据的有效长度。
在一个具体的实施方式中，所述封装信息包括第六字段，所述第六字段为填充字段。
在一个具体的实施方式中，所述封装信息包括第七字段，所述第七字段用于承载校验信息。
在一个具体的实施方式中，根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷，包括：
对所述多个CBR业务切片进行以太网报文封装，得到第二数据流，所述第二数据流包括多个码块；
对所述第二数据流按照所述每个子用户sub-client子时隙净荷的长度进行切片，获得所述多个子用户sub-client子时隙净荷。
在一个具体的实施方式中，所述第二数据流包括多个64B/66B码块或多个64B/65B码块或多个256B/257B码块。
在一个具体的实施方式中，所述第一数据流包括多个OAM码块，用于承载OAM信息。
在一个具体的实施方式中，根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷，包括：
将每个所述CBR业务切片直接作为一个子用户sub-client子时隙净荷。
在一个具体的实施方式中，所述第一数据流包括多个64B/66B码块或多个64B/65B码块或多个256B/257B码块。
需要说明的是，对于CBR业务数据流进行切片，封装以及获得所述多个子用户sub-client子时隙净荷的具体过程，可参见上文中对于图13至图15所对应的方法200，方法1400以及方法1500中的相关说明，此处不再赘述。
在一个具体的实施方式中，所述方法还包括：所述第一通信装置接收第二通信装置发送的第一sub-client子时隙映射表，所述第一sub-client子时隙映射表用于指示所述M个子时隙和所述Z个sub-client接口之间的第一映射关系，每个所述sub-client接口映射所述M个子时隙中的至少一个子时隙；
保存所述第一sub-client子时隙映射表。
在一个具体的实施方式中，所述第一sub-client子时隙映射表通过Z个子用户标识sub-client ID和M个子时隙标识sub-slot ID的映射来指示所述第一映射关系，其中，所述Z个sub-client ID分别用于指示所述Z个sub-client接口，所述M个sub-slot ID分别用于指示所述M个子时隙。
在一个具体的实施方式中，所述第二通信装置可以是控制管理设备或与所述第一通信装置进行数据通信的转发装置。控制管理设备例如可以是网管或者控制器等。转发装置例如可以是用于转发的装置，例如，路由器，交换机，防火墙，分组传输网络PTN设备等，还可以是网络设备中的单板。
在一个具体的实施方式中，所述第一sub-client子时隙映射表被承载在所述基帧开销中。或者，所述第一sub-client子时隙映射表被承载在所述M个子时隙的指定子时隙中。
在一个具体的实施方式中，本申请所提供的sub-client子时隙映射表包括子时隙编号和sub-client编号，每个sub-client可以映射多个子时隙，上述的映射也可以理解为配置或者占用。即每个sub-client通过映射的多个子时隙发送数据。通信的发送端和接收端按照相同的sub-client子时隙映射表发送以及恢复(或称之为解映射)相应的子时隙内所传输数据。
下面结合图17和图18示例性的说明第一通信装置获取第一sub-client子时隙映射表的方法流程。
图17示出了本申请提供的一种基于控制管理设备进行sub-client子时隙映射表配置的方法示意图。如图17所示，在通信的接收端和发送端，均由控制管理设备分别进行配置。
图18示出了本申请提供的一种基于数据通路配置sub-client子时隙映射表的方法示意图。如图17所示，控制管理设备只配置发送端的sub-client子时隙映射表，发送端通过数据通路传递至接收端，数据通路可以采用基帧开销中传输定义的时隙表传递通道来传输所述sub-client子时隙映射表，也可以指定M个子时隙中的特定子时隙中进行传递。如果是FlexE接口，还可以通过FlexE的开销传递sub-client子时隙映射表。本申请对与数据通路进行sub-client子时隙映射表的传递方式不做具体限制。
对于图17所对应的方法中，第一通信装置可以是发送端装置也可以是接收端装置。在图18所对应的方法中，第一通信装置作为接收端装置。
在一个具体的实施方式中，所述第一sub-client接口映射到所述第一接口的W个子时隙，所述生成第一数据流包括：
将所述多个第一sub-client子时隙净荷分别映射到所述W个子时隙，W为大于1的整数。
在一个具体的实施方式中，将所述多个第一sub-client子时隙净荷分别映射到所述W个子时隙，包括：
根据所述第一sub-client接口和所述W个子时隙的映射关系，基于所述第一接口的时隙调度周期，按顺序调度所述W个子时隙。可以根据所述第一sub-client子时隙映射表确定所述第一sub-client接口和所述W个子时隙的映射关系。
在一个具体的实施方式中，所述第一通信装置包括接收侧的第二sub-client接口，所述生成第一数据流，包括：
获取所述第二sub-client接口的多个第二sub-client子时隙净荷，
基于所述第二sub-client接口和所述第一sub-client接口之间的子时隙交叉关系，对所述多个第二sub-client子时隙净荷进行处理，得到所述多个第一sub-client子时隙净荷；
将所述多个第一sub-client子时隙净荷，封装在所述基帧净荷中。
该实施方式的具体实现可以参见下文中图20-图23中中间时隙交叉设备NE2中的具体说明。
在一个具体的实施方式中，获取所述第二sub-client接口的多个第二sub-client子时隙净荷，包括：
获取接收侧的第二接口的第三数据流,按照第二sub-client子时隙映射表，从所述第三数据流中解映射出所述多个第二sub-client子时隙净荷，所述第二接口在时域上被划分为A个子时隙，所述第二接口逻辑上划分为B个sub-client接口，所述B个sub-client接口包括所述第二sub-client接口，所述第二子时隙时隙表用于指示所述A个子时隙和所述B个sub-client接口的第二映射关系。A和B均为整数。
第三数据流对应于图20-图23中中间时隙交叉设备NE2中的高阶通道，即某个client接口或某个以太接口中所获取的数据流。
在一个具体的实施方式中，所述第二接口为以太接口。
在一个具体的实施方式中，所述第二接口为第二FlexE Cilent接口。
在一个具体的实施方式中，所述第一通信装置还包括接收侧的第二FlexE接口，所述获取所述第三数据流，包括：
获取所述第二FlexE接口的第四数据流，所述第二FlexE接口从逻辑上被划分为多个FlexE client接口，所述多个FlexE client接口包括所述第二FlexE client接口；
根据所述第二FlexE client接口和所述第二flexE接口的时隙映射关系，从所述第四数据流中解映射出所述第三数据流，所述第三数据流包括多个第二基帧，所述多个第二基帧包括所述多个第二sub-client子时隙净荷其中。
第二FlexE接口例如可以是图20或图21中所示的接收侧的FlexE接口。第四数据流为接收侧的FlexE接口所获取的数据流。所示第三数据流例如可以是图21或图22中所示出的高阶通道client-1所对应的数据流。
下面结合图19来举例说明本申请所提供的方法1600中通过所述第一接口发送所述第一数据流的具体方法1900。
S1901：按顺序调度M个子时隙。其中，第一接口(FlexE Client接口或普通ETH接口)在发送端通过FlexE sub-shim层配置TDM时隙调度器，按照顺序调度M个子时隙。所述TDM时隙调度器按照第一接口所划分的M个子时隙为一个时隙调度周期，循环调度。
S1902：根据子时隙调度的顺序，将所述第一数据流中所包括的多个不同sub-client子时隙净荷，基于第一sub-client子时隙映射表，分别映射到对应的sub-client接口所对应的子时隙。
S1903：基帧封装。一个具体的实现中，每M个子时隙平均分布X个基帧。则每调度M/X个子时隙，进行一次基帧封装，基帧封装的过程参见上文中的具体说明，此处不再赘述。
S1904，通过所述第一接口发送包含了多个基帧的所述第一数据流。
在上述方法1600中，由于每个sub-client的子时隙净荷和基帧开销都封装在基帧的净荷中，并且在以太网业务映射时，作为数据码块封装在/D/码块中，因此，即便是不支持标准FlexE模式的普通以太接口也可以基于本申请所提供的方法，在接口时隙带宽隔离。本申请提供的方法，通过重构基帧的格式，因此，无论是以太接口或者灵活以太接口，均可以实现大带宽中进一步的灵活的配置各种速率的小带宽。对于不同速率的低速率业务，可以提供多种灵活的带宽分配方案。极大提升了带宽的利用效率。
方法1600中，第一接口可以是以太接口或者灵活以太接口，可以用于承载普通以太业务，也可以用于承载CBR业务，技术方案的应用场景非常广泛。下面结合图20-23对于方法1600的应用场景做具体的举例说明。图20示出了基于flexE接口传输以太业务的方法流程示意图。图21示出了基于flexE接口传输CBR业务的方法流程示意图。图22示出了基于以太接口传输以太业务的方法流程示意图。图23示出了基于以太接口传输CBR业务的方法示意图。在图20到图23中，本申请所述的第一通信装置可以是图20-24任一附图中所示的源端业务接入设备NE1，中间时隙交叉设备NE2或宿端业务发送设备NE3。该第一通信 装置也可以是源端业务接入设备NE1，中间时隙交叉设备NE2或宿端业务发送设备NE3中的单板，用于执行图20至图23所对应的方法中的一个或多个操作。
下面结合图20，对基于flexE接口传输以太业务的方法进行简单介绍。如图20所示，在基于flexE进行通信的网络中，包括三种类型的设备，分别是：源端业务接入设备NE1，中间时隙交叉设备NE2和宿端业务发送设备NE3。
源端业务接入设备NE1：接收侧为以太网接口，发送侧为FlexE端口。接收侧端口收到以太网报文，首先完成分组层业务处理(比如VLAN、IP、MPLS、SR等)，然后按照以太网时隙映射过程将不同业务流映射到对应的低阶通道(即本申请所述的sub-Client接口，图20中所示出的sub-client1-1……sub-client 1-m)中，再装载到高阶通道(即本申请所述的FlexE Client接口，对应图20中所示的Client 1-1…Client1-n)，最后从FlexE接口发出。上述过程可以分别参见图12所对应的方法100中的相关说明，首先生成每个sub-Client子时隙净荷，然后基于图19所对应的方法，基于sub-client子时隙映射表，通过TDM时隙调度器，将每个sub-Client子时隙净荷映射到每个sub-client所对应的子时隙上，然后进行相应的基帧封装，从对应的Flex-client接口中发出。每个Flex-client接口与对应的FlexE接口之间的映射过程，属于现有实现，此处不再赘述。
中间时隙交叉设备NE2：接收侧和发送侧均为FlexE接口。首先从接收的FlexE高阶通道(即本申请所述的FlexE Client接口，对应图20中所示的Client 1-1…Client1-n)中按照sub-client子时隙表解映射出低阶通道(即本申请所述的sub-Client接口，图20中所示出的sub-client1-1……sub-client 1-m)时隙，然后进行低阶时隙交叉到出口低阶通道(即本申请所述的sub-Client接口，图20中所示出的sub-client2-1……sub-client 2-m)中，出口低阶通道(即本申请所述的FlexE Client接口，对应图20中所示的Client 2-1…Client2-n)再装载到高阶通道从发送侧FlexE接口发出。
在NE2上，所述低阶时隙交叉是基于接收侧的第二sub-client接口(例如，图20中NE2设备中sub-client 1-1)和发送侧的第一sub-client接口(例如，图20中所示的sub-client 2-1)之间的子时隙交叉关系，对第二sub-client接口中的多个第二sub-client子时隙净荷进行处理，得到所述第一sub-client接口的多个第一sub-client子时隙净荷，然后进行基帧封装。
宿端业务发送设备NE3：接收侧为FlexE端口，发送侧为以太网端口。首先从接收的FlexE高阶通道中按照sub-client子时隙映射表解映射出低阶通道时隙，然后按照以太网时隙解映射过程恢复成以太网报文，完成分组层业务处理后从发送侧以太网端口发出。
下面结合图21，对基于flexE接口传输CBR业务的方法进行简单介绍。如图21所示，在基于flexE进行通信的网络中，包括三种类型的设备，分别是：源端业务接入设备NE1，中间时隙交叉设备NE2和宿端业务发送设备NE3。
源端业务接入设备NE1：接收侧为E1/E3/T1/T3/STM-N/FC等CBR业务接口，发送侧为FlexE接口。接收侧端口收到CBR业务比特流后按照图13或图14或图15任一所述的方法，获取CBR业务sub-cient子时隙净荷，将获得的多个CBR业务sub-cient子时隙净荷对应的不同CBR业务流分别映射到对应的低阶通道(即本申请所述的sub-Client接口，图21中所示出的sub-client1-1……sub-client 1-m)中，再装载到高阶通道(即本申请所述的FlexE Client接口，对应图20中所示的Client 1-1…Client1-n)从FlexE接口发出。具体来说，可以基于图19所对应的方法，基于sub-client子时隙映射表，通过TDM时隙调度器，将每个CBR业务的sub-Client子时隙净荷映射到每个sub-client所对应的子时隙上，然后进行相应的基帧封装，从对应的Flex-client接口中发出。每个Flex-client接口与对应的FlexE接口之间的映射过程，属于现有实现，此处不再赘述。
中间时隙交叉设备：和图20所示的中间时隙交叉设备相同。此处不再赘述。
宿端业务发送设备：接收侧为FlexE接口口，发送侧为1/E3/T1/T3/STM-N/FC等CBR业务接口。从接 收的FlexE高阶通道中按照时隙表解映射出低阶通道时隙，然后按照CBR时隙解映射过程恢复成CBR业务比特流，完成后从发送侧CBR业务接口发出。
在flexE接口传输CBR业务时，关于对CBR业务进行切片，封装以及基帧封装的过程，参见上文中相关描述，此处不再赘述。
下面结合图22，对基于以太接口传输以太业务的方法进行简单介绍。
图22中，在基于flexE进行通信的网络中，包括三种类型的设备，分别是：源端业务接入设备NE1，中间时隙交叉设备NE2和宿端业务发送设备NE3。
图22和图20的主要区别在于网络侧接口是普通以太接口而不是FlexE接口。
源端业务接入设备NE1：接收侧为以太接口，发送侧为以太接口。接收侧端口收到以太网报文，首先完成分组层业务处理(比如VLAN、IP、MPLS、SR等)，按照图12所对应的方法获得多个sub-client的子时隙净荷。然后基于图19所示的方法，对所述多个sub-client的子时隙净荷按照sub-client子时隙映射表进行时隙映射，在进行基帧封装后，从对应的以太接口发出。
中间时隙交叉设备NE2：接收侧和发送从均为以太接口。首先从以太接口按照sub-client子时隙表解映射出低阶通道(即本申请所述的sub-Client接口，图22中所示出的sub-client1-1……sub-client 1-m)的子时隙，然后进行低阶时隙交叉到出口低阶通道(即本申请所述的sub-Client接口，图22中所示出的sub-client2-1……sub-client 2-m)中。然后基于图19所示的方法，对所述多个sub-client的子时隙净荷按照sub-client子时隙映射表进行时隙映射，在进行基帧封装后，从对应的以太接口发出。
在NE2上，所述低阶时隙交叉是基于接收侧的第二sub-client接口(例如，图22中NE2设备中sub-client 1-1)和发送侧的第一sub-client接口(例如，图22中所示的sub-client 2-1)之间的子时隙交叉关系，对第二sub-client接口中的多个第二sub-client子时隙净荷进行处理，得到所述第一sub-client接口的多个第一sub-client子时隙净荷，然后进行所述基帧封装。
宿端业务发送设备NE3：接收侧为以太接口，发送侧为以太接口。首先从接收侧的以太接口中按照sub-client子时隙映射表解映射出低阶通道时隙，然后按照以太网时隙解映射过程恢复成以太网报文，完成分组层业务处理后从发送侧以太网端口发出。
下面结合图23，对基于以太接口传输CBR业务的方法进行简单介绍。
图23中，在基于flexE进行通信的网络中，包括三种类型的设备，分别是：源端业务接入设备NE1，中间时隙交叉设备NE2和宿端业务发送设备NE3。
源端业务接入设备：接收侧为E1/E3/T1/T3/STM-N/FC等CBR业务接口，发送侧为以太接口。接收侧端口收到CBR业务比特流后按照图13或图14或图15任一所述的方法，获取CBR业务sub-cient子时隙净荷，将获得的多个CBR业务sub-cient子时隙净荷对应的不同CBR业务流分别映射到对应的低阶通道(即本申请所述的sub-Client接口，图23中所示出的sub-client1-1……sub-client 1-m)中。然后基于图19所示的方法，对所述多个sub-client的子时隙净荷按照sub-client子时隙映射表进行时隙映射，在进行基帧封装后，从对应的以太接口发出。
中间时隙交叉设备：和图22的中间时隙交叉设备相同。此处不再赘述。
宿端业务发送设备：接收侧为灵活以太接口，发送侧为1/E3/T1/T3/STM-N/FC等CBR业务接口。。首先从接收侧的以太接口中按照sub-client子时隙映射表解映射出低阶通道时隙，然后按照CBR时隙解映射过程恢复成CBR业务比特流，完成后从发送侧CBR业务接口发出。
下面结合图24，对本申请实施例所提供的一种通信装置700进行介绍。通信装置700可以应用于图3所示的网络架构中。举例来说，通信装置700例如可以是本申请所述网络设备1(TX)或者网络设备2(RX)，通信装置700还可以是本申请所述的第一通信装置或第二通信装置。本申请所述的第一通信装置和第二通信装置可以是整体的网络设备，也可以是网络设备1中的单板，例如接口板或者线卡或哑板或集中交叉板。 通信装置800还可以是本申请所述控制管理设备，执行控制管理设备所执行的各种操作。通信装置700用于执行前述图6-图23任一附图所对应的实施例的方法。通信装置700包括收发单元701和处理单元702。收发单元701用于执行收发操作，处理单元用于执行收发以外的操作。例如，当通信装置700作为第一通信装置执行图16所示的方法1600时，处理单元702用于生成所述第一数据流，收发单元701可以用于发送所述第一数据流。
下面结合图25，对本申请实施例所提供的另一种通信装置800进行介绍。通信装置800可以应用于图3所示的网络架构中。举例来说，通信装置800例如可以是本申请所述网络设备1(TX)或者网络设备2(RX)，通信装置800还可以是本申请所述的第一通信装置或第二通信装置。通信装置800还可以是本申请所述控制管理设备，执行控制管理设备所执行的各种操作。本申请所述的第一通信装置和第二通信装置可以是整体的网络设备，也可以是网络设备1中的单板，例如接口板或者线卡或哑板或集中交叉板。通信装置800用于执行前述图6-图23任一附图所对应的实施例的方法。网络设备800包括通信接口801以及与通信接口相连的处理器802。通信接口801用于执行收发操作，处理器802用于执行收发以外的操作。例如，当通信装置800作为第一通信装置执行图16所示的方法1600时，处理器802用于生成所述第一数据流，通信接口801可以用于发送所述第一数据流。
下面结合图26，对本申请实施例提供的另一种通信装置900进行介绍。通信装置900可以应用于图3所示的网络架构中。举例来说，通信装置900例如可以是本申请所述网络设备1(TX)或者网络设备2(RX)，通信装置900还可以是本申请所述的第一通信装置或第二通信装置。通信装置900还可以是本申请所述控制管理设备，执行控制管理设备所执行的各种操作。本申请所述的第一通信装置和第二通信装置可以是整体的网络设备，也可以是网络设备1中的单板，例如接口板或者线卡或哑板或集中交叉板。通信装置900用于执行前述图6-图23任一附图所对应的实施例的方法。通信装置900包括存储器901和与所述存储器相连的处理器902。存储器901中存储有指令，处理器902读取所述指令，使得通信装置900执行图6-图23任一附图所对应的实施例的方法。
下面结合图27，对本申请实施例提供的另一种通信装置1000进行介绍。通信装置800可以应用于图3所示的网络架构中。举例来说，通信装置800例如可以是本申请所述网络设备1(TX)或者网络设备2(RX)，通信装置1000还可以是本申请所述的第一通信装置或第二通信装置。通信装置1000还可以是本申请所述控制管理设备，执行控制管理设备所执行的各种操作。本申请所述的第一通信装置和第二通信装置可以是整体的网络设备，也可以是网络设备1中的单板，例如接口板或者线卡或哑板或集中交叉板。通信装置800用于执行前述图6-图23任一附图所对应的实施例的方法。如图27所示，通信装置1000包括处理器1010，与所述处理器耦合连接的存储器1020以及通信接口1030。在一个具体的实施方式中，存储器1020中存储有计算机可读指令，所述计算机可读指令包括多个软件模块，例如发送模块1021，处理模块1022和接收模块1023。处理器1010执行各个软件模块后可以按照各个软件模块的指示进行相应的操作。在本实施例中，一个软件模块所执行的操作实际上是指处理器1010根据所述软件模块的指示而执行的操作。例如，当网络设备1000作为第一通信装置执行图16所示的方法时，发送模块1021用于发送所述第一数据流，处理模块1022用于生成所述第一数据流。此外，处理器1010执行存储器1020中的计算机可读指令后，可以按照计算机可读指令的指示，执行本申请中由第一通信装置可以执行的全部操作。例如，当通信装置1000作为第一通信装置时，通信装置1000可以执行图6-图23任一附图所对应的实施例中由第一通信装置所执行的方法。
在本申请中所提到的处理器可以是中央处理器(英文：central processing unit，缩写：CPU)，网络处理器(英文：network processor，缩写：NP)或者CPU和NP的组合。处理器还可以是专用集成电路(英文：application-specific integrated circuit，缩写：ASIC)，可编程逻辑器件(英文：programmable logic device，缩写：PLD)或其组合。上述PLD可以是复杂可编程逻辑器件(英文：complex programmable  logic device，缩写：CPLD)，现场可编程逻辑门阵列(英文：field-programmable gate array，缩写：FPGA)，通用阵列逻辑(英文：generic array logic,缩写：GAL)或其任意组合。处理器1010可以是指一个处理器，也可以包括多个处理器。本申请中所提到的存储器可以包括易失性存储器(英文：volatile memory)，例如随机存取存储器(英文：random-access memory，缩写：RAM)；存储器也可以包括非易失性存储器(英文：non-volatile memory)，例如只读存储器(英文：read-only memory，缩写：ROM)，快闪存储器(英文：flash memory)，硬盘(英文：hard disk drive，缩写：HDD)或固态硬盘(英文：solid-state drive，缩写：SSD)；存储器还可以包括上述种类的存储器的组合。存储器可以是指一个存储器，也可以包括多个存储器。
本申请实施例还提供了一种通信系统，包括第一通信装置和第二通信装置，其中，第一通信装置或者第二通信装置可以图24-图27任一项所述的通信装置，用与执行图6至图23对对应的任意一个实施例中的方法。所述通信系统还可以包括本申请所述的控制管理设备。
本申请还提供了一种计算机程序产品，包括计算机程序，当其在计算机上运行时，使得计算机可以执行图6至图23对应的任意一个实施例中由第一通信装置，第二通信装置或控制管理设备所执行的方法。
本申请还提供了一种计算机程序产品，包括计算机程序，当其在计算机上运行时，使得计算机可以执行图6至图23对应的任意一个实施例中由第一通信装置，第二通信装置或控制管理设备所执行的方法。
本申请提供了一种计算机可读存储介质，包括计算机指令，当其在计算机上运行时，使得计算机可以执行图6至图23对应的任意一个实施例中由第一通信装置，第二通信装置或控制管理设备所执行的方法。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的模块及方法操作，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和模块的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在上述实施例中，可以全部或部分地通过硬件、固件或者其任意组合来实现。当具体实现过程中涉及软件时，可以全部或部分地体现为计算机程序产品的形式。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
本说明书的各个部分均采用递进的方式进行描述，各个实施方式之间相同相似的部分互相参见即可，每个实施方式重点介绍的都是与其他实施方式不同之处。尤其，对于装置和系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例部分的说明即可。

Claims (49)

  1. 一种传输数据的方法，其特征在于，由第一通信装置实施，所述方法包括：
    生成第一数据流，所述第一数据流包括多个数据码块；
    所述多个数据码块包括多个第一基帧，每个第一基帧包括基帧净荷，所述基帧净荷包括基帧开销和多个子用户sub-client子时隙净荷，所述多个sub-client子时隙净荷包括多个第一sub-client子时隙净荷，所述多个第一sub-client子时隙净荷包括第一sub-client接口的业务数据；
    通过所述第一接口发送所述第一数据流。
  2. 根据权利要求1所述的方法，其特征在于，所述第一接口在逻辑上被划分为Z个sub-client接口，所述Z个sub-client接口包括所述第一sub-client接口,Z为大于1的整数。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一接口为灵活以太用户FlexE client接口。
  4. 根据权利要求1或2所述的方法，其特征在于，所述第一接口为以太接口。
  5. 根据权利要求1或2所述的方法，其特征在于，所述第一接口为第一灵活以太用户FlexE client接口，所述第一通信装置还包括发送侧的第一flexE接口，所述通过所述第一接口发送所述第一数据流，包括：
    根据所述第一FlexE client接口和所述第一flexE接口的时隙映射关系，通过所述第一flexE接口发送所述第一数据流，其中，所述第一FlexE接口从逻辑上被划分为多个FlexE client接口，所述多个FlexE client接口包括所述第一FlexE client接口。
  6. 根据权利要求1-5任一项所述的方法，其特征在于，所述每个第一基帧还包括第一码块和第二码块，所述第一码块用于指示所述第一基帧的帧头，所述第二码块用于指示所述第一基帧的帧尾。
  7. 根据权利要求6所述的方法，其特征在于，所述第一码块为S码块，所述第二码块为T码块。
  8. 根据权利要求6或7所述的方法，其特征在于，所述第一码块包括第一指示字段和第一数据字段，所述第一指示字段用于指示所述帧头，所述第一数据字段用于承载所述基帧净荷的部分数据。
  9. 根据权利要求6-8任一项所述的方法，其特征在于，所述第二码块包括第二指示字段和第二数据字段，所述第二指示字段用于指示所述帧尾，所述第二数据字段用于承载所述基帧净荷的部分数据。
  10. 根据权利要求6-9所述的方法，其特征在于，所述第一码块和所述第二码块的格式遵从电子工程师学会IEEE 802.3标准所定义的码块格式。
  11. 根据权利要求1-10任一项所述的方法，其特征在于，所述基帧开销包括一项或多项信息：
    基帧的序列号；
    sub-client子时隙映射表；
    时隙调整请求信息；
    时隙调整响应信息；
    时隙剩下指示信息；
    管理通道信息；
    基帧开销校验信息。
  12. 根据权利要求1-11任一项所述的方法，其特征在于，所述第一接口在时域上被划分为M个子时隙，所述M个子时隙中的每个子时隙的时隙带宽为P，P<5吉比特/秒Gbp/s，M是大于1的整数。
  13. 根据权利要求12所述的方法，其特征在于，所述M个子时隙平均分布在X个第一基帧中，每调度M/X个子时隙，执行一次基帧封装，每个所述基帧净荷包括M/X个sub-client子时隙净荷，X为大于1的整数。
  14. 根据权利要求1-13任一项所述的方法，其特征在于，所述第一接口的传输速率为N Gbp/s，N大 于等于1。
  15. 根据权利要求12或13所述的方法，其特征在于，所述方法还包括：
    接收第二通信装置发送的第一sub-client子时隙映射表，所述第一sub-client子时隙映射表用于指示所述M个子时隙和所述Z个sub-client接口之间的第一映射关系，每个所述sub-client接口映射所述M个子时隙中的至少一个子时隙；
    保存所述第一sub-client子时隙映射表。
  16. 根据权利要求15所述的方法，其特征在于，所述第一sub-client子时隙映射表通过Z个子用户标识sub-client ID和M个子时隙标识sub-slot ID的映射来指示所述第一映射关系，其中，所述Z个sub-client ID分别用于指示所述Z个sub-client接口，所述M个sub-slot ID分别用于指示所述M个子时隙。
  17. 根据权利要求15或16所述的方法，其特征在于，所述第二通信装置为控制管理设备。
  18. 根据权利要求15或16所述的方法，其特征在于，所述第二通信装置为转发装置。
  19. 根据权利要求15-18任一项所述的方法，其特征在于，所述第一sub-client子时隙映射表被承载在所述基帧开销中；或者，所述第一sub-client子时隙映射表被承载在所述M个子时隙的指定子时隙中。
  20. 根据权利要求1-19任一项所述的方法，其特征在于，所述第一数据流用于承载以太网业务。
  21. 根据权利要求20所述的方法，其特征在于，所述生成第一数据流，包括：
    从物理编码子层PCS获取第一以太业务数据流；
    对所述第一以太业务数据流进行切片，得到多个以太业务切片；
    将所述多个以太业务切片作为所述多个子用户sub-client子时隙净荷，封装在所述基帧净荷中。
  22. 根据权利要求21所述的方法，其特征在于，所述第一以太业务数据流包括多个64B/66B码块或多个64B/65B码块或多个256B/257B码块。
  23. 根据权利要求1-19任一项所述的方法，其特征在于，所述第一数据流用于承载固定比特流CBR业务。
  24. 根据权利要求23所述的方法，其特征在于，所述生成第一数据流，包括：
    对第一CBR业务数据流进行切片，得到多个CBR业务切片数据,所述第一CBR业务数据流包括多个CBR业务帧；
    对所述多个CRB业务切片数据分别进行切片封装，得到多个CBR业务切片，每个所述CBR业务切片包括所述CBR业务切片数据以及封装信息；
    根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷；
    将所述多个子用户sub-client子时隙净荷封装在所述基帧净荷中。
  25. 根据权利要求24所述的方法，其特征在于，每个所述CBR业务切片的切片粒度为i比特bits，在对所述第一CBR业务数据流进行切片时不识别所述多个CBR业务帧的内容，i为整数。
  26. 根据权利要求24所述的方法，其特征在于，每个所述CBR业务切片的切片粒度为j个完整的CBR业务帧，j为大于等于1的整数。
  27. 根据权利要求24-26任一项所述的方法，其特征在于，所述CBR业务切片包括第一字段，用于承载所述CBR业务切片数据。
  28. 根据权利要求24-27任一项所述的方法，其特征在于，所述封装信息包括第二字段，所述第二字段用于承载时钟频率信息。
  29. 根据权利要求24-28任一项所述的方法，其特征在于，所述封装信息包括第三字段，所述第三字段用于承载操作，管理和维护OAM信息。
  30. 根据权利要求24-29任一项所述的方法，其特征在于，所述封装信息包括第四字段，所述第四字 段用于承载CBR业务切片的序列号。
  31. 根据权利要求30所述的方法，其特征在于，所述CBR业务切片的序列号用于切片重组。
  32. 根据权利要求24-31任一项所述的方法，其特征在于，所述封装信息包括第五字段，所述第五字段用于承载净荷长度信息，所述净荷长度信息为每个所述CBR业务切片中所承载的CBR业务切片数据的有效长度。
  33. 根据权利要求24-32任一项所述的方法，其特征在于，所述封装信息包括第六字段，所述第六字段为填充字段。
  34. 根据权利要求24-33任一项所述的方法，其特征在于，所述封装信息包括第七字段，所述第七字段用于承载校验信息。
  35. 根据权利要求24-34任一项所述的方法，其特征在于，根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷，包括：
    对所述多个CBR业务切片进行以太网报文封装，得到第二数据流，所述第二数据流包括多个码块；
    对所述第二数据流按照所述每个子用户sub-client子时隙净荷的长度进行切片，获得所述多个子用户sub-client子时隙净荷。
  36. 根据权利要求35所述的方法，其特征在于，所述第二数据流包括多个64B/66B码块或多个64B/65B码块或多个256B/257B码块。
  37. 根据权利要求35或36所述的方法，其特征在于，所述第一数据流包括多个OAM码块，用于承载OAM信息。
  38. 根据权利要求24-34任一项所述的方法，其特征在于，根据所述多个CBR业务切片，获得所述多个子用户sub-client子时隙净荷，包括：
    将每个所述CBR业务切片直接作为一个子用户sub-client子时隙净荷。
  39. 根据权利要求1-38任一项所述的方法，其特征在于，所述第一数据流包括多个64B/66B码块或多个64B/65B码块或多个256B/257B码块。
  40. 根据权利要求1-39任一项所述的方法，其特征在于，所述第一sub-client接口映射到所述第一接口的W个子时隙，所述生成第一数据流包括：
    将所述多个第一sub-client子时隙净荷分别映射到所述W个子时隙，W为大于1的整数。
  41. 根据权利要求40所述的方法，其特征在于，将所述多个第一sub-client子时隙净荷分别映射到所述W个子时隙，包括：
    根据所述第一sub-client接口和所述W个子时隙的映射关系，基于所述第一接口的时隙调度周期，按顺序调度所述W个子时隙。
  42. 权利要求1-41任一项所述的方法，其特征在于，所述第一通信装置包括接收侧的第二sub-client接口，所述生成第一数据流，包括：
    获取所述第二sub-client接口的多个第二sub-client子时隙净荷，
    基于所述第二sub-client接口和所述第一sub-client接口之间的子时隙交叉关系，对所述多个第二sub-client子时隙净荷进行处理，得到所述多个第一sub-client子时隙净荷；
    将所述多个第一sub-client子时隙净荷，封装在所述基帧净荷中。
  43. 根据权利要求42所述的方法，其特征在于，获取所述第二sub-client接口的多个第二sub-client子时隙净荷，包括：
    获取接收侧的第二接口的第三数据流,按照第二sub-client子时隙映射表，从所述第三数据流中解映射出所述多个第二sub-client子时隙净荷，所述第二接口在时域上被划分为A个子时隙，所述第二接口逻辑上划分为B个sub-client接口，所述B个sub-client接口包括所述第二sub-client接口，所述 第二子时隙时隙表用于指示所述A个子时隙和所述B个sub-client接口的第二映射关系，A和B均为大于1的整数。
  44. 根据权利要求43所述的方法，其特征在于，所述第二接口为以太接口。
  45. 根据权利要求43或44所述的方法，其特征在于，所述第二接口为第二FlexE Cilent接口。
  46. 根据权利要求45所述的方法，其特征在于，所述第一通信装置还包括接收侧的第二FlexE接口，所述获取所述第三数据流，包括：
    获取所述第二FlexE接口的第四数据流，所述第二FlexE接口从逻辑上被划分为多个FlexE client接口，所述多个FlexE client接口包括所述第二FlexE client接口；
    根据所述第二FlexE client接口和所述第二flexE接口的时隙映射关系，从所述第四数据流中解映射出所述第三数据流，所述第三数据流包括多个第二基帧，所述多个第二基帧包括所述多个第二sub-client子时隙净荷。
  47. 一种第一通信装置，其特征在于，包括：
    存储器，存储有指令；
    与所述存储器相连的处理器，所述处理器执行所述指令时，使得所述第一通信装置执行权利要求1至46中任一项所述的方法。
  48. 一种计算机可读存储介质，其特征在于，包括程序或指令，当其在计算机上运行时，使得计算机执行如权利要求1-46任意一项所述的方法。
  49. 一种通信系统，包括权利要求47所述的第一通信装置和第二通信装置，用于执行权利要求1-46任一项所述的方法。
PCT/CN2021/105642 2020-07-25 2021-07-12 一种传输数据的方法和设备 WO2022022263A1 (zh)

Priority Applications (7)

Application Number Priority Date Filing Date Title
BR112023001387A BR112023001387A2 (pt) 2020-07-25 2021-07-12 Método de transmissão de dados e dispositivo
KR1020237005664A KR20230041057A (ko) 2020-07-25 2021-07-12 데이터 전송 방법 및 디바이스
CA3187237A CA3187237A1 (en) 2020-07-25 2021-07-12 Data transmission method and device
EP21849396.3A EP4178297A4 (en) 2020-07-25 2021-07-12 DATA TRANSMISSION METHOD AND DEVICE
MX2023001056A MX2023001056A (es) 2020-07-25 2021-07-12 Metodo de transmision de datos y dispositivo.
JP2023504859A JP2023535750A (ja) 2020-07-25 2021-07-12 データ伝送方法及びデバイス
US18/155,804 US20230155756A1 (en) 2020-07-25 2023-01-18 Data Transmission Method and Device

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202010726636.X 2020-07-25
CN202010726636 2020-07-25
CN202010761609.6A CN113972997A (zh) 2020-07-25 2020-07-31 一种传输数据的方法和设备
CN202010761609.6 2020-07-31

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/155,804 Continuation US20230155756A1 (en) 2020-07-25 2023-01-18 Data Transmission Method and Device

Publications (1)

Publication Number Publication Date
WO2022022263A1 true WO2022022263A1 (zh) 2022-02-03

Family

ID=79585014

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/105642 WO2022022263A1 (zh) 2020-07-25 2021-07-12 一种传输数据的方法和设备

Country Status (9)

Country Link
US (1) US20230155756A1 (zh)
EP (1) EP4178297A4 (zh)
JP (1) JP2023535750A (zh)
KR (1) KR20230041057A (zh)
CN (1) CN113972997A (zh)
BR (1) BR112023001387A2 (zh)
CA (1) CA3187237A1 (zh)
MX (1) MX2023001056A (zh)
WO (1) WO2022022263A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114584258A (zh) * 2022-02-15 2022-06-03 烽火通信科技股份有限公司 业务时延降低方法、装置、设备及可读存储介质
CN115499085A (zh) * 2022-11-17 2022-12-20 之江实验室 一种灵活以太网小颗粒时隙分配方法及装置
WO2024032269A1 (zh) * 2022-08-09 2024-02-15 华为技术有限公司 通信方法、相关装置及计算机可读存储介质

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109728948B (zh) * 2018-12-26 2022-05-13 苏州盛科通信股份有限公司 一种运营维护管理信息处理方法和装置
CN116566542A (zh) * 2022-01-29 2023-08-08 中兴通讯股份有限公司 业务数据承载方法、承载帧结构及业务处理设备
CN116996418A (zh) * 2022-04-26 2023-11-03 华为技术有限公司 报文的处理方法及装置
CN117354159A (zh) * 2022-06-28 2024-01-05 中兴通讯股份有限公司 切片方法、业务处理方法、通信节点及存储介质
CN117439702A (zh) * 2022-07-15 2024-01-23 中兴通讯股份有限公司 数据传输方法及装置、电子设备、计算机可读介质
CN115276905B (zh) * 2022-07-22 2024-02-13 南京南瑞信息通信科技有限公司 一种基于FlexE传输系统的小带宽业务传输方法
CN115065439B (zh) * 2022-08-16 2022-11-11 中国信息通信研究院 一种spn网络恒定比特率业务传送方法和设备
CN115460704A (zh) * 2022-09-13 2022-12-09 中国电信股份有限公司 流量数据的处理方法及装置、存储介质、电子设备
CN115865277B (zh) * 2022-11-30 2023-12-15 苏州异格技术有限公司 灵活以太网的数据处理方法、装置、存储介质、电子设备
CN118353721B (zh) * 2024-06-18 2024-09-13 国网江苏省电力有限公司信息通信分公司 一种电力以太网业务传输设备、方法及存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632886A (zh) * 2017-03-21 2018-10-09 华为技术有限公司 一种业务处理方法及装置
CN109818704A (zh) * 2017-11-21 2019-05-28 华为技术有限公司 数据传输方法和设备
WO2019119388A1 (en) * 2017-12-22 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for configuring a flex ethernet node
WO2019153253A1 (zh) * 2018-02-09 2019-08-15 华为技术有限公司 一种光传送网中业务数据的处理方法及装置
CN111107641A (zh) * 2019-12-11 2020-05-05 Ut斯达康通讯有限公司 FlexE业务处理方法、装置及电子设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632886A (zh) * 2017-03-21 2018-10-09 华为技术有限公司 一种业务处理方法及装置
CN109818704A (zh) * 2017-11-21 2019-05-28 华为技术有限公司 数据传输方法和设备
WO2019119388A1 (en) * 2017-12-22 2019-06-27 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus for configuring a flex ethernet node
WO2019153253A1 (zh) * 2018-02-09 2019-08-15 华为技术有限公司 一种光传送网中业务数据的处理方法及装置
CN111107641A (zh) * 2019-12-11 2020-05-05 Ut斯达康通讯有限公司 FlexE业务处理方法、装置及电子设备

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
LIAO YUN; HASHEMI SEYYED ALI; ELBAKOURY HESHAM; CIOFFI JOHN; GOLDSMITH ANDREA: "Calendar Allocation Based on Client Traffic in the Flexible Ethernet Standard", ICC 2020 - 2020 IEEE INTERNATIONAL CONFERENCE ON COMMUNICATIONS (ICC), IEEE, 7 June 2020 (2020-06-07), pages 1 - 6, XP033798303, DOI: 10.1109/ICC40277.2020.9149293 *
See also references of EP4178297A4

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114584258A (zh) * 2022-02-15 2022-06-03 烽火通信科技股份有限公司 业务时延降低方法、装置、设备及可读存储介质
CN114584258B (zh) * 2022-02-15 2023-05-26 烽火通信科技股份有限公司 业务时延降低方法、装置、设备及可读存储介质
WO2024032269A1 (zh) * 2022-08-09 2024-02-15 华为技术有限公司 通信方法、相关装置及计算机可读存储介质
CN115499085A (zh) * 2022-11-17 2022-12-20 之江实验室 一种灵活以太网小颗粒时隙分配方法及装置

Also Published As

Publication number Publication date
CA3187237A1 (en) 2022-02-03
US20230155756A1 (en) 2023-05-18
BR112023001387A2 (pt) 2023-04-04
CN113972997A (zh) 2022-01-25
EP4178297A1 (en) 2023-05-10
MX2023001056A (es) 2023-02-16
EP4178297A4 (en) 2024-01-03
JP2023535750A (ja) 2023-08-21
KR20230041057A (ko) 2023-03-23

Similar Documents

Publication Publication Date Title
WO2022022263A1 (zh) 一种传输数据的方法和设备
US11316545B2 (en) Data transmission method, communications device, and storage medium
WO2010020130A1 (zh) 包分插复用设备及包分插复用设备的数据传输方法
EP2395682A1 (en) A service adaptation method and service adaptation device
CN113452623B (zh) 基于FlexE传输业务流的方法及设备
WO2011057545A1 (zh) 传输多路业务的方法和装置
WO2022042743A1 (zh) 数据传输方法和装置、电子设备、计算机可读介质
KR20200103070A (ko) 데이터 송신 방법, 통신 디바이스, 및 저장 매체
WO2017177549A1 (zh) 无源光网络架构及其实现数据传输的方法和光网络设备
EP4117237A1 (en) Service flow adjustment method and communication device
US20230412446A1 (en) Method for Determining Transmission Slot and Related Apparatus
WO2019114544A1 (zh) 一种数据传送的方法、设备和系统
WO2021073406A1 (zh) 一种业务数据的传输方法、相关设备以及数字处理芯片
WO2023109424A1 (zh) 一种数据传输的方法以及相关装置
CN113472826A (zh) 一种业务承载、提取方法、数据交换方法及设备
US11451420B2 (en) Data transmission method, communications device, and storage medium
CN115811388A (zh) 一种通信方法、相关装置以及存储介质
CN100384177C (zh) 一种以太网在多个e1信道中传输的方法
WO2023116284A1 (zh) 一种灵活以太网FlexE中小颗粒业务的时隙协商及装置
JP2002101103A (ja) 基地局変復調装置及びａｔｍセル送受信方法
WO2023071249A1 (zh) 一种时隙协商方法及装置
CN118054891A (zh) 时隙调整方法、通信装置及计算机可读存储介质
WO2024087975A1 (zh) 一种通信方法及装置
WO2024032191A1 (zh) 一种故障码块处理方法及装置
CN118677718A (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: 21849396

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2023504859

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 3187237

Country of ref document: CA

WWE Wipo information: entry into national phase

Ref document number: 202337005293

Country of ref document: IN

REG Reference to national code

Ref country code: BR

Ref legal event code: B01A

Ref document number: 112023001387

Country of ref document: BR

ENP Entry into the national phase

Ref document number: 2021849396

Country of ref document: EP

Effective date: 20230201

ENP Entry into the national phase

Ref document number: 20237005664

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 112023001387

Country of ref document: BR

Kind code of ref document: A2

Effective date: 20230125