CN111586752B

CN111586752B - Configuration method and device of time slot container

Info

Publication number: CN111586752B
Application number: CN201910120305.9A
Authority: CN
Inventors: 占治国; 陈捷
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2019-02-18
Filing date: 2019-02-18
Publication date: 2023-07-14
Anticipated expiration: 2039-02-18
Also published as: CN111586752A; WO2020169009A1

Abstract

The application provides a configuration method and device of a time slot container, and specifically the method comprises the following steps: establishing a time slot container according to customer service; sub-slot division is carried out on the time slot container; mapping the customer service into one or a group of divided sub-slots. According to the method and the device, the problem that the flexibility of the small-particle customer service in the transmission process is low is solved, and the flexible mixed transmission of the small-particle customer service in the rigid pipeline is realized.

Description

Configuration method and device of time slot container

Technical Field

The present invention relates to the field of communications, and in particular, to a method and an apparatus for configuring a timeslot container.

Background

The flexible ethernet (FlexE-Flexible Ethernet) technology was studied by the international standardization organization OIF at month 3 of 2015 and officially voted through the relevant technical documents at month 3 of 2016. The flexible ethernet technology provides a general mechanism to transmit a series of services with different media access control MAC (Media Access Control) rates, which may be a service with a relatively large single MAC rate, or a set of services with a relatively small multiple MAC rates, and is not limited to a service with a single MAC rate.

The current FlexE standard supports a customer service of N5G granularity, which is less efficient and wasteful for carrying customer services smaller than 5G granularity. Although some methods for supporting small-granule customer service are also proposed in the industry, the method is improved on the time slot of the original 5G granule of FlexE, and has the disadvantages of low flexibility, difficulty in supporting the mixed transmission of small-granule customer service with different granule sizes in one 5G time slot, and difficulty in realizing that the same small-granule customer service is distributed and carried on different PHYs.

Disclosure of Invention

The embodiment of the application provides a configuration method and a device of a time slot container, which are used for at least solving the problem of low flexibility of small-particle customer service in the transmission process in the related technology.

According to an embodiment of the present application, there is provided a method for configuring a timeslot container, including: establishing a time slot container according to customer service; sub-slot division is carried out on the time slot container; mapping the customer service into one or a group of divided sub-slots.

Optionally, the timeslot container is located between the customer service and a FlexE calendar.

Optionally, before sub-slot division of the slot container, the method includes: allocating a preset number of FlexE slots of 5G granules to each slot container; wherein a predetermined number of FlexE slots of the 5G granule are located in one FlexE group, provided by the same or different PHYs.

Optionally, sub-slot division is performed on the slot container, including: the sub-slots are divided by base particles in the data payload portion of each of the slot containers.

Optionally, when sub-slot partitioning the slot container, the method further comprises: and reserving a specified number of data blocks in the time slot container as overhead blocks of the time slot container, wherein the overhead blocks carry indication information for indicating the mapping relationship between the client service and the divided sub-slots.

Optionally, mapping the customer service into one or a group of divided sub-slots includes: and mapping the client service to one or a group of data payloads corresponding to the divided sub-slots according to the indication information.

Optionally, the method further comprises: and switching the client service in the time slot container according to the FlexE overhead field and/or the overhead block.

Optionally, the starting position of the customer service is determined by at least one of the following means: multiframe of FlexE, overhead in the slot container.

According to one embodiment of the present application, there is provided a configuration apparatus of a timeslot container, an establishing module, configured to establish the timeslot container according to customer service; the division module is used for carrying out sub-time slot division on the time slot container; and the mapping module is used for mapping the client service into one or a group of divided sub-slots.

According to a further embodiment of the present application, there is also provided a storage medium having stored therein a computer program, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

According to a further embodiment of the present application, there is also provided an electronic device comprising a memory having stored therein a computer program and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

According to the method and the device, the sub-slot division is carried out by utilizing the time slot container corresponding to the customer service, and the customer service is mapped into the divided sub-slot. Therefore, the problem of low flexibility of small-particle customer service in the transmission process can be solved, and the flexible mixed transmission of the small-particle customer service in a rigid pipeline is realized.

Drawings

The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:

FIG. 1 is a flow chart of a method of configuring a slot container according to an embodiment of the present application;

FIG. 2 is a hierarchical diagram of a slot container according to an embodiment of the present application;

FIG. 3 is a block diagram of a slot container according to an embodiment of the present application;

FIG. 4 is a schematic diagram of division of sub-slots based on scenario 1 according to an embodiment of the present application;

FIG. 5 is a schematic view of a calclendar value based on scenario 1 according to an embodiment of the present application;

FIG. 6 is a schematic diagram of overhead arrangement of a scenario 1-based slot container according to an embodiment of the present application;

FIG. 7 is a schematic diagram of a FG-client calclendar based on scenario 1 according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a scene 1 based FG-client calendar A according to an embodiment of the present application;

FIG. 9 is a schematic diagram of an indication overhead for a scenario 1-based slot container according to an embodiment of the present application;

FIG. 10 is a customer service mapping relationship diagram based on scenario 1 according to an embodiment of the present application;

FIG. 11 is a schematic illustration of a scenario 2-based callendar handoff according to an embodiment of the present application;

FIG. 12 is a schematic diagram of a scene 2 based FG-client calendar B according to an embodiment of the present application;

FIG. 13 is a customer service mapping relationship diagram based on scenario 2 according to an embodiment of the present application;

Fig. 14 is a slot structure diagram based on scenario 3 according to an embodiment of the present application;

FIG. 15 is a schematic diagram of division of a sub-slot based on scenario 3 according to an embodiment of the present application;

FIG. 16 is a schematic diagram of overhead arrangement of a scenario 3-based slot container according to an embodiment of the present application;

fig. 17 is a schematic diagram of an OAM block based on scenario 3 according to an embodiment of the present application;

FIG. 18 is a schematic diagram of scene 3 based overhead according to an embodiment of the present application;

FIG. 19a is a schematic diagram one of a scene 3 based FG-client calendar A according to an embodiment of the present application;

FIG. 19b is a schematic diagram two of a scene 3 based FG-client calendar A according to an embodiment of the present application;

FIG. 19c is a schematic diagram two of a scene 3 based FG-client calendar A according to an embodiment of the present application;

FIG. 19d is a schematic diagram two of FG-client calendar A based on scenario 3 according to an embodiment of the present application;

FIG. 20 is a traffic map based on scenario 3 according to an embodiment of the present application;

FIG. 21a is a schematic diagram of a scene 4 based FG-client calendar B according to an embodiment of the present application;

FIG. 21b is a schematic diagram of a scene 4 based FG-client calendar B according to an embodiment of the present application;

FIG. 21c is a schematic diagram of a scene 4 based FG-client calendar B according to an embodiment of the present application;

FIG. 21d is a schematic diagram of a scene 4 based FG-client calendar B according to an embodiment of the present application;

FIG. 22 is a customer service mapping relationship diagram based on scenario 4 according to an embodiment of the present application;

fig. 23 is a slot structure diagram based on scenario 5 according to an embodiment of the present application;

FIG. 24 is a schematic diagram of partitioning of sub-slots based on scenario 5 according to an embodiment of the present application;

FIG. 25 is a schematic diagram of overhead arrangement of a scenario 5-based slot container according to an embodiment of the present application;

fig. 26 is a schematic diagram of an OAM block based on scenario 5 according to an embodiment of the present application;

FIG. 27 is a schematic diagram of scene 5 based overhead according to an embodiment of the present application;

FIG. 28 is a schematic diagram of a scene 5 based FG-client calendar A according to an embodiment of the present application;

FIG. 29 is a traffic map based on scenario 5 according to an embodiment of the present application;

FIG. 30a is a schematic diagram one of a scene 6 based FG-client calendar A according to an embodiment of the present application;

FIG. 30b is a schematic diagram two of a scene 6 based FG-client calendar A according to an embodiment of the present application;

Fig. 31 is a schematic diagram of initiating a CR within a slot container based on scenario 6, according to an embodiment of the present application;

fig. 32 is a schematic diagram of a scenario 6-based CA received within a slot container according to an embodiment of the present application;

FIG. 33a is a schematic diagram one of a C-bit transmission based on scenario 6 according to an embodiment of the present application;

FIG. 33b is a schematic diagram two of a C-bit transmission based on scenario 6 according to an embodiment of the present application;

FIG. 34 is a schematic diagram of a scenario 6-based container switch to FG-client calendar B in time slots according to an embodiment of the present application;

FIG. 35 is a traffic map based on scenario 6 according to an embodiment of the present application;

FIG. 36 is an overhead schematic of a scenario 7-based slot container multiframe according to an embodiment of the present application;

FIG. 37 is a schematic diagram of a scenario 7-based slot container multiframe number and numbering according to an embodiment of the present application;

fig. 38 is a block diagram of a configuration apparatus of a slot container according to an embodiment of the present application.

Detailed Description

The present application will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that, in the case of no conflict, the embodiments and features in the embodiments may be combined with each other.

It should be noted that the terms "first," "second," and the like in the description and claims of the present application and the above figures are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order.

Example 1

In this embodiment, a method for configuring a timeslot container is provided, fig. 1 is a flowchart of a method for configuring a timeslot container according to an embodiment of the present application, as shown in fig. 1, where the flowchart includes the following steps:

step S102, establishing a time slot container according to customer service;

step S104, sub-slot division is carried out on the time slot container;

and step S106, mapping the customer service into one or a group of divided sub-slots.

5G in this document represents bandwidth.

Specifically, fig. 2 is a hierarchical diagram of a timeslot container according to an embodiment of the present application, as shown in fig. 2, where the Slot container in fig. 2 is the timeslot container described in this implementation. The timeslot container is located between FG-Client service (i.e. Client service) and a flexible ethernet calendar FlexE calendar, sub calendar being Sub calendar, N5G FlexE Client being a flexible ethernet Client of N5G.

It should be noted that, in consideration of the number of customer services that may exist, in this embodiment, a slot container is actually allocated for each customer service. So there may be a plurality of slot containers.

Optionally, before sub-slot division of the slot container, the method includes: allocating a preset number of FlexE slots of 5G granules to each slot container; wherein a predetermined number of FlexE slots of said 5G granules are located in one FlexE group, provided by the same or different physical layers (Port Physical Layer, abbreviated PHY).

In particular, flexE slots of different preset numbers of 5G granules can be allocated for different slot containers. For example, slot container 1 allocates i×5g slots, slot container 2 allocates j×5g slots, and slot container 3 allocates k×5g slots. Meanwhile, the specific location of the FlexE slot allocated by the slot container may be determined by at least one of the following means: indicated by the client calendar client calendar A and/or client calendar client calendar B fields of the FlexE overhead, or an overhead identification in the slot container.

Specifically, the sub-time slots are divided according to a certain basic granule in each time slot container, and the basic granules of different time slot containers can be the same or different. For example, for the slot container 1 to which i×5g slots are allocated, if the division is made with 250M as basic grains, the total number of sub slots in the slot container is i×20. For another example, for the slot container 2 to which j×5g slots are allocated, if the division is made with 500M as the basic granule, the total number of sub-slots in the slot container is i×10. For another example, for the slot container 3 to which k×5g slots are allocated, if the slots are divided by 1G as basic grains, the total number of sub slots in the slot container is i×5. Thus, in this embodiment, the base granularity is in a multiple relationship with 5G slots. The specific multiple relationship is determined, for example, according to a preset rule or a requirement of a customer service, and will not be described in detail herein.

Fig. 3 is a block diagram of a slot container according to an embodiment of the present application. As shown in fig. 3, each slot is divided into two parts. Part of the Data payload is the Data payload described above, that is, the sub-slot group comprising the divided sub-slots, overhead, data payload, sub-slot group. While the other part is the overhead block. The role of the overhead block is first to satisfy the overhead of the slot container. Secondly, an overhead of at least one of the following is carried in the overhead block: FG-client cache, location pointer and idle block. And if FG-client cache is carried in the overhead, the overhead block can also be used to indicate the mapped position of the sub-slots after the client traffic is divided in the slot container.

Specifically, the Flexe overhead field includes, but is not limited to, client calendar A/client calendar B, a calendar switch request CR (Calendar Switch Request, abbreviated CR), a calendar switch acknowledgement CA (Calendar Switch Acknowledg, abbreviated CA), and a calendar configuration in-use C bit (Calendar configuration in use, abbreviated C). Meanwhile, the overhead resource can also indicate the mapping position of the client service after the handover.

In order to better understand the technical solutions described in the foregoing embodiments, in this embodiment, the following scenario is further provided for understanding:

scene 1:

a certain FlexE-enabled node, the FlexE group contains only one 100G PHY. The 100G PHY is divided into 20 slots, each slot being 5G granularity. There is now a small particle customer service A (FG-client A for short) with a bandwidth of 250Mb/s, FG-client B with a bandwidth of 500Mb/s, and FG-client C with a bandwidth of 1Gb/s. Depending on the small particle customer traffic situation, this embodiment configures a slot container 1 that contains the first 5G slot of the 100G PHY for carrying these small particle customer traffic.

Slot container 1 divides sub-slots at a basic granularity of 250M and fig. 4 is a schematic diagram of division of sub-slots based on scenario 1 according to an embodiment of the present application. As shown in fig. 4:

1) Based on the current FlexE multiframe structure, each time slot is 1023×8×32= 261888 blocks with 66b size, 8 blocks are used as time slot container overhead, the remaining 261880 blocks are divided into 20 sub-time slots, each sub-time slot has 13094 blocks, namely 13094×20+8=1023×8×32, and the size of each sub-time slot is 250M.

2) Since only 8 blocks out of 261888 blocks are used as overhead, the bandwidth loss is 8/261888= 0.00305%, i.e. the bandwidth loss is less than 0.003% (30 PPM) of the nominal rate, within the allowable range.

3) Fig. 5 is a schematic diagram of a calclendar value based on scenario 1 according to an embodiment of the present application. As shown in fig. 5, the first 5G slot (slot 0) of the 100G allocated by slot container 1 is indicated by client calendar A/client calendar B of the FlexE overhead for carrying small particle customer traffic. Client calendar A/client calendar B in the OIF FlexE IA 2.0 standard is a 16-bit value, in this scenario the first 3 bits=111 by definition client calendar A slot/client calendar B slot0 indicates that the timeslot is allocated to a timeslot container carrying flexible granule customer traffic, and the first 3 bits=other values indicate that the timeslot is allocated to normal n×5g granule customer traffic. In this scenario, the identifier of the timeslot container 1 is 0xE001, and the client Calendar A/client Calendar B value of slot0 indicated in the corresponding FlexE Calendar is equal to 0xE001, which indicates that the timeslot belongs to the timeslot container 1.Client carried calendar A slot 0= 0xE001,Client carried calendar B slot0 =0xe001, meaning that the 5G time slot is allocated to carry flexible granular customer traffic.

The mapping process of small particle customer service initialization,

fig. 6 is a schematic diagram of overhead arrangement of a scenario 1-based slot container according to an embodiment of the present application. As shown in fig. 6, there are 8 blocks in the slot container as slot container overhead. The 8 blocks are allocated as follows, 5 blocks as FG-client calclendar, 1 block as pointer, 2 blocks as idle blocks.

FG-client coolant overhead: FG-client identification carried by sub-slots is denoted by 1 BYTE, 20 BYTEs are used for FG-client calendar A of 20 sub-slots, 20 BYTEs are used for FG-client calendar B of 20 sub-slots, and a total of 40 BYTE are used. FIG. 7 is a schematic diagram of a FG-client calclendar based on scenario 1 according to an embodiment of the present application. As shown in FIG. 7, the selection of FG-client Calendar A/B remains consistent with the selection of client Calendar A/B indicated in Flexe Calendar to which it belongs.

In this scenario, FIG. 8 is a schematic diagram of a scenario 1-based FG-client calendar A according to an embodiment of the present application. As shown in FIG. 8, FG-client calendar A is identified as 0x0A, FG-client calendar B is identified as 0x0B, and FG-client calendar C is identified as 0x0C.

In this scenario, fig. 9 is a schematic diagram of an indication overhead of a slot container based on scenario 1 according to an embodiment of the present application, as shown in fig. 9, the pointer overhead: the starting position of 13094 x 20 66b data blocks (data payloads) is denoted by 1 BYTE; the last two BYTE are CRC-16, checking the slot container overhead. At the present scene pointer value of 0x08, it means that the data payload starts from block 8 (i.e., the 9 th block of slot container). The pointer is 8, indicating that the payload of 13094 x 20 blocks starts at block 8 and the last two BYTEs are CRC-16.

The coding mode of the small particle customer service is converted from 8/10b to 64/66b.

Fig. 10 is a mapping relationship diagram of customer service based on scenario 1 according to an embodiment of the present application. As shown in fig. 10, small particle customer services a, B and C are interleaved into the data payload, i.e. 13094 x 20 66B data blocks.

Scene 2:

on the basis of scenario 1, the bandwidth of FG-client C is reduced from 1Gb/s to 750Mb/s, requiring that FG-client C be allocated sub-slots from the slot container from 4 to 3. Fig. 11 is a schematic diagram of a scenario 2-based calendar handoff according to an embodiment of the present application. As shown in fig. 11, the switching of the Calendar configuration is thus performed for small particle customer services a, B and C, including the synchronous switching of FlexE Calendar a and FG-client Calendar A to FlexE Calendar B and FG-client Calendar B. Fig. 12 is a schematic diagram of a scene 2 based FG-client calendar B in accordance with an embodiment of the present application. As shown in FIG. 12, the sub-slot configuration indication of FG-client calendar B after handoff is described with FG-client calendar A identified as 0x0A, FG-client calendar B identified as 0x0B, FG-client calendar C identified as 0x0C.

The home end node initiates a CR message in FlexE overhead, switching from client calendar A to client calendar B for this PHY. client calendar B is a 16 bit value, and the embodiment of the present invention is customized client calendar B slot 0.0.3bit=111 indicates that the timeslot is allocated to a timeslot container carrying flexible granular customer traffic, and reference may be made to fig. 5 in scenario 1 for a specific value.

After receiving the CR message, the correspondent node knows client calendar B slot that the time slot is allocated to the time slot container from client calendar B field of Flexe overhead;

and reading the time slot container overhead in the time slot container, knowing whether FG-client A corresponds to the 0 th sub-time slot, FG-client B corresponds to the 1 st and 2 nd sub-time slots and FG-client C corresponds to the 3 rd, 4 th and 5 th sub-time slots after switching to FG-client calendar B.

The opposite node is judged to be capable of switching.

The correspondent node replies a message to the CA in the FlexE overhead indicating that the handover is agreed.

After the home node receives the message of the CA,

replying to a C-bit=1 message,

the switch then formally proceeds to client calendar B in the next FlexE message frame, while FG-client calendar A in the slot container is also synchronously switched to FG-client calendar B.

Fig. 13 is a mapping relationship diagram of customer service based on scenario 2 according to an embodiment of the present application. As shown in fig. 13, flexible granular customer traffic is mapped to new sub-slots according to the overhead indication of the slot container.

The correspondent node receives the C bit=1 message,

Flexible granular client traffic is mapped to new sub-slots according to the overhead indication of the slot container.

Scene 3:

there is only one 100G PHY in a FlexE group for a FlexE-enabled node. The 100G PHY default is divided into 20 slots, each slot being 5G granularity. There is now a flexible granular customer service FG-client A bandwidth of Gb/s, FG-client B bandwidth of 1.25Gb/s, FG-client C bandwidth of 6Gb/s. Fig. 14 is a slot structure diagram based on scenario 3 according to an embodiment of the present application, according to the small particle customer service scenario. As shown in fig. 14, the scenario configures 1 slot container 1, which contains the first and second 5G slots of the 100G PHY for carrying customer traffic for these flexible particles. As shown in fig. 13.

The slot container divides sub-slots by granularity of 250M, and fig. 15 is a schematic diagram of division of sub-slots based on scenario 3 according to an embodiment of the present application.

1) Based on the current FlexE multiframe structure, in a multiframe period, each 5G slot is 1023×8×32= 261888 blocks with 66b size, 8 blocks are used as slot container overhead, the remaining 261880 blocks are divided into 20 sub-slots, each sub-slot has 13094 blocks, that is, 13094×20+8=1023×8×32, and each sub-slot has a size of 250M.

2) The above operation is the same for both 5G slots in the slot container. As in fig. 14.

Mapping process of flexible granular customer service initialization:

fig. 16 is a schematic diagram of overhead arrangement of a scenario 3-based slot container according to an embodiment of the present application. As shown in fig. 16, there are 8 blocks in the slot container as slot container overhead. The 8 blocks are allocated as follows:

the 1 st to 6 th blocks overhead contains OAM type, pointer information, FG-client calendar A/B and CRC-16.

The overhead of the 7 th and 8 th blocks is used as idle block.

Fig. 17 is a schematic diagram of an OAM block based on scenario 3 according to an embodiment of the present application. The OAM overhead of the 1 st block adopts an OAM specification defined by China Mobile Enterprise Standard, the general technical requirement of the China Mobile slice packet network (SPN 103661).

For the type definition, the extension defines a new type=0x16, representing a slot container carrying flexible granular customer traffic, and sub-slot division is performed.

Value1 is used as a pointer to indicate the position of 13094×20 66b data blocks (data payloads); at the present scene pointer value of 0x08, it means that the data payload starts from block 8.

Value2, value3, value4 represent slot containers FG-client calendar A subslot 0, FG-client calendar A subslot 1, and FG-client calendar A subslot 2.

Fig. 18 is a schematic diagram of scene 3-based overhead according to an embodiment of the present application. As shown in FIG. 18, the overhead of blocks 2 through 6 of the overhead arrangement of slot containers represent the slot containers FG-client calendar A subslot 3 through FG-client calendar A subslot 19, FG-client calendar B subslot 0 through FG-client calendar B subslot 19, and CRC-16.CRC-16 is a check on the time slot container overhead.

Fig. 19a is a schematic diagram one of FG-client calendar A based on scenario 3, showing an overhead OAM (Orbital Angular Momentum ) indication of 1 st in the first 5G Slot in the Slot container, according to an embodiment of the present application.

Fig. 19b is a schematic diagram two of FG-client calendar A based on scenario 3, showing the 2 nd to 6 th overhead indications in the first 5G Slot in the Slot container, according to an embodiment of the present application.

Fig. 19c is a schematic diagram two of FG-client calendar A based on scenario 3, showing the 1 st overhead OAM indication in the second 5G Slot in the Slot container according to an embodiment of the present application.

Fig. 19d is a schematic diagram two of FG-client calendar A based on scenario 3, showing the 2 nd to 6 th overhead indications in the second 5G Slot in the Slot container, according to an embodiment of the present application.

In the above scenarios of FIGS. 19a, 19B, 19C, and 19d, FG-client A has a bandwidth of GE, FG-client B has a bandwidth of 1.25GE, and FG-client C has a bandwidth of 6GE.

The bandwidth of FG-client A is GE, 4 sub-slots of 250M are allocated, and the sub slot0-sub slot 3 of the first 5G slot; FG-client A is identified as 0x0A.

FG-client B has a bandwidth of 1.25GE, allocates 5 sub-slots of 250M, and subslot 4-subslot 8 in the first 5G slot; FG-client B is identified as 0x0B.

The bandwidth of FG-client C is 6GE, 24 sub-slots of 250M are allocated, subslot 9-subslot 12 in the first 5G slot, and subslot0-subslot19 in the second 5G slot; FG-client C is identified as 0x0C.

The flexible granular customer service coding mode is converted from 8/10b to 64/66b.

Fig. 20 is a service mapping relationship diagram based on scenario 3 according to an embodiment of the present application. As shown in fig. 20, flexible granular customer services a, B and C are interleaved into the data payloads of the slot containers, i.e., 13094 x 20 66B data blocks.

Scene 4

On the basis of scenario 3, the bandwidth of FG-client C is increased from 6Gb/s to 7Gb/s, requiring the sub-slots allocated to FG-client C from the slot container to be adjusted from 24 to 26. The switching of the Calendar configuration is thus performed for the flexible granular customer services a, B and C, including the synchronous switching of FlexE Calendar a and FG-client Calendar A to FlexE Calendar B and FG-client Calendar B.

The sub-slots are specifically allocated as follows:

the bandwidth and sub-slot allocation of FG-client A is consistent with the original; the bandwidth is GE, 4 sub-slots of 250M are allocated, and the sub slot 0-sub slot 3 of the first 5G slot; FG-client A is identified as 0x0A.

The bandwidth and sub-slot allocation of FG-client B is consistent with the original; the bandwidth is 1.25GE, 5 sub-slots of 250M are allocated, and the sub slot 4-sub slot 8 of the first 5G slot; FG-client B is identified as 0x0B.

The bandwidth of FG-client C is 7GE, 26 sub-slots of 250M are allocated, subslot 9-subslot 14 in the first 5G slot, and subslot 0-subslot 19 in the second 5G slot; FG-client C is identified as 0x0C.

The switching process is as shown in fig. 11 in the above embodiment. Fig. 21a is a schematic diagram of FG-client calendar B based on scenario 4, showing the 1 st overhead OAM indication in the first 5G Slot in the Slot container according to an embodiment of the present application.

Fig. 21b is a schematic diagram of FG-client calendar B based on scenario 4, showing the 2 nd to 6 th overhead indications in the first 5G Slot in the Slot container, according to an embodiment of the present application.

Fig. 21c is a schematic diagram of FG-client calendar B based on scenario 4, showing the 1 st overhead OAM indication in the second 5G Slot in the Slot container according to an embodiment of the present application.

Fig. 21d is a schematic diagram of FG-client calendar B based on scenario 4, showing the 2 nd to 6 th overhead indications in the second 5G Slot in the Slot container, according to an embodiment of the present application.

As shown in fig. 21a, 21b, 21c, 21d, FG-client calendar B after switching is described.

Fig. 22 is a customer service mapping relationship diagram based on scenario 4 according to an embodiment of the present application. As shown in fig. 22, after the handoff is completed, the flexible granular customer traffic is mapped to the new sub-slot.

The specific switching process may refer to scenario 2, and will not be described herein in detail.

Scene 5

A certain FlexE-enabled node, flexE group, contains a 100G PHY. The 100G PHY is divided into 20 slots, each slot being 5G granularity. There is now a flexible granular customer service FG-client A bandwidth of Gb/s, FG-client B bandwidth of 2Gb/s, FG-client C bandwidth of 2Gb/s. Fig. 23 is a slot structure diagram based on scenario 5 according to an embodiment of the present application. As shown in fig. 23, according to the customer service situation, this embodiment configures 1 slot container 1, which contains the first 5G slot of the 100G PHY for carrying these flexible granular customer services. The slot container divides the sub-slots according to the basic granularity of GE, as shown in fig. 23:

1) Based on the current FlexE multiframe structure, in a multiframe period, each 5G slot is 1023×8×32= 261888 blocks with 66b size, 8 blocks are used as slot container overhead, the remaining 261880 blocks are equally divided into 5 sub-slots, each sub-slot has 52376 blocks, that is 52376×5+8=1023×8×32, and each sub-slot has a size GE.

Fig. 24 is a schematic diagram of division of sub-slots based on scene 5 according to an embodiment of the present application. As shown in fig. 24, fig. 24 reflects the mapping process of flexible granular client service initialization.

Fig. 25 is a schematic diagram of overhead arrangement of a scenario 5-based slot container according to an embodiment of the present application. As shown in fig. 25, there are 8 blocks in the slot container as slot container overhead. The 8 blocks are allocated as follows:

the 1 st block overhead is an OAM block.

The overhead of the 2,3 rd blocks is FG-client calendar A/B and CRC-16.

The 4 th to 8 th blocks overhead is used as idle blocks.

Fig. 26 is a schematic diagram of an OAM block based on scenario 5 according to an embodiment of the present application. As shown in fig. 26, the OAM overhead of the 1 st block adopts OAM specification defined in chinese mobile enterprise standard "general technical requirement of chinese mobile slice packet network (SPN 103661)".

Value1 as a pointer, represents the position of 52376 x 5 66b data blocks (data payloads); at the present scene pointer value of 0x08, it is shown that the data payload starts from block 8

The first bit in Value2 is the C bit;

value3, value4 as reserved field;

the overhead of the 2 nd blocks represents the slot containers FG-client calendar A subslot 0 through FG-client calendar A subslot4, and also the C bit bits;

fig. 27 is an overhead schematic diagram based on scenario 5 according to an embodiment of the present application. As shown in FIG. 27, the overhead of the 3 rd blocks represents the slot containers FG-client calendar B subslot to FG-client calendar B subslot, as well as the C bit bits, CR, CA and CRC-16. The C bit bits, CR and CA, are switched for the next embodiment. CRC-16 is a check on the time slot container overhead.

Fig. 28 is a schematic diagram of a scene 5 based FG-client calendar A in accordance with an embodiment of the present application. As shown in FIG. 28, FG-client calendar A is labeled 0x0A, FG-client calendar B is labeled 0x0B, FG-client calendar C is labeled 0x0C, and in this scenario FG-client A has a bandwidth of GE, FG-client B has a bandwidth of 2GE, and FG-client C has a bandwidth of 2GE.

The bandwidth of FG-client A is GE, 1 GE sub-slot is allocated, subslot 0 in the first 5G slot; FG-client A is identified as 0x0A.

The bandwidth of FG-client B is 2GE, 2GE sub-slots are allocated, and the sub slot 1-sub slot 2 of the first 5G slot; FG-client B is identified as 0x0B.

The bandwidth of FG-client C is 2GE, 2GE sub-slots are allocated, and the sub slot 3-sub slot 4 of the first 5G slot; FG-client C is identified as 0x0C.

Fig. 29 is a service mapping relationship diagram based on scenario 5 according to an embodiment of the present application. Flexible granular customer services a, B and C are interleaved into the data payloads of the slot containers, i.e., 52376 x 5 66B data blocks.

Scene 6

On the basis of scenario 5, the bandwidth of FG-client B is increased from 2Gb/s to 3Gb/s, requiring an adjustment from 2 to 3 of the sub-slots allocated to FG-client B from the slot container. Reducing the bandwidth of FG-client C from 2Gb/s to 1Gb/s requires adjusting the sub-slots allocated to FG-client C from 2 to 1 from the slot container. Thus for flexible granular customer services a, B and C, the canendar configured switch is only required to switch FG-client Calendar A to FG-client Calendar B in the slot container. The method comprises the following steps:

FIG. 30a is a schematic diagram one of a scene 6 based FG-client calendar A according to an embodiment of the present application, and FIG. 30b is a schematic diagram two of a scene 6 based FG-client calendar A according to an embodiment of the present application, FG-client calendar A identified as 0x0A, FG-client calendar B identified as 0x0B, FG-client calendar C identified as 0x0C. Initially, the slot container takes FG-client calendar A, CR, CA and 3C-bit values of 0.

Fig. 31 is a schematic diagram of initiating a CR within a slot container based on scenario 6, according to an embodiment of the present application. As shown in fig. 31, FG-client calendar A is marked with 0x0a, FG-client calendar B is marked with 0x0b, FG-client calendar C is marked with 0x0C, the home node wants to switch from FG-client calendar A to FG-client calendar B in the timeslot container, sets cr=1 in the 3 rd overhead of the timeslot container, and sends it to the opposite end.

Fig. 32 is a schematic diagram of a scenario 6-based CA received within a slot container according to an embodiment of the present application. As shown in FIG. 32, FG-client calendar A is marked with 0x0A, FG-client calendar B is marked with 0x0B, FG-client calendar C is marked with 0x0C, and if the opposite end considers that the switching to FG-client calendar A can be performed, CA=1 is set in the 3 rd overhead of the time slot container, and the message is replied.

After the home node receives the message of the CA,

fig. 33a is a schematic diagram one of a C-bit transmission based on scene 6 according to an embodiment of the present application. Fig. 33b is a schematic diagram two of a C-bit transmission based on scenario 6, FG-client calendar A identified as 0x0a, FG-client calendar B identified as 0x0b, FG-client calendar C identified as 0x0C, and the message is replied by setting C-bit=1 in the

slot container

1,2 and 3 overheads, as shown in fig. 33a, 33b, according to an embodiment of the present application.

Fig. 34 is a schematic diagram of a switch to FG-client calendar B in a slotted container based on scenario 6, according to an embodiment of the present application. As shown in FIG. 34, FG-client calendar A is identified as 0x0A, FG-client calendar B is identified as 0x0B, FG-client calendar C is identified as 0x0C, and a switch is formally made to FG-client calendar B in the next FlexE message frame, and a representation of FG-client calendar B in the slot container.

Fig. 35 is a service mapping relationship diagram based on scene 6 according to an embodiment of the present application. As shown in fig. 35, after the handover is completed, the flexible granular customer traffic is mapped to the new sub-slot.

The correspondent node receives the C bit=1 message,

as shown in fig. 34, the handoff FG-client calendar B is then formally performed in the next Flexe message frame, and the representation of FG-client calendar B is in the slot container.

As shown in fig. 35, after the handover is completed, the flexible granular customer traffic is mapped to the new sub-slot.

Scene 7

On the basis of scene 5, a processing mechanism of time slot container multiframe is added. The method comprises the following steps:

this embodiment configures 1 slot container 1, which contains the first 5G slot of the 100G PHY for carrying customer traffic for these flexible particles.

The slot container divides the sub-slots according to the basic granularity of GE.

The overhead and data payload are divided by a plurality of FlexE-frame structures, in this embodiment 5 FlexE-frames, i.e. one slot container frame = 5 FlexE-frames, each slot container frame = 1 FlexE-frame.

In a period of FlexE multiframe, each 5G slot is 1023×8×32= 261888 blocks with 66b size, 8 blocks are used as slot container overhead, the remaining 261880 blocks are equally divided into 5 sub-slots, and each sub-slot has 52376 blocks, i.e. 52376×5+8=1023×8×32.

In a period of 5 FlexE subframes, the overhead number is 8*5 66b blocks, the data payload size is 261880 x 5 66b blocks, and each sub-slot has 52376 x 5 blocks.

Fig. 36 is an overhead schematic of a scenario 7-based slot container multiframe according to an embodiment of the present application. As shown in fig. 36, the first 8 blocks in each frame in the timeslot container multiframe are overhead, the first block in the overhead is OAM, and the OAM overhead adopts OAM specifications defined in the chinese mobile enterprise standard "general technical requirement of the chinese mobile slice packet network (SPN 103661)".

For type definition in OAM, extension defines a new type=0x16, representing a slot container carrying flexible granular customer traffic, and sub-slot division is performed.

Value1 is used as a pointer to indicate the position of the 5 66b data blocks (data payloads) currently in the frame of the timeslot container 52376 x; in this embodiment the pointer value is 0x08, indicating that the data payload starts from block 8.

The upper 4 bits of Value3 represent the number of slot container frames and the lower 4 bits represent the number of the current frame.

Fig. 37 is a schematic diagram of a slot container multiframe number and number based on scenario 7 according to an embodiment of the present application. As shown in fig. 37, the number of time slot container frames (CMA) Container Multiframe Amount =5, and the number of container frames (CMN) Container Multiframe Number will be 0,1,2,3,4, which indicates the number of the current frame in the frames.

The flexible granular customer service is encoded and mapped in a manner similar to scenario 5 and will not be described in detail herein.

From the description of the above embodiments, it will be clear to a person skilled in the art that the method according to the above embodiments may be implemented by means of software plus the necessary general hardware platform, but of course also by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (such as ROM/RAM, magnetic disk, optical disk), comprising several instructions for causing a terminal device (which may be a mobile phone, a computer, a server, or a network device, etc.) to perform the method described in the embodiments of the present application.

Example 2

The embodiment also provides a configuration device of the timeslot container, which is used for implementing the foregoing embodiments and preferred embodiments, and is not described in detail. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. While the means described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and contemplated.

Fig. 38 is a block diagram of a configuration apparatus of a slot container according to an embodiment of the present application, as shown in fig. 38, including:

a building module 3802, configured to build a timeslot container according to a customer service;

a dividing module 3804, configured to divide the time slot container into sub-time slots;

a mapping module 3806, configured to map the client service into one or a group of divided sub-slots.

It should be noted that each of the above modules may be implemented by software or hardware, and for the latter, it may be implemented by, but not limited to: the modules are all located in the same processor; alternatively, the above modules may be located in different processors in any combination.

Example 3

Embodiments of the present application also provide a storage medium having a computer program stored therein, wherein the computer program is arranged to perform the steps of any of the method embodiments described above when run.

Alternatively, in the present embodiment, the above-described storage medium may be configured to store a computer program for performing the steps of:

s1, establishing a time slot container according to customer service;

s2, sub-slot division is carried out on the time slot container;

and S3, mapping the client service into one or a group of divided sub-slots.

Alternatively, in the present embodiment, the storage medium may include, but is not limited to: a usb disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing a computer program.

Embodiments of the present application also provide an electronic device comprising a memory having a computer program stored therein and a processor arranged to run the computer program to perform the steps of any of the method embodiments described above.

Optionally, the electronic apparatus may further include a transmission device and an input/output device, where the transmission device is connected to the processor, and the input/output device is connected to the processor.

Alternatively, in the present embodiment, the above-described processor may be configured to execute the following steps by a computer program:

s1, establishing a time slot container according to customer service;

s2, sub-slot division is carried out on the time slot container;

and S3, mapping the client service into one or a group of divided sub-slots.

Alternatively, specific examples in this embodiment may refer to examples described in the foregoing embodiments and optional implementations, and this embodiment is not described herein.

It will be appreciated by those skilled in the art that the modules or steps of the application described above may be implemented in a general purpose computing device, they may be centralized on a single computing device, or distributed across a network of computing devices, or they may alternatively be implemented in program code executable by computing devices, such that they may be stored in a memory device for execution by the computing devices and, in some cases, the steps shown or described may be performed in a different order than what is shown or described, or they may be implemented as individual integrated circuit modules, or as individual integrated circuit modules. Thus, the present application is not limited to any specific combination of hardware and software.

The foregoing description is only of the preferred embodiments of the present application and is not intended to limit the same, but rather, various modifications and variations may be made by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application should be included in the protection scope of the present application.

Claims

1. A method for configuring a timeslot container, comprising:

establishing a time slot container according to customer service;

sub-slot partitioning is performed on the slot container, including: dividing the sub-slots according to basic particles in the data payload part of each time slot container, wherein when the time slot containers are divided into sub-slots, a specified number of data blocks are reserved in the time slot containers as overhead blocks of the time slot containers, and the overhead blocks carry indication information for indicating the mapping relationship between the client service and the divided sub-slots;

mapping the customer service into one or a group of divided sub-slots, including: and mapping the client service to one or a group of data payloads corresponding to the divided sub-slots according to the indication information.

2. The method according to claim 1, wherein the slot container is located between the customer service and a flexible ethernet FlexE calendar.

3. The method of claim 1, wherein prior to sub-slot partitioning the slot container, the method comprises:

allocating a preset number of FlexE slots of 5G granules to each slot container;

wherein a predetermined number of FlexE slots of the 5G granule are located in one FlexE group, provided by the same or different physical layer PHYs.

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

and switching the client service in the time slot container according to the FlexE overhead field and/or the overhead block.

5. The method according to any of claims 1 to 4, wherein the starting position of the customer service is determined by means of at least one of:

multiframe of FlexE; overhead in the slot container.

6. A time slot container configuration apparatus, comprising:

the establishing module is used for establishing a time slot container according to the customer service;

the division module is configured to divide the time slot container into sub-time slots, and includes: dividing the sub-slots according to basic particles in the data payload part of each time slot container, wherein when the time slot containers are divided into sub-slots, a specified number of data blocks are reserved in the time slot containers as overhead blocks of the time slot containers, and the overhead blocks carry indication information for indicating the mapping relationship between the client service and the divided sub-slots;

A mapping module, configured to map the client service to one or a group of divided sub-slots, including: and mapping the client service to one or a group of data payloads corresponding to the divided sub-slots according to the indication information.

7. A storage medium having a computer program stored therein, wherein the computer program is arranged to perform the method of any of claims 1 to 5 when run.

8. An electronic device comprising a memory and a processor, characterized in that the memory has stored therein a computer program, the processor being arranged to run the computer program to perform the method of any of the claims 1 to 5.