Software secondary radar data processing system based on micro service

Abstract

The invention discloses a software secondary radar data processing system based on micro-service, and relates to the technical field of secondary radar. The system comprises a hardware management layer which is used for shielding the difference of a hardware architecture and providing a unified application programming API interface for an upper layer service; the data service layer is used for decomposing the whole data processing flow of the secondary radar into multiple types of independent micro-services and processing the data received through the API interface based on the micro-services; the service scheduling layer is used for monitoring and scheduling the multiple types of independent micro-services of the data service layer in real time; and the application interface layer is used for providing a calling interface for an upper-layer application and docking with an external system so as to output the data processed by each micro-service and received from the data service layer. According to the invention, the problems of tight coupling, poor expansibility and the like of a traditional radar architecture are solved, and software, service and modularization of radar data processing are realized.

Description

Technical Field

[0001] This invention relates to the field of secondary radar technology, and more specifically to a software-based secondary radar data processing system based on microservices. Background Technology

[0002] Traditional radar data processing systems often adopt an "integrated monolithic architecture," meaning that functional modules such as signal processing, data processing, data fusion, and terminal display are highly integrated into a single hardware platform or tightly coupled software system. Radar data processing systems with this architecture suffer from the following problems:

[0003] (1 High hardware dependence: Functions are tightly bound to hardware platforms, and the processing systems of different radar models are difficult to reuse, resulting in long radar system development cycles, high costs, and inability to quickly adapt to different application scenarios.

[0004] (2) High maintenance and upgrade costs: The modules are highly coupled, and the failure of a single module may cause the entire system to crash. Software updates and iterations require stopping the entire system and hot upgrades cannot be achieved. Summary of the Invention

[0005] This invention addresses the problems of poor scalability, insufficient real-time performance, high hardware dependence, and low iteration efficiency in existing radar data processing systems. It provides a software-based secondary radar data processing system, method, device, and storage medium based on microservices, which solves the problems of tight coupling and poor scalability in traditional radar architectures and realizes the software-based, service-oriented, and modularization of radar data processing.

[0006] The present invention is achieved through the following technical solution.

[0007] Firstly, a software-based secondary radar data processing system based on microservices is provided, the system comprising:

[0008] The hardware management layer is used to shield differences in hardware architecture and provide a unified application programming API interface for upper-layer services.

[0009] The data service layer is used to decompose the entire data processing process of the secondary radar into multiple independent microservices, and to process the data received through the API interface based on the microservices.

[0010] The service scheduling layer is used for real-time monitoring and scheduling of various independent microservices in the data service layer;

[0011] The application interface layer is used to provide calling interfaces to upper-layer applications and to interface with external systems in order to output the data received from the microservices of the data service layer after processing.

[0012] In some embodiments, the hardware management layer includes: a hardware driver encapsulation module, a hardware resource management module, and a hardware interface module, wherein,

[0013] The hardware driver encapsulation module is used to: encapsulate the driver programs for the front-end radio frequency hardware unit, processing computing unit, and storage hardware unit of the secondary radar, and form a standardized driver interface for upper-layer services to call.

[0014] The hardware resource management module is used to: monitor the usage status of hardware resources in real time, virtualize and encapsulate the hardware resources, realize the dynamic allocation of hardware resources, and provide hardware status information to the service scheduling layer in real time.

[0015] The hardware interface module is used to: uniformly encapsulate the resource usage status, running status, and operation status of hardware, provide standardized hardware resource call APIs, and encapsulate the APIs to provide interfaces for upper-layer services to monitor and call hardware services.

[0016] In some embodiments, the multiple independent microservices of the data service layer include: signal access service, signal preprocessing service, target detection and decoding service, point aggregation service, trajectory processing service, data fusion service, target classification and recognition service, and data display service.

[0017] The signal access service is used to: acquire the raw signal output by the radio frequency front-end of the secondary radar and convert it into a digital intermediate frequency signal;

[0018] The signal preprocessing service is used to: preprocess the digital intermediate frequency signal;

[0019] The target detection and decoding service is used to: decode the digital intermediate frequency signal preprocessed by the signal preprocessing service and output target attribute information;

[0020] The point aggregation service is used to: aggregate multiple original target points within the antenna scanning beamwidth into a unique point in the coordinate space based on the target attribute information, and output the aggregated target point trace.

[0021] The track processing service is used to: preprocess the target point track to obtain track information and report the track information;

[0022] The data fusion service is used to: fuse target tracks from multiple data sources / multiple secondary radars, and simultaneously smooth and filter the fused target tracks to output fused target trajectory information.

[0023] The target classification and recognition service is used to: extract key attribute information of the target based on the target point traces and the target trajectory information, construct an attribute information database, and store targets of different categories into the corresponding databases;

[0024] The data display service is used to display the target attribute information, target classification information, and target location information through a graphical interface.

[0025] In some embodiments, the service scheduling layer includes: a service registration and management module, a dynamic resource scheduling module, and a service monitoring module, wherein,

[0026] The service registration and management module is used to: build a registration center platform, manage the address, status and interface information of all microservice instances, and support dynamic service discovery and communication;

[0027] The dynamic resource scheduling module is used to: orchestrate based on software containers, design scheduling priorities based on the resources and priorities required by services and based on real-time levels, and dynamically adjust the service call priorities and hardware resource allocation;

[0028] The service monitoring module is used to: monitor the running status and resource usage status of all microservices in real time, and report the status of all microservices.

[0029] In some embodiments, the application interface layer includes: a user interaction module, an external interface module, and a customized service module, wherein,

[0030] The user interaction module is used to: provide standard APIs for upper-layer applications, and support upper-layer applications in configuring radar data processing parameters, obtaining system and microservice running status information, obtaining radar data processing results, and other information.

[0031] The external interface module is used to: encapsulate external system interfaces and provide APIs for external system calls;

[0032] The customized service module is used to: customize applications for specific scenarios and provide functional extensions and custom interfaces for upper-layer applications.

[0033] In some embodiments, the system further includes a data bus, a service bus, and a control bus built at the system software level, wherein,

[0034] The data bus is used to: realize the real-time transmission of massive radar data, support subscription / publish mode, and meet the needs of parallel data processing of multiple services.

[0035] The service bus is used for: a base network transmission protocol, using a predetermined file format to transmit communication data, so as to realize synchronous / asynchronous communication and collaborative work between microservices;

[0036] The control bus is used to transmit configuration commands, scheduling commands, and control commands based on a lightweight communication protocol.

[0037] In some embodiments, the dynamic resource scheduling module dynamically adjusts the service call priority and hardware resource allocation, including: reserving sufficient computing, storage and communication resources for core services and prohibiting other non-core services from occupying them; and dynamically sharing idle computing and storage resources for non-core services.

[0038] Secondly, a microservice-based software-based secondary radar data processing method is provided, the method comprising:

[0039] By using a hardware management layer, the differences in hardware architecture are shielded, and a unified application programming API interface is provided for upper-layer services.

[0040] Through the data service layer, the entire data processing process of the secondary radar is decomposed into multiple independent microservices, and the data received through the API interface is processed based on the microservices.

[0041] The service scheduling layer performs real-time monitoring and scheduling of various independent microservices in the data service layer.

[0042] The application interface layer provides calling interfaces to upper-layer applications and interfaces with external systems to output data processed by various microservices received from the data service layer.

[0043] Thirdly, a microservice-based software-defined secondary radar data processing device is provided, the device comprising:

[0044] At least one processor;

[0045] At least one memory is coupled to the at least one processor and stores instructions for execution by the at least one processor, which, when executed by the at least one processor, implement the method described above.

[0046] Fourthly, a computer-readable storage medium is provided, the computer-readable storage medium storing instructions that, when executed by a computer, cause the computer to perform the methods described above.

[0047] Compared with existing technologies, this invention has the following advantages and beneficial effects: Through a layered decoupling design of four service layers and three major buses, it solves the problems of tight coupling and poor scalability in traditional radar architecture, realizes the software-based, service-oriented and modularization of radar data processing, and can significantly improve the real-time performance, scalability and iteration efficiency of radar data processing, providing an efficient solution for the implementation of software-based secondary radar engineering based on microservices. Attached Figure Description

[0048] To more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0049] Figure 1 This is an architecture diagram of a microservice-based software-defined secondary radar data processing system according to an embodiment of the present invention.

[0050] Figure 2 This is a flowchart of a microservice-based data processing procedure according to an embodiment of the present invention.

[0051] Figure 3 This is a flowchart of a software-based secondary radar data processing method based on microservices according to an embodiment of the present invention.

[0052] Figure 4 This is a schematic diagram of the structure of a software-based secondary radar data processing device based on microservices according to an embodiment of the present invention. Detailed Implementation

[0053] To make the objectives, technical solutions, and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the embodiments and accompanying drawings. The illustrative embodiments and descriptions of the present invention are only used to explain the present invention and are not intended to limit the present invention.

[0054] This invention proposes a software-based secondary radar data processing scheme based on microservices. Through layered decoupling, service-oriented encapsulation, and dynamic scheduling design, the entire radar data processing process is decomposed into independent microservices. Hardware decoupling is achieved through the hardware management layer, and task real-time performance and reliability are achieved through the data service layer and service scheduling layer. This results in the construction of a scalable, easily iterative, and cross-platform software-based secondary radar data processing system.

[0055] On the one hand, the present invention provides a software-based secondary radar data processing system based on microservices. Figure 1 This is an architecture diagram of a microservice-based software-defined secondary radar data processing system according to an embodiment of the present invention. (Reference) Figure 1 The microservice-based software-defined secondary radar data processing system includes: a hardware management layer, a data service layer, a service scheduling layer, and an application interface layer.

[0056] The hardware management layer is used to shield differences in hardware architecture and provide a unified application programming API interface for upper-layer services.

[0057] The data service layer is used to decompose the entire data processing process of the secondary radar into multiple independent microservices, and to process the data received through the API interface based on the microservices.

[0058] The service scheduling layer is used for real-time monitoring and scheduling of various independent microservices in the data service layer.

[0059] The application interface layer provides calling interfaces to upper-layer applications and interfaces with external systems to output data processed by various microservices received from the data service layer.

[0060] The following detailed description, with reference to the accompanying drawings, describes each layer of this microservice-based software-defined secondary radar data processing system.

[0061] The hardware management layer is the lowest-level service of the secondary radar data processing system. It is used to shield the differences in hardware architecture and provide a unified API interface for upper-level services, so that the upper-level services can focus on functionality without worrying about the differences in hardware architecture, thus enabling the secondary radar data processing system to be developed and run across hardware platforms.

[0062] In some embodiments, the hardware management layer includes three functional modules: a hardware driver encapsulation module, a hardware resource management module, and a hardware interface module. The hardware driver encapsulation module encapsulates the drivers for the radar front-end RF hardware unit, processing and computing unit, and storage hardware unit, forming standardized driver interfaces for upper-layer services to call. The hardware resource management module monitors the hardware resource usage status in real time, such as CPU / memory usage, hard disk usage, and currently running processes. It virtualizes and encapsulates hardware resources using Docker containers to achieve dynamic allocation of hardware resources and provides real-time hardware status information to the service scheduling layer. The hardware interface module uniformly encapsulates the hardware resource usage status, running status, and operational status, providing standardized hardware resource call APIs. The API encapsulation is implemented using JSON or XML, providing upper-layer services with interfaces for monitoring and calling hardware services.

[0063] The data service layer is located between the hardware management layer and the service scheduling layer. As the core functional layer of the software-based secondary radar data processing system, it decomposes the entire radar data processing process into multiple independent microservices.

[0064] In some embodiments, the data service layer includes multiple independent microservices such as: signal access service, signal preprocessing service, target detection and decoding service, point aggregation service, trajectory processing service, data fusion service, target classification and recognition service, and data display service. Each microservice interacts through a data bus and a service bus. These microservices are described in detail below.

[0065] The signal access service is used to acquire the raw signal output from the radar RF front-end and convert it into a software-processable digital intermediate frequency (IF) signal. For example, the signal access service converts the IF analog signal output from the RF front-end into an IF digital signal via an A / D (analog-to-digital) converter, then performs amplitude and phase calibration and clock synchronization to ensure signal accuracy, and finally sends the signal data to the signal preprocessing service via a data bus.

[0066] The signal preprocessing service is used to preprocess digital intermediate frequency (IF) signals. For example, the IF signal is converted into a lower-frequency video signal using a digital down-conversion (DDC) algorithm. Then, digital filtering techniques are used to reduce noise and filter the signal, removing clutter and interference. Pulse compression is then performed to improve range resolution and signal-to-noise ratio. Algorithms such as constant false alarm rate (CFAR) and moving target detection are used to suppress interference from ground features, clouds, rain, and other debris. Finally, the preprocessed signal is sent to the target detection and decoding service via a data bus.

[0067] The target detection and decoding service decodes the preprocessed signal and outputs target attribute information. For example, it determines whether a real target exists in the preprocessed signal by setting a threshold, completes target marking, and decodes the signal data to obtain key information such as the target's azimuth, pitch angle, distance, and velocity. The decoded target is then sent to the point aggregation service via the data bus.

[0068] The target point aggregation service, based on target attribute information, aggregates multiple original target points within the antenna scanning beamwidth into a unique point in coordinate space and outputs the aggregated target point trace. For example, based on target attribute information, an algorithm aggregates multiple original target points within the antenna scanning beamwidth into a unique point in coordinate space, and outputs the aggregated target point trace.

[0069] The track processing service preprocesses the target points to obtain track information and reports it. For example, invalid points are filtered out using algorithms and rules, then point-to-way correlation and pairing are performed. The optimal point-to-way queue is used to update the track, and the track information is smoothed and filtered to obtain filtered track information. The track management service also needs to maintain the track queue, process tracks that need to be extrapolated and deleted, and report the tracks through the data bus.

[0070] The data fusion service fuses target tracks from multiple data sources / radar sources, and simultaneously smooths and filters the fused tracks to output the fused target track information.

[0071] The target classification and recognition service extracts key attribute information of targets based on target point traces and target trajectory information, constructs an attribute information database, and stores targets of different categories into the corresponding database.

[0072] The data display service presents target location information, target attribute information, and target classification information through a graphical interface.

[0073] Figure 2 This is a flowchart illustrating a microservice-based data processing procedure according to an embodiment of the present invention. (Reference) Figure 2 After receiving the signal at the RF front end, the signal is sent to the signal preprocessing service via the data bus. The signal preprocessing service preprocesses the signal and then sends it to the target detection and decoding service via the data bus. The target detection and decoding service decodes the preprocessed signal to identify the target, obtain target attribute information, and sends the relevant data to the target point processing service via the data bus. The target point processing service processes the data and outputs the aggregated target point traces via the data bus. The track processing service and data fusion service receive the aggregated target point traces, process them accordingly, and then output them to the target classification and identification service via the data bus to extract key target attribute information, build an attribute information database, store different categories of targets in the corresponding databases, and send the data to the data display service via the data bus. The data display service displays relevant information through a graphical interface.

[0074] The service scheduling layer is the central hub of the data processing system, used for real-time monitoring and scheduling of microservices in the data service layer to ensure efficient and stable system operation. The service scheduling layer is further subdivided into three functional modules: service registration and management module, dynamic resource scheduling module, and service monitoring module.

[0075] The service registration and management module is used to build a registry platform, manage the address, status and interface information of all microservice instances, and support dynamic service discovery and communication.

[0076] The dynamic resource scheduling module is used for orchestration based on software containers. It dynamically adjusts service call priorities and hardware resource allocation according to the resources and priorities required by services and the real-time requirements. Sufficient computing, storage, and communication resources are reserved for core services, and non-core services are prohibited from occupying them. Idle computing and storage resources are dynamically shared by non-core services.

[0077] The service monitoring module is used to monitor the running status and resource usage of all microservices in the system in real time, and to report the status of microservices.

[0078] The application interface layer provides calling interfaces for upper-layer applications and interfaces with external systems. It provides standardized APIs for upper-layer applications to external systems, supporting the development of radar data processing applications. The application interface layer includes: a user interaction module, an external interface module, and a customized service module.

[0079] The user interaction module provides standard APIs for upper-layer web or client applications, enabling them to configure radar data processing parameters, obtain system and microservice running status information, and obtain radar data processing results.

[0080] The external interface module is used to encapsulate commonly used external system interfaces and provide APIs for external system calls.

[0081] The customization service module is used to tailor applications for specific scenarios and provides functional extensions and custom interfaces for upper-layer applications. Furthermore, token authentication and data encryption technologies are employed to ensure the security of API calls.

[0082] In some embodiments, the microservice-based software-defined secondary radar data processing system further includes a data bus, a service bus, and a control bus built at the system software level.

[0083] The data bus is used to: realize the real-time transmission of massive radar data, support subscription / publish mode, and meet the needs of parallel data processing of multiple services;

[0084] The service bus is used to: transmit communication data using a base network transport protocol and a predefined file format to enable synchronous / asynchronous communication and collaborative work between microservices;

[0085] The control bus is used to transmit configuration commands, scheduling commands, and control commands based on a lightweight communication protocol.

[0086] This system establishes three major buses across its four service layers to connect them and facilitate the transmission of data and commands between them. The data bus enables real-time transmission of massive amounts of radar data, supports publish / subscribe modes, and meets the needs of parallel data processing across multiple services. The service bus is based on the RESTful (Representational State Transmission) network protocol and uses JSON (JavaScript Object Notation) / XML (Extensible Markup Language) file formats for transmission, enabling synchronous / asynchronous communication and collaborative work between microservices. The control bus is based on the lightweight MQTT (Message Queuing Telemetry Transport) protocol, transmitting system configuration commands, scheduling commands, and control commands, and is used for the transmission of control commands.

[0087] In this invention, a layered decoupling design with four service layers and three major buses solves the problems of tight coupling and poor scalability in traditional radar architecture. It realizes the software-based, service-oriented, and modularization of radar data processing, which can significantly improve the real-time performance, scalability, and iteration efficiency of radar data processing, and provide an efficient solution for the implementation of software-based secondary radar engineering based on microservices.

[0088] On the other hand, the present invention provides a software-based secondary radar data processing method based on microservices. Figure 3 This is a flowchart illustrating a microservice-based software-defined secondary radar data processing method according to an embodiment of the present invention. (Reference) Figure 3 The microservice-based software-based secondary radar data processing method includes: S10 to S40.

[0089] In S10, the hardware management layer shields the differences in hardware architecture and provides a unified application programming API interface for upper-layer services.

[0090] In S20, the entire data processing flow of the secondary radar is decomposed into multiple independent microservices through the data service layer, and the data received through the API interface is processed based on the microservices.

[0091] In S30, the service scheduling layer performs real-time monitoring and scheduling of various independent microservices in the data service layer.

[0092] In S40, the application interface layer provides calling interfaces to upper-layer applications and interfaces with external systems to output data processed by various microservices received from the data service layer.

[0093] Other implementation details of this microservice-based software-based secondary radar data processing method are described in the previous section on the microservice-based software-based secondary radar data processing system, and will not be repeated here.

[0094] In implementing the functions of the integrated modules described above in hardware, this embodiment of the invention provides a structure for the software-based secondary radar data processing device based on microservices as described in the above embodiments. Figure 4 This is a schematic diagram of a microservice-based software-defined secondary radar data processing device according to an embodiment of the present invention. (Reference) Figure 4 The microservice-based software-defined secondary radar data processing device includes: at least one processor; and at least one memory. The at least one memory is coupled to the at least one processor and stores instructions for execution by the at least one processor, which, when executed by the at least one processor, implement the methods described above.

[0095] A processor can be a set of logic blocks, modules, and circuits that implement or execute the various exemplary logic blocks, modules, and circuits described in connection with embodiments of the present invention. The processor can be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It can implement or execute the various exemplary logic blocks, modules, and circuits described in connection with embodiments of the present invention. A processor can also be a combination that implements computational functions, such as a combination of one or more microprocessors, a combination of a digital signal processor and a microprocessor, etc.

[0096] The memory may be read-only memory (ROM) or other types of static storage devices that can store static information and instructions, random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited thereto.

[0097] In one implementation, the memory can exist independently of the processor. The memory can be connected to the processor via a bus and used to store instructions or program code. When the processor calls and executes the instructions or program code stored in the memory, it can implement the methods provided in the embodiments of the present invention. In another implementation, the memory can also be integrated with the processor.

[0098] On the other hand, the present invention also provides a computer-readable storage medium (e.g., a non-transitory computer-readable storage medium) storing computer program instructions that, when executed on a computer, cause the computer to perform the method as described in any of the above embodiments.

[0099] Exemplary examples show that the aforementioned computer-readable storage media may include, but are not limited to: magnetic storage devices (e.g., hard disks, floppy disks, or magnetic tapes), optical discs (e.g., compact disks (CDs), digital versatile disks (DVDs), etc.), smart cards, and flash memory devices (e.g., erasable programmable read-only memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this invention may represent one or more devices and / or other machine-readable storage media for storing information. The term "machine-readable storage medium" may include, but is not limited to, wireless channels and various other media capable of storing, containing, and / or carrying instructions and / or data.

[0100] This invention provides a computer program that, when run on a computer, causes the computer to perform the method of any of the above embodiments.

[0101] This invention provides a computer program product containing instructions that, when run on a computer, cause the computer to perform the method of any of the above embodiments.

[0102] The specific embodiments described above further illustrate the purpose, technical solution, and beneficial effects of the present invention. It should be understood that the above description is only a specific embodiment of the present invention and is not intended to limit the scope of protection of the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the scope of protection of the present invention.

Claims

1. A software-based secondary radar data processing system based on microservices, characterized in that, The system includes: The hardware management layer is used to shield differences in hardware architecture and provide a unified application programming API interface for upper-layer services. The data service layer is used to decompose the entire data processing process of the secondary radar into multiple independent microservices, and to process the data received through the API interface based on the microservices. The service scheduling layer is used for real-time monitoring and scheduling of various independent microservices in the data service layer; The application interface layer is used to provide calling interfaces to upper-layer applications and to interface with external systems in order to output the data received from the microservices of the data service layer after processing.

2. The system according to claim 1, characterized in that, The hardware management layer includes: a hardware driver encapsulation module, a hardware resource management module, and a hardware interface module, wherein... The hardware driver encapsulation module is used to: encapsulate the driver programs for the front-end radio frequency hardware unit, processing computing unit, and storage hardware unit of the secondary radar, and form a standardized driver interface for upper-layer services to call. The hardware resource management module is used to: monitor the usage status of hardware resources in real time, virtualize and encapsulate the hardware resources, realize the dynamic allocation of hardware resources, and provide hardware status information to the service scheduling layer in real time. The hardware interface module is used to: uniformly encapsulate the resource usage status, running status, and operation status of hardware, provide standardized hardware resource call APIs, and encapsulate the APIs to provide interfaces for upper-layer services to monitor and call hardware services.

3. The system according to claim 1, characterized in that, The data service layer includes multiple independent microservices: signal access service, signal preprocessing service, target detection and decoding service, point aggregation service, trajectory processing service, data fusion service, target classification and recognition service, and data display service. The signal access service is used to: acquire the raw signal output by the radio frequency front-end of the secondary radar and convert it into a digital intermediate frequency signal; The signal preprocessing service is used to: preprocess the digital intermediate frequency signal; The target detection and decoding service is used to: decode the digital intermediate frequency signal preprocessed by the signal preprocessing service and output target attribute information; The point aggregation service is used to: aggregate multiple original target points within the antenna scanning beamwidth into a unique point in the coordinate space based on the target attribute information, and output the aggregated target point trace. The track processing service is used to: preprocess the target point track to obtain track information and report the track information; The data fusion service is used to: fuse target tracks from multiple data sources / multiple secondary radars, and simultaneously smooth and filter the fused target tracks to output fused target trajectory information. The target classification and recognition service is used to: extract key attribute information of the target based on the target point traces and the target trajectory information, construct an attribute information database, and store targets of different categories into the corresponding databases; The data display service is used to display the target attribute information, target classification information, and target location information through a graphical interface.

4. The system according to claim 1, characterized in that, The service scheduling layer includes: a service registration and management module, a dynamic resource scheduling module, and a service monitoring module, wherein... The service registration and management module is used to: build a registration center platform, manage the address, status and interface information of all microservice instances, and support dynamic service discovery and communication; The dynamic resource scheduling module is used to: orchestrate based on software containers, design scheduling priorities based on the resources and priorities required by services and based on real-time levels, and dynamically adjust the service call priorities and hardware resource allocation; The service monitoring module is used to: monitor the running status and resource usage status of all microservices in real time, and report the status of all microservices.

5. The system according to claim 1, characterized in that, The application interface layer includes: a user interaction module, an external interface module, and a customized service module, wherein... The user interaction module is used to: provide standard APIs for upper-layer applications, and support upper-layer applications in configuring radar data processing parameters, obtaining system and microservice running status information, obtaining radar data processing results, and other information. The external interface module is used to: encapsulate external system interfaces and provide APIs for external system calls; The customized service module is used to: customize applications for specific scenarios and provide functional extensions and custom interfaces for upper-layer applications.

6. The system according to any one of claims 1 to 5, characterized in that, The system also includes a data bus, a service bus, and a control bus built at the system software level, wherein... The data bus is used to: realize the real-time transmission of massive radar data, support subscription / publish mode, and meet the needs of parallel data processing of multiple services. The service bus is used for: a base network transmission protocol, using a predetermined file format to transmit communication data, so as to realize synchronous / asynchronous communication and collaborative work between microservices; The control bus is used to transmit configuration commands, scheduling commands, and control commands based on a lightweight communication protocol.

7. The system according to claim 2, characterized in that, The dynamic resource scheduling module dynamically adjusts the service call priority and hardware resource allocation, including: reserving sufficient computing, storage and communication resources for core services and prohibiting other non-core services from occupying them; and dynamically sharing idle computing and storage resources for non-core services.

8. A software-based secondary radar data processing method based on microservices, characterized in that, The method includes: By using a hardware management layer, the differences in hardware architecture are shielded, and a unified application programming API interface is provided for upper-layer services. Through the data service layer, the entire data processing process of the secondary radar is decomposed into multiple independent microservices, and the data received through the API interface is processed based on the microservices. The service scheduling layer performs real-time monitoring and scheduling of various independent microservices in the data service layer. The application interface layer provides calling interfaces to upper-layer applications and interfaces with external systems to output data processed by various microservices received from the data service layer.

9. A software-based secondary radar data processing device based on microservices, characterized in that, The device includes: At least one processor; At least one memory coupled to the at least one processor and storing instructions for execution by the at least one processor, the instructions implementing the method of claim 8 when executed by the at least one processor.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed by a computer, cause the computer to perform the method of claim 8.

Images