CN118677718A

CN118677718A - A data processing method and device

Info

Publication number: CN118677718A
Application number: CN202310293028.8A
Authority: CN
Inventors: 陈井凤; 祁云磊
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2023-03-17
Filing date: 2023-03-17
Publication date: 2024-09-20

Abstract

The embodiment of the application discloses a data processing method which is applied to a first communication device in FlexE ring networks. The method comprises the following steps: receiving a first data stream of a first small particle service through a time slot occupied by a first FlexE client; in response to a failure of the first FlexE group between the first communication device and a second communication device in the FlexE ring network, the first data stream is sent to a third communication device in the FlexE ring network over a time slot occupied by the second FlexE client. The plurality of first sub-slots occupied by the second FlexE client are all active slots. By utilizing the scheme, when the first communication device switches the first data stream to be transmitted to the third communication device through the time slot occupied by the second FlexE client, the small-particle time slot configuration corresponding to the second FlexE client is not required to be perceived, so that the processing overhead is reduced.

Description

Data processing method and device

Technical Field

The present application relates to the field of communications, and in particular, to a data processing method and apparatus.

Background

The flexible Ethernet (Flexible Ethernet, flexE) technology has the advantage of flexible bandwidth allocation according to needs, and can meet network scene requirements of mobile bearing, home broadband, private line access and the like. To reasonably utilize FlexE bandwidth resources, flexE technology can be utilized to carry small particle traffic. The small-grain service can be understood as dividing a slot (slot) corresponding to a large bandwidth in FlexE into a plurality of sub-slots (sub-slots), where the sub-slots obtained by dividing are used for carrying customer service with smaller bandwidth requirements.

When carrying the small-particle service by FlexE technology, in order to ensure the service quality provided for the small-particle service, when the working path for transmitting the small-particle service fails, the small-particle service can be switched to the protection path for forwarding. However, in some scenarios, the processing overhead of the network device is relatively high in the manner of switching the small-particle service to forwarding on the protection path.

Therefore, a solution is urgently needed to solve the above-mentioned problems.

Disclosure of Invention

The embodiment of the application provides a data processing method and a data processing device, which can reduce the processing overhead of network equipment when small-particle business is switched to be forwarded on a protection path.

In a first aspect, an embodiment of the present application provides a data processing method, where the method may be applied to a first communication device in a FlexE ring network. The first communication device may receive a first data stream of a first small particle service via a time slot occupied by a first FlexE client (client). A first FlexE group (group) is provided between the first communication device and a second communication device in the FlexE ring network, the first FlexE group carries a third FlexE client, and a time slot occupied by the third FlexE client is divided into a plurality of second sub-time slots, where the plurality of second sub-time slots are configured to carry the first small particle service, and the plurality of second sub-time slots are all working time slots. In the event that the first FlexE group is not faulty, the first communications device may send the first data stream to a second communications device over a time slot occupied by the third FlexE client. In addition, a second FlexE group is provided between the first communication device and a third communication device in the FlexE ring network, the second FlexE group carries a second FlexE client, a time slot occupied by the second FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used for carrying the first small particle service, the plurality of first sub-time slots are all working time slots, and the first FlexE client and the second FlexE client have a first time slot mapping relationship. In one example, if the first FlexE group fails, the first communication device may send the first data stream to the third communication device through a time slot occupied by the second FlexE client according to a first time slot mapping relationship of the first FlexE client and the second FlexE client. In the embodiment of the present application, both the first sub-slots included in the second FlexE client and the second sub-slots included in the third FlexE client are all in an operating state, but not a part of the sub-slots are in an operating state and a part of the sub-slots are in a protection state. Therefore, when the first communication device switches the first data stream to be transmitted to the third communication device through the time slot occupied by the second FlexE client, the first communication device does not need to perceive the small particle time slot configuration corresponding to the second FlexE client, so that the processing overhead of the first communication device is reduced.

In one possible implementation, the path for transmitting the first data stream may include a working path and a protection path, wherein the first FlexE group may be FlexE group on the working path and the second FlexE group may be FlexE group on the protection path. By using the scheme of the embodiment of the application, when the working path fails, the first data stream can be switched to the protection path for transmission, and when the first data stream is switched to the protection path for transmission, the first communication device does not need to perceive the configuration of the small particle time slot, thereby effectively saving the processing overhead of the communication device.

In one possible implementation, the first communication device may send, in addition to the first data stream to the third communication device through the timeslot occupied by the second FlexE client, path protection switching indication information to the third communication device, where the path protection switching indication information indicates that the third communication device switches from the working path to the protection path. In this way, after the third communication device receives the first data stream and the path protection switching indication information, the third communication device may continue forwarding the first data stream through the protection path, so as to ensure that the first data stream is forwarded to the destination communication device through the protection path.

In one possible implementation manner, the first communication device may send the path protection switching indication information to the third communication device through a time slot occupied by the second FlexE client. In a specific example, the first communication device may send FlexE an operation, administration and maintenance (Operation Administration AND MAINTENANCE, OAM) message to the third communication device through a time slot occupied by the second FlexE client, where the FlexE OAM message includes an automatic protection switching (Automatic Protection Switching, APS) code block, where the APS code block is used to carry the path protection switching indication information.

In one possible implementation, the first communication device may re-switch the small particle traffic to forwarding on the working path after the working path failure has recovered. In a specific example, the first communication device may further receive a second data stream of the first small particle service through a time slot occupied by the first FlexE client, and in a case of failure recovery of the first FlexE group, send the second data stream to the second communication device through a time slot occupied by the third FlexE client based on the second time slot mapping relationship of the first FlexE client and the third FlexE client.

In a possible implementation manner, the first communication device may further receive a third data stream of the second small particle service through a time slot occupied by a fourth FlexE client, a third FlexE group is provided between the first communication device and the third communication device in the FlexE ring network, the third FlexE group carries a sixth FlexE client, and the time slot occupied by the sixth FlexE client is divided into a plurality of fourth sub-time slots, and the plurality of fourth sub-time slots are configured to carry the second small particle service, and the plurality of fourth sub-time slots are all working time slots. In the case that the third FlexE group is fault-free, the first communication device may send the third data stream to a third communication device through a slot occupied by the sixth FlexE client. In addition, a fourth FlexE group is provided between the first communication device and the second communication device, the fourth FlexE group carries a fifth FlexE client, the time slot occupied by the fifth FlexE client is divided into a plurality of third sub-time slots, the plurality of third sub-time slots are used for carrying the second small particle service, and the plurality of third sub-time slots are all working time slots. The fourth FlexE client and fifth FlexE client have a third slot mapping relationship. In one example, if the third FlexE group fails, the first communications device may send the third data stream to the second communications device through a slot occupied by the fifth FlexE client according to a third slot mapping relationship of the fourth FlexE client and fifth FlexE client. In the embodiment of the present application, both the third sub-slots included in the fifth FlexE client and the fourth sub-slots included in the sixth FlexE client are all in the working state, but not part of the sub-slots are in the working state and part of the sub-slots are in the protection state. Therefore, when the first communication device switches the third data stream to be transmitted to the second communication device through the timeslot occupied by the fifth FlexE client, the first communication device does not need to perceive the small particle timeslot configuration corresponding to the fifth FlexE client, so that the processing overhead of the first communication device is reduced.

In one possible implementation, the first small particle service and the second small particle service belong to the same small particle service. For this case, for the first small-particle service, the paths of the corresponding uplink and downlink data flows are symmetrical, so that better service quality can be provided for the small-particle service.

In a second aspect, an embodiment of the present application provides a data processing method, where the method may be applied to a first communication device in a FlexE ring network, where the first communication device may receive, through a time slot occupied by a first FlexE client, a first data stream of a first small-particle service sent by a second communication device; wherein: a first FlexE group is provided between the second communication device and the first communication device, the first FlexE group carries the first FlexE client, the time slot occupied by the first FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used for carrying the first small particle service, and the plurality of first sub-time slots are all working time slots; and transmitting the first data stream through a protection path. In the embodiment of the application, the plurality of first sub-slots are all in the working state, but not part of the sub-slots are in the working state, and part of the sub-slots are in the protection state. Therefore, when the first communication device sends the first data stream through the protection path, the small particle time slot configuration corresponding to the first FlexE client is not required to be perceived, so that the processing overhead of the first communication device is reduced.

In one possible implementation, the method further includes: and receiving path protection switching indication information sent by the second communication device, wherein the path protection switching indication information indicates the first communication device to switch from a working path to the protection path.

In one possible implementation manner, receiving path protection switching indication information sent by the second communication device includes: and receiving FlexE operation, administration and maintenance (OAM) information sent by the second communication device through a time slot occupied by the first FlexE client, wherein an Automatic Protection Switching (APS) code block in the FlexE OAM information is used for bearing the path protection switching indication information.

In one possible implementation manner, the sending the first data stream through a protection path includes: and sending the first data stream through the protection path according to the path protection switching indication information.

In a third aspect, an embodiment of the present application provides a first communication apparatus, including: a transceiver unit and/or a processing unit; the transceiver unit is configured to perform the receiving and/or transmitting operation performed by the first communication device according to the first aspect or the second aspect; the processing unit is configured to perform operations other than the receiving and/or transmitting operations performed by the first communication device as described in the first aspect above or in the second aspect above.

In a specific example, the first communication apparatus may include a receiving unit and a transmitting unit.

As one example:

A receiving unit, configured to receive a first data stream of a first small-granule service through a time slot occupied by a first flexible ethernet client FlexE client; a sending unit, configured to send, in response to a failure of a first FlexE group between a first communication device and a second communication device in the FlexE ring network, the first data stream to a third communication device in the FlexE ring network through a time slot occupied by the second FlexE client based on a first time slot mapping relationship of the first FlexE client and the second FlexE client, where: a second FlexE group is provided between the first communication device and the third communication device, the second FlexE group carries the second FlexE client, the time slot occupied by the second FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used for carrying the first small particle service, and the plurality of first sub-time slots are all working time slots; the first FlexE group is configured to carry a third FlexE client, and a time slot occupied by the third FlexE client is divided into a plurality of second sub-time slots, where the plurality of second sub-time slots are configured to carry the first small particle service, and the plurality of second sub-time slots are all working time slots.

In a possible implementation manner, the sending unit is further configured to: and sending path protection switching indication information to the third communication device, wherein the path protection switching indication information indicates the third communication device to switch from a working path to a protection path.

In a possible implementation manner, the sending unit is specifically configured to: and sending FlexE operation, administration and maintenance OAM message to the third communication device through the timeslot occupied by the second FlexE client, where an automatic protection switching APS code block in the FlexE OAM message is used to carry the path protection switching indication information.

In a possible implementation manner, the receiving unit is further configured to: receiving a second data stream of the first small particle service through a time slot occupied by the first FlexE client; the sending unit is further configured to send, in response to the first FlexE group failure recovery, the second data stream to the second communication device through a slot occupied by the third FlexE client based on a second slot mapping relationship of the first FlexE client and the third FlexE client.

In a possible implementation manner, the receiving unit is further configured to receive a third data stream of the second small-granule service through a time slot occupied by a fourth FlexE client; the sending unit is further configured to send, in response to a third FlexE group failure between the first communication device and a third communication device in the FlexE ring network, the third data stream to a second communication device in the FlexE ring network through a time slot occupied by the fifth FlexE client based on a third time slot mapping relationship of the fourth FlexE client and the fifth FlexE client, where: a fourth FlexE group is provided between the first communication device and the second communication device, the fourth FlexE group carries the fifth FlexE client, the time slot occupied by the fifth FlexE client is divided into a plurality of third sub-time slots, the plurality of third sub-time slots are used for carrying the second small particle service, and the plurality of third sub-time slots are all working time slots; the third FlexE group is configured to carry the sixth FlexE client, and the time slot occupied by the sixth FlexE client is divided into a plurality of fourth sub-time slots, where the plurality of fourth sub-time slots are configured to carry the second small particle service, and the plurality of fourth sub-time slots are all working time slots.

In one possible implementation, the first small particle service and the second small particle service belong to the same small particle service.

In one possible implementation, the first FlexE group is FlexE group on the working path and the second FlexE group is FlexE group on the protection path.

As yet another example:

a receiving unit, configured to receive, through a time slot occupied by the first flexible ethernet client FlexE client, a first data stream of a first small-granule service sent by the second communication device; wherein: a first FlexE group is provided between the second communication device and the first communication device, the first FlexE group carries the first FlexE client, the time slot occupied by the first FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used for carrying the first small particle service, and the plurality of first sub-time slots are all working time slots; and the transmitting unit is used for transmitting the first data stream through a protection path.

In a possible implementation manner, the receiving unit is further configured to: and receiving path protection switching indication information sent by the second communication device, wherein the path protection switching indication information indicates the first communication device to switch from a working path to the protection path.

In a possible implementation manner, the receiving unit is specifically configured to: and receiving FlexE operation, administration and maintenance (OAM) information sent by the second communication device through a time slot occupied by the first FlexE client, wherein an Automatic Protection Switching (APS) code block in the FlexE OAM information is used for bearing the path protection switching indication information.

In a possible implementation manner, the sending unit is specifically configured to: and sending the first data stream through the protection path according to the path protection switching indication information.

In a fourth aspect, an embodiment of the present application provides a communication apparatus, including: a communication interface and a processor, according to which the communication device performs the method of any of the above first aspects or any of the above second aspects.

In a specific design, the communication device may be a chip, the communication interface includes an interface circuit, and the processor includes a processing circuit. The interface circuit may include an input circuit and an output circuit. The processing circuitry is to receive signals through the input circuitry and to transmit signals through the output circuitry such that any one of the first to second aspects, and any implementation of any one of the aspects, is effected.

In a fifth aspect, embodiments of the present application provide a computer readable storage medium comprising instructions or a computer program which, when run on a processor, performs the method of any of the first aspect above, or any of the second aspect above.

In a sixth aspect, embodiments of the present application provide a computer program product comprising a computer program product which, when run on a processor, performs the method of any one of the first aspect and the first aspect above, or performs the method of any one of the second aspect and the second aspect above.

In a seventh aspect, an embodiment of the present application provides a communication system, including: a first communication device performing the method of the first aspect above and any of the first aspects above and a first communication device performing the method of the second aspect above and any of the second aspects above.

In an eighth aspect, embodiments of the present application provide a chip system, which may include a processor. The processor is coupled to the memory and operable to perform any of the above-described first to second aspects, and any implementation of any of the aspects. Optionally, the system on a chip further comprises a memory. Memory for storing a computer program (which may also be referred to as code, or instructions). A processor for invoking and running a computer program from memory to cause a device on which the system-on-chip is installed to perform any of the first to second aspects, and any implementation of any of the aspects.

In a ninth aspect, an embodiment of the present application provides a communication apparatus, including: interface circuitry and processing circuitry. The interface circuit may include an input circuit and an output circuit. The processing circuitry is to receive signals through the input circuitry and to transmit signals through the output circuitry such that any one of the first to second aspects, and any implementation of any one of the aspects, is effected. In one particular implementation, the processing circuitry includes circuitry to implement operations performed by the Flexe shim layers.

In a specific implementation process, the communication device may be a chip, the input circuit may be an input pin, the output circuit may be an output pin, and the processing circuit may be a transistor, a gate circuit, a flip-flop, various logic circuits, and the like. The input signal received by the input circuit may be received and input by, for example and without limitation, a receiver, the output signal may be output by, for example and without limitation, a transmitter and transmitted by a transmitter, and the input circuit and the output circuit may be the same circuit, which functions as the input circuit and the output circuit, respectively, at different times. The application is not limited to the specific implementation of the processor and various circuits.

In yet another implementation, the communication device may be part of a device in the first communication device or the controller, such as an integrated circuit product such as a system chip or a communication chip. The interface circuit may be an input/output interface, interface circuit, output circuit, input circuit, pin or related circuitry, etc. on the chip or system of chips. The processing circuitry may be logic circuitry on the chip.

Drawings

In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings that are required to be used in the embodiments or the description of the prior art will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments described in the present application, and other drawings may be obtained according to the drawings without inventive effort to those skilled in the art.

FIG. 1a is a schematic diagram of an SPN architecture supporting small particle technology according to an embodiment of the present application;

Fig. 1b is a schematic diagram of a network architecture according to an embodiment of the present application;

Fig. 2a is a schematic diagram of an exemplary application scenario provided in an embodiment of the present application;

FIG. 2b is a schematic diagram of another exemplary application scenario provided by an embodiment of the present application;

fig. 3 is a schematic view of an application scenario provided in an embodiment of the present application;

Fig. 4 is a signaling interaction diagram of a data processing method according to an embodiment of the present application;

fig. 5 is a signaling interaction diagram of yet another data processing method according to an embodiment of the present application;

fig. 6 is a signaling interaction diagram of yet another data processing method according to an embodiment of the present application;

FIG. 7 is a schematic flow chart of a data processing method according to an embodiment of the present application;

FIG. 8 is a flowchart of another data processing method according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a first communication device according to an embodiment of the present application;

fig. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 11 is a schematic structural diagram of a communication device according to an embodiment of the present application.

Detailed Description

For ease of understanding, the relevant content of FlexE will be described first.

FlexE group: each FlexE group includes one or more PHYs. When multiple PHYs are included, the multiple PHYs are physically independent. The network device to which FlexE technology is applied may implement logical bundling of multiple PHYs by identifying which PHYs are included in one FlexE group through the numbering of the PHYs. For example, the number of each PHY may be identified by a number between 1 and 254, with 0 and 255 being reserved numbers. The number of one PHY may correspond to one interface on the network device. The same number is used between two adjacent network devices to identify the same PHY. The number of each PHY included in one FlexE group need not be consecutive. Typically, there is one FlexE group between two network devices, but the application is not limited to only one FlexE group between two network devices, i.e., there may be multiple FlexE group between two network devices. One PHY may be used to carry at least one client, and one client may transmit on at least one PHY. FlexE can support mapping and transmission of any number of different FlexE Client on any set of PHYs, thereby implementing functions such as PHY bundling, channelization, and subrate.

FlexE Client various user interfaces or bandwidths corresponding to the network. FlexE Client represents a customer data stream transmitted over a designated time slot (time slot or slots) FlexE Group, one FlexE Group may carry a plurality FlexE Client, and one FlexE Client may correspond to one to a plurality of customer service data streams (also referred to as MAC CLIENT). FlexE client is flexibly configurable according to bandwidth requirements, and supports various rates of ethernet Media Access Control (MAC) data streams (e.g., 10G, 40G, n x 25G data streams, and even non-standard rate data streams), for example, the data streams may be delivered to FlexE shim layers by 64B/66B coding. Clients transmitting through the same FlexE group need to share the same clock and these clients need to adapt according to the assigned slot rate. In the present application, flexE client (also referred to as FlexE client interface) may be used to transmit the corresponding traffic data stream of FlexE client. The FlexE client interface is a logical interface. Each FlexE interface may be logically divided into one or more FlexE client interfaces, each FlexE interface may be time-domain divided into a plurality of time slots, and each FlexE client interface occupies at least one of the plurality of time slots. Wherein: 64/66B means that the data code block includes 66 bits, the first two bits of the 66 bits are sync bits, the last 64 bits are data bits, and at the PCS layer, 64/66B can be extracted by the first two sync bits.

FlexE shim as an additional logical layer interposed between the MAC and PHY (PCS sublayers) of the conventional ethernet architecture, is a core architecture for implementing FlexE technology based on a slot distribution mechanism. For the transmitting end, flexE shim has the main role of encapsulating the data into pre-divided slots (slots). Then, each divided slot is mapped to PHY in FlexE group for transmission according to FlexE slot table. Wherein each slot maps to one PHY in FlexE group. Taking 100GE PHY as an example, flexE Shim layers may divide each 100GE PHY in FlexE Group into 20 slots (slots) of data-carrying channels, each slot corresponding to a bandwidth of 5Gbps. An Overhead FlexE (OH) is inserted every time the PHY transmits 1023 x 20slot 64/66B data, thereby informing the receiving end how to parse the received data.

Small particle traffic: in some embodiments, slots corresponding to a large bandwidth may be further divided into a plurality of sub-slots (sub-slots) for carrying customer traffic with smaller bandwidth requirements, which is also referred to as small-particle traffic. For example, the large bandwidth may be understood as a bandwidth corresponding to a service layer of the small-particle service. For example, when the service layer of the small-particle service is an MTN channel layer, the bandwidth of the MTN channel layer is 5Gbps, slots corresponding to the large bandwidth of 5Gbps are further divided into 480 sub-slots according to the granularity of 10Mbps, and the 480 sub-slots are used for carrying the small-particle service. For example, the 1 st sub-slot, the 3 rd sub-slot, and the 5 th sub-slot of the 480 sub-slots are used to carry the small particle service 1. For another example, when the service layer of the small-particle service is a 10GE ethernet physical layer, the corresponding large bandwidth is further divided into a plurality of sub-slots according to finer granularity, and the sub-slots are used for carrying the small-particle service. It follows that small particle bandwidth granularity is finer, small particle traffic refers to traffic that has relatively less bandwidth requirements. For example, the bandwidth requirement of the dedicated power line service is 10Mbps, and at this time, the dedicated power line service can be allocated with a specified bandwidth by using a small-grain technology, so as to be used for carrying the service traffic of the dedicated power line service, where the dedicated power line service is a small-grain service.

When transmitting the small-granule service, for the transmitting end, flexE shim may package data into the sub-slots divided in advance according to the time slot configuration of the small granule in an example for transmission. For the receiving end, flexE shim can restore the data received through the slot with the corresponding bandwidth of 5Gbps into the original small-granule service data according to the slot configuration of the small-granule and continue to transmit. In yet another example, for a transmitting end, data may be encapsulated into a corresponding sub-slot for transmission by using an MTN channel layer adaptation function (MTN path adaptation function), and for a receiving end, data received through the slot with a corresponding bandwidth of 5Gbps may be recovered into original small-particle service data by using the MTN channel layer adaptation function and transmitted continuously. In one example, the small particle business data may be carried in a small particle unit (fine granularity unit, FGU) base frame. In one example, small particle units, which may also be referred to as small particle base units (fine granularity basic unit, fgBU), are used interchangeably in the following description.

Regarding FlexE OH insertion and the structure of overhead frames, in one specific implementation, reference may be made to the relevant description section of the electrical and optical internet forum (optical internetworking forum, OIF) regarding FlexE, which is not described in detail herein.

One possible architecture for a Slice Packet Network (SPN) that supports small particle technology is described next. Referring to fig. 1a, a schematic diagram of an SPN architecture supporting small particle technology according to an embodiment of the present application is shown.

As shown in fig. 1a, the SPN architecture includes:

Slice packet layer (SLICING PACKET LAYER, SPL), slice lane layer (SLICING CHANNEL LAYER, SCL), slice transport layer (slicing transport layer, STL), control-in-one software defined network (software defined network, SDN) slice control plane and ultra-high precision event frequency synchronization techniques. Wherein:

The SCL includes an FGU layer, an MTN path (MTNP) layer, and an MTN segment (MTNS) layer. Wherein: FGU layer provides end-to-end deterministic low-delay N10 Mbps granularity hard slice channel for small particle service. The FGU layer is an independent sublayer, and can be flexibly carried on an MTN channel layer or an Ethernet physical layer according to requirements, in other words, a service layer of the FGU layer can be the MTN channel layer or the Ethernet physical layer.

The STL adds a 10GE Ethernet physical layer interface based on the original high-speed Ethernet physical layer interface. The 10GE Ethernet physical layer can be applied to customer terminal equipment (CPE) scenes to directly bear the FGU layer.

Next, taking the MTN channel layer as an example to carry small particle service, the MTNS and MTNP will be described from the perspective of the sending side behavior and the receiving side behavior.

The transmit-side behavior and the receive-side behavior of MTNS will be described first.

In one example, taking a 100GBASE-R PHY as an example, MTNS provides point-to-point connections, is responsible for time-slotted processing of adjacent nodes that connect Ethernet PHYs together, and provides binding, subrate, and tunneling functions. MTNS are bi-directionally symmetrical, and are described herein as one direction of data transmission.

On the transmitting side, MTNS inserts a special O code block in the 66B code block sequence, inserts a D code block after 1023×20 66B code blocks, inserts a D code block after every 1023×20 66B code blocks, and needs to insert 7D code blocks in total. After inserting the 7 th D code block, a special O code block is inserted after another 1023 x 20 code blocks are spaced apart. Thus, a total of 8 x (1023 x 20+1) code blocks constitute one MTNS frame (frame).

The O code block plus the 7D code blocks described above constitutes the overhead of MTNS frames. Overhead carries some point-to-point link configuration information, e.g., slot configuration information, packet group configuration information, etc., of the indication MTNS.

MTNS continuously transmit data to the receiving end according to the frame structure. The continuous MTNS frames are equivalent to a 66B code block stream, and are transmitted from the transmitting device as bits, optical signals, or other analog signals such as electrical pulses, according to the lower PHY layer protocol defined by the Institute of Electrical and Electronics Engineers (IEEE) 802.3.

The receiving side first locks the frame header of MTNS frames by identifying the O-code blocks by the received signal (e.g., bits, optical signals, or other analog signals such as electrical pulses) according to the protocol of the ethernet layer PHY (Ethernet lower PHY layer), and knows that the next overhead code block occurs after 1023 x 20 code blocks according to a fixed count. Correspondingly, the receiving side can determine the position of the data corresponding to each time slot in the received signal according to the O code block.

MTNS can only provide point-to-point connections, while the MTNP is responsible for providing "end-to-end channel connections" from network ingress to network egress, providing end-to-end rigid hard pipe connections, providing management maintenance and protection (OAM and protection, OAMP) functions. A typical network related to MTNP may be shown in fig. 1b, and fig. 1b is a schematic diagram of a network architecture according to an embodiment of the present application.

The transmit side behavior and the receive side behavior of the MTNP are described next in connection with fig. 1 b.

As shown in fig. 1b, an end-to-end MTNP is included between Provider Edge (PE) 1 and PE2, and a point-to-point MTNS is included between PE1 and PE 2.

On the network side interface (network to network interface, NNI) side of PE1, the MTNP layer obtains a client signal, which may be a MAC frame, from the MAC layer. The MAC referred to herein may be a processing module of the MAC layer. After the MTNP layer obtains the MAC frame, the MAC frame is encoded into a series of 64/66B code block sequences. Specifically, each MAC frame is encoded into a series of 66B code block sequences defined by a start code block (S code block) and an end code block (i.e., T code block), and a series of MAC frame sequences is encoded into a series of 66B code block sequences.

In one example, if there is no valid MAC frame waiting to be sent, the MTNP will fill the 66B code block with I code blocks, thereby ensuring that the hard pipe of the MTNP has data to send from time to time.

The receiving side of the P node first identifies MTNS frames according to the receiving side behavior of MTNS described above. The MTNP data is then recovered from the assigned MTNS slots according to the pre-configuration. The P node then performs MTNP forwarding. Here, the essential difference between MTNP forwarding and IP forwarding and MAC bridge forwarding is that: MTNP forwards exclusive device forwarding resources without supporting statistical multiplexing, and both the ingress and egress of a network node (e.g., P-node) need to be configured with the same number MTNS of slots.

As described above, in some embodiments, slots corresponding to a large bandwidth may be further divided into a plurality of sub-slots for carrying small particle traffic. For example, slots with the corresponding bandwidth of 5Gbps are further divided according to the granularity of 10Mbps, and 480 sub-slots are divided, and the 480 sub-slots are used for carrying small-particle service. For this case, the MTN FGU may further divide 480 slots of 10Mbps in the MTNP of 5Gbps in a hierarchical manner. In this scenario, the MTNP and MTN FGU may be decoupled, in which case the MTNP acts as a service layer for the MTN FGU. In one example, the fg-BU may include FGU base frame overhead and FGU base frame payload. The FGU base frame overhead may be used to carry timeslot information of small particles, and the FGU base frame payload is used to carry the small particle service data. The time slot information of the small particles can be a mapping relation between sub-slots and sub-clients. Wherein sub-clients are similar to FlexE client and also correspond to various user interfaces or bandwidths of the network. The difference from FlexE client is that: the sub-clients represent client data streams transmitted on sub-slots, and one sub-client may correspond to one or more sub-slots.

For a scenario in which slots with a corresponding bandwidth of 5Gbps are further partitioned at a granularity of 10Mbps, in one example, one FGU base frame may include 24 sub-slots, each sub-slot including 65 bytes, each sub-slot may carry 8 65-bit code blocks. In other words, the aforementioned base frame payload 120 may include 65×24=1560 bytes. The 20 FGU base frames constitute a multiframe in which 24×20=480 sub-slots are provided. In one example, after the fg-BU is 64/66B encoded, 1S 0 code block, 196D code blocks, and 1T code block may be obtained.

For the NNI transmission side of PE1, the MTN FGU layer, like the MTNP, encodes the MAC frame client signal into a 66B code block sequence and then inserts the OAM code block. At this time, inserted into the MTN FGU layer is an OAM code block of a small particle MTNP (fgMTNP) instead of an OAM code block of the MTNP. Then, a series of 66B code block sequences containing fgMTNP OAM code blocks are mapped into 10Mbps slots designated according to the pre-configuration in fg-BU.

The fgBU sequence itself is actually a string of 66B code blocks, which may be equivalently MTNP client signals, after insertion of the MTNP OAM code blocks, are mapped into MTNS assigned slots according to the above-described MTNS transmit side behavior.

The receiving side of the P node recovers the MTNP signal according to the above-described behavior of the receiving side of the MTNP, and then extracts the OAM code block in the MTNP. After the receiving side of the P node recovers the MTNP signal, the framing of fg-BU can be completed by searching for the S code block.

The P node performs fgMTNP forwarding, and fgMTNP forwarding is TDM forwarding, exclusive equipment forwarding resources, and does not support statistical multiplexing, as in MTNP forwarding. The P node does not terminate the OAM code block of fgMTNP.

The sender-side behavior of the P-node is the inverse of the receiver-side behavior of the P-node and will not be described in detail here. In addition, the receiving-side behavior of the PE2 node is the inverse of the transmitting-side behavior of the PE1 node, which is not described in detail herein. Currently, when carrying small-particle service by FlexE technology, in order to ensure the quality of service provided for the small-particle service, when the working path for transmitting the small-particle service fails, the small-particle service can be switched to the protection path for forwarding. Referring to fig. 2a, an exemplary application scenario is schematically shown in the embodiment of the present application.

As shown in fig. 2a, network devices (network equipment, NE) 1, NE2, NE3, NE4, NE5 and NE6 form a FlexE ring network. The FlexE ring network is understood to be a ring network to which FlexE technology is applied. The FlexE technique may also be referred to as FlexE mapping technique, flexE mapping referring to mapping of slots. The time slots mentioned here may be time slots corresponding to large grains or sub-time slots corresponding to small grains.

For each network device, it may be a receiving end (RX) or a transmitting end (TX). When the network device is used as the receiving end, it may receive the data stream corresponding to the small-granule service through the timeslot occupied by FlexE client a, as shown in fig. 2a, and when the network device NE4 is used as the receiving end, the timeslot occupied by FlexE client0 is divided into two parts, respectively W1 and P2, where, as an example, the W1 and P2 each occupy half of the sub-timeslot occupied by FlexE client 0. Wherein W1 is in a working state and P2 is in a protection state. In one specific example, flexE client a occupies a bandwidth of 5G, comprising 480 sub-slots, W1 and P2 each occupying 240 sub-slots. In one example, W1 and P2 may be carried by FlexE group1 between NE4 and NE 5.

Similarly, when the network device is used as the transmitting end, it may send a data stream corresponding to the small-granule service through a time slot occupied by FlexE client0, as shown in fig. 2a, and when the network device NE4 is used as the transmitting end, the time slot occupied by FlexE client0 is divided into two parts, respectively, W2 and P1, and as an example, each of W2 and P1 occupies half of the sub-time slot occupied by FlexE client 0. Wherein W2 is in a working state and P1 is in a protection state. In one specific example, flexE client a occupies a bandwidth of 5G, comprising 480 sub-slots, W2 and P1 each occupying 240 sub-slots. In one example, W2 and P1 may be carried by FlexE group between NE4 and NE 5.

In one example, NE4 may send small particle traffic data to NE2 along the working path when FlexE group provided between the various network devices shown in fig. 2a has not failed. As one example, NE4 may send small particle traffic data to NE2 in a counterclockwise direction, and in particular NE4 may send small particle traffic data to NE2 in a counterclockwise direction over path 201. Where NE4 sends small particle traffic data to NE2 via path 201, the small particle traffic data is carried via W1 between NE4 and NE3 and W1 between NE3 and NE2.

In one example, as shown in fig. 2b, fig. 2b is a schematic view of yet another exemplary application scenario provided in an embodiment of the present application. When FlexE group between NE4 and NE2 fails, NE4 may send the data flow corresponding to the small-particle traffic to NE2 through the protection path. As an example, NE4 may send the data flow for the aforementioned small particle traffic to NE2 in a clockwise direction. Specifically, NE4 transmits the aforementioned data stream, which it receives via W1 between NE5 and NE4, to NE5 via P1 between NE5 and NE4, and NE5 further transmits the data stream to NE2 via P1 between NE5 and NE 6. Where NE5 sends a data flow to NE2 through P1 between NE5 and NE6, the data flow is carried through P1 between NE5 and NE6, P1 between NE6 and NE1, and P1 between NE1 and NE2.

However, since half of the sub-slots occupied by FlexE client a are in the active state and half are in the protection state, when NE4 transmits the data stream to NE5 through P1 between NE5 and NE4, the data stream needs to be mapped according to the local small granule slot configuration of NE4, and similarly, when NE5, NE6 and NE1 forward the data stream, the data stream also needs to be mapped according to the local small granule slot configuration.

The processing overhead of performing slot mapping on the data stream based on the small-granule configuration is relatively high, so in the scenarios shown in fig. 2a and fig. 2b, the processing overhead of the network device is relatively high when the small-granule service is switched to the forwarding mode on the protection path.

In order to solve the problem, the embodiment of the application provides a data processing method and device. Next, a description is given of a data processing method provided by an embodiment of the present application with reference to the accompanying drawings.

Referring to fig. 3, the diagram is a schematic view of an application scenario provided in an embodiment of the present application. The data processing method provided by the embodiment of the application can be applied to the application scene shown in fig. 3.

As shown in FIG. 3, NE1, NE2, NE3, NE4, NE5, and NE6 form a FlexE ring network.

Each network device may function as an RX or as a transmitting end TX. When the network device is used as the receiving end, it can receive the data stream corresponding to the small-granule service through the time slot occupied by FlexE client, as shown in fig. 3, taking the network device NE4 as an example, when it is used as the receiving end, the time slots W1 occupied by FlexE client are all in working states. In other words, the time slot occupied by FlexE client0 is divided into a plurality of sub-slots, which are all working time slots. In a specific example, flexE client a occupies 5G bandwidth, including 480 sub-slots in total, and W1 occupies 480 sub-slots. In one example, W1 may be carried by FlexE group between NE4 and NE 5.

Similarly, when the network device is used as the transmitting end, it may transmit the data stream corresponding to the small-granule service through the timeslot occupied by FlexE client0, as shown in fig. 3, taking the network device NE4 as an example, and when the network device NE is used as the transmitting end, timeslots P1 occupied by FlexE client0 are all in an operating state. In a specific example, flexE client a occupies 5G bandwidth, including 480 sub-slots in total, and P1 occupies 480 sub-slots. In one example, P1 may be carried over FlexE group between NE4 and NE 5.

Next, in conjunction with fig. 4, a data processing method applied to the application scenario shown in fig. 3 provided by the embodiment of the present application is described. Fig. 4 is a signaling interaction diagram of a data processing method according to an embodiment of the present application. The data processing method 100 shown in fig. 4 may include the following S101-S104.

The communication device mentioned in the embodiment of the present application may be a network device such as a switch, a router, or a part of components on the network device, for example, a board, a line card on the network device, or a functional module on the network device, or a chip for implementing the method of the present application, and the embodiment of the present application is not specifically limited. The communication devices may be directly connected to each other, for example, but not limited to, via an ethernet cable or an optical cable.

In the embodiment of the present application, the communication device corresponds to a network device, and refers to: the communication means may be the network device itself or may be a part of a component on the network device.

The network device or node in the embodiment of the application can be a switch, a router and other network devices.

In one example, when the method 100 shown in fig. 4 is applied in the application scenario shown in fig. 3, the communication device 1 in the method 100 may correspond to the NE4 shown in fig. 3; the communication device 2 in the method 100 may correspond to NE3 shown in fig. 3; the communication device 3 in the method 100 may correspond to NE5 shown in fig. 3.

S101: the communication device 1 receives the data stream 1 of the small particle service 1 through the time slot occupied by FlexE client 1.

In one example, flexE client may be FlexE client carried by FlexE group between communication device 3 and communication device 1. For this case, the communication device 1 may receive the data stream 1 transmitted by the communication device 3 through a slot occupied by FlexE client 1. In the scenario shown in fig. 3, the slot taken up by FlexE client may correspond to W1 between NE4 and NE5, and correspondingly, flexE group carrying FlexE client1 may be FlexE group carrying the W1 provided between NE4 and NE 5.

S102: in response to a failure of FlexE group1 between communication devices 1 and 2 in the FlexE ring network, communication device 1 sends data stream 1 to communication device 3 in the FlexE ring network through a time slot occupied by FlexE client based on the time slot mapping relationship of FlexE client and FlexE client 2.

In the embodiment of the present application, flexE group2 is provided between the communication device 1 and the communication device 3, the FlexE group2 carries the FlexE client2, the time slot occupied by the FlexE client2 is divided into a plurality of sub-time slots 1, the plurality of sub-time slots 1 are used for carrying the small granule service 1, and the plurality of sub-time slots 1 are all working time slots. As can be appreciated with reference to fig. 3, the time slot occupied by FlexE client2 may correspond to P1 between NE4 and NE5, and, correspondingly, flexE group2 is FlexE group provided between NE4 and NE5 and carrying the P1. As an example, the slots FlexE client and FlexE client have a slot mapping relationship, and the data stream 1 received by the communication device 1 through the slot occupied by FlexE client1 may be mapped to the slot occupied by FlexE client and forwarded. As an example, data stream 1 received over the time slot occupied by FlexE client a may be mapped by the shim layer of the communication device 1 onto the time slot occupied by FlexE client b. Since all sub-slots 1 in the plurality of sub-slots 1 occupied by FlexE client are working slots, when the data stream 1 received through the slots occupied by FlexE client1 is mapped to the slots occupied by FlexE client for forwarding, the configuration of small-granule slots is not needed, and the large-granule slot mapping is performed on the large-granule level, so that the processing overhead of the communication device 1 is small.

In the embodiment of the present application, flexE group a 1 is provided between the communication device 1 and the communication device 3. The FlexE group is configured to carry FlexE client3, the time slot occupied by the FlexE client is divided into a plurality of sub-slots 2, the plurality of sub-slots 2 is configured to carry the small particle service 1, and the plurality of sub-slots 2 are all working time slots. As can be appreciated with reference to fig. 3, the time slot occupied by FlexE client may correspond to W1 between NE4 and NE3, and, correspondingly, flexE group1 is FlexE group provided between NE4 and NE3, carrying the W1. As an example, the slots FlexE client and FlexE client are configured with a slot mapping relationship, and the data stream 1 received by the communication device 1 through the slot occupied by FlexE client1 may be mapped to the slot occupied by FlexE client for forwarding. As an example, data stream 1 received over the slot occupied by FlexE client a may be mapped by the shim layer of the communication device 1 onto the slot occupied by FlexE client b. Since all sub-slots 2 in the plurality of sub-slots 2 occupied by FlexE client are working slots, when the data stream 1 received through the slot occupied by FlexE client1 is mapped to the slot occupied by FlexE client for forwarding, the configuration of small-granule slots is not needed, and the slot mapping of large granules is performed on the large-granule level, so that the processing overhead of the communication device 1 is small.

In one example, paths that can be used to forward the aforementioned data stream 1 may include a working path through which the data stream 1 may be forwarded when the working path is free of faults, and a protection path through which the data stream 1 may be switched to be forwarded when the working path is faulty. As one example, the foregoing FlexE group may be FlexE group on the working path and FlexE group2 may be FlexE group on the protection path. For this case, the communication device 1 may generate the data stream 1 to the communication device 3 through the timeslot carried by FlexE client2 carried by FlexE group2 in the event of FlexE group failure of the communication device 1, so that the data stream 1 may be forwarded through the protection path. In one example, flexE group1 fails, for example, it may be that a PHY included in FlexE group1 fails.

In one example, the communication apparatus 1 may also send path protection switching indication information to the communication apparatus 3, the path protection switching indication information indicating that the communication apparatus 3 switches from the working path to the protection path. In this way, after receiving the path protection switching instruction information, the communication device 3 can switch from the working path to the protection path, so as to forward the data stream 1 received from the communication device 1 through the protection path, thereby enabling the data stream 1 to be forwarded to the destination communication device through the protection path.

The embodiment of the present application does not specifically limit the specific implementation of the communication apparatus 1 transmitting the path protection switching indication information to the communication apparatus 3. In one example, the communication device 1 may send path protection switching indication information to the communication device 3 through a slot occupied by FlexE client. In a specific example, the communication device 1 may send an OAM message to the communication device 3 through a timeslot occupied by FlexE client b 2, where the OAM message may include the path protection switching indication information, and as an example, the path protection switching indication information may be carried by an APS code block in the OAM message.

S103: the communication device 3 receives the data stream 1 sent by the communication device 1 through the time slot occupied by FlexE client.

S104: the communication means 3 transmit said data stream 1 via a protection path.

After the communication device 1 transmits the data stream 1 to the communication device 3 through the slot occupied by FlexE client 2, the communication device 3 may receive the data stream 1 transmitted by the communication device 1 through the slot occupied by FlexE client. And further transmits the data stream 1 over a protection path. As an example, the communication device 3 may send the data stream 1 through a protection path according to path protection switching indication information sent by the communication device 1. As can be appreciated with reference to fig. 3, after NE5 receives data stream 1 transmitted by NE4 via the time slot comprised by P1 between NE5 and NE4, data stream 1 may be transmitted to NE6 via the time slot comprised by P1 between NE5 and NE6. Specifically, NE5 may map data stream 1 received over the time slot comprised by P1 between NE5 and NE4 to be transmitted over the time slot comprised by P1 between NE5 and NE6. In one example, all sub-slots included in P1 between NE5 and NE6 are in operation, so that NE5 maps data stream 1 received through slots included in P1 between NE5 and NE4 onto slots included in P1 between NE5 and NE6 without sensing small granule slot configuration, and large granule slot mapping is performed at the large granule level, so that processing overhead of communication device 3 is small.

As can be seen from the above description, with the solution according to the embodiment of the present application, when the communication device 1 forwards the data stream 1 of the small-granule service 1 through the protection path, the communication device 1 does not need to perceive the configuration of the small-granule time slot, and the processing overhead of the communication device 1 is small.

In one example, after the working path failure recovery, the communication device 1 may re-switch the small particle traffic 1 to forwarding on the working path. In a specific example, the communication device 1 may also receive the data stream 2 of the small particle service 1 through a time slot occupied by FlexE client a 1. In the case of the FlexE group a failure recovery, the communication device 1 may send the data stream 2 to the communication device 2 through the time slot occupied by the FlexE client a based on the time slot mapping relationship of the FlexE client a and the FlexE client a. Specifically, the shim layer of the communication device 1 may map the data stream 2 received through the timeslot occupied by FlexE client to the timeslot occupied by FlexE client, so as to send the data stream 2 through the working path.

In an example, the data processing method provided by the embodiment of the present application may further include the method 200 shown in fig. 5. Fig. 5 is a signaling interaction diagram of another data processing method according to an embodiment of the present application. The data processing method shown in fig. 5 can be applied to the application scenario shown in fig. 5.

In one example, when the method 200 shown in fig. 5 is applied in the application scenario shown in fig. 6, the communication device 1 in the method 200 may correspond to the NE4 shown in fig. 6; the communication device 2 in the method 200 may correspond to NE3 shown in fig. 6; the communication device 3 in the method 200 may correspond to NE5 shown in fig. 6.

The method 200 may include, for example, S201-S204 as follows.

S201: the communication device 1 receives the data stream 3 of the small particle service 2 via the time slot occupied by FlexE client 4.

Fig. 6 is a schematic diagram of a FlexE ring network according to an embodiment of the present application. As shown in fig. 6, in one example, flexE client4 may be FlexE client carried by FlexE group between communication device 2 and communication device 1. For this case, the communication device 1 may receive the data stream 3 transmitted by the communication device 2 through the slot occupied by FlexE client 4. In the scenario shown in fig. 6, the timeslot taken up by FlexE client4 may correspond to W2 between NE4 and NE3, and correspondingly, flexE group carrying FlexE client may be FlexE group carrying the W2 provided between NE4 and NE 3.

S202: the communication device 1 responds to FlexE group faults between the communication device 1 and the communication device 3, and sends the data stream 3 to the communication device 2 through the time slot occupied by the FlexE client on the basis of the time slot mapping relation of the FlexE client and the FlexE client 5.

In the embodiment of the present application, flexE group4 is provided between the communication device 1 and the communication device 2, the FlexE group carries the FlexE client5, the time slot occupied by the FlexE client is divided into a plurality of sub-slots 3, the plurality of sub-slots 3 are used for carrying the small particle service 2, and the plurality of sub-slots 3 are all working time slots. As can be appreciated with reference to fig. 6, the time slot occupied by FlexE client may correspond to P2 between NE4 and NE3, and, correspondingly, flexE group is FlexE group provided between NE4 and NE3 to carry the P2. As an example, the slots FlexE client and FlexE client5 have a slot mapping relationship, and the data stream 2 received by the communication device 1 through the slot occupied by FlexE client may be mapped to the slot occupied by FlexE client and forwarded. As an example, data stream 2 received over the slots occupied by FlexE client may be mapped onto the slots occupied by FlexE client by the shim layer of the communication device 1. Since all sub-slots 3 in the plurality of sub-slots 3 occupied by FlexE client are working slots, when the data stream 2 received through the slot occupied by FlexE client4 is mapped to the slot occupied by FlexE client for forwarding, the configuration of small-granule slots is not needed, and the slot mapping of large granules is performed on the large-granule level, so that the processing overhead of the communication device 1 is small.

In the embodiment of the present application, the FlexE group is used for carrying FlexE client6, the time slot occupied by the FlexE client is divided into a plurality of sub-slots 4, the plurality of sub-slots 4 are configured for carrying the small particle service 2, and the plurality of sub-slots 4 are all working time slots. As can be appreciated with reference to fig. 6, the time slot occupied by FlexE client may correspond to W2 between NE4 and NE5, and, correspondingly, flexE group is FlexE group provided between NE4 and NE5 to carry the W2. As an example, the slots FlexE client and FlexE client are configured with a slot mapping relationship, and the data stream 2 received by the communication device 1 through the slot occupied by FlexE client may be mapped to the slot occupied by FlexE client and forwarded. As an example, data stream 2 received over the time slot occupied by FlexE client a may be mapped by the shim layer of the communication device 1 onto the time slot occupied by FlexE client a. Since all the sub-slots 4 in the plurality of sub-slots 4 occupied by FlexE client are working slots, when the data stream 2 received through the slots occupied by FlexE client is mapped to the slots occupied by FlexE client for forwarding, the configuration of small-granule slots is not needed, and the large-granule slot mapping is performed at the large-granule level, so that the processing overhead of the communication device 1 is small.

In one example, paths that can be used to forward the aforementioned data stream 2 may include a working path through which the data stream 2 may be forwarded when the working path is free of faults, and a protection path through which the data stream 2 may be switched to be forwarded when the working path is faulty. As one example, the foregoing FlexE group may be FlexE group on the working path and FlexE group4 may be FlexE group on the protection path. For this case, the communication device 1 may generate the data stream 2 to the communication device 2 through the timeslot carried by FlexE client5 carried by FlexE group4 in the event of FlexE group failure, so that the data stream 2 may be forwarded through the protection path. In one example, flexE group is malfunctioning, which may be, for example, a PHY included in FlexE group is malfunctioning.

In one example, the communication apparatus 1 may also send path protection switching indication information to the communication apparatus 2, the path protection switching indication information indicating that the communication apparatus 2 switches from the working path to the protection path. In this way, after receiving the path protection switching instruction information, the communication device 2 can switch from the working path to the protection path, so as to forward the data stream 2 received from the communication device 1 through the protection path, thereby enabling the data stream 2 to be forwarded to the destination communication device through the protection path. As for the specific implementation of the communication apparatus 1 transmitting the path protection switching indication information to the communication apparatus 2, reference may be made to the above specific implementation of the method 100 for the communication apparatus 1 transmitting the path protection switching indication information to the communication apparatus 3, which is not repeated here.

S203: the communication device 2 transmits the data stream 3 via the time slot occupied by the FlexE client by the receiving communication device 1.

S204: the communication device 2 transmits said data stream 3 via a protection path.

After the communication device 1 transmits the data stream 2 to the communication device 2 through the slot occupied by FlexE client, the communication device 2 may receive the data stream 2 transmitted by the communication device 1 through the slot occupied by FlexE client. And further transmits the data stream 2 over a protection path. As an example, the communication device 2 may send the data stream 2 through a protection path according to path protection switching indication information sent by the communication device 1. As can be appreciated with reference to fig. 6, after NE3 receives data stream 2 transmitted by NE4 via the time slot comprised by P2 between NE3 and NE4, data stream 2 may be transmitted to NE2 via the time slot comprised by P2 between NE3 and NE 3. Specifically, NE3 may map data stream 2 received over the time slot comprised by P2 between NE3 and NE4 to be transmitted over the time slot comprised by P2 between NE3 and NE2. In one example, all sub-slots included in P2 between NE3 and NE2 are in operation, so that NE3 maps data stream 2 received through slots included in P2 between NE4 and NE3 onto slots included in P2 between NE3 and NE2 without sensing small granule slot configuration, and large granule slot mapping is performed at the large granule level, so that processing overhead of communication device 2 is small.

In an example, the small particle service 1 and the small particle service 2 may correspond to the same small particle service, and in this case, by using the scheme of the embodiment of the present application, the path symmetry of the uplink and downlink data streams corresponding to the small particle service may be implemented. Next, in connection with fig. 6, a description will be given by taking as an example a small-particle service transmitted between NE3 and NE 5. When the NE3 sends a data stream corresponding to the small-particle service to the NE5, the forwarding path of the data stream is as follows: NE3-NE4-NE5, wherein the data stream may be carried over the time slot occupied by W2 between NE3 and NE4, and over the time slot occupied by W2 between NE4 and NE 5. When the NE5 sends a data stream corresponding to the small-particle service to the NE3, the forwarding path of the data stream is as follows: NE5-NE4-NE3, wherein the data stream may be carried over the time slot occupied by W1 between NE5 and NE4, and over the time slot occupied by W1 between NE4 and NE 3.

The embodiment of the application also provides a data processing method 300 which can be applied to the first communication device in the FlexE ring network. In one example, the method may be applied to the above method 100 or 200 for performing the operations performed by the communication device 1 in the above method 100 or 200.

Referring to fig. 7, the flow chart of a data processing method according to an embodiment of the present application is shown. The method 300 shown in fig. 7 may include, for example, the following S301-S302.

S301: a first data stream of a first small particle service is received over a time slot occupied by a first flexible ethernet client FlexE client.

First FlexE client in method 300 may correspond to FlexE client1 in method 100; the first small particle service in method 300 may correspond to small particle service 1 in method 100; the first data stream in method 300 may correspond to data stream 1 in method 100.

S302: in response to a failure of a first FlexE group between a first communication device and a second communication device in the FlexE ring network, the first data stream is sent to a third communication device in the FlexE ring network through a time slot occupied by the second FlexE client based on a first time slot mapping relationship of the first FlexE client and second FlexE client.

The second communication device in method 300 may correspond to communication device 2 in method 100; first FlexE group in method 300 may correspond to FlexE group1 in method 100; second FlexE client in method 300 may correspond to FlexE client in method 100; the third communication device in method 300 may correspond to communication device 3 in method 100.

Wherein:

A second FlexE group is provided between the first communication device and the third communication device, the second FlexE group carries the second FlexE client, the time slot occupied by the second FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used for carrying the first small particle service, and the plurality of first sub-time slots are all working time slots.

Second FlexE group in method 300 may correspond to FlexE group in method 100; the first sub-slot in method 300 may correspond to sub-slot 1 in method 100.

The first FlexE group is configured to carry a third FlexE client, and a time slot occupied by the third FlexE client is divided into a plurality of second sub-time slots, where the plurality of second sub-time slots are configured to carry the first small particle service, and the plurality of second sub-time slots are all working time slots.

Third FlexE client in method 300 may correspond to FlexE client in method 100; the second sub-slot in method 300 may correspond to sub-slot 2 in method 100.

In one possible implementation, the method further includes: and sending path protection switching indication information to the third communication device, wherein the path protection switching indication information indicates the third communication device to switch from a working path to a protection path.

In one possible implementation manner, the sending path protection switching indication information to the third communication device includes: and sending FlexE operation, administration and maintenance OAM message to the third communication device through the timeslot occupied by the second FlexE client, where an automatic protection switching APS code block in the FlexE OAM message is used to carry the path protection switching indication information.

In one possible implementation, the method further includes: receiving a second data stream of the first small particle service through a time slot occupied by the first FlexE client; in response to the first FlexE group failure recovery, the second data stream is sent to the second communications device over the time slot occupied by the third FlexE client based on the second time slot mapping relationship of the first FlexE client and the third FlexE client.

The second data stream in method 300 may correspond to data stream 2 in method 100.

In one possible implementation, the method further includes:

Receiving a third data stream of the second small particle service through a time slot occupied by a fourth FlexE client; in response to a third FlexE group failure between a first communication device and a third communication device in the FlexE ring network, transmitting the third data stream to a second communication device in the FlexE ring network over a time slot occupied by the fifth FlexE client based on a third time slot mapping relationship of the fourth FlexE client and fifth FlexE client.

Fourth FlexE client in method 300, which may correspond to FlexE client in method 200; the second small particle traffic in method 300 may correspond to small particle traffic 2 in method 200; third FlexE group in method 300 may correspond to FlexE group in method 200; fifth FlexE client in method 300 may correspond to FlexE client5 in method 200;

wherein:

A fourth FlexE group is provided between the first communication device and the second communication device, the fourth FlexE group carries the fifth FlexE client, the time slot occupied by the fifth FlexE client is divided into a plurality of third sub-time slots, the plurality of third sub-time slots are used for carrying the second small particle service, and the plurality of third sub-time slots are all working time slots.

The third FlexE group is configured to carry the sixth FlexE client, and the time slot occupied by the sixth FlexE client is divided into a plurality of fourth sub-time slots, where the plurality of fourth sub-time slots are configured to carry the second small particle service, and the plurality of fourth sub-time slots are all working time slots.

Fourth FlexE group in method 300, which may correspond to FlexE group in method 200; the third sub-slot in method 300 may correspond to sub-slot 3 in method 200; sixth FlexE client in method 300 may correspond to FlexE client in method 200; the fourth sub-slot in method 300 may correspond to sub-slot 4 in method 200.

The embodiment of the application also provides a data processing method 400 which can be applied to the first communication device in the FlexE ring network. In one example, the method may be applied to the above method 100 or 200 for performing the operations performed by the communication device 2 or the communication device 3 in the above method 100 or 200. When the method 400 is applied to the above method 100, the first communication device in the method 400 may correspond to the communication device 3 in the method 100; when the method 400 is applied to the above method 200, the first communication device in the method 400 may correspond to the communication device 2 in the method 200.

Referring to fig. 8, a flow chart of another data processing method according to an embodiment of the present application is shown. The method 400 shown in fig. 8 may include, for example, the following S401-S402.

S401: receiving a first data stream of a first small particle service sent by a second communication device through a time slot occupied by a first flexible ethernet client FlexE client; wherein: a first FlexE group is provided between the second communication device and the first communication device, the first FlexE group carries the first FlexE client, the time slot occupied by the first FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used for carrying the first small particle service, and the plurality of first sub-time slots are all working time slots.

When the method 400 is applied to the above method 100: first FlexE client in method 400 may correspond to FlexE client in method 100; the second communication device in method 400 may correspond to communication device 1 in method 100; first FlexE group in method 400 may correspond to FlexE group in method 100; the first small particle service in method 400 may correspond to small particle service 1 in method 100; the first data stream in method 400 may correspond to data stream 1 in method 100; the first sub-slot in method 400 may correspond to sub-slot 1 in method 100.

When the method 400 is applied to the method 200 above: first FlexE client in method 400 may correspond to FlexE client in method 200; the second communication device in method 400 may correspond to communication device 1 in method 100; first FlexE group in method 400 may correspond to FlexE group in method 200; the first small particle traffic in method 400 may correspond to small particle traffic 2 in method 200; the first data stream in method 400 may correspond to data stream 3 in method 200; the first sub-slot in method 400 may correspond to sub-slot 3 in method 200.

S402: and transmitting the first data stream through a protection path.

With respect to the specific implementation of the method 300 and the method 400, reference may be made to the relevant description of the method 100 and the method 200 above, which is not repeated here.

The embodiment of the application provides a first communication device, which comprises: a transceiver unit and/or a processing unit; the transceiver unit is configured to perform a receiving and/or transmitting operation performed by the first communication device according to any one of the above method embodiments; the processing unit is configured to perform operations other than the receiving and/or transmitting operations performed by the first communication device according to any of the above method embodiments.

In a specific example, reference may be made to fig. 9, and fig. 9 is a schematic structural diagram of a first communication device according to an embodiment of the present application. The first communication apparatus shown in fig. 9 may include a receiving unit 901 and a transmitting unit 902.

As one example:

The receiving unit 901 is configured to receive a first data stream of a first small-granule service through a time slot occupied by a first flexible ethernet client FlexE client;

A sending unit 902, configured to send, in response to a failure of a first FlexE group between a first communication device and a second communication device in the FlexE ring network, the first data stream to a third communication device in the FlexE ring network through a time slot occupied by the second FlexE client based on a first time slot mapping relationship of the first FlexE client and the second FlexE client, where:

A second FlexE group is provided between the first communication device and the third communication device, the second FlexE group carries the second FlexE client, the time slot occupied by the second FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used for carrying the first small particle service, and the plurality of first sub-time slots are all working time slots; the first FlexE group is configured to carry a third FlexE client, and a time slot occupied by the third FlexE client is divided into a plurality of second sub-time slots, where the plurality of second sub-time slots are configured to carry the first small particle service, and the plurality of second sub-time slots are all working time slots.

In a possible implementation manner, the sending unit 902 is further configured to: and sending path protection switching indication information to the third communication device, wherein the path protection switching indication information indicates the third communication device to switch from a working path to a protection path.

In a possible implementation manner, the sending unit 902 is specifically configured to: and sending FlexE operation, administration and maintenance OAM message to the third communication device through the timeslot occupied by the second FlexE client, where an automatic protection switching APS code block in the FlexE OAM message is used to carry the path protection switching indication information.

In a possible implementation manner, the receiving unit 901 is further configured to: receiving a second data stream of the first small particle service through a time slot occupied by the first FlexE client; the sending unit 902 is further configured to send, in response to the first FlexE group failure recovery, the second data stream to the second communication device through a slot occupied by the third FlexE client based on a second slot mapping relationship of the first FlexE client and the third FlexE client.

In a possible implementation manner, the receiving unit 901 is further configured to receive a third data stream of the second small-granule service through a time slot occupied by a fourth FlexE client; the sending unit 902 is further configured to send, in response to a failure of a third FlexE group between the first communication device and a third communication device in the FlexE ring network, the third data stream to the second communication device in the FlexE ring network through a time slot occupied by the fifth FlexE client based on a third time slot mapping relationship of the fourth FlexE client and the fifth FlexE client, where: a fourth FlexE group is provided between the first communication device and the second communication device, the fourth FlexE group carries the fifth FlexE client, the time slot occupied by the fifth FlexE client is divided into a plurality of third sub-time slots, the plurality of third sub-time slots are used for carrying the second small particle service, and the plurality of third sub-time slots are all working time slots; the third FlexE group is configured to carry the sixth FlexE client, and the time slot occupied by the sixth FlexE client is divided into a plurality of fourth sub-time slots, where the plurality of fourth sub-time slots are configured to carry the second small particle service, and the plurality of fourth sub-time slots are all working time slots.

As another example:

A receiving unit 901, configured to receive, through a time slot occupied by a first flexible ethernet client FlexE client, a first data stream of a first small-granule service sent by a second communication device; wherein: a first FlexE group is provided between the second communication device and the first communication device, the first FlexE group carries the first FlexE client, the time slot occupied by the first FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used for carrying the first small particle service, and the plurality of first sub-time slots are all working time slots;

a transmitting unit 902, configured to transmit the first data stream through a protection path.

In a possible implementation manner, the receiving unit 901 is further configured to: and receiving path protection switching indication information sent by the second communication device, wherein the path protection switching indication information indicates the first communication device to switch from a working path to the protection path.

In a possible implementation manner, the receiving unit 901 is specifically configured to: and receiving FlexE operation, administration and maintenance (OAM) information sent by the second communication device through a time slot occupied by the first FlexE client, wherein an Automatic Protection Switching (APS) code block in the FlexE OAM information is used for bearing the path protection switching indication information.

In a possible implementation manner, the sending unit 902 is specifically configured to: and sending the first data stream through the protection path according to the path protection switching indication information.

As shown in fig. 10, the communication device 1000 includes a processing circuit 1010 and an interface circuit 1020. The processing circuit 1010 and the interface circuit 1020 are coupled to each other. It is understood that interface circuit 1020 may be a transceiver or an input-output interface. Optionally, the communication device 1000 may further comprise a memory for storing instructions for execution by the processing circuitry or for storing input data required by the processing circuitry 1010 to execute instructions or for storing data generated after the processing circuitry 1010 has executed instructions.

When the communication apparatus 1000 is used to implement the method 100, the method 200, the method 300, or the method 400, the interface circuit 1020 is used to implement the functions of the receiving unit 901 and the transmitting unit 902 corresponding to the first communication apparatus 900 described above; the processing circuit 1010 is configured to realize functions other than the functions of the reception unit 901 and the transmission unit 902 realized by the first communication apparatus 900 described above.

As shown in fig. 11, the communication device 1100 includes a processor 1110 and a communication interface 1120. Processor 1110 and communication interface 1120 are coupled to each other. It is to be appreciated that the communication interface 1120 may be a transceiver or an input-output interface. Optionally, the communication device 1100 may further include a memory 1130 for storing instructions to be executed by the processor 1110 or for storing input data required by the processor 1110 to execute instructions or for storing data generated after the processor 1110 executes instructions.

When the communication device 1100 is used to implement the method 100, the method 200, the method 300 or the method 400, the communication interface 1120 is used to implement the functions of the receiving unit 901 and the transmitting unit 902 corresponding to the first communication device 900, and the processor 1110 is used to implement other functions implemented by the first communication device 900, except for the functions of the receiving unit 901 and the transmitting unit 902.

When the communication device (e.g., the first communication device 900, the communication device 1000, and the communication device 1100) is a chip applied to the communication device, the communication device chip implements the functions of the communication device in the above-described method embodiment. The communication device chip receives information from other modules (e.g., radio frequency modules or antennas) in the communication device, the information being sent to the communication device chip by other communication devices; or the communication device chip transmits information to other modules (e.g., radio frequency modules or antennas) in the communication device that the communication device sends to the other communication device chips.

It is to be appreciated that the processor in embodiments of the present application may be a central processing unit (central processing unit, CPU), other general purpose processor, digital signal processor (DIGITAL SIGNAL processor, DSP), application Specific Integrated Circuit (ASIC), field programmable gate array (field programmable GATE ARRAY, FPGA) or other programmable logic device, transistor logic device, hardware components, or any combination thereof. The general purpose processor may be a microprocessor, but in the alternative, it may be any conventional processor.

The application also provides a computer readable storage medium having instructions stored therein which, when run on a computer, cause the computer to perform any one or more of the operations of the methods described in the previous embodiments (e.g., method 100, method 200, method 300, or method 400).

The application also provides a computer program product comprising a computer program which, when run on a computer, causes the computer to perform any one or more of the operations of the methods described in the previous embodiments (e.g. method 100, method 200, method 300 or method 400).

The application also provides a communication system. In one example, the communication system may include communication device 1 and communication device 3 in method 100 above. In yet another example, the communication system may include communication device 1 and communication device 2 in the above method 200. In another example, the communication system may include the first communication device in the above method 300 and the first communication device in the above method 400.

According to the method provided by the application, the application further provides a chip system, and the chip system can comprise a processor. The processor is coupled to the memory and may be used in the above method 100, method 200, method 300, or method 400. Optionally, the system on a chip further comprises a memory. Memory for storing a computer program (which may also be referred to as code, or instructions). A processor for calling and running a computer program from a memory, causing a device on which the chip system is installed to perform the above method 100, method 200, method 300 or method 400.

The terms "first," "second," "third," "fourth" and the like in the description and in the claims and in the above drawings, if any, are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that the embodiments described herein may be implemented in other sequences than those illustrated or otherwise described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, which are not repeated herein.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, e.g., the division of units is merely a logical service division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each service unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software business units.

The integrated units, if implemented in the form of software business units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

Those skilled in the art will appreciate that in one or more of the examples described above, the services described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the services may be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The objects, technical solutions and advantageous effects of the present invention have been described in further detail in the above embodiments, and it should be understood that the above are only embodiments of the present invention.

The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the application.

Claims

1. A data processing method, characterized in that it is applied to a first communication device in a Flexible Ethernet FlexE ring network, the method comprising:

Receiving a first data stream of a first small-granularity service through a time slot occupied by a first flexible Ethernet client FlexE client;

In response to a failure of a first FlexE group between a first communication device and a second communication device in the FlexE ring network, based on a first time slot mapping relationship between the first FlexE client and the second FlexE client, the first data stream is sent to a third communication device in the FlexE ring network through a time slot occupied by the second FlexE client, wherein:

A second FlexE group is provided between the first communication device and the third communication device, the second FlexE group carries the second FlexE client, the timeslot occupied by the second FlexE client is divided into a plurality of first sub-timeslots, the plurality of first sub-timeslots are used to carry the first small-granularity service, and the plurality of first sub-timeslots are all working timeslots;

The first FlexE group is used to carry a third FlexE client, the time slot occupied by the third FlexE client is divided into multiple second sub-time slots, the multiple second sub-time slots are configured to carry the first small-granularity service, and the multiple second sub-time slots are all working time slots.

2. The method according to claim 1, characterized in that the method further comprises:

Path protection switching indication information is sent to the third communication device, where the path protection switching indication information instructs the third communication device to switch from the working path to the protection path.

3. The method according to claim 2, wherein the sending of the path protection switching indication information to the third communication device comprises:

A FlexE operation, administration and maintenance OAM message is sent to the third communication device through the time slot occupied by the second FlexE client, and the automatic protection switching APS code block in the FlexE OAM message is used to carry the path protection switching indication information.

4. The method according to any one of claims 1 to 3, characterized in that the method further comprises:

receiving a second data stream of the first small-granularity service through the time slot occupied by the first FlexE client;

In response to the failure recovery of the first FlexE group, based on the second time slot mapping relationship between the first FlexE client and the third FlexE client, the second data stream is sent to the second communication device through the time slot occupied by the third FlexE client.

5. The method according to claim 1, characterized in that the method further comprises:

receiving a third data stream of a second small-granularity service through a timeslot occupied by a fourth FlexE client;

In response to a third FlexE group failure between the first communication device and the third communication device in the FlexE ring network, based on a third time slot mapping relationship between the fourth FlexE client and the fifth FlexE client, the third data stream is sent to the second communication device in the FlexE ring network through the time slot occupied by the fifth FlexE client, wherein:

A fourth FlexE group is provided between the first communication device and the second communication device, the fourth FlexE group carries the fifth FlexE client, the timeslot occupied by the fifth FlexE client is divided into a plurality of third sub-timeslots, the plurality of third sub-timeslots are used to carry the second small-granularity service, and the plurality of third sub-timeslots are all working timeslots;

The third FlexE group is used to carry the sixth FlexE client, the time slot occupied by the sixth FlexE client is divided into multiple fourth sub-time slots, the multiple fourth sub-time slots are configured to carry the second small-granularity service, and the multiple fourth sub-time slots are all working time slots.

6 . The method according to claim 5 , wherein the first small-granule service and the second small-granule service belong to the same small-granule service.

7. The method according to any one of claims 1-6 is characterized in that the first FlexE group is a FlexE group on a working path, and the second FlexE group is a FlexE group on a protection path.

8. A data processing method, characterized in that it is applied to a first communication device in a FlexE ring network, the method comprising:

receiving a first data stream of a first small-grained service sent by a second communication device through a time slot occupied by a first flexible Ethernet client FlexE client; wherein: a first FlexE group is provided between the second communication device and the first communication device, the first FlexE group carries the first FlexE client, the time slot occupied by the first FlexE client is divided into a plurality of first sub-time slots, the plurality of first sub-time slots are used to carry the first small-grained service, and the plurality of first sub-time slots are all working time slots;

The first data flow is sent through a protection path.

9. The method according to claim 8, characterized in that the method further comprises:

receiving path protection switching indication information sent by the second communication device;

According to the path protection switching indication information, the working path is switched to the protection path.

10. The method according to claim 9, wherein receiving the path protection switching indication information sent by the second communication device comprises:

The FlexE operation, administration and maintenance OAM message sent by the second communication device is received through the time slot occupied by the first FlexE client, and the automatic protection switching APS code block in the FlexE OAM message is used to carry the path protection switching indication information.

11. A first communication device, characterized in that the device comprises:

A receiving unit and a sending unit;

The transceiver unit is used to perform the receiving operation performed by the first communication device as described in any one of claims 1 to 7, and the sending unit is used to perform the sending operation performed by the first communication device as described in any one of claims 1 to 7; or

The transceiver unit is used to perform the receiving operation performed by the first communication device as described in any one of claims 8-10, and the sending unit is used to perform the sending operation performed by the first communication device as described in any one of claims 8-10.

12. A communication device, characterized in that it comprises: a communication interface and a processor, and according to the communication interface and the processor, the communication device executes the method according to any one of claims 1 to 10.

13. A communication system, characterized in that the system comprises:

A first communication device that executes the method according to any one of claims 1 to 7 above and a first communication device that executes the method according to any one of claims 8 to 10.