CN111586752A

CN111586752A - Method and device for configuring time slot container

Info

Publication number: CN111586752A
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: 2020-08-25
Anticipated expiration: 2039-02-18
Also published as: CN111586752B; WO2020169009A1

Abstract

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

Description

Method and device for configuring time slot container

Technical Field

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

Background

Flexible Ethernet (FlexE-Flexible Ethernet) technology was developed by the international organization for standardization OIF at 3 months 2015 and formally documented through related technologies at 3 months 2016. The flexible ethernet technology provides a general mechanism to transmit a series of services with different Media Access Control (MAC) rates, which may be a service with a relatively high MAC rate or a collection of services with relatively low MAC rates, and is not limited to a service with a single MAC rate.

The client service supported by the current FlexE standard is of granularity N × 5G, and the client service carrying the granules smaller than 5G is inefficient and wastes a lot. Although some methods for supporting the small-granule client service are proposed in the industry, the methods are improved on the time slot of the FlexE original 5G granule, and the disadvantages are that the flexibility is low, it is difficult to support the mixed transmission of the small-granule client services with different granularities in one 5G time slot, and it is difficult to realize that the same small-granule client service is distributed and carried on different PHYs.

Disclosure of Invention

The embodiment of the application provides a method and a device for configuring a time slot container, so as to at least solve the problem that the flexibility of a small-particle client service is low in a 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 the customer service; performing sub-slot division on the slot container; and mapping the client service to one or a group of divided sub-time slots.

Optionally, the time slot container is located between the customer service and the FlexE calendar.

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

Optionally, the sub-slot dividing the slot container includes: and dividing the sub-time slots according to the basic particles in the data payload part in each time slot container.

Optionally, when performing sub-slot division on the slot container, the method further includes: 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 customer service and the divided sub-time slots.

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

Optionally, the method further comprises: and switching the client service in the time slot container according to a 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: multiframe of FlexE, overhead in the slot container.

According to an embodiment of the present application, there is provided a time slot container configuration apparatus, including an establishing module, configured to establish a time slot container according to a client service; the dividing 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 to one or a group of divided sub-time slots.

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

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

According to the method and the device, the sub-time slot is divided by using the time slot container corresponding to the client service, and the client service is mapped to the divided sub-time slot. Therefore, the problem that the flexibility of the small-particle customer service is low in the transmission process can be solved, and the flexible particle customer service is transmitted in a rigid pipeline in a mixed mode.

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 embodiment(s) of the application and together with the description serve to explain the application and not to limit the application. In the drawings:

fig. 1 is a flowchart of a method for configuring a timeslot container according to an embodiment of the present application;

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

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

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

fig. 5 is a schematic diagram of a value of a calendar based on a scene 1 according to an embodiment of the present application;

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

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

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

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;

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

fig. 11 is a schematic diagram of a caption switching based on scene 2 according to an embodiment of the present application;

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

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

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

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

fig. 16 is a schematic diagram of an overhead arrangement of a slot container based on scenario 3 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 an overhead based on scenario 3 according to an embodiment of the present application;

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

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

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

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

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

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

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

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

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

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

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

fig. 24 is a schematic diagram of sub-slot division based on scenario 5 according to an embodiment of the present application;

fig. 25 is a diagram illustrating an overhead arrangement of a slot container based on scenario 5 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 an overhead based on scenario 5 according to an embodiment of the present application;

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

fig. 29 is a service mapping relationship diagram based on scenario 5 according to an embodiment of the present application;

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

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

fig. 31 is a diagram illustrating a scenario 6-based CR initiation within a timeslot container according to an embodiment of the present application;

fig. 32 is a diagram illustrating receiving CA in a timeslot container according to an embodiment of the present application based on scenario 6;

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

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

FIG. 34 is a diagram illustrating a switch to FG-clientcaldar B in a slot container based on scenario 6 according to an embodiment of the present application;

fig. 35 is a service mapping relationship diagram based on scenario 6 according to an embodiment of the present application;

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

fig. 37 is a diagram illustrating the number and numbering of the timeslot container multiframes based on scenario 7 according to an embodiment of the present application;

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

Detailed Description

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

It should be noted that the terms "first," "second," and the like in the description and claims of this application and in the drawings described above are used for distinguishing between similar elements 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, and fig. 1 is a flowchart of a method for configuring a timeslot container according to an embodiment of the present application, where as shown in fig. 1, the flowchart includes the following steps:

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

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

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

5G in this document denotes bandwidth.

Specifically, fig. 2 is a hierarchical diagram of a timeslot container according to an embodiment of the present application, and as shown in fig. 2, a Slot container in fig. 2 is the timeslot container described in this implementation. The time slot container is located between the FG-client service (i.e., client service) and a flexible ethernet calendar FlexE calendar, where Sub calendar is a Sub-calendar and N × 5G FlexE client is an N × 5G flexible ethernet client.

It should be noted that, in the present embodiment, it is actually necessary to allocate a timeslot container for each customer service, considering that there may be a plurality of customer services. The number of slot containers can be multiple.

Optionally, before sub-slot dividing the slot container, the method includes: allocating a preset number of FlexE time slots of 5G particles to each time slot container; wherein the FlexE time slots of the preset number of 5G grains are located in one FlexE group and are provided by the same or different Physical layers (PHY).

In particular, different preset numbers of FlexE slots of 5G grains can be allocated for different slot containers. For example, slot container 1 is allocated i × 5G slots, slot container 2 is allocated j × 5G slots, and slot container 3 is allocated k × 5G slots. Meanwhile, the specific position of the FlexE time slot allocated by the time slot container can be determined by at least one of the following modes: indicated by the client calendar a and/or client calendar B fields of the FlexE overhead, or, an identifier of the opening in the slot container.

Specifically, the sub-slots are divided according to a certain basic particle in each slot container, and the basic particles in different slot containers may be the same or different. For example, for the timeslot container 1 to which i × 5G timeslots are allocated, if the partition is performed with 250M as the basic granule, the total number of subslots in the timeslot container is i × 20. For another example, if the time slot container 2 to which j × 5G time slots are allocated is divided by using 500M as the basic granule, the total number of sub-time slots in the time slot container is i × 10. For another example, for the timeslot container 3 allocated with k × 5G timeslots, if the timeslot container is divided by 1G as the basic granule, the total number of subslots in the timeslot container is i × 5. Therefore, in the present embodiment, the basic granule has a multiple relationship with 5G slots. The specific multiple relationship is determined according to a preset rule or the requirement of the customer service, for example, and will not be described herein in detail.

Fig. 3 is a block diagram of a timeslot 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, i.e. the Data payload includes the divided sub-slots, the Overhead, the Data payload, and the sub-slot group. And the other part is an opening block. The effect of the overhead block is firstly to satisfy the overhead of the slot container. Secondly, the overhead block carries at least one of the following overheads: FG-client calendar, location pointer and free idle block. If FG-clientcalander is carried in the overhead, the overhead block can also be used to indicate the mapping position of the sub-slot after the client service is divided in the slot container.

Specifically, the FlexE overhead field includes, but is not limited to, a client Calendar a/b, a Calendar Switch Request CR (call Switch Request, abbreviated as CR), a Calendar Switch acknowledgement CA (call Switch acknowledgement, abbreviated as CA), and a Calendar configuration in-use C bit (call configuration input, abbreviated as C). Meanwhile, the overhead resource can also indicate the mapping position of the client service after switching.

In order to better understand the technical solutions described in the above embodiments, in this embodiment, the following scenarios are also provided for understanding:

scene 1:

for a node supporting Flexe, the Flexe group contains only one 100G PHY. The 100G PHY is divided into 20 slots, each slot being of granularity of 5G. The bandwidth of the current small-particle client service A (FG-client A for short) is 250Mb/s, the bandwidth of FG-client B is 500Mb/s, and the bandwidth of FG-client C is 1 Gb/s. According to the situation of the small-granule client service, the embodiment configures a time slot container 1, which contains the first 5G time slot of 100G PHY for carrying the small-granule client service.

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

1) based on the current FlexE multiframe structure, each slot is 1023 × 8 × 32-261888 blocks of size 66b, 8 of which are used as the slot container overhead, the remaining 261880 blocks are divided equally into 20 sub-slots, each of which has 13094 blocks, i.e., 13094 + 20+ 8-1023 × 8 × 32, each of which has a size of 250M.

2) Since only 8 blocks 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% (30PPM) of the nominal rate, within the allowable range.

3) Fig. 5 is a schematic diagram of a value of a calendar based on scene 1 according to an embodiment of the present application. As shown in fig. 5, the first 5G slot (slot 0) of 100G allocated by the slot container 1 is indicated by a client calendar a/client calendar B of FlexE overhead for carrying small-particle client traffic. In the OIF FlexE IA 2.0 standard, a client calendar a/a client calendar B is a value of 16 bits, in this scenario, the first 3 bits ═ 111 of the client calendar allocate 0/client calendar B slot0 is defined to indicate that the slot is allocated to a slot container carrying flexible particle client traffic, and the other values of the first 3 bits ═ represent that the slot is allocated to client traffic of normal N5G particles. In this scenario, if the identifier of the timeslot container 1 is 0xE001, then the value of client Calendar a/client Calendar B of the slot0 indicated in the corresponding FlexE Calendar is equal to 0xE001, which indicates that the timeslot belongs to the timeslot container 1. The Client carrier capacity slot0 ═ 0xE001, and the Client carrier capacity B slot0 ═ 0xE001, indicating that this 5G slot is allocated to carry flexible particle customer traffic.

The mapping process for the initialization of the small-grain client service,

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

FG-client calendar overhead: the FG-client id carried by the sub-slot is represented by 1 BYTE, the FG-client calendar a of 20 sub-slots uses 20 BYTEs, the FG-client calendar B of 20 sub-slots uses 20 BYTEs, and a total of 40 BYTEs are used. Fig. 7 is a schematic diagram of an FG-clientalens based on scene 1 according to an embodiment of the present application. As shown in FIG. 7, the choice of FG-client calendar A/B is consistent with the choice of client calendar A/B indicated in the FlexeCalendar to which it belongs.

In this scenario, fig. 8 is a schematic diagram of FG-client calendar a based on scenario 1 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 0x 0C.

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

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

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

Scene 2:

on the basis of the scenario 1, the bandwidth of FG-client C is reduced from 1Gb/s to 750Mb/s, and the sub-slots needing to be allocated to FG-client C from the slot container are changed from 4 to 3. Fig. 11 is a schematic diagram of a caption switching based on scene 2 according to an embodiment of the present application. As shown in fig. 11, therefore, the switching of the calenar configuration is performed for the small-grained client services a, B and C, including the synchronous switching of the FlexE Calendar a and the FG-client Calendar a to the FlexE Calendar B and the FG-client Calendar B. Fig. 12 is a schematic diagram of FG-clientalens B based on scene 2 according to an embodiment of the present application. As shown in fig. 12, describing the sub-slot configuration indication of the FG-client calendar B after switching, the flag of FG-client calendar a is 0x0A, the flag of FG-client calendar B is 0x0B, and the flag of FG-client calendar C is 0x 0C.

The home node initiates a message of the CR in the FlexE overhead, and switches from the client calendar a to the client calendar B of this PHY. The client calendar B is a value of 16 bits, and in this embodiment, 3 bits before the custom client calendar B slot0 is 111, which indicates that the time slot is allocated to a time slot container for carrying the flexible particle client service, and the specific value may refer to fig. 5 in the scenario 1.

After the opposite end node receives the message of the CR, the time slot of the client calendar B slot0 is known to be allocated to a time slot container from the client calendar B field of the Flexe overhead;

and reading the time slot container overhead in the time slot container, and knowing that after switching to FG-client calendar B, 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.

And the opposite end node judges that the switching can be carried out.

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

After the home node receives the message of the CA,

replying to a message with C bit 1,

and then formally switching to the client calendar B in the next Flexe message frame, and synchronously switching to the FG-client calendar B in the time slot container.

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

The correspondent node receives a message with C bit 1,

The flexible granular client traffic is mapped to the new subslot according to the overhead indication of the timeslot container.

Scene 3:

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

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

1) Based on the current FlexE multiframe structure, in one multiframe period, each 5G slot is 1023 × 8 × 32 blocks of size 261888 b, 8 of which are used as the slot container overhead, the remaining 261880 blocks are divided into 20 subslots, each of which has 13094 blocks, i.e., 13094 × 20+8 × 1023 8 × 32, and each of which 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 for flexible granular customer service initialization:

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

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

The overhead of the 7 th, 8 blocks is taken as a free 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 OAM specifications defined by China Mobile Enterprise Standard 'China Mobile slicing packet network (SPN103661) Total technical requirement'.

For the type definition, a new type of 0x16 is defined by extension, which represents a slot container carrying flexible granular customer service, and sub-slot division is performed.

Value1 as a pointer, indicating the location of 13094 x 20 data blocks (data payloads); at this scene pointer value of 0x08, the data payload begins at block 8.

Value2, Value3, and Value4 indicate slot containers FG-client calendar a subslot0, FG-client calendar a subslot1, and FG-client calendar a subslot 2.

Fig. 18 is a schematic diagram of an overhead based on scenario 3 according to an embodiment of the present application. As shown in FIG. 18, the overhead of the overhead arrangement of the slot containers from the 2 nd to the 6 th blocks represents the slot containers FG-client calendar Asubslot 3 to FG-client calendar A subslot19, and also FG-client calendar B subslot0 to FG-client calendar B subslot19 and CRC-16. CRC-16 checks the slot container overhead.

Fig. 19a is a first schematic diagram of an FG-client calendar a based on scenario 3 according to the embodiment of the present application, which shows a 1 st indication of an overhead OAM (Orbital angular momentum) in the first 5G timeslot in a Slot container.

Fig. 19b is a diagram of a scene 3 based FG-client calendar a according to the embodiment of the present application, which shows 2 nd to 6 th overhead indications in the first 5G Slot of the Slot container.

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

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

In the scenarios of FIG. 19a, FIG. 19b, FIG. 19C, and FIG. 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 6 GE.

The bandwidth of FG-client A is GE, 4 250M subslots are allocated, and subslot0-subslot 3 in the first 5G time slot; FG-client A is identified as 0x 0A.

The bandwidth of FG-client B is 1.25GE, 5 250M subslots are allocated, and the subslot4-subslot 8 in the first 5G time slot; FG-client B is identified as 0x 0B.

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

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

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, the flexible granular client services a, B and C are interleaved into the data payload of the slot container, i.e., 13094 x 20 data blocks of 66B.

Scene 4

On the basis of scenario 3, the bandwidth of FG-client C is increased from 6Gb/s to 7Gb/s, and the sub-slots required to be allocated to FG-client C from the slot container are adjusted from 24 to 26. Therefore, the switching of the Calendar configuration is carried out on the flexible particle client services A, B and C, and comprises 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-time slot allocation of FG-client A are consistent with the original allocation; the bandwidth is GE, 4 250M subslots are allocated, and subslot0-subslot 3 in the first 5G time slot; FG-client A is identified as 0x 0A.

The bandwidth and sub-time slot allocation of FG-client B are consistent with the original allocation; the bandwidth is 1.25GE, 5 250M subslots are allocated, and subslot4-subslot 8 in the first 5G time slot; FG-client B is identified as 0x 0B.

FG-client C has a bandwidth of 7GE, 26 250M subslots are allocated, and the subslot9-subslot 14 in the first 5G slot and the subslot0-subslot19 in the second 5G slot are allocated; FG-client C is identified as 0x 0C.

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

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

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

Fig. 21d is a diagram of a scene 4 based FG-client caption B according to an embodiment of the present application, which shows 2 nd to 6 th overhead indications in the second 5G Slot of the Slot container.

As shown in fig. 21a, 21B, 21c, and 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 handover is completed, the flexible granular client traffic is mapped to the new sub-slot.

The specific switching process may refer to scenario 2, which is not described herein in detail.

Scene 5

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

1) based on the current FlexE multi-frame structure, in one multi-frame period, each 5G slot is 1023 × 8 × 32 blocks of size 261888 b, 8 blocks of which are used as slot container overhead, the remaining 261880 blocks are divided into 5 sub-slots, each sub-slot has 52376 blocks, that is, 52376 × 5+8 × 1023 8 × 32, and each sub-slot has size GE.

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

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

the overhead of the 1 st blocks is an OAM block.

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

The overhead of blocks 4 through 8 is taken 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 cost of the 1 st block adopts OAM specification defined in china mobile enterprise standard "chinese mobile slicing packet network (SPN103661) general technical requirement".

Value1 is used as a pointer to indicate the position of 52376 x 5 data blocks (data payload); in the present scenario, the pointer value is 0x08, indicating that the data payload starts from block8

The first bit in Value2 is the C bit;

value3, Value4 as reserved fields;

the overhead of the 2 nd blocks represents slot containers FG-client calendar A subslot0 to FG-client calendar A subslot4, and C bit;

fig. 27 is a schematic diagram of an overhead 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 subslot0 through FG-client calendar Bsbslot 4, as well as the C bit bits, CR, CA, and CRC-16. The C bit, CR and CA are switched for the next embodiment. CRC-16 checks the slot container overhead.

Fig. 28 is a schematic diagram of FG-client calendar a based on scene 5 according to an embodiment of the present application. As shown in FIG. 28, 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 in this scenario, FG-client A is GE, FG-client B is 2GE, and FG-client C is 2 GE.

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

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

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

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

Scene 6

On the basis of the scenario 5, the bandwidth of FG-client B is increased from 2Gb/s to 3Gb/s, and the sub-slots required to be allocated to FG-client B from the slot container are adjusted from 2 to 3. The bandwidth of the FG-client C is reduced from 2Gb/s to 1Gb/s, and the sub-time slots required to be allocated to the FG-client C from the time slot container are adjusted from 2 to 1. Therefore, for the flexible granular client services A, B and C to switch the Calendar configuration, only FG-client Calendar A needs to be switched to FG-client Calendar B in the time slot container. The method comprises the following specific steps:

fig. 30a is a first schematic diagram of FG-client calendar a based on scene 6 according to the embodiment of the present application, and fig. 30B is a second schematic diagram of FG-client calendar a based on scene 6 according to the embodiment of the present application, where FG-client calendar a is denoted by 0x0A, FG-client calendar B is denoted by 0x0B, and FG-client calendar C is denoted by 0x 0C. At the beginning, the slot container takes the values of FG-client calendar A, CR, CA and 3C bits all as 0.

Fig. 31 is a diagram of initiating a CR in a timeslot container according to an embodiment of the present application based on scenario 6. As shown in fig. 31, FG-client calendar a is denoted by 0x0A, FG-client calendar B is denoted by 0x0B, FG-client calendar C is denoted by 0x0C, and the local node desires to switch from FG-client calendar a to FG-client calendar B of the slot container, sets CR to 1 at the 3 rd overhead of the slot container, and sends it to the opposite node.

Fig. 32 is a diagram illustrating receiving CA in a slot container according to an embodiment of the present application based on scenario 6. As shown in fig. 32, 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 if the peer considers that it can switch to FG-client calendar a, CA is set to 1 at the 3 rd overhead of the slot container, and the message is replied.

After the home node receives the message of the CA,

fig. 33a is a first schematic diagram of C-bit transmission based on scenario 6 according to an embodiment of the present application. Fig. 33B is a diagram illustrating C-bit transmission based on scenario 6 according to the embodiment of the present application, where 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, and as shown in fig. 33a and fig. 33B, C-bit is set to 1 in 1 st, 2 nd, and 3 rd overheads of the slot container, and the message is replied.

Fig. 34 is a diagram illustrating switching to FG-clientcaldar B in a slot container based on scenario 6 according to an embodiment of the present application. As shown in fig. 34, FG-client calendar a is denoted by 0x0A, FG-client calendar B is denoted by 0x0B, FG-client calendar C is denoted by 0x0C, and a switch to FG-client calendar B is formally made in the next FlexE message frame, the representation of FG-client calendar B in the slot container.

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

The correspondent node receives a message with C bit 1,

as shown in fig. 34, FG-client calendar B is then formally switched in the next Flexe message frame, and FG-client calendar B is indicated in the slot container.

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

Scene 7

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

this embodiment configures 1 slot container 1, which contains the first 5G slot of a 100G PHY for carrying these flexible granular client services.

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

In the present embodiment, 5 FlexE multiframes are used, that is, one timeslot container multiframe is 5 FlexE multiframes, and each timeslot container frame is 1 FlexE multiframe.

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

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

Fig. 36 is an overhead diagram of a timeslot container multiframe based on scenario 7 according to an embodiment of the present application. As shown in fig. 36, the first 8 blocks of each frame in the timeslot container multiframe are overheads, the first block of the overheads is OAM, and the OAM overheads adopt OAM specifications defined in china mobile enterprise standard "general technical requirements for china mobile slicing and grouping network (SPN 103661).

For the type definition in OAM, the new type of the extended definition is 0x16, which represents the time slot container carrying the flexible particle customer service, and the sub-time slot division is performed.

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

The upper 4 bits of Value3 indicate the number of slot container multiframes and the lower 4 bits indicate the number of the current multiframe.

Fig. 37 is a diagram illustrating the number and numbering of the timeslot container multiframes based on scenario 7 according to an embodiment of the present application. As shown in fig. 37, the Number of slot Container multiframes (CMA for short) is 5, and the Number of Container multiframes (CMN for short) is 0,1,2,3,4, which represents the Number of the current frame in the Multiframe.

The encoding and mapping manner of the flexible granule client service is similar to that of scenario 5, and will not be described in detail herein.

Through the above description of the embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but the former is a better implementation mode in many cases. Based on such understanding, the technical solutions of the present application may be embodied in the form of a software product, which is stored in a storage medium (e.g., ROM/RAM, magnetic disk, optical disk) and includes instructions for enabling a terminal device (e.g., a mobile phone, a computer, a server, or a network device) to execute the method according to the embodiments of the present application.

Example 2

In this embodiment, a configuration device of a timeslot container is further provided, where the configuration device is used to implement the foregoing embodiments and preferred embodiments, and details of the foregoing description are omitted. As used below, the term "module" may be a combination of software and/or hardware that implements a predetermined function. Although the means described in the embodiments below are preferably implemented in software, an 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 timeslot container according to an embodiment of the present application, and as shown in fig. 38, the apparatus includes:

an establishing module 3802 for establishing a time slot container according to the client service;

a dividing module 3804, configured to perform sub-slot division on the slot container;

a mapping module 3806 for mapping the client traffic into one or a group of divided sub-slots.

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

Example 3

Embodiments of the present application further provide a storage medium having a computer program stored therein, wherein the computer program is configured to perform the steps in any of the above method embodiments when executed.

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

s1, establishing a time slot container according to the client service;

s2, dividing the sub-time slot of the time slot container;

s3, mapping the client service to one or a group of divided sub-slots.

Optionally, in this embodiment, the storage medium may include, but is not limited to: various media capable of storing computer programs, such as a usb disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a removable hard disk, a magnetic disk, or an optical disk.

Embodiments of the present application further provide an electronic device comprising a memory having a computer program stored therein and a processor configured to execute the computer program to perform the steps of any of the above method embodiments.

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

Optionally, in this embodiment, the processor may be configured to execute the following steps by a computer program:

s1, establishing a time slot container according to the client service;

s2, dividing the sub-time slot of the time slot container;

s3, mapping the client service to one or a group of divided sub-slots.

Optionally, the specific examples in this embodiment may refer to the examples described in the above embodiments and optional implementation manners, and this embodiment is not described herein again.

It will be apparent to those skilled in the art that the modules or steps of the present application described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, and in some cases, the steps shown or described may be performed in an order different than that described herein, or they may be separately fabricated into individual integrated circuit modules, or multiple ones of them may be fabricated into a single integrated circuit module. Thus, the present application is not limited to any specific combination of hardware and software.

The above description is only a preferred embodiment of the present application and is not intended to limit the present application, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, improvement and the like made within the principle of the present application shall 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 the customer service;

performing sub-slot division on the slot container;

and mapping the client service to one or a group of divided sub-time slots.

2. The method of claim 1, wherein the timeslot 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 time slots of 5G particles to each time slot container;

wherein the FlexE time slots of the preset number of 5G grains are located in one FlexE group and are provided by the same or different physical layers PHY.

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

and dividing the sub-time slots according to the basic particles in the data payload part in each time slot container.

5. The method of claim 4, wherein in 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 customer service and the divided sub-time slots.

6. The method of claim 5, wherein mapping the customer traffic into one or a group of partitioned sub-slots comprises:

and mapping the client service to the data payload corresponding to one or a group of the divided sub-time slots according to the indication information.

7. The method of claim 5 or 6, further comprising:

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

8. The method according to any of claims 1 to 6, 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.

9. An apparatus for configuring a timeslot container, comprising:

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

the dividing 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 to one or a group of divided sub-time slots.

10. A storage medium, in which a computer program is stored, wherein the computer program is arranged to perform the method of any of claims 1 to 8 when executed.

11. An electronic device comprising a memory and a processor, wherein the memory has stored therein a computer program, and wherein the processor is arranged to execute the computer program to perform the method of any of claims 1 to 8.