Abnormal data positioning method and device, equipment and storage medium

Abstract

The application provides an abnormal data positioning method, device and equipment and a storage medium. In the scheme, based on the response of the user to the abnormal node click operation on the audit map, the next page of the abnormal node is displayed to the user. In the page, the user sends abnormal data alarm information to the management equipment of the abnormal area which needs to be checked based on the indication of the abnormal area. The abnormal data positioning method provided by the application clearly shows the position and quantity of abnormal data in the form of an audit map, so that the abnormal data can be found and modified in a short time, thereby realizing income guarantee.

Description

Technical Field

[0001] This application relates to the field of revenue protection in the telecommunications industry, and in particular to a method, apparatus, device, and storage medium for locating abnormal data. Background Technology

[0002] With the development of the telecommunications industry, operators have become increasingly adept at handling business and revenue processes with numerous steps involved, which can lead to revenue discrepancies. Therefore, pinpointing the source of these revenue discrepancies and identifying anomalies is crucial.

[0003] Existing technical solutions primarily rely on manual methods. Specifically, when revenue discrepancies arise, technical personnel from each department investigate each business module under their management until the source of the discrepancy is identified.

[0004] However, the above-mentioned method of manually locating the source of revenue discrepancies is difficult to identify truly abnormal data across multiple business segments in a short period of time, resulting in low efficiency. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for locating abnormal data, in order to solve the technical problem of low efficiency in identifying abnormal data in existing income protection technologies.

[0006] Firstly, this application provides a method for locating abnormal data, including:

[0007] In response to a user's click on an abnormal node in the audit map displayed on the page, the next level page of the abnormal node is displayed; the main page of the audit map includes nodes of multiple production units and the connection relationships between the nodes, and each production unit node stores business data and data specifications generated in various regions.

[0008] Based on the abnormal region indication in the next level page of the abnormal node, at least one abnormal region that needs to be viewed for abnormal business data is determined. The next level page of the abnormal node includes multiple regions and at least one abnormal region identifier.

[0009] Based on the at least one abnormal region, send an abnormal data alarm message to the management device of each abnormal region.

[0010] In one possible design of the first aspect, before displaying the next-level page of the abnormal node in response to a user's click on an abnormal node of the audit map displayed on the page, the method further includes:

[0011] Multiple business modules within the system are acquired as multiple production units;

[0012] Based on the multiple production units, the predecessor and successor relationships between business modules, the list of interfaces between business modules, the list of functional modules within each business module and the list of interfaces between functional modules, and the list of interfaces between each business module and the system, the audit map is generated. The audit map includes the main page and the next-level page of each production unit node.

[0013] In one possible design of the first aspect, the method further includes:

[0014] For each production unit, business data for each region under the production unit is retrieved from the data storage server according to a preset cycle, and the business data is updated to the data storage area of ​​the next-level page of the corresponding production unit node in the audit map.

[0015] Based on the business data stored in the data storage area and the preset data specifications, the business data of each region under the node of the production unit is checked to determine whether there is any abnormal business data;

[0016] For each region containing abnormal business data in the next-level page of the node of the production unit, an abnormal region identifier is set, which is used to indicate the number of abnormal business data in the current region.

[0017] In one possible design of the first aspect, the method further includes:

[0018] If any node in a production unit contains abnormal business data, the node of that production unit will be marked as abnormal on the main page of the audit map. The abnormality mark indicates that the node of the production unit is an abnormal node and the total amount of abnormal business data.

[0019] In one possible design of the first aspect, the method further includes:

[0020] For each abnormal region, obtain authorization information to view the abnormal data. The authorization information includes the login account and password for logging into the audit map system.

[0021] The authorization information is sent to the management equipment in the abnormal area.

[0022] In one possible design of the first aspect, the method further includes:

[0023] Accept login requests for the audit map system sent by management devices in any abnormal area, wherein the login request for the audit map system includes a login account and password;

[0024] Verify the login account and password;

[0025] If the verification is successful, all abnormal business data of the abnormal area in the audit map will be returned to the management device of the abnormal area.

[0026] In one possible design of the first aspect, the plurality of production units include multiple of the following business functions: rule center, resource center, public product center, clearing center, recharge center, number portability, permission center, public order center, public customer center, rights center, data exchange center, payment center, headquarters electronic invoice system, channel management center, Internet of Things, operation management system, activation center, delivery center, activity center, public accounting center, credit control center, notification center, partner relationship management, financial shared service center, supply chain shared service center, provincial comprehensive procurement, call detail record management center, public billing center, settlement accounting, revenue management center, enterprise resource planning core system, financial management application, virtual operation open platform, government and enterprise product center, government and enterprise order center, government and enterprise finance center, government and enterprise billing center, government and enterprise aggregation center, emerging information and communication technology system, government and enterprise customer center, government and enterprise marketing center, and government and enterprise strategy center.

[0027] Secondly, this application provides a device for locating abnormal data, comprising:

[0028] The response module is used to respond to the user's click operation on the abnormal node of the audit map displayed on the page and display the next level page of the abnormal node; the main page of the audit map includes nodes of multiple production units and the connection relationship between the nodes, and each production unit node stores business data and data specifications generated in various regions.

[0029] The processing module is used to determine at least one abnormal region that needs to be viewed for abnormal business data based on the abnormal region indication in the next level page of the abnormal node. The next level page of the abnormal node includes multiple regions and at least one abnormal region identifier.

[0030] The sending module is used to send abnormal data alarm messages to the management device of each abnormal region based on the at least one abnormal region.

[0031] Thirdly, this application provides an electronic device, including: a processor, and a memory communicatively connected to the processor;

[0032] The memory stores computer-executed instructions;

[0033] The processor executes computer execution instructions stored in the memory to implement the method for locating abnormal data as described in any of the first aspects.

[0034] Fourthly, this application provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method for locating abnormal data as described in any of the first aspects.

[0035] Fifthly, this application provides a computer program product, the computer program product comprising a computer program, which, when executed by a processor, is used to implement a method for locating abnormal data as described in any of the first aspects.

[0036] The method, apparatus, equipment, and storage medium for locating abnormal data provided in this application can be applied to the revenue protection field of the telecommunications industry. In this solution, accurate location of abnormal data primarily relies on an audit map. This audit map uses the revenue chain as its main thread and data flow as its guiding principle, and is practically applied in the revenue protection process to quickly pinpoint the root cause of abnormal data. The audit map responds to user clicks on abnormal nodes, displaying the next level page of the abnormal node in a visual format. Based on the identification of the abnormal data volume on this page, users can send abnormal data alarm messages to the management equipment in the abnormal area where abnormal data needs to be viewed, thereby achieving data auditing within and between systems. This allows abnormal data to be discovered and modified in a short time, reducing the occurrence of revenue loss problems. Attached Figure Description

[0037] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0038] Figure 1 A schematic diagram illustrating the application scenario of the abnormal data location method provided in this application;

[0039] Figure 2 A flowchart illustrating an embodiment of the method for locating abnormal data provided in this application;

[0040] Figure 3 A flowchart illustrating Embodiment 2 of the method for locating abnormal data provided in this application;

[0041] Figure 4 A template diagram outlining the business modules in the audit map provided in this application;

[0042] Figure 5 A flowchart illustrating Embodiment 3 of the method for locating abnormal data provided in this application;

[0043] Figure 6 A flowchart illustrating Embodiment 4 of the method for locating abnormal data provided in this application;

[0044] Figure 7A flowchart illustrating Embodiment 5 of the method for locating abnormal data provided in this application;

[0045] Figure 8 A flowchart illustrating Embodiment Six of the method for locating abnormal data provided in this application;

[0046] Figure 9 This application provides an internal production unit view of the audit map system.

[0047] Figure 10 This is a view of the internal functional modules of the audit map system provided in this application;

[0048] Figure 11 The internal functional matrix of the audit map system provided in this application;

[0049] Figure 12 The audit map system structure diagram provided in this application;

[0050] Figure 13 A schematic diagram of the structure of an embodiment of the abnormal data location device provided in this application;

[0051] Figure 14 A schematic diagram of the structure of Embodiment 2 of the abnormal data location device provided in this application;

[0052] Figure 15 A schematic diagram of the structure of the electronic device for locating abnormal data provided in this application.

[0053] The accompanying drawings illustrate specific embodiments of this application, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the concept in any way, but rather to illustrate the concept of this application to those skilled in the art through reference to particular embodiments. Detailed Implementation

[0054] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims.

[0055] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with relevant laws, regulations and standards, and corresponding operation entry points are provided for users to choose to authorize or refuse.

[0056] With the rapid development of the telecommunications industry, major operators have taken numerous measures to ensure their revenue and stable development. Among these measures, timely detection and correction of abnormal business data is one of the most fundamental revenue protection measures.

[0057] Existing technical solutions primarily rely on maintenance engineers and other technical personnel to promptly detect and correct abnormal service data. Specifically, during the actual operation of various operator systems, maintenance engineers and other technical personnel are responsible for detecting and correcting abnormal service data in a specific system. When maintenance engineers or other technical personnel discover abnormal service data, they systematically check all nodes within their assigned system until they pinpoint the location where the abnormal service data originated, and then correct it.

[0058] However, existing technical solutions for locating and modifying abnormal business data rely heavily on maintenance engineers and other technical personnel. Furthermore, with changes in operators' business and revenue models, revenue processes are becoming increasingly complex, with provincial-level personalized services mixed with nationwide common services. This makes it difficult to pinpoint the causes of abnormal business data. Maintenance engineers and other technical personnel, when investigating the location of abnormal business data one by one, cannot promptly identify the true abnormal business data, resulting in low efficiency and potentially widening revenue disparities.

[0059] To address the aforementioned issues, the inventors, during their research on the low efficiency of anomaly data location, discovered that within multiple business systems of telecom operators, the location and timing of data flow from its initial generation to final financial management are constantly changing. Furthermore, the data flow process is lengthy and involves numerous stages, making timely detection and identification of anomaly data across these business links difficult, easily leading to reduced efficiency in data discovery and correction. Therefore, the inventors considered whether the anomaly data location process could reduce reliance on maintenance engineers and other technical personnel, enabling 24 / 7 monitoring of nationwide business data and identification of anomalies. Specifically, before anomaly data location, the concept of an audit map is introduced to display anomaly data generated by each system and module, facilitating root cause analysis. This audit map primarily uses the revenue chain as its main thread, exploring the flow and changes of business data from its initial generation to final financial management throughout the entire revenue chain. Simultaneously, from both IT and business perspectives, the necessity of data auditing and corresponding audit logic are considered in terms of the completeness, consistency, accuracy, and standardization of business data, enabling data auditing within and between systems. Each system conducts a detailed and meticulous review of all its business points, modules, and applications, thereby establishing an audit map and covering audit indicators for application modules within and between systems. Based on the review results, gaps are identified and addressed, establishing a long-term effective audit mechanism. After the audit map is constructed, it combines business data standards to monitor real-time business data generated in various regions across the country, displaying abnormal business data as anomaly markers on the audit map. When the amount of abnormal data reaches a preset threshold, the administrators of the relevant business systems are notified to initiate the viewing and correction of abnormal data, thereby achieving rapid location of abnormal data and ensuring business revenue.

[0060] Figure 1 A schematic diagram illustrating an application scenario for the abnormal data location method provided in this application. For example... Figure 1 As shown, the application scenario of the solution provided in this application includes a server 100, a production unit management device 101, and a production unit management device 102. The server 100 is mainly used to deploy the audit map system 1001. The server 100 is connected to the production unit management device 101 and the production unit management device 102 via wireless connection.

[0061] Based on the audit map system 1001, relevant operations and maintenance personnel can view the actual situation of abnormal data generation in each production unit on its provided visual interface. If the amount of abnormal data generated in a production unit reaches a preset threshold, the relevant operations and maintenance personnel will send abnormal data alarm information to the corresponding production unit management device 101 and production unit management device 102. Upon receiving the alarm information, production unit management devices 101 and 102, based on their authorized login permissions, log in to the audit map system 1001 to view the location and quantity of abnormal data generation, and send abnormal data viewing information to the technical personnel in the corresponding regions according to the actual amount of abnormal data generation, thereby assisting operations and maintenance personnel in each region to quickly locate the location of abnormal data generation and reduce the loss of business revenue. Although Figure 1 Only one server 100 is shown, but it should be understood that two or more servers 100 may exist. Meanwhile, although... Figure 1 Only two production unit management devices, production unit management device 101 and production unit management device 102, are shown in the diagram, but it should be understood that there may be three or more production unit management devices.

[0062] The technical solution of this application and how the technical solution of this application solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of this application will now be described with reference to the accompanying drawings.

[0063] Figure 2 A flowchart illustrating an embodiment of the method for locating abnormal data provided in this application. Figure 2 As shown, the process of locating this abnormal data may include:

[0064] S201: In response to the user's click on the abnormal node of the audit map displayed on the page, the next level page of the abnormal node is displayed; the main page of the audit map includes nodes of multiple production units and the connection relationships between nodes. Each production unit node stores business data and data specifications generated in various regions.

[0065] In this step, after logging into the audit map system, the user can access the visual interface provided by the system. This interface displays numerous production unit modules that identify abnormal nodes. When the user clicks on one of these modules, the audit map system immediately responds by displaying the next level page for that abnormal node.

[0066] The main page of the audit map includes nodes for multiple production units and the connections between them. Each production unit node stores business data and data specifications generated in various regions.

[0067] Specifically, the nodes of a production unit represent specific business systems. For example, if all the business systems used within Company A are a, b, and c, then the audit map main page will display three production unit nodes, representing business systems a, b, and c respectively. The relationships between business systems a, b, and c are as follows: business system a connects to business system b, business system a connects to business system c, and there is no connection between business system b and business system c. Therefore, the connection relationships between these three production unit nodes will also be displayed on the audit map system main page.

[0068] Different business systems have their own data standards for internal business data. These standards include naming conventions, data formats, storage methods, and security. Furthermore, even within the same business system, different regions may have their own data standards for the transmitted business data. Therefore, in this audit map system, each production unit node stores the data standards for each region.

[0069] Because business systems operate in real-time in real-world scenarios, business data is generated continuously. To ensure the accuracy of this business data through auditing, it is essential to store this data in the storage area under the corresponding production unit node.

[0070] S202: Based on the abnormal region indication in the next level page of the abnormal node, determine at least one abnormal region that needs to be viewed for abnormal business data. The next level page of the abnormal node includes multiple regions and at least one abnormal region identifier.

[0071] In this step, based on step S201, the audit map system responds to the user's click operation on the abnormal node of the audit map displayed on the page. After displaying the next level page of the abnormal node, the user needs to determine at least one abnormal area that needs to be viewed for abnormal business data according to the abnormal area indication in the next level page of the abnormal node.

[0072] The next level page of the abnormal node includes multiple regions and at least one abnormal region identifier.

[0073] Specifically, the audit map system aggregates the business systems used by telecom operators across the country. Each business system contains multiple business function modules. Within each module, business data from various regions across the country flows. Using the data specifications of that function module as the standard, the system compares the real-time generated business data against the relevant criteria in the data specifications. If any business data is found to be inconsistent with the data specifications, the audit map system marks the corresponding abnormal data point and automatically indicates the number of abnormal data points in the corresponding function module node.

[0074] The number of abnormal data points will gradually increase as business data is generated in real time. When the number of abnormal data points reaches a certain threshold, corresponding inspection operations are required. In one specific implementation, the audit map system divides the corresponding regional production units into three states: low, medium, and high, based on the number of abnormal data points. The low state corresponds to 0 to 99 abnormal data points, the medium state to 100 to 1000, and the high state to more than 1000. However, this value can be adjusted according to actual circumstances.

[0075] Users are typically internal operations and maintenance (O&M) personnel within an enterprise. When they discover a production unit node with a high anomaly flag in the audit map system, they identify at least one abnormal region requiring an investigation into business data anomalies based on this flag. For example, in the production unit node corresponding to the call detail record (CDR) management system, the number of anomaly flags is 3000, and the status is high. If the O&M personnel open the production unit node for this CDR management system and find that the number of anomaly flags for region A and region B are 1002 and 1134 respectively, both exceeding the preset number of anomaly flags, then region A and region B will be identified as abnormal regions requiring an investigation into business data anomalies by the O&M management personnel.

[0076] S203: Based on at least one abnormal region, send an abnormal data alarm message to the management device of each abnormal region.

[0077] In this step, based on step S202, after determining at least one abnormal region that needs to be viewed for abnormal business data according to the abnormal region indication in the next level page of the abnormal node, the audit map system needs to send abnormal data alarm information to the management device of each abnormal region.

[0078] The management equipment for abnormal regions is based on a specific area, such as Hebei, Shandong, or Liaoning. This equipment is managed by specialized technical personnel and is used to resolve abnormal data issues in specific regions.

[0079] For example, based on step S202, after regions A and B are identified by operations and maintenance personnel as abnormal regions requiring anomaly monitoring of business data, the audit map system sends abnormal data alarm information to the management devices in regions A and B. Upon receiving this information, the technical personnel managing the abnormal data log into the regional audit map system to view the corresponding abnormal data and take appropriate measures.

[0080] This embodiment provides a method for locating abnormal data, primarily illustrating how to locate abnormal data based on an audit map system. The audit map identifies the volume of abnormal data. Users can determine the abnormal area requiring anomaly monitoring on the visual interface provided by the audit map system and send anomaly alarm messages to the corresponding management devices. This method allows for the timely detection of the location of abnormal data and the implementation of appropriate measures to promptly eliminate revenue issues caused by the abnormal data, thereby reducing internal business revenue loss for the enterprise.

[0081] Figure 3 A flowchart illustrating Embodiment Two of the method for locating abnormal data provided in this application. Figure 3 As shown, based on the above embodiments, in response to a user's click on an abnormal node in the audit map displayed on the page, before displaying the next-level page of the abnormal node, the process of locating the abnormal data further includes:

[0082] S301: Obtain multiple business modules within the system as multiple production units.

[0083] In this step, before locating abnormal data based on the audit map system, the user needs to obtain the audit map system first. Specifically, when creating the audit map, the system needs to first acquire multiple internal business modules as multiple production units.

[0084] The system's multiple business modules can cover all business data exchanges within an enterprise. For example, if an enterprise uses only three business modules (1, 2, and 3), then when creating the corresponding audit map system for that enterprise, these three business modules need to be retrieved as production unit nodes on the system's main interface.

[0085] S302: Based on multiple production units, the predecessor and successor relationships between business modules, the list of interfaces between business modules, the list of functional modules within each business module and the list of interfaces between functional modules, and the list of interfaces between each business module and the system, generate an audit map. The audit map includes the main page and the next-level page of each production unit's node.

[0086] In this step, after obtaining multiple business modules within the system as multiple production units based on step S301, considering that there are many functional modules within each production unit, it is necessary to generate an audit map based on the multiple production units, the predecessor and successor relationships between business modules, the interface list between business modules, the functional modules within each business module and the interface list between functional modules, and the interface list between each business module and the system.

[0087] Each production unit contains multiple business modules. For example, the billing management system, which serves as a production unit, contains business modules such as accounting management, rate management, billing engine, settlement management, and data acquisition.

[0088] Based on the multiple business modules provided by the billing management system, there are certain predecessor and successor relationships among these modules. For example, the data collection module is the first, the rate management module is the second, the billing engine module is the third, the settlement management module is the fourth, and the accounting management module is the fifth, and so on.

[0089] Multiple business modules communicate with each other based on a predecessor-successor relationship. The communication method used is the interface between business modules. Therefore, when drawing an audit map, a list of interfaces between business modules is essential, as it helps to clarify the source and destination of business data flowing between systems. For example, there is business data exchange between the billing engine module and the settlement management module. This data exchange is carried out through the interface between these two modules. The predecessor-successor relationship is that after the billing engine module completes its calculation, it transmits the calculated data to the settlement management module.

[0090] Each business module also contains a different number of functional modules, and there is a certain business data flow between these functional modules. Therefore, it is also necessary to obtain the list of functional modules within each business module and the interface list between the functional modules. For example, the interface relationship between functional modules a, b, and c within business module A is that a connects to b, and b connects to c.

[0091] During the actual operation of the system, there is also a data flow process between each business module and the system. Therefore, it is necessary to sort out the input data sources (such as tables, files, messages, etc.) of each application module and the interface between the system, down to the field level read by the program, as well as the output or change result set (such as tables, files, messages, etc.) of each application module and the interface between the system, down to the field level of the program output or operation, so as to realize the connection between the input and output data sources and achieve the whole process of data flow.

[0092] In one possible implementation, Figure 4 This is a template diagram outlining the business modules in the audit map provided in this application. For example... Figure 4 As shown, when each business system sorts out relevant information such as internal modules and interfaces, it can use this sorting template to do so. Specifically, under the premise of completeness and consistency of audit indicators, it records relevant content such as module name, file / table name, data source type, whether it is audited, rendezvous point support system, and audit logic, thereby completing the sorting out of each business system.

[0093] The method for locating abnormal data provided in this embodiment mainly illustrates the basic content required for drawing an audit map system. The audit map system primarily displays the actual flow of business data between systems. Therefore, each business system needs to conduct a detailed review of all business points, modules, and applications involved. The purpose is to enable each business system to establish an audit map and cover audit indicators between and within systems by reviewing the predecessor-successor relationships between system interfaces and application modules, details of input / output terminals, and the existing status of audit indicators for system interfaces and application modules. This establishes a long-term effective audit mechanism, ensuring the timely detection of abnormal data and reducing the loss of business revenue.

[0094] Figure 5 A flowchart illustrating Embodiment 3 of the method for locating abnormal data provided in this application. Figure 5 As shown, based on any of the above embodiments, the process of the abnormal data location method may include:

[0095] S501: For each production unit, retrieve the business data of each region under the production unit from the data storage server according to a preset cycle, and update the business data to the data storage area of ​​the next level page of the corresponding production unit node in the audit map.

[0096] In this step, after obtaining the predecessor and successor relationships between various business systems and internal functional modules within the enterprise, it is necessary to map the corresponding business data to them in order to monitor the generation of abnormal data in real time. Specifically, for each production unit, business data for each region under the production unit is retrieved from the data storage server according to a preset cycle, and the business data is updated to the data storage area of ​​the next-level page of the corresponding production unit node in the audit map.

[0097] The business data is uniformly stored on a server set up within the enterprise. This data storage server stores the business data generated in real time by various business systems. When business data needs to be obtained, the system connects to this server and can obtain the target business data based on the business data name, etc.

[0098] The audit map system includes business data from all business systems, therefore it needs to be read in real-time from the server storing business data and stored in the corresponding location on the audit map. In practice, each production unit is used by at least one region. Therefore, when a region applies the production unit, it generates business data in real time, which is stored in a specific location on the server. Once the audit map establishes the node for that production unit, it reads the business data generated by the region applying that production unit from the server and stores it in the data storage area of ​​the next-level page of the corresponding production unit node on the audit map, thus enabling the application of business data in the audit map system.

[0099] In one possible implementation, the business data stored on the data storage server is collected in real time by the management devices of each production unit. Specifically, audit slots are set up under the functional modules of each production unit based on audit indicators and audit elements. Within a preset time period, the management devices of each production unit collect the business data generated by the audit slots in real time and upload it to the data storage server for the audit map system to obtain the business data in real time.

[0100] S502: Based on the business data stored in the data storage area and the preset data specifications, check the business data of each region under the node of the production unit to determine whether there is any abnormal business data.

[0101] In this step, based on step S501, business data for each region under the production unit is obtained from the data storage server according to a preset period. After updating the business data to the data storage area of ​​the next-level page of the corresponding production unit node in the audit map, the business data for each region under the production unit node is checked in conjunction with the preset data specifications to determine whether there is any abnormal business data.

[0102] The pre-defined data specifications are embedded in the audit map system. These specifications are primarily used to determine whether there are any issues with the actual business data generated by each business system. For example, if the specification for a certain business data is four lowercase letters, but the detected actual business data is four digits, this does not conform to the business data specification and therefore needs to be processed as abnormal data.

[0103] S503: For each region containing abnormal business data in the next-level page of the production unit node, an abnormal region identifier is set. The abnormal region identifier is used to indicate the number of abnormal business data in the current region.

[0104] In this step, based on step S502 and the preset data specifications, the business data of each region under the node of the production unit is checked to determine whether there is any abnormal business data. If there is abnormal business data, the audit map system marks each region with abnormal business data in the next level page of the node of the production unit as an abnormal region. The abnormal region mark is used to indicate the number of abnormal business data in the current region.

[0105] Specifically, the generation of abnormal business data is located to a specific production unit in a specific region. If the audit map system, in conjunction with preset data specifications, finds that the actual business data generated in a certain region is inconsistent with the preset data specifications, the audit map system will automatically mark the abnormal region under that production unit. This abnormality mark is used to indicate the number of abnormal business data existing in the current region. Based on the number of records, it can be determined whether to view the abnormal data and other operations.

[0106] The abnormal data location method provided in this embodiment mainly explains how to acquire business data and identify abnormal data. The actual business data for each region under each production unit is read from the data storage server. Abnormal data identification is primarily based on preset data specifications. When the actual generated business data is inconsistent with the preset data specifications, the corresponding region under the production unit corresponding to the abnormal data is marked as abnormal, indicating the quantity of abnormal business data in that region. Through this method, users can clearly see the quantity of abnormal data generated in each region on the audit map visualization interface, enabling timely detection and location of abnormal data, laying the foundation for subsequent revenue assurance.

[0107] Figure 6 A flowchart illustrating Embodiment 4 of the method for locating abnormal data provided in this application. Figure 6 As shown, based on any of the above embodiments, the process of the abnormal data location method may include:

[0108] S601: If any node in a production unit contains abnormal business data, the node of the production unit will be marked as abnormal on the main page of the audit map. The abnormality mark is used to indicate that the node of the production unit is an abnormal node and the total amount of abnormal business data.

[0109] In this step, when the audit map system finds problems with the actual business data based on the preset data specifications, it identifies the data as abnormal business data and marks the nodes of the production unit as abnormal on the main page of the audit map. The abnormal mark indicates that the nodes of the production unit are abnormal nodes and the total amount of abnormal business data.

[0110] The audit map main page displays numerous production unit nodes. Under each production unit node, there is business data for various regions. When the business data generated by a region is inconsistent with the preset data specifications, the audit map system will promptly identify it and mark the anomaly in the corresponding production unit, indicating that there is an abnormal node within that production unit, and also displaying the total amount of abnormal business data.

[0111] The abnormal data location method provided in this embodiment mainly illustrates how to represent abnormal nodes in an audit map system. Based on abnormal business data, the audit map system identifies the abnormal node at the corresponding location of the business data and marks the abnormal node and the total amount of abnormal business data on the corresponding production unit. This assists users in accurately locating the abnormal data and promptly eliminating subsequent revenue loss issues caused by the abnormal data.

[0112] Figure 7 A flowchart illustrating Embodiment 5 of the method for locating abnormal data provided in this application. Figure 7 As shown, based on any of the above embodiments, the process of the abnormal data location method further includes:

[0113] S701: For each abnormal region, obtain authorization information to view the abnormal data. The authorization information includes the login account and password for logging into the audit map system.

[0114] In this step, based on the audit map and preset data specifications, after abnormal business data is detected, the audit map system automatically identifies the corresponding region as an abnormal region. When the number of abnormal business transactions in a certain region reaches a preset threshold, the audit map system needs to send an alarm message to the management device corresponding to that abnormal region. After receiving the corresponding alarm message, the management device needs to log in to the audit map system to view the abnormal data. However, logging into the audit map system from an abnormal region requires authorization. Therefore, for each abnormal region, authorization information for viewing the abnormal data needs to be obtained first.

[0115] Specifically, the authorization information includes the login account and password for logging into the audit map system. This login account and password assists managers of abnormal areas in logging into the audit map system to view abnormal data for the corresponding areas.

[0116] S702: Send authorization information to management devices in abnormal areas.

[0117] In this step, based on step S701, after the audit map system obtains the authorization information to view the abnormal data, it sends the authorization information to the management device of the abnormal area.

[0118] In this system, management devices in abnormal areas log in to the audit map system using the login account and password provided with authorization information. However, the audit map system only displays the actual flow of business data within the corresponding production unit's business function modules, as well as the identified abnormal data.

[0119] The abnormal data location method provided in this embodiment mainly explains how the audit map system authorizes management devices in abnormal areas to log in to the corresponding audit map system. Specifically, the audit map system authorizes a login account and password for each management device in an abnormal area, enabling it to log in to the audit map system to view and correct the corresponding abnormal data after receiving an alarm message from the audit map system, thereby ensuring business revenue.

[0120] Figure 8 A flowchart illustrating Embodiment Six of the method for locating abnormal data provided in this application. Figure 8 As shown, based on any of the above embodiments, the process of the abnormal data location method may further include:

[0121] S801: Accepts login requests for the audit map system sent by management devices in any abnormal area. The login request for the audit map system includes the login account and password.

[0122] In this step, after receiving authorization information from the audit map system, the management device in the abnormal area logs into the audit map system using the login account and password included in the authorization information to view the corresponding abnormal data information. When the management device in the abnormal area receives the login account and password entered by the maintenance personnel, it sends a login request to the audit map system.

[0123] The login request includes a login account and password. Only after the audit map system verifies that the login information is correct can the management devices in the corresponding abnormal areas access the visualization interface of the audit map and view the abnormal business data.

[0124] S802: Verify the login account and password.

[0125] In this step, based on step S801, after the audit map system receives the audit map system login request sent by the management device of any abnormal area, it verifies the login account and password included in the login request.

[0126] The audit map system stores the login account and password for each regional management device. When a region sends a login request, the login account and password it carries can be compared with the account and password stored in the audit map system to determine whether the login account and password are correct.

[0127] S803: If the verification passes, return all abnormal business data of the abnormal area in the audit map to the management device of the abnormal area.

[0128] In this step, after the login account and password are verified by the audit map system based on step S802, if the verification is successful, the audit map system returns all abnormal business data of the abnormal area in the audit map to the management device of the abnormal area.

[0129] Once the management devices in the abnormal area have successfully logged in using their username and password, they can access the visualization interface of the audit map system. This visualization interface primarily displays all abnormal business data corresponding to that abnormal area; abnormal business data for other areas are not shown.

[0130] This embodiment provides a method for locating abnormal data, primarily illustrating how management devices in abnormal areas can successfully log in to the audit map system. Specifically, the management device in the abnormal area sends a login request containing its username and password to the audit map system. After successful verification, the management device in the abnormal area can successfully log in to the visual interface of the audit map system. This interface only displays abnormal business data from the specific abnormal area; abnormal business data from other areas is not accessible to the management device in that area. This method provides management devices in abnormal areas with the permission to view and correct abnormal business data, while preventing the display of abnormal business data from other areas on the management device in the abnormal area. This protects the data privacy of other areas and avoids data corruption.

[0131] As an optional implementation, multiple production units include multiple of the following business functions: Rule Center, Resource Center, Public Product Center, Clearing Center, Recharge Center, Number Portability, Permission Center, Public Order Center, Public Customer Center, Rights Center, Data Exchange Center, Payment Center, Headquarters Electronic Invoice System, Channel Management Center, Internet of Things, Operations Management System, Activation Center, Delivery Center, Activity Center, Public Accounts Center, Credit Control Center, Notification Center, Partner Relationship Management (PRM), Financial Shared Service Center, Supply Chain Shared Service Center, Provincial Procurement Center, Call Detail Record Management Center, Public Billing Center, Settlement Accounts, Revenue Management Center, Enterprise Resource Planning (ERP) Core System, Financial Management Application, Virtual Operations Open Platform (VOP), Government and Enterprise Product Center, Government and Enterprise Order Center, Government and Enterprise Finance Center, Government and Enterprise Billing Center, Government and Enterprise Aggregation Center, Information and Communications Technology (ICT) System, Government and Enterprise Customer Center, Government and Enterprise Marketing Center, and Government and Enterprise Strategy Center.

[0132] Specifically, each enterprise has multiple business systems. Therefore, in the audit map system, the multiple production units corresponding to multiple business systems include multiple of the following business functions.

[0133] The included production units include: Public Product Center, Clearing Center, Recharge Center, Number Portability, Permission Center, Public Order Center, Public Customer Center, Rights Center, Data Exchange Center, Payment Center, Headquarters Electronic Invoice System, Channel Management Center, Internet of Things (IoT), Operations Management System, Activation Center, Delivery Center, Activity Center, Public Accounting Center, Credit Control Center, Notification Center, PRM, Financial Shared Service Center, Supply Chain Shared Service Center, Provincial Procurement Center, Call Detail Record Management Center, Public Billing Center, Settlement Accounts, Revenue Management Center, ERP Core System, Financial Management Application, VOP, Government and Enterprise Product Center, Government and Enterprise Order Center, Government and Enterprise Finance Center, Government and Enterprise Billing Center, Government and Enterprise Aggregation Center, Emerging ICT System, Government and Enterprise Customer Center, Government and Enterprise Marketing Center, and Government and Enterprise Strategy Center. These production units provide different functionalities and are identified by boxes in the audit map system. The specific identifiers used in the visual interface of the audit map system can be adjusted according to actual needs. At the same time, there are certain data flow relationships and sequential call relationships between the various production units. Therefore, there are data connections between the various production units on the main page of the audit map system, which represent the flow process of business data.

[0134] Based on any of the above embodiments, in one possible implementation, Figure 9 This is a view of the internal production unit of the audit map system provided in this application. For example... Figure 9 As shown, the internal production unit view of this audit map system includes various business systems. Based on different business types, they are divided into front-end, application programs, customer service operation platform, network elements, government and enterprise operation platform, and government and enterprise application programs. Each business type contains multiple business systems; for example, the front-end includes a rules center and resource center, while the customer service operation platform includes an operation management system, activation center, and payment center. Connections exist between different business systems, representing the predecessor and successor relationships between different production units, clearly demonstrating the data flow process between production units throughout the enterprise.

[0135] This embodiment primarily describes the multiple business functions included in the various production units within the audit map system. These business functions correspond to all business systems used within the enterprise, thus providing a reliable logical framework for the construction of the audit map system. Furthermore, subsequent use of the audit map to locate abnormal data is relatively quick and accurate, enabling the determination of the abnormal data's origin within a short period, thereby ensuring business revenue.

[0136] Based on any of the above embodiments, in one possible implementation, Figure 10 This is a view of the internal functional modules of the audit map system provided in this application. For example... Figure 10 As shown, the internal functional module view of this audit map system mainly displays various functional modules within the Public Billing Center production unit, but not all of them are shown; only a portion of the modules included within the Public Billing Center production unit are displayed. In this functional module view, the Public Billing Center includes functional modules such as Call Detail Record (CDR) interface acquisition, Sub-Segmentation, Sub-Segmentation, Retrieval, Rollback, Error Request Entry, and Real-time Billing and Pricing. The predecessor-successor relationships between these functional modules are defined by lines with arrows; for example, the Sub-Segmentation module connects to the new architecture Sub-Segmentation, and the CDR interface acquisition module connects to the IOP, etc.

[0137] Based on any of the above embodiments, in one possible implementation, Figure 11 This is the internal functional matrix of the audit map system provided in this application. For example... Figure 11As shown, the internal functional matrix of this audit map system is four rows and five columns. The first row represents the matrix / dimension, consistency (input), accuracy (input), completeness (input), and standardization (input). The matrix / dimension represents the database tables storing business data involved in the actual operation of a functional module within a production unit, such as tables a, b, and c. Consistency (input), accuracy (input), completeness (input), and standardization (input) represent the audit elements. Figure 11 The main information recorded includes the person who organized the information, the time of organization, the person who confirmed the information, and the time of confirmation.

[0138] Based on any of the above embodiments, in one possible implementation, Figure 12 This is a structural diagram of the audit map system provided in this application. Figure 12 As shown in the diagram, the audit map system structure, based on the integrated billing and accounting operation model, categorizes business data into public middle platform, government and enterprise middle platform, management middle platform, and data middle platform according to different service targets. Simultaneously, based on the different locations of business data flow, audit objects are set as data files, data messages, and database table data. The specific audit map system model structure is divided into four parts: production unit, application module, audit slots, and audit indicators. Specifically, each production unit contains multiple application modules, and each application module includes multiple nodes for business data flow. Based on audit elements, audit slots are set at corresponding audit locations. The subsequent business data acquisition system can collect corresponding business data according to the audit slot identifiers to achieve business data monitoring. At each audit slot, audit indicators are set, mainly used to set certain audit standards for the audit slot. Audit elements include completeness, consistency, accuracy, and standardization. To cover the entire business data flow process within the enterprise and achieve comprehensive coverage both horizontally and vertically, the system structure utilizes a collaborative approach between IT auditing and business auditing. IT auditing primarily focuses on the business data stored in all database tables, while business auditing focuses on the business nodes that flow through a specific business process from start to finish. Based on a collaborative model, the necessity of data auditing and its corresponding audit logic are considered from the perspectives of data integrity, consistency, accuracy, and standardization, enabling data auditing within and between systems. Simultaneously, this audit map can connect all domains in the revenue chain, including B, M, O, and D domains. The B domain mainly relates to user and business data, such as user consumption habits, business content, and target audience, primarily involving billing information. The M domain mainly relates to the management platform, primarily involving revenue-related content. The O domain mainly relates to network data, such as faults and network resources, primarily involving network elements. The D domain mainly relates to data domains, i.e., data generated during business operations.

[0139] Figure 13 A schematic diagram of the structure of an embodiment of the abnormal data location device provided in this application. Figure 13 As shown, the abnormal data locating device 1300 includes:

[0140] The response module 1301 is used to respond to the user's click operation on the abnormal node of the audit map displayed on the page and display the next level page of the abnormal node; the main page of the audit map includes nodes of multiple production units and the connection relationship between nodes, and each production unit node stores business data and data specifications generated in various regions.

[0141] The processing module 1302 is used to determine at least one abnormal region that needs to be viewed for abnormal business data based on the abnormal region indication in the next level page of the abnormal node. The next level page of the abnormal node includes multiple regions and at least one abnormal region identifier.

[0142] The sending module 1303 is used to send an abnormal data alarm message to the management device of each abnormal region based on at least one abnormal region.

[0143] Optionally, the processing module 1302 is also used for:

[0144] Based on the predecessor and successor relationships between multiple production units and business modules, the list of interfaces between business modules, the list of functional modules within each business module and the list of interfaces between functional modules, and the list of interfaces between each business module and the system, an audit map is generated. The audit map includes the main page and the next-level page of each production unit node.

[0145] Optionally, the processing module 1302 is also used for:

[0146] For each production unit, business data for each region under the production unit is retrieved from the data storage server according to a preset cycle, and the business data is updated to the data storage area of ​​the next level page of the corresponding production unit node in the audit map.

[0147] For the business data stored in the data storage area and the preset data specifications, the business data of each region under the node of the production unit is checked to determine whether there is any abnormal business data;

[0148] For each region containing abnormal business data in the next-level page of the production unit node, an abnormal region identifier is created. The abnormal region identifier is used to indicate the number of abnormal business data existing in the current region.

[0149] Optionally, the processing module 1302 is also used for:

[0150] If any node in a production unit contains abnormal business data, the node of the production unit will be marked as abnormal on the main page of the audit map. The abnormality mark is used to indicate that the node of the production unit is an abnormal node and the total amount of abnormal business data.

[0151] Optionally, the transmitting module 1303 is also used for:

[0152] Send authorization information to management devices in abnormal areas.

[0153] Optionally, the processing module 1302 is also used for:

[0154] Verify the login account and password.

[0155] Optionally, the transmitting module 1303 is also used for:

[0156] If the verification passes, all abnormal business data of the abnormal area in the audit map will be returned to the management equipment of the abnormal area.

[0157] Optionally, multiple production units may include multiple of the following business functions: Rules Center, Resource Center, Public Product Center, Clearing Center, Recharge Center, Number Portability, Permission Center, Public Order Center, Public Customer Center, Rights Center, Data Exchange Center, Payment Center, Headquarters Electronic Invoice System, Channel Management Center, Internet of Things, Operations Management System, Activation Center, Delivery Center, Activity Center, Public Accounts Center, Credit Control Center, Notification Center, Partner Relationship Management, Financial Shared Service Center, Supply Chain Shared Service Center, Provincial Comprehensive Procurement, Call Detail Record Management Center, Public Billing Center, Settlement Accounts, Revenue Management Center, Enterprise Resource Planning Core System, Financial Management Application, Virtual Operations Open Platform, Government and Enterprise Product Center, Government and Enterprise Order Center, Government and Enterprise Finance Center, Government and Enterprise Billing Center, Government and Enterprise Aggregation Center, Emerging Information and Communication Technology System, Government and Enterprise Customer Center, Government and Enterprise Marketing Center, and Government and Enterprise Strategy Center.

[0158] The apparatus provided in this application embodiment can be used to execute the abnormal data location method in the above-described embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0159] Figure 14 A schematic diagram of the structure of Embodiment 2 of the abnormal data locating device provided in this application. Figure 13 Based on the first embodiment of the abnormal data location device, such as Figure 14 As shown, the abnormal data locating device 1300 also includes:

[0160] Module 1304 is used for:

[0161] Multiple business modules within the system are acquired as multiple production units.

[0162] Optionally, module 1304 is also used for:

[0163] For each abnormal region, obtain authorization information to view the abnormal data. The authorization information includes the login account and password for logging into the audit map system.

[0164] Optionally, module 1304 is also used for:

[0165] Accept login requests for the audit map system sent by management devices in any abnormal area. The login request for the audit map system includes the login account and password.

[0166] The apparatus provided in this application embodiment can be used to execute the abnormal data location method in the above-described embodiments. Its implementation principle and technical effect are similar, and will not be described again here.

[0167] Figure 15 A schematic diagram of the structure of the electronic device for locating abnormal data provided in this application. Figure 15 As shown, the electronic device may specifically include a receiver 1500, a transmitter 1501, a processor 1502, and a memory 1503. The receiver 1500 and transmitter 1501 are used to realize data transmission between the audit map system and the production unit management equipment. The memory 1503 stores computer-executed instructions. The processor 1502 executes the computer-executed instructions stored in the memory 1503 to implement the abnormal data location method in the above embodiment.

[0168] This embodiment provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the abnormal data location method in the above embodiment.

[0169] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the abnormal data location method provided in any of the above embodiments.

[0170] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are all optional embodiments, and the actions and modules involved are not necessarily essential to this application.

[0171] It should be further noted that although the steps in the flowchart are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowchart may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these sub-steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the sub-steps or stages of other steps.

[0172] It should be understood that the above-described device embodiments are merely illustrative, and the device of this application can also be implemented in other ways. For example, the division of units / modules in the above embodiments is only a logical functional division, and there may be other division methods in actual implementation. For example, multiple units, modules, or components may be combined, or integrated into another system, or some features may be ignored or not executed.

[0173] Furthermore, unless otherwise specified, the functional units / modules in the various embodiments of this application can be integrated into one unit / module, or each unit / module can exist physically separately, or two or more units / modules can be integrated together. The integrated units / modules described above can be implemented in hardware or in the form of software program modules.

[0174] When integrated units / modules are implemented in hardware, the hardware can be digital circuits, analog circuits, etc. The physical implementation of the hardware structure includes, but is not limited to, transistors, memristors, etc. Unless otherwise specified, the processor can be any suitable hardware processor, such as a CPU, GPU, FPGA, DSP, and ASIC, etc. Unless otherwise specified, the storage unit can be any suitable magnetic or magneto-optical storage medium, such as Resistive Random Access Memory (RRAM), Dynamic Random Access Memory (DRAM), Static Random Access Memory (SRAM), Enhanced Dynamic Random Access Memory (EDRAM), High-Bandwidth Memory (HBM), Hybrid Memory Cube (HMC), etc.

[0175] If the integrated unit / module is implemented as a software program module and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0176] In the above embodiments, the descriptions of each embodiment have their own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments. The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as the combination of these technical features does not contradict each other, it should be considered within the scope of this specification.

[0177] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.

[0178] It should be understood that this application is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of this application is limited only by the appended claims.

Claims

1. A method for locating abnormal data, characterized in that, include: In response to a user's click on an abnormal node in the audit map displayed on the page, the next level page of the abnormal node is displayed; the main page of the audit map includes nodes of multiple production units and the connection relationships between the nodes, and each production unit node stores business data and data specifications generated in various regions. Based on the abnormal region indication in the next level page of the abnormal node, at least one abnormal region that needs to be viewed for abnormal business data is determined. The next level page of the abnormal node includes multiple regions and at least one abnormal region identifier. Based on the at least one abnormal region, send an abnormal data alarm message to the management device of each abnormal region; Before displaying the next level page of the abnormal node in response to a user's click on an abnormal node in the audit map displayed on the page, the method further includes: Multiple business modules within the system are acquired as multiple production units; Based on the multiple production units, the predecessor and successor relationships between business modules, the list of interfaces between business modules, the list of functional modules within each business module and the list of interfaces between functional modules, and the list of interfaces between each business module and the system, the audit map is generated. The audit map includes the main page and the next-level page of each production unit node.

2. The method according to claim 1, characterized in that, The method further includes: For each production unit, business data for each region under the production unit is retrieved from the data storage server according to a preset cycle, and the business data is updated to the data storage area of ​​the next-level page of the corresponding production unit node in the audit map. Based on the business data stored in the data storage area and the preset data specifications, the business data of each region under the node of the production unit is checked to determine whether there is any abnormal business data; For each region containing abnormal business data in the next-level page of the node of the production unit, an abnormal region identifier is set, which is used to indicate the number of abnormal business data in the current region.

3. The method according to claim 2, characterized in that, The method further includes: If any node in a production unit contains abnormal business data, the node of that production unit will be marked as abnormal on the main page of the audit map. The abnormality mark indicates that the node of the production unit is an abnormal node and the total amount of abnormal business data.

4. The method according to any one of claims 1 to 3, characterized in that, The method further includes: For each abnormal region, obtain authorization information to view the abnormal data. The authorization information includes the login account and password for logging into the audit map system. The authorization information is sent to the management equipment in the abnormal area.

5. The method according to claim 4, characterized in that, The method further includes: Accept login requests for the audit map system sent by management devices in any abnormal area, wherein the login request for the audit map system includes a login account and password; Verify the login account and password; If the verification is successful, all abnormal business data of the abnormal area in the audit map will be returned to the management device of the abnormal area.

6. The method according to any one of claims 1 to 3, characterized in that, The multiple production units include several of the following business functions: Rules Center, Resource Center, Public Product Center, Clearing Center, Recharge Center, Number Portability, Permission Center, Public Order Center, Public Customer Center, Rights Center, Data Exchange Center, Payment Center, Headquarters Electronic Invoice System, Channel Management Center, Internet of Things, Operation Management System, Activation Center, Delivery Center, Activity Center, Public Accounts Center, Credit Control Center, Notification Center, Partner Relationship Management, Financial Shared Service Center, Supply Chain Shared Service Center, Provincial Comprehensive Procurement, Call Detail Record Management Center, Public Billing Center, Settlement Accounts, Revenue Management Center, Enterprise Resource Planning Core System, Financial Management Application, Virtual Operation Open Platform, Government and Enterprise Product Center, Government and Enterprise Order Center, Government and Enterprise Finance Center, Government and Enterprise Billing Center, Government and Enterprise Aggregation Center, Emerging Information and Communication Technology System, Government and Enterprise Customer Center, Government and Enterprise Marketing Center, and Government and Enterprise Strategy Center.

7. A device for locating abnormal data, characterized in that, include: The response module is used to respond to the user's click operation on the abnormal node of the audit map displayed on the page and display the next level page of the abnormal node; the main page of the audit map includes nodes of multiple production units and the connection relationship between the nodes, and each production unit node stores business data and data specifications generated in various regions. The processing module is used to determine at least one abnormal region that needs to be viewed for abnormal business data based on the abnormal region indication in the next level page of the abnormal node. The next level page of the abnormal node includes multiple regions and at least one abnormal region identifier. The sending module is used to send an abnormal data alarm message to the management device of each abnormal region based on the at least one abnormal region; The processing module is further configured to, before displaying the next-level page of the abnormal node in response to a user's click operation on an abnormal node of the audit map displayed on the page, obtain multiple business modules within the system as multiple production units; and generate the audit map based on the multiple production units, the predecessor and successor relationships between the business modules, the interface list between the business modules, the functional modules within each business module and the interface list between the functional modules, and the interface list between each business module and the system. The audit map includes the main page and the next-level page of each production unit's node.

8. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the abnormal data location method as described in any one of claims 1 to 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method for locating abnormal data as described in any one of claims 1 to 6.

Images