Data auditing method and device, electronic equipment, storage medium and computer program product

Abstract

The invention provides a data auditing method and device, electronic equipment, a storage medium and a computer program product, and relates to the technical field of cloud computing big data, and the method comprises the steps: periodically carrying out data auditing for order data, charging data and resource data corresponding to each user, and determining problem data with state differences among the order data, the charging data and the resource data. Thus, the order data, the charging data and the resource data of each user are periodically audited, and compared with a manual auditing mode in the related technology, the data auditing efficiency among the service systems of the cloud operators is improved.

Description

Technical Field

[0001] The present application relates to the field of cloud computing and big data technology, and in particular to a data auditing method, device, electronic device, storage medium and computer program product. Background Art

[0002] In the prior art, in the case of data inconsistency caused by abnormalities or changes in cloud operator services between systems, audit differences are currently conducted through passive discovery or active discovery. Passive discovery mainly involves passively discovering data differences through customer complaints or fault handling, and then conducting root cause investigation and data maintenance. Active discovery involves extracting source data, importing the source data into a temporary database, and performing manual data comparison according to the audit plan. The above methods have low audit efficiency. Summary of the invention

[0003] The embodiments of the present application provide a data audit method, device, electronic device, storage medium and computer program product, which can be used to improve the efficiency of data auditing between cloud operator business systems.

[0004] The technical solution of this application is implemented as follows:

[0005] The present application embodiment provides a data audit method, including:

[0006] Periodically perform data audits on the order data, billing data, and resource data corresponding to each user to determine problematic data with status differences among the order data, the billing data, and the resource data.

[0007] In the above scheme, the periodic data audit is performed on the order data, billing data and resource data corresponding to each user to determine the problematic data with status differences between the order data, the billing data and the resource data, including:

[0008] Periodically obtaining the order data and the billing data corresponding to each user at the same time point, and performing data audit on the order data and the billing data to determine the first problem data with status differences in the order data and the billing data corresponding to each user;

[0009] Periodically obtain the console resource data and the underlying resource data corresponding to each user, and perform data audit on the console resource data and the underlying resource data to determine the second problem data with status difference in the console resource data and the underlying resource data corresponding to each user; wherein the resource data includes at least one of the following: the console resource data and the underlying resource data;

[0010] Periodically obtain the console resource data corresponding to each user and the order data corresponding to each user within a predetermined time period, perform data audit on the console resource data and the order data, and determine the third problem data with status differences in the console resource data and the order data corresponding to each user.

[0011] In the above scheme, the periodic acquisition of the order data and the billing data corresponding to each user at the same time point, and the data audit of the order data and the billing data to determine the first problem data with status differences in the order data and the billing data corresponding to each user, includes:

[0012] Periodically obtaining the order data corresponding to each user from the business operation system at the same time point, and obtaining the billing data corresponding to each user from the billing system;

[0013] The order data and the billing data having the same identification information are audited to determine the first problem data.

[0014] In the above solution, the step of performing data audit on the order data and the billing data having the same identification information to determine the first problematic data includes:

[0015] Determine a consistency test result of a state represented by a preset character string in the order data and a state represented by a preset character string in the billing data having the same identification information;

[0016] If the consistency detection result indicates that the state represented by the preset string in the order data corresponding to the first identification information is inconsistent with the state represented by the preset string in the billing data, it is determined that the order data and the billing data corresponding to the first identification information are the first problem data.

[0017] In the above scheme, the periodic acquisition of the console resource data and the underlying resource data corresponding to each user, and the data audit of the console resource data and the underlying resource data to determine the second problem data with status differences in the console resource data and the underlying resource data corresponding to each user, include:

[0018] Periodically acquiring the console resource data and the underlying resource data corresponding to each user in the resource system according to the identification information corresponding to each user;

[0019] The console resource data and the bottom layer resource data having the same identification information are audited to determine the second problem data.

[0020] In the above scheme, the method further comprises:

[0021] The social attribute of the user corresponding to the second question data configuration.

[0022] In the above scheme, the periodic acquisition of the console resource data corresponding to each user and the order data corresponding to each user within a predetermined period, the data audit of the console resource data and the order data, and the determination of the third problem data having a status difference in the console resource data and the order data corresponding to each user include:

[0023] Periodically obtaining the console resource data corresponding to each user from the resource pool interface within a predetermined time period;

[0024] Periodically obtaining the order data corresponding to each user from the business operation system within a predetermined period; wherein the update time point corresponding to the order data is before the predetermined period;

[0025] The target order data corresponding to the console resource data is determined in the order data corresponding to each user, and data audit is performed on the console resource data and the target order data to determine the third problem data with status differences in the console resource data corresponding to each user and the target order data.

[0026] In the above scheme, the method further comprises:

[0027] Each resource pool stores the data fragments of N products corresponding to each user in a read-only library; where N is an integer greater than 0;

[0028] The database collects the data fragments in each read-only library into the database, and the database merges multiple data fragments of each product corresponding to each user to determine the intermediate resource data; wherein the database is configured with the resource pool interface;

[0029] The database performs a unified data model conversion on the enumeration value representing the status in the intermediate resource data of each user to determine the console resource data.

[0030] The present application also provides a data auditing device, including:

[0031] The audit unit is used to periodically perform data audit on the order data, billing data and resource data corresponding to each user, and determine the problematic data with status differences among the order data, the billing data and the resource data.

[0032] An embodiment of the present application further provides an electronic device, including a memory and a processor, wherein the memory stores a computer program that can be run on the processor, and the processor implements the steps in the above method when executing the computer program.

[0033] An embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the above method are implemented.

[0034] An embodiment of the present application also provides a computer program product, including a computer program, which implements the steps in the above method when executed by a processor.

[0035] In the embodiment of the present application, data audit is performed periodically on the order data, billing data and resource data corresponding to each user, and the problematic data with status differences between the order data, billing data and resource data are determined. In this way, the order data, billing data and resource data of each user are audited periodically, which improves the data audit efficiency between cloud operator business systems compared to the manual audit method in the related art. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] Figure 1 An optional effect schematic diagram of the related technology provided by the embodiment of the present application;

[0037] Figure 2 An optional flow chart of a data audit method provided in an embodiment of the present application;

[0038] Figure 3 An optional effect diagram of the data audit method provided in the embodiment of the present application;

[0039] Figure 4 An optional flow chart of a data audit method provided in an embodiment of the present application;

[0040] Figure 5 An optional flow chart of a data audit method provided in an embodiment of the present application;

[0041] Figure 6 An optional flow chart of a data audit method provided in an embodiment of the present application;

[0042] Figure 7 An optional effect diagram of the data audit method provided in the embodiment of the present application;

[0043] Figure 8 An optional flow chart of a data audit method provided in an embodiment of the present application;

[0044] Fig. 9An optional effect diagram of the data audit method provided in the embodiment of the present application;

[0045] Fig.10 An optional flow chart of a data audit method provided in an embodiment of the present application;

[0046] Fig.11 An optional flow chart of a data audit method provided in an embodiment of the present application;

[0047] Fig.12 An optional effect diagram of the data audit method provided in the embodiment of the present application;

[0048] Fig.13 A schematic diagram of the structure of a data audit device provided in an embodiment of the present application;

[0049] Fig.14 A hardware entity schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0050] In order to make the purpose, technical solutions and advantages of the present application clearer, the technical solutions of the present application are further elaborated in detail below in conjunction with the drawings and embodiments. The described embodiments should not be regarded as limiting the present application. All other embodiments obtained by ordinary technicians in the field without making creative work are within the scope of protection of the present application.

[0051] In the following description, reference is made to “some embodiments”, which describe a subset of all possible embodiments, but it will be understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0052] If similar descriptions of "first / second" appear in the application documents, the following instructions are added. In the following description, the terms "first\second\third" involved are merely used to distinguish similar objects and do not represent a specific ordering of the objects. It can be understood that "first\second\third" can be interchanged in a specific order or sequence where permitted, so that the embodiments of the present application described herein can be implemented in an order other than that illustrated or described herein.

[0053] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application belongs. The terms used herein are only for the purpose of describing the embodiments of this application and are not intended to limit this application.

[0054] Combination Figure 1In the related technologies, with the continuous development of cloud operators' business, the number of customers and customer orders has increased dramatically. The business process starts with customers placing orders through the portal, using orders as a carrier, and through mutual calls between systems, billing relationships are generated, and customer resources are opened / closed. During the entire life cycle of orders, billing, and resources, multiple systems need to interact through interfaces. During the frequent interactions between systems, data inconsistencies may occur due to system anomalies and changes.

[0055] Currently, there are two ways to audit data inconsistencies:

[0056] 1. Passive discovery of audit differences: Passive discovery of data differences during customer complaints / fault handling, root cause investigation and data maintenance. 2. Active discovery of audit differences: After the source data is extracted, it is imported into a temporary database, and manual data comparison is performed according to the audit plan. Obtain the difference results.

[0057] Among them, audit differences are passively discovered through complaints, customer satisfaction is reduced, user experience is poor, and difference data cannot be fully covered. Differences are actively discovered through manual data comparison, because the collection of data from each system is manual, involving multiple products, multiple resource pools and other issues. At the same time, manual collection is difficult to control the collection time, and there are time differences in the data. This leads to high labor costs, and the accuracy of the audit cannot be guaranteed. This application proposal proposes to automatically perform data audits at a specified period to solve the problems of long audit cycles, reduce labor costs, and improve the accuracy of audit results.

[0058] In order to solve the above technical problems, the present application embodiment provides a data audit method. Please refer to 2, which is an optional flow chart of the data audit method provided in the present application embodiment. Figure 2 The steps shown are explained:

[0059] S101. Periodically audit the order data, billing data, and resource data corresponding to each user to determine problematic data with status differences among the order data, the billing data, and the resource data.

[0060] In an embodiment of the present application, a data audit device is connected in communication with a system platform for managing order data, billing data, and resource data in a cloud operator's business. The data audit device can periodically obtain order data, billing data, and resource data corresponding to each user from a system platform for managing order data, billing data, and resource data. Data audits are performed on order data and billing data, and data audits are performed on console resource data and underlying resource data in resource data. Data audits are performed on order data and resource data to determine problematic data with status differences between the order data, the billing data, and the resource data.

[0061] In the embodiment of the present application, the data audit device can periodically obtain the order data, billing data and resource data corresponding to each user from the system platform that manages order data, billing data and resource data according to the predetermined audit time. Perform data audit on the order data, billing data and resource data corresponding to each user to determine the problem data.

[0062] In the present application embodiment, combined Figure 3 The data audit device is divided into three audit sub-modules: the business support audit module is used to audit the problem data with status differences between order data and billing data. The resource management audit module is used to audit the problem data with status differences between console resource data and underlying resource data; the order and resource audit module is used to audit the problem data with status differences between order data and console resource data. Among them, order data is stored in the business operation system, and billing data is stored in the billing system.

[0063] Among them, the order data of each user is used to reflect the product type, transaction time, transaction value, transaction method, buyer information, seller information and other information of the corresponding user for the ordered product. The billing data is used to reflect the billing relationship of any product ordered by the corresponding user. Resource data includes basic resources, platform capabilities and software applications. Exemplarily, resource data may include information corresponding to the following resources:

[0064] Cloud host / cloud server: provides elastic computing resources, and users can flexibly adjust resource configuration according to their needs.

[0065] Cloud phone: A mobile phone service provided through virtualization technology that supports a variety of applications and functions.

[0066] Cloud space: provides storage services where users can store and manage large amounts of data.

[0067] Big data: Use the big data platform to collect, process and analyze data to help users tap into the value of data.

[0068] Artificial Intelligence: Provides artificial intelligence platforms and products to support the development and deployment of artificial intelligence (AI) projects.

[0069] In the embodiment of the present application, data audit is performed periodically on the order data, billing data and resource data corresponding to each user, and the problematic data with status differences between the order data, billing data and resource data are determined. In this way, the order data, billing data and resource data of each user are audited periodically, which improves the data audit efficiency between cloud operator business systems compared to the manual audit method in the related art.

[0070] Please refer to 4, which is an optional flow chart of the data audit method provided in the embodiment of the present application. Figure 2 S101 shown in the figure can also be implemented by S201 to S203, which will be described in combination with the steps:

[0071] S201. Periodically obtain the order data and the billing data corresponding to each user at the same time point, and perform data audit on the order data and the billing data to determine the first problem data with status difference in the order data and the billing data corresponding to each user.

[0072] In an embodiment of the present application, the data audit device periodically obtains the order data corresponding to each user from the business operation system at the same time point, and obtains the billing data corresponding to each user from the billing system. Compare the status differences between the order data and the billing data corresponding to the same user, and determine that the order data and billing data with status differences are the first problem data. Among them, the status differences between the order data and the billing data may include: 1. The order status has expired, and the billing relationship is valid / 2. The order status is valid, and the billing relationship is invalid; 3. Both the order status and the billing relationship are valid but the status is inconsistent (one is normal and the other is frozen).

[0073] Among them, the business operation system can be an MOP system: the MOP system is a mobile cloud business operation management platform, which mainly involves the management system of customer basic information and order information. Users initiate resource subscriptions through portals such as official websites, and MOP uses orders as data carriers to interact with the EBOSS system and resource system through interface calls to generate billing relationships, resource instances, etc. The billing system can be an EBOSS system: a business operation support system. The functions of the BOSS system mainly include three areas: billing, service guarantee and service implementation. With the introduction of new network technologies, each field will be affected by its own series of problems. This application mainly involves the billing module.

[0074] S202, periodically obtaining console resource data and underlying resource data corresponding to each user, and performing data audit on the console resource data and the underlying resource data to determine second problem data having status differences in the console resource data and the underlying resource data corresponding to each user.

[0075] In an embodiment of the present application, resource data includes: console resource data and underlying resource data. The data auditing device can periodically obtain the console resource data and underlying resource data corresponding to each user from the resource system. Compare the status differences between the console resource data and the underlying resource data corresponding to the same user, and determine that the console resource data and the underlying resource data with status differences are the second problem data. Among them, the status differences between the console resource data and the underlying resource data may include: 1. The console resource status is invalid, and the underlying resource is valid; 2. The console resource status is valid, and the underlying resource is invalid; 3. The console resource status and the underlying resource are both valid but the status is inconsistent (one is normal and the other is frozen).

[0076] The console resource data includes: the resource data of cloud hosts / cloud servers, cloud phones, cloud spaces, big data and artificial intelligence that can be displayed to users. The underlying resource data includes: the resource data of cloud hosts / cloud servers, cloud phones, cloud spaces, big data and artificial intelligence that cannot be displayed to users.

[0077] S203, periodically obtaining the console resource data corresponding to each user and the order data corresponding to each user within a predetermined time period, performing data audit on the console resource data and the order data, and determining third problem data having status differences in the console resource data and the order data corresponding to each user.

[0078] In an embodiment of the present application, the data auditing device periodically obtains the console resource data corresponding to each user from the resource pool within a predetermined period of time. And periodically obtains the order data corresponding to each user within a predetermined period of time. Wherein, the update time of the obtained order data is before the predetermined period of time. The data auditing device can compare the status difference between the console resource data and the corresponding order data corresponding to the same user, and determine that the console resource data and order data with differences are third problem data. Wherein, the status difference between the console resource data and the corresponding order data may include: 1. The order status is invalid, and the console resource status is valid; 2. The order status is valid, and the console resource status is invalid; 3. The order status and the console resource status are both valid but the status is inconsistent (one is normal and the other is frozen).

[0079] In the embodiment of the present application, the period for determining the first question data, the period for determining the second question data, and the period for determining the third question data may be the same or different.

[0080] In the embodiment of the present application, data auditing is performed on order data and billing data, data auditing is performed on the console resource data and the underlying resource data, and data auditing is performed on the console resource data and the order data. Compared with the manual auditing method in the related art, the efficiency of data auditing between cloud operator business systems is improved.

[0081] Please refer to 5, which is an optional flow chart of the data audit method provided in the embodiment of the present application. Figure 4 S201 shown in the figure can also be implemented through S301 to S302, which will be described in combination with the steps:

[0082] S301. Periodically and at the same time point, obtain the order data corresponding to each user from the business operation system, and obtain the billing data corresponding to each user from the billing system.

[0083] In an embodiment of the present application, the data auditing device can obtain the time point of extracting data, and then periodically use the identification information corresponding to each user to obtain the order data corresponding to each user from the business operation system, and obtain the billing data corresponding to each user from the billing system.

[0084] For example, the data audit device obtains data at a certain time point, and the two systems agree on a certain time point, for example, the full order data is compared with the billing data at 0:00:00 every day. The MOP and EBOSS systems clearly define the data acquisition criteria and use the billing code as the unique identification information of the two systems.

[0085] S302: Perform data audit on the order data and the billing data having the same identification information to determine the first problem data.

[0086] In the embodiment of the present application, the data auditing device can perform data audit on order data and billing data with the same identification information, and compare whether the states represented by the order data and billing data with the same identification information are consistent. A pair of order data and billing data with inconsistent states is determined as the first problem data.

[0087] In the embodiment of the present application, after the first question data is determined, the first question data can be stored in the target library for display.

[0088] In the embodiment of the present application, the order data corresponding to each user is periodically obtained from the business operation system at the same time point, and the billing data corresponding to each user is obtained from the billing system. The order data and the billing data with the same identification information are audited to determine the first problem data. In this way, by obtaining the order data and the billing data at the same time point, the data state error caused by obtaining the order data and the billing data at different time points is eliminated, and the accuracy of the determined first problem data is improved.

[0089] Please refer to 6, which is an optional flow chart of the data audit method provided in the embodiment of the present application. Figure 5 S302 shown in the figure can also be implemented through S401 to S402, which will be described in combination with the steps:

[0090] S401: Determine a consistency test result of a state represented by a preset character string in the order data having the same identification information and a state represented by a preset character string in the billing data.

[0091] In the embodiment of the present application, the preset character string in the order data is used to represent the state of the order data, and the preset character string in the billing data is used to represent the state of the billing data. The data auditing device can compare the state represented by the preset character string of the order data with the same identification information to see whether it is consistent with the state represented by the preset character string in the billing data, and determine the consistency test result.

[0092] The states represented by the preset character strings in the order data and the billing data may include: normal, frozen, and invalid.

[0093] S402. If the consistency detection result indicates that the state represented by the preset string in the order data corresponding to the first identification information is inconsistent with the state represented by the preset string in the billing data, it is determined that the order data and the billing data corresponding to the first identification information are the first problem data.

[0094] In an embodiment of the present application, if the consistency detection result represents that the state represented by the preset string in the order data corresponding to the first identification information is inconsistent with the state represented by the preset string in the billing data, the data auditing device determines that the order data and the billing data corresponding to the first identification information are the first problem data.

[0095] Exemplary, combined Figure 7The data audit device can obtain the order data corresponding to each user from the MOP system and the billing data corresponding to each user from the EBOSS system. Compare whether the order data and billing data corresponding to the same user are consistent. If they are inconsistent, the order data and billing data of the user are determined to be the first problematic data.

[0096] Please refer to 8, which is an optional flow chart of the data audit method provided in the embodiment of the present application. Figure 4 S202 shown in FIG. 1 can also be implemented through S501 to S502, which will be described in combination with the steps:

[0097] S501. Periodically obtain the console resource data and the underlying resource data corresponding to each user in a resource system according to identification information corresponding to each user.

[0098] In the embodiment of the present application, the data auditing device can obtain the identification information corresponding to each user, and obtain the console resource data and underlying resource data corresponding to each user in each resource pool of the resource system based on the identification information corresponding to each user.

[0099] In the embodiment of the present application, the console and the underlying data involve multiple resource pools, and data audit is performed in each resource pool. After the audit, the audit results are output to the target library. The console and the underlying data belong to the same system but different resource pools, so cross-resource pool data collection is not involved.

[0100] S502: Perform data audit on the console resource data and the bottom-level resource data having the same identification information to determine the second problem data.

[0101] In the embodiment of the present application, the preset character string in the console resource data is used to represent the state of the console resource data, and the preset character string in the underlying resource data is used to represent the state of the underlying resource data. The data auditing device can compare the state represented by the preset character string of the order data with the same identification information to see whether it is consistent with the state represented by the preset character string in the billing data. If they are inconsistent, it is determined that the console resource data and the underlying resource data of the user corresponding to the identification information are the second problem data.

[0102] In the embodiment of the present application, the data auditing device may also configure the social attributes of the user corresponding to the second question data.

[0103] In the embodiment of the present application, the data audit device needs to add social attributes, corresponding customer information, order information, whether to charge, etc. to the second problem data; and needs to complete the social attribute information from the MOP. After completing the information, the audited second problem data is output and the data is displayed in the form of a report.

[0104] Exemplary, combined Fig. 9 The data audit device can obtain the console resource data corresponding to each user from the console resource pool, and obtain the underlying resource data corresponding to each user from the underlying resource pool. Compare whether the states of the console resource data and the underlying resource data corresponding to the same user are consistent. If they are inconsistent, the console resource single data and the underlying resource data of the user are determined to be the second problem data.

[0105] In the embodiment of the present application, the console resource data and the underlying resource data corresponding to each user are periodically obtained in the resource system according to the identification information corresponding to each user. The console resource data and the underlying resource data having the same identification information are audited to determine the second problem data. In this way, compared with the manual data auditing method in the related art, the auditing efficiency for the console resource data and the underlying resource data is improved.

[0106] Please refer to 10, which is an optional flow chart of the data audit method provided in the embodiment of the present application. Figure 4 S203 shown in FIG. 1 can also be implemented through S601 to S603, which will be described in combination with the steps:

[0107] S601. Periodically obtain the console resource data corresponding to each user from a resource pool interface within a predetermined period of time.

[0108] In the embodiment of the present application, the data auditing device obtains identification information corresponding to each user, and obtains the console resource data corresponding to each user from the resource pool interface of the database within a predetermined time period based on the identification information.

[0109] S602: Periodically obtain the order data corresponding to each user from the business operation system within a predetermined period of time.

[0110] In the embodiment of the present application, the data auditing device periodically obtains the order data corresponding to each user from the business operation system within a predetermined time period.

[0111] The update time point corresponding to the order data is before the predetermined time period.

[0112] In the embodiment of the present application, the order data may include an update time field, and the data auditing device may obtain the order data before a predetermined period of time based on the update time field.

[0113] Among them, data collection is divided into time periods of T days (T>0). The audit needs to exclude data that has changed on T days, and data with update_time>0:00 on T days. This part of the data may cause "false differences" due to the problem of collection time difference; the inconsistency of this part of the data will be compared in the next round of audit over time. For example, at 15:00 on T day, the data of a product console is collected, and the order data is uniformly extracted at 16:00. As a result, the data of orders and resources generated normally from 15:00 to 16:00 are mistakenly considered to be valid orders and invalid resources during the comparison. Generate "false differences"

[0114] S603. Determine the target order data corresponding to the console resource data in the order data corresponding to each user, and perform data audit on the console resource data and the target order data to determine the third problem data having status differences between the console resource data corresponding to each user and the target order data.

[0115] The console resource data may be resource data corresponding to a product that has not been taken offline for a user. The data audit device may determine, in the order data corresponding to each user, the target order data corresponding to the console resource data corresponding to the product that has not been taken offline for the user. The data audit device may compare the state represented by a preset string of the target order data having the same identification information to see whether it is consistent with the state represented by a preset string in the console resource data. If they are inconsistent, the console resource data and the target order data of the user corresponding to the identification information are determined to be the third problematic data.

[0116] In the embodiment of the present application, the console resource data corresponding to each user is periodically obtained from the resource pool interface within a predetermined period. The order data corresponding to each user is periodically obtained from the business operation system within a predetermined period. The update time point corresponding to the order data is before the predetermined period. Since the update time point corresponding to the order data is before the predetermined period, the acquired order data has been updated, so the console data corresponding to the order data has also been updated, eliminating the audit error caused by the asynchronous update of the order data and the console data, and improving the accuracy of data auditing.

[0117] Please refer to 11, which is an optional flow chart of the data audit method provided in the embodiment of the present application, and will be described in combination with the steps:

[0118] S701. Each resource pool stores data segments corresponding to N products of each user in a read-only library.

[0119] In the embodiment of the present application, each resource pool creates a read-only library, and the resource pool stores data fragments corresponding to N products of each user in the read-only library, where N is an integer greater than 0.

[0120] Among them, multiple data fragments corresponding to the same product of the same user can be stored in readable libraries of different resource pools.

[0121] S702, the database collects the data fragments in each read-only library into the database, and the database merges multiple data fragments of each product corresponding to each user to determine the intermediate resource data; wherein the database is configured with the resource pool interface.

[0122] In the embodiment of the present application, the database collects the data fragments in each read-only library into the database. The database merges multiple data fragments corresponding to each product of each user to determine the intermediate resource data of N products corresponding to each user. The database is configured with the resource pool interface.

[0123] The data segments corresponding to the same product have the same data structure, and the database can merge the data segments with the same data structure for the same user to determine the corresponding intermediate resource data.

[0124] S703: The database performs a unified data model conversion on the enumeration value representing the state in the intermediate resource data of each user to determine the console resource data.

[0125] In the embodiment of the present application, the database performs a unified data model conversion on the enumeration value representing the status in the intermediate resource data of each user to determine the target resource data, and unifies the mapping relationship between the status of different product representations and the enumeration value.

[0126] Among them, because the data models and enumeration value definitions of each product are different, the aggregated data cannot be directly compared with the order, and a unified data model data conversion is required, and the enumeration value mapping relationship is unified. For example, the unified target resource data can be represented by Table 1:

[0127]

[0128] Table 1

[0129] In the embodiment of the present application, because the business development resource data (console) is generally distributed in multiple resource pools and deployed in different database nodes according to different products, and the order data does not involve cross-resource pools; therefore, the console data needs to be collected and aggregated first. Fig.12 The process of determining the third question data will be described with a specific example:

[0130] 1. Console data collection: Create a read-only library in each resource pool and collect the data of all products in the resource pool into the read-only library.

[0131] 2. Console data aggregation: Collect data from the read-only library of each product into the newly created data warehouse, merge tables with the same table structure, and add resource pool fields during the merging process to distinguish which resource pool the data comes from.

[0132] 3. Console data cleaning: Because the data models and enumeration value definitions of each product are different, the aggregated data cannot be directly compared with the orders. It is necessary to perform unified data model data conversion and unify the enumeration value mapping relationship.

[0133] 4. Console data transmission: After the console data is cleaned in the data warehouse, massive data is pushed to Kafka. At the same time, the audit platform agrees on the end time of pushing. The audit platform collects data regularly every day after the agreed time.

[0134] 5. Audit time point caliber: Data collection comes from a large number of different data nodes. Collecting data at the same time will cause certain pressure and risks to the existing network database. Therefore, data collection is designed to be collected in different time periods and completed on the same day (T days).

[0135] 6. Audit resource types are configurable: Because there are many types of resources and resources change frequently with marketing needs, the audit of orders and resources needs to be configurable, and the audit should be performed on the data in the basic table.

[0136] 7. Order data collection: Order data is collected at a specified time and needs to be completed on the same day as the resource console data. There must be an update time field in the order data.

[0137] In an embodiment of the present application, the database collects the data fragments in each read-only library into the database, and the database merges the multiple data fragments of each product corresponding to each user to determine the intermediate resource data; wherein the database is configured with the resource pool interface. The database performs a unified data model conversion to determine the console resource data for the enumeration value representing the state in the intermediate resource data of each user. In this way, the operation of merging the multiple data fragments of each product corresponding to each user can reduce the number of data fragments in the database, reduce the workload of database processing, and improve data processing efficiency. And performing a unified data model conversion on the intermediate resource data can eliminate the problem of different mapping relationships between data states and enumeration values ​​caused by inconsistent data models of each product, so that the mapping relationship between the state of console resource data of different products and the enumeration value is the same, eliminating the defect that the state of console resource data of different products cannot be compared with order data, and improving the accuracy of data auditing.

[0138] Please refer to 13, which is a structural diagram of the data auditing device provided in an embodiment of the present application.

[0139] The embodiment of the present application further provides a data auditing device 800 , including: an auditing unit 801 .

[0140] The audit unit 801 is used to periodically perform data audit on the order data, billing data and resource data corresponding to each user, and determine the problematic data with status differences among the order data, the billing data and the resource data.

[0141] In the embodiment of the present application, the audit unit 801 in the data audit device 800 is used to periodically obtain the order data and the billing data corresponding to each user at the same time point, and perform data audit on the order data and the billing data to determine the first problem data with status differences in the order data and the billing data corresponding to each user;

[0142] Periodically obtain the console resource data and the underlying resource data corresponding to each user, and perform data audit on the console resource data and the underlying resource data to determine the second problem data with status difference in the console resource data and the underlying resource data corresponding to each user; wherein the resource data includes at least one of the following: the console resource data and the underlying resource data;

[0143] Periodically obtain the console resource data corresponding to each user and the order data corresponding to each user within a predetermined time period, perform data audit on the console resource data and the order data, and determine the third problem data with status differences in the console resource data and the order data corresponding to each user.

[0144] In the embodiment of the present application, the audit unit 801 in the data audit device 800 is used to periodically obtain the order data corresponding to each user from the business operation system at the same time point, and obtain the billing data corresponding to each user from the billing system;

[0145] The order data and the billing data having the same identification information are audited to determine the first problem data.

[0146] In the embodiment of the present application, the audit unit 801 in the data audit device 800 is used to determine the consistency test result of the state represented by the preset string in the order data having the same identification information and the state represented by the preset string in the billing data;

[0147] If the consistency detection result indicates that the state represented by the preset string in the order data corresponding to the first identification information is inconsistent with the state represented by the preset string in the billing data, it is determined that the order data and the billing data corresponding to the first identification information are the first problem data.

[0148] In the embodiment of the present application, the audit unit 801 in the data audit device 800 is used to periodically obtain the console resource data and the underlying resource data corresponding to each user in the resource system according to the identification information corresponding to each user;

[0149] The console resource data and the bottom layer resource data having the same identification information are audited to determine the second problem data.

[0150] In the embodiment of the present application, the audit unit 801 in the data audit device 800 is used to configure the social attributes of the user corresponding to the second problem data.

[0151] In the embodiment of the present application, the audit unit 801 in the data audit device 800 is used to periodically obtain the console resource data corresponding to each user from the resource pool interface within a predetermined period of time;

[0152] Periodically obtaining the order data corresponding to each user from the business operation system within a predetermined period; wherein the update time point corresponding to the order data is before the predetermined period;

[0153] The target order data corresponding to the console resource data is determined in the order data corresponding to each user, and data audit is performed on the console resource data and the target order data to determine the third problem data with status differences in the console resource data corresponding to each user and the target order data.

[0154] In the embodiment of the present application, each resource pool stores data fragments of N products corresponding to each user in a read-only library; wherein N is an integer greater than 0;

[0155] The database collects the data fragments in each read-only library into the database, and the database merges multiple data fragments of each product corresponding to each user to determine the intermediate resource data; wherein the database is configured with the resource pool interface;

[0156] The database performs a unified data model conversion on the enumeration value representing the status in the intermediate resource data of each user to determine the console resource data.

[0157] It should be noted that in the embodiments of the present application, if the above-mentioned method for processing item information is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly reflected in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium and includes several instructions for enabling an item information processing device (which can be a personal computer, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a magnetic disk or an optical disk. In this way, the embodiments of the present application are not limited to any specific combination of hardware and software.

[0158] Correspondingly, an embodiment of the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps in the method on the data audit device side are implemented.

[0159] It should be noted here that the description of the above storage medium and device embodiments is similar to the description of the above method embodiments, and has similar beneficial effects as the method embodiments. For technical details not disclosed in the storage medium and device embodiments of this application, please refer to the description of the method embodiments of this application for understanding.

[0160] It should be noted that Fig.14 A hardware entity diagram of an electronic device provided in an embodiment of the present application, such as Fig.14 As shown, an embodiment of the present application provides an electronic device 900, including a memory 902 and a processor 901, wherein the memory 902 stores a computer program that can be run on the processor 901, and the processor 901 implements the steps in the above method when executing the program, wherein;

[0161] The processor 901 generally controls the overall operation of the electronic device 900 .

[0162] The memory 902 is configured to store instructions and applications executable by the processor 901, and can also cache data to be processed or processed by the processor 901 and various modules in the electronic device 900 (for example, image data, audio data, voice communication data, and video communication data), which can be implemented through flash memory (FLASH) or random access memory (Random Access Memory, RAM).

[0163] Correspondingly, an embodiment of the present application further provides a computer program product, including a computer program, which can be executed by the processor 901 of the electronic device 900 to complete the steps in the method on the data auditing device 800 side.

[0164] It should be understood that "one embodiment" or "an embodiment" mentioned throughout the specification means that specific features, structures or characteristics related to the embodiment are included in at least one embodiment of the present application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. In addition, these specific features, structures or characteristics can be combined in one or more embodiments in any suitable manner. It should be understood that in various embodiments of the present application, the size of the sequence number of the above-mentioned processes does not mean the order of execution, and the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The above-mentioned sequence numbers of the embodiments of the present application are only for description and do not represent the advantages and disadvantages of the embodiments.

[0165] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0166] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as: multiple units or components can be combined, or can be integrated into another system, or some features can be ignored, or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of the device or unit can be electrical, mechanical or other forms.

[0167] The units described above as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units; they may be located in one place or distributed on multiple network units; some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0168] In addition, all functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may be a separate unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0169] A person skilled in the art can understand that all or part of the steps of implementing the above method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it executes the steps of the above method embodiment; and the aforementioned storage medium includes: a mobile storage device, a read-only memory (ROM), a magnetic disk or an optical disk, and other media that can store program codes.

[0170] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application can be essentially or partly embodied in the form of a software product that contributes to the relevant technology. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the methods described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a mobile storage device, a ROM, a magnetic disk, or an optical disk.

[0171] The above is only an implementation method of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application.

Claims

1. A data audit method, characterized in that: include: Periodically perform data audits on the order data, billing data, and resource data corresponding to each user to determine problematic data with status differences among the order data, the billing data, and the resource data.

2. The data audit method according to claim 1, characterized in that: The periodic data audit is performed on the order data, billing data and resource data corresponding to each user to determine the problematic data with status differences between the order data, the billing data and the resource data, including: Periodically obtaining the order data and the billing data corresponding to each user at the same time point, and performing data audit on the order data and the billing data to determine the first problem data with status differences in the order data and the billing data corresponding to each user; Periodically obtain the console resource data and the underlying resource data corresponding to each user, and perform data audit on the console resource data and the underlying resource data to determine the second problem data with status difference in the console resource data and the underlying resource data corresponding to each user; wherein the resource data includes at least one of the following: the console resource data and the underlying resource data; Periodically obtain the console resource data corresponding to each user and the order data corresponding to each user within a predetermined time period, perform data audit on the console resource data and the order data, and determine the third problem data with status differences in the console resource data and the order data corresponding to each user.

3. The data audit method according to claim 2, characterized in that: The periodically acquiring the order data and the billing data corresponding to each user at the same time point, and performing data audit on the order data and the billing data to determine the first problem data having a status difference in the order data and the billing data corresponding to each user, includes: Periodically obtaining the order data corresponding to each user from the business operation system at the same time point, and obtaining the billing data corresponding to each user from the billing system; The order data and the billing data having the same identification information are audited to determine the first problem data.

4. The data audit method according to claim 3, characterized in that: The step of performing data audit on the order data and the billing data having the same identification information to determine the first problem data includes: Determine a consistency test result of a state represented by a preset character string in the order data and a state represented by a preset character string in the billing data having the same identification information; If the consistency detection result indicates that the state represented by the preset string in the order data corresponding to the first identification information is inconsistent with the state represented by the preset string in the billing data, it is determined that the order data and the billing data corresponding to the first identification information are the first problem data.

5. The data audit method according to claim 2, characterized in that: The periodic acquisition of the console resource data and the underlying resource data corresponding to each user, and the data audit of the console resource data and the underlying resource data to determine the second problem data having a status difference in the console resource data and the underlying resource data corresponding to each user, includes: Periodically acquiring the console resource data and the underlying resource data corresponding to each user in the resource system according to the identification information corresponding to each user; The console resource data and the bottom layer resource data having the same identification information are audited to determine the second problem data.

6. The data audit method according to claim 5, characterized in that: The method further comprises: The social attribute of the user corresponding to the second question data configuration.

7. The data audit method according to claim 2, characterized in that: The periodic acquisition of the console resource data corresponding to each user and the order data corresponding to each user within a predetermined period, performing data audit on the console resource data and the order data, and determining the third problem data having a status difference between the console resource data and the order data corresponding to each user, includes: Periodically obtaining the console resource data corresponding to each user from the resource pool interface within a predetermined time period; Periodically obtaining the order data corresponding to each user from the business operation system within a predetermined period; wherein the update time point corresponding to the order data is before the predetermined period; The target order data corresponding to the console resource data is determined in the order data corresponding to each user, and data audit is performed on the console resource data and the target order data to determine the third problem data with status differences in the console resource data corresponding to each user and the target order data.

8. The data audit method according to claim 7, characterized in that: The method further comprises: Each resource pool stores data fragments of N products corresponding to each user in a read-only library; where N is an integer greater than 0; The database collects the data fragments in each read-only library into the database, and the database merges multiple data fragments of each product corresponding to each user to determine the intermediate resource data; wherein the database is configured with the resource pool interface; The database performs a unified data model conversion on the enumeration value representing the state in the intermediate resource data of each user to determine the console resource data.

9. A data auditing device, characterized in that: include: The audit unit is used to periodically perform data audit on the order data, billing data and resource data corresponding to each user, and determine the problematic data with status differences among the order data, the billing data and the resource data.

10. An electronic device, characterized in that: The method comprises a memory and a processor, wherein the memory stores a computer program executable on the processor, and the processor implements the steps of the method according to any one of claims 1 to 8 when executing the computer program.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps in the method according to any one of claims 1 to 8 are implemented.

12. A computer program product, comprising a computer program, characterized in that The computer program implements the steps of the method according to any one of claims 1 to 8 when executed by a processor.

Images