A distributed multi-node coordinated disaster recovery Beidou communication system

Abstract

The present invention belongs to the field of communication technology, and more specifically, it relates to a distributed multi-node coordinated disaster recovery Beidou communication system, wherein the Beidou communication system is based on Beidou satellites and Beidou communication equipment communicating with each other, wherein the Beidou communication system includes a number of Beidou communication front-end service subsystems and coordination and scheduling subsystems: the coordination and scheduling subsystem includes a database and a front-end scheduling service connected to the database, and a main control unit for disaster recovery scheduling of the Beidou communication front-end subsystem. The present invention significantly improves the system stability and communication efficiency through multi-node architecture, coordinated scheduling, dynamic update and identity ID information management, and effectively reduces the risk of single point failure. The system reduces manual intervention, is easy to expand and maintain, supports distributed dynamic access, and flexibly adapts to changes in business needs. Its optimized architecture and technical means ensure the continuity, accuracy and efficiency of communication services, and meet the high requirements of practical applications.

Description

Technical Field

[0001] The present invention belongs to the field of communication technology, and more specifically relates to a distributed multi-node collaborative disaster recovery Beidou communication system. Background Art

[0002] With the large-scale application and promotion of the Beidou satellite system, more and more business applications have begun to integrate Beidou communication capabilities. However, the implementation of Beidou satellite short message application technology needs to rely on Beidou communication control machine and Beidou card physical equipment. This technology is based on the point-to-point communication mode of Beidou card, in which the sender and receiver of the communication process use Beidou card number as identity. In this case, the stability of the hardware equipment has a direct impact on the reliability of the entire system;

[0003] Traditional Beidou short message communication service system architecture (such as Figure 5 The architecture (as shown) includes a database, a Beidou communication front-end service subsystem, a Beidou control machine, a Beidou card, a Beidou satellite and Beidou communication equipment. These unit components are connected in sequence. In this architecture, the stability of the system depends to a large extent on the reliability of the Beidou control machine. Once an abnormality occurs in the Beidou communication front-end service, especially when the Beidou control machine or Beidou card fails to work, it is usually necessary to manually troubleshoot the equipment problem to restore the system. For most systems, this situation is very unstable in use, which is not conducive to the normalization and stability of business applications. Summary of the invention

[0004] The purpose of the present invention is to solve the above technical problems and provide a distributed multi-node collaborative disaster recovery Beidou communication system.

[0005] In order to achieve the above-mentioned purpose, the present invention specifically adopts the following technical solutions:

[0006] The present invention proposes a distributed multi-node coordinated disaster recovery Beidou communication system, wherein the Beidou communication system is based on Beidou satellites and Beidou communication equipment for mutual communication connection, wherein the Beidou communication system includes a plurality of Beidou communication front-end service subsystems and a coordination and scheduling subsystem:

[0007] The coordination and dispatching subsystem includes a database and a front-end dispatching service connected to the database, and is used as a main control unit for disaster recovery dispatching of the Beidou communication front-end subsystem;

[0008] A database, an information storage unit for the Beidou communication system, recording information of several Beidou communication front subsystems of the Beidou communication system, wherein the Beidou communication front subsystem information includes identity ID information, operation status information, whether it is a master node information field, and node information;

[0009] The front-end dispatching service is interconnected with the Beidou communication front-end service subsystem, and is used to interact with several Beidou communication front-end service subsystems in real time, and monitor the status of several Beidou communication front-end subsystems in real time. When an abnormality is detected in the main node of the Beidou communication front-end subsystem, a new main node is dynamically recalculated and allocated in real time. When one of the Beidou communication front-end service subsystems is allocated as the new main node, the Beidou communication front-end subsystem of the node actively enters the new main node workflow, notifies the Beidou communication equipment to update and synchronize the communication target address, which is the Beidou card address information corresponding to the new main node;

[0010] Beidou communication front-end service subsystem, including Beidou communication front-end software, Beidou control machine and Beidou card, is responsible for Beidou short message communication function and actively enters the new master node workflow when taking over the new master node;

[0011] The Beidou card is installed in the Beidou control machine and is used as the identity ID information of the Beidou communication front-end service subsystem;

[0012] The Beidou control machine and Beidou communication front-end software communicate through the serial port to realize the sending and receiving functions of Beidou short message data.

[0013] As a preferred technical solution of the present invention, the pre-scheduling service specifically performs the following process steps:

[0014] 1): Pre-scheduling service starts;

[0015] 2): Check whether the current system has been assigned a master node. If yes, jump to step 3). If no, jump to step 4);

[0016] 3): Determine whether the currently recorded master node is in normal operation. If yes, jump to step eight). If no, jump to step four). The specific steps are as follows: The front-end scheduling service sends a status query frame to the Beidou communication front-end service subsystem of the master node to determine whether the Beidou communication front-end service subsystem of the master node has a reply status frame within 1 second. If yes, and the content of the reply frame indicates that the status is normal, then the Beidou communication front-end service subsystem of the master node is judged to be in a normal state, and jump to step eight); if no reply frame is received within 1 second, or a reply frame is received but the content identification is not in a normal state, then the Beidou communication front-end service subsystem of the master node is judged to be in an abnormal state, and jump to step four);

[0017] 4): Read the database to obtain the identity ID information of several Beidou communication front-end subsystems of the current Beidou communication system;

[0018] Five): Filter the identity ID information, and filter out the identity ID information of several Beidou communication front-end subsystems that are currently in normal operation from the information obtained in step four);

[0019] VI): Recalculate the identity ID information, using the several identity ID information selected in step 5) as parameters, and select one identity ID information from them based on a random algorithm, and the identity ID information will be used as the new master node identity ID information;

[0020] VII): Update the database record of the coordination and scheduling subsystem. The specific steps are as follows: First, update the "Is it the master node" field information in the corresponding database record of the new master node identity ID information in step VI) to "yes", and secondly, find the identity ID information of the Beidou communication front-end subsystem originally recorded as the master node, and update the "Is it the master node" field information in the corresponding database record to "no";

[0021] 8): Sleep for 1 minute. The front-end scheduling service enters the sleep state for 1 minute, and then re-executes step 2) for the next round of inspection and scheduling.

[0022] As a preferred technical solution of the present invention, when the Beidou communication front-end service subsystem takes over the new master node, the specific steps of actively entering the new master node workflow are as follows:

[0023] S1: Start: Beidou communication front-end software starts;

[0024] S2: Read identity ID information: Beidou communication front-end software reads the corresponding identity ID information of the Beidou card on the Beidou command machine;

[0025] S3: Notify the current node to start: Beidou communication front-end software notifies the front-end scheduling service that the current node is started and sends a notification message, which includes identity ID information and operation status information;

[0026] S4: Request to obtain the ID information of the current system master node: Beidou communication front-end software requests the front-end scheduling service to obtain the ID information of the currently enabled master node;

[0027] S5: Determine whether the identity ID information of the current node is consistent with that of the master node: The Beidou communication front-end software determines whether the identity ID information of the master node allocated by the front-end scheduling service is consistent with that of the current node. If yes, the current master node is the master node, and the process goes to step S7; if no, the process goes to step S6;

[0028] S6: Sleep for 1 minute: After the main thread of the Beidou communication front-end software sleeps for 1 minute, it jumps to step S4;

[0029] S7: Notify the pre-scheduling service: Beidou communication pre-software notifies the pre-scheduling service, the current node starts, and takes over the workflow of the main node;

[0030] S8: Query and obtain device information: Beidou communication front-end software queries and obtains Beidou communication device information managed by the Beidou communication system;

[0031] S9: Device updates and synchronizes Beidou card address information: Beidou communication front-end software targets the Beidou communication devices in step S8, and issues instructions for synchronously updating Beidou card address information one by one through the command machine. The Beidou card address information is the identity ID information of the current node in step S5;

[0032] S10: Confirm whether the device updates and synchronizes Beidou card address information: Beidou communication front-end software confirms whether the Beidou communication device in step S8 updates and synchronizes Beidou card address information. If yes, jump to step S11; if not, jump to step S9;

[0033] S11: Switching completed: Beidou communication equipment completes the Beidou card address information switching task.

[0034] As a preferred technical solution of the present invention, the specific steps of updating and synchronizing the Beidou card address information in step S9 are as follows:

[0035] 1st) Beidou communication equipment started operation;

[0036] 2nd) Triggering to start and update and synchronize address: Beidou communication equipment triggers to start updating and synchronizing Beidou card address information, and the triggering mode includes the Beidou communication equipment automatically running and starting and receiving the instruction of Beidou card address information in step S9; wherein the Beidou communication equipment automatically running and starting mode is only valid when the Beidou communication front-end service subsystem is the master node, and in other cases, the instruction of receiving the Beidou card address information in step S9 is used as the entry for triggering to start and update and synchronize address;

[0037] 3rd) Send request: Beidou communication equipment sends a request to the Beidou communication front-end service subsystem. The request is a short message to confirm the Beidou card address information. The request also carries a parameter including the central card address currently used by the Beidou communication equipment. The central card address is the master node identity ID information currently used by the equipment side recorded by the Beidou communication equipment.

[0038] 4th) Matching and judging whether the addresses are consistent: the Beidou communication front-end service subsystem matches and judges whether the central card address sent in step 3rd) is consistent with the Beidou card address information of the current master node. If yes, jump to step 9th); if not, jump to step 5th); the Beidou card address information is the identity ID information of the current node in step S5;

[0039] 5th) Sending an instruction: The Beidou communication front-end service subsystem sends an instruction to the Beidou communication device, the instruction being: the central card address of the Beidou communication device is updated and synchronized to the Beidou card address information of step 4th);

[0040] 6th) Obtaining address: The Beidou communication device receives and obtains the Beidou card address information in step 4th);

[0041] 7th) Confirm the update and synchronize the new address: the Beidou communication device updates and synchronizes the Beidou card address information in step 4th) to become the new central card address;

[0042] 8th) Determine whether the new address is consistent: Beidou communication equipment sends a request to Beidou communication front service subsystem, and the request carries a new central card address as a parameter. Beidou communication front service subsystem receives the new central card address, and then determines whether the new central card address is consistent with the Beidou card address information in step 4th). If yes, jump to step 9th), if no, jump to step 7th);

[0043] 9th) Confirm that the update and synchronization address task is completed: the Beidou communication front-end service subsystem confirms that the Beidou communication device has updated and synchronized the Beidou card address information, and jumps to step 10th);

[0044] 10th) Enable new address: Beidou communication equipment enables a new central card address.

[0045] The beneficial effects of the present invention are as follows:

[0046] The present invention significantly improves system stability and communication efficiency and effectively reduces the risk of single point failure through multi-node architecture, coordinated scheduling, dynamic update and identity ID information management. The system reduces manual intervention, is easy to expand and maintain, supports distributed dynamic access, and flexibly adapts to changes in business needs. Its optimized architecture and technical means ensure the continuity, accuracy and efficiency of communication services, meeting the high requirements of practical applications. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] Figure 1 is a system block diagram of the present invention;

[0048] Figure 2 A flowchart of specific execution steps of the pre-scheduling service of the present invention;

[0049] Figure 3 A flowchart of specific steps for actively entering the workflow of a new master node when the Beidou communication front-end service subsystem of the present invention takes over a new master node;

[0050] Figure 4 A flowchart of the specific steps for updating and synchronizing Beidou card address information for the device of the present invention;

[0051] Figure 5 This is a traditional system block diagram. DETAILED DESCRIPTION

[0052] Reference Figure 1 As shown, the present invention proposes a distributed multi-node coordinated disaster recovery Beidou communication system, wherein the Beidou communication system is based on Beidou satellites and Beidou communication equipment for mutual communication connection, wherein the Beidou communication system includes a plurality of Beidou communication front-end service subsystems and a coordination and scheduling subsystem:

[0053] The coordination and dispatching subsystem includes a database and a front-end dispatching service connected to the database, and is used as a main control unit for disaster recovery dispatching of the Beidou communication front-end subsystem;

[0054] A database, an information storage unit for the Beidou communication system, recording information of several Beidou communication front subsystems of the Beidou communication system, wherein the Beidou communication front subsystem information includes identity ID information, operation status information, whether it is a master node information field, and node information;

[0055] The front-end dispatching service is interconnected with the Beidou communication front-end service subsystem, and is used to interact with several Beidou communication front-end service subsystems in real time, and monitor the status of several Beidou communication front-end subsystems in real time. When an abnormality is detected in the main node of the Beidou communication front-end subsystem, a new main node is dynamically recalculated and allocated in real time. When one of the Beidou communication front-end service subsystems is allocated as the new main node, the Beidou communication front-end subsystem of the node actively enters the new main node workflow, notifies the Beidou communication equipment to update and synchronize the communication target address, which is the Beidou card address information corresponding to the new main node;

[0056] Beidou communication front-end service subsystem, including Beidou communication front-end software, Beidou control machine and Beidou card, is responsible for Beidou short message communication function and actively enters the new master node workflow when taking over the new master node;

[0057] The Beidou card is installed in the Beidou control machine and is used as the identity ID information of the Beidou communication front-end service subsystem;

[0058] The Beidou control machine and Beidou communication front-end software communicate through the serial port to realize the sending and receiving functions of Beidou short message data;

[0059] Among them, refer to Figure 2 As shown, the pre-scheduling service specifically performs the following process steps:

[0060] 1): Pre-scheduling service starts;

[0061] 2): Check whether the current system has been assigned a master node. If yes, jump to step 3). If no, jump to step 4);

[0062] 3): Determine whether the currently recorded master node is in normal operation. If yes, jump to step eight). If no, jump to step four). The specific steps are as follows: The front-end scheduling service sends a status query frame to the Beidou communication front-end service subsystem of the master node to determine whether the Beidou communication front-end service subsystem of the master node has a reply status frame within 1 second. If yes, and the content of the reply frame indicates that the status is normal, then the Beidou communication front-end service subsystem of the master node is judged to be in a normal state, and jump to step eight); if no reply frame is received within 1 second, or a reply frame is received but the content identification is not in a normal state, then the Beidou communication front-end service subsystem of the master node is judged to be in an abnormal state, and jump to step four);

[0063] 4): Read the database to obtain the identity ID information of several Beidou communication front-end subsystems of the current Beidou communication system;

[0064] Five): Filter the identity ID information, and filter out the identity ID information of several Beidou communication front-end subsystems that are currently in normal operation from the information obtained in step four);

[0065] VI): Recalculate the identity ID information, using the several identity ID information selected in step 5) as parameters, and select one identity ID information from them based on a random algorithm, and the identity ID information will be used as the new master node identity ID information;

[0066] VII): Update the database record of the coordination and scheduling subsystem. The specific steps are as follows: First, update the "Is it the master node" field information in the corresponding database record of the new master node identity ID information in step VI) to "yes", and secondly, find the identity ID information of the Beidou communication front-end subsystem originally recorded as the master node, and update the "Is it the master node" field information in the corresponding database record to "no";

[0067] Eight): Sleep for 1 minute, the front-end scheduling service enters the sleep state for 1 minute, and then re-executes step 2) to perform the next round of inspection and scheduling;

[0068] Among them, refer to Figure 3 As shown, when the Beidou communication front-end service subsystem takes over the new master node, the specific steps of actively entering the new master node workflow are as follows:

[0069] S1: Start: Beidou communication front-end software starts;

[0070] S2: Read identity ID information: Beidou communication front-end software reads the corresponding identity ID information of the Beidou card on the Beidou command machine;

[0071] S3: Notify the current node to start: Beidou communication front-end software notifies the front-end scheduling service that the current node is started and sends a notification message, which includes identity ID information and operation status information;

[0072] S4: Request to obtain the ID information of the current system master node: Beidou communication front-end software requests the front-end scheduling service to obtain the ID information of the currently enabled master node;

[0073] S5: Determine whether the identity ID information of the current node is consistent with that of the master node: Beidou communication front-end software determines whether the identity ID information of the master node assigned by the front-end scheduling service is consistent with that of the current node. If yes, the current master node is the master node and the process goes to step S7. If no, the process goes to step S6.

[0074] S6: Sleep for 1 minute: After the main thread of the Beidou communication front-end software sleeps for 1 minute, it jumps to step S4;

[0075] S7: Notify the pre-scheduling service: Beidou communication pre-software notifies the pre-scheduling service, the current node starts, and takes over the workflow of the main node;

[0076] S8: Query and obtain device information: the Beidou communication front-end software queries and obtains the Beidou communication device information managed by the Beidou communication system;

[0077] S9: Device updates and synchronizes Beidou card address information: Beidou communication front-end software targets the Beidou communication devices in step S8, and issues instructions for synchronously updating Beidou card address information one by one through the command machine. The Beidou card address information is the identity ID information of the current node in step S5;

[0078] S10: Confirm whether the device updates and synchronizes Beidou card address information: Beidou communication front-end software confirms whether the Beidou communication device in step S8 updates and synchronizes Beidou card address information. If yes, jump to step S11; if not, jump to step S9;

[0079] S11: Switching completed: Beidou communication equipment completes Beidou card address information switching task;

[0080] Among them, refer to Figure 4 As shown, the specific steps of updating and synchronizing the Beidou card address information in step S9 are as follows:

[0081] 1st) Beidou communication equipment is started and put into operation;

[0082] 2nd) Triggering and starting, updating and synchronizing address: Beidou communication equipment triggers and starts updating and synchronizing Beidou card address information, and the triggering mode includes the Beidou communication equipment automatically running and starting, and receiving the instruction of the Beidou card address information in step S9; wherein the Beidou communication equipment automatically running and starting mode is only valid when the Beidou communication front service subsystem is the main node, and in other cases, the instruction of receiving the Beidou card address information in step S9 is used as the trigger to start and update and synchronize the address;

[0083] 3rd) Send request: Beidou communication equipment sends a request to Beidou communication front-end service subsystem. The request is a short message to confirm Beidou card address information, and the request also carries a parameter of the central card address currently used by Beidou communication equipment. The central card address is the master node identity ID information currently in use by the equipment side recorded by Beidou communication equipment;

[0084] 4th) Matching and judging whether the addresses are consistent: the Beidou communication front-end service subsystem matches and judges whether the central card address sent in step 3rd) is consistent with the Beidou card address information of the current master node. If yes, jump to step 9th); if not, jump to step 5th); the Beidou card address information is the identity ID information of the current node in step S5;

[0085] 5th) Sending an instruction: the Beidou communication front-end service subsystem sends an instruction to the Beidou communication device, the instruction being: the central card address of the Beidou communication device is updated and synchronized to the Beidou card address information of step 4th);

[0086] 6th) Obtaining the address: the Beidou communication device receives and obtains the Beidou card address information of step 4th);

[0087] 7th) Confirm the update and synchronize the new address: the Beidou communication device updates and synchronizes the Beidou card address information in step 4th) to become the new central card address;

[0088] 8th) Determine whether the new address is consistent: the Beidou communication device sends a request to the Beidou communication front service subsystem, and the request carries a new central card address as a parameter. The Beidou communication front service subsystem receives the new central card address, and then determines whether the new central card address is consistent with the Beidou card address information in step 4th). If yes, jump to step 9th), if not, jump to step 7th);

[0089] 9th) Confirm that the update and synchronization address task is completed: the Beidou communication front-end service subsystem confirms that the Beidou communication device updates and synchronizes the Beidou card address information, and jumps to step 10th);

[0090] 10th) Enable new address: Beidou communication equipment enables a new central card address.

[0091] How it works

[0092] The distributed multi-node coordinated disaster recovery Beidou communication system provided by the present invention is innovatively designed to solve the problems of the traditional Beidou short message communication service system architecture, such as the stability relying on a single Beidou command machine and the need for manual intervention for troubleshooting. The working principle of the system is as follows:

[0093] Multi-node architecture:

[0094] The system consists of multiple Beidou communication front-end service subsystems, each of which has Beidou short message communication function and can work independently;

[0095] This multi-node architecture enables the system to quickly switch to other normally operating subsystems when facing a single point failure, ensuring the continuity of communication services;

[0096] Coordination and Scheduling:

[0097] The coordination and dispatching subsystem interacts with each Beidou communication front-end service subsystem in real time through the front-end dispatching service to monitor its operating status;

[0098] Once an abnormality is detected in the master node, the front-end scheduling service will immediately recalculate and assign a new master node to ensure the stability and reliability of the system;

[0099] Dynamic Updates:

[0100] When a new master node is assigned, the Beidou communication front-end subsystem of the node will actively enter the new master node workflow, notify the Beidou communication equipment to update and synchronize the communication target address;

[0101] This dynamic update mechanism enables the system to quickly adapt to changes, ensuring the accuracy and efficiency of communication services;

[0102] Identity ID information management:

[0103] Beidou card is the identity ID information of Beidou communication front-end service subsystem. By installing it on Beidou control machine, it realizes the identity authentication and authority management of the system.

[0104] The database records the information of all Beidou communication front-end subsystems, including identity ID information, operating status, etc., providing strong support for system scheduling and management;

[0105] Advantage Analysis

[0106] Improve system stability:

[0107] By introducing multiple Beidou communication front-end service subsystems and coordination and scheduling subsystems, the system realizes multi-node collaboration and disaster recovery backup, effectively reducing the impact of single point failures on system stability;

[0108] Even if a subsystem fails, the system can quickly switch to other normally operating subsystems to ensure the continuity of communication services;

[0109] Reduce manual intervention:

[0110] When a fault occurs in the traditional Beidou short message communication service system architecture, manual troubleshooting and recovery of equipment problems are usually required;

[0111] The distributed multi-node coordinated disaster recovery Beidou communication system achieves rapid fault detection and recovery through automated scheduling and dynamic update mechanisms, greatly reducing the need for manual intervention;

[0112] Improve communication efficiency:

[0113] The system ensures the accuracy and efficiency of communication services by monitoring the status of each Beidou communication front-end subsystem in real time and dynamically adjusting the main node;

[0114] At the same time, identity ID information management and dynamic update mechanisms also enable the system to quickly adapt to changes and improve communication efficiency;

[0115] Easy to expand and maintain:

[0116] The distributed multi-node coordinated disaster recovery Beidou communication system adopts a modular design, and each subsystem is relatively independent, which is easy to expand and maintain;

[0117] As business needs grow, new Beidou communication front-end service subsystems can be easily added to improve the system's processing capabilities and stability;

[0118] Combined with actual application construction needs:

[0119] The system supports distributed dynamic on-demand access and can flexibly adjust the number of Beidou communication front-end subsystems according to actual needs;

[0120] The front-end coordination service can perceive the information of new subsystems going online and abnormal system exit in real time, and update the system records to maintain the access status information of the Beidou communication front-end distributed multi-nodes in the overall system;

[0121] By deploying different communication front-end service systems in different environments and adopting a distributed approach, the robustness of the system is improved;

[0122] In summary, the distributed multi-node collaborative disaster recovery Beidou communication system effectively solves the problems existing in the traditional Beidou short message communication service system architecture by optimizing the system architecture, introducing a coordinated scheduling subsystem, and realizing dynamic updates and identity ID information management. It improves the system's stability and communication efficiency and meets the construction needs of actual applications.

[0123] Example: Application of distributed multi-node coordinated disaster recovery Beidou communication system in emergency rescue

[0124] Application scenario description

[0125] After a natural disaster (such as an earthquake) occurs, emergency rescue teams need to quickly establish communication links in order to coordinate rescue operations. Since the communication infrastructure in the disaster area may be damaged, traditional communication methods may not work properly. Therefore, the distributed multi-node coordinated disaster recovery Beidou communication system proposed in the present invention is used to ensure unimpeded communication between rescue teams.

[0126] System configuration and initialization

[0127] System Configuration:

[0128] Five Beidou communication front-end service subsystems (nodes A, B, C, D, and E) were deployed, each of which includes Beidou communication front-end software, Beidou control machine, and Beidou card;

[0129] Coordinate the scheduling subsystem, including database and front-end scheduling services;

[0130] initialization:

[0131] The database records the identity ID information, operation status information, whether it is the main node information field, and node information of each Beidou communication front-end subsystem;

[0132] The front-end dispatching service is started and begins to monitor the status of each Beidou communication front-end subsystem;

[0133] Node selection and master node reallocation process

[0134] The pre-scheduling service starts and verifies the current system:

[0135] After the pre-scheduling service is started, first check whether the current system has been assigned a master node;

[0136] In this example, it is assumed that node A is initially assigned as the master node;

[0137] Master node status monitoring:

[0138] The front-end scheduling service sends a status query frame to node A;

[0139] Assume that due to an earthquake, the Beidou communication front-end service subsystem of node A fails and cannot reply to the status frame within 1 second;

[0140] Recalculate and assign new master nodes:

[0141] The front-end dispatch service reads the database to obtain the identity ID information (A, B, C, D, E) of all current Beidou communication front-end subsystems;

[0142] Filter out the identity ID information of the Beidou communication front-end subsystem that is currently in normal operation (assuming that B, C, D, and E are operating normally);

[0143] Based on a random algorithm (such as a polling algorithm, a random selection algorithm, etc.), select an identity ID information as a new master node; in this example, assume that node B is selected as the new master node;

[0144] Update database records:

[0145] Update the "Is it a master node" field of node B to "yes";

[0146] Update the "Is it a master node" field of node A, which was originally recorded as the master node, to "No";

[0147] Beidou communication front-end service subsystem takes over the new master node process

[0148] Node B starts and reads the identity ID information:

[0149] The Beidou communication front-end software of node B is started to read the corresponding identity ID information of the Beidou card on the Beidou control machine;

[0150] Notify the front-end scheduling service and request the master node information:

[0151] Node B notifies the front-end scheduling service that the current node is started, and requests the ID information of the currently enabled master node;

[0152] The front-end scheduling service confirms that Node B is the new master node and notifies Node B;

[0153] The device updates and synchronizes the Beidou card address information:

[0154] Node B queries and obtains Beidou communication equipment information managed by the Beidou communication system;

[0155] Node B sends instructions to synchronize and update Beidou card address information to all Beidou communication devices one by one through the command machine;

[0156] Beidou communication equipment triggers the start of the update and synchronization of Beidou card address information process;

[0157] Specific update process (taking device 1 as an example):

[0158] Device 1 starts running and triggers the update and synchronization of Beidou card address information;

[0159] Device 1 sends a request to node B to confirm the Beidou card address information and carry the current central card address in use (assuming it is the address of node A);

[0160] Node B matches and determines that the central card address sent by device 1 is inconsistent with the Beidou card address information of the current master node (the address of node B), so it sends an update instruction to device 1;

[0161] Device 1 receives and obtains the Beidou card address information of node B, updates and synchronizes it to the new central card address;

[0162] Device 1 sends a request to Node B, carrying the new central card address for confirmation;

[0163] Node B confirms that the task of device 1 to update and synchronize Beidou card address information is completed;

[0164] Complete the switch:

[0165] All Beidou communication devices complete the Beidou card address information switching task and start using the new master node (node ​​B) for communication;

[0166] Results and Effects

[0167] Through the above process, the distributed multi-node collaborative disaster recovery Beidou communication system successfully achieved the reallocation of the main node and the synchronization of the address update of Beidou communication equipment in the emergency rescue scenario; the rescue team was able to use the Beidou communication system to maintain smooth communication, effectively coordinate rescue operations, and improve rescue efficiency.

[0168] The above shows and describes the basic principles and main features of the present invention and the advantages of the present invention. It is obvious to those skilled in the art that the present invention is not limited to the details of the above exemplary embodiments, and the present invention can be implemented in other specific forms without departing from the spirit or basic features of the present invention. Therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-restrictive. The scope of the present invention is defined by the attached claims rather than the above description, and it is intended that all changes falling within the meaning and scope of the equivalent elements of the claims are included in the present invention. Any figure mark in the claims should not be regarded as limiting the claims involved.

[0169] In addition, it should be understood that although the present specification is described according to implementation modes, not every implementation mode contains only one independent technical solution. This description of the specification is only for the sake of clarity. Those skilled in the art should regard the specification as a whole. The technical solutions in each embodiment may also be appropriately combined to form other implementation modes that can be understood by those skilled in the art.

Claims

1. A distributed multi-node coordinated disaster recovery Beidou communication system, wherein the Beidou communication system is based on Beidou satellites and Beidou communication equipment communicating with each other, characterized in that: The Beidou communication system includes several Beidou communication front-end service subsystems and coordination and scheduling subsystems: The coordination and dispatching subsystem includes a database and a front-end dispatching service connected to the database, and is used as a main control unit for disaster recovery dispatching of the Beidou communication front-end subsystem; A database, an information storage unit for the Beidou communication system, recording information of several Beidou communication front subsystems of the Beidou communication system, wherein the Beidou communication front subsystem information includes identity ID information, operation status information, whether it is a master node information field, and node information; The front-end dispatching service is interconnected with the Beidou communication front-end service subsystem, and is used to interact with several Beidou communication front-end service subsystems in real time, and monitor the status of several Beidou communication front-end subsystems in real time. When an abnormality is detected in the main node of the Beidou communication front-end subsystem, a new main node is dynamically recalculated and allocated in real time. When one of the Beidou communication front-end service subsystems is allocated as the new main node, the Beidou communication front-end subsystem of the node actively enters the new main node workflow, notifies the Beidou communication equipment to update and synchronize the communication target address, which is the Beidou card address information corresponding to the new main node; Beidou communication front-end service subsystem, including Beidou communication front-end software, Beidou control machine and Beidou card, is responsible for Beidou short message communication function and actively enters the new master node workflow when taking over the new master node; The Beidou card is installed in the Beidou control machine and is used as the identity ID information of the Beidou communication front-end service subsystem; The Beidou control machine and Beidou communication front-end software communicate through the serial port to realize the sending and receiving functions of Beidou short message data; The pre-scheduling service specifically performs the following process steps: 1): The pre-scheduling service starts; 2): Check whether the current system has been assigned a master node. If yes, jump to step 3). If no, jump to step 4); 3): Determine whether the master node of the current record is in normal operation. If yes, jump to step 8). If no, jump to step 4); 4): Read the database to obtain the identity ID information of several Beidou communication front-end subsystems of the current Beidou communication system; Five): Filter the identity ID information, and filter out the identity ID information of several Beidou communication front-end subsystems that are currently in normal operation from the information obtained in step four); VI): Recalculate the identity ID information, using the several identity ID information selected in step 5) as parameters, and select one identity ID information from them based on a random algorithm, and the identity ID information will be used as the new master node identity ID information; VII): Update the database records of the coordination and scheduling subsystem; 8): Sleep for 1 minute. The front-end scheduling service enters the sleep state for 1 minute, and then re-executes step 2) for the next round of inspection and scheduling.

2. A distributed multi-node coordinated disaster recovery Beidou communication system according to claim 1, characterized in that: When the Beidou communication front-end service subsystem takes over the new master node, the specific steps of actively entering the new master node workflow are as follows: S1: Start: Beidou communication front-end software starts; S2: Read identity ID information: Beidou communication front-end software reads the corresponding identity ID information of the Beidou card on the Beidou command machine; S3: Notify the current node to start: Beidou communication front-end software notifies the front-end scheduling service that the current node is started and sends a notification message, which includes identity ID information and operation status information; S4: Request to obtain the ID information of the current system master node: Beidou communication front-end software requests the front-end scheduling service to obtain the ID information of the currently enabled master node; S5: Determine whether the identity ID information of the current node is consistent with that of the master node: The Beidou communication front-end software determines whether the identity ID information of the master node allocated by the front-end scheduling service is consistent with that of the current node. If yes, the current master node is the master node, and the process goes to step S7; if no, the process goes to step S6; S6: Sleep for 1 minute: After the main thread of the Beidou communication front-end software sleeps for 1 minute, it jumps to step S4; S7: Notify the pre-scheduling service: Beidou communication pre-software notifies the pre-scheduling service, the current node starts, and takes over the workflow of the main node; S8: Query and obtain device information: Beidou communication front-end software queries and obtains Beidou communication device information managed by the Beidou communication system; S9: Device updates and synchronizes Beidou card address information: Beidou communication front-end software targets the Beidou communication devices in step S8, and issues instructions for synchronously updating Beidou card address information one by one through the command machine. The Beidou card address information is the identity ID information of the current node in step S5; S10: Confirm whether the device updates and synchronizes Beidou card address information: Beidou communication front-end software confirms whether the Beidou communication device in step S8 updates and synchronizes Beidou card address information. If yes, jump to step S11; if not, jump to step S9; S11: Switching completed: Beidou communication equipment completes the Beidou card address information switching task.

3. A distributed multi-node coordinated disaster recovery Beidou communication system according to claim 2, characterized in that: The specific steps of updating and synchronizing the Beidou card address information in step S9 are as follows: (1) Beidou communication equipment is started and put into operation; (2) Triggering to start and updating and synchronizing the address: The Beidou communication device triggers to start updating and synchronizing the Beidou card address information. The triggering methods include the Beidou communication device automatically starting and receiving the Beidou card address information instruction in step S9. The Beidou communication device automatically starting is only valid when the Beidou communication front-end service subsystem is the master node. In other cases, the instruction of receiving the Beidou card address information in step S9 is used as the entry for triggering to start and updating and synchronizing the address. (3) Sending a request: The Beidou communication device sends a request to the Beidou communication front-end service subsystem. The request is a short message to confirm the Beidou card address information. The request also carries a parameter including the central card address currently used by the Beidou communication device. The central card address is the master node identity ID information currently being used by the device side recorded by the Beidou communication device. (4) Matching and judging whether the addresses are consistent: the Beidou communication front-end service subsystem matches and judges whether the central card address sent in step (3) is consistent with the Beidou card address information of the current master node. If yes, jump to step (9); if not, jump to step (5); the Beidou card address information is the identity ID information of the current node in step S5; (5) Sending an instruction: The Beidou communication front-end service subsystem sends an instruction to the Beidou communication device, wherein the instruction is: the central card address of the Beidou communication device is updated and synchronized to the Beidou card address information of step (4); (6) Obtaining address: The Beidou communication device receives and obtains the Beidou card address information of step (4); (7) Confirming the update and synchronizing the new address: the Beidou communication device updates and synchronizes the Beidou card address information of step (4) to become the new central card address; (8) Determine whether the new address is consistent: the Beidou communication device sends a request to the Beidou communication front-end service subsystem, and the request carries a parameter including the new central card address. The Beidou communication front-end service subsystem receives the new central card address and then determines whether the new central card address is consistent with the Beidou card address information in step (4). If yes, jump to step (9); if no, jump to step (7); (9) Confirm that the task of updating and synchronizing the address is completed: The Beidou communication front-end service subsystem confirms that the task of updating the Beidou communication equipment and synchronizing the Beidou card address information is completed, and jumps to step (10); (10) Activate new address: Beidou communication equipment activates the new central card address.

Images