Flow data processing method and device, storage medium, and electronic device

Abstract

The present disclosure is about a method and device for processing flow data, a storage medium, and an electronic device, and relates to the fields of network technology and security technology. The method includes: obtaining flow data to be transmitted and a target program identifier of a target client that generates the flow data to be transmitted; matching a target time slot and a target sub-time slot corresponding to the target client in a flexible Ethernet group according to the target program identifier; wherein the target time slot and the target sub-time slot are configured according to the service category of the target client; generating a flow message to be transmitted according to the flow data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot, and the target sub-time slot; transmitting the flow message to be transmitted to the opposite network device based on the target time slot and the target sub-time slot. The present disclosure improves the utilization rate of bandwidth.

Description

Background Art

[0002] With the construction of 5G, network development has put forward higher requirements for mobile bearer bandwidth. At present, when standard Ethernet interfaces are used as telecommunication network interfaces, there are the following problems: the same interface is not supported to carry various services, resulting in low bandwidth utilization.

[0003] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to ordinary technicians in the field. Summary of the invention

[0004] The purpose of the present disclosure is to provide a method for processing traffic data, a device for processing traffic data, a computer-readable storage medium, and an electronic device, thereby at least to a certain extent overcoming the problem of low bandwidth utilization caused by the limitations and defects of related technologies.

[0005] According to one aspect of the present disclosure, a method for processing flow data is provided, which is configured on a local network device, and the method for processing flow data includes:

[0006] Acquire the traffic data to be transmitted and the target program identifier of the target client that generates the traffic data to be transmitted;

[0007] According to the target program identifier, a target time slot and a target sub-time slot corresponding to the target client are matched in the flexible Ethernet group; wherein the target time slot and the target sub-time slot are configured according to the service category of the target client;

[0008] Generate a traffic message to be transmitted according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot;

[0009] The traffic message to be transmitted is transmitted to the opposite network device based on the target time slot and the target sub-time slot, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and the target program identifier included in the traffic message to be transmitted.

[0010] In an exemplary embodiment of the present disclosure, the method for processing traffic data further includes:

[0011] Building the flexible Ethernet group on the local network device, and binding one or more original physical flexible Ethernet interfaces into the flexible Ethernet group;

[0012] Creating one or more original clients with original program identifiers, and associating each of the original clients with the program identifiers into the flexible Ethernet group;

[0013] According to the service category of the original client included in the flexible Ethernet group, the original timeslot and the original sub-timeslot of the original physical flexible Ethernet interface are allocated to the original client, and a mapping relationship between the original timeslot and the original sub-timeslot and the original program identifier is established;

[0014] A logical interface service corresponding to the original client is configured in a logical interface included in an original physical flexible Ethernet interface allocated to the original client, and an original logical sub-interface corresponding to the original client is created in the logical interface.

[0015] In an exemplary embodiment of the present disclosure, the method for processing traffic data further includes:

[0016] According to the time slot distribution mechanism included in the preset time slot allocator, the original time slot is allocated to the original physical flexible Ethernet interface, and based on the time slot distribution mechanism, the original time slot allocated to the original physical flexible Ethernet interface is divided into multiple original sub-time slots; wherein the time slot granularity of the original physical flexible Ethernet interface is 5G, and the time slot granularity of the original sub-time slot is 1G.

[0017] In an exemplary embodiment of the present disclosure, the flexible Ethernet group is an interface with a preset bandwidth;

[0018] The bandwidth of the flexible Ethernet group is the sum of the bandwidths of all original physical flexible Ethernet interfaces bound in the flexible Ethernet group.

[0019] In an exemplary embodiment of the present disclosure, matching a target timeslot and a target sub-timeslot corresponding to the target client in a flexible Ethernet group according to the target program identifier includes:

[0020] Based on the mapping relationship between the original timeslot and the original sub-timeslot and the original program identifier, a target timeslot and a target sub-timeslot corresponding to the target client are matched in the flexible Ethernet group according to the target program identifier.

[0021] In an exemplary embodiment of the present disclosure, transmitting the to-be-transmitted traffic message to the opposite network device based on the target time slot and the target sub-time slot includes:

[0022] The traffic message to be transmitted is forwarded to the target logical sub-interface based on the target time slot, and the traffic message to be transmitted is transmitted to the opposite network device via the target logical sub-interface based on the target sub-time slot.

[0023] In an exemplary embodiment of the present disclosure, the peer network device forwards the to-be-transmitted traffic data to the target client where the peer network device is located according to the coding sequence number and the target program identifier included in the to-be-transmitted traffic message, including:

[0024] The opposite network device obtains the target time slot and the target sub-time slot included in the traffic message to be transmitted, and determines the target physical flexible Ethernet interface and the target logical sub-interface corresponding to the target time slot and the target sub-time slot according to the time slot scheduling rule;

[0025] The opposite network device determines, based on the binding relationship between the flexible Ethernet group and the original physical flexible Ethernet interface, the flexible Ethernet group corresponding to the coding sequence number included in the traffic message to be transmitted;

[0026] The opposite network device determines the target client corresponding to the target program identifier included in the traffic message to be transmitted in the flexible Ethernet group based on the mapping relationship between the original physical flexible Ethernet interface and the original program identifier, and transmits the traffic message to be transmitted to the target client.

[0027] According to one aspect of the present disclosure, a flow data processing device is provided, which is configured in a local network device, and the flow data processing device includes:

[0028] A flow data acquisition module, used to acquire the flow data to be transmitted and the target program identifier of the target client that generates the flow data to be transmitted;

[0029] A time slot matching module, used for matching a target time slot and a target sub-time slot corresponding to the target client in the flexible Ethernet group according to the target program identifier; wherein the target time slot and the target sub-time slot are configured according to the service category of the target client;

[0030] A traffic message generation module, used for generating a traffic message to be transmitted according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot;

[0031] A traffic message transmission module is used to transmit the traffic message to be transmitted to the opposite network device based on the target time slot and the target sub-time slot, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and the target program identifier included in the traffic message to be transmitted.

[0032] According to one aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the method for processing flow data described in any one of the above is implemented.

[0033] According to one aspect of the present disclosure, there is provided an electronic device, including:

[0034] Processor; and

[0035] A memory, configured to store executable instructions of the processor;

[0036] The processor is configured to execute any one of the above-mentioned methods for processing traffic data by executing the executable instructions.

[0037] A method for processing flow data provided by an embodiment of the present disclosure includes, on the one hand, matching a target time slot and a target sub-time slot corresponding to a target client in a flexible Ethernet group according to a target program identifier; then generating a flow message to be transmitted according to the flow data to be transmitted, a coding sequence number of the flexible Ethernet group, a target program identifier, a target time slot and a target sub-time slot; finally transmitting the flow message to be transmitted to a peer network device based on the target time slot and the target sub-time slot, so that the peer network device forwards the flow data to be transmitted to the target client where the peer network device is located according to the coding sequence number and the target program identifier included in the flow message to be transmitted, thereby solving the problem in the prior art that the same interface is not supported to carry various different services, thereby improving the bandwidth utilization; on the other hand, matching a target time slot and a target sub-time slot corresponding to a target client in a flexible Ethernet group according to a target program identifier, and the target time slot and the target sub-time slot are configured according to the service category of the target client, thereby enabling different target clients to use different target time slots and target sub-time slots, thereby achieving service isolation and improving service access efficiency.

[0038] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] The accompanying drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification are used to explain the principles of the present disclosure. Obviously, the accompanying drawings described below are only some embodiments of the present disclosure, and for ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without creative work.

[0040] Figure 1A flow chart schematically illustrates a method for processing traffic data according to an exemplary embodiment of the present disclosure.

[0041] Figure 2 A schematic diagram of a FlexE general architecture based on the Flexible Ethernet protocol according to an exemplary embodiment of the present disclosure is schematically shown.

[0042] Figure 3 A schematic diagram schematically shows a time slot allocation situation of a FlexE Group according to an exemplary embodiment of the present disclosure.

[0043] Figure 4 A schematic diagram of an application scenario of a FlexE communication system according to an exemplary embodiment of the present disclosure is schematically shown.

[0044] Figure 5 The flowchart schematically shows a method for allocating time slots of a Client according to an exemplary embodiment of the present disclosure.

[0045] Figure 6 An example diagram schematically shows an allocation scenario example of an original physical flexible Ethernet interface and an original client included in a flexible Ethernet group according to an example embodiment of the present disclosure.

[0046] Figure 7 An example diagram of a configuration scenario of a logical interface service and a logical sub-interface service according to an example embodiment of the present disclosure is schematically shown.

[0047] Figure 8 The following schematically shows an example diagram of a traffic data transmission scenario according to an example embodiment of the present disclosure.

[0048] Fig. 9 A block diagram schematically shows a device for processing traffic data according to an example embodiment of the present disclosure.

[0049] Fig.10 An electronic device for implementing the above-mentioned method for processing traffic data according to an exemplary embodiment of the present disclosure is schematically shown. DETAILED DESCRIPTION

[0050] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as being limited to the examples set forth herein; on the contrary, these embodiments are provided so that the present disclosure will be more comprehensive and complete, and the concepts of the example embodiments are fully conveyed to those skilled in the art. The described features, structures, or characteristics may be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided to provide a full understanding of the embodiments of the present disclosure. However, those skilled in the art will appreciate that the technical solutions of the present disclosure may be practiced while omitting one or more of the specific details, or other methods, components, devices, steps, etc. may be adopted. In other cases, known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0051] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the figures represent the same or similar parts, and their repeated description will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities can be implemented in software form, or implemented in one or more hardware modules or integrated circuits, or implemented in different networks and / or processor devices and / or microcontroller devices.

[0052] With the construction of 5G (5th Generation Mobile Communication Technology), network development has put forward higher requirements for mobile bearer bandwidth. Currently, when the standard Ethernet interface is used as a telecommunications network interface, there are the following problems: on the one hand, it does not support more flexible bandwidth granularity; on the other hand, it does not support the same interface to carry a variety of different services.

[0053] Based on this, this exemplary embodiment first provides a method for processing traffic data, which can be run on a local network device, etc. The local network device can be a routing device or a gateway device where the data sending end is located; of course, those skilled in the art can also run the method disclosed in this disclosure on other platforms as required, and this exemplary embodiment does not specifically limit this. Specifically, refer to Figure 1 As shown, the method for processing the flow data may include the following steps:

[0054] Step S110. Acquire the traffic data to be transmitted and the target program identifier of the target client that generates the traffic data to be transmitted;

[0055] Step S120. Matching a target timeslot and a target sub-timeslot corresponding to the target client in the flexible Ethernet group according to the target program identifier; wherein the target timeslot and the target sub-timeslot are configured according to the service category of the target client;

[0056] Step S130. Generate a traffic message to be transmitted according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot;

[0057] Step S140. Transmit the traffic message to be transmitted to the opposite network device based on the target time slot and the target sub-time slot, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and the target program identifier included in the traffic message to be transmitted.

[0058] In the above-mentioned method for processing traffic data, on the one hand, since the target time slot and the target sub-time slot corresponding to the target client can be matched in the flexible Ethernet group according to the target program identifier; then the traffic message to be transmitted is generated according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot; finally, the traffic message to be transmitted is transmitted to the opposite network device based on the target time slot and the target sub-time slot, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and the target program identifier included in the traffic message to be transmitted, thereby solving the problem in the prior art that the same interface is not supported to carry various different services, thereby improving the bandwidth utilization; on the other hand, since the target time slot and the target sub-time slot corresponding to the target client can be matched in the flexible Ethernet group according to the target program identifier, and the target time slot and the target sub-time slot are configured according to the service category of the target client, different target clients can use different target time slots and target sub-time slots, thereby realizing service isolation and improving service access efficiency.

[0059] Hereinafter, the method for processing traffic data according to the exemplary embodiment of the present disclosure will be explained and illustrated in detail with reference to the accompanying drawings.

[0060] First, the terms involved in the exemplary embodiments of the present disclosure are explained and illustrated.

[0061] FlexE group: Flexible Ethernet group, also known as a bundling group. The multiple PHYs (Physical, port physical layer) included in each FlexE group have a logical bundling relationship. The so-called logical bundling relationship means that there may be no physical connection relationship between different PHYs, so the multiple PHYs in the FlexE group can be physically independent. The network devices in FlexE can use the PHY number to identify which PHYs are included in a FlexE group to achieve logical bundling of multiple PHYs. For example, the number of each PHY can be identified by a number between 1 and 254, and 0 and 255 are reserved numbers. A PHY number can correspond to an interface on a network device. The same number must be used to identify the same PHY between two adjacent network devices. The numbers of the PHYs included in a FlexEgroup do not have to be continuous. Normally, there is a FlexE group between two network devices, but this application does not limit the existence of only one FlexE group between the two network devices, that is, there can also be multiple FlexE groups between the two network devices. A PHY can be used to carry at least one client, and a client can be transmitted on at least one PHY.

[0062] FlexE client: corresponds to various user interfaces or bandwidths of the network. FlexE client can be flexibly configured according to bandwidth requirements, and supports Ethernet MAC data streams of various rates (such as 10G, 40G, n*25G data streams, and even non-standard rate data streams). For example, the data stream can be passed to the FlexE shim layer through 64B / 66B encoding. Clients sent through the same FlexE group need to share the same clock, and these clients need to adapt according to the allocated time slot rate. The FlexE client interface described in this application is used to transmit the service data stream of the corresponding FlexE client. The FlexEclient interface is a logical interface. Each FlexE interface can be logically divided into one or more FlexEclient interfaces, each FlexE interface can be divided into multiple time slots in the time domain, and each FlexE client interface occupies at least one of the multiple time slots.

[0063] FlexE shim: As an additional logical layer inserted between the MAC and PHY (PCS sublayer) of the traditional Ethernet architecture, it is the core architecture for implementing FlexE technology based on the calendar-based time slot distribution mechanism. The main function of FlexE shim is to slice the data according to the same clock and encapsulate the sliced ​​data into pre-divided time slots. Then, according to the pre-configured time slot allocation table, the divided time slots are mapped to the PHY in the FlexE group for transmission. Among them, each time slot is mapped to a PHY in the FlexE group.

[0064] Calender: time slot allocation table, also known as time slot table. FlexE Group corresponds to calendar, and the time slot mapping table corresponding to a single physical link (PHY) included in a FlexE Group can be called a sub-time slot allocation table (English: sub-calendar). FlexE calendar can be composed of one or more sub-calendars. Each subcalendar can indicate how the 20 time slots (written as slots in English) on the single physical link are allocated to the corresponding FlexE client. In other words, each sub-calendar can indicate the correspondence between the time slots on the single physical link and the FlexE client. The current standard defines that two Calenders are specified in each FlexE overhead frame, namely the current main time slot table (Calender A) and the backup time slot table (Calender B).

[0065] FlexE constructs a fixed frame format for physical interface transmission and performs TDM time slot division. As mentioned above, the FlexEshim layer reflects the time slot mapping relationship between the client and the FlexE group and the calendar working mechanism by defining overhead frames and overhead multiframes. It should be noted that the above-mentioned overhead frame can also be called a flexible Ethernet overhead frame (English: FlexE overhead frame), and the above-mentioned overhead multiframe can also be called a flexible Ethernet overhead multiframe (English: FlexEoverhead Multiframe). The FlexE shim layer provides an in-band management channel through overhead, supports the transmission of configuration and management information between the two connected FlexE interfaces, and realizes the automatic negotiation and establishment of the link.

[0066] The data on each FlexE PHY is aligned by periodically inserting code blocks of the FlexE overhead frame (OH) frame, for example, one 66B overhead code block FlexE OH can be inserted every 1023x 20 66B payload data code blocks. According to the FlexE Implementation Agreement, a FlexE Group will send a 64B / 66B code block of a FlexE overhead frame to the remote PHY at a predetermined time interval on each PHY, and 8 64B / 66B code blocks of FlexE overhead frames sent in sequence constitute a FlexE overhead frame. FlexE defines some fields on the overhead frame to carry the time slot allocation table, and synchronizes the time slot allocation table to the PHY on the remote communication device through the FlexE overhead frame to ensure that the communication devices on both ends use the same time slot allocation table to receive and send the data stream corresponding to the FlexE customer.

[0067] Sub-timeslot: A sub-timeslot is also called a low-order time slot. Compared to the time slots (also called large time slots or high-order time slots) configured by the existing FlexE Client interface or the large bandwidth of the ordinary ETH interface. For a standard FlexE Client interface or an ordinary ETH interface, each FlexE Client interface or ETH interface is divided into M sub-time slots in the time domain, and each sub-user interface occupies at least one sub-time slot bandwidth for data transmission.

[0068] FlexE sub-shim, based on the sub-timeslot distribution mechanism, slices the data of the same sub-client and encapsulates the switched data as sub-timeslot payload in the pre-divided sub-timeslot. Then, according to the pre-acquired sub-client sub-timeslot mapping table, the divided sub-timeslots are mapped to the corresponding FlexE Client interface. Each sub-timeslot is mapped to a FlexE client interface.

[0069] Secondly, the application scenarios of the exemplary embodiments of the present disclosure are explained and illustrated. Specifically, Figure 2 The following is an example of a FlexE general architecture diagram based on the Flexible Ethernet protocol. Figure 2As shown, the FlexE Group includes 4 PHYs. FlexE Client represents the customer data stream transmitted in a specified time slot (one time slot or multiple time slots) on the FlexE Group. A FlexE Group can carry multiple FlexE Clients. A FlexE Client can correspond to one to multiple user service data streams (also called MAC Client). The FlexE Shim layer provides data adaptation and conversion from FlexE Client to MAC Client. FlexE can support the mapping and transmission of any number of different FlexE Clients on any group of PHYs, thereby realizing functions such as PHY bundling, channelization and sub-rate; multiple PHYs are combined into a FlexE Group (also called FlexE Group in English), which is used to carry one or more FlexE client data streams distributed and mapped through the FlexE Shim layer. Taking 100GE PHY as an example, the FlexE Shim layer can divide each 100GE PHY in the FlexE Group into a data bearer channel of 20 time slots, and the bandwidth corresponding to each slot is 5Gbps.

[0070] Figure 3 The schematic diagram schematically shows the time slot allocation of the FlexE Group across 4 physical link interfaces (aggregating 4 PHYs). Figure 3 As shown in the figure, each PHY has 20 time slots, so the FlexE Group has 20*4 time slots. Figure 3 As shown, Figure 2 Take the example that the FlexE Group includes 4 PHYs, which are PHYA1201, PHYB1202, PHYC1203 and PHYD1204. The FlexEGroup corresponds to the time slot allocation table (also called Calendar in English); the time slot mapping table corresponding to a single physical link included in a FlexEGroup can be called a sub-time slot allocation table (also called sub-calendar in English). The FlexE calendar can be composed of one or more sub-calendars. Each sub-calendar can indicate how the 20 time slots on the single physical link are allocated to the corresponding FlexE client. In other words, each sub-calendar can indicate the correspondence between the time slots on the single physical link and the FlexEclient. Figure 3 As shown, each PHY can correspond to 20 time slots, which are represented by slot 0 to slot 19 respectively in the figure. Figure 3Schematic diagrams showing 20 time slots corresponding to each of PHYs in PHYA 1201, PHY B 1202, PHY C 1203 and PHY D 1204 are shown respectively.

[0071] Figure 4 FIG. 1 shows a schematic diagram of an application scenario of the FlexE communication system involved in the present application. Figure 4 As shown, the FlexE communication system 400 includes a network device 1, a network device 2, a user device 1, and a user device 2. Network device 1 may be an intermediate node, in which case network device 1 is connected to user device 1 through other network devices. Network device 1 may be an edge node, in which case network device 1 is directly connected to user device 1. Network device 1 may be an intermediate node, in which case network device 1 is connected to user device 1 through other network devices. Network device 1 may also be an edge node, in which case network device 1 is directly connected to user device 1. Network device 2 may be an intermediate node, in which case network device 2 is connected to user device 2 through other network devices. Network device 2 may also be an edge node, in which case network device 2 is directly connected to user device 2. Network device 1 includes a FlexE interface 1, and network device 2 includes a FlexE interface 2. FlexE interface 1 is adjacent to FlexE interface 2. Each FlexE interface includes a sending port and a receiving port. The difference from a traditional Ethernet interface is that a FlexE interface can carry multiple Clients, and a FlexE interface as a logical interface can be composed of multiple physical interfaces. Figure 4 The flow of business data in the forward channel shown in Figure 4 As shown by the solid arrows, the flow of business data in the reverse channel is as follows Figure 4 The transmission channel of the embodiment of the present invention takes the forward channel as an example, and the flow direction of the service data in the transmission channel is user equipment 1→network equipment 1→network equipment 2→user equipment 2.

[0072] It should be understood that Figure 4 Only two network devices and two user devices are shown as an example. The network may include any other number of network devices and user devices, which is not limited in the embodiments of the present application. Figure 4 The FlexE communication system shown in the figure is only an example. The application scenarios of the FlexE communication system provided in this application are not limited to Figure 4 The technical solution provided in this application is applicable to all network scenarios where FlexE technology is used for data transmission.

[0073] Furthermore, the purpose of the invention of the example embodiment of the present disclosure is explained and illustrated. Specifically, in view of the problem that the current standard Ethernet interface does not support more flexible bandwidth granularity and does not support service isolation, the example embodiment of the present disclosure provides a flow data processing method based on time slot scheduling; in the flow data management method, it mainly includes the implementation of the group / client architecture and time slot scheduling; wherein, the group is mainly used to bundle the actual physical interface and build an ultra-large bandwidth interface; the client is mainly used to create a logical service port and realize service isolation; the time slot scheduling is mainly used for the time slot division of the physical interface in the group, the client bandwidth time slot configuration, and the service port traffic scheduling, so that the bandwidth utilization rate reaches 100%.

[0074] Furthermore, the method for allocating sub-time slots involved in the exemplary embodiment of the present disclosure is explained and illustrated. Figure 5 As shown, the sub-time slot allocation method may specifically include the following steps:

[0075] Step S510, building the flexible Ethernet group on the local network device, and binding one or more original physical flexible Ethernet interfaces to the flexible Ethernet group; wherein the flexible Ethernet group is an interface with a preset bandwidth; the bandwidth of the flexible Ethernet group is the sum of the bandwidths of all the original physical flexible Ethernet interfaces bound to the flexible Ethernet group;

[0076] Step S520, creating one or more original clients with original program identifiers, and associating each of the original clients with program identifiers into the flexible Ethernet group;

[0077] Step S530, allocating an original timeslot and an original sub-timeslot of the original physical flexible Ethernet interface to the original client according to the service category of the original client included in the flexible Ethernet group, and establishing a mapping relationship between the original timeslot and the original sub-timeslot and the original program identifier;

[0078] Step S540: configure a logical interface service corresponding to the original client in a logical interface included in the original physical flexible Ethernet interface allocated to the original client, and create an original logical sub-interface corresponding to the original client in the logical interface.

[0079] In an exemplary embodiment, the method for processing traffic data may further include: allocating original time slots to the original physical flexible Ethernet interface according to a time slot distribution mechanism included in a preset time slot allocator, and based on the time slot distribution mechanism, dividing the original time slot allocated to the original physical flexible Ethernet interface into multiple original sub-time slots; wherein the time slot granularity of the original physical flexible Ethernet interface is 5G, and the time slot granularity of the original sub-time slot is 1G.

[0080] The following will explain and illustrate steps S510 to S540. Figure 6 As shown, that is, in the specific application process, build a Client / Group architecture, design a command line, and through command line configuration, bundle multiple physical interfaces (that is, the original physical flexible Ethernet interface) into a Group (flexible Ethernet group) to work together, and treat the Group as an ultra-large bandwidth interface; at the same time, use the Slot distribution mechanism of the time slot allocator Calendar to divide the time slots for the physical interfaces bound in the Group according to the time slot granularity; in the specific application process, according to the service bandwidth requirements, you can directly configure the time slots of the physical interfaces in the Group for the Client, and then send interface-related services to the Client, and distribute the data streams to the physical ports based on time slot scheduling. Specifically, as Figure 6 As shown in the figure, multiple connected physical interfaces are added to the Group at both ends, and time slots are allocated to different clients.

[0081] In some example embodiments, reference Figure 7As shown in the figure, first, groups (flexible Ethernet groups) are created on the devices at both ends (the local network device and the remote network device) respectively, and the same group number (coding sequence number) is marked; wherein the coding sequence number may include G1 or G2, etc., which can be set according to actual needs, and this example does not impose any special restrictions on this; then, the interfaces (original physical flexible Ethernet interfaces) that physically connect the two devices are marked with the same phy number (interface serial number), and bundle the original physical flexible Ethernet interface into the group; wherein the group (flexible Ethernet group) can be regarded as an ultra-large bandwidth interface, and the bandwidth value is equal to the sum of the bandwidths of the original physical flexible Ethernet interfaces bound in the group; further, the original physical flexible Ethernet interface is allocated the original time slot according to the Slot (time slot) distribution mechanism of the slot allocator Calendar; wherein, by default, the time slot granularity of the original physical flexible Ethernet interface is 5G; for example, the interface time slot of 50GE (50Gbps) is 0-9, and the interface time slot of 100GE (100Gbps) is 0-19; further, the original time slot of each original physical flexible Ethernet interface is divided into 5 sub-time slots, and the sub-time slot granularity is 1G.

[0082] In some example embodiments, after obtaining the original time slot and the original sub-time slot, a client (original client) can be created at both ends of the local network device and the opposite network device respectively, and the client can be associated with the group according to the service category of the original client, and the corresponding logical interface can be allocated to the client (that is, a sub-logical interface can be allocated to the original client from the original physical flexible Ethernet interface). At the same time, the target client client to be communicated with on the local network device and the opposite network device respectively is marked with the same client_id (original program identifier), and then the original time slot and original sub-time slot of the physical interface in the group (flexible Ethernet group) are configured for the client; when the original time slot and the original sub-time slot are allocated, the client logical interface can be entered to configure the service of the interface; at the same time, a sub-interface of the client logical interface is created, the sub-interface is entered, and the service is configured.

[0083] exist Figure 5 In the method shown in, on the one hand, by bundling interfaces, ultra-large bandwidth can be achieved; on the other hand, by setting original time slots and original sub-time slots, bandwidth utilization can reach 100%; on the other hand, logical interfaces and sub-interfaces can be created according to the service categories of the original clients, so that different services can be isolated.

[0084] The following will be combined Figure 5-Figure 7 right Figure 1 The processing method of the traffic data shown in is explained and illustrated. Specifically:

[0085] In step S110, the traffic data to be transmitted and the target program identifier of the target client that generates the traffic data to be transmitted are obtained.

[0086] Specifically, the local network device can receive the traffic data to be transmitted sent by the client set on the local network device side, and then obtain the target program identifier of the target client that generates the traffic data to be transmitted included in the traffic data to be transmitted; wherein, the target client recorded here may include the client of an application, and the client of the application may include, for example, an instant chat program client, a shopping program client, a learning program client, a banking program client, an information sending program client, etc., and this example does not impose any special restrictions on this.

[0087] In step S120, a target timeslot and a target sub-timeslot corresponding to the target client are matched in a flexible Ethernet group according to the target program identifier; wherein the target timeslot and the target sub-timeslot are configured according to the service category of the target client.

[0088] In this example embodiment, after the target program identifier is obtained, the target time slot and target sub-time slot corresponding to the target client can be matched in the flexible Ethernet group according to the target program identifier. Specifically, it can be implemented in the following manner: based on the mapping relationship between the original time slot and the original sub-time slot and the original program identifier, the target time slot and target sub-time slot corresponding to the target client are matched in the flexible Ethernet group according to the target program identifier. It should be supplemented here that since the target time slot and the target sub-time slot are configured according to the service category of the target client, the target clients of the same service category can be allocated to the same target time slot and target sub-time slot, thereby avoiding the problem of low processing efficiency of data traffic due to excessive service traffic required by a certain service category and too small target time slot and target sub-time slot; at the same time, it can also avoid the problem of low bandwidth utilization due to small service traffic required by a certain service category and too large target time slot and target sub-time slot; that is, the method recorded in the example embodiment of the present disclosure, by allocating corresponding target time slots and target sub-time slots to the target client according to the service category, can improve service processing efficiency and bandwidth utilization on the basis of achieving service isolation.

[0089] In step S130, a traffic message to be transmitted is generated according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot.

[0090] Specifically, since the same flexible Ethernet group as that in the local network device is set in the opposite network device, in order to achieve the same purpose, when sending the traffic message to be transmitted to the opposite network device, it is necessary to carry the coding number of the flexible Ethernet group, the target program identifier of the target client, and the target time slot and target sub-time slot required by the target client.

[0091] In step S140, the traffic message to be transmitted is transmitted to the opposite network device based on the target time slot and the target sub-time slot, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and the target program identifier included in the traffic message to be transmitted.

[0092] In this example embodiment, first, the traffic message to be transmitted is transmitted to the opposite network device based on the target time slot and the target sub-time slot. Specifically, it can be achieved in the following manner: forwarding the traffic message to be transmitted to the target logical sub-interface based on the target time slot, and transmitting the traffic message to be transmitted to the opposite network device via the target logical sub-interface based on the target sub-time slot. Secondly, after the opposite network device receives the traffic message to be transmitted, the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and target program identifier included in the traffic message to be transmitted. Specifically, it can be achieved in the following way: first, the opposite network device obtains the target time slot and target sub-time slot included in the traffic message to be transmitted, and determines the target physical flexible Ethernet interface and target logical sub-interface corresponding to the target time slot and target sub-time slot according to the time slot scheduling rule; secondly, the opposite network device determines the flexible Ethernet group corresponding to the coding sequence number included in the traffic message to be transmitted based on the binding relationship between the flexible Ethernet group and the original physical flexible Ethernet interface; then, the opposite network device determines the target client in the flexible Ethernet group corresponding to the target program identifier included in the traffic message to be transmitted based on the mapping relationship between the original physical flexible Ethernet interface and the original program identifier, and transmits the traffic message to be transmitted to the target client.

[0093] In some example embodiments, reference Figure 8As shown, the traffic on the client (where client_id is c1) c1 located on the local network device side passes through the physical interface PHY1 or PHY2, and according to the time slot scheduling, first arrives at the time slot corresponding to PHY1 or PHY2 of the opposite network device, and then arrives at G1 according to the group number (encoding sequence number of the flexible Ethernet group) in the traffic message to be transmitted, and finally arrives at c1 (target client) according to the client_id (target program identifier).

[0094] It should be noted that in actual application, since both the local network device and the opposite network device are provided with flexible Ethernet groups, the flexible Ethernet groups provided may include one or more; therefore, when transmitting a message, firstly, according to the target time slot and target sub-time slot included in the data message to be transmitted, it is matched to the target time slot and target sub-time slot corresponding to the target physical flexible Ethernet interface (such as PHY1 or PHY2) on the opposite network device corresponding to the target time slot and target sub-time slot, and then the data message to be transmitted is processed through the target time slot and target sub-time slot on the opposite network device, so that the data message to be transmitted reaches the flexible Ethernet group G1 of the opposite network device, and then the subsequent processing process is implemented. Through this method, not only the bandwidth utilization rate of the local network device can be improved, but also the bandwidth utilization rate of the opposite network device can be improved.

[0095] It should be further explained here that, since the flexible Ethernet group is also configured with logical interface services and logical sub-interface services corresponding to the target client, in the specific application process, the received data message can be processed first based on the logical interface service, and then the corresponding logical sub-interface service can be allocated to it according to the sub-service content included in the data message, and then processed based on the logical sub-interface service; taking a shopping program client as an example, the logical sub-services can include purchase sub-services, collection sub-services or browsing sub-services, etc., and this example does not impose any special restrictions on this.

[0096] The exemplary embodiment of the present disclosure also provides a flow data processing device, which is configured in a local network device. Fig. 9 As shown, the flow data processing device may include a flow data acquisition module 910, a time slot matching module 920, a flow message generation module 930 and a flow message transmission module 940. Among them:

[0097] The traffic data acquisition module 910 may be used to acquire the traffic data to be transmitted and the target program identifier of the target client that generates the traffic data to be transmitted;

[0098] The time slot matching module 920 may be used to match the target time slot and the target sub-time slot corresponding to the target client in the flexible Ethernet group according to the target program identifier; wherein the target time slot and the target sub-time slot are configured according to the service category of the target client;

[0099] The traffic message generation module 930 may be used to generate a traffic message to be transmitted according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot;

[0100] The traffic message transmission module 940 can be used to transmit the traffic message to be transmitted to the opposite network device based on the target time slot and the target sub-time slot, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and the target program identifier included in the traffic message to be transmitted.

[0101] In an exemplary embodiment of the present disclosure, the flow data processing device further includes:

[0102] A flexible Ethernet group building module can be used to build the flexible Ethernet group on the local network device and bind one or more original physical flexible Ethernet interfaces into the flexible Ethernet group;

[0103] The original client association module may be used to create one or more original clients with original program identifiers, and associate each of the original clients with program identifiers with the flexible Ethernet group;

[0104] A first time slot allocation module may be used to allocate an original time slot and an original sub-time slot of the original physical flexible Ethernet interface to the original client according to the service category of the original client included in the flexible Ethernet group, and establish a mapping relationship between the original time slot and the original sub-time slot and the original program identifier;

[0105] The logical interface service configuration module can be used to configure the logical interface service corresponding to the original client in the logical interface included in the original physical flexible Ethernet interface allocated to the original client, and create an original logical sub-interface corresponding to the original client in the logical interface.

[0106] In an exemplary embodiment of the present disclosure, the flow data processing device further includes:

[0107] The second time slot allocation module can be used to allocate original time slots to the original physical flexible Ethernet interface according to the time slot distribution mechanism included in the preset time slot allocator, and based on the time slot distribution mechanism, divide the original time slot allocated to the original physical flexible Ethernet interface into multiple original sub-time slots; wherein the time slot granularity of the original physical flexible Ethernet interface is 5G, and the time slot granularity of the original sub-time slot is 1G.

[0108] In an exemplary embodiment of the present disclosure, the flexible Ethernet group is an interface with a preset bandwidth;

[0109] The bandwidth of the flexible Ethernet group is the sum of the bandwidths of all original physical flexible Ethernet interfaces bound in the flexible Ethernet group.

[0110] In an exemplary embodiment of the present disclosure, matching a target timeslot and a target sub-timeslot corresponding to the target client in a flexible Ethernet group according to the target program identifier includes:

[0111] Based on the mapping relationship between the original timeslot and the original sub-timeslot and the original program identifier, a target timeslot and a target sub-timeslot corresponding to the target client are matched in the flexible Ethernet group according to the target program identifier.

[0112] In an exemplary embodiment of the present disclosure, transmitting the to-be-transmitted traffic message to the opposite network device based on the target time slot and the target sub-time slot includes:

[0113] The traffic message to be transmitted is forwarded to the target logical sub-interface based on the target time slot, and the traffic message to be transmitted is transmitted to the opposite network device via the target logical sub-interface based on the target sub-time slot.

[0114] In an exemplary embodiment of the present disclosure, the peer network device forwards the to-be-transmitted traffic data to the target client where the peer network device is located according to the coding sequence number and the target program identifier included in the to-be-transmitted traffic message, including:

[0115] The opposite network device obtains the target time slot and the target sub-time slot included in the traffic message to be transmitted, and determines the target physical flexible Ethernet interface and the target logical sub-interface corresponding to the target time slot and the target sub-time slot according to the time slot scheduling rule;

[0116] The opposite network device determines, based on the binding relationship between the flexible Ethernet group and the original physical flexible Ethernet interface, the flexible Ethernet group corresponding to the coding sequence number included in the traffic message to be transmitted;

[0117] The opposite network device determines the target client corresponding to the target program identifier included in the traffic message to be transmitted in the flexible Ethernet group based on the mapping relationship between the original physical flexible Ethernet interface and the original program identifier, and transmits the traffic message to be transmitted to the target client.

[0118] The specific details of each module in the above-mentioned flow data processing device have been described in detail in the corresponding flow data processing method, so they will not be repeated here.

[0119] It should be noted that, although several modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. On the contrary, the features and functions of one module or unit described above can be further divided into multiple modules or units to be embodied.

[0120] In addition, although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that the steps must be performed in this specific order, or that all the steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps, etc.

[0121] In an exemplary embodiment of the present disclosure, an electronic device capable of implementing the above method is also provided.

[0122] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods or program products. Therefore, various aspects of the present disclosure may be specifically implemented in the following forms, namely: complete hardware implementation, complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software, which may be collectively referred to herein as "circuits", "modules" or "systems".

[0123] Refer to the following Fig.10 The electronic device 1000 according to this embodiment of the present disclosure is described. Fig.10 The electronic device 1000 shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0124] like Fig.10As shown, the electronic device 1000 is in the form of a general computing device. The components of the electronic device 1000 may include, but are not limited to: the at least one processing unit 1010, the at least one storage unit 1020, a bus 1030 connecting different system components (including the storage unit 1020 and the processing unit 1010), and a display unit 1040.

[0125] The storage unit stores program codes, which can be executed by the processing unit 1010, so that the processing unit 1010 performs the steps according to various exemplary embodiments of the present disclosure described in the above “Exemplary Method” section of this specification. For example, the processing unit 1010 can perform the following steps: Figure 1 Step S110 shown in: obtaining the traffic data to be transmitted and the target program identifier of the target client that generates the traffic data to be transmitted; step S120: matching the target time slot and target sub-time slot corresponding to the target client in the flexible Ethernet group according to the target program identifier; wherein the target time slot and target sub-time slot are configured according to the service category of the target client; step S130: generating a traffic message to be transmitted according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot; step S140: transmitting the traffic message to be transmitted to the opposite network device based on the target time slot and the target sub-time slot, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and the target program identifier included in the traffic message to be transmitted.

[0126] The storage unit 1020 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 10201 and / or a cache storage unit 10202 , and may further include a read-only storage unit (ROM) 10203 .

[0127] The storage unit 1020 may also include a program / utility 10204 having a set (at least one) of program modules 10205, such program modules 10205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0128] Bus 1030 may represent one or more of several types of bus structures, including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0129] The electronic device 1000 may also communicate with one or more external devices 1100 (e.g., keyboards, pointing devices, Bluetooth devices, etc.), may also communicate with one or more devices that enable a user to interact with the electronic device 1000, and / or may communicate with any device that enables the electronic device 1000 to communicate with one or more other computing devices (e.g., routers, modems, etc.). Such communication may be performed via an input / output (I / O) interface 1050. Furthermore, the electronic device 1000 may also communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) via a network adapter 1060. As shown, the network adapter 1060 communicates with other modules of the electronic device 1000 via a bus 1030. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1000, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0130] Through the description of the above implementation, it is easy for those skilled in the art to understand that the example implementation described here can be implemented by software, or by software combined with necessary hardware. Therefore, the technical solution according to the implementation of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the implementation of the present disclosure.

[0131] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of the present specification is stored. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes a program code, and when the program product is run on a terminal device, the program code is used to enable the terminal device to execute the steps according to various exemplary implementations of the present disclosure described in the above "Exemplary Method" section of the present specification.

[0132] According to the program product for implementing the above method in the embodiment of the present disclosure, it can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of the present disclosure is not limited thereto. In this document, a readable storage medium can be any tangible medium containing or storing a program, which can be used by or in combination with an instruction execution system, an apparatus or a device.

[0133] The program product may use any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of readable storage media include: an electrical connection with one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0134] Computer readable signal media may include data signals propagated in baseband or as part of a carrier wave, in which readable program code is carried. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Readable signal media may also be any readable medium other than a readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0135] The program code embodied on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.

[0136] Program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, etc., and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user computing device, partially on the user device, as a separate software package, partially on the user computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device may be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0137] In addition, the above-mentioned figures are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present disclosure, and are not intended to be limiting. It is easy to understand that the processes shown in the above-mentioned figures do not indicate or limit the time sequence of these processes. In addition, it is also easy to understand that these processes can be performed synchronously or asynchronously, for example, in multiple modules.

[0138] Other embodiments of the present disclosure will be readily apparent to those skilled in the art after considering the specification and practicing the inventions invented herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not invented by the present disclosure. The specification and examples are to be considered merely exemplary, and the true scope and spirit of the present disclosure are indicated by the claims.

Claims

1. A method for processing flow data, characterized in that: Configured on the local network device, the method for processing the traffic data includes: Acquire the traffic data to be transmitted and the target program identifier of the target client that generates the traffic data to be transmitted; Based on the mapping relationship between the original time slot and the original sub-time slot and the original program identifier, matching the target time slot and the target sub-time slot corresponding to the target client in the flexible Ethernet group according to the target program identifier; wherein the target time slot and the target sub-time slot are configured according to the service category of the target client; Generate a traffic message to be transmitted according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot; Based on the target time slot, the traffic message to be transmitted is forwarded to the target logical sub-interface, and based on the target sub-time slot, the traffic message to be transmitted is transmitted to the opposite network device via the target logical sub-interface, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and target program identifier included in the traffic message to be transmitted.

2. The method for processing flow data according to claim 1, characterized in that: The method for processing flow data further includes: Building the flexible Ethernet group on the local network device, and binding one or more original physical flexible Ethernet interfaces into the flexible Ethernet group; Creating one or more original clients with original program identifiers, and associating each of the original clients with the original program identifiers into the flexible Ethernet group; According to the service category of the original client included in the flexible Ethernet group, the original timeslot and the original sub-timeslot of the original physical flexible Ethernet interface are allocated to the original client, and a mapping relationship between the original timeslot and the original sub-timeslot and the original program identifier is established; A logical interface service corresponding to the original client is configured in a logical interface included in an original physical flexible Ethernet interface allocated to the original client, and an original logical sub-interface corresponding to the original client is created in the logical interface.

3. The method for processing flow data according to claim 2, characterized in that: The method for processing flow data further includes: According to the time slot distribution mechanism included in the preset time slot allocator, the original time slot is allocated to the original physical flexible Ethernet interface, and based on the time slot distribution mechanism, the original time slot allocated to the original physical flexible Ethernet interface is divided into multiple original sub-time slots; wherein the time slot granularity of the original physical flexible Ethernet interface is 5G, and the time slot granularity of the original sub-time slot is 1G.

4. The method for processing flow data according to claim 2 or 3, characterized in that: The flexible Ethernet group is an interface with a preset bandwidth; The bandwidth of the flexible Ethernet group is the sum of the bandwidths of all original physical flexible Ethernet interfaces bound in the flexible Ethernet group.

5. The method for processing flow data according to claim 1, characterized in that: The peer network device forwards the to-be-transmitted traffic data to the target client where the peer network device is located according to the coding sequence number and the target program identifier included in the to-be-transmitted traffic message, including: The opposite network device obtains the target time slot and the target sub-time slot included in the traffic message to be transmitted, and determines the target physical flexible Ethernet interface and the target logical sub-interface corresponding to the target time slot and the target sub-time slot according to the time slot scheduling rule; The opposite network device determines, based on the binding relationship between the flexible Ethernet group and the original physical flexible Ethernet interface, the flexible Ethernet group corresponding to the coding sequence number included in the traffic message to be transmitted; The opposite network device determines the target client corresponding to the target program identifier included in the traffic message to be transmitted in the flexible Ethernet group based on the mapping relationship between the original physical flexible Ethernet interface and the original program identifier, and transmits the traffic message to be transmitted to the target client.

6. A flow data processing device, characterized in that: Configured in the local network device, the flow data processing device includes: A flow data acquisition module, used to acquire the flow data to be transmitted and the target program identifier of the target client that generates the flow data to be transmitted; A time slot matching module, configured to match a target time slot and a target sub-time slot corresponding to the target client in a flexible Ethernet group according to the target program identifier based on a mapping relationship between the original time slot and the original sub-time slot and the original program identifier; wherein the target time slot and the target sub-time slot are configured according to the service category of the target client; A traffic message generation module, used for generating a traffic message to be transmitted according to the traffic data to be transmitted, the coding sequence number of the flexible Ethernet group, the target program identifier, the target time slot and the target sub-time slot; A traffic message transmission module is used to forward the traffic message to be transmitted to the target logical sub-interface based on the target time slot, and based on the target sub-time slot, transmit the traffic message to be transmitted to the opposite network device via the target logical sub-interface, so that the opposite network device forwards the traffic data to be transmitted to the target client where the opposite network device is located according to the coding sequence number and target program identifier included in the traffic message to be transmitted.

7. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for processing flow data according to any one of claims 1 to 5 is implemented.

8. An electronic device, characterized in that: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the method for processing traffic data according to any one of claims 1 to 5 by executing the executable instructions.

Images