A deep data packet inspection system, method, device and medium
By using a universal application server and high-performance processing unit in deep packet detection systems, efficient packet detection and processing is achieved, solving the problems of inefficiency and high cost in existing systems, and providing flexible scaling and low-cost deployment plan.
Patent Information
- Application Number
- CN202411261484.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-09-10
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2044-09-10
AI Technical Summary
Existing deep packet detection systems are inefficient, poorly scalable, and costly, making them difficult to deploy on a large scale when processing high-traffic data.
Using a general application server as the hardware platform, through modular and distributed design, high-performance processing units (such as DPUs) and programmable network devices (such as P4 Switch) are introduced to achieve efficient packet detection and reduce deployment and operation and maintenance costs.
It improves the processing performance and scalability of the system, reduces deployment and operation and maintenance costs, and achieves rapid and accurate detection of high-traffic data, adapting to future network development needs.
Smart Images

Figure CN118784504B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of DPI communication technology, and in particular to a deep data packet inspection system, method, device and medium. Background Art
[0002] With the rapid development of Internet services, data traffic is growing exponentially, causing unprecedented challenges for network systems. Existing technologies mainly rely on a single server or centralized architecture to process data packets, but this approach is often inefficient when processing high-traffic data and can easily become a system bottleneck. Especially when the data volume reaches hundreds of G or even higher levels, the existing centralized Deep Packet Inspection (DPI) system has significant deficiencies in processing performance, scalability, and resource utilization.
[0003] DPI technology is one of the important technologies in the field of network security. By deeply analyzing the data packets in the network traffic, potential threats and abnormal behaviors in the network can be detected. However, traditional DPI systems usually use high-performance dedicated hardware. Although they can provide high processing power, their high cost limits the feasibility of large-scale deployment. At the same time, as the cost of hardware continues to decrease, how to efficiently use these low-cost hardware resources has become an urgent problem to be solved.
[0004] In order to cope with the ever-increasing network traffic and increasingly complex application scenarios, distributed architecture has gradually become an effective solution. By distributing packet detection tasks to multiple general-purpose servers, distributed architecture can achieve good scalability and cost-effectiveness while ensuring high processing performance. However, existing distributed DPI systems still face technical challenges in terms of packet forwarding, traffic load balancing, and application identification accuracy. Summary of the invention
[0005] One object of the present application is to provide a deep data packet inspection system, method, device and medium, at least to solve the problem of insufficient scalability of the deep data packet inspection system.
[0006] To achieve the above objectives, some embodiments of the present application provide the following aspects:
[0007] In the first aspect, some embodiments of the present application also provide a deep data packet inspection system, including an XDR subsystem, the hardware platform of the XDR subsystem is a general application server; an interface adapter subsystem, the hardware platform of the interface adapter subsystem is a general application server; a front-end subsystem, the front-end subsystem is a frame-type device composed of multiple heterogeneous logical processors, including a main control board and multiple slot service boards; the interface adapter subsystem is connected to the front-end subsystem through an L1 interface; the L1 interface is an interface machine-front-end southbound command interface; the interface adapter subsystem is connected to the XDR subsystem through an L2 interface; the L2 interface is an interface machine-XDR southbound command interface; the front-end subsystem is connected to the XDR subsystem through L3 and L4 interfaces; the L3 interface is a data forwarding interface, and the L4 interface is an RPC control interface.
[0008] On the second aspect, some embodiments of the present application also provide a deep data packet inspection method, including transmitting service-independent control instructions through the L1 interface between the interface adaptation subsystem and the front-end subsystem; transmitting service-related control instructions through the L2 interface between the interface adaptation subsystem and the XDR subsystem; forwarding the first N packets of each flow, forwarding netflow statistical information, and forwarding netflow disposal information through the L3 interface between the front-end subsystem and the XDR subsystem; and issuing service-based instructions by XDR through RPC through the L4 interface between the front-end subsystem and the XDR subsystem.
[0009] In a third aspect, some embodiments of the present application further provide an electronic device, comprising: one or more processors; and a memory storing computer program instructions, wherein the computer program instructions, when executed, cause the processor to perform the steps of the method described above.
[0010] In a fourth aspect, some embodiments of the present application further provide a computer-readable medium having computer program instructions stored thereon, wherein the computer program instructions can be executed by a processor to implement the method as described above.
[0011] Compared with the related art, the solution provided in the embodiment of the present application realizes fast and accurate detection of high-traffic data through innovative hardware platform design and efficient data packet processing methods, and can be flexibly expanded to meet future network development needs. By modularizing and distributing the DPI system and introducing high-performance processing units (such as DPU) and programmable network devices (such as P4 Switch), the present application not only improves the overall performance of the system, but also significantly reduces deployment and operation and maintenance costs, providing the possibility for large-scale applications. BRIEF DESCRIPTION OF THE DRAWINGS
[0012] One or more embodiments are exemplarily described by pictures in the corresponding drawings, and these exemplified descriptions do not constitute limitations on the embodiments. Elements with the same reference numerals in the drawings represent similar elements, and unless otherwise stated, the figures in the drawings do not constitute proportional limitations.
[0013] Figure 1 A schematic diagram of the architecture of a deep data packet inspection system provided according to an embodiment of the present application;
[0014] Figure 2 A schematic diagram of the structure of a deep data packet inspection system provided according to an embodiment of the present application;
[0015] Figure 3 The present invention is a schematic diagram of the structure of an electronic device provided according to an embodiment of the present application. DETAILED DESCRIPTION
[0016] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.
[0017] First embodiment
[0018] The first embodiment of the present application relates to a deep data packet inspection system. Figure 1 As shown, the system may include:
[0019] XDR subsystem, the hardware platform of the XDR subsystem is a general application server, which is responsible for processing high-resource services. Using a general application server as a hardware platform reduces hardware costs and improves the scalability of the system. The use of a general server allows the system to be flexibly expanded when processing high-resource services, avoiding the high cost of high-performance dedicated hardware. The XDR subsystem is specifically responsible for processing high-resource services, separating complex and resource-consuming services from the front-end subsystem, and improving the overall processing efficiency and performance of the system.
[0020] Interface adapter subsystem, the hardware platform of the interface adapter subsystem is a general application server, which is responsible for connecting the front-end subsystem and the XDR subsystem. The interface adapter subsystem is connected to the front-end subsystem through the L1 interface; the L1 interface is the interface machine-front-end southbound command interface. The interface adapter subsystem is connected to the XDR subsystem through the L2 interface; the L2 interface is the interface machine-XDR southbound command interface. Like the XDR subsystem, the interface adapter subsystem uses a general application server to reduce costs and provide flexible expansion capabilities. Through this interface design, the accurate transmission of control instructions can be ensured, and the management efficiency and reliability of the system can be improved. The interface adapter subsystem acts as a connecting bridge in the system, ensuring the seamless connection and collaborative work of the front-end subsystem and the XDR subsystem, and enhancing the overall coordination of the system.
[0021] The front-end subsystem is a frame-type device composed of multiple heterogeneous logical processors, including a main control board and multiple slot business boards. The main control board is responsible for unified management of other business boards, ensuring that the business boards are linearly stacked to form a business processing matrix with high port density and high computing power density, and realizing the core business of unified DPI. The control logic of the main control board consists of CPU and CPLD. Due to its low computing power, the CPU is only responsible for implementing general control logic; CPLD is responsible for implementing control logic for peripherals (such as fans, LED lights, power supplies, etc.). The business board control logic consists of CPU, DPU, programmable Switch chip and CPLD. Through this combination of multiple processing units, the business board can simultaneously realize general control and advanced business processing, providing powerful processing capabilities.
[0022] Due to its relatively small computing power, the CPU is only responsible for implementing general control logic; the DPU is a high-performance processing unit responsible for implementing advanced processing of business traffic; the programmable Switch chip implements basic processing of business traffic through the P4 programmable language.
[0023] The front-end subsystem is connected to the XDR subsystem through L3 and L4 interfaces; the L3 interface is a data forwarding interface, and the L4 interface is an RPC control interface. This interface design ensures efficient forwarding of data packets and accurate execution of control instructions, improving the overall performance and efficiency of the system.
[0024] It is not difficult to find that compared with the related art, in the solution provided by the embodiment of the present application, efficient, flexible and scalable deep packet inspection is achieved under the collaborative work of various parts. The general server platform design of the XDR subsystem and the interface adapter subsystem reduces costs and improves the scalability of the system; the heterogeneous processors and multiple processing unit combinations of the front-end subsystem improve the processing performance of the system; the design of the L1, L2, L3 and L4 interfaces ensures efficient communication and collaborative work between various parts of the system. On the whole, it has significant technical advantages in solving the problems of high-traffic processing bottlenecks, insufficient resource utilization and poor scalability existing in the prior art.
[0025] Second embodiment
[0026] The second embodiment of the present application relates to a deep data packet inspection system. The second implementation is an improvement based on the first embodiment, and the specific improvements are:
[0027] like Figure 2 As shown in the figure, the interface adapter subsystem is connected to the front-end subsystem through the L1 interface; the L1 interface is the southbound command interface between the interface machine and the front-end; the L1 interface is used to transmit control instructions that are not related to the business, including mirroring, blocking, speed limiting, and traffic collection. The L1 interface is used to transmit control instructions that are not related to the business, ensuring that the system can perform traffic mirroring, blocking, and speed limiting operations as needed when processing business traffic. These instructions provide basic support for the management and control of business traffic, ensuring the security and stability of the system.
[0028] The interface adapter subsystem is connected to the XDR subsystem through the L2 interface; the L2 interface is the interface machine-XDR southbound command interface; the L2 interface is used to transmit business-related control instructions, including application-based mirroring, speed limiting and blocking. The L2 interface is used to transmit business-related control instructions, enabling the system to manage traffic in a refined manner according to the needs of specific applications. For example, through mirroring instructions, specific application traffic can be monitored; through speed limiting and blocking instructions, abnormal traffic can be controlled to ensure the normal operation of the system.
[0029] The front-end subsystem is connected to the XDR subsystem through L3 and L4 interfaces; the L3 interface is a data forwarding interface, and the L4 interface is an RPC control interface. The L3 interface is used to forward the first N packets of each flow, netflow statistics information, and netflow disposal information; the L4 interface is used for XDR to issue business-based instructions through RPC. The L3 interface is used for data forwarding, especially the forwarding of the first N packets of each flow. Through this interface, the system can forward the traffic packets processed in the front-end subsystem to the XDR subsystem for further processing. The forwarding of netflow statistics and disposal information enables the XDR subsystem to analyze and process the traffic in detail, improving the detection accuracy and response capability of the system. The L4 interface is used for the XDR subsystem to issue business-based instructions through RPC (remote procedure call). This design enables the XDR subsystem to dynamically adjust the processing behavior of the front-end subsystem, improving the flexibility and adaptability of the system. Through remote calls, instructions can be quickly transmitted and executed, ensuring that the system can respond to various business needs in a timely manner.
[0030] The L1 and L2 interfaces ensure the accurate transmission of business-independent and business-related instructions, enabling the system to manage and control traffic as needed; the L3 interface implements efficient forwarding of data packets and transmission of traffic statistics, ensuring that the system can perform detailed analysis and processing of traffic; the L4 interface implements the issuance and execution of remote instructions through RPC, improving the system's dynamic adjustment capabilities and response speed.
[0031] The DPU (data processing unit) in the front-end subsystem is a high-performance processing unit that mainly processes services based on five tuples (source IP address, destination IP address, source port, destination port, and protocol type). In order to maximize the performance of the DPU, relatively resource-intensive application-related services are sent to the XDR subsystem for processing through the L3 interface.
[0032] The features of application identification are usually contained in the first few packets of the data message. The specific application can be identified through the first few packets of these messages. Design the logic of forwarding the first N packets. This N value can be configured and modified on the DPU. Through the L3 interface, the first N packets are forwarded to the XDR subsystem for further processing. The XDR subsystem identifies the application through the first N packets received. If the application needs to be controlled, the IP information of the application is sent back to the DPU through the L4 interface for control processing.
[0033] Since the XDR subsystem can only receive part of the messages, the statistical information about the flow needs to be notified to the XDR subsystem by the DPU through the designed netflow package. The XDR subsystem can deploy one or more general application servers. In theory, the number of XDR general servers deployed corresponds to the number of network ports on the front-end switch. You only need to configure the XDR network port on the switch. Through the hash algorithm, the switch will calculate the five-tuple of the message forwarded by the DPU to the XDR to ensure that the same flow is only forwarded to one XDR server and evenly distributed to all XDRs for processing.
[0034] Netflow is flow statistics information, including the time when SYN, SYN-ACK, SYN-ACK-ACK are received, the time when the flow is successfully established, the number of packets and bytes of the entire flow, etc. The DPU notifies the XDR subsystem of the flow statistics information through the designed netflow package, ensuring that the XDR subsystem can fully understand the traffic situation and perform effective traffic management and analysis.
[0035] Operation process example: traffic enters the front-end subsystem, and the DPU performs preliminary processing based on the five-tuple; the first N data packets are forwarded to the XDR subsystem through the L3 interface, and the XDR performs application identification; if the identified application needs to be controlled, the XDR sends the application's IP information back to the DPU through the L4 interface, and the DPU performs traffic control according to the instructions; the DPU notifies the XDR subsystem of the flow statistics through the netflow packet to ensure that the XDR has a comprehensive grasp of the sub-flow. The XDR subsystem is deployed on multiple general application servers, and the switch hash algorithm is used to achieve balanced distribution of traffic to ensure efficient processing.
[0036] L3 interface design: L3 interface mainly distinguishes different packets by adding a private MAC header to the original message and including different VLAN IDs in the MAC header. The message types include:
[0037] VLAN 101 message, VLAN 101 identifies the original message forwarded from DPU to XDR. In the current VLAN, only the private MAC header is added to the original message. After receiving the message, XDR can directly offset the private MAC header for processing. Message format:
[0038]
[0039] For the message of vlan 102, the vlan 102 identifier adds netflow information at the end of the message. The private mac header needs to be added to the original message under the current vlan, and the private netflow information needs to be added to the end of the original message. After receiving the message, XDR first offsets the private mac header, and then removes the netflow according to the information at the end of the message. The structure of netflow is to add 2 bytes of magic and 2 bytes of netflow length at the end of the message. The message format is:
[0040]
[0041] The message of vlan 103, the vlan 103 identifier message only contains netflow information. The message under the current vlan is not the original message, but the udp message generated according to the five-tuple of the original message. The source and destination IP addresses and ports of the udp message are the same as those of the original packet. The protocol of the original packet is in the payload part of the udp. The payload part of the udp is the same as the netflow structure of vlan102. The message format is:
[0042]
[0043] It is not difficult to find that in the embodiments of the present application, while ensuring the security and stability of the system, the flexibility and processing efficiency of the system are significantly improved. The collaborative processing mechanism of the front-end subsystem and the XDR subsystem, combined with high-performance DPU processing and precise application identification and control, enhances the system's ability to detect large-scale, high-traffic data packets. The multi-server deployment and load balancing design of the XDR subsystem further enhance the scalability and reliability of the system. In short, the deep data packet inspection system of the present application has significant technical advantages in efficient processing and fine management.
[0044] It is worth mentioning that all modules involved in this embodiment are logic modules. In practical applications, a logic unit can be a physical unit, a part of a physical unit, or a combination of multiple physical units. In addition, in order to highlight the innovative part of this application, this embodiment does not introduce units that are not closely related to solving the technical problems proposed by this application, but this does not mean that there are no other units in this embodiment.
[0045] Third embodiment
[0046] A third embodiment of the present application relates to a deep data packet inspection method, the method comprising:
[0047] Transmitting service-independent control instructions through the L1 interface between the interface adapter subsystem and the front-end subsystem;
[0048] Transmitting service-related control instructions through the L2 interface between the interface adapter subsystem and the XDR subsystem;
[0049] Through the L3 interface between the front-end subsystem and the XDR subsystem, the first N packets of each flow are forwarded, netflow statistics information is forwarded, and netflow disposal information is forwarded;
[0050] Through the L4 interface between the front-end subsystem and the XDR subsystem, XDR sends service-based instructions through RPC.
[0051] It is not difficult to find that this embodiment is a method embodiment corresponding to the first embodiment, and this embodiment can be implemented in conjunction with the first embodiment. The relevant technical details mentioned in the first embodiment are still valid in this embodiment, and in order to reduce repetition, they are not repeated here. Accordingly, the relevant technical details mentioned in this embodiment can also be applied in the first embodiment.
[0052] In addition, some embodiments of the present application also provide an electronic device. The electronic device may be a digital computer in various forms, such as a laptop computer, a desktop computer, a workbench, a personal digital assistant, a server, a blade server, a mainframe computer, etc. The electronic device may also be a mobile device in various forms, such as a personal digital processing, a cellular phone, a smart phone, a wearable device, and other similar computing devices.
[0053] The electronic device includes: one or more processors; and a memory storing computer program instructions, wherein when the computer program instructions are executed, the processor executes the steps of the method provided in any one or more of the above embodiments. Figure 3 An exemplary structural diagram of the electronic device is disclosed. Figure 3As shown, the electronic device includes: one or more processors 1101, a memory 1102, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. The various components are connected to each other using different buses and can be installed on a common motherboard or installed in other ways as needed. The processor can process instructions executed in the electronic device, including instructions stored in or on the memory to display graphical information of the GUI on an external input / output device (such as a display device coupled to the interface). In some other embodiments, if necessary, multiple processors and / or multiple buses can be used with multiple memories and multiple memories. Similarly, multiple electronic devices can be connected, and each device provides some necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Among them, the components shown in this article, their connections and relationships, and their functions are only examples, and are not intended to limit the implementation of the present application described and / or required herein.
[0054] The electronic device may further include: an input device 1103 and an output device 1104. The processor 1101, the memory 1102, the input device 1103 and the output device 1104 may be connected via a bus or other means. Figure 3 The example of connecting through bus is taken in the following.
[0055] The input device 1103 can receive input digital or character information, and generate key signal input related to the user settings and function control of the electronic device, such as a touch screen, a keypad, a mouse, a track pad, a touch pad, an indicator rod, one or more mouse buttons, a trackball, a joystick and other input devices. The output device 1104 may include a display device, an auxiliary lighting device (e.g., an LED) and a tactile feedback device (e.g., a vibration motor), etc. The display device may include, but is not limited to, a liquid crystal display (LCD), a light emitting diode (LED) display and a plasma display. In some embodiments, the display device may be a touch screen.
[0056] To provide interaction with a user, the electronic device may be a computer. The computer has: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or a trackball), through which the user can provide input to the computer. Other types of devices may also be used to provide interaction with a user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).
[0057] In the embodiments of the present application, a computer program / instruction is stored on a computer-readable medium, and when the computer program / instruction is executed by a processor, the steps of the method provided by any one or more of the above embodiments are implemented. The computer-readable medium may be included in the electronic device described in the above embodiments; or it may exist independently without being assembled into the device. The above computer-readable medium carries one or more computer-readable instructions.
[0058] The memory 1102 can be used as a non-transient computer-readable storage medium, which can be used to store non-transient software programs, non-transient computer executable programs and modules. The processor 1101 executes various functional applications and data processing of the server by running the non-transient software programs, instructions and modules stored in the memory 1102, so as to implement the program instructions / modules corresponding to the method provided by any one or more embodiments in the embodiments of the present application.
[0059] The memory 1102 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 1102 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory 1102 may optionally include a memory remotely arranged relative to the processor 1101, and these remote memories may be connected to the electronic device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0060] It should be noted that the computer-readable medium described in this application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable 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 of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer 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. In this application, a computer-readable medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device.
[0061] Computer readable media include permanent and non-permanent, removable and non-removable media, and can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, modules of programs or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device.
[0062] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0063] In the above embodiments, all or part of the embodiments may be implemented by software, hardware, firmware or any combination thereof. For example, an application specific integrated circuit (ASIC), a general-purpose computer or any other similar hardware device may be used to implement the embodiments. In some embodiments, the software program of the present application may be executed by a processor to implement the above steps or functions. Similarly, the software program of the present application (including related data structures) may be stored in a computer-readable recording medium, such as a RAM memory, a magnetic or optical drive or a floppy disk and the like. In addition, some steps or functions of the present application may be implemented by hardware, for example, as a circuit that cooperates with a processor to perform various steps or functions.
[0064] The computer program product provided in the embodiment of the present application includes one or more computer programs / instructions, and when the computer program / instructions are executed by the processor, the process or function described in the embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions may be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions may be transmitted from a website site, a computer, a server, or a data center to another website site, a computer, a server, or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or a data center that includes one or more available media integrations. The available medium may be a magnetic medium, (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)), etc.
[0065] The flow chart or block diagram in the accompanying drawings shows the possible architecture, function and operation of the equipment, method and computer program product according to various embodiments of the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in a different order from the order marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be implemented with a dedicated system for hardware that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0066] The scope of the present application is defined by the appended claims rather than the above description, and it is intended that all changes that fall within the meaning and scope of the equivalent elements of the claims are included in the present application. Any figure mark in the claims should not be regarded as limiting the claims involved. In addition, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices stated in the device claim may also be implemented by one unit or device through software or hardware. The words "first", "second", etc. are only used to distinguish the description, and do not indicate any particular order, nor can they be understood as indicating or implying relative importance.
[0067] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art can easily mention changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims, and the above embodiments should be regarded as exemplary and non-restrictive.
Claims
1. A deep packet inspection system, It is characterized in that The system comprises: XDR subsystem, the hardware platform of the XDR subsystem is a general application server; An interface adapter subsystem, wherein the hardware platform of the interface adapter subsystem is a general application server; A front-end subsystem, which is a frame-type device composed of multiple heterogeneous logical processors, including a main control board and multiple slot service boards; The interface adapter subsystem is connected to the front-end processor subsystem via an L1 interface; the L1 interface is an interface machine-front-end processor southbound instruction interface; The interface adaptation subsystem is connected to the XDR subsystem via an L2 interface; the L2 interface is an interface machine-XDR southbound command interface; The front-end subsystem is connected to the XDR subsystem via L3 and L4 interfaces; the L3 interface is a data forwarding interface, and the L4 interface is an RPC control interface; The L1 interface is used to transmit service-independent control instructions, including mirroring, blocking, speed limiting and traffic collection; The L2 interface is used to transmit service-related control instructions, including application-based mirroring, rate limiting and blocking; The L3 interface is used to forward the first N packets of each flow, forward netflow statistics information, and forward netflow disposal information; The L4 interface is used by XDR to send service-based instructions through RPC.
2. The system according to claim 1, It is characterized in that The XDR subsystem and the interface adaptation subsystem are deployed on multiple general application servers based on a distributed architecture.
3. The system according to claim 2, It is characterized in that The main control board includes: a CPU processor for processing general control logic; a CPLD processor for processing the control logic of peripherals.
4. The system according to claim 3, It is characterized in that The slot service board includes: a CPU processor for processing general control logic; a DPU processor for performing advanced processing of service traffic; a Switch chip for performing basic processing of service traffic through the P4 programmable language; and a CPLD processor for processing the control logic of peripherals.
5. The system according to claim 1, It is characterized in that The system comprises: Identify specific applications through the first N packets of each flow and allocate processing services based on the characteristics of specific applications; Processing quintuple-based services through the DPU processor of the slot service board; processing high-resource services through the XDR subsystem; The message forwarded by the DPU processor to the XDR subsystem is calculated through the Switch chip of the slot service board, and the flow data is distributed to the general application server of the XDR subsystem.
6. The system according to claim 1, It is characterized in that The L3 interface adds a private MAC header to the original message, and distinguishes packets according to the VLAN ID in the MAC header. The processed messages include VLAN 101 messages, VLAN 102 messages, and VLAN 103 messages.
7. A deep packet inspection method, applied to the system according to any one of claims 1 to 6, It is characterized in that The method comprises: Transmitting service-independent control instructions through the L1 interface between the interface adapter subsystem and the front-end subsystem; Transmitting service-related control instructions through the L2 interface between the interface adapter subsystem and the XDR subsystem; Through the L3 interface between the front-end subsystem and the XDR subsystem, the first N packets of each flow are forwarded, netflow statistics information is forwarded, and netflow disposal information is forwarded; Through the L4 interface between the front-end subsystem and the XDR subsystem, XDR sends business-based instructions through RPC.
8. An electronic device, It is characterized in that The electronic device comprises: one or more processors; and A memory storing computer program instructions which, when executed, cause the processor to perform the steps of the method of claim 7.
9. A computer readable medium having a computer program / instructions stored thereon, It is characterized in that When the computer program / instructions are executed by a processor, the steps of the method of claim 7 are implemented.
Citation Information
Patent Citations
Deep packet inspection (DPI) system and method based on cloud computing
CN106453550A
Method and device for network flow data analysis based on stream processing
CN108259371A
Big data security analysis system based on massive network monitoring data
CN108259462A
Switch system based on service function chain
CN108471389A
Flow collection strategy distribution method and device, electronic equipment and storage medium
CN115811468A
