Satellite communication-based accompanying guarantee management collaboration method and system for all-network public network base station

Abstract

The invention discloses a satellite communication-based accompanying guarantee management cooperation method and a satellite communication-based accompanying guarantee management cooperation system for an all-network public network base station, which are applied to the field of emergency communication guarantee. Collection, processing, storage and interaction of satellite station, base station and user service related data are realized. Through an accompanying guarantee task management module, an instruction processing module, a feedback statistics module and a ground station position scheduling management module, full life cycle management of accompanying guarantee tasks, effective transmission and execution tracking of instructions, statistical analysis of guarantee effect data and cooperation of ground station position scheduling and guarantee tasks are respectively realized. Through online operation, the problems that in the prior art, emergency communication guarantee commanding and dispatching efficiency is low, and data statistics timeliness and accuracy are insufficient are solved, commanding and dispatching of accompanying guarantee can be efficiently carried out, guarantee effect data of accompanying guarantee point locations can be automatically counted in real time, the management collaboration process is optimized, and the commanding and dispatching efficiency of the accompanying guarantee point locations is improved. And the emergency communication guarantee capability and efficiency are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of emergency communication support, and specifically relates to a satellite communication-based all-network public network base station accompanying support management collaboration method and system. Background Art

[0002] In the field of emergency communication support, achieving efficient management coordination is the key to ensuring unimpeded communication. This is not only related to the timely communication and execution of rescue instructions in emergency situations, but also to the success or failure of the entire rescue operation. However, the existing technical solutions have a series of drawbacks that are difficult to ignore.

[0003] In terms of resource coordination and dispatch, there is currently a serious lack of effective online command and dispatch means. At this stage, information communication is mainly carried out with the help of instant messaging tools such as WeChat. However, this method has many obvious defects: due to the lack of a unified online platform for centralized management, the information communication channels are scattered and messy, resulting in a significant increase in communication costs. The information transmission between different departments and personnel lacks systematicity and standardization, and it is easy to have information omissions and misunderstandings, which greatly affects the efficiency of communication. For example, in the emergency communication guarantee of a sudden earthquake disaster, multiple rescue teams need to coordinate the deployment and use of satellite communication equipment. Due to the use of WeChat communication, messages are scattered between different groups and personnel, resulting in some groups failing to receive key information on equipment deployment in a timely manner, resulting in a contradictory situation where equipment is idle and groups that urgently need equipment cannot obtain it in time, delaying the deployment of rescue communications.

[0004] More importantly, it is impossible to obtain accurate information on the scheduling progress in real time, which makes it difficult for managers to make efficient overall planning and timely and flexible adjustments to the entire support work from a global perspective, which seriously restricts the timeliness and effectiveness of emergency communication support work, and may cause delays in key rescue operations in emergency situations. When a large-scale natural disaster occurs, the situation at the rescue site changes rapidly, and the rational allocation of communication resources is crucial. However, based on the existing communication methods, managers cannot grasp the installation progress, usage status and personnel deployment of communication equipment in each area in real time, and it is difficult to adjust the resource allocation strategy in time according to actual needs, resulting in a long period of time in which communications in some severely affected areas cannot be restored, affecting the smooth progress of rescue work.

[0005] In terms of business statistical data, the problems of insufficient timeliness and accuracy are particularly prominent. At present, the statistics and feedback of the guarantee effect mainly rely on the manual completion of each department participating in the rescue. This process not only requires a large amount of human and time costs, but also due to the limitations of manual operations, data errors are extremely likely to occur. The manual statistical method cannot update the data in real time. In the tense scenario of emergency rescue where every minute counts, the lag of data will bring great risks to decision-making. During the emergency rescue process, decisions often need to be made based on the latest communication guarantee data, such as network coverage, signal strength, and the number of user accesses. However, the manually statistical data may lag behind for several hours or even days. Decisions made based on the lagged data are very likely to be out of touch with the actual situation, resulting in the inability to adjust the guarantee strategy in a timely manner according to the real-time changes on the scene. For example, in a fire rescue, due to the inability to obtain the real-time traffic data of a certain area's communication base station in a timely manner, the rescue command center may misjudge the communication needs of this area and allocate valuable communication resources to other areas, causing communication congestion at the fire scene and the rescue instructions cannot be conveyed in a timely manner, thus having a negative impact on the quality and efficiency of the entire emergency communication guarantee work and being difficult to meet the strict requirements of emergency command in terms of data timeliness and accuracy.

[0006] In summary, in order to overcome the deficiencies of the existing technology, it is urgent to provide a brand-new accompanying guarantee method to improve the overall level of emergency communication guarantee work. This method needs to build a unified online command and dispatch platform to achieve efficient overall planning of resources and real-time monitoring of the dispatch progress; at the same time, with the help of automated data collection and statistical technologies, ensure the timeliness and accuracy of business statistical data, provide reliable data support for emergency command, so as to make correct decisions quickly in case of emergencies, ensure smooth communication, and provide strong support for the smooth progress of rescue work. Summary of the Invention

[0007] In view of this, the purpose of the present invention is to overcome the deficiencies of the existing technology and provide an accompanying guarantee management and coordination method and system for a network-wide public network base station based on satellite communication. The present invention aims to solve the defects existing in the existing emergency communication guarantee technology and comprehensively improve the efficiency and quality of emergency communication guarantee. The purposes of the present invention are as follows: Design an innovative accompanying guarantee method: For the emergency communication guarantee scenario, design a brand-new accompanying guarantee method. This method covers the entire process from resource allocation to task execution, aiming to optimize the working modes of each link, improve the overall guarantee efficiency, and provide a more scientific and efficient action guide for emergency communication.

[0008] Realize online and offline coordinated dispatch and efficient feedback: Conduct in-depth online development of the accompanying guarantee process and build a dispatch process that is closely integrated online and offline. By building a unified online platform, we can realize the centralized management and allocation of dispatch tasks, optimize the feedback process, and improve the management and feedback mechanism of dispatch tasks in different states such as unsubmitted, in dispatch, completed, and closed, to ensure the smooth flow of information. At the same time, we open up the data interaction channel between the mobile terminal and the management terminal to achieve seamless docking and task collaborative processing between the two, so that the commander can issue instructions in a timely manner, and the executors can provide real-time feedback, which significantly improves the response speed and execution efficiency of emergency communication guarantee.

[0009] Intelligent data processing based on geographic location: Use geographic location information to achieve automated data statistics. Automatically collect and analyze communication data in the security area, such as base station coverage, signal strength changes, etc., to accurately grasp the communication status. At the same time, realize online collection of security effect information, obtain on-site feedback in a timely manner, and provide comprehensive and accurate data support for emergency command, so as to quickly adjust the security strategy according to the actual situation, ensure the stability and reliability of communication services, and meet the stringent requirements of emergency command for data real-time and accuracy.

[0010] To achieve the above-mentioned purpose, the technical solution adopted by the present invention is as follows: In a first aspect, the present invention provides a method for accompanying security management and coordination of a full-network public network base station based on satellite communication, comprising the following steps: S1 system architecture construction: Build a system architecture including data collection layer, data processing layer, data storage layer and user interaction layer; the data collection layer collects raw data from satellite stations, base stations and user service-related data sources, and uses API interface calls, log file parsing and database synchronization technology for verification and preprocessing; the data processing layer uses cleaning, integration and analysis algorithms to identify and correct data errors and outliers, classify, aggregate and convert data according to business needs, and support custom processing logic; the data storage layer designs real-time data wide tables and historical data summary tables to store data, and has data backup and recovery functions; the user interaction layer adopts an intuitive and easy-to-use interface design, provides data visualization tools and interactive functions, and supports data export.

[0011] S2 accompanying guarantee task management: all accompanying guarantee tasks are displayed on the accompanying guarantee task list page of the user interaction layer, supporting paging, filtering and statistics functions; tasks can be opened / closed, deleted, issued instructions, viewed details, and fed back statistics. Task details have different operation permissions in different states, and when there are guarantee instructions under the guarantee task, the modification of the sites used by the instructions is restricted; obtain task-related information and store task data; S3 Adjacent Support Instruction Processing: Display all adjacent support instructions on the adjacent support instruction list page in the user interaction layer, supporting functions such as paging, filtering, and exporting; one or more operations such as viewing instruction details, expediting, initiating a new instruction, and deleting an instruction can be performed; when creating an adjacent support instruction, select the support task to obtain site data, fill in the instruction information and select the third-level unit, and the relevant data are saved to the corresponding tables respectively. After the instruction is issued, record the SMS and phone information; S4 Adjacent Support Feedback Statistics: On the adjacent support feedback statistics page in the user interaction layer, display the detailed information, automatic summary statistics, associated support forms, and daily statistics details of the task by selecting the support task; obtain data by calling the interface and perform statistical analysis on the data related to the support task; S5 Ground Station Location Scheduling Management: Display all ground station location scheduling records on the ground station location scheduling page in the user interaction layer, supporting one or more operations such as paging, filtering, initiating, generating a scheduling order, modifying, deleting, and enabling / disabling; obtain scheduling task data and associate other tables to obtain relevant information; when initiating a scheduling task, fill in the information and select the site, and the relevant data are saved to the corresponding tables respectively. After the scheduling order is generated, send an SMS and the task status changes; Furthermore, the steps of the S1 system architecture construction at least include the following steps: S11 Data Collection: The data collection layer obtains the remaining traffic, status, MIR, and CIR data of the satellite station through API interface calls, obtains the operation log data of the base station through log file parsing, and obtains the business data related to user services through database synchronization; S12 Data Processing: The data processing layer uses data cleaning algorithms to remove duplicate, incorrect, and invalid data, and uses data integration techniques to associate and merge data from different data sources according to specific rules; uses data analysis algorithms to deeply analyze the data, including calculating the traffic usage trend of the site, the change law of the number of user accesses, etc.; S13 Data Storage: The real-time data wide table designed in the data storage layer is used to store the real-time collected and processed data, including the real-time operation status of the satellite station and the base station, the real-time access information of users, etc.; the historical data summary table summarizes and stores the data according to the time period for historical data query and analysis; data backup adopts a combination of regular full backup and incremental backup, and the backup data is stored in off-site storage devices to ensure the security and recoverability of the data.

[0012] S14 User Interaction: The interface design of the user interaction layer adopts a responsive layout to adapt to the screen sizes of different terminal devices; provides data visualization tools such as bar charts, line charts, maps, etc. to intuitively display various types of data; the interaction functions include operations such as filtering, sorting, searching, and exporting, and users can flexibly view and process data according to their needs; supports exporting data to common formats such as Excel and PDF to facilitate data sharing and further analysis by users.

[0013] Furthermore, the S2 accompanying guarantee task management steps at least include the following steps: S21 Task List Display and Filtering: When the task list is displayed, if the data exceeds the page display, it is paged, with 10 data items per page by default, and can be manually modified; the filtering function is implemented through filtering by creation time, start time, status, and fuzzy query in the search box, where the creation time is accurate to the day, the start time is accurate to the hour and minute, and the status includes in progress, completed, and not started; the number of guarantee tasks, the number of completed tasks, and the number of tasks in progress are displayed in real time above the page, and the statistical information is updated in real time after operations such as adding, modifying, and deleting task data; S22 Task Operation Permission Control: After the task is closed, the front-end page restricts the guarantee task information and points from being modified by setting the read-only property; in the open state, if there is a guarantee instruction under the guarantee task and the instruction has used the guarantee point, the system queries the POINT__BASE_REL table to obtain the point association information, and then judges whether the point is used by querying the POINT__PATH_REL table; the front-end sets the writable status-related fields (such as the editing permissions of fields such as task name and guarantee point information) to true or false according to the judgment result. If the point is used, the editing permissions of the corresponding fields are set to false, otherwise set to true.

[0014] S23 Task Creation and Data Storage: When initiating a guarantee task, the accompanying guarantee person in charge is selected from the accompanying guarantee - select the third-level unit configuration in the list configuration, and this configuration information is stored in the sys_user table or related configuration tables; when adding point data, two methods of selecting points on the map and manually entering point information are supported; the main data of the accompanying guarantee is saved to the POINT_POSITION_INFO table, including information such as task name, guarantee level, guarantee type, start time, and person in charge; the added point data is saved to the POINT__BASE_REL table, including information such as point name, location, and radius; the selected accompanying guarantee start time is recorded in the POINT_POSITION_INFO table and the POSITION_TIME_REL table, and at the same time, information such as the creation time and update time of the task is recorded in the POSITION_TIME_REL table; Further, the S3 accompanying guarantee instruction processing step at least includes the following steps: S31 Instruction list display and screening: When the instruction list is paged, 10 pieces of data are displayed per page by default and can be adjusted manually; The screening conditions include the issuance time, start time, status, affiliated unit screening, and fuzzy query in the search box. The issuance time is accurate to the hour, minute, and second, and the status includes to be executed, in execution, completed, etc.; It supports exporting the list data to an Excel file, and the exported header fields include point serial number, point name, location, point description, and the screened instruction data; S32 Instruction details and reminder operation: The instruction details page displays all data of the instruction, including instruction number, task code, issuer, receiving enterprise, receiver, receiver contact information; The feedback detailed record displays the feedback information during the instruction execution process, including feedback time, feedback person, feedback content, etc.; The reminder detailed record displays the relevant information of the reminder operation, including reminder time, reminder person, reminder method; For direct reminder, after selecting the executor, the reminder instruction is issued, the reminder information is recorded, and the reminder text message is sent by calling the SMS interface and the record interface; For scheduled reminder, the start and end times and the daily reminder time are selected. The system calls the SMS interface to issue the reminder instruction and send a text message notification every day when the reminder time arrives within the set time period through the scheduled task mechanism; S33 Instruction creation and data recording: When creating an accompanying guarantee instruction, query the unclosed guarantee tasks through the POINT_POSITION_INFO table. After selecting a task, query the site data in the POINT__BASE_REL table according to the guarantee task Id, including site name, location, equipment type, etc.; Select the third-level unit, fill in the instruction information including instruction content and guarantee requirements, and then initiate the instruction; The content of the guarantee instruction is saved to the POINT_INSTUCT_INFO table, the selected third-level unit is saved to the POINT__USER_REL table, and the selected site information on the page is saved to the POINT__PATH_REL table; For the first new operation, all point data is saved in the POINT__MENT_REL table, recording the initial state and relevant information of the point; After issuing the instruction, the operation information of sending text messages and making voice calls is recorded in the INSTUCT_PATH_INFO table by calling the SMS interface and the voice call interface, including communication time, communication object, and communication content.

[0015] Further, the S4 accompanying guarantee feedback statistics step at least includes the following steps: S41 Task information display: On the accompanying guarantee feedback statistics page, after selecting the guarantee task through the drop-down box, display detailed information such as task code, guarantee name, guarantee level, guarantee description, guarantee time, task person in charge, and contact information; S42 Automatic Summary and Statistics: The system automatically counts the device data within the range of n kilometers from the center point of guarantee according to longitude and latitude, where n is greater than or equal to 2; specifically, by obtaining the center point coordinates of the guarantee task and querying the site data within the range in the database based on this coordinate; the queries involved are through associating the EQUIPMENT_INFO_Rel table and the BASE_NOW_INFO table, and counting indicators such as site type, user usage traffic, number of text messages sent, number of online sites, satellite data traffic used, number of accesses, number of calls, and call duration, etc.; including when counting user usage traffic, obtaining the user traffic data of each site from the BASE_NOW_INFO table and then classifying and summarizing according to the site type; when counting the number of online sites, judging the online status field of the sites in the EQUIPMENT_INFO_Rel table for counting.

[0016] S43 Associated Form Display: The associated form is implemented by calling an interface; after selecting a guarantee task, the Id of the guarantee task is automatically passed as a parameter to this interface; the backend queries the satellite resource scheduling and ground station location scheduling tasks by obtaining the PointId and associating the Point_id field in the DISPATH_INIO table; queries the whole network integration site application data by associating the Point_id field in the TRIPLE_NETWORK_ACCESS table; queries all eligible accompanying guarantee instruction data by associating the Point_id field in the POINT_INSTUCT_INFO table; encapsulates the data into the corresponding List entities respectively and then stores them in a Map, and the front end filters and displays the data from the returned Map; when clicking on different tasks, the Id of the task is passed to the backend, and the backend queries the detailed information from the corresponding table according to the Id and returns it to the front end for display, including displaying the scheduling details and executor information of the satellite resource scheduling task.

[0017] Daily statistical details display: The daily statistical details are implemented through an interface. First, query all the closed / opened times of the task in the POSITION_TIME_REL table by the incoming id; then traverse the set of closed / opened times, calculate the number of days in between and store it in a set; then query the specific task in the POINT_POSITION_INFO table by the id, and then query the set of guaranteed points in the POINT__BASE_REL table by the id of the guaranteed task; use an SQL statement to query the specific information in the BASE_ALL_INFO table, including the device operation data of each point at different times, etc. Then traverse the set, and within the traversal of the set, traverse the set of guaranteed points, and while traversing the set of guaranteed points, traverse the specific information queried from the BASE_ALL_INFO table. Only when traversing the set of guaranteed points, query the feedback information of the corresponding point in the POINT__MENT_REL table, and store the data obtained each time in the PointMentRel entity. Add PointMentRel to the Map every day of statistics, and finally return the Map set to the front end to display the daily statistical details, including the device operation status of each point and the execution status of the guaranteed tasks every day.

[0018] Further, the S5 ground station location scheduling management steps at least include the following steps: S51 Scheduling record list display and operation: When the scheduling record list is displayed, paging is supported. By default, 10 pieces of data are displayed on each page. Records can be filtered through filtering conditions, including issued time, start time, status, affiliated unit filtering, and fuzzy query in the search box; operations such as initiating, generating a dispatch order, modifying, deleting, and opening / closing the scheduling task can be performed; when generating a dispatch order, the system automatically generates a unique dispatch order number and generates a dispatch order containing task details and dispatch requirement content according to the task information; the modification operation can be performed when the scheduling task has not been submitted, and the modified content is updated in real time on the page and in the database; the deletion operation is performed in three cases: when the scheduling task is completed, closed, or not submitted. When deleting, all associated data related to the scheduling task is deleted simultaneously, including the relevant records in the DISPATH__UAV_REL table and the FLOW_PATH_INFO table; S52 Data Acquisition and Association: Filter out the ground station location scheduling task data through the Dis_type field in the DISPATH_INIO table, and query the scheduling executor information of the task from the DISPATH__USER_REL table by associating with the primary key Id of DISPATH_INIO, including the executor's name and contact information; query the guarantee task name from the POINT_POSITION_INFO table through the Point_id field of DISPATH_INIO; the statistical data above the page comes from the parameter passed by the interface, which is the value of Dis_type corresponding to the ground station location scheduling. The backend performs statistics from the DISPATH_INIO table based on this parameter. The scheduling task data is the quantity of all Dis_type with the specified value, the scheduled completion data is the quantity of Dis_type with the specified value and Is_submit equal to 2, the scheduling in-progress data is the quantity of Dis_type with the specified value and Is_submit equal to 1, and the pending execution data is the quantity of Dis_type with the specified value and Is_submit equal to 0. S53 Scheduling Task Initiation and Data Saving: When initiating a scheduling task, fill in the scheduling name, start time, and end time data. Among them, the end time determines that when the task is submitted, a text message and voice will be sent for reminder one hour before the end time; the scheduling executor data comes from the configuration of the ground station location scheduling executor in the list configuration; all enabled accompanying guarantee tasks will be displayed for the accompanying guarantee task, and only the Id value of the accompanying guarantee task will be recorded when saving; the site data is obtained through map selection or list selection, and the detailed data of the site comes from the EQUIPMENT_INFO_Rel table. Click to generate scheduling or only save, and add the detailed information of the scheduling task to the DISPATH_INIO table. The Point_id in the DISPATH_INIO table saves the selected accompanying guarantee task id, the Dis_type is defaulted to the identification value corresponding to the ground station location scheduling, the selected site information is recorded in the DISPATH__UAV_REL table, the selected scheduling executor is recorded in the DISPATH__USER_REL table, and the FLOW_PATH_INFO table will not be recorded when only saving. Only when generating scheduling will the feedback information of the currently issued task be recorded.

[0019] The second aspect of the present invention provides an accompanying guarantee management collaboration system for a network-wide communication public network base station based on satellite communication. This system is used to implement the above method. The system at least includes: System Architecture Building Module: Build a system architecture covering the data acquisition layer, data processing layer, data storage layer, and user interaction layer; the data acquisition layer collects raw data from satellite stations, base stations, and user service-related data sources, and performs verification and preprocessing using API interface calls, log file parsing, and database synchronization technologies; the data processing layer uses cleaning, integration, and analysis algorithms to identify and correct data errors and outliers, classifies, aggregates, and transforms data according to business requirements, and also supports custom processing logic; the data storage layer designs real-time data wide tables and historical data summary tables to store data, and has data backup and recovery functions; the user interaction layer adopts an intuitive and easy-to-use interface design, provides data visualization tools, interaction functions, and data export functions to support data interaction and display for the accompanying support service; Accompanying Support Task Management Module: Display all accompanying support tasks on the accompanying support task list page of the user interaction layer, supporting paging, filtering, and statistical functions; operations such as start / stop, deletion, issuance of instructions, viewing details, and feedback statistics can be performed on tasks; the operation permissions are different in different states for task details, and when there are support instructions under the support task, the modification of the sites used by the instructions is restricted; obtain task-related information and store task data to achieve the full life cycle management of accompanying support tasks; Accompanying Support Instruction Processing Module: Display all accompanying support instructions on the accompanying support instruction list page of the user interaction layer, supporting paging, filtering, and export functions; operations such as viewing instruction details, reminder, issuance of new instructions, and deletion of instructions can be performed; when creating an accompanying support instruction, select the support task to obtain site data, fill in the instruction information and select the third-level unit, and the relevant data are saved to the corresponding tables respectively. After the instruction is issued, the SMS and call information are recorded to track the effective transmission and execution of the support instruction; Accompanying Support Feedback Statistics Module: On the accompanying support feedback statistics page of the user interaction layer, display the detailed information, automatic summary statistics, associated support forms, and daily statistics details of the task by selecting the support task; obtain data by calling the interface, perform statistical analysis on the data related to the support task, and provide data support for the evaluation of the accompanying support effect; Ground Station Location Scheduling Management Module: Display all ground station location scheduling records on the ground station location scheduling page of the user interaction layer, supporting paging, filtering, initiation, generation of scheduling orders, modification, deletion, start / stop operations; obtain scheduling task data and associate other tables to obtain relevant information; when initiating a scheduling task, fill in the information and select the site, and the relevant data are saved to the corresponding tables respectively. After the scheduling order is generated, it is sent via SMS, and the task status changes, realizing the coordination of ground station location scheduling and accompanying support tasks.

[0020] Further, for the system architecture related sub-module: The data acquisition layer obtains the remaining traffic, status, MIR, and CIR data of the satellite station through API interface calls, obtains the operation log data of the base station through log file parsing, and obtains the business data related to user services through database synchronization; The data processing layer uses data cleaning algorithms to remove duplicate, incorrect, and invalid data, applies data integration technologies to associate and merge data from different data sources according to specific rules, and uses data analysis algorithms to deeply analyze the data; The real-time data wide table designed in the data storage layer is used to store the real-time collected and processed data, and the historical data summary table summarizes and stores the data according to time periods; The interface design of the user interaction layer adopts a responsive layout, provides data visualization tools, and the interaction functions include filtering, sorting, searching, and export operations, supporting data export in common formats such as Excel and PDF. For the accompanying support task management sub-module: When the task list is displayed, if the data exceeds the page display, it is paged, with 10 data items per page by default, which can be manually modified; The filtering function is implemented through filtering by creation time, start time, status, and a fuzzy query in the search box; The number of support tasks, the number of completed tasks, and the number of tasks in progress are displayed in real time above the page; After the task is closed, the front-end page restricts the modification of support task information and points; In the open state, if there are support instructions under the support task and the support points have been used in the instructions, it is judged whether the points can be modified by querying the relevant tables; When initiating a support task, the accompanying support person in charge is selected from the list configuration, point data is added, and the relevant data is saved to the corresponding tables respectively. Further, for the accompanying support instruction processing sub-module: When the instruction list is paged and displayed, 10 data items per page are available by default and can be manually adjusted; The filtering conditions include filtering by issuance time, start time, status, affiliated unit, and a fuzzy query in the search box; The instruction details page displays all instruction data, detailed feedback records, and detailed reminder records; For direct reminder, after selecting the executor, a reminder instruction is issued, the reminder information is recorded, and a reminder text message is sent; For scheduled reminder, the start and end times and the daily reminder time are selected, and the system issues a reminder instruction and notifies by text message every day at the reminder time within the set time period; When creating an accompanying support instruction, the support task and site data are obtained by querying the relevant tables, the third-level unit is selected, the instruction information is filled in, and then the instruction is initiated. The relevant data is saved to the corresponding tables respectively, and the text message and phone operation information are recorded after the instruction is issued.

[0021] For the accompanying support feedback statistics sub-module: When displaying the detailed information of the support task, the support task is selected through a drop-down box; Automatic summary statistics are used to count the equipment data within a certain range of the support center point according to longitude and latitude; The associated form is implemented by calling an interface. After selecting the support task, parameters are automatically passed, and the backend associates and queries the relevant data and encapsulates it, and the frontend filters and displays it; The daily statistics details are implemented through an interface. According to the incoming task id, the relevant time, points, and equipment data are queried, and after statistical analysis, it is returned to the frontend for display.

[0022] Furthermore, the ground station location scheduling management sub-module: When displaying the scheduling record list, it supports pagination and can filter records through filtering conditions; it can initiate, generate a scheduling order, modify, delete, and enable / disable scheduling tasks; when generating a scheduling order, the system automatically generates a unique scheduling order number and generates the content of the scheduling order according to the task information; the modification operation is performed when the scheduling task has not been submitted, and the deletion operation is performed under specific circumstances and the associated data is deleted simultaneously; data acquisition and association are achieved through filtering and associated queries of relevant table fields; when initiating a scheduling task, relevant information is filled in and a site is selected, and the relevant data is saved to the corresponding tables respectively. After the scheduling order is generated, a text message is sent, the task status changes, and the reminder function for the end time and the record rules of relevant tables under different save operations are considered.

[0023] The accompanying guarantee management coordination method and system for the all-net-communication public network base station based on satellite communication proposed by the present invention have made remarkable progress in many aspects and have outstanding beneficial effects compared with the traditional emergency communication guarantee method: Efficient command and scheduling: Through online operations, an integrated command and scheduling platform is constructed. The accompanying guarantee task management module realizes the centralized display, filtering, and statistics of tasks. The task list supports pagination, filtering, and search functions, facilitating managers to quickly locate and process tasks. The operation permissions such as enabling / disabling and initiating instructions are clear and easy to execute, and the task status is updated in real time, enabling commanders to always grasp the progress of tasks. For example, in large-scale emergency events involving numerous guarantee tasks and instructions, through this system, urgent tasks can be quickly filtered out and instructions can be issued in a timely manner. Compared with the traditional offline communication method, the instruction transmission time is greatly shortened, the command and scheduling efficiency is improved, and it is ensured that the emergency communication guarantee work can be carried out efficiently and orderly.

[0024] Real-time and accurate data statistics: The system can automatically and real-time statistically analyze the guarantee effect data of the accompanying guarantee points. In the accompanying guarantee feedback statistics module, using advanced data analysis techniques, it automatically statistically analyzes the equipment data within a certain range of the guarantee center point according to longitude and latitude, including multi-dimensional information such as site type, user traffic usage, and number of text messages sent. These data are automatically collected and analyzed by the system, avoiding the errors and delays of manual statistics, and ensuring the timeliness and accuracy of the data. Emergency commanders can understand the guarantee effect in a timely manner based on these real-time data. For example, if it is found that the communication traffic in a certain area is too large, causing network congestion, resources can be quickly adjusted to achieve precise command, effectively improving the pertinence and effectiveness of emergency communication guarantee.

[0025] Optimized Task and Instruction Management: The accompanying support task management module and the accompanying support instruction processing module cooperate closely to optimize the management process of tasks and instructions. The operation permissions for task details are different in different states. When there are support instructions under a support task, the modification of the sites used by the instructions is restricted, ensuring the data accuracy and stability during the execution of tasks and instructions. At the same time, the instruction processing module supports various operations, such as direct reminder and scheduled reminder, which can effectively urge the execution of instructions and ensure the progress of tasks according to the plan. For example, in an emergency rescue scenario, the timely issuance and effective execution of instructions are crucial for ensuring communication. This system can ensure that instructions are accurately conveyed to the executors and effectively track the execution status, improving the reliability of emergency communication support.

[0026] Convenient Data Interaction and Visualization Display: The design of the user interaction layer provides users with convenient data interaction and visualization display functions. The intuitive and easy-to-use interface is combined with data visualization tools, such as maps, bar charts, line charts, etc., to present complex data to users in an intuitive and easy-to-understand way. Users can quickly obtain the required information through interactive operations such as filtering and sorting, and can also export the data in common formats for further analysis. When viewing the accompanying support tasks and instructions, the visual interface allows users to quickly understand the task distribution, instruction execution progress, etc., facilitating comprehensive decision-making and improving the decision-making efficiency and scientific nature of emergency communication support work.

[0027] Enhanced Collaborative Management Capability: The system realizes the collaborative work between the ground station location scheduling management and other modules. The ground station location scheduling management module supports comprehensive operations on scheduling records, from initiating scheduling tasks to generating scheduling forms, then to data saving and task status changes, with each link closely connected. At the same time, this module conducts data interaction with the accompanying support task management module, instruction processing module, etc., realizing the collaborative management of all links in emergency communication support. For example, during the emergency communication support process, the scheduling of ground station locations needs to match the support tasks and instructions. Through the collaborative management of the system, it can ensure the reasonable allocation of ground station resources and improve the coordination and resource utilization efficiency of overall emergency communication support. Description of the Drawings

[0028] In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, the following-described drawings are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on these drawings.

[0029] Figure 1 It is a flowchart of the accompanying support management collaboration method for the full-network communication public network base station of the present invention; Figure 2It is a schematic diagram of the system module of the accompanying guarantee management collaboration method for the full-network communication public network base station of the present invention. Detailed implementation manners

[0030] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The implementation manners described in the following exemplary embodiments do not represent all implementation manners consistent with the present invention. On the contrary, they are only examples of the devices and methods consistent with some aspects of the present invention as detailed in the appended claims. Embodiment 1

[0031] As Figure 1 shown, this embodiment provides an accompanying guarantee management collaboration method for a full-network communication public network base station based on satellite communication, including the following steps: S1 System architecture construction: Construct a system architecture including a data acquisition layer, a data processing layer, a data storage layer, and a user interaction layer; the data acquisition layer collects raw data from satellite stations, base stations, and user service-related data sources, and uses API interface calls, log file parsing, and database synchronization technologies for verification and preprocessing; the data processing layer uses cleaning, integration, and analysis algorithms to identify and correct data errors and outliers, classify, aggregate, and transform the data according to business requirements, and at the same time supports custom processing logic; the data storage layer designs real-time data wide tables and historical data summary tables to store data, and has data backup and recovery functions; the user interaction layer adopts an intuitive and easy-to-use interface design, provides data visualization tools and interaction functions, and supports data export.

[0032] S2 Accompanying guarantee task management: Display all accompanying guarantee tasks on the accompanying guarantee task list page of the user interaction layer, and support paging, filtering, and statistical functions; one or more operations such as opening / closing, deleting, initiating instructions, viewing details, and feedback statistics can be performed on the tasks; the operation permissions of the task details are different in different states, and when there are guarantee instructions under the guarantee task, the modification of the sites where the instructions have been used is restricted; obtain task-related information and store task data; S3 Accompanying guarantee instruction processing: Display all accompanying guarantee instructions on the accompanying guarantee instruction list page of the user interaction layer, and support paging, filtering, and export functions; one or more operations such as viewing instruction details, reminding, initiating new instructions, and deleting instructions can be performed; when creating an accompanying guarantee instruction, select the guarantee task to obtain site data, fill in the instruction information and select the third-level unit, and the relevant data are saved to the corresponding tables respectively. After the instruction is issued, the short message and call information are recorded; S4 Adjacent Support Feedback Statistics: On the adjacent support feedback statistics page in the user interaction layer, display the detailed information, automatic summary statistics, associated support forms, and daily statistics details of the task by selecting the support task; obtain data by calling the interface to perform statistical analysis on data related to the support task; S5 Ground Station Location Scheduling Management: Display all ground station location scheduling records on the ground station location scheduling page in the user interaction layer, supporting operations such as paging, filtering, initiating, generating scheduling orders, modifying, deleting, and enabling / disabling one or more operations; obtain scheduling task data and associate other tables to obtain relevant information; when initiating a scheduling task, fill in information and select a site, and save the relevant data into the corresponding tables respectively. After generating a scheduling order, send a text message, and the task status changes; As an implementation method, the steps of the S1 system architecture construction in this embodiment at least include the following steps: S11 Data Collection: The data collection layer obtains the remaining traffic, status, MIR, and CIR data of the satellite station by calling the API interface, obtains the operation log data of the base station by parsing the log file, and obtains the business data related to user services by database synchronization; S12 Data Processing: The data processing layer uses data cleaning algorithms to remove duplicate, incorrect, and invalid data, and uses data integration technologies to associate and merge data from different data sources according to specific rules; uses data analysis algorithms to deeply analyze the data, including calculating the traffic usage trend of the site, the change law of the number of user accesses, etc.; S13 Data Storage: The real-time data wide table designed by the data storage layer is used to store the real-time collected and processed data, including the real-time operation status of the satellite station and the base station, user real-time access information, etc.; the historical data summary table summarizes and stores the data according to the time period for historical data query and analysis; data backup adopts a combination of regular full backup and incremental backup, and the backup data is stored in off-site storage devices to ensure the security and recoverability of the data.

[0033] S14 User Interaction: The interface design of the user interaction layer adopts a responsive layout to adapt to the screen sizes of different terminal devices; provides data visualization tools such as bar charts, line charts, maps, etc. to intuitively display various types of data; the interaction functions include operations such as filtering, sorting, searching, and exporting, and users can flexibly view and process data according to their needs; supports data export in common formats such as Excel and PDF to facilitate data sharing and further analysis by users.

[0034] As an implementation method, the steps of the S2 adjacent support task management in this embodiment at least include the following steps: S21 Task List Display and Filtering: When the task list is displayed, if the data exceeds the page display, paging is performed. By default, 10 pieces of data are shown per page, and this can be manually modified. The filtering function is implemented through filtering by creation time, start time, status, and fuzzy query in the search box. Among them, the creation time is accurate to the day, the start time is accurate to the hour and minute, and the status includes in progress, completed, and not started. The number of guarantee tasks, the number of completed tasks, and the number of tasks in progress are displayed in real time above the page, and the statistical information is updated in real time after operations such as adding, modifying, and deleting task data. S22 Task Operation Permission Control: After the task is closed, the front-end page restricts the guarantee task information and points from being modified by setting the read-only property. In the open state, if there are guarantee instructions under the guarantee task and the guarantee points have been used in the instructions, the system queries the POINT__BASE_REL table to obtain the point association information, and then queries the POINT__PATH_REL table to determine whether the point has been used. According to the judgment result, the front-end sets the writable status-related fields (such as the editing permissions of fields such as task name and guarantee point information) to true or false. If the point has been used, the editing permissions of the corresponding fields are set to false, and vice versa to true.

[0035] S23 Task Creation and Data Storage: When initiating a guarantee task, the accompanying guarantee person is selected from the list configuration of accompanying guarantee - selecting the third-level unit configuration. This configuration information is stored in the sys_user table or related configuration tables. When adding point data, two methods are supported: selecting points on the map and manually entering point information. The main data of the accompanying guarantee is saved to the POINT_POSITION_INFO table, including information such as task name, guarantee level, guarantee type, start time, and person in charge. The added point data is saved to the POINT__BASE_REL table, including information such as point name, location, and radius. The selected start time of the accompanying guarantee is recorded in the POINT_POSITION_INFO table and the POSITION_TIME_REL table, and at the same time, information such as the creation time and update time of the task is recorded in the POSITION_TIME_REL table. As an implementation method, the S3 accompanying guarantee instruction processing steps in this embodiment at least include the following steps: S31 Instruction List Display and Filtering: When the instruction list is displayed in pages, by default, 10 pieces of data per page can be manually adjusted. The filtering conditions include filtering by issued time, start time, status, affiliated unit, and fuzzy query in the search box. The issued time is accurate to the hour, minute, and second, and the status includes to be executed, executing, and completed, etc. It supports exporting the list data to an Excel file. When exporting, the header fields included are point serial number, point name, location, point description, and the filtered instruction data. Details of S32 Instruction and Reminder Operation: All data of the instruction are displayed on the instruction details page, including instruction number, task code, issuer, receiving enterprise, receiver, and receiver's contact information; detailed feedback records display feedback information during the execution of the instruction, including feedback time, feedback person, feedback content, etc.; detailed reminder records display relevant information about reminder operations, including reminder time, reminder person, and reminder method; for direct reminder, after selecting the executor, a reminder instruction is issued, reminder information is recorded, and a reminder text message is sent by calling the SMS interface and the record interface; for scheduled reminder, start and end times and the daily reminder time are selected. The system uses the scheduled task mechanism to call the SMS interface to issue a reminder instruction and send a text message notification every day when the reminder time arrives within the set time period. S33 Instruction Creation and Data Recording: When creating an accompanying support instruction, unclosed support tasks are queried through the POINT_POSITION_INFO table. After selecting a task, site data, including site name, location, equipment type, etc., is queried from the POINT__BASE_REL table according to the support task Id; a third-level unit is selected, and instruction information, including instruction content and support requirements, is filled in and the instruction is initiated; the content of the support instruction is saved to the POINT_INSTUCT_INFO table, the selected third-level unit is saved to the POINT__USER_REL table, and the site information selected on the page is saved to the POINT__PATH_REL table; for the first new operation, all point data is saved in the POINT__MENT_REL table, recording the initial state and relevant information of the points; after the instruction is issued, the operation information of sending text messages and making voice calls is recorded in the INSTUCT_PATH_INFO table by calling the SMS interface and the voice call interface, including communication time, communication object, and communication content.

[0036] As an implementation manner, the S4 accompanying support feedback statistics step in this embodiment at least includes the following steps: S41 Task Information Display: On the accompanying support feedback statistics page, after selecting a support task through the drop-down box, detailed information such as task code, support name, support level, support description, support time, task responsible person, and contact information is displayed. S42 Automatic Summary and Statistics: The system automatically calculates the device data within the range of n kilometers from the center point of the guarantee, where n is greater than or equal to 2. Specifically, by obtaining the center point coordinates of the guarantee task, query the site data within the range in the database based on this coordinate. The queries involved are through associating the EQUIPMENT_INFO_Rel table and the BASE_NOW_INFO table, and calculating indicators such as site type, user usage traffic, number of text messages sent, number of online sites, satellite data traffic used, number of accesses, number of calls, and call duration. When calculating user usage traffic, obtain the user traffic data of each site from the BASE_NOW_INFO table and then classify and summarize according to the site type. When calculating the number of online sites, count by judging the online status field of the sites in the EQUIPMENT_INFO_Rel table.

[0037] S43 Associated Form Display: The associated form is implemented by calling an interface. After selecting a guarantee task, automatically pass the Id of the guarantee task as a parameter to this interface. The backend queries the satellite resource scheduling and ground station location scheduling tasks by obtaining the PointId and associating the Point_id field in the DISPATH_INIO table. Query the whole network integration site application data by associating the Point_id field in the TRIPLE_NETWORK_ACCESS table. Query all eligible accompanying guarantee instruction data by associating the Point_id field in the POINT_INSTUCT_INFO table. Package the data into corresponding List entities respectively and then store them in a Map. The front end filters and displays the data from the returned Map. When clicking on different tasks, pass the Id of the task to the backend. The backend queries the detailed information from the corresponding table according to the Id and returns it to the front end for display, including displaying the scheduling details and executor information of the satellite resource scheduling task.

[0038] Daily statistical details display: The daily statistical details are implemented through an interface. First, query all the closed / opened times of the task in the POSITION_TIME_REL table by the incoming id; then traverse the set of closed / opened times, calculate the number of days in between and store them in a set; then query the specific task in the POINT_POSITION_INFO table by the id, and then query the set of guaranteed points in the POINT__BASE_REL table by the id of the guaranteed task; use an SQL statement to query the specific information in the BASE_ALL_INFO table, including the device operation data of each point at different times, etc. Then traverse the set, and within the set traversal, traverse the set of guaranteed points, and while traversing the set of guaranteed points, traverse the specific information retrieved from the BASE_ALL_INFO table. Only when traversing the set of guaranteed points, query the feedback information of the corresponding point in the POINT__MENT_REL table, and store the data retrieved each time in the PointMentRel entity. Add PointMentRel to the Map every day of statistics, and finally return the Map set to the front end to display the daily statistical details, including the device operation status of each point every day and the execution status of the guaranteed tasks.

[0039] As an implementation manner, the steps of the S5 ground station location scheduling management in this embodiment at least include the following steps: S51 Display and operation of the scheduling record list: When the scheduling record list is displayed, paging is supported. By default, 10 pieces of data are displayed per page. Records can be filtered through filtering conditions, including the issued time, start time, status, affiliated unit filtering, and fuzzy query in the search box; operations such as initiating, generating a dispatch order, modifying, deleting, and opening / closing the scheduling task can be performed; when generating a dispatch order, the system automatically generates a unique dispatch order number, and generates a dispatch order containing task details and dispatch requirement content according to the task information; the modification operation can be performed when the scheduling task has not been submitted, and the modified content is updated in real time on the page and in the database; the deletion operation is performed in three cases: when the scheduling task is completed, closed, or not submitted. When deleting, all associated data related to the scheduling task is deleted simultaneously, including the relevant records in the DISPATH__UAV_REL table and the FLOW_PATH_INFO table; S52 Data Acquisition and Association: Filter out the ground station location scheduling task data through the Dis_type field in the DISPATH_INIO table. Query the scheduling executor information of the task, including the executor's name and contact information, from the DISPATH__USER_REL table by associating with the primary key Id of the DISPATH_INIO. Query the support task name from the POINT_POSITION_INFO table through the Point_id field of the DISPATH_INIO. The statistical data at the top of the page comes from the parameter passed by the interface, which is the value of Dis_type corresponding to the ground station location scheduling. The backend performs statistics from the DISPATH_INIO table through this parameter. The scheduling task data is the quantity of all Dis_type with the specified value, the completed scheduling data is the quantity of Dis_type with the specified value and Is_submit equal to 2, the scheduling-in-progress data is the quantity of Dis_type with the specified value and Is_submit equal to 1, and the pending execution data is the quantity of Dis_type with the specified value and Is_submit equal to 0. S53 Initiation and Data Saving of Scheduling Tasks: When initiating a scheduling task, fill in the scheduling name, start time, and end time data. The end time determines that when the task is submitted, a text message and voice reminder will be sent one hour before the end time. The scheduling executor data comes from the configuration of the ground station location scheduling executor in the list configuration. All enabled accompanying support tasks will be displayed for the accompanying support task. Only the Id value of the accompanying support task will be recorded when saving. The site data is obtained through map selection or list selection. The detailed data of the site comes from the EQUIPMENT_INFO_Rel table. Click to generate a schedule or only save, and add the detailed information of the scheduling task to the DISPATH_INIO table. The Point_id in the DISPATH_INIO table saves the selected accompanying support task id, the Dis_type is defaulted to the identification value corresponding to the ground station location scheduling, the selected site information is recorded in the DISPATH__UAV_REL table, and the selected scheduling executor is recorded in the DISPATH__USER_REL table. The FLOW_PATH_INFO table will not be recorded when only saving, and only the feedback information of the currently issued task will be recorded when generating a schedule. Embodiment 2

[0040] As Figure 2 shown, this embodiment provides an accompanying support management collaboration system for a network-wide public network base station based on satellite communication. This system is used to implement the above method. The system at least includes: System Architecture Building Module: Build a system architecture covering the data collection layer, data processing layer, data storage layer, and user interaction layer; the data collection layer collects raw data from satellite stations, base stations, and user service-related data sources, and performs verification and preprocessing using API interface calls, log file parsing, and database synchronization technologies; the data processing layer uses cleaning, integration, and analysis algorithms to identify and correct data errors and outliers, classify, aggregate, and transform data according to business requirements, and also supports custom processing logic; the data storage layer designs real-time data wide tables and historical data summary tables to store data, and has data backup and recovery functions; the user interaction layer adopts an intuitive and easy-to-use interface design, provides data visualization tools, interaction functions, and data export functions to support data interaction and display for the accompanying support business; Accompanying Support Task Management Module: Display all accompanying support tasks on the accompanying support task list page in the user interaction layer, supporting paging, filtering, and statistical functions; operations such as start / stop, deletion, issuing instructions, viewing details, and feedback statistics can be performed on tasks; the operation permissions are different in different states for task details, and when there are support instructions under the support task, the modification of the sites where the instructions have been used is restricted; obtain task-related information and store task data to achieve the full-life cycle management of accompanying support tasks; Accompanying Support Instruction Processing Module: Display all accompanying support instructions on the accompanying support instruction list page in the user interaction layer, supporting paging, filtering, and export functions; operations such as viewing instruction details, reminder, issuing new instructions, and deleting instructions can be performed; when creating an accompanying support instruction, select the support task to obtain site data, fill in the instruction information and select the third-level unit, and the relevant data are saved to the corresponding tables respectively. After issuing the instruction, record the SMS and phone information to track the effective communication and execution of the support instruction; Accompanying Support Feedback Statistics Module: On the accompanying support feedback statistics page in the user interaction layer, display the detailed information, automatic summary statistics, associated support forms, and daily statistics details of the task by selecting the support task; obtain data by calling the interface, perform statistical analysis on the data related to the support task, and provide data support for the evaluation of the accompanying support effect; Ground Station Location Scheduling Management Module: Display all ground station location scheduling records on the ground station location scheduling page in the user interaction layer, supporting paging, filtering, initiation, generating a scheduling order, modification, deletion, start / stop operations; obtain scheduling task data and associate other tables to obtain relevant information; when initiating a scheduling task, fill in the information and select the site, and the relevant data are saved to the corresponding tables respectively. After generating the scheduling order, send an SMS, and the task status changes to achieve the coordination of ground station location scheduling and accompanying support tasks.

[0041] As an implementation method, the sub-modules related to the system architecture of this embodiment: The data acquisition layer obtains the remaining traffic, status, MIR, and CIR data of the satellite station through API interface calls, obtains the operation log data of the base station through log file parsing, and obtains the business data related to user services through database synchronization; the data processing layer uses data cleaning algorithms to remove duplicate, incorrect, and invalid data, uses data integration technologies to associate and merge data from different data sources according to specific rules, and uses data analysis algorithms to deeply analyze the data; the real-time data wide table designed in the data storage layer is used to store the real-time collected and processed data, and the historical data summary table summarizes and stores the data according to time periods; the interface design of the user interaction layer adopts a responsive layout, provides data visualization tools, and the interaction functions include filtering, sorting, searching, and export operations, and supports data export in common formats such as Excel and PDF; Accompanying support task management sub-module: When the task list is displayed, if the data exceeds the page display, paging is performed, with 10 data items per page by default, which can be manually modified; the filtering function is implemented through filtering by creation time, start time, status, and fuzzy query in the search box; the number of support tasks, the number of completed tasks, and the number of tasks in progress are displayed in real time above the page; after the task is closed, the front-end page restricts the modification of support task information and points; in the open state, if there are support instructions under the support task and the support points have been used in the instructions, it is judged whether the points can be modified by querying the relevant tables; when initiating a support task, the accompanying support person in charge is selected from the list configuration, point data is added, and the relevant data is saved to the corresponding tables respectively; As an implementation method, the accompanying support instruction processing sub-module of this embodiment: When the instruction list is displayed in pages, 10 data items per page are displayed by default and can be adjusted manually; the filtering conditions include filtering by issuance time, start time, status, affiliated unit, and fuzzy query in the search box; the instruction details page displays all the data of the instruction, detailed feedback records, and detailed reminder records; for direct reminder, after selecting the executor, a reminder instruction is issued, the reminder information is recorded, and a reminder text message is sent; for scheduled reminder, the start and end times and the daily reminder time are selected, and the system issues a reminder instruction and notifies by text message every day at the reminder time within the set time period; when creating an accompanying support instruction, the support task and site data are obtained by querying the relevant tables, the third-level unit is selected, the instruction information is filled in, and the instruction is initiated. The relevant data is saved to the corresponding tables respectively, and the text message and phone operation information are recorded after the instruction is issued.

[0042] Accompanying guarantee feedback statistics sub-module: When displaying the detailed information of the guarantee task, select the guarantee task through a drop-down box; automatically summarize and statistically analyze the device data within a certain range of the guarantee center point according to longitude and latitude; the associated form is implemented by calling an interface. After selecting the guarantee task, parameters are automatically passed, and the backend queries and encapsulates relevant data, and the frontend filters and displays; the daily statistics details are implemented through an interface. According to the incoming task ID, relevant time, location, and device data are queried, and after statistical analysis, they are returned to the frontend for display.

[0043] As an implementation method, in this embodiment, the ground station location scheduling management sub-module: When displaying the scheduling record list, paging is supported, and records can be filtered through filtering conditions; operations such as initiating, generating a scheduling order, modifying, deleting, and enabling / disabling the scheduling task can be performed; when generating a scheduling order, the system automatically generates a unique scheduling order number and generates the content of the scheduling order according to the task information; the modification operation is performed when the scheduling task has not been submitted, and the deletion operation is performed under specific circumstances and the associated data is deleted at the same time; data acquisition and association are achieved through filtering and associated query of relevant table fields; when initiating a scheduling task, fill in relevant information and select a site, and the relevant data is saved to the corresponding table respectively. After generating the scheduling order, a text message is sent, the task status changes, and the reminder function for the end time and the record rules of relevant tables under different save operations are considered. Embodiment III

[0044] This embodiment provides a companion guarantee management collaboration system for a full-network communication public network base station based on satellite communication, including: System architecture module: It includes a data acquisition layer, a data processing layer, a data storage layer, and a user interaction layer. The data acquisition layer is used to collect raw data from satellite stations, base stations, and user service-related data sources, and perform verification and preprocessing using API interface calls, log file parsing, and database synchronization technologies; the data processing layer uses cleaning, integration, and analysis algorithms to identify and correct data errors and outliers, classify, aggregate, and transform data according to business requirements, and at the same time support custom processing logic; the data storage layer designs real-time data wide tables and historical data summary tables to store data, and has data backup and recovery functions; the user interaction layer provides an intuitive and easy-to-use interface, data visualization tools, interaction functions, and data export functions.

[0045] As an implementation method, in this embodiment, the data acquisition layer further includes: Satellite data acquisition unit: Obtain the remaining traffic, status, MIR, and CIR data of the satellite station through API interface calls, perform real-time data acquisition, and verify the integrity, accuracy, and timeliness of the data during the acquisition process. For example, check whether data fields are missing, whether the data format is correct, and whether the data is updated within the specified time. Mark and preprocess abnormal data.

[0046] Base station data acquisition unit: Use log file parsing technology to obtain the base station's operating log data, parse the key information in the log file, such as the base station's startup time, fault records, communication traffic, etc., and preliminarily organize and verify the parsed data.

[0047] User data collection unit: uses database synchronization technology to obtain business data related to user services, including user access information, service usage time, traffic consumption and other data, to ensure data consistency with the user service database.

[0048] As an implementation method, the data processing layer described in this embodiment further includes: a data cleaning unit: using a data cleaning algorithm to remove duplicate, erroneous and invalid data, for example, by setting data duplication checking rules to remove duplicate records; identifying and correcting erroneous data based on the data value range and format requirements; for invalid data, such as data that cannot be parsed or is incomplete, deleting or marking it.

[0049] Data integration unit: Use data integration technology to associate and merge data from different data sources according to specific rules, and integrate related data based on the timestamp, geographic location and other related fields between satellite stations, base stations and user data to form a unified data view.

[0050] Data analysis unit: Use data analysis algorithms to conduct in-depth analysis of data, including calculating the site's traffic usage trends, changes in the number of user accesses, etc. Through statistical analysis methods, predict future traffic demand and user access conditions, and provide data support for resource scheduling.

[0051] Custom processing interface unit: provides a custom processing logic interface, allowing users to write code to personalize data processing according to specific business needs. Users can upload custom algorithm scripts through this interface to achieve special processing and analysis of data.

[0052] As an implementation method, the data storage layer described in this embodiment further includes: a real-time data storage unit: a real-time data wide table is designed to store data collected and processed in real time, including the real-time operating status of satellite stations and base stations, user real-time access information, etc. The real-time data wide table adopts an efficient data storage structure, which can quickly read and write data to meet the system's requirements for fast access to real-time data.

[0053] Historical data storage unit: The historical data summary table summarizes and stores data by time period (such as day, week, month) to facilitate historical data query and analysis. The historical data summary table uses partition storage to divide data into different partitions according to the time dimension to improve the query efficiency of historical data.

[0054] Data Backup and Recovery Unit: Data backup adopts a combination of regular full backup and incremental backup. The backup data is stored in off-site storage devices to ensure data security and recoverability. When performing data recovery, it can quickly and accurately restore the data state to the specified time point according to the timestamp and version information of the backup data.

[0055] As an implementation, the user interaction layer in this embodiment further includes: Interface Design Unit: The interface design adopts a responsive layout to adapt to the screen sizes of different terminal devices, including desktop, mobile, and tablet devices, etc., to ensure that users can obtain a good user experience on different devices.

[0056] Visualization Display Unit: Provides data visualization tools, such as bar charts, line charts, maps, etc., to intuitively display various types of data. Users can quickly understand the system operation status and data trends through the visualization interface. For example, the geographical location distribution and coverage of base stations are displayed through a map, and the traffic usage in different time periods is displayed through a bar chart.

[0057] Interaction Operation Unit: Interaction functions include operations such as filtering, sorting, searching, and exporting. Users can flexibly view and process data according to their needs. Users can filter out interested data through filtering conditions, such as time range, device type, etc.; sort the data in ascending or descending order through the sorting function; quickly find specific data records through the search box; support exporting data to common formats such as Excel and PDF for convenient data sharing and further analysis.

[0058] As an implementation, this embodiment also includes: Adjacent Support Task Management Module: Configured in the user interaction layer, it is used to display all adjacent support tasks on the adjacent support task list page, supporting paging, filtering, and statistical functions; performing operations such as starting / stopping, deleting, initiating instructions, viewing details, and feedback statistics on tasks; controlling the operation permissions of task details according to task status and associated instructions, and obtaining and storing task-related data.

[0059] As an implementation, this embodiment also includes: Task List Display and Filtering Unit: When the task list is displayed, paging is performed when the data exceeds the page display. The default number of data per page is 10, which can be manually modified; the filtering function is implemented through filtering by creation time, start time, status, and fuzzy query in the search box. Among them, the creation time is accurate to the day, the start time is accurate to the hour and minute, and the status includes in progress, completed, not started, etc.; the number of support tasks, the number of completed tasks, and the number of tasks in progress are displayed in real time above the page, and the statistical information is updated in real time after operations such as adding, modifying, and deleting task data.

[0060] Task operation permission control unit: After the task is closed, the front-end page restricts and safeguards the non-modifiability of task information and points by setting read-only attributes; in the open state, if there are safeguard instructions under the safeguard task and the instructions have used safeguard points, the system queries the POINT__BASE_REL table to obtain point association information, and then judges whether the point is used by querying the POINT__PATH_REL table; according to the judgment result, the front-end sets the writable state-related fields (such as the editing permissions of fields such as task name and safeguard point information) to true or false. If the point is used, the editing permissions of the corresponding fields are set to false, otherwise set to true.

[0061] Task creation and data storage unit: When initiating a safeguard task, the accompanying safeguard person in charge is selected from the accompanying safeguard - selection of tertiary unit configuration in the list configuration, and this configuration information is stored in the sys_user table or relevant configuration tables; when adding point data, two methods of map point selection and manual input of point information are supported; the main data of the accompanying safeguard is saved to the POINT_POSITION_INFO table, including information such as task name, safeguard level, safeguard type, start time, person in charge, etc.; the added point data is saved to the POINT__BASE_REL table, including information such as point name, location, radius, etc.; the selected start time of the accompanying safeguard is recorded in the POINT_POSITION_INFO table and the POSITION_TIME_REL table, and at the same time, information such as the creation time and update time of the task is recorded in the POSITION_TIME_REL table.

[0062] As an implementation method, this embodiment further includes: Accompanying safeguard instruction processing module: Set in the user interaction layer, used to display all accompanying safeguard instructions on the accompanying safeguard instruction list page, supporting paging, filtering, and export functions; performing operations such as viewing instruction details, reminder (direct reminder and scheduled reminder), initiating new instructions, deleting instructions, etc.; when creating an accompanying safeguard instruction, select the safeguard task to obtain site data, fill in the instruction information and select the tertiary unit, and the relevant data are saved to the corresponding tables respectively. After the instruction is issued, the SMS and phone information are recorded.

[0063] As an implementation method, this embodiment further includes: Instruction list display and filtering unit: When the instruction list is paged and displayed, the default number of data per page is 10, which can be adjusted manually; the filtering conditions include issued time, start time, status, affiliated unit filtering, and fuzzy query in the search box. The issued time is accurate to hours, minutes, and seconds, and the status includes to be executed, in execution, completed, etc.; it supports exporting the list data to an Excel file, and the exported file includes header fields (point serial number, point name, location, point description, etc.) and the filtered instruction data.

[0064] Instruction Details and Reminder Operation Unit: The instruction details page displays all the data of the instruction, including the instruction number, task code, issuer, receiving enterprise, recipient, recipient's contact information, etc.; the feedback details record displays the feedback information during the execution of the instruction, including the feedback time, feedback person, feedback content, etc.; the reminder details record displays the relevant information of the reminder operation, including the reminder time, reminder person, reminder method (direct reminder or scheduled reminder), etc.; for direct reminder, after selecting the executor, the reminder instruction is issued, the reminder information is recorded, and the reminder text message is sent by calling the SMS interface and the record interface; for scheduled reminder, the start and end times and the daily reminder time are selected, and the system calls the SMS interface to issue the reminder instruction and send the SMS notification every day when the reminder time arrives within the set time period through the scheduled task mechanism.

[0065] Instruction Creation and Data Recording Unit: When creating an accompanying support instruction, query the unclosed support tasks through the POINT_POSITION_INFO table, and after selecting the task, query the site data in the POINT__BASE_REL table according to the support task Id, including the site name, location, equipment type, etc.; select the third-level unit, fill in the instruction information (such as the instruction content, support requirements, etc.) and then initiate the instruction; the content of the support instruction is saved to the POINT_INSTUCT _INFO table, the selected third-level unit is saved to the POINT__USER_REL table, and the site information selected on the page is saved to the POINT__PATH_REL table; for the first new operation, all point data is saved in the POINT__MENT_REL table, recording the initial state and relevant information of the points; after issuing the instruction, the operation information of sending SMS and making voice calls is recorded in the INSTUCT_PATH_INFO table by calling the SMS interface and the voice call interface, including the communication time, communication object, and communication content.

[0066] As an implementation manner, this embodiment further includes: an accompanying support feedback statistics module: located at the user interaction layer, used to display the detailed information, automatically summarize and statistically analyze, associate the support form, and display the daily statistical details of the task on the accompanying support feedback statistics page by selecting the support task; call the interface to obtain data and perform statistical analysis on the data related to the support task.

[0067] As an implementation manner, this embodiment includes: a task information display unit: on the accompanying support feedback statistics page, after selecting the support task through the drop-down box, display the detailed information such as the task code, support name, support level, support description, support time, task responsible person and contact information, and the support level and support type are judged and displayed by calling the dictionary type at the front end.

[0068] Automatic Summary and Statistics Unit: The system automatically counts the equipment data within the range of n kilometers from the center point of guarantee according to longitude and latitude, where n is greater than or equal to 2. Specifically, it obtains the center point coordinates of the guarantee task and queries the site data within the range in the database based on this coordinate. The queries involved are through associating the EQUIPMENT_INFO_Rel table and the BASE_NOW_INFO table to count indicators such as site type, user usage traffic, number of text messages sent, number of online sites, satellite data traffic used, number of accesses, number of calls, and call duration. For example, when counting the user usage traffic, it obtains the user traffic data of each site from the BASE_NOW_INFO table and then classifies and summarizes according to the site type. When counting the number of online sites, it judges the online status field of the sites in the EQUIPMENT_INFO_Rel table for counting.

[0069] Associated Form Display Unit: The associated form is implemented by calling the / PointPath / rel / getAssociateForms / {PointId} interface. After selecting the guarantee task, the Id of the guarantee task is automatically passed as a parameter to this interface. The backend queries the satellite resource scheduling and ground station location scheduling tasks by obtaining the Point_id field in the DISPATH_INIO table through PointId. It queries the whole network integration site application data by associating the Point_id field in the TRIPLE_NETWORK_ACCESS table. It queries all eligible accompanying guarantee instruction data by associating the Point_id field in the POINT_INSTUCT _INFO table. The data is respectively encapsulated into the corresponding List entities and then stored in the Map. The front end filters and displays the data from the returned Map. When clicking on different tasks, the Id of the task is passed to the backend, and the backend queries the detailed information from the corresponding table according to the Id and returns it to the front end for display, such as displaying the scheduling details and executor information of the satellite resource scheduling task.

[0070] Daily Statistical Details Display Unit: The daily statistical details are implemented through the / biz / BaseAllInfo / getEveryDayStatistics / {id} interface. First, query all the closed / opened times of the task in the POSITION_TIME_REL table based on the passed-in id; then traverse the set of closed / opened times, calculate the number of days in between and store them in a set; then query the specific task in the POINT_POSITION_INFO table by the id, and query the set of guaranteed points in the POINT__BASE_REL table by the id of the guaranteed task; use SQL statements to query the specific information in the BASE_ALL_INFO table, including the device operation data of each point at different times, etc.; then traverse the set, and within the traversal of the set, traverse the set of guaranteed points, and while traversing the set of guaranteed points, traverse the specific information queried from the BASE_ALL_INFO table; only when traversing the set of guaranteed points, query the feedback information of the corresponding point in the POINT__MENT_REL table, and store the data obtained each time in the PointMentRel entity. Add PointMentRel to the Map every day of statistics, and finally return the Map set to the front end to display the daily statistical details, including the device operation status of each point every day and the execution status of the guaranteed tasks.

[0071] As an implementation, this embodiment further includes: a ground station location scheduling management module: used to display all ground station location scheduling records on the ground station location scheduling page, supporting operations such as paging, filtering, initiating, generating dispatch orders, modifying, deleting, opening / closing, etc.; obtaining dispatch task data and associating other tables to obtain relevant information; when initiating a dispatch task, fill in information and select a site, and save the relevant data to the corresponding tables respectively. After generating a dispatch order, send a text message, and the task status changes.

[0072] As an implementation manner, this embodiment includes: a scheduling record list display and operation unit: when the scheduling record list is displayed, paging is supported, and 10 pieces of data are displayed per page by default. Records can be filtered through filtering conditions, including the issued time, start time, status, affiliated unit filtering, and fuzzy query in the search box; operations such as initiating a scheduling task, generating a scheduling order, modifying, deleting, enabling / disabling, etc. can be performed on the scheduling task; when generating a scheduling order, the system automatically generates a unique scheduling order number and generates a scheduling order containing task details, scheduling requirements, etc. according to the task information; the modification operation can be performed when the scheduling task has not been submitted, and the modified content is updated in real time on the page and in the database; the deletion operation is performed in three cases: when the scheduling task is completed, closed, or not submitted. When deleting, all associated data related to the scheduling task is deleted simultaneously, such as the relevant records in the DISPATH__UAV_REL table and the FLOW_PATH_INFO table.

[0073] Data acquisition and association unit: Filter out the ground station location scheduling task data through the Dis_type field in the DISPATH_INIO table, and associate and query the scheduling executor information of the task from the DISPATH__USER_REL table through the primary key Id of DISPATH_INIO, including the executor's name, contact information, etc.; Query the guarantee task name from the POINT_POSITION_INFO table through the Point_id field of DISPATH_INIO; The statistical data above the page is sourced from the / biz / DispathInfo / getTaskAllNum / {type} interface, and the parameter passed is the value of Dis_type corresponding to the ground station location scheduling. The backend performs statistics from the DISPATH_INIO table through this parameter. The scheduling task data is the quantity of all Dis_type with the specified value, the scheduled completion data is the quantity of Dis_type with the specified value and Is_submit being 2, the data in progress is the quantity of Dis_type with the specified value and Is_submit being 1, and the data to be executed is the quantity of Dis_type with the specified value and Is_submit being 0.

[0074] Dispatch task initiation and data saving unit: When initiating a dispatch task, data such as the dispatch name, start time, and end time are filled in. Among them, the end time determines that a text message and voice reminder will be sent one hour before the end time after the task is submitted; the dispatch executor data is sourced from the configuration of the ground station location dispatch executor in the list configuration; the accompanying guarantee task will display all enabled accompanying guarantee tasks, and only the Id value of the accompanying guarantee task will be recorded when saving; the site data is obtained through map selection or list selection. The detailed data of the site comes from the EQUIPMENT_INFO_Rel table. Click to generate a dispatch or only save, and add the detailed information of the dispatch task to the DISPATH_INIO table. In the DISPATH_INIO table, the Point_id saves the selected accompanying guarantee task id, and the Dis_type defaults to the identification value corresponding to the ground station location dispatch. The selected site information is recorded in the DISPATH__UAV_REL table, and the selected dispatch executor is recorded in the DISPATH__USER_REL table. When only saving, the FLOW_PATH_INFO table will not be recorded. Only when generating a dispatch will the feedback information of the currently issued task be recorded.

[0075] Although the embodiments of the present invention have been shown and described above, it can be understood that the above embodiments are exemplary and should not be construed as limiting the present invention. Those of ordinary skill in the art can make changes, modifications, substitutions, and variations to the above embodiments within the scope of the present invention.

Claims

1. A method for accompanying guarantee management collaboration of a network - compatible public network base station based on satellite communication, characterized in that: It includes the following steps: S1 Build a system architecture including a data acquisition layer, a data processing layer, a data storage layer, and a user interaction layer; The data acquisition layer collects raw data from satellite stations, base stations, and user service-related data sources, and uses API interface calls, log file parsing, and database synchronization technologies for verification and preprocessing; S2 Display all accompanying support tasks on the accompanying support task list page in the user interaction layer, supporting paging, filtering, and statistical functions; The operation permissions are different in different states for task details, and when there are support instructions under a support task, the modification of the used sites is restricted; S3 Display all accompanying support instructions on the accompanying support instruction list page in the user interaction layer; When creating an accompanying support instruction, select a support task to obtain site data, fill in the instruction information and select a third-level unit, and the relevant data are saved to the corresponding tables respectively. After issuing the instruction, record the SMS and phone information; S4 On the accompanying support feedback statistics page in the user interaction layer, display the detailed information, automatic summary statistics, associated support forms, and daily statistics details of the task by selecting the support task; Obtain data by calling the interface and perform statistical analysis on the data related to the support task; S5 Display all ground station location scheduling records on the ground station location scheduling page in the user interaction layer; Obtain scheduling task data and associate other tables to obtain relevant information; When initiating a scheduling task, fill in the information and select a site, and the relevant data are saved to the corresponding tables respectively. After generating a scheduling order, send an SMS, and the task status changes.

2. The method according to claim 1, wherein: In the S1 system architecture building step, it at least includes the following steps: S11 Data acquisition: The data acquisition layer obtains the remaining traffic, status, MIR, and CIR data of the satellite station through API interface calls, obtains the operation log data of the base station through log file parsing, and obtains the business data related to user services through database synchronization; S12 Data processing: The data processing layer uses data cleaning algorithms to remove duplicate, incorrect, and invalid data, and uses data integration technologies to associate and merge data from different data sources according to specific rules; Use data analysis algorithms to deeply analyze the data, including calculating the traffic usage trend of the site and the change law of the number of user accesses; S13 Data storage: The real-time data wide table designed in the data storage layer is used to store the real-time collected and processed data, including the real-time operation status of satellite stations and base stations, and user real-time access information; The historical data summary table summarizes and stores the data according to a time period for historical data query and analysis; Data backup adopts a combination of regular full backup and incremental backup, and the backup data is stored in off-site storage devices to ensure the security and recoverability of the data; S14 User interaction: The interface design of the user interaction layer adopts a responsive layout to adapt to the screen sizes of different terminal devices; Provide data visualization tools, such as bar charts, line charts, and maps, to intuitively display various types of data.

3. The method according to claim 2, characterized in that: In the S2 accompanying support task management step, it at least includes the following steps: S21 Task List Display and Filtering: When the task list is displayed, if the data exceeds the page display, paging is performed; the filtering function is implemented through filtering by creation time, start time, status, and fuzzy query in the search box. Among them, the creation time is accurate to the day, the start time is accurate to the hour and minute, and the status includes in progress, completed, and not started; the number of guarantee tasks, the number of completed tasks, and the number of tasks in guarantee are displayed in real time above the page, and the statistical information is updated in real time after the addition, modification, or deletion of task data; S22 Task Operation Permission Control: After the task is closed, the front-end page restricts the non-modification of guarantee task information and points by setting the read-only property; in the open state, if there is a guarantee instruction under the guarantee task and the instruction has used the guarantee point, the system queries the POINT__BASE_REL table to obtain the point association information, and then judges whether the point is used by querying the POINT__PATH_REL table; according to the judgment result, the front-end sets the writable state-related fields to true or false. If the point is used, the editing permission of the corresponding field is set to false, otherwise it is set to true; S23 Task Creation and Data Storage: When initiating a guarantee task, the accompanying guarantee person is selected from the accompanying guarantee - select the third-level unit configuration in the list configuration, and this configuration information is stored in the sys_user table or the relevant configuration table; when adding point data, two methods of selecting points on the map and manually entering point information are supported; the main data of the accompanying guarantee is saved to the POINT_POSITION_INFO table, the added point data is saved to the POINT__BASE_REL table, the selected start time of the accompanying guarantee is recorded in the POINT_POSITION_INFO table and the POSITION_TIME_REL table, and at the same time, the creation time and update time information of the task are recorded in the POSITION_TIME_REL table.

4. The method according to claim 3, wherein In the S3 accompanying guarantee instruction processing steps, at least the following steps are included: S31 Instruction List Display and Filtering: When the instruction list is paged and displayed, the default number of data per page is 10, which can be adjusted manually; the filtering conditions include filtering by issued time, start time, status, affiliated unit, and fuzzy query in the search box, and the issued time is accurate to the hour, minute, and second; it supports exporting the list data to an Excel file, and the header fields included in the export include point serial number, point name, location, point description, and the filtered instruction data; Details of S32 Instruction and Reminder Operation: All data of the instruction are displayed on the instruction details page, including instruction number, task code, issuer, receiving enterprise, receiver, and receiver's contact information; detailed feedback records display the feedback information during the execution of the instruction, and detailed reminder records display the relevant information of the reminder operation, including reminder time, reminder person, and reminder method; for direct reminder, after selecting the executor, the reminder instruction is issued, the reminder information is recorded, and the reminder text message is sent by calling the SMS interface and the record interface; for scheduled reminder, the start and end times and the daily reminder time are selected. The system calls the SMS interface to issue the reminder instruction and send a text message notification every day when the reminder time arrives within the set time period through the scheduled task mechanism. S33 Instruction Creation and Data Recording: When creating an accompanying support instruction, unclosed support tasks are queried through the POINT_POSITION_INFO table. After selecting a task, site data is queried from the POINT__BASE_REL table based on the support task Id; a third-level unit is selected, and the instruction information, including instruction content and support requirements, is filled in and then the instruction is initiated; the content of the support instruction is saved to the POINT_INSTUCT_INFO table, the selected third-level unit is saved to the POINT__USER_REL table, and the site information selected on the page is saved to the POINT__PATH_REL table; for the first new operation, all point data is saved in the POINT__MENT_REL table, recording the initial status and relevant information of the points; after issuing the instruction, the operation information of sending text messages and making voice calls, including communication time, communication object, and communication content, is recorded in the INSTUCT_PATH_INFO table by calling the SMS interface and the voice call interface.

5. The method according to claim 4, characterized in that: The S4 accompanying support feedback statistics step at least includes the following steps: S41 Task Information Display: On the accompanying support feedback statistics page, after selecting a support task through the dropdown box, detailed information such as task code, support name, support level, support description, support time, task responsible person, and contact information is displayed. S42 Automatic Aggregation and Statistics: The system automatically statistics the equipment data within n kilometers of the support center point according to longitude and latitude, where n is greater than or equal to 2; specifically, by obtaining the center point coordinates of the support task, the site data within the range is queried from the database based on this coordinate; the queries involved are through associating the EQUIPMENT_INFO_Rel table and the BASE_NOW_INFO table to statistics indicators such as site type, user traffic used, number of text messages sent, number of online sites, satellite data traffic used, number of accesses, number of calls, and call duration. When statistics the user traffic used, the user traffic data of each site is obtained from the BASE_NOW_INFO table and then classified and summarized according to the site type. When statistics the number of online sites, the online status field of the sites in the EQUIPMENT_INFO_Rel table is judged for counting. S43 Associated form display: The associated form is implemented by calling an interface; after selecting a guarantee task, the Id of the guarantee task is automatically passed as a parameter to this interface; the backend queries the satellite resource scheduling and ground station location scheduling tasks by obtaining the PointId and associating with the Point_id field in the DISPATH_INIO table; queries the application data of the whole network integration sites by associating with the Point_id field in the TRIPLE_NETWORK_ACCESS table; queries all eligible accompanying guarantee instruction data by associating with the Point_id field in the POINT_INSTUCT_INFO table. The data is respectively encapsulated into corresponding List entities and then stored in a Map. The front-end filters and displays the data from the returned Map; when clicking on different tasks, the Id of the task is passed to the backend, and the backend queries the detailed information from the corresponding table according to the Id and returns it to the front-end for display, including displaying the scheduling details and executor information of the satellite resource scheduling task. S44 Daily statistics details display: The daily statistics details are implemented through an interface; first, query all the closed / opened times of this task in the POSITION_TIME_REL table by passing in the id; then traverse the set of closed / opened times, calculate the number of days in between and store it in a set; then query the specific task in the POINT_POSITION_INFO table by the id, and query the set of guarantee points in the POINT__BASE_REL table by the id of the guarantee task; query the specific information in the BASE_ALL_INFO table through an sql statement, including the device operation data of each point at different times; then traverse the set, and within the set traversal, traverse the set of guarantee points, and while traversing the set of guarantee points, traverse the specific information queried from the BASE_ALL_INFO table; only when traversing the set of guarantee points, query the feedback information of the corresponding point in the POINT__MENT_REL table, and store the data obtained each time in the PointMentRel entity. Add PointMentRel to the Map every day of statistics, and finally return the Map collection to the front-end to display the daily statistics details, including the device operation conditions of each point every day and the execution conditions of the guarantee tasks.

6. The method according to claim 1, wherein The S5 ground station location scheduling management steps at least include the following steps: S51 Scheduling Record List Display and Operations: When displaying the scheduling record list, paging is supported. By default, 10 pieces of data are displayed per page. Records can be filtered through filtering conditions, including issued time, start time, status, affiliated unit filtering, and fuzzy query in the search box. Operations such as initiating, generating a dispatch order, modifying, deleting, and enabling / disabling the scheduling task can be performed. When generating a dispatch order, the system automatically generates a unique dispatch order number and generates a dispatch order containing task details and scheduling requirements based on the task information. The modification operation can be performed when the scheduling task has not been submitted, and the modified content is updated in real time on the page and in the database. The deletion operation is performed in three cases: when the scheduling task is completed, closed, or not submitted. When deleting, all associated data related to the scheduling task is deleted simultaneously, including relevant records in the DISPATH__UAV_REL table and FLOW_PATH_INFO table. S52 Data Acquisition and Association: Filter out the ground station location scheduling task data through the Dis_type field in the DISPATH_INIO table. Query the scheduling executor information of the task, including the executor's name and contact information, by associating and querying through the primary key Id of DISPATH_INIO in the DISPATH__USER_REL table. Query the guarantee task name in the POINT_POSITION_INFO table through the Point_id field of DISPATH_INIO. The statistical data above the page comes from the parameter passed by the interface, which is the value of Dis_type corresponding to the ground station location scheduling. The backend performs statistics from the DISPATH_INIO table through this parameter. The scheduling task data is the quantity of all Dis_type with the specified value. The completed scheduling data is the quantity of Dis_type with the specified value and Is_submit equal to 2. The scheduling-in-progress data is the quantity of Dis_type with the specified value and Is_submit equal to 1. The to-be-executed data is the quantity of Dis_type with the specified value and Is_submit equal to 0. S53 Scheduling Task Initiation and Data Saving: When initiating a scheduling task, fill in the scheduling name, start time, and end time data. Among them, the end time determines that a text message and voice reminder will be sent one hour before the end time after the task is submitted; the scheduling executor data is sourced from the configuration of the ground station location scheduling executor in the list configuration; the accompanying guarantee tasks will display all enabled accompanying guarantee tasks, and only the Id value of the accompanying guarantee tasks will be recorded when saving; the site data is obtained through map selection or list selection, and the detailed data of the site comes from the EQUIPMENT_INFO_Rel table. Click to generate a schedule or only save, and add the detailed information of the scheduling task to the DISPATH_INIO table. In the DISPATH_INIO table, Point_id saves the selected accompanying guarantee task id, and Dis_type defaults to the identification value corresponding to the ground station location scheduling. The selected site information is recorded in the DISPATH__UAV_REL table, and the selected scheduling executor is recorded in the DISPATH__USER_REL table. When only saving, the FLOW_PATH_INFO table will not be recorded, and only when generating a schedule will the feedback information of the currently issued task be recorded.

7. A satellite communication-based accompanying guarantee management collaboration system for a full-network public network base station, characterized in that: This system is used to implement the method described in any one of claims 1 to 6 above. The system at least includes: System Architecture Building Module: Build a system architecture covering the data acquisition layer, data processing layer, data storage layer, and user interaction layer; the data acquisition layer collects raw data from satellite stations, base stations, and user service-related data sources, and performs verification and preprocessing using API interface calls, log file parsing, and database synchronization technologies; the data processing layer uses cleaning, integration, and analysis algorithms to identify and correct data errors and outliers, classify, aggregate, and transform data according to business requirements, and at the same time support custom processing logic; the data storage layer designs real-time data wide tables and historical data summary tables to store data, and has data backup and recovery functions; the user interaction layer adopts an intuitive and easy-to-use interface design, provides data visualization tools, interaction functions, and data export functions to support data interaction and display for accompanying guarantee services; Accompanying Guarantee Task Management Module: Display all accompanying guarantee tasks on the accompanying guarantee task list page of the user interaction layer, supporting paging, filtering, and statistical functions; operations such as enabling / disabling, deleting, initiating instructions, viewing details, and feedback statistics can be performed on tasks; the operation permissions for task details are different in different states, and when there are guarantee instructions under the guarantee task, the modification of the used sites is restricted; obtain task-related information and store task data to achieve the full life cycle management of accompanying guarantee tasks; Accompanying Support Instruction Processing Module: Display all accompanying support instructions on the accompanying support instruction list page in the user interaction layer, supporting paging, filtering, and export functions; capable of viewing instruction details, reminding, initiating new instructions, and deleting instructions; when creating an accompanying support instruction, select the support task to obtain site data, fill in the instruction information and select the third-level unit, and save the relevant data to the corresponding tables respectively. After issuing the instruction, record the SMS and call information to track the effective transmission and execution of the support instruction; Accompanying Support Feedback Statistics Module: On the accompanying support feedback statistics page in the user interaction layer, display the detailed information of the task, automatically summarize and statistically analyze, associate the support form, and show the daily statistical details of the task by selecting the support task; obtain data by calling the interface, conduct statistical analysis on the data related to the support task, and provide data support for the evaluation of the accompanying support effect; Ground Station Location Scheduling Management Module: Display all ground station location scheduling records on the ground station location scheduling page in the user interaction layer, supporting paging, filtering, initiating, generating a scheduling order, modifying, deleting, and enabling / disabling operations; obtain scheduling task data and associate other tables to obtain relevant information; when initiating a scheduling task, fill in the information and select the site, and save the relevant data to the corresponding tables respectively. After generating the scheduling order, send an SMS, and the task status changes to achieve the coordination of ground station location scheduling and accompanying support tasks.

8. The accompanying support management and coordination system for the network-wide public network base station based on satellite communication according to claim 7, characterized in that: System Architecture-related Sub-module: The data acquisition layer obtains the remaining traffic, status, MIR, and CIR data of the satellite station through API interface calls, obtains the operation log data of the base station through log file parsing, and obtains the business data related to user services through database synchronization; The data processing layer uses data cleaning algorithms to remove duplicate, incorrect, and invalid data, applies data integration technologies to associate and merge data from different data sources according to specific rules, and uses data analysis algorithms to deeply analyze the data; The real-time data wide table designed in the data storage layer is used to store the real-time collected and processed data, and the historical data summary table summarizes and stores the data according to the time period; the interface design in the user interaction layer adopts a responsive layout, provides data visualization tools, and the interaction functions include filtering, sorting, searching, and export operations, supporting data export in common formats such as Excel and PDF; Accompanying Support Task Management Sub-module: When the task list is displayed, paging is performed when the data exceeds the page display; The filtering function is realized through filtering by creation time, start time, status, and fuzzy query in the search box; the number of support tasks, the number of completed tasks, and the number of tasks in progress are displayed in real time above the page; after the task is closed, the front-end page restricts the modification of support task information and points; when the support task is in the open state and there are support instructions under the support task and the support points have been used, it is judged whether the point can be modified by querying the relevant tables; when initiating a support task, the accompanying support person in charge is selected from the list configuration, and the point data is added, and the relevant data is saved to the corresponding tables respectively.

9. The accompanying guarantee management collaboration system for the satellite communication-based all-net public network base station according to claim 8, characterized in that: Accompanying guarantee instruction processing sub-module: When the instruction list is displayed in pages; the screening conditions include the issuing time, start time, status, affiliated unit screening, and fuzzy query in the search box; The instruction details page displays all data of the instruction, detailed feedback records, and detailed reminder records; for direct reminder, after selecting the executor, a reminder instruction is issued, the reminder information is recorded, and a reminder text message is sent; for scheduled reminder, the start and end times and the daily reminder time are selected, and the system issues a reminder instruction and sends a text message notification every day when the reminder time arrives within the set time period; when creating an accompanying guarantee instruction, the guarantee task and site data are obtained by querying the relevant tables, the third-level unit is selected, the instruction information is filled in, and then the instruction is initiated. The relevant data are respectively saved in the corresponding tables, and the text message and phone operation information are recorded after the instruction is issued; Accompanying guarantee feedback statistics sub-module: When displaying the detailed information of the guarantee task, the guarantee task is selected through a drop-down box; the automatic summary statistics are used to count the equipment data within a certain range of the guarantee center point according to the longitude and latitude; the associated form is realized by calling an interface. After selecting the guarantee task, the parameters are automatically passed, and the backend associates and queries the relevant data and encapsulates them, and the frontend filters and displays them; the daily statistics details are realized through an interface. According to the incoming task id, the relevant time, location, and equipment data are queried, and after statistical analysis, they are returned to the frontend for display.

10. The accompanying guarantee management collaboration system for the satellite communication-based all-net public network base station according to claim 9, characterized in that: Ground station location scheduling management sub-module: When the scheduling record list is displayed, paging is supported, and the records can be screened through the screening conditions; operations such as initiating, generating a scheduling order, modifying, deleting, and opening / closing the scheduling task can be performed; When generating a scheduling order, the system automatically generates a unique scheduling order number and generates the content of the scheduling order according to the task information; The modification operation is performed when the scheduling task is in an unsubmitted state, and the deletion operation is performed under specific circumstances and the associated data is deleted at the same time; the data acquisition and association are realized through the screening and associated query of the relevant table fields; when initiating a scheduling task, the relevant information is filled in and the site is selected, and the relevant data are respectively saved in the corresponding tables. After the scheduling order is generated, a text message is sent, the task status changes, and the reminder function for the end time and the record rules of the relevant tables under different save operations are considered.

Images