GNSS reference station server and resource management method thereof

Abstract

This application discloses a GNSS reference station server and its resource management method. The GNSS reference station server includes embedded hardware and multiple GNSS boards. The embedded hardware includes a CPU, storage medium, network interface card (NIC), and multiple physical interfaces. The method includes: periodically polling the connection between the embedded hardware and the GNSS boards to obtain the version information of the connected GNSS boards; determining the communication protocol dependencies and data broadcasting programs of the connected GNSS boards based on the version information; creating process isolation spaces corresponding to the communication protocol dependencies and data broadcasting programs of the GNSS boards; allocating CPU and storage medium resources to the process isolation space and limiting the resources used by the communication protocol dependencies and data broadcasting programs within the process isolation space to no more than the allocated resources; connecting to the corresponding GNSS boards through the communication protocol dependencies within the process isolation space to obtain GNSS data, and broadcasting the GNSS data through the NIC using the corresponding data broadcasting program.

Description

Technical Field

[0001] This application relates to the field of satellite navigation technology, and in particular to a GNSS reference station server and its resource management method. Background Technology

[0002] In the field of Global Navigation Satellite System (GNSS), the Continuously Operating Reference Stations (CORS) system is a network system that utilizes computer technology, modern communication technology, data communication, and the Internet (LAN / WAN) to automatically provide real-time, verified GPS / GNSS observations (carrier phase, pseudorange), various corrections, status information, and other relevant GNSS services to users of different types, needs, and levels. It provides dynamic, high-precision positioning and continuous spatial framing services for various industry applications, and has become an indispensable spatial information infrastructure for cities, regions, and nations.

[0003] Traditional CORS receivers use a single GNSS board. A failure in one GNSS board can cause the entire base station to fail, impacting the entire CORS system. Therefore, a new type of multi-GNSS board reference station server has emerged. This server manages multiple GNSS boards, each independently outputting raw observation data. If one GNSS board fails, data from other boards can be used, providing multi-active functionality. Furthermore, when observation data from all boards is available, the data can be compared and the optimal data selected. However, multi-GNSS board reference station servers still face challenges related to internal resource allocation and inter-module interference, leading to poor stability and continuity, which in turn affects the stability of the entire CORS network. Summary of the Invention

[0004] The purpose of this application is to provide a GNSS reference station server and its resource management method to avoid mutual interference between various GNSS boards and improve system stability.

[0005] One embodiment of this application discloses a resource management method for a GNSS reference station server. The GNSS reference station server includes embedded hardware and multiple GNSS cards. The embedded hardware includes a CPU, a storage medium, a network card, and multiple physical interfaces. The multiple GNSS cards are used to connect to the physical interfaces. The method includes:

[0006] The connection between the embedded hardware and the multiple GNSS boards is periodically polled to obtain the version information of the multiple connected GNSS boards;

[0007] Based on the version information, determine the communication protocol dependencies and data broadcasting programs of the multiple GNSS boards connected, and create process isolation spaces for each of the communication protocol dependencies and data broadcasting programs corresponding to the multiple GNSS boards.

[0008] Allocate CPU and storage medium resources to the process isolation space and limit the resources used by communication protocol dependencies and data broadcasting programs within the process isolation space to no more than the allocated resources;

[0009] The GNSS data is obtained by connecting to the corresponding GNSS board through the communication protocol dependency in the process isolation space, and the GNSS data is broadcast through the network card through the corresponding data broadcasting program.

[0010] In a preferred embodiment, the method further includes: when one of the GNSS boards is upgraded or fails, restarting the GNSS board and the communication protocol dependencies and data broadcasting programs in the process isolation space corresponding to the GNSS board, while the communication protocol dependencies and data broadcasting programs corresponding to the other GNSS boards continue to run in their respective process isolation spaces.

[0011] In a preferred embodiment, when identifying the GNSS card inserted into the reference station server, a pair of virtual network cards are created on the reference station server, one of which is placed in the created process isolation space, and the other is placed in the operating system of the embedded hardware.

[0012] In a preferred embodiment, when the GNSS board is identified as being removed, the process isolation space corresponding to the GNSS board is deleted and the corresponding allocated CPU and storage media resources are released.

[0013] In a preferred embodiment, the method further includes: creating a mirror template set, wherein each mirror template in the mirror template set includes a communication protocol dependency template and a data broadcasting program template corresponding to the version information of a GNSS board;

[0014] During the process of creating a process isolation space for the communication protocol dependencies and data broadcasting program corresponding to the GNSS board, the applicable image template is determined based on the obtained version information in the image template set, and the corresponding communication protocol dependency template and data broadcasting program template are copied into the process isolation space.

[0015] In a preferred embodiment, the version information includes the software version, hardware version, and SN serial number of the GNSS board.

[0016] In a preferred embodiment, the version information and corresponding communication protocol dependencies of the plurality of GNSS boards are different.

[0017] In a preferred embodiment, the GNSS reference station server further includes an operating system corresponding to the embedded hardware.

[0018] Another embodiment of this application discloses a GNSS reference station server, including: embedded hardware and multiple GNSS boards, wherein the embedded hardware includes a CPU, a storage medium, a network card, and multiple physical interfaces, wherein the multiple GNSS boards are used to connect to the physical interfaces; and further includes:

[0019] The polling module is used to periodically poll the connection between the embedded hardware and the multiple GNSS boards to obtain the version information of the multiple connected GNSS boards;

[0020] The process isolation space creation module is used to determine the communication protocol dependencies and data broadcasting programs of the multiple GNSS boards connected according to the version information, and to create process isolation spaces for each of the communication protocol dependencies and data broadcasting programs corresponding to the multiple GNSS boards.

[0021] The allocation module is used to allocate CPU and storage medium resources to the process isolation space and limit the resources used by communication protocol dependencies and data broadcasting programs within the process isolation space to no more than the allocated resources.

[0022] The broadcast module is used to connect to the corresponding GNSS board through the communication protocol dependency in the process isolation space to obtain GNSS data, and broadcast the GNSS data through the network card through the corresponding data broadcasting program.

[0023] One embodiment of this application also discloses a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the method described above.

[0024] This patent proposes a GNSS reference station server and its resource management method, which has at least the following beneficial effects:

[0025] This invention can detect the hardware status of a multi-GNSS board reference station server. Based on the hardware status, it creates a container environment, packaging each GNSS board, its corresponding dependencies, and broadcast application processes into a unified container. The reference station server directly manages each container, and the containers are independent of each other, avoiding coupling between different GNSS boards and processes running within the reference station server, thus enhancing system stability.

[0026] The specification of this application contains numerous technical features distributed across various technical solutions. Listing all possible combinations of these technical features (i.e., technical solutions) would make the specification excessively lengthy. To avoid this problem, the various technical features disclosed in the above-described invention, the various technical features disclosed in the following embodiments and examples, and the various technical features disclosed in the accompanying drawings can be freely combined to form various new technical solutions (all of which are considered to have been described in this specification), unless such a combination of technical features is technically infeasible. For example, one example discloses feature A+B+C, and another example discloses feature A+B+D+E. Features C and D are equivalent technical means that serve the same function, and technically only one needs to be used; they cannot be used simultaneously. Feature E can technically be combined with feature C. Therefore, the solution A+B+C+D should not be considered as described because it is technically infeasible, while the solution A+B+C+E should be considered as described. Attached Figure Description

[0027] Figure 1 This is a schematic diagram of the structure of a GNSS reference station server according to one embodiment of this application.

[0028] Figure 2 This is a flowchart illustrating a resource management method for a GNSS reference station server according to one embodiment of this application.

[0029] Figure 3 This is a schematic diagram illustrating the operation of a GNSS reference station server according to one embodiment of this application; Detailed Implementation

[0030] In the following description, many technical details are presented to help the reader better understand this application. However, those skilled in the art will understand that the technical solutions claimed in this application can be implemented even without these technical details and various variations and modifications based on the following embodiments.

[0031] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0032] Explanation of some terms:

[0033] Reference station server: A reference station server is a fixed ground-based observation station server that performs long-term, continuous observations of satellite navigation signals and transmits the observation data to the data center in real time or at regular intervals via communication facilities. It possesses the capabilities to observe satellite signals, transmit data, and perform edge computing. Reference stations are generally also called base stations, and the concepts are equivalent.

[0034] Continuously Operating Reference Stations (CORS) is a geospatial information infrastructure consisting of reference stations equipped with GNSS receivers and other equipment, communication systems, and data processing centers distributed across different areas. It is a system that continuously tracks and receives satellite signals, aggregates raw observation data, and processes it to obtain various data products such as satellite orbit, clock bias, carrier phase correction, and pseudorange correction.

[0035] Containerization (Dockerizing): Essentially, containerization is the process of packaging an application, its runtime environment, and dependencies into a single package, which can then be installed, moved, and deleted together. The environment provided by a container is independent of each running program and does not affect the existing system.

[0036] Image: A file storage format, a type of redundancy, where data on one disk has an exact copy on another disk.

[0037] Decoupling: Reducing coupling can be understood as decoupling. Dependencies between modules inevitably lead to coupling. Theoretically, absolute zero coupling is impossible, but existing methods can be used to minimize coupling.

[0038] Edge computing refers to an open platform that integrates network, computing, storage, and application capabilities, located close to the source of objects or data, to provide services at the nearest edge. Applications originate at the edge, resulting in faster network service responses and meeting the industry's basic needs in real-time business, application intelligence, security, and privacy protection. Edge computing sits between physical entities and industrial connections, or at the top of physical entities. Cloud computing can still access historical data from edge computing.

[0039] Application Programming Interface (API): These are predefined interfaces (such as functions or HTTP interfaces), or conventions for connecting different components of a software system. They provide applications and developers with a set of routines accessible to them based on certain software or hardware, without requiring access to the source code or understanding of the details of the internal workings.

[0040] The innovation of this invention lies in:

[0041] Existing multi-GNSS reference station servers directly manage GNSS cards and hardware / software resources on the operating system. Different GNSS cards, modules, and processes within these servers are interdependent; failures of any module or process can lead to instability or epochal interruptions for the entire server. Therefore, this invention proposes containerizing the reference station server application, enabling the server to possess elastic resource management capabilities, application deployment capabilities within seconds, and decoupling capabilities between modules and GNSS cards, ensuring the stability and reliability of the entire system during operation and maintenance.

[0042] One embodiment of this application discloses a GNSS reference station server. Figure 1 A block diagram of a GNSS reference server 100 is shown. (As shown...) Figure 1 As shown, the GNSS reference station server 100 includes embedded hardware 110 and multiple GNSS boards 113.1-113.N. The embedded hardware 110 includes a processor (CPU or MCU), storage media (e.g., memory), a network interface card (NIC), and multiple physical interfaces. The multiple GNSS boards 113.1-113.N are used to connect to the physical interfaces. In one embodiment, the GNSS reference station server 100 also includes an operating system 130 corresponding to the embedded hardware 110. In one embodiment, basic services 140 can also run on the operating system to manage the multiple GNSS boards 113.1-113.N.

[0043] One embodiment of this application discloses Figure 1 The resource management method of the GNSS reference station server is shown. Figure 2 A flowchart illustrating the resource management method of the GNSS reference station server is shown, the method comprising the following steps:

[0044] Step 210: Periodically poll the connection between the embedded hardware 110 and the plurality of GNSS boards 113.1-113.N to obtain the version information of the connected GNSS boards 113.1-113.N. In one embodiment, the version information includes the software version, hardware version, and SN serial number of the GNSS boards 113.1-113.N.

[0045] Step 220: Determine the communication protocol dependencies and data broadcasting programs of the multiple GNSS boards 113.1-113.N connected according to the version information, and create process isolation spaces (or containers) for each of the communication protocol dependencies and data broadcasting programs corresponding to the multiple GNSS boards. That is, containerize the GNSS boards and their corresponding dependencies and broadcasting applications, and package them into their respective containers.

[0046] For example, for the first GNSS board 113.1, a process isolation space 120.1 (or container 1) is created for GNSS board 113.1, its corresponding communication protocol dependency 112.1, and data broadcasting program 111.1. For the first GNSS board 113.2, a process isolation space 120.2 (or container 2) is created for GNSS board 113.2, its corresponding communication protocol dependency 112.2, and data broadcasting program 111.2, and so on. For the Nth GNSS board 113.N, a process isolation space 120.N (or container N) is created for GNSS board 113.N, its corresponding communication protocol dependency 112.N, and data broadcasting program 111.N. In one embodiment, the version information of the plurality of GNSS boards 113.1-113.N and their corresponding communication protocol dependencies 112.1-112.N are different.

[0047] Step 230: Allocate CPU and storage medium resources to the process isolation space 120.1-120.N and limit the resources used by the communication protocol dependencies 112.1-112.N and the data broadcasting program 111.1-111.N within the process isolation space 120.1-120.N to no more than the allocated resources.

[0048] Step 240: Connect to the corresponding GNSS board 113.1-113.N through the communication protocol dependency 112.1-112.N in the process isolation space 120.1-120.N to obtain GNSS data, and broadcast the GNSS data through the network card through the corresponding data broadcasting program 111.1-111.N.

[0049] In one embodiment, the resource management method further includes: when one of the GNSS boards is upgraded or fails, restarting the GNSS board and the communication protocol dependencies and data broadcasting programs in the process isolation space corresponding to the GNSS board; the communication protocol dependencies and data broadcasting programs corresponding to other GNSS boards continue to run in their respective process isolation spaces. For example, when the GNSS board 113.1 in process isolation space 120.1 fails, restarting the GNSS board 113.1 and the corresponding communication protocol dependencies 112.1 and data broadcasting program 111.1 in process isolation space 120.1 does not affect the operation of the GNSS boards 113.2 and 113.N and the corresponding communication protocol dependencies 112.2 and 112.N and data broadcasting programs 111.2 and 111.N in other process isolation spaces 120.2 and 120.N.

[0050] This application can intelligently identify GNSS cards and realize dynamic management of GNSS cards. In one embodiment, when a GNSS card is inserted into the reference station server 100, a pair of virtual network cards are created on the reference station server. One virtual network card is placed in the created process isolation space, and the other virtual network card is placed in the operating system of the embedded hardware. In one embodiment, when the GNSS card is removed, the process isolation space corresponding to the GNSS card is deleted, and the corresponding allocated CPU and storage media resources are released.

[0051] In one embodiment, the resource management method further includes: creating a set of image templates, each image template in the set including a communication protocol dependency template and a data broadcasting program template corresponding to the version information of a GNSS board. During the process of creating a process isolation space for the communication protocol dependencies and data broadcasting program corresponding to the GNSS board, an applicable image template is determined from the set of image templates based on the acquired version information, and the corresponding communication protocol dependency template and data broadcasting program template are copied into the process isolation space.

[0052] The containerized deployment of the reference server used in this application has the advantages of being extremely lightweight, deploying in seconds, easy to port, and elastically scalable. It also ensures consistency between the testing and production environments.

[0053] The second embodiment of this application relates to a GNSS reference station server, comprising: embedded hardware and multiple GNSS boards. The embedded hardware includes a CPU, a storage medium, a network interface card (NIC), and multiple physical interfaces. The multiple GNSS boards are used to connect to the physical interfaces. The GNSS reference station server further includes a polling module, a process isolation space creation module, an allocation module, and a broadcast module.

[0054] The polling module is used to periodically poll the connection between the embedded hardware and the multiple GNSS boards to obtain the version information of the multiple connected GNSS boards.

[0055] The process isolation space creation module is used to determine the communication protocol dependencies and data broadcasting programs of the multiple GNSS boards connected based on the version information, and to create process isolation spaces for each of the communication protocol dependencies and data broadcasting programs corresponding to the multiple GNSS boards.

[0056] The allocation module is used to allocate CPU and storage medium resources to the process isolation space and limit the resources used by communication protocol dependencies and data broadcasting programs within the process isolation space to no more than the allocated resources.

[0057] The broadcast module is used to connect to the corresponding GNSS board through the communication protocol dependency in the process isolation space to obtain GNSS data, and broadcast the GNSS data through the network card through the corresponding data broadcasting program.

[0058] The first embodiment is a method embodiment corresponding to this embodiment. The technical details in the first embodiment can be applied to this embodiment, and the technical details in this embodiment can also be applied to the first embodiment.

[0059] It should be noted that those skilled in the art should understand that the implementation functions of each module shown in the above-described GNSS reference station server implementation can be understood with reference to the relevant description of the resource management method of the above-described GNSS reference station server. The functions of each module shown in the above-described GNSS reference station server implementation can be implemented by a program (executable instructions) running on a processor, or by specific logic circuits. If the above-described GNSS reference station server in this application embodiment is implemented in the form of software functional modules and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application embodiment, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes: USB flash drive, mobile hard drive, read-only memory (ROM), magnetic disk, or optical disk, and other media that can store program code. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0060] To better understand the technical solution in this specification, a specific example is provided below. The details listed in this example are mainly for ease of understanding and are not intended to limit the scope of protection of this application.

[0061] The reference station server integrates multiple GNSS boards, fiber optic terminals, firewalls, backup power supplies, and other equipment, possessing features not found in traditional base station equipment, such as a multi-redundant complete system, cloud-integrated collaboration, and data application capabilities. Multiple GNSS board redundancy, multiple network redundancy, and multiple power supply redundancy are used to ensure the reference station server's data availability, network link reliability, and power reliability, thereby guaranteeing uninterrupted data transmission.

[0062] During operation, the reference station server consists of a series of different processes controlling and collecting data from various GNSS boards. Simultaneously, as a server suitable for edge computing, it also runs processes performing computational tasks. These processes share CPU and memory resources. When edge computing processes or GNSS board-related processes consume excessive CPU or memory, or when other malfunctions occur, they may preempt CPU or memory resources from other board processes, causing integrated equipment failure. In the most extreme case, if the program is poorly designed, a process entering an infinite loop might exhaust CPU resources, or a memory leak might consume most of the system resources, ultimately rendering the entire reference station server unusable.

[0063] Meanwhile, there are also issues of mutual interference between different GNSS boards. When a GNSS board needs to be upgraded and restarted, the entire system is usually restarted, causing other normally functioning GNSS boards to also restart, resulting in epoch interruptions and affecting the overall operation of the system.

[0064] Therefore, this invention aims to solve the above two problems by managing the reference station server in a containerized manner, ultimately achieving the goals of decoupling (non-interference) of multiple GNSS boards in the reference station server, elastic resource management, and stable operation.

[0065] refer to Figure 1 As shown, the lowest layer of the reference server architecture is embedded hardware 110, including a CPU (MCU), memory, disk, network card, and various physical interfaces. Above this hardware runs a Linux operating system 130; the Linux kernel version here must be V3.8 or higher. Kernel compilation requires activating features such as namespaces, Cggroups, netfilter, and veth, and also has dependencies on tools such as iptablesst.

[0066] The following table lists the Linux versions that began supporting each namespace:

[0067] namespace System call parameters Quarantine content kernel version UTS CLONE_NEWUTS Hostname and domain name 2.6.19 IPC CLONE_NEWIPC Semaphores, message queues, and shared memory 2.6.19 PID CLONE_NEWPID Process number 2.6.24 Network CLONE_NEWNET Network devices, network stack, ports, etc. 2.6.29 Mount CLONE_NEWNS Mount point (file system) 2.4.19 User CLONE_NEWUSER Users and user groups 3.8

[0068] Above the operating system, a basic service 140 runs. This service detects changes in GNSS board hardware, dynamically manages containers, and safeguards the applications running within them. Linux communicates with containers using a bridge. A pair of virtual network interface (veth) devices are created on the host. When a new container is created, one end of the virtual network interface is placed into the new container and named eth0 (the container's network interface), while the other end is placed into the operating system and named vethxxxx. This veth device is then placed into container0, which acts as the network bridge.

[0069] The top layer consists of containers managed by basic services. A single reference station server runs multiple logically isolated containers, meaning a single physical reference station server virtualizes multiple container environments. Each container runs its own GNSS-related processes. These processes run independently, with each GNSS board running in a separate container. GNSS boards do not interfere with each other, and container resources have upper limits. Abnormalities in processes or resources within a container will not affect the processes or resources of other containers or the entire machine.

[0070] The operating system can intelligently identify GNSS cards through underlying services and create ways to enter containers. The operating system allows applications on each card to run as if they were on independent machines, but can still share underlying resources.

[0071] Furthermore, the implementation of a multi-board GNSS reference station server based on the Linux system requires not only container management but also the creation of image templates and the establishment of an image repository.

[0072] refer to Figure 3 As shown, after the reference station server is powered on, it runs the operating system and automatically starts basic services. The basic services dynamically manage containers by detecting the hot-swapping of GNSS boards.

[0073] 1. Testing method for hot-swapping GNSS boards (plug-in boards)

[0074] The basic service periodically polls to check the connectivity between the interface and the specific network port of the GNSS board. If the GNSS board is confirmed to be connected, a command is sent to obtain the GNSS board version information. The version information includes the GNSS board's hardware and software version, SN number, and other information to confirm whether the board has been plugged in, unplugged, or replaced.

[0075] 2. Container Dynamic Management Methods

[0076] The basic services implement dynamic container management, providing a dynamic management API. When the basic services detect changes to the GNSS board, they run automated scripts to call the API for dynamic container management. A container is a running instance created from an image. It can be started, stopped, and deleted. Each container is an isolated and secure platform. Each container can be viewed as a simplified Linux environment (including root user privileges, process space, user space, and network space) and the application running within it. The container management commands are detailed below:

[0077] The command to create a container is `container create`. <image-id>

[0078] The `container create` command adds a read-write layer to a specified image, creating a new container. The `container create` command provides many parameter options to specify the name, hardware resources, network configuration, and more.

[0079] The command to start a container is `container start`. <container-id>

[0080] The container start command creates a process-isolated space for the container file system.

[0081] Enter the container using the command `container exec`. <container-id>

[0082] Executing a new command in the current container, if you add the -it parameter to run bash, will have the same effect as logging into the container.

[0083] The command to stop a container is `container stop`. <container-id>

[0084] The command to delete a container is `container rm`. <container-id>

[0085] Run the container command: container run <image-id>

[0086] `container run` is a combination of the `container create` and `container start` commands, and they support the same parameters. If you specify a container name that already exists, it will throw an error. You can add the `--rm` parameter to make the container automatically deleted when it exits.

[0087] The command to view the list of containers is `container ps`.

[0088] The `ps` command lists all running containers. This hides the existence of non-running containers. To find these containers, add the `-a` parameter.

[0089] The command to delete an image is container rmi. <image-id>

[0090] Accordingly, embodiments of this application also provide a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, implement the various method embodiments of this application. Computer-readable storage media include permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, 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 technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device. As defined herein, computer-readable storage media does not include transient media, such as modulated data signals and carrier waves.

[0091] It should be noted that in this patent application, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one" does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element. In this patent application, if it refers to performing an action according to an element, it means performing the action at least according to that element, including two cases: performing the action only according to that element, and performing the action according to that element and other elements. Expressions such as "multiple," "repeatedly," and "various" include two, two times, two kinds, and more than two, more than two times, and more than two kinds.

[0092] All references to this application are considered to be incorporated in their entirety into the disclosure of this application so that they can serve as a basis for modifications if necessary. Furthermore, it should be understood that after reading the foregoing disclosure of this application, those skilled in the art can make various alterations or modifications to this application, and these equivalent forms also fall within the scope of protection claimed in this application.

Claims

1. A resource management method for a GNSS reference station server, characterized in that, The GNSS reference station server includes embedded hardware and multiple GNSS cards. The embedded hardware includes a CPU, storage medium, network interface card (NIC), and multiple physical interfaces. The multiple GNSS cards are used to connect to the physical interfaces. The method includes: The connection between the embedded hardware and the multiple GNSS boards is periodically polled to obtain the version information of the multiple connected GNSS boards; Based on the version information, determine the communication protocol dependencies and data broadcasting programs of the multiple GNSS boards connected, and create process isolation spaces for each of the communication protocol dependencies and data broadcasting programs corresponding to the multiple GNSS boards. Allocate CPU and storage medium resources to the process isolation space and limit the resources used by communication protocol dependencies and data broadcasting programs within the process isolation space to no more than the allocated resources; The GNSS data is obtained by connecting to the corresponding GNSS board through the communication protocol dependency in the process isolation space, and the GNSS data is broadcast through the network card through the corresponding data broadcasting program.

2. The resource management method for a GNSS reference station server according to claim 1, characterized in that, Also includes: When one of the GNSS boards is upgraded or fails, the communication protocol dependencies and data broadcasting programs of that GNSS board and its corresponding process isolation space are restarted. The communication protocol dependencies and data broadcasting programs of the other GNSS boards continue to run in their respective process isolation spaces.

3. The resource management method for a GNSS reference station server according to claim 2, characterized in that, When identifying the GNSS card inserted into the reference station server, a pair of virtual network cards are created on the reference station server. One virtual network card is placed in the created process isolation space, and the other virtual network card is placed in the operating system of the embedded hardware.

4. The resource management method for a GNSS reference station server according to claim 1, characterized in that, When the GNSS board is removed, the process isolation space corresponding to the GNSS board is deleted and the corresponding allocated CPU and storage media resources are released.

5. The resource management method for a GNSS reference station server according to claim 1, characterized in that, Also includes: Create a set of mirror templates, wherein each mirror template in the set includes a communication protocol dependency template and a data broadcasting program template corresponding to the version information of a GNSS board; During the process of creating a process isolation space for the communication protocol dependencies and data broadcasting program corresponding to the GNSS board, the applicable image template is determined based on the obtained version information in the image template set, and the corresponding communication protocol dependency template and data broadcasting program template are copied into the process isolation space.

6. The resource management method for a GNSS reference station server according to claim 1, characterized in that, The version information includes the software version, hardware version, and SN serial number of the GNSS board.

7. The resource management method for a GNSS reference station server according to claim 1, characterized in that, The version information and corresponding communication protocol dependencies of the multiple GNSS boards are different.

8. The resource management method for a GNSS reference station server according to claim 1, characterized in that, The GNSS reference station server also includes an operating system corresponding to the embedded hardware.

9. A GNSS reference station server, characterized in that, include: Embedded hardware and multiple GNSS boards, the embedded hardware including a CPU, storage medium, network interface card (NIC), and multiple physical interfaces, wherein the multiple GNSS boards are used to connect to the physical interfaces; further comprising: The polling module is used to periodically poll the connection between the embedded hardware and the multiple GNSS boards to obtain the version information of the multiple connected GNSS boards; The process isolation space creation module is used to determine the communication protocol dependencies and data broadcasting programs of the multiple GNSS boards connected according to the version information, and to create process isolation spaces for each of the communication protocol dependencies and data broadcasting programs corresponding to the multiple GNSS boards. The allocation module is used to allocate CPU and storage medium resources to the process isolation space and limit the resources used by communication protocol dependencies and data broadcasting programs within the process isolation space to no more than the allocated resources. The broadcast module is used to connect to the corresponding GNSS board through the communication protocol dependency in the process isolation space to obtain GNSS data, and broadcast the GNSS data through the network card through the corresponding data broadcasting program.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when executed by a processor, implement the steps of the method as described in any one of claims 1 to 8.

Images