Data processing system, method and equipment and storage medium

Abstract

The invention provides a data processing system, method and device and a storage medium. The data processing system comprises a software defined network controller, a slow forwarding network element and a fast forwarding network element. The software defined network controller is used for issuing a service instance created by a user to the slow forwarding network element, and issuing network element control information to the slow forwarding network element and the fast forwarding network element; and the fast forwarding network element is used for sending the data message to the slow forwarding network element when the data message is received and the target flow table corresponding to the data message cannot be queried in the network element control information, so that the slow forwarding network element generates the target flow table corresponding to the data message according to the service logic in the service instance and issues the target flow table to the fast forwarding network element. Namely, in the embodiment of the invention, the SDN controller only performs configuration issuing and does not process the data reporting request of the forwarding network element any more, and the fast forwarding network element and the slow forwarding network element are formed by setting the virtual machine to realize fast forwarding and slow forwarding of data forwarding, so that the data forwarding efficiency and the overall performance of the system are improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of network communication technology, and in particular, to a data processing system, method, device and storage medium. Background Art

[0002] In the field of network communication technology, SDN technology implements fast forwarding by forwarding network elements, which is a stateless network element and can be called a fast forwarding plane. When the fast forwarding plane cannot find the flow table, it will be sent to the SDN controller. At this time, the SDN controller will determine how to process the message according to the business logic and then send it down for processing.

[0003] However, since the SDN controller does not perform session management, it will perform service processing from the beginning when processing packets, which will cause exceptions in some service scenarios, such as load balancing and NAT. Summary of the invention

[0004] Embodiments of the present application provide a data processing system, method, device, and storage medium.

[0005] In a first aspect, an embodiment of the present application provides a data processing system, the data processing system comprising: a software defined network controller, a slow-transfer network element and a fast-transfer network element, the software defined network controller being communicatively connected to the slow-transfer network element and the fast-transfer network element respectively;

[0006] The software defined network controller is used to send the service instance created by the user to the slow-transfer network element, and send network element control information to the slow-transfer network element and the fast-transfer network element;

[0007] The fast-forwarding network element is used to send the data packet to the slow-forwarding network element when it receives a data packet and the target flow table corresponding to the data packet cannot be found in the network element control information of the fast-forwarding network element, so that the slow-forwarding network element generates the target flow table corresponding to the data packet according to the business logic in the business instance, and sends the target flow table to the fast-forwarding network element.

[0008] Optionally, the fast-forwarding network element includes a plurality of first virtual machines, and the traffic of processing the data message is evenly divided among the plurality of first virtual machines.

[0009] Optionally, the slow-forwarding network element includes a plurality of second virtual machines, and flow table session information is synchronized between the plurality of second virtual machines.

[0010] Optionally, the fast-forwarding network element is also used to process forward messages and return messages of data flows of different service instances corresponding to the same user through the same processor core in the fast-forwarding network element, wherein the transmission directions of the data flows between the forward messages and the return messages are opposite.

[0011] Optionally, the fast-forwarding network element is further configured to process the data packet according to the target flow table when receiving the data packet and querying the target flow table.

[0012] Optionally, a port mapping mechanism and a flow marking mechanism are provided on the first virtual machine and the second virtual machine;

[0013] The first virtual machine and the second virtual machine schedule the forward messages and return messages of the data flows of different service instances corresponding to the same user to the same fast-forwarding network element and the slow-forwarding network element through the port mapping mechanism and the flow labeling mechanism.

[0014] Optionally, the data stream processing system includes a message analysis server;

[0015] The message analysis server is used to receive the data message processed by the slow-transfer network element through the configurable multi-tuple, perform message analysis on the data message, obtain the message flow stickiness feature, and report the message flow stickiness feature to the software-defined network controller, so that the software-defined network controller sends the message flow stickiness feature to the slow-transfer network element.

[0016] In a second aspect, an embodiment of the present application provides a data processing method, which is applied to a fast-forwarding network element in the data processing system, and the method includes:

[0017] When a data message is received and the target flow table corresponding to the data message cannot be found in the network element control information of the fast-forwarding network element, the data message is sent to the slow-forwarding network element so that the slow-forwarding network element generates the target flow table corresponding to the data message according to the service logic in the service instance, and sends the target flow table to the fast-forwarding network element;

[0018] Among them, the business instance is sent by the software-defined network controller to the slow-transfer network element, and the network element control information is sent by the software-defined network controller to the slow-transfer network element and the fast-transfer network element, and the software-defined network controller is communicated with the slow-transfer network element and the fast-transfer network element respectively.

[0019] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor; and a memory for storing instructions executable by the processor, wherein the processor is configured to execute the instructions to implement any of the data processing methods described above.

[0020] In a fourth aspect, an embodiment of the present application further provides a storage medium, which, when instructions in the storage medium are executed by a processor of an electronic device, enables the electronic device to execute any of the data processing methods described above.

[0021] In an embodiment of the present application, the data processing system includes: a software-defined network controller, a slow-transfer network element and a fast-transfer network element, the software-defined network controller being communicatively connected to the slow-transfer network element and the fast-transfer network element respectively; the software-defined network controller being used to send a service instance created by a user to the slow-transfer network element, and to send network element control information to the slow-transfer network element and the fast-transfer network element; the fast-transfer network element being used to send the data packet to the slow-transfer network element when a data packet is received and a target flow table corresponding to the data packet cannot be found in the network element control information of the fast-transfer network element, so that the slow-transfer network element generates the target flow table corresponding to the data packet according to the service logic in the service instance, and sends the target flow table to the fast-transfer network element. That is, in the embodiment of the present application, the SDN controller only issues configurations and no longer processes data reporting requests from forwarding network elements. Fast forwarding and slow forwarding of data forwarding are achieved by setting up virtual machines to form fast-forwarding network elements and slow-forwarding network elements. If the fast-forwarding network element cannot find the flow table, it will send the message to the slow-forwarding network element. The slow-forwarding network element implements complex business logic and then sends the flow table rules to the fast-forwarding network element. Subsequent data messages do not need to be processed by the slow-forwarding network element. That is, in the embodiment of the present application, by setting up virtual machines to form fast-forwarding network elements and slow-forwarding network elements, fast forwarding and slow forwarding of data forwarding are achieved. The SDN controller is only responsible for configuration issuance and no longer processes data reporting requests from forwarding network elements, thereby simplifying the functions of the controller. After receiving the data message, if the fast-forwarding network element cannot find the corresponding target flow table in the local flow table, it will send the message to the slow-forwarding network element. The slow-forwarding network element generates the target flow table according to the business logic in the business instance and sends it to the fast-forwarding network element. Subsequent data messages do not need to be processed by the slow-forwarding network element, thereby improving the efficiency of data forwarding and the overall performance of the system. This architectural design not only reduces reporting traffic, lowers latency and jitter, but also improves the scalability and flexibility of the system.

[0022] The above description is only an overview of the technical solution of the present application. In order to more clearly understand the technical means of the present application, it can be implemented in accordance with the contents of the specification. In order to make the above and other purposes, features and advantages of the present application more obvious and easy to understand, the specific implementation methods of the present application are listed below. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Various other advantages and benefits will become apparent to those of ordinary skill in the art by reading the detailed description of the preferred embodiments below. The accompanying drawings are only for the purpose of illustrating the preferred embodiments and are not to be considered as limiting the present application. Also, the same reference symbols are used throughout the accompanying drawings to represent the same components. In the accompanying drawings:

[0024] Figure 1 is a schematic diagram of a data processing system provided in an embodiment of the present application;

[0025] Figure 2 is a flowchart of a data processing method provided by an embodiment of the present application;

[0026] Figure 3 is a structural diagram of an electronic device provided in an embodiment of the present application;

[0027] Figure 4 It is a schematic diagram of an exemplary data processing system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0028] The exemplary embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although the exemplary embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein. On the contrary, these embodiments are provided in order to enable a more thorough understanding of the present application and to fully convey the scope of the present application to those skilled in the art.

[0029] Figure 1 is a schematic diagram of a data processing system provided by an embodiment of the present application, the data processing system comprising: a software defined network controller, a fast-forwarding network element and a slow-forwarding network element, the software defined network controller being communicatively connected with the slow-forwarding network element and the fast-forwarding network element respectively;

[0030] The software defined network controller is used to send the service instance created by the user to the slow-transfer network element, and send network element control information to the slow-transfer network element and the fast-transfer network element;

[0031] The fast-forwarding network element is used to send the data packet to the slow-forwarding network element when it receives a data packet and the target flow table corresponding to the data packet cannot be found in the network element control information of the fast-forwarding network element, so that the slow-forwarding network element generates the target flow table corresponding to the data packet according to the business logic in the business instance, and sends the target flow table to the fast-forwarding network element.

[0032] It should be noted that the software-defined network controller is responsible for sending the service instances and network element control information created by the user to the slow-transfer network element and the fast-transfer network element respectively. After receiving the data message, if the fast-transfer network element cannot find the corresponding target flow table in the local network element control information, it will send the message to the slow-transfer network element. The slow-transfer network element generates the target flow table according to the business logic in the service instance and sends it to the fast-transfer network element so that subsequent data messages can be processed quickly.

[0033] Among them, the software-defined network controller is the SDN controller. SDN (Software Defined Network) is a technology that centrally manages programmable switches through software controllers to achieve flexible forwarding of network traffic.

[0034] Therefore, in the embodiment of the present application, the SDN controller sends the service instance created by the user to the slow-transfer network element, and sends the network element control information to the fast-transfer network element and the slow-transfer network element, that is, the SDN controller only sends the configuration and no longer processes the data reporting request of the forwarding network element.

[0035] Specifically, the SDN controller is responsible for delivering user-created service instances (such as virtual networks, security policies, QoS policies, etc.) to slow-moving network elements. Slow-moving network elements usually handle complex service logic and state management, so these service instances are needed to perform corresponding operations.

[0036] The SDN controller is also responsible for sending network element control information (such as flow table rules, routing policies, policy configurations, etc.) to fast-forwarding network elements and slow-forwarding network elements. These control information instructs network elements on how to handle network traffic.

[0037] The SDN controller is only responsible for configuration delivery and no longer processes data reporting requests from forwarding network elements. This means that after fast-forwarding network elements and slow-forwarding network elements process traffic, they no longer report data to the SDN controller. This design simplifies the controller's functions, allowing it to focus on configuration management without having to handle complex real-time data reporting.

[0038] It should be noted that the Fast Path Network Element needs to receive messages before it can process them. The main task of the Fast Path Network Element is to quickly process network traffic and perform the "parse-query-execute" pipeline operation. The Fast Path Network Element first needs to receive messages from the network interface. These messages may come from network devices or terminals of different users, including data packets, frames, etc. The process of receiving messages usually involves the processing of the network interface card (NIC) or smart network card (SmartNIC).

[0039] After receiving the message, the fast forwarding network element needs to parse the message. The purpose of parsing is to extract key information in the message, such as source IP address, destination IP address, protocol type, port number, etc. This information will be used for subsequent flow table query and forwarding decision.

[0040] After parsing the message, the fast-forwarding network element will query the flow table sent by the slow-forwarding device after the service processing is completed to determine how to process the message. The flow table contains predefined formats, and these rules guide the fast-forwarding network element on how to forward the message. If the corresponding flow table rules are queried, the fast-forwarding network element will forward according to the rules.

[0041] Therefore, in the embodiment of the present application, if the fast-forwarding network element cannot query the flow table, it will report the message to the slow-path network element for further processing. The slow-path network element usually handles complex business logic and state management, and can process messages that the fast-path network element cannot process.

[0042] Furthermore, the fast-forwarding network element includes a plurality of first virtual machines, and the traffic of processing the data message is evenly distributed among the plurality of first virtual machines.

[0043] It should be noted that Figure 1 In the fast-forwarding network element, several first virtual machines are included, and a cluster is formed by multiple virtual machines, and each virtual machine has an equal status.

[0044] Among them, it is mainly responsible for network traffic access and forwarding, executing the "analysis-query-execution" pipeline, forwarding according to the flow table when the flow table is queried, and reporting the traffic to the slow-transfer network element if the flow table rules cannot be found. The fast-transfer network element does not perceive the service status, has simple logic, and can be unloaded using intelligent devices such as smart network cards, DPUs, and IPUs.

[0045] Furthermore, the slow-forwarding network element includes a plurality of second virtual machines, and flow table session information between the plurality of second virtual machines is synchronized.

[0046] It should be noted that Figure 1 In the slow-transfer network element, there are several second virtual machines, which will synchronize messages with each other. For example, if the LB application allocates a port IP to one of them, then this virtual machine will be shared with the other two. It should be noted that this application does not limit the specific number of virtual machines and can be configured according to the actual scenario.

[0047] In addition, in the embodiment of the present application, multiple groups of slow-turning network elements can also be set to address problems such as performance bottlenecks of slow-turning devices and limitations on the number of service ports. Multiple slow-turning devices in each group are synchronized, and the devices between groups have equal status.

[0048] Furthermore, the fast-forwarding network element is also used to process forward messages and return messages of data flows of different service instances corresponding to the same user through the same processor core in the fast-forwarding network element, wherein the transmission directions of the data flows between the forward messages and the return messages are opposite.

[0049] It should be noted that data flow is a logical concept. In the TCP / IP field, it generally refers to the same five-tuple (source / destination IP, source / destination port and protocol). For example, when a web page is visited on a computer, it is a flow. Before the visit ends, this five-tuple generally does not change.

[0050] It should be noted that in the embodiment of the present application, the fast-forwarding network element uses a self-learning intelligent redirection mechanism to map the processing of forward and return messages of the same flow to the same CPU core of the network element, thereby realizing the CPU affinity characteristics of data message processing and ensuring the maximization of the network element forwarding performance.

[0051] Among them, data messages can be divided into forward messages and return messages. The transmission directions of the data flow between the forward message and the return message are opposite. The forward message refers to from the sending end to the receiving end, and the return message refers to from the receiving end to the sending end.

[0052] The virtual machine includes a CPU core. Therefore, in order to maximize the performance of the network element in processing data packets in the data flow, the present application ensures that the data flows of different service instances corresponding to the same user are processed by the same CPU core in a virtual machine, so that the data packets going back and forth can use the same cache and can share transmission data, etc.

[0053] Furthermore, the fast-forwarding network element is further configured to process the data packet according to the target flow table when receiving the data packet and searching the target flow table.

[0054] Furthermore, a port mapping mechanism and a flow marking mechanism are provided on the first virtual machine and the second virtual machine;

[0055] The first virtual machine and the second virtual machine schedule the forward messages and return messages of the data flows of different service instances corresponding to the same user to the same fast-forwarding network element and the slow-forwarding network element through the port mapping mechanism and the flow labeling mechanism.

[0056] It should be noted that in the embodiment of the present application, the overlay network of the first virtual machine and the second virtual machine in the fast-transfer network element and the slow-transfer network element uses port mapping mechanism, flow labeling and other mechanisms to ensure that the forward and return messages of the same flow are scheduled to the same fast-transfer network element and the slow-transfer network element to the maximum extent when undergoing ECMP scheduling, thereby reducing reporting and reducing network message delay and jitter.

[0057] That is, in the Overlay network, through mechanisms such as port mapping and flow labeling, it can be ensured that the forward and return messages of the same flow are scheduled to the same Fast Path Network Element and Slow Path Network Element as much as possible when scheduling through Equal-Cost Multi-Path (ECMP). This mechanism helps to reduce the reported traffic and reduce network message delay and jitter.

[0058] Among them, the Overlay network is a virtual network built on top of the existing network infrastructure. It encapsulates the traffic of the virtual network on the underlying physical network through tunneling technology (such as VXLAN, GRE, etc.), achieving isolation and flexibility of the virtual network.

[0059] Port mapping is a mechanism that maps the ports of a virtual network to the ports of the underlying physical network. Through port mapping, the Overlay network can ensure that the traffic of the virtual network is correctly forwarded in the underlying physical network.

[0060] Flow Tagging is a mechanism that adds identifiers to packets to identify specific flows. Flow tagging can be based on information such as source IP address, destination IP address, protocol type, port number, etc. Through flow tagging, the Overlay network can identify the forward and return packets of the same flow during ECMP scheduling.

[0061] ECMP scheduling is a mechanism to balance traffic among multiple equal-cost paths. ECMP scheduling is usually based on a hash algorithm, which calculates the hash value based on the key information of the message (such as source IP address, destination IP address, protocol type, port number, etc.) and distributes the traffic to different paths.

[0062] Therefore, in the embodiment of the present application, during ECMP scheduling, the Overlay network calculates the hash value based on the flow marking information and schedules the forward and return messages of the same flow to the same network element. The specific steps are as follows:

[0063] The overlay network receives the message; the overlay network adds flow labeling information to the message; the overlay network calculates the hash value based on the flow labeling information, and schedules the forward and return messages of the same flow to the same network element; the fast-forward network element and the slow-forward network element receive the scheduled message and perform corresponding processing.

[0064] In summary, in the embodiments of the present application, by ensuring that the forward and return messages of the same flow are scheduled to the same network element, the Overlay network can reduce the reporting traffic. After the fast-forwarding network element queries the matching rule in the local flow table, it can directly forward it without reporting it to the slow-forwarding network element again. By reducing the reporting traffic, the Overlay network can reduce the delay of network messages. After the fast-forwarding network element queries the matching rule in the local flow table, it can directly forward it, reducing the additional processing time. By ensuring that the forward and return messages of the same flow are scheduled to the same network element, the Overlay network can reduce the jitter of network messages. The forward and return messages of the same flow are processed on the same network element, which reduces the changes in the network path and thus reduces jitter.

[0065] Furthermore, the data stream processing system includes a message analysis server;

[0066] The message analysis server is used to receive the data message processed by the slow-transfer network element through the configurable multi-tuple, perform message analysis on the data message, obtain the message flow stickiness feature, and report the message flow stickiness feature to the software-defined network controller, so that the software-defined network controller sends the message flow stickiness feature to the slow-transfer network element.

[0067] It should be noted that, in the embodiment of the present application, the SDN controller is responsible for delivering the service characteristics of the flow stickiness feature to the slow-transfer network element, and supports the user to configure the flow stickiness feature from the console;

[0068] The slow-transfer network element implements service scheduling based on configurable multi-tuples, and when processing data packets, it splits the packets to the packet analysis service system for packet analysis;

[0069] The packet analysis service system learns the flow viscosity characteristics based on packet detection and big data, and reports the learned characteristics to the SDN controller;

[0070] The SDN controller sends the learned flow viscosity feature rules to the slow-moving network elements, which are ultimately used for service scheduling.

[0071] In addition, in an embodiment of the present application, the fast-forwarding network element senses the connection status, sends connection control messages (SYNC, ACK, RST, FIN, etc.), and the slow-forwarding network element receives and sends them to complete session management (aging, etc.); the fast-forwarding network element intelligently reports the last active time of the flow (based on load, network congestion, etc.), and the slow-forwarding network element updates the session keep-alive time or ages the flow table.

[0072] The slow-forwarding network element cluster uses multicast or chain packet transmission technology to achieve session synchronization. For the flow that has established a connection, whether fast-forwarding or slow-forwarding is restarted or switched (that is, the same flow goes to another network element with the same function); the processing result of the flow will be consistent with the previous one, and no abnormal processing such as rescheduling will occur.

[0073] Reference Figure 4 , the data flow of data packet 1 reports slow speed, triggering service scheduling, and the subsequent data packet 2 is forwarded only on the fast path. When one of the fast network elements corresponding to the fast path goes down or other reasons trigger ECMP to reschedule traffic to another fast-forwarding network element, the newly scheduled fast-forwarding network element reports slow speed ( Figure 4 The data flow corresponding to the data packet 3 in the data packet is slowly queried and sent (without triggering service rescheduling) the flow table to the newly scheduled fast network element. The fast network element can then directly query the flow table entry and forward it.

[0074] In an embodiment of the present application, the embodiment of the present application realizes fast forwarding and slow forwarding of data forwarding by setting up virtual machines to form fast-forwarding network elements and slow-forwarding network elements. The SDN controller is only responsible for configuration delivery and no longer processes data reporting requests from forwarding network elements, thereby simplifying the functions of the controller. After receiving a data packet, if the fast-forwarding network element cannot find the corresponding target flow table in the local flow table, the packet is sent to the slow-forwarding network element. The slow-forwarding network element generates a target flow table according to the business logic in the business instance and sends it to the fast-forwarding network element. Subsequent data packets no longer need to be processed by the slow-forwarding network element, thereby improving the efficiency of data forwarding and the overall performance of the system. This architectural design not only reduces reporting traffic, reduces latency and jitter, but also improves the scalability and flexibility of the system.

[0075] In addition, the embodiments of the present application are based on SDN and NFV technologies, and realize fast forwarding and slow forwarding of data forwarding through virtual machines, and realize configurable business processing logic based on flow stickiness (optional multi-group), to ensure that dependent services are scheduled to the same back-end server for processing, and through intelligent message redirection technology, to ensure the affinity characteristics of the forward and return messages of the business logic to be processed on the same CPU of the same fast-forward network element.

[0076] Figure 2 is a flowchart of a data processing method provided by an embodiment of the present application, such as Figure 2 As shown, the method is applied to the fast-forwarding network element in the data processing system, and includes:

[0077] Step 101, when a data message is received and a target flow table corresponding to the data message cannot be found in the network element control information of the fast-forwarding network element, the data message is sent to the slow-forwarding network element, so that the slow-forwarding network element generates the target flow table corresponding to the data message according to the service logic in the service instance, and sends the target flow table to the fast-forwarding network element;

[0078] Among them, the business instance is sent by the software-defined network controller to the slow-transfer network element, and the network element control information is sent by the software-defined network controller to the slow-transfer network element and the fast-transfer network element, and the software-defined network controller is communicated with the slow-transfer network element and the fast-transfer network element respectively.

[0079] It should be noted that in the embodiment of the present application, a fast-forwarding network element is applied to a data processing system, and reference is made to the foregoing description, which will not be repeated here.

[0080] In an embodiment of the present application, fast forwarding and slow forwarding of data forwarding are achieved by setting up virtual machines to form fast-forwarding network elements and slow-forwarding network elements. The SDN controller is only responsible for configuration delivery and no longer processes data reporting requests from forwarding network elements, thereby simplifying the functions of the controller. After receiving a data packet, if the fast-forwarding network element cannot find the corresponding target flow table in the local flow table, the packet is sent to the slow-forwarding network element. The slow-forwarding network element generates a target flow table based on the business logic in the business instance and sends it to the fast-forwarding network element. Subsequent data packets no longer need to be processed by the slow-forwarding network element, thereby improving the efficiency of data forwarding and the overall performance of the system. This architectural design not only reduces reporting traffic, reduces latency and jitter, but also improves the scalability and flexibility of the system.

[0081] Figure 3 This is a structural diagram of an electronic device M00 provided in an embodiment of the present application. In the figure, the electronic device M00 includes a processor M01 and a memory M02. The electronic device includes: a processor; a memory for storing instructions executable by the processor, wherein the processor is configured to execute the instructions to implement any of the data processing methods described above, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0082] In an embodiment of the present application, the memory M02 can be used to store software programs and various data. The memory M02 may mainly include a first storage area for storing programs or instructions and a second storage area for storing data, wherein the first storage area may store an operating system, an application program or instructions required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory M02 may include a volatile memory or a non-volatile memory, or the memory x09 may include both volatile and non-volatile memories. Among them, the non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM), a static random access memory (SRAM), a dynamic random access memory (DRAM), a synchronous dynamic random access memory (SDRAM), a double data rate synchronous dynamic random access memory (DDRSDRAM), an enhanced synchronous dynamic random access memory (ESDRAM), a synchronous link dynamic random access memory (SLDRAM) and a direct memory bus random access memory (DRRAM). The memory M02 in the embodiment of the present application includes but is not limited to these and any other suitable types of memories.

[0083] The processor M01 may include one or more processing units; optionally, the processor M01 integrates an application processor and a modem processor, wherein the application processor mainly processes operations related to an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communication signals, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor M01.

[0084] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the various processes of the above-mentioned data processing method embodiment are implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0085] The processor is the processor in the electronic device described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory ROM, a random access memory RAM, a magnetic disk or an optical disk.

[0086] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the above-mentioned data processing method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0087] It should be understood that the chip involved in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0088] An embodiment of the present application further provides a storage medium. When instructions in the storage medium are executed by a processor of an electronic device, the electronic device can execute any of the data processing methods described above.

[0089] An embodiment of the present application provides a computer program product, which is stored in a storage medium. The program product is executed by at least one processor to implement the various processes of the above-mentioned data processing method embodiment and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0090] An embodiment of the present application also provides a vehicle, which includes the data processing device as described above.

[0091] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0092] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the relevant technology, can be embodied in the form of a computer software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0093] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A data processing system, characterized in that: The data processing system comprises: a software defined network controller, a fast-forwarding network element and a slow-forwarding network element, wherein the software defined network controller is communicatively connected with the slow-forwarding network element and the fast-forwarding network element respectively; The software defined network controller is used to send the service instance created by the user to the slow-transfer network element, and send the network element control information configured based on the service instance to the slow-transfer network element and the fast-transfer network element; The fast-forwarding network element is used to send the data packet to the slow-forwarding network element when it receives a data packet and the target flow table corresponding to the data packet cannot be found in the network element control information of the fast-forwarding network element, so that the slow-forwarding network element generates the target flow table corresponding to the data packet according to the business logic in the business instance, and sends the target flow table to the fast-forwarding network element.

2. The system according to claim 1, characterized in that The fast-forwarding network element includes a plurality of first virtual machines, and the traffic of processing the data message is evenly distributed among the plurality of first virtual machines.

3. The system according to claim 1, characterized in that The slow-forwarding network element includes a plurality of second virtual machines, and flow table session information between the plurality of second virtual machines is synchronized.

4. The system according to claim 1, characterized in that The fast-forwarding network element is also used to process forward messages and return messages of data flows of different service instances corresponding to the same user through the same processor core in the fast-forwarding network element, wherein the transmission directions of the data flows between the forward messages and the return messages are opposite.

5. The system according to claim 1, characterized in that The fast-forwarding network element is further configured to process the data message according to the target flow table when receiving the data message and searching the target flow table.

6. The system according to claim 1, characterized in that The first virtual machine and the second virtual machine are provided with a port mapping mechanism and a flow marking mechanism; The first virtual machine and the second virtual machine schedule the forward messages and return messages of the data flows of different service instances corresponding to the same user to the same fast-forwarding network element and the slow-forwarding network element through the port mapping mechanism and the flow labeling mechanism.

7. The system according to claim 1, characterized in that The data stream processing system includes a message analysis server; The message analysis server is used to receive the data message processed by the slow-transfer network element through the configurable multi-tuple, perform message analysis on the data message, obtain the message flow stickiness feature, and report the message flow stickiness feature to the software-defined network controller, so that the software-defined network controller sends the message flow stickiness feature to the slow-transfer network element.

8. A data processing method, characterized in that: Applied to the fast-forwarding network element in the data processing system, the method comprises: When a data message is received and the target flow table corresponding to the data message cannot be found in the network element control information of the fast-forwarding network element, the data message is sent to the slow-forwarding network element so that the slow-forwarding network element generates the target flow table corresponding to the data message according to the service logic in the service instance, and sends the target flow table to the fast-forwarding network element; Among them, the business instance is sent by the software-defined network controller to the slow-transfer network element, and the network element control information is sent by the software-defined network controller to the slow-transfer network element and the fast-transfer network element, and the software-defined network controller is communicated with the slow-transfer network element and the fast-transfer network element respectively.

9. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the data processing method as claimed in claim 8.

10. A computer storage medium, a readable storage medium, for storing a program, characterized in that: When the program is executed by a processor, the data processing method as claimed in claim 8 is implemented.

Images