CN111309758B - Charging data verification comparison method and device - Google Patents
Charging data verification comparison method and device Download PDFInfo
- Publication number
- CN111309758B CN111309758B CN202010059070.XA CN202010059070A CN111309758B CN 111309758 B CN111309758 B CN 111309758B CN 202010059070 A CN202010059070 A CN 202010059070A CN 111309758 B CN111309758 B CN 111309758B
- Authority
- CN
- China
- Prior art keywords
- interface
- data record
- user
- identification
- charging
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 45
- 238000013524 data verification Methods 0.000 title claims abstract description 15
- 238000012545 processing Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 12
- 238000010606 normalization Methods 0.000 claims description 6
- 238000012795 verification Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000010586 diagram Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 238000004573 interface analysis Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000737 periodic effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computational Linguistics (AREA)
- Telephonic Communication Services (AREA)
- Meter Arrangements (AREA)
Abstract
The embodiment of the invention discloses a charging data verification comparison method and a device, wherein the method comprises the following steps: acquiring user charging information and sorting the user charging information into charging data records; acquiring an interface call log and sorting the interface call log into an interface call data record; the charging data record and the interface call data record are in the same data format; and comparing the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record. According to the embodiment of the invention, according to the user identification and the interface identification of the called interface, the charging data in the database and the interface call log of the cloud are compared, and the accuracy of the user charging data is confirmed through comparison, so that the charging data and the actual interface call data can be checked again, the accuracy of the charging data is ensured, the charging requirement of a system is met, the charging data is more accurate, and the user experience is greatly improved.
Description
Technical Field
The invention relates to the technical field of computers and networks, in particular to a method and a device for verifying and comparing charging data.
Background
Along with the continuous development of computer technology, scientific and technological achievements brought by the method are integrated into the aspects of life of people, and bring convenience to life of people. The "Tianyan view" is a outstanding one in this aspect, and is based on government public data, combined with exclusive graph database technology and world leading computer language learning capability, on-line provides software and a platform for information of more than 1.8 hundred million domestic social entities and more than 90 data dimensions nationally, which not only covers the angles of enterprise background, actual control person, external investment, financing history, stock right structure, legal litigation and the like, but also can monitor the change of the multidimensional of the concerned enterprise in real time. "Tianyan" addresses a wide range of business security needs in an open manner with published data.
The open platform for the data of the sky eye examination is a billing platform for the management and the interface of the order of the clients of the sky eye examination, has a large number of clients of enterprises and individuals, and has hundreds of millions of call volumes every day. In order to ensure correct charging of clients, not only is the processing verification carried out on the charging log needed, but also the real-time or regular arrangement and transfer of charging data are needed.
In order to ensure correct charging of clients, the charging data needs to be verified and compared while the charging log is processed and checked. In the prior art, the verification and comparison method of charging cannot meet the verification of a large amount of practical user charging data, and a new scheme for verifying and comparing the charging data is needed.
Disclosure of Invention
One technical problem to be solved by the embodiment of the invention is as follows: the method and the device for verifying and comparing the charging data solve the problem that in the prior art, the charging data is inaccurate due to the fact that errors are easy to occur in a charging data verification link.
According to an aspect of the present invention, there is provided a charging data verification comparison method, the method comprising:
acquiring user charging information and sorting the user charging information into charging data records;
acquiring an interface call log and sorting the interface call log into an interface call data record; the charging data record and the interface call data record are in the same data format;
and comparing the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record.
Preferably, the obtaining the interface call log and sorting the interface call log into the interface call data record includes:
acquiring the interface call log;
acquiring all records associated with the user identification and the interface identification in the interface call log according to the user identification and the interface identification;
and saving the record as an interface call data record.
Preferably, the method further comprises:
according to the user identification and the interface identification, declaring a temporary association container;
determining whether the record in the interface call log contains the user identifier and the interface identifier one by one; placing a record containing the user identification and the interface identification into the temporary association container;
traversing the interface call log until all records containing the user identification and the interface identification are obtained.
Preferably, the comparing the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record includes:
acquiring data records associated with the user identification and the interface identification from the charging data record and the interface calling data record respectively according to the user identification and the interface identification associated key value;
and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values.
Preferably, the method further comprises:
and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values at regular time.
According to another aspect of the present invention, there is provided a billing data verification and comparison apparatus including:
the normalization unit is used for acquiring user charging information and collating the user charging information into a charging data record; acquiring an interface call log and sorting the interface call log into an interface call data record; the charging data record and the interface call data record are in the same data format;
and the comparison unit is used for comparing the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record.
Preferably, the normalization unit specifically includes an interface call data processing subunit, configured to:
acquiring the interface call log; acquiring all records associated with the user identification and the interface identification in the interface call log according to the user identification and the interface identification; and saving the record as an interface call data record.
Preferably, the interface invokes the data processing subunit, and is further configured to:
according to the user identification and the interface identification, declaring a temporary association container; determining whether the record in the interface call log contains the user identifier and the interface identifier one by one; placing a record containing the user identifier and the interface identifier into the temporary association container; traversing the interface call log until all records containing the user identification and the interface identification are obtained.
Preferably, the comparing unit is further configured to:
acquiring data records associated with the user identification and the interface identification from the charging data record and the interface calling data record respectively according to the user identification and the interface identification associated key value;
and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values.
Preferably, the comparing unit is further configured to:
and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values at regular time.
According to another aspect of the present invention, there is provided an electronic apparatus including:
a memory for storing a computer program;
and a processor for executing the computer program stored in the memory, and when the computer program is executed, implementing any of the methods described above.
According to another aspect of the present invention, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements any of the methods described above.
Based on the charging data verification and comparison scheme provided by the embodiment of the invention, the charging information of the user is obtained and is arranged into the charging data record; acquiring an interface call log and sorting the interface call log into an interface call data record; the charging data record and the interface call data record are in the same data format; and comparing the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record. According to the embodiment of the invention, according to the user identification and the interface identification of the called interface, the charging data in the database and the interface call log of the cloud are compared, and the accuracy of the user charging data is confirmed through comparison, so that the charging data and the actual interface call data can be checked again, the accuracy of the charging data is ensured, the charging requirement of a system is met, the charging data is more accurate, and the user experience is greatly improved.
The technical scheme of the invention is further described in detail through the drawings and the embodiments.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the invention and together with the description, serve to explain the principles of the invention.
Meanwhile, it should be understood that the sizes of the respective parts shown in the drawings are not drawn in actual scale for convenience of description.
The invention may be more clearly understood from the following detailed description taken in conjunction with the accompanying drawings, in which:
fig. 1 is a schematic flow chart of a charging data verification comparison method according to an embodiment of the present invention.
Fig. 2 is a schematic diagram of a charging data verification and comparison device according to an embodiment of the present invention.
Detailed Description
Various exemplary embodiments of the present invention will now be described in detail with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present invention unless it is specifically stated otherwise.
The following description of at least one exemplary embodiment is merely exemplary in nature and is in no way intended to limit the invention, its application, or uses.
As shown in fig. 1, a schematic flow chart of a charging data verification comparison method according to the present embodiment is provided, wherein,
step 11, obtaining user charging information and sorting the user charging information into charging data records; acquiring an interface call log and sorting the interface call log into an interface call data record; the charging data record and the interface call data record are in the same data format.
The processing of the user charging information or the interface call log aims at processing the user charging information and the interface call log into the same format and then carrying out verification comparison. The two are processed into the same format, and one of the data can be processed into the other data, or the two can be processed into the other data format.
The interface call log may be processed into the same data format as the user billing information in the billing database. Or the user identifier and the interface identifier are used as key values, and corresponding data are respectively obtained from the charging data record and the calling data record; and comparing the acquired data.
Acquiring the interface call log; acquiring all records associated with the user identification and the interface identification in the interface call log according to the user identification and the interface identification; and storing the record into the same data format as the user charging information.
According to the user identification and the interface identification, declaring a temporary association container; comparing records in the interface call log one by one, and placing the records containing the user identifier and the interface identifier into the temporary association container; and traversing the interface call log until the record comparison between the user identification and the interface identification is completed. Records that do not contain the user identification and interface identification are additionally declared temporary association containers.
Acquiring the user charging information stored in a charging database and the interface call log stored in a cloud; and according to the user identification and the interface identification, sorting the user charging information and the interface call log respectively to obtain a data record taking the user identification and the interface identification as key values.
And step 12, comparing the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record.
In one embodiment of the present invention, the corresponding data records may be obtained from the charging data record and the calling data record, respectively, according to the user identifier and the interface identifier, and then compared.
In one embodiment of the present invention, the data records with the user identifier and the interface identifier as key values may be compared at regular time. For example, it may be performed in the early morning hours.
In the embodiment, the user charging information and the interface call log are arranged into the charging data record and the call data record with the same format; and comparing the data in the charging data record and the calling data record according to the user identification and the interface identification. According to the embodiment of the invention, according to the user identification and the interface identification of the called interface, the charging data in the database and the interface call log of the cloud are compared, and the accuracy of the user charging data is confirmed through comparison, so that the charging data and the actual interface call data can be checked again, the accuracy of the charging data is ensured, the charging requirement of a system is met, the charging data is more accurate, and the user experience is greatly improved.
In one embodiment of the present invention, the user charging data is stored in a charging database, which may be a local database or a cloud database. The interface call log can be a record of each interface call data, can be stored in a local database, and can also be stored in a cloud server in real time.
The interface call log can be stored in a special log server provided by the cloud server, and the SDK call is called through the special interface provided by the cloud server, and only a fixed log format is provided. For example, the ali cloud log server may access the SDK of the ali cloud through JAVA codes and Maven, and provide a log interface through the ali cloud to obtain log data provided by the ali cloud log server, that is, the interface call log in this embodiment. The log file output by the Arian cloud log server has a special table structure, and the log file needs to be processed before specific log data can be obtained.
In one embodiment of the present invention, obtaining an interface call log and sorting the interface call log into an interface call data record may specifically include:
acquiring the interface call log;
acquiring all records associated with the user identification and the interface identification in the interface call log according to the user identification and the interface identification;
and saving the record as an interface call data record.
In one embodiment of the present invention, a specific data conversion method of an interface call log may include:
according to the user identification and the interface identification, declaring a temporary association container;
determining whether the record in the interface call log contains the user identifier and the interface identifier one by one; placing a record containing the user identification and the interface identification into the temporary association container;
traversing the interface call log until all records containing the user identification and the interface identification are obtained.
In one embodiment of the present invention, comparing the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record includes:
acquiring data records associated with the user identification and the interface identification from the charging data record and the interface calling data record respectively according to the user identification and the interface identification associated key value;
and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values.
And the charging data record and the interface call data record can be compared by taking the user identifier and the interface identifier as key values at regular time.
In one embodiment of the present invention, a specific charging data verification and comparison process is as follows:
the solution of this embodiment can be divided into three main steps.
The first step: and buffering before the periodic processing, carrying out charging metering processing according to the user identification, the interface ID, the order ID and the like, and storing the consumption record of the user into a database.
And a second step of: and storing the call interface engineering log according to the format of the call interface engineering log, and placing the call interface engineering log in an Arian log service.
And a third step of: the interface engineering log is compared with the database log.
The specific verification and comparison process is as follows:
SDK of the Arian cloud is introduced through JAVA codes and Maven, a log interface is provided through the Arian cloud to call an interface analysis function, SQL is matched, and a required log format is obtained.
The processing procedure of the interface call log of the cloud is as follows:
the log (log) is obtained using JAVA and then taken to a log table (logContent). And integrating the cloud logs one by one into one piece of data according to the fact that a user key (token) and an interface unique identifier (url) are the same. By traversing the logContent, a key value (key) and a value (value) in the content model are acquired. For example
{
url:service_Interface_One,
token:23122edqwdq213nhkad，
Status:0，
Num: number of call interfaces
}
The specific explanation is as follows:
a temporary association container (map) is declared, a user key (token) and an interface unique identifier (url) are used as key values, and the key values are put into the map to convert the content model into the map format.
A intra-method log association container (logMap) is declared, and it is determined whether there is a value in the logMap that is key with token_url in the current map.
If not, a temporary state association container (status map) is declared, and the current data class and quantity is placed.
For example: status map.put (map.get ("status"). ToString ()), map.get ("num"). ToString (); the current log data is then put into a status map with token_url as a key.
If present, declaring a temporary variable (tmpMap), obtaining the current value of token_url as key and assigning tmpMap, putting the current data class and quantity into tmpMap. Put (map. Get ("status"). ToString ()), map. Get ("num"). ToString ()); then put a status map into the logMap with token_url as key.
And outputting logMap, and processing the log into a Map form.
logMap:{
token_url：{status:num},
token_url：{status:num}
}
For example:
logMap:{23122edqwdq213nhkad_service_Interface_One:{
0:10000,
1:20000
}，
11111111_service_Interface_Two:{
0:10000
}
}
the Token is a key of the user and a unique identifier of the user. Url interface URL, interface unique identification. Status 0 indicates no data, 1 indicates data, 2 indicates abnormal data, and 3 indicates a charging basis. Num: number of call interfaces.
Further, user charging information in the charging database is arranged. The method comprises the following steps:
the charging database log is taken out through Java codes and then is arranged into a Map form token_url: { status: num }. For example:
23122edqwdq213nhkad_service_Interface_One:{
url:service_Interface_One,
token:23122edqwdq213nhkad，
fId:1,
fName interface 1,
orgId:3083,
orgName-the user,
AutId:1,
dataCount:100,
exdataCount:100,
noDataCount:100
}。
further, the log is aligned.
Timing tasks may be used: and executing the task, acquiring an Arian cloud log and a database log, and arranging the Arian cloud log and the database log into corresponding formats.
The logMap of the log is converted into a Set, the logMap is traversed, all records (entry) of the logMap are obtained, and then the key is obtained. The value of the same key of the database dataBaseMap is taken and converted into the value map through jsonob object. For example:
23122edqwdq213nhkad_service_Interface_One:{
url:service_Interface_One,
token:23122edqwdq213nhkad，
fId:1,
fName interface 1,
orgId:3083,
orgName-the user,
AutId:1,
dataCount:100,
exdataCount:100,
noDataCount:100
}
this Map is stored in the object logModel. And obtaining a value status map of the logMap, converting the value status map into a Set, obtaining a status entry, traversing the status entry, and matching corresponding values according to keys.
case"0":
logModel.setNoAuthCount(Integer.parseInt(statusEntry.getValue()))；
break；
case"1":
logModel.setDataMinus(logModel.getDataCount()-Integer.parseInt(statusEntry.getValue()))；
break；
case"2":
logModel.setNoDataMinus(logModel.getNoDataCount()-Integer.parseInt(statusEntry.getValue()))；
break；
case"3":
logModel.setExMinus(logModel.getExCount()-Integer.parseInt(statusEntry.getValue()))；
After the process is completed, it is checked whether there is a difference in the data of the user. If the difference exists, the related difference is reported, otherwise, the data verification is considered to be correct.
As shown in fig. 2, a device for verifying and comparing charging data according to an embodiment of the present invention includes,
a normalization unit 21, configured to obtain user charging information and sort the user charging information into a charging data record; acquiring an interface call log and sorting the interface call log into an interface call data record; the charging data record and the interface call data record are in the same data format;
and the comparison unit 22 is configured to compare the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record.
Specifically, the normalization unit 21 specifically includes an interface call data processing subunit 211, configured to obtain the interface call log; acquiring all records associated with the user identification and the interface identification in the interface call log according to the user identification and the interface identification; and saving the record as an interface call data record.
Specifically, the interface call data processing subunit 211 is further configured to declare a temporary association container according to the user identifier and the interface identifier; determining whether the record in the interface call log contains the user identifier and the interface identifier one by one; placing a record containing the user identifier and the interface identifier into the temporary association container; traversing the interface call log until all records containing the user identification and the interface identification are obtained.
Specifically, the comparing unit 22 is further configured to
Acquiring data records associated with the user identification and the interface identification from the charging data record and the interface calling data record respectively according to the user identification and the interface identification associated key value;
and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values.
Specifically, the comparing unit 22 is further configured to compare the charging data record and the interface call data record with the user identifier and the interface identifier as key values at regular time.
The embodiment of the invention also provides electronic equipment, which comprises:
a memory for storing a computer program;
and a processor for executing the computer program stored in the memory, and when the computer program is executed, implementing the method according to any one of the above embodiments.
The embodiment of the invention also provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements the method according to any of the embodiments above.
Based on the charging data verification and comparison scheme provided by the embodiment of the invention, the charging information of the user is obtained and is arranged into the charging data record; acquiring an interface call log and sorting the interface call log into an interface call data record; the charging data record and the interface call data record are in the same data format; and comparing the data in the charging data record and the interface call data record according to the user identifier and the interface identifier in the charging data record and the interface call data record. According to the embodiment of the invention, according to the user identification and the interface identification of the called interface, the charging data in the database and the interface call log of the cloud are compared, and the accuracy of the user charging data is confirmed through comparison, so that the charging data and the actual interface call data can be checked again, the accuracy of the charging data is ensured, the charging requirement of a system is met, the charging data is more accurate, and the user experience is greatly improved.
Techniques, methods, and apparatus known to one of ordinary skill in the relevant art may not be discussed in detail, but are intended to be part of the specification where appropriate.
It should be noted that: like reference numerals and letters denote like items in the following figures, and thus once an item is defined in one figure, no further discussion thereof is necessary in subsequent figures.
Those of ordinary skill in the art will appreciate that: all or part of the steps for implementing the above method embodiments may be implemented by hardware associated with program instructions, where the foregoing program may be stored in a computer readable storage medium, and when executed, the program performs steps including the above method embodiments; and the aforementioned storage medium includes: various media that can store program code, such as ROM, RAM, magnetic or optical disks.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described in a different manner from other embodiments, so that the same or similar parts between the embodiments are mutually referred to. For system embodiments, the description is relatively simple as it essentially corresponds to method embodiments, and reference should be made to the description of method embodiments for relevant points.
The method and apparatus of the present invention may be implemented in a number of ways. For example, the methods and apparatus of the present invention may be implemented by software, hardware, firmware, or any combination of software, hardware, firmware. The above-described sequence of steps for the method is for illustration only, and the steps of the method of the present invention are not limited to the sequence specifically described above unless specifically stated otherwise. Furthermore, in some embodiments, the present invention may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present invention. Thus, the present invention also covers a recording medium storing a program for executing the method according to the present invention.
The description of the present invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art. The embodiments were chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.
Claims (8)
1. A method for charging data verification comparison, the method comprising:
acquiring user charging information and sorting the user charging information into charging data records;
acquiring an interface call log; acquiring all records associated with the user identification and the interface identification in the interface call log according to the user identification and the interface identification; saving the record as an interface call data record; the charging data record and the interface call data record are in the same data format;
acquiring data records associated with the user identification and the interface identification from the charging data record and the interface calling data record respectively according to the user identification and the interface identification associated key value; and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values.
2. The method of claim 1, wherein the method further comprises:
according to the user identification and the interface identification, declaring a temporary association container;
determining whether the record in the interface call log contains the user identifier and the interface identifier one by one; placing a record containing the user identification and the interface identification into the temporary association container;
traversing the interface call log until all records containing the user identification and the interface identification are obtained.
3. The method of claim 1, wherein the method further comprises:
and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values at regular time.
4. A billing data verification and comparison apparatus, comprising:
the normalization unit is used for acquiring user charging information and collating the user charging information into a charging data record; acquiring an interface call log and sorting the interface call log into an interface call data record; the charging data record and the interface call data record are in the same data format;
the comparison unit is used for acquiring data records associated with the user identifier and the interface identifier from the charging data record and the interface calling data record respectively according to the user identifier and the interface identifier associated key value; the user identification and the interface identification are used as key values, and the charging data record and the interface calling data record are compared;
the normalization unit comprises an interface call data processing subunit, and the interface call data processing subunit is used for acquiring the interface call log; acquiring all records associated with the user identification and the interface identification in the interface call log according to the user identification and the interface identification; and saving the record as an interface call data record.
5. The apparatus of claim 4, wherein the interface invokes a data processing subunit further to:
according to the user identification and the interface identification, declaring a temporary association container; determining whether the record in the interface call log contains the user identifier and the interface identifier one by one; placing a record containing the user identification and the interface identification into the temporary association container; traversing the interface call log until all records containing the user identification and the interface identification are obtained.
6. The apparatus of claim 4, wherein the alignment unit is further configured to:
and comparing the charging data record with the interface call data record by taking the user identifier and the interface identifier as key values at regular time.
7. An electronic device, comprising:
a memory for storing a computer program;
a processor for executing a computer program stored in said memory, and which, when executed, implements the method of any of the preceding claims 1-3.
8. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of any of the preceding claims 1-3.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010059070.XA CN111309758B (en) | 2020-01-19 | 2020-01-19 | Charging data verification comparison method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010059070.XA CN111309758B (en) | 2020-01-19 | 2020-01-19 | Charging data verification comparison method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111309758A CN111309758A (en) | 2020-06-19 |
| CN111309758B true CN111309758B (en) | 2024-02-13 |
Family
ID=71148855
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010059070.XA Active CN111309758B (en) | 2020-01-19 | 2020-01-19 | Charging data verification comparison method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111309758B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113517989B (en) * | 2021-09-14 | 2021-12-17 | 浙江九州云信息科技有限公司 | Resource charging method and device for IaaS cloud platform |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101827346A (en) * | 2009-03-04 | 2010-09-08 | 中国移动通信集团上海有限公司 | Automatic test method and device for charge system |
| CN103650416A (en) * | 2012-06-27 | 2014-03-19 | 华为技术有限公司 | Billing management method and device |
| CN104144400A (en) * | 2013-05-10 | 2014-11-12 | 中国电信股份有限公司 | Online application charging method and system |
| CN108366176A (en) * | 2018-01-25 | 2018-08-03 | 网宿科技股份有限公司 | A kind of charging method of terminal applies, apparatus and system |
| CN108805632A (en) * | 2018-05-07 | 2018-11-13 | 北京京东尚科信息技术有限公司 | A kind of charging method and device |
| CN110110516A (en) * | 2019-01-04 | 2019-08-09 | 北京车和家信息技术有限公司 | Log recording method, apparatus and system |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8135636B2 (en) * | 2003-11-25 | 2012-03-13 | International Business Machines Corporation | System for metering in an on-demand utility environment |
| US8589510B2 (en) * | 2008-09-05 | 2013-11-19 | Paul Alexander Jackson | Method and system of synchronizing accounting objects between a client and server |
| EP2987293A1 (en) * | 2013-04-03 | 2016-02-24 | Telefonaktiebolaget LM Ericsson (publ) | A method of and a device handling charging data in an ip-based network |
| US20150254740A1 (en) * | 2014-03-06 | 2015-09-10 | International Business Machines Corporation | Non-Intrusive Cloud Services Billing |
-
2020
- 2020-01-19 CN CN202010059070.XA patent/CN111309758B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101827346A (en) * | 2009-03-04 | 2010-09-08 | 中国移动通信集团上海有限公司 | Automatic test method and device for charge system |
| CN103650416A (en) * | 2012-06-27 | 2014-03-19 | 华为技术有限公司 | Billing management method and device |
| CN104144400A (en) * | 2013-05-10 | 2014-11-12 | 中国电信股份有限公司 | Online application charging method and system |
| CN108366176A (en) * | 2018-01-25 | 2018-08-03 | 网宿科技股份有限公司 | A kind of charging method of terminal applies, apparatus and system |
| CN108805632A (en) * | 2018-05-07 | 2018-11-13 | 北京京东尚科信息技术有限公司 | A kind of charging method and device |
| CN110110516A (en) * | 2019-01-04 | 2019-08-09 | 北京车和家信息技术有限公司 | Log recording method, apparatus and system |
Non-Patent Citations (2)
| Title |
|---|
| 王建辉 ; 李涛 ; .基于Hive的支付SDK日志分析系统的设计研究.计算机应用与软件.2017,(07),全文. * |
| 黄淼 ; 徐向艺 ; 马丽 ; .基于Open Lab的电信计费数据采集系统开发.电子设计工程.2015,(16),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111309758A (en) | 2020-06-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109522746B (en) | A data processing method, electronic device and computer storage medium | |
| US9280569B2 (en) | Schema matching for data migration | |
| CN110383319A (en) | Large scale scale heterogeneous data intake and user's parsing | |
| US20090030754A1 (en) | Methods, systems and computer software utilizing xbrl to identify, capture, array, manage, transmit and display documents and data in litigation preparation, trial and regulatory filings and regulatory compliance | |
| CN111383101A (en) | Post-loan risk monitoring method, device, equipment and computer-readable storage medium | |
| WO2020082673A1 (en) | Invoice inspection method and apparatus, computing device and storage medium | |
| CN115526605A (en) | Enterprise internal control management-based approval method and system | |
| CN111309758B (en) | Charging data verification comparison method and device | |
| CN116166641A (en) | Mapping method, device, equipment and medium for data model and data standard | |
| WO2021000645A1 (en) | Contract generation method and apparatus based on data crawling and computer device | |
| CN109947797B (en) | Data inspection device and method | |
| CN112860722A (en) | Data checking method and device, electronic equipment and readable storage medium | |
| CN115982429B (en) | Knowledge management method and system based on flow control | |
| CN114491184B (en) | Data processing method and device, storage medium and electronic equipment | |
| CN116739602A (en) | Suspicious electronic bill prediction method based on multi-model fusion | |
| JP2020150509A (en) | Digital Evidence Management Method and Digital Evidence Management System | |
| CN111414427B (en) | A data processing method and device suitable for quasi-real-time service | |
| CN109785099B (en) | Method and system for automatically processing service data information | |
| US11256708B2 (en) | Method of creating process protocols | |
| CN114925050A (en) | Data verification method and device based on knowledge base, electronic equipment and storage medium | |
| CN112395292A (en) | Data feature extraction and matching method and device | |
| CN111695870A (en) | Project process management system | |
| CN112200655B (en) | Application review method, device, electronic device and storage medium | |
| US11941004B1 (en) | System and method for executing database operations based on a policy | |
| Pan et al. | Data checking method of intelligent warehouse data inventory based on digital filtering and correlation analysis |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |