Whole list management method and system of all-network public network base station based on satellite communication

Abstract

The invention relates to a white list management method of an all-network public network base station based on satellite communication, and belongs to the technical field of satellite communication. A user inputs or uploads a mobile phone number, the mobile phone number platform converts the mobile phone number into an IMSI and pushes the IMSI to an all-network public network base station, the base station processes the IMSI and then returns successful information, and the user can dynamically manage a white list. The platform is provided with a white list management page and is provided with functional modules such as list displaying, screening, pushing, editing and deleting, white list information is stored in a NOTCIEINFO table and is associated with a Pushnoice table through fields, and a whole-website white list interface is called through pushing operation. The white list effective time is greatly shortened through an automatic process, and the emergency communication response speed is improved; dynamic resource allocation is realized, and resource waste is avoided; the practicability and usability of the system are improved, and the emergency communication guarantee capability and the communication resource utilization efficiency can be effectively improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of satellite communication, and particularly relates to the technical field of whitelist management for realizing high-priority communication for specific users in a full-network public network base station in an emergency communication scenario. Specifically, it relates to a whitelist management method and system for a full-network public network base station based on satellite communication. Background Art

[0002] In the modern communication system, public network base stations are crucial for ensuring user communication. Currently, the conventional way for public network base stations to implement whitelists is for technical personnel of major operators to manually configure operations in their respective core networks. However, in an emergency communication scenario, this traditional method exposes many problems.

[0003] In terms of full-network public network base stations, there has not been a dedicated and effective whitelist management case before. When facing emergencies such as natural disasters or major emergencies, the number of users accessing the full-network public base station for communication is often severely limited. Once the number of base station accesses reaches the upper limit, those who play key roles in emergency rescue operations and need to ensure communication priority, such as disaster relief commanders and front-line rescue personnel, may not be able to communicate smoothly, which seriously hinders the efficient development and coordinated command of rescue work.

[0004] The traditional method of ensuring priority is to manually transfer the whitelist to relevant personnel of the three major operators, and then they deploy it to the core network to enable communication for users on the list under a specific base station. This method has obvious drawbacks: First, the efficiency is extremely low, and the entire process basically takes about 2 days. In the emergency rescue situation where every minute counts, such a long wait may lead to missing the best rescue opportunity; Second, due to the list being transferred among different entities multiple times, there is a great risk of leakage. Especially when it comes to ensuring the communication of important government personnel (such as leaders, governors, ministers, etc.), once the information is leaked, it may cause serious security risks, threatening the personal safety of relevant personnel and the confidentiality of rescue operations; Third, the previous release policy was too simple and crude. As long as a person is not on the whitelist, they cannot communicate, which makes emergency communication resources not fully utilized, resulting in the idle and waste of resources and unable to meet the diverse communication needs in actual emergency scenarios.

[0005] In summary, the existing whitelist management methods for public network base stations have significant deficiencies in the application of full-network public network base stations and emergency communication guarantee. There is an urgent need for a new, efficient, and secure whitelist management method to fill this technical gap and improve the reliability and effectiveness of emergency communication. Summary of the Invention

[0006] In view of this, the purpose of the present invention is to overcome the deficiencies of the prior art and provide a white list management method for a full-network public network base station based on satellite communication. By means of innovative technical means and process optimization, it can quickly and accurately configure and manage the white list, effectively avoiding the low efficiency problem caused by traditional manual operations; using advanced encryption and security protection strategies to strictly protect the security of white list information during transmission and storage, eliminating the risk of list leakage; at the same time, adopting an intelligent priority determination and resource allocation mechanism to give full play to the effectiveness of emergency communication resources and overcome the resource waste phenomenon caused by previous release strategies, so as to build a new, efficient, safe and reasonable system for the white list management of the full-network public network base station in the emergency communication scenario, effectively guaranteeing the communication needs of key users and improving the utilization efficiency of the overall communication resources.

[0007] To achieve the above object, the technical solution adopted by the present invention is as follows: In the first aspect of the present invention, a white list management method for a full-network public network base station based on satellite communication is provided, including the following steps: Step S1: The user performs secondary authentication to log in to the platform, and after successful login, enters or uploads white list information containing mobile phone numbers. Step S2: After the platform receives the mobile phone number submitted by the user, it requests the operator interface for the mobile phone number to convert the mobile phone number into an International Mobile Subscriber Identity (IMSI); after processing by the operator interface, the corresponding IMSI is returned to the platform. Step S3: The platform pushes the obtained IMSI to the full-network public network base station according to the time requirement; after the full-network public network base station processes the IMSI, it returns a successful entry message to the platform, and the platform displays that the push is successful; it displays on the interface that the full-network public network base station has successfully entered, so that the user knows that the white list has been successfully effective at the base station. Step S4: The platform is provided with an intelligent judgment mechanism to ensure the accurate push and security protection of the IMSI; the platform does not store the IMIS throughout the process, and directly pushes it to the base station after reading it completely through the interface, and there is no IMSI information in the system after the push. In step S4, the platform is set with an intelligent judgment mechanism after data push Step S41 sets a time limit, which starts counting from the moment when the platform pushes the IMSI data to the base station side. Step S42: If the base station side normally receives the pushed IMSI data and returns a successful data reception within the specified time, the IMIS data on the platform side automatically becomes invalid to ensure data security. Step S43: If the base station side does not normally return the data reception information within the specified time, the platform then starts interface verification. After passing the verification, a new push is started until it is successfully pushed to the base station side, and the IMSI data automatically becomes invalid. Step S5: The user can perform operations of adding, deleting, modifying, and querying the effective whitelist as needed to achieve dynamic management of the whitelist.

[0008] Furthermore, the communication between the platform and the operator interface uses the POST method in the HTTP method. The request parameters include an array of mobile phone numbers, and the return value format is a JSON object, which includes the result indicating success or failure, the status code, the error message, and an array of IMSI data.

[0009] Furthermore, the platform is provided with a whitelist management page to manage the whitelist of the whole network integration site, which has the following function modules: List display module: All whitelists are displayed in the list. When the data exceeds the page display amount, paging display is performed. By default, 10 pieces of data are displayed per page and can be manually modified. The number of items displayed per page can be selected through the paging dropdown. When there are multiple pages, the corresponding page can be jumped to by entering a number in the paging input box; Filter function module: A filter box is provided, and whitelist records can be filtered out and displayed in the list through time filtering and fuzzy query in the search box; List push operation module: Select the required site for list push, and the push record will display all push records of this whitelist; List editing operation module: The data of this whitelist can be edited, including deleting personnel information, exporting the list to Excel format to the local, downloading the template, entering personnel, and then importing the list; List deletion operation module: The data of this whitelist and all related content data can be deleted.

[0010] Furthermore, the whitelist information data is sourced from the NOTICE_INFO table, where: To add new whitelist data, call the PostMapping interface under / biz / NoticeInfo to add; For list editing, call the PutMapping interface under / biz / NoticeInfo; For list deletion, call the / biz / NoticeInfo / {ids} interface; For list push, select the site and call the whitelist push interface. The push information is called to the external interface - the whole network whitelist interface. The input parameter information is SiteId and the whitelist list, and the push information is inserted into the PUSH_NOTICE table as a data record. The push list is queried from the NOTICE_INFO table through the / biz / NoticeInfo / list interface and displayed.

[0011] Further, the NOTCIE_INFO table is associated with the Push_notice table through set fields. The Push_notice table records push-related information about one or more of the push site, time, pusher, and result. In the list push operation, the whole-network whitelist interface is called to achieve effective control and update of whitelist data across the network, ensuring the synchronization and accurate application of data between different systems.

[0012] Further, NOTCIE_INFO is the main table; the Push_notice table is associated with the notice_info table through the notice_id field and the id field of the notice_info table.

[0013] The second aspect of the present invention provides a whole-network public network base station whitelist management system based on satellite communication, characterized in that: the system is used to implement the method described in any one of the above claims 1 to 6, and the system at least includes: User interaction module: used for users to perform secondary authentication to log in to the platform. After successful login, it supports users to enter or upload whitelist information containing mobile phone numbers, and receives user operation instructions for adding, deleting, modifying, and querying the whitelist; and after the platform displays the successful entry information of the whole-network public network base station, it provides an interactive interface for users to perform relevant operations based on the effective whitelist. Number conversion module: connected to the user interaction module, receives the mobile phone number submitted by the user, sends a request to the operator interface to convert the mobile phone number into an International Mobile Subscriber Identity (IMSI), and receives the IMSI data returned by the operator interface. Data push module: connected to the number conversion module, obtains the IMSI data obtained by the number conversion module, and pushes the IMSI to the whole-network public network base station according to time requirements; at the same time, receives the successful entry information returned by the whole-network public network base station and transmits this information to the user interaction module for display. Intelligent judgment and security protection module: connected to the data push module, starts timing when the data push module pushes the IMSI data to the base station side; if the base station side normally receives the pushed IMSI data within the specified time and returns successful data reception, the IMSI data on the platform side is automatically invalidated; if the base station side does not normally return the data reception information within the specified time, interface verification is started. After verification passes, the data push module is notified to start a new push until it is successfully pushed to the base station side, and the IMSI data is automatically invalidated; this module ensures that the platform does not store IMSI throughout the process, and only realizes the transfer of IMSI through interface reading and pushing. Whitelist Management Page Module: It has a list display module, a filtering function module, a list push operation module, a list editing operation module, and a list deletion operation module. The list display module is used to display all whitelists in a list. When the data exceeds the page display amount, it is paged. By default, 10 pieces of data are displayed per page and manual modification is supported. The number of items displayed per page can be selected by clicking on the paging dropdown. When there are multiple pages, the corresponding page can be jumped to by entering a number in the paging input box; The filtering function module provides a filtering box, supporting filtering out whitelist records through time filtering and fuzzy query in the search box and displaying them in the list; The list push operation module supports selecting the required sites for list push and records the push information. The push records will display all push records of this whitelist; The list editing operation module can perform editing operations on the data of this whitelist, including deleting personnel information, exporting the list to Excel format to the local, downloading a template, entering personnel, and then importing the list; The list deletion operation module can delete the data of this whitelist and all related content data; Data Storage and Management Module: It includes the NOTICE_INFO table and the Push_notice table. The NOTICE_INFO table is the main table, storing the core information of the whitelist. The Push_notice table is associated with the id field of the NOTICE_INFO table through the notice_id field, and is used to record one or more push-related information such as the push site, time, pusher, and result; The data of the whitelist management page module comes from the NOTICE_INFO table. When adding new whitelist data, the PostMapping interface under / biz / NoticeInfo is called to add it to the NOTICE_INFO table. When editing the list, the PutMapping interface under / biz / NoticeInfo is called to modify the data in the NOTICE_INFO table. When deleting the list, the / biz / NoticeInfo / {ids} interface is called to delete the data from the NOTICE_INFO table; When performing the list push operation, the push whitelist interface is called during the push. The push information is called through an external interface - the full-site whitelist interface, with the input parameter information being SiteId and the whitelist list. And data records of the push information are inserted into the Push_notice table. The push list is displayed by querying the NOTICE_INFO table through the / biz / NoticeInfo / list interface; Communication Interface Module: It is responsible for the communication between the platform and the operator interface. The POST method in the HTTP method is used for data transmission. The request parameters include an array of mobile phone numbers, and the received return value is data in JSON format. This data includes the result indicating success or failure, the status code, the error message, and an array of IMSI data; Further, the list display module of the whitelist management page module reads the whitelist data from the NOTICE_INFO table and displays it in reverse order according to the list creation time; when the data volume exceeds 10 items displayed by default on the page, the system automatically performs paging processing. The paging component has a quick jump function. After the user enters the page number in the paging input box and clicks the "Jump" button, the system can complete the data loading and display the data of the corresponding page; when the user clicks the paging dropdown menu to select the number of items displayed per page, the system immediately updates the list display data, and during the process of switching pages or the number of items displayed, the table header of the list is always fixed and displayed; The time filtering of the filtering function module of the whitelist management page module supports filtering by day, week, month, and custom time period. When filtering by custom time period, the user can accurately select the start time and end time through the calendar control. The system queries in the background based on the time range selected by the user on the CREATE_TIME field of the NOTICE_INFO table to quickly filter out the whitelist records that meet the conditions; the fuzzy query function of the search box supports comprehensive fuzzy matching of multiple fields such as list name, list description, and creator. After the user enters the keyword, the system starts searching and displays the matched whitelist records in the list in real time. The search results will be dynamically updated according to the changes in the user input content; Further, after the user clicks the list push button, the site selection interface popped up by the list push operation module of the whitelist management page module displays the information of the public network base station sites of the whole network in a tree structure, including site classifications in different regions and different operators; after selecting the site, the system automatically obtains the current logged-in user information as the pusher information, and uses the SiteId, whitelist list, and pusher information as parameters to call the push whitelist interface and the external interface - the whole network whitelist interface for data push; during the push process, the system displays the push progress bar in real time. After the push is completed, according to the result returned by the base station, the push time, push site, push result, and failure reason are detailedly recorded in the push record. The push records can be sorted and viewed according to the push time; When the list editing operation module of the whitelist management page module deletes personnel information, after the user clicks the delete button, the system pops up a confirmation delete dialog box, prompting the user that the delete operation cannot be restored, and displaying the details of the personnel information to be deleted; after the user confirms, the system calls the PutMapping interface under / biz / NoticeInfo, and deletes the corresponding record from this table according to the unique identifier of the personnel information in the NOTICE_INFO table, and synchronously updates the relevant associated data; when exporting the list as an Excel format file, the system fills in the data according to the preset Excel template, and the template includes fields such as list name, list description, mobile phone number, creation time, etc., and the name of the exported file is named in the format of "whitelist_export time.xlsx"; for the Excel template file provided by the download template function, the filling requirements and examples of each field are clearly marked in the table header. After the user fills in the personnel information according to the requirements and clicks the import button, the system calls the PostMapping interface under / biz / NoticeInfo to parse and verify the data of the imported Excel file. If the data format is correct and conforms to the business rules, the data will be added to the NOTICE_INFO table. After the import is successful, the system gives a success prompt and immediately updates and displays the newly added personnel information in the list.

[0014] Further, when the user selects the whitelist record to be deleted and clicks the delete button in the list deletion operation module of the whitelist management page module, the system first performs permission verification, and only users with administrator privileges or specific authorizations can perform the delete operation; after the verification passes, the system pops up a secondary confirmation dialog box, prompting the user that the delete operation will simultaneously delete the whitelist and all its related push records and associated data, and cannot be restored; after the user confirms again, the system calls the / biz / NoticeInfo / {ids} interface, and deletes the corresponding record from the NOTICE_INFO table according to the primary key ID of the whitelist in the NOTICE_INFO table, and cascades to delete all push records related to this whitelist in the Push_notice table. After the delete operation is completed, the system automatically refreshes the list page to display the whitelist data after deletion; The length limit of the name field in the NOTICE_INFO table of the data storage and management module is 100 characters. The Explain_note field is stored in rich text format. The Notice_type field reserves extension values in addition to distinguishing between whitelists and blacklists. The CREATE_BY field is associated with the system user table and stores the user ID of the creator. The CREATE_TIME field uses a timestamp accurate to the second to record the creation time. The UPDATE_BY field is associated with the system user table and records the user ID of the last modifier. The UPDATE_TIME field is automatically updated to the current timestamp each time the whitelist information is modified; A foreign key constraint is established between the notice_id field in the Push_notice table of the data storage and management module and the id field in the NOTICE_INFO table; the push site information is stored in the site_id field, adopting a coding format corresponding to the unique identifier of the network-wide public network base station site; the push time field records the exact time when the push operation occurs, accurate to milliseconds; the pusher information is stored in the operator_id field, associated with the user ID of the system user table; the push result field is represented by enumerated values, including statuses such as "success", "failure", and "partial success". If the push result is "failure" or "partial success", the reason for failure or the specific situation of partial success is detailedly recorded in the remark field.

[0015] The present invention adopts the above technical solutions, and has the following specific beneficial effects: 1. Through the automated interaction process between the platform, operator interfaces, and base stations, the present invention abandons the cumbersome way of manually configuring the whitelist in the traditional manner, greatly shortening the time required for the whitelist to take effect. In emergency communication scenarios, it can quickly grant communication permissions to important users, ensuring that key roles such as disaster relief commanders and front-line rescue personnel can obtain communication guarantees in a timely manner, effectively avoiding the obstacles to rescue work caused by communication delays, and greatly improving the response speed and overall efficiency of emergency communication.

[0016] 2. In the technical solution provided by the present invention, strict security measures, such as secondary authentication, are set at key links such as user login and successful information feedback and entry by the base station, effectively preventing information leakage and illegal operations. Especially when it comes to ensuring the communication of important personnel, the strict security protection can significantly reduce the security risks during the list transmission process, ensuring the confidentiality of communication content and the security of the communication link, and effectively maintaining the security and stability of emergency communication.

[0017] 3. The present invention changes the previous simple and extensive release strategy, realizing dynamic resource allocation according to user priorities and actual communication needs. On the premise of ensuring the smooth communication of important users, it can reasonably utilize communication resources, allow a certain degree of access by other users, avoid the idle and waste of emergency communication resources, give full play to the maximum efficiency of communication resources, improve the quality and fairness of communication services, and better meet the complex and changeable communication needs in emergency scenarios.

[0018] 4. Users of the present invention can add, delete, modify and check the whitelist at any time according to actual needs, and the platform provides a rich variety of screening, pushing and editing functions. For example, in the whitelist management of the whole network integrated site, the whitelist information can be quickly located and processed in a variety of ways, supporting efficient management and flexible adjustment of the list data, making the whitelist management more in line with the actual application scenarios, adapting to the ever-changing communication guarantee needs, and effectively improving the practicality and ease of use of the system. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0020] Figure 1 It is an interactive timing diagram of the whitelist management method of the present invention; Figure 2 It is a schematic diagram of the whitelist association relationship of the present invention. DETAILED DESCRIPTION

[0021] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Instead, they are merely examples of devices and methods consistent with some aspects of the present invention as detailed in the appended claims. Embodiment 1

[0022] See also Figure 1 This embodiment provides a whitelist management method for a satellite communication-based all-network public network base station, comprising the following steps: Step S1: The user performs secondary authentication to log in to the platform, and enters or uploads whitelist information containing the mobile phone number after successful login; Step S2: After receiving the mobile phone number submitted by the user, the platform interfaces the mobile phone number with the operator and requests to convert the mobile phone number into an international mobile subscriber identity code (IMSI); after the operator interface processes the number, the corresponding international mobile subscriber identity code (IMSI) is returned to the platform; Step S3, the platform pushes the acquired International Mobile Subscriber Identity IMSI to the all-network public network base station according to the time requirement; after processing the IMSI, the all-network public network base station returns the entry success information to the platform, and the platform displays the push success; the all-network public network base station entry success is displayed on the interface, letting the user know that the whitelist has been successfully effective at the base station; Step S4: The platform is equipped with an intelligent judgment mechanism to ensure the accurate push and security protection of the International Mobile Subscriber Identity (IMSI); the platform does not store the IMIS throughout the process. It directly reads through the interface and pushes it to the base station. After the push, there is no IMSI information in the system anymore; In step S4, the platform is set with an intelligent judgment mechanism after data push Step S41 sets a time limit, which starts counting from the moment when the platform pushes the IMSI data to the base station side; In step S42, if the base station side normally receives the pushed IMSI data and returns a successful data reception within the specified time, the IMIS data on the platform side automatically becomes invalid to ensure data security; In step S43, if the base station side does not normally return the data reception information within the specified time, the platform then starts interface verification. After passing the verification, a new push is started until it is successfully pushed to the base station side, and the IMSI data automatically becomes invalid; Step S5: The user can perform operations of adding, deleting, modifying, and querying the effective whitelist according to needs to realize the dynamic management of the whitelist.

[0023] As an implementation method, in this embodiment, after receiving the IMSI data returned by the operator interface, the platform pushes the IMSI data to the network - compatible public network base station through the operator interface according to the preset time interval and push rules. During the push process, to ensure the stability and integrity of data transmission, an encrypted transmission protocol is adopted to prevent data from being stolen or tampered with.

[0024] After receiving the IMSI data, the network - compatible public network base station stores it in the local database and performs legality verification and processing. After the processing is completed, the base station returns a successful entry message to the platform. After receiving the successful message, the platform displays a prompt on the interface indicating that the network - compatible public network base station has successfully entered, so that the user knows that the whitelist has been successfully activated at the base station.

[0025] In this embodiment, the IMIS is not stored at all during the whole process. The transfer of the IMIS is realized through interface reading and pushing throughout the process, that is, there is no cache or database of the IMIS in the platform.

[0026] As an implementation method, in this embodiment, the communication between the platform and the operator interface adopts the POST method in the HTTP method. The request parameters include an array of mobile phone numbers, and the return value format is a JSON object, which includes results indicating success or failure, status codes, error messages, and an array of IMSI data.

[0027] The interaction between the platform and the operator interface in this embodiment is as follows: After the platform receives the mobile phone number submitted by the user, it sends a request to the operator interface in the POST manner according to the HTTP protocol. The request parameters are organized in JSON format, which contains an array field named "numbers" for mobile phone numbers. The mobile phone number submitted by the user is encapsulated in this array and sent to the operator interface.

[0028] After the operator interface receives the request, it converts the mobile phone number into the corresponding IMSI (International Mobile Subscriber Identity) according to the internal conversion algorithm and database query. After the processing is completed, the operator interface returns the result to the platform in the form of a JSON object. This JSON object contains a "result" field indicating success or failure of the operation (0 represents success, 1 represents failure), an "errorCode" field indicating the status code (such as 200 represents normal, and other values represent different error types), an "errorMsg" field for describing the specific error information (such as data reading failure, etc.), and an "imsi" field, which is an array of IMSI data, with each IMSI value separated by an English comma. For example, the call example: Request data example: {"numbers":["156XXXXXXXX","156XXXXXXXX","156XXXXXXXX"]} Return data example: { "result":"0", "errorCode":"200", "errorMsg":"", "data":{"imsi":["460070123456053","460070123456054"]} }。

[0029] As an implementation manner, in this embodiment, the platform is provided with a whitelist management page to manage the whitelist of the whole network integration site, and it has the following functional modules: List display module: Displays all whitelists in a list. When the data exceeds the page display amount, it is paged. By default, 10 pieces of data are displayed per page and can be manually modified. You can click the paging dropdown to select the number of items displayed per page. When there are multiple pages, you can enter a number in the paging input box to jump to the corresponding page; In this embodiment, the platform queries the whitelist data from the NOTCIE_INFO table and displays it in a list form on the page. When the data volume exceeds 10 records, which is the default display number on the page, the system automatically performs paging processing. Users can click on the paging dropdown menu to select the number of records to be displayed per page, or enter a specific number in the paging input box and then click the jump button. The system will reload the data according to the page number or the number of records entered by the user and display the whitelist information of the corresponding page.

[0030] Filter function module: A filter box is provided, and whitelist records can be filtered out and displayed in a list through time filtering and fuzzy query in the search box; in this embodiment, in the filter box on the page, users can select time filtering conditions, such as entering the start time and end time. The system will query the whitelist records in the NOTCIE_INFO table whose creation time is within this time period in the background and display them in the list. At the same time, users can also enter keywords (such as partial numbers of a person's name, mobile phone number, etc.) in the search box for fuzzy query. The system performs fuzzy matching on relevant fields in the NOTCIE_INFO table, filters out the whitelist records that meet the conditions, and updates the content displayed in the list.

[0031] List push operation module, select the required site for list push, and the push records will display all push records of this whitelist; in this embodiment, after the user clicks the list push button, a site selection dropdown menu or list will pop up on the page, showing the information of the public network base stations of the whole network that can be pushed. After the user selects the required site, click the OK button. The system will call the whitelist push interface, use the selected site ID (SiteId) and the current whitelist list information as parameters, and send them to the relevant system through the external interface - the whole network whitelist interface. At the same time, the system inserts a data record in the PUSH_NOTICE table, including information such as push time, push site, and pusher, for recording the push history. The push records will be displayed in a specific area on the page, and users can view all push records of this whitelist at any time to understand information such as the push time and results.

[0032] Whitelist Editing Operation Module: It can perform editing operations on the whitelist data of this item, including deleting personnel information, exporting the list to the local in Excel format, downloading a template to input personnel and then importing the list. In this embodiment, after the user clicks the edit button of a certain whitelist in the list, the edit page will be entered. On the edit page, the user can delete unnecessary personnel information. By clicking the delete button, the corresponding deletion operation is triggered. The system will call the PutMapping interface under / biz / NoticeInfo to update the data in the NOTCIE_INFO table according to the user's operation. The user can also click the export button to export the list to an Excel format file to the local for convenient data backup or use in other systems. In addition, if the user needs to add personnel information, they can click the download template button to download a pre-designed Excel template file containing personnel information fields. After filling in the personnel information in the template according to the format requirements and clicking the import button, the system will call the PostMapping interface under / biz / NoticeInfo to parse the data in the Excel file and add it to the NOTCIE_INFO table to achieve batch import of personnel information.

[0033] Whitelist Deletion Operation Module: It can delete the whitelist data of this item and all related content data. In this embodiment, after the user selects the whitelist record to be deleted and clicks the delete button, the system will first pop up a confirmation deletion dialog box to prompt the user about the irreversibility of the deletion operation. After the user confirms, the system calls the / biz / NoticeInfo / {ids} interface to delete the corresponding record and all its related associated data from the NOTCIE_INFO table according to the unique identifier of the whitelist (such as the ID field), including the push records in the PUSH_NOTICE table, etc., to ensure data consistency and integrity.

[0034] As an implementation method, in this embodiment, the whitelist information data comes from the NOTICE_INFO table, where: The PostMapping interface under / biz / NoticeInfo is called to add new whitelist data; The PutMapping interface under / biz / NoticeInfo is called for whitelist editing; The / biz / NoticeInfo / {ids} interface is called for whitelist deletion; When selecting a site for whitelist push, the push whitelist interface is called. The push information is called through an external interface - the full-site whitelist interface. The input parameters are SiteId and the whitelist list, and data records of the push information are inserted into the PUSH_NOTICE table. The push list is displayed by querying the NOTICE_INFO table through the / biz / NoticeInfo / list interface.

[0035] As an implementation, in this embodiment, the NOTCIE_INFO table is associated with the Push_notice table through set fields. The Push_notice table records push-related information of one or more of the push site, time, pusher, and result; the NOTCIE_INFO is the main table; the Push_notice table is associated with the notice_info table through the notice_id field and the id field of the notice_info table.

[0036] In the list push operation, the whole-site whitelist interface is called to achieve effective control and update of the whitelist data across the network, ensuring the synchronization and accurate application of the data between different systems.

[0037] Such as Figure 2 As shown, in this embodiment, the NOTCIE_INFO table serves as the main table for whitelist information and stores the core data of the whitelist. Its primary key ID field uniquely identifies each whitelist record, the name field stores the name of the whitelist, the Explain_note field is used to record the detailed description information of the whitelist, the Notice_type field distinguishes the whitelist type (such as 1 represents a normal whitelist, and other values can be used for the definition of special type whitelists), the CREATE_BY field records the user account that created the whitelist, the CREATE_TIME field records the creation time, the UPDATE_BY field records the user account that last modified the whitelist, and the UPDATE_TIME field records the last modification time. The Push_notice table establishes an association relationship through the notice_id field and the id field of the notice_info table. When the list push operation is performed, the system inserts a record in the Push_notice table to record the relevant information of the push. For example, the push site information is stored in the corresponding field, the push time is automatically obtained by the system as the current time and stored, the pusher information is obtained from the user login information and stored, and the push result is updated according to the information returned by the base station after the push is completed and stored in this table. Through this association relationship, the system can conveniently query and manage the push history of the whitelist, realizing data traceability and analysis. Embodiment Two

[0038] This embodiment provides a satellite communication-based all-network public network base station whitelist management system. Embodiment Two focuses on the satellite communication-based all-network public network base station whitelist management system and elaborates on the functions and implementation methods of each module of the system. This system is used to implement the above-mentioned method, and the system at least includes: User Interaction Module: It is used for users to perform secondary authentication to log in to the platform. After successful login, it supports users to input or upload white list information containing mobile phone numbers and receive operation instructions from users for adding, deleting, modifying, and querying the white list. And after the platform displays the successful information of the entry of the all-net public network base station, it provides an interactive interface for users to perform relevant operations based on the effective white list. Number Conversion Module: It is connected to the user interaction module, receives the mobile phone numbers submitted by users, sends requests to the operator interface to convert the mobile phone numbers into International Mobile Subscriber Identity (IMSI), and receives the IMSI data returned by the operator interface. Data Push Module: It is connected to the number conversion module, obtains the IMSI data obtained by the number conversion module, and pushes the IMSI to the all-net public network base station according to the time requirement. At the same time, it receives the successful entry information returned by the all-net public network base station and transmits this information to the user interaction module for display. Intelligent Judgment and Security Protection Module: It is connected to the data push module and starts timing when the data push module pushes the IMSI data to the base station side. If the base station side normally receives the pushed IMSI data and returns the data reception success within the specified time, the IMSI data on the platform side will be automatically invalidated. If the base station side does not normally return the data reception information within the specified time, the interface verification will be started. After the verification passes, the data push module will be notified to start a new push until it is successfully pushed to the base station side and the IMSI data is automatically invalidated. This module ensures that the platform does not store IMSI throughout the process and only realizes the transfer of IMSI through interface reading and pushing. White List Management Page Module: It has a list display module, a filtering function module, a list push operation module, a list editing operation module, and a list deletion operation module. The list display module is used to display all white lists in a list. When the data exceeds the page display amount, it is paged. By default, 10 pieces of data are displayed per page and manual modification is supported. The number of data displayed per page can be selected by clicking the paging dropdown. When there are multiple pages, the corresponding page can be jumped to by entering a number in the paging input box. The filtering function module provides a filtering box, supporting filtering out white list records through time filtering and fuzzy query in the search box and displaying them in the list. The list push operation module supports selecting the required sites for list push and records the push information. The push record will display all push records of this white list. The list editing operation module can perform editing operations on the data of this white list, including deleting personnel information, exporting the list to Excel format to the local, downloading a template, inputting personnel, and then importing the list. The list deletion operation module can delete the data of this white list and all related content data. Data storage and management module: It includes the NOTICE_INFO table and the Push_notice table. The NOTICE_INFO table is the main table, storing the core information of the whitelist. The Push_notice table is associated with the id field of the NOTICE_INFO table through the notice_id field, and is used to record the push-related information of one or more of the push site, time, pusher, and result. The data of the whitelist management page module comes from the NOTICE_INFO table. When adding new whitelist data, it is added to the NOTICE_INFO table by calling the PostMapping interface under / biz / NoticeInfo. When editing the list, the PutMapping interface under / biz / NoticeInfo is called to modify the data in the NOTICE_INFO table. When deleting the list, the / biz / NoticeInfo / {ids} interface is called to delete the data from the NOTICE_INFO table. When performing the list push operation, the push whitelist interface is called during the push, and the push information is called through the external interface - the full-site whitelist interface. The input parameter information is the SiteId and the whitelist list, and data records of the push information are inserted into the Push_notice table. The push list is displayed by querying the NOTICE_INFO table through the / biz / NoticeInfo / list interface. Communication interface module: Responsible for the communication between the platform and the operator interface, using the POST method in the HTTP method for data transmission. The request parameters include an array of mobile phone numbers, and the received return value is data in JSON format, which includes the result indicating success or failure, status code, error information, and an array of IMSI data. As an implementation, the list display module of the whitelist management page module in this embodiment reads the whitelist data from the NOTICE_INFO table and displays it in reverse order according to the list creation time. When the data volume exceeds 10 items displayed by default on the page, the system automatically performs paging processing. The paging component has a quick jump function. After the user enters the page number in the paging input box and clicks the "Jump" button, the system can complete the data loading and display the data of the corresponding page. When the user clicks the paging drop-down menu to select the number of items displayed per page, the system immediately updates the list display data, and during the process of switching pages or the number of displayed items, the table header of the list is always fixed and displayed. The time filtering of the filtering function module of the whitelist management page module supports filtering by day, week, month, and custom time period. When filtering by custom time period, the user can accurately select the start time and end time through the calendar control. The system queries on the CREATE_TIME field of the NOTICE_INFO table in the background according to the time range selected by the user, and quickly filters out the whitelist records that meet the conditions; the fuzzy query function of the search box supports comprehensive fuzzy matching of multiple fields such as list name, list description, and creator. When the user enters a keyword, the system starts searching and displays the matched whitelist records in the list in real time. The search results will be dynamically updated according to the changes in the user input content. As an implementation manner, in this embodiment, after the user clicks the list push button in the list push operation module of the whitelist management page module, the pop-up site selection interface displays the information of the all-net public network base station sites in a tree structure, including site classifications in different regions and different operators; after selecting a site, the system automatically obtains the current logged-in user information as the pusher information, and uses the SiteId, whitelist list, and pusher information as parameters to call the push whitelist interface and the external interface - the all-site whitelist interface for data push; during the push process, the system displays the push progress bar in real time. After the push is completed, according to the result returned by the base station, the push time, push site, push result, and failure reason are detailedly recorded in the push record. The push records can be sorted and viewed according to the push time. When deleting personnel information in the list editing operation module of the whitelist management page module, after the user clicks the delete button, the system pops up a confirmation delete dialog box, prompting the user that the delete operation cannot be restored and displaying the details of the personnel information to be deleted; after the user confirms, the system calls the PutMapping interface under / biz / NoticeInfo, and deletes the corresponding record from the table according to the unique identifier of the personnel information in the NOTICE_INFO table, and synchronously updates the relevant associated data; when exporting the list as an Excel format file, the system fills in the data according to the preset Excel template. The template contains fields such as list name, list description, mobile phone number, and creation time, and the exported file name is named in the format of "whitelist_export time.xlsx"; the Excel template file provided by the download template function clearly marks the filling requirements and examples of each field in the table header. After the user fills in the personnel information according to the requirements and clicks the import button, the system calls the PostMapping interface under / biz / NoticeInfo to parse and verify the data of the imported Excel file. If the data format is correct and meets the business rules, the data will be added to the NOTICE_INFO table. After the import is successful, the system gives a success prompt and instantaneously updates and displays the newly added personnel information in the list.

[0039] As an implementation method, in this embodiment, after the list deletion operation module of the whitelist management page module has the user select the whitelist record to be deleted and click the delete button, the system first performs permission verification. Only users with administrator privileges or specific authorizations can perform the deletion operation. After the verification passes, the system pops up a secondary confirmation dialog box, prompting the user that the deletion operation will simultaneously delete the whitelist and all its related push records and associated data, and it cannot be restored. After the user confirms again, the system calls the / biz / NoticeInfo / {ids} interface. According to the primary key ID of the whitelist in the NOTICE_INFO table, the corresponding record is deleted from the NOTICE_INFO table, and all push records related to the whitelist in the Push_notice table are cascaded and deleted. After the deletion operation is completed, the system automatically refreshes the list page to display the whitelist data after deletion; The length limit of the name field in the NOTICE_INFO table of the data storage and management module is 100 characters. The Explain_note field is stored in rich text format. The Notice_type field reserves extended values in addition to distinguishing between whitelists and blacklists. The CREATE_BY field is associated with the system user table and stores the user ID of the creator. The CREATE_TIME field uses a timestamp accurate to the second to record the creation time. The UPDATE_BY field is associated with the system user table and records the user ID of the last modifier. The UPDATE_TIME field is automatically updated to the current timestamp each time the whitelist information is modified; The notice_id field in the Push_notice table of the data storage and management module establishes a foreign key constraint with the id field of the NOTICE_INFO table; the push site information is stored in the site_id field and uses a coding format corresponding to the unique identifier of the whole-network communication public network base station site; the push time field records the exact time when the push operation occurs, accurate to the millisecond; the pusher information is stored in the operator_id field and is associated with the user ID of the system user table; the push result field is represented by an enumeration value, including statuses such as "success", "failure", and "partial success". If the push result is "failure" or "partial success", the failure reason or the specific situation of partial success is detailedly recorded in the remark field.

[0040] In this embodiment, the secondary authentication and login mechanism of the user interaction module, combined with the account locking and unlocking notification functions, ensures the security of the user account while providing clear operation feedback to the user. The optimization of the functions of each module on the whitelist management page, such as the sorting, paging, and fixed table header of the list display module, the diversified filtering and real-time search of the filtering function module, the visual progress bar and detailed records of the list push operation module, the import / export function and template guidance of the list editing operation module, and the permission verification and secondary confirmation of the list deletion operation module, have greatly improved the operation convenience and intuitiveness of the user for whitelist management, making the complex whitelist management work efficient, smooth, and meeting the actual usage needs of the user.

[0041] The intelligent judgment and security protection module ensures the secure transmission of IMSI data through precise time setting and strict interface verification mechanisms, effectively preventing the risks of data leakage and loss, and providing strong guarantee for the security of the system. The optimization of the structures of the NOTICE_INFO table and the Push_notice table by the data storage and management module, as well as measures such as data encryption, backup, archiving, and permission control, further improve the security, integrity, and stability of data storage, ensuring the reliable management of data during the long-term operation of the system. The log recording and transmission strategy adjustment functions of the communication interface module can timely discover and solve problems in the communication process, ensuring the stability and reliability of data transmission.

[0042] The clear time requirements and warning mechanism of the data push module can ensure the timely and accurate push of IMSI data to the base station, improving the system response speed. The various optimized functions of the whitelist management page module, such as fast data loading and display, efficient filtering and editing operations, and the regular archiving and cleaning mechanism of the data storage and management module, all contribute to improving the overall operation efficiency of the system and reducing resource occupancy. At the same time, the detailed operation records and classified storage of the log recording module facilitate the administrator to conduct system monitoring, fault troubleshooting, and performance analysis, improving the management efficiency of the system.

[0043] The precise time filtering and comprehensive fuzzy query of the filtering function module, as well as the data format verification and import verification mechanisms of the list editing operation module, ensure the accuracy of the whitelist data obtained and modified by the user. The foreign key constraint, transaction processing mechanism, and data consistency check of the data storage and management module ensure the consistency and integrity of the data between the NOTICE_INFO table and the Push_notice table, avoiding data conflicts and errors, and providing a solid data foundation for the stable operation of the system.

[0044] Although the embodiments of the present invention have been shown and described above, it is to 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 whitelist management method for all-network public network base stations based on satellite communication, characterized in that: The following steps are involved: Step S1: The user performs secondary authentication to log in to the platform, and enters or uploads whitelist information containing the mobile phone number after successful login; Step S2: After receiving the mobile phone number submitted by the user, the platform interfaces the mobile phone number with the operator and requests to convert the mobile phone number into an international mobile subscriber identity code (IMSI); after the operator interface processes the number, the corresponding international mobile subscriber identity code (IMSI) is returned to the platform; Step S3, the platform pushes the acquired International Mobile Subscriber Identity IMSI to the all-network public network base station according to the time requirement; the all-network public network base station returns the entry success information to the platform after processing the IMSI, and the platform displays the push success; the all-network public network base station entry success is displayed on the interface, letting the user know that the whitelist has been successfully effective at the base station; Step S4: The platform is equipped with an intelligent judgment mechanism to ensure accurate push and security protection of the International Mobile Subscriber Identity (IMSI). The platform does not store IMIS during the entire process, and it is pushed directly to the base station after reading through the interface. After the push, there is no more IMSI information in the system. In step S4, the platform is set up with an intelligent judgment mechanism after data push Step S41 sets a time limit, which starts from the moment the platform pushes the IMSI data to the base station side; Step S42: If the base station receives the pushed IMSI data normally within the specified time and then returns the successful data reception, the IMSI data on the platform will automatically become invalid to ensure data security; Step S43: If the base station does not return the data reception information normally within the specified time, the platform starts the interface verification. After the verification passes, a new push is started until it is successfully pushed to the base station, and the IMSI data is automatically invalidated. Step S5: The user can add, delete, modify, and check the effective whitelist as needed to achieve dynamic management of the whitelist.

2. The whitelist management method according to claim 1, characterized in that: The communication between the platform and the operator interface adopts the POST method in the HTTP method. The request parameters include an array of mobile phone numbers. The return value format is a JSON object, which includes a result indicating success or failure, a status code, an error message, and an array of IMSI data.

3. The whitelist management method according to claim 1, characterized in that: The platform is equipped with a whitelist management page to manage the whitelist of all network-wide integrated sites, which has the following functional modules: List display module: Display all whitelists in the list. When the data exceeds the page display capacity, it will be displayed in pages. The default is 10 data items per page and can be modified manually. You can select the number of items to display per page by clicking the paging drop-down. When there are multiple pages, you can enter a number in the paging input box to jump to the corresponding page. Filter function module: provides a filter box, which can filter out whitelist records through time filtering and fuzzy query in the search box and display them in the list; In the list push operation module, select the desired site to push the list, and the push record will display all push records of this whitelist; List editing operation module: can edit the whitelist data, including deleting personnel information, exporting the list to the local in Excel format, downloading the template, inputting personnel, and then importing the list; The list deletion operation module can delete the whitelist data and all related content data.

4. The whitelist management method according to claim 3, characterized in that: The whitelist information data is derived from the NOTICE_INFO table, where: Added the PostMapping interface under / biz / NoticeInfo for new whitelist data calls; The list editor calls the PutMapping interface under / biz / NoticeInfo; To delete the list, call the / biz / NoticeInfo / {ids} interface; The list push selects the site to call the push whitelist interface, and calls the external interface - the full website whitelist interface to push information. The input information is SiteId and the whitelist list, and the data record push information is inserted into the PUSH_NOTICE table. The push list is displayed by calling the / biz / NoticeInfo / list interface to query the NOTICE_INFO table.

5. The whitelist management method for all-network public base stations based on satellite communication according to claim 1, characterized in that: The NOTCIE_INFO table is associated with the Push_notice table through the set fields. The Push_notice table records one or more push-related information including the push site, time, pusher, and result. In the list push operation, the website-wide whitelist interface is called to achieve effective control and update of whitelist data across the entire network, ensuring synchronization and accurate application of data between different systems. NOTCIE_INFO is the main table; the Push_notice table is associated with the id field of the notice_info table through the notice_id field.

6. A satellite communication-based all-network public network base station whitelist management system, characterized by: The system is used to implement the method described in any one of claims 1 to 5 above, and the system at least includes: User interaction module: used for users to log in to the platform for secondary authentication. After successful login, users are supported to enter or upload whitelist information containing mobile phone numbers, and receive user instructions for adding, deleting, modifying and checking the whitelist. After the platform displays the successful entry information of the public network base station of the full network, an interactive interface is provided for users to perform related operations based on the effective whitelist. Number conversion module: connected with the user interaction module, receives the mobile phone number submitted by the user, sends a request to the operator interface to convert the mobile phone number into the International Mobile Subscriber Identity IMSI, and receives the IMSI data returned by the operator interface; Data push module: connects with the number conversion module, obtains the IMSI data obtained by the number conversion module, and pushes the IMSI to the all-network public network base station according to the time requirement; at the same time, receives the entry success information returned by the all-network public network base station, and transmits the information to the user interaction module for display; Intelligent judgment and security protection module: connected to the data push module, the timing starts when the data push module pushes the IMSI data to the base station side; if the base station side receives the pushed IMSI data normally within the specified time and returns the successful data reception, the IMSI data on the platform side will be automatically invalidated; if the base station side does not return the data reception information normally within the specified time, the interface verification will be started, and after the verification is passed, the data push module will be notified to start a new push until it is successfully pushed to the base station side, and the IMSI data will be automatically invalidated; this module ensures that the platform does not store IMSI throughout the entire process, and the IMSI is only transmitted through interface reading and pushing; Whitelist management page module: It has a list display module, a filtering function module, a list push operation module, a list editing operation module and a list deletion operation module. The list display module is used to display all whitelists in the list. When the data exceeds the page display capacity, it will be displayed in pages. The default is 10 data items per page and supports manual modification. You can select the number of items to display per page by clicking the paging drop-down. When there are multiple pages, you can enter a number in the paging input box to jump to the corresponding page; the filtering function module provides a filtering box, supports filtering out whitelist records through time filtering and fuzzy query in the search box and displaying them in the list; the list push operation module supports selecting the required site for list push, and records the push information. The push record will display all push records for this whitelist; the list editing operation module can edit the whitelist data, including deleting personnel information, exporting the list to Excel format to the local computer, downloading the template to enter the personnel and then importing the list; the list deletion operation module can delete the whitelist data and all related content data; Data storage and management module: including NOTICE_INFO table and Push_notice table. NOTICE_INFO table is the main table, which stores the core information of the whitelist. Push_notice table is associated with the id field of NOTICE_INFO table through the notice_id field, which is used to record one or more push-related information such as push site, time, pusher and result. The data of the whitelist management page module comes from the NOTICE_INFO table. The newly added whitelist data calls the PostMapping interface under / biz / NoticeInfo to be added to the NOTICE_INFO table. The editor calls the PutMapping interface under / biz / NoticeInfo to modify the data in the NOTICE_INFO table. The list deletion calls the / biz / NoticeInfo / {ids} interface to delete data from the NOTICE_INFO table. The list push operation module calls the push whitelist interface when pushing, and calls the external interface-the full website whitelist interface for the push information. The input parameter information is SiteId and the whitelist list, and inserts data to record the push information in the Push_notice table. The push list is displayed by querying the NOTICE_INFO table by calling the / biz / NoticeInfo / list interface. Communication interface module: responsible for the communication between the platform and the operator interface, using the POST method in the HTTP method for data transmission. The request parameters include an array of mobile phone numbers. The received return value is data in JSON format, which includes results indicating success or failure, status code, error information, and IMSI data array.

7. The satellite communication-based all-network public network base station whitelist management system according to claim 6, characterized in that: The list display module of the whitelist management page module reads the whitelist data from the NOTICE_INFO table and displays them in reverse order of the list creation time; when the amount of data exceeds the default 10 displayed on the page, the system automatically performs paging processing, and the paging component has a fast jump function. After the user enters the page number in the paging input box and clicks the "jump" button, the system can complete the data loading and display the corresponding page data; when the user clicks the paging drop-down menu to select the number of items to be displayed per page, the system immediately updates the list display data, and in the process of switching pages or displaying the number of items, the list header is always fixedly displayed; The time filtering of the filtering function module of the whitelist management page module supports filtering by day, week, month, and custom time period. When filtering by custom time period, the user can accurately select the start time and end time through the calendar control. The system queries the CREATE_TIME field of the NOTICE_INFO table in the background according to the time range selected by the user, and quickly filters out the whitelist records that meet the conditions; the fuzzy query function of the search box supports comprehensive fuzzy matching of multiple fields such as list name, list description, creator, etc. When the user enters a keyword, the system starts searching and displays the matched whitelist records in the list in real time. The search results will be dynamically updated according to changes in the user input content.

8. The satellite communication-based all-network public network base station whitelist management system according to claim 7, characterized in that: After the user clicks the list push button, the list push operation module of the whitelist management page module pops up a site selection interface to display the site information of the full network public network base station in a tree structure, including the site classification of different regions and different operators; after selecting the site, the system automatically obtains the current logged-in user information as the pusher information, and uses SiteId, whitelist list and pusher information as parameters to call the push whitelist interface and the external interface-full website whitelist interface to push data; During the push process, the system displays the push progress bar in real time. After the push is completed, the system records the push time, push site, push result and failure reason in detail according to the result returned by the base station. The push record can be sorted and viewed according to the push time. When deleting personnel information in the list editing operation module of the whitelist management page module, after the user clicks the delete button, the system pops up a confirmation deletion dialog box, prompting the user that the deletion operation is irreversible, and displays the details of the personnel information to be deleted; after the user confirms, the system calls the PutMapping interface under / biz / NoticeInfo, deletes the corresponding record from the NOTICE_INFO table according to the unique identifier of the personnel information in the NOTICE_INFO table, and synchronously updates the relevant associated data; when exporting the list as an Excel format file, the system fills in the data according to the preset Excel template, the template includes the name of the list, the list description, the mobile phone number, the creation time and other fields, and the exported file name is named in the "whitelist_export time.xlsx" format; the Excel template file provided by the download template function clearly marks the filling requirements and examples of each field in the table header. After the user fills in the personnel information as required, clicks the import button, the system calls the PostMapping interface under / biz / NoticeInfo, parses and verifies the imported Excel file, and if the data format is correct and complies with the business rules, the data is added to the NOTICE_INFO table. After the import is successful, the system gives a success prompt and instantly updates the newly added personnel information in the list.

9. The satellite communication-based all-network public network base station whitelist management system according to claim 8, characterized in that: In the list deletion operation module of the whitelist management page module, after the user selects the whitelist record to be deleted and clicks the delete button, the system first performs permission verification. Only users with administrator privileges or specific authorization can perform the deletion operation; after the verification is passed, the system pops up a secondary confirmation dialog box to prompt the user that the deletion operation will delete the whitelist and all related push records and associated data at the same time, and cannot be restored; after the user confirms again, the system calls the / biz / NoticeInfo / {ids} interface, and deletes the corresponding record from the NOTICE_INFO table according to the primary key ID of the whitelist in the NOTICE_INFO table, and cascade deletes all push records related to the whitelist in the Push_notice table. After the deletion operation is completed, the system automatically refreshes the list page to display the deleted whitelist data; The name field in the NOTICE_INFO table of the data storage and management module is limited to 100 characters in length, the Explain_note field is stored in rich text format, the Notice_type field reserves extended values ​​in addition to distinguishing between whitelists and blacklists, the CREATE_BY field is associated with the system user table to store the creator's user ID, the CREATE_TIME field uses a timestamp accurate to seconds to record the creation time, the UPDATE_BY field is associated with the system user table to record the user ID of the last modifier, and the UPDATE_TIME field is automatically updated to the current timestamp each time the whitelist information is modified; The notice_id field in the Push_notice table of the data storage and management module establishes a foreign key constraint with the id field of the NOTICE_INFO table; the push site information is stored in the site_id field, using a coding format corresponding to the unique identifier of the all-network public network base station site; the push time field records the exact time when the push operation occurs, accurate to milliseconds; the pusher information is stored in the operator_id field, which is associated with the user ID of the system user table; the push result field is represented by an enumeration value, including "success", "failure", "partial success" and other states. If the push result is "failure" or "partial success", the reason for the failure or the specific circumstances of the partial success are recorded in detail in the remark field.

Images