Centralized monitoring system of measurement and control equipment

Abstract

The invention relates to a centralized monitoring system for measurement and control equipment, and the system comprises a first monitoring server which is used for receiving a work plan of central equipment, generating observation station tasks according to the tracking arc information of the central equipment, adding the observation station tasks into a scheduling queue, and carrying out the scheduling and execution of the observation station tasks at preset time; the second monitoring server is used for replacing the first monitoring server and executing the work of the first monitoring server when the first monitoring server is down; normal operation of an automatic process is ensured, and high-reliability execution of tasks is ensured.

Description

Technical Field

[0001] The present application relates to the field of aerospace measurement and control technology, and in particular to a centralized monitoring system for measurement and control equipment. Background Art

[0002] At present, the core operation process of domestic aerospace measurement and control is as follows: the measurement and control center uses the resource scheduling system to calculate the tracking targets and arcs of each station equipment according to the measurement and control requirements proposed by the user in the future (generally the next week), and generates a work plan for the measurement and control equipment during this period. The plan includes the start and end time of each tracking arc of a certain set of equipment, the working mode of the spacecraft and the planned arc type (remote control, telemetry, data transmission, etc.). The resource scheduling system automatically sends the plan to the measurement and control equipment of each station in the form of real-time data packets or XML at a fixed time.

[0003] After the measurement stations in various places receive the equipment work plan, the centralized monitoring system of the measurement and control equipment automatically reads and stores its own equipment plan into the local database, and adds it to the task scheduling queue, waiting for scheduling. The equipment loads the plan at a fixed time (usually 5 minutes) before the tracking start time specified in the plan, generates the equipment's macro parameter configuration and channel link configuration process, automatically initiates the ranging zero calibration sub-process (if necessary) according to the process configuration node, initiates the phase calibration sub-process (if necessary) after the satellite enters the station, and automatically tracks and captures the process, and drives the equipment to perform specific actions according to the time sequence specified by these fixed processes.

[0004] Although the current domestic spacecraft measurement and control equipment has been developed and evolved for decades and can already perform preliminary automated operations, the entire centralized monitoring system of the measurement and control equipment still has a single point failure problem, which will cause the automation to stop operating when a single point failure occurs. Summary of the invention

[0005] In view of the above problems, the present invention provides a centralized monitoring system for measurement and control equipment, which adds a master-slave device design to the original single-node centralized monitoring system for measurement and control equipment to ensure high reliability of the centralized monitoring system for measurement and control equipment.

[0006] The present application is implemented through the following technical solutions, a centralized monitoring system for measurement and control equipment, including:

[0007] The first monitoring server is used to receive the work plan of the central equipment, generate the station task according to the tracking arc information of the central equipment, add the station task to the scheduling queue, and schedule and execute the station task at a predetermined time;

[0008] The second monitoring server replaces the first monitoring server and performs the work of the first monitoring server when the first monitoring server goes down.

[0009] Preferably, the first monitoring server is also used to detect whether the working time of the central equipment work plan overlaps with the working time of other equipment work plans to be executed.

[0010] Preferably, when the working time of the central equipment work plan overlaps with the working time of other equipment work plans to be executed, the working time of the central equipment work plan covers the working time of other conflicting equipment work plans.

[0011] Preferably, when the working time of the central equipment work plan does not overlap with the working time of other equipment work plans to be executed, the central equipment work plan is inserted into the list of other equipment work plans.

[0012] Preferably, the method for determining whether the first monitoring server is down is to detect the operating status of the first monitoring server in real time and call the health check interface according to the set time interval. If there is no response for three consecutive times, it is determined that the first monitoring server is abnormal.

[0013] Preferably, detecting the operating status of the first monitoring server includes the operating status of the Mysql database or the operating status of Redis.

[0014] Preferably, set the time interval to 1-3 seconds.

[0015] Preferably, when the running status of the first monitoring server is the running status of the Mysql database, the Mysql database process monitoring script is called once every 3 seconds. If there is no response or process for more than 3 consecutive times, the first monitoring server is determined to be abnormal, and the second monitoring server replaces the first monitoring server and performs the work of the first monitoring server.

[0016] Preferably, when the running status of the first monitoring server is the running status of Redis, the Redis monitoring script is called once every 3 seconds. If there is no response or process for more than 3 consecutive times, the first monitoring server is judged to be abnormal, and the second monitoring server replaces the first monitoring server and performs the work of the first monitoring server.

[0017] The beneficial effects of this application are:

[0018] The present application designs a first monitoring server and a second monitoring server. The first monitoring server and the second monitoring server are master-slave devices to each other. When the devices start running, the first monitoring server is the master and the second monitoring server is the slave. When the first monitoring server goes down, the second monitoring server replaces the first monitoring server and performs the work of the first monitoring server to ensure the normal operation of the automation process and the high-reliability execution of the task. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.

[0020] Figure 1 It is a flow chart of a centralized monitoring system of a measurement and control device in an embodiment of the present invention. DETAILED DESCRIPTION

[0021] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be implemented in a variety of forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more comprehensive and complete and fully convey the concept of the example embodiments to those skilled in the art.

[0022] In addition, described feature, structure or characteristic can be combined in one or more embodiments in any suitable manner. In the following description, many specific details are provided so as to provide a full understanding of the embodiments of the present application. However, those skilled in the art will appreciate that the technical scheme of the present application can be put into practice without one or more of the specific details, or other methods, components, devices, steps, etc. can be adopted. In other cases, known methods, systems, implementations or operations are not shown or described in detail to avoid blurring the various aspects of the application.

[0023] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities may be implemented in software form, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0024] The flowcharts shown in the accompanying drawings are only exemplary and do not necessarily include all the contents and operations / steps, nor must they be executed in the order described. For example, some operations / steps can be decomposed, and some operations / steps can be combined or partially combined, so the actual execution order may change according to actual conditions.

[0025] like Figure 1 A centralized monitoring system for measurement and control equipment is shown, comprising:

[0026] The first monitoring server is used to receive the work plan of the central equipment, generate the station task according to the tracking arc information of the central equipment, add the station task to the scheduling queue, and schedule and execute the station task at a predetermined time;

[0027] The second monitoring server replaces the first monitoring server and performs the work of the first monitoring server when the first monitoring server goes down.

[0028] In this embodiment, when in use, the first monitoring server is the host and the second monitoring server is the backup server. The first monitoring server is used to receive the equipment tracking segment and generate the equipment work plan according to the equipment tracking segment; the equipment work plan issued by the measurement and operation control center is parsed into a measurement station task, added to the task scheduling queue, and returned to the measurement and operation control center for response; if it is a normal plan, the equipment work plan is returned for normal execution; if the verification plan is abnormal, it is returned to the measurement and operation control center as abnormal information; the first monitoring server and the second monitoring server monitor each other's status in real time through heartbeats. Once the first monitoring server (host) is abnormal, the second monitoring server (backup) takes over the host and continues to work, thereby avoiding the single point failure problem of the centralized monitoring system of the measurement and control equipment; the automated operation process of the core functions of the measurement and operation control can also be realized through the master-slave device design to achieve relay execution, thereby ensuring high-reliability execution of the task.

[0029] In this embodiment, the first monitoring server and the second monitoring server monitor the running status of the Redis database and the Mysql database, and provide preconditions for switching the master machine and the backup machine according to the running status.

[0030] Specifically, the running status of the first monitoring server is monitored, and the health check interface is called according to the set time interval. If no response occurs for three consecutive times, it is determined that an abnormality occurs in the first monitoring server;

[0031] In one embodiment, when monitoring the first monitoring server, the running status of the Mysql database in the first monitoring server is actually monitored, and the Mysql database process monitoring script is called at a specified time interval (3 seconds / time). If there is no response or the process status is abnormal for more than 3 consecutive times, the Mysql database service is determined to be abnormal, and Keepalived is notified to downgrade the current host to a backup machine, and the original backup machine is upgraded to the host. At the same time, the Mysql databases of the two monitoring servers are synchronized in real time in both directions, thereby ensuring that the status of the centralized monitoring system of the two sets of measurement and control equipment is consistent.

[0032] In another embodiment, when monitoring the second detection server, the running status of Redis is monitored, and the Redis check script is called at a specified time interval (3 seconds / time). If there is no response or the process is abnormal for more than 3 consecutive times, it is determined that the Redis service is running abnormally, and Keepalived is notified to downgrade the current host to a backup machine, and the original backup machine is upgraded to the host.

[0033] When switching between the master and standby machines of the two detection servers, in order not to affect the relay execution of the automated process, all node information of the process will be initialized in the database before the automated process starts, and the process execution node status will be kept as unexecuted, and the standby database table will be updated through the dual-master real-time synchronization of the MySQL database. The two servers will execute the automated process at the same time. The master-slave device design can ensure that only the host can send control instructions to the device, and the standby only monitors the status of the host's running nodes. If the host does not execute the node, the standby will temporarily wait for the host to execute. If the role is switched, that is, the host is downgraded to the standby, and the standby is upgraded to the host, the role will be switched to ensure the normal operation of the automated process.

[0034] In another embodiment, the first monitoring server is further used to detect whether the working time of the central equipment work plan overlaps with the working time of other equipment work plans to be executed.

[0035] When the working time of the central equipment work plan overlaps with the working time of other equipment work plans to be executed, the working time of the central equipment work plan covers the working time of other conflicting equipment work plans.

[0036] When the working time of the central equipment work plan does not overlap with the working time of other equipment work plans to be executed, the central equipment work plan is inserted into the list of other equipment work plans.

[0037] In another embodiment, since the current domestic spacecraft measurement and control equipment receives the equipment work plan of the measurement and control center, and uses binary format or text for plan interaction, considering the development of measurement and control services, such as the overlapping of multi-station tracking arcs requires relay measurement and control, and the need to change the receiving downlink data code rate during tracking, etc. The binary format or text format can no longer meet the development of measurement and control services, and in this embodiment, the original binary format and text format are replaced by XML format to meet current business needs, so the equipment work plan in this application is in XML format.

[0038] The monitoring server can generate a one-day or multi-day equipment work plan based on the received equipment tracking arc segment arrangement, and send it to the equipment-side server in the form of an XML file.

[0039] Among them, when arranging the work plan of the equipment, it can be shown as follows:

[0040]

[0041]

[0042]

[0043]

[0044]

[0045]

[0046] After receiving the equipment work plan, the device-side server parses and saves it, generates an equipment work plan response, and sends it to the measurement and operation control center server in the form of a file.

[0047] The equipment work plan response format is as follows:

[0048] <? xml version="1.0" encoding="UTF-8"? >

[0049] <equipmentplancon><! --Confirmation of equipment related documents [equipment work plan | equipment working parameters | equipment work flow] -->

[0050] <filename> 01_TCLS9_TCBC_OP_F10_20200508_162408_0005.XML< / filename> <!--File Name-->

[0051] <planno> MH3101-DWP-20200508-20200508-1< / planno> <!--Plan Number-->

[0052] <constatus> 0001002< / constatus> <! --Confirmation status 0001001 valid 0001002 invalid -->

[0053] <constatusname> invalid< / constatusname> <! --Confirm the Chinese name of the status -->

[0054] <invaildreason> Incorrect format< / invaildreason> <! --Invalid reason If valid, there is no such node -->

[0055] <timesystem> BST< / timesystem> <!--Time System-->

[0056] <createtime> 20200508102101< / createtime> <!-- Creation Time -->

[0057] < / equipmentplancon>

[0058] Keepalived master-slave device design configuration script information, one is to ensure the normal operation of Keepalived, the other is to monitor the middleware and regularly call the monitoring interface of the centralized monitoring system of the measurement and control equipment. The configuration information is as follows:

[0059]

[0060]

[0061]

[0062] Among them, check_alive.sh is a process and interface calling script, which is used to monitor the middleware of the two servers and the survival status of the centralized monitoring system of the measurement and control equipment in real time. The script information is as follows:

[0063]

[0064]

[0065] In one embodiment, when the monitoring server of the measurement and operation control equipment detects that the current working state is "automatic", the monitoring server 1 and the monitoring server 2 automatically monitor and switch the active and standby states during the process automation operation. When the device-side server detects that the current working state is "manual", it does not automatically switch between active and standby states, but the active and standby states are manually switched by the equipment personnel.

[0066] The solution in this embodiment fully meets the current business and development needs, and meets the business needs of the master and slave devices for at least 5 to 10 years. The centralized monitoring system of the measurement and control equipment adopts parameterized configuration, through which the working plan of the equipment, automatic or manual switching of the master and standby can be flexibly set, the program does not need to be changed, and maintenance is convenient.

[0067] Those skilled in the art will readily appreciate other embodiments of the present application after considering the specification and practicing the embodiments disclosed herein. The present application is intended to cover any variations, uses or adaptations of the present application, which follow the general principles of the present application and include common knowledge or customary technical means in the art that are not disclosed in the present application.

[0068] It should be understood that the present application is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present application is limited only by the appended claims.

Claims

1. A centralized monitoring system for measurement and control equipment, characterized in that: include: The first monitoring server is used to receive the work plan of the central equipment, generate the station task according to the tracking arc information of the central equipment, add the station task to the scheduling queue, and schedule and execute the station task at a predetermined time; The second monitoring server, when the first monitoring server goes down, the second monitoring server replaces the first monitoring server and performs the work of the first monitoring server.

2. The centralized monitoring system for measurement and control equipment according to claim 1, characterized in that: The first monitoring server is also used to detect whether the working time of the central equipment work plan overlaps with the working time of other equipment work plans to be executed.

3. The centralized monitoring system for measurement and control equipment according to claim 2, characterized in that: When the working time of the central equipment work plan overlaps with the working time of other equipment work plans to be executed, the working time of the central equipment work plan covers the working time of other conflicting equipment work plans.

4. A centralized monitoring system for measurement and control equipment according to claim 2 or 3, characterized in that: When the working time of the central equipment work plan does not overlap with the working time of other equipment work plans to be executed, the central equipment work plan is inserted into the list of other equipment work plans.

5. The centralized monitoring system for measurement and control equipment according to claim 1, characterized in that: The method for determining whether the first monitoring server is down is to monitor the running status of the first monitoring server and call the health check interface according to the set time interval. If there is no response for three consecutive times, it is determined that the first monitoring server is abnormal.

6. The centralized monitoring system for measurement and control equipment according to claim 5, characterized in that: Detecting the operating status of the first monitoring server includes monitoring the operating status of a Mysql database or the operating status of a Redis database.

7. A centralized monitoring system for measurement and control equipment according to claim 6, characterized in that: The set time interval is 1-3 seconds.

8. The centralized monitoring system for measurement and control equipment according to claim 7, characterized in that: When monitoring the running status of the Mysql database, the Mysql database process monitoring script is called once every 3 seconds. If there is no response or process for more than 3 consecutive times, the first detection server is determined to be abnormal, and the second monitoring server replaces the first monitoring server and performs the work of the first monitoring server.

9. The centralized monitoring system for measurement and control equipment according to claim 7, characterized in that: When detecting the running status of the Redis database, the Redis database monitoring script is called once every 3 seconds. If there is no response or process for more than 3 consecutive times, the first detection server is judged to be abnormal, and the second monitoring server replaces the first monitoring server and performs the work of the first monitoring server.

Images