Data statistical method, device, equipment and storage medium

Abstract

This application discloses a data statistics method, apparatus, device, and storage medium, relating to the field of computer technology. The method includes sending a first anonymity statistical query request to multiple queried parties in an anonymity alliance; receiving statistical query results from the queried parties, including a first zero-sum random number, where the first zero-sum random number is the negative sum of all second zero-sum random numbers within the service period of the queried party; and determining the hit statistics of the queried parties based on the statistical query results and the anonymity query results of the queried parties. By adding a first zero-sum random number and binding it to the second zero-sum random numbers related to the zero-sum ring of a single query, the reliability of the specific hit situation of the queried parties can be guaranteed. By canceling the second zero-sum random numbers in the anonymity query results of a single query using the first zero-sum random number in the statistical combination result, accurate hit statistics of the queried parties can be obtained.

Description

Technical Field

[0001] This application belongs to the field of computer technology, and in particular relates to a data statistics method, apparatus, device and storage medium. Background Technology

[0002] Anonymous querying refers to a privacy-preserving computing technology that obtains query results from the queried party without revealing the original search criteria of the querying party. A typical application scenario for anonymous queries is risk information sharing, where multiple organizations with risk information form an anonymity alliance to provide a unified anonymous risk information query service to the public.

[0003] To ensure privacy, the queried parties in the Anonymous Alliance obfuscate the local hit rate of the query data (e.g., a hit of 1 and a miss of 0) and then report the obfuscated results to the coordinator. Because of this anonymity query technology, the coordinator cannot know the specific hit rate of the query data on each queried party. Summary of the Invention

[0004] This application provides a data statistics method, apparatus, device, and storage medium that can solve the problem of not being able to know the specific hit rate of query data in each queried party.

[0005] In a first aspect, embodiments of this application provide a data statistics method applied to a coordinating party, which may include:

[0006] Send the first stealth statistics query request to multiple queried parties in the stealth alliance;

[0007] Receive statistical query results sent by the queried party. The statistical query results include a first zero-sum random number, which is the negative sum of all second zero-sum random numbers of the queried party within the service period.

[0008] Based on the statistical query results and the anonymous query results of the queried party, determine the hit statistics of the queried party.

[0009] Secondly, embodiments of this application provide a data statistics method applied to the queried party in an anonymity alliance. This method may include:

[0010] Receive the first stealth statistics query request sent by the coordinator;

[0011] Based on the first cloaking statistics query request, the sum of the negative numbers of the second zero-sum random numbers of the queried party within the service period is determined as the first zero-sum random number;

[0012] Send the statistical query results to the coordinator. The statistical query results include the first zero and a random number.

[0013] Thirdly, embodiments of this application provide a data statistics device applied to a coordinating party, which may include:

[0014] The sending module is used to send the first cloaking statistics query request to multiple queried parties in the cloaking alliance;

[0015] The receiving module is used to receive the statistical query results sent by the queried party. The statistical query results include a first zero and a random number, which is the negative sum of all the second zero and random numbers sent by the queried party within the service period.

[0016] The determination module is used to determine the hit statistics of the queried party based on the statistical query results and the anonymous query results of the queried party.

[0017] Fourthly, embodiments of this application provide a data statistics device applied to the queried party in an anonymity alliance. This device may include:

[0018] The receiving module is used to receive the first stealth statistics query request sent by the coordinator;

[0019] The acquisition module is used to determine the first zero-sum random number as the sum of the negative numbers of all second zero-sum random numbers of the queried party within the service period, based on the first cloaking statistics query request.

[0020] The sending module is used to send statistical query results to the coordinator. The statistical query results include the first zero and a random number.

[0021] Fifthly, embodiments of this application provide a computer device, which includes: a processor and a memory storing computer program instructions;

[0022] When the processor executes computer program instructions, it implements the data statistics method as shown in the first aspect or the data statistics method as shown in the second aspect.

[0023] In a sixth aspect, embodiments of this application provide a computer storage medium storing computer program instructions. When the computer program instructions are executed by a processor, they implement the data statistics method as shown in the first aspect or the data statistics method as shown in the second aspect.

[0024] In a seventh aspect, embodiments of this application provide a chip, which includes a processor and a communication interface. The communication interface and the processor are coupled together. The processor is used to run programs or instructions to implement the data statistics method as shown in the first aspect or the data statistics method as shown in the second aspect.

[0025] Eighthly, embodiments of this application provide a computer program product stored in a storage medium, which is executed by at least one processor to implement the data statistics method as shown in the first aspect or the data statistics method as shown in the second aspect.

[0026] The data statistics method, apparatus, device, and storage medium of this application embodiment send a first anonymity statistical query request to multiple queried parties in an anonymity alliance; receive statistical query results sent by the queried parties, the statistical query results including a first zero-sum random number, which is the negative sum of all second zero-sum random numbers of the queried party within the service period; and determine the hit statistics of the queried parties based on the statistical query results and the anonymity query results of the queried parties. Thus, for the hit statistics scenario, a new first zero-sum random number is added and bound to the second zero-sum random number related to the zero-sum ring of a single query, ensuring the reliability of the specific hit situation of the queried parties. Furthermore, by using the first zero-sum random number in the statistical combination result to cancel out the second zero-sum random number in the anonymity query result of a single query, the hit statistics of the queried parties are obtained. Therefore, it is not necessary for each queried party to report its own hit statistics; the specific hit situation of each queried party can be known without the need for each queried party to report its own hit statistics. Attached Figure Description

[0027] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0028] Figure 1 This is a schematic diagram of a data statistics system according to an embodiment of the data statistics method provided in this application;

[0029] Figure 2 This is a flowchart of a data statistics method according to an embodiment of the data statistics method provided in this application;

[0030] Figure 3 This is a flowchart of a data statistics method according to an embodiment of the data statistics method provided in this application;

[0031] Figure 4 This is a schematic diagram of a target period according to an embodiment of the data statistics method provided in this application;

[0032] Figure 5 This is a schematic diagram of data statistics interaction according to an embodiment of the data statistics method provided in this application;

[0033] Figure 6 This is a schematic diagram of the structure of a data statistics device provided in one embodiment of this application;

[0034] Figure 7 This is a schematic diagram of the structure of a data statistics device provided in one embodiment of this application;

[0035] Figure 8 This is a schematic diagram of the structure of a computer device provided in one embodiment of this application. Detailed Implementation

[0036] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0037] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0038] The acquisition, storage, use, and processing of data (including but not limited to features and information mentioned in this document) in the technical solution of this application all comply with the relevant provisions of national laws and regulations.

[0039] The coordinating service provider actively built a risk information sharing platform for all parties involved, achieving positive application results. In recent years, with increasingly stringent data regulations requiring financial institutions to comply with data security and personal information protection requirements, multiple systems have mandated that financial institutions strengthen the security of shared risk information. Against this backdrop, a risk intelligence analysis and early warning system based on anonymized query-based risk information sharing has emerged. To incentivize financial institutions to provide data, the service provider offers a contribution-based scheme, calculating the contribution of each financial institution's data contribution to provide services. Hit rate statistics are a crucial factor in the contribution calculation. Due to the use of anonymized query technology, the coordinating party cannot know the specific hit rate of the queried data across each queried party. Although each queried party can periodically report its specific hit rate, in the event of false or misleading reports, the coordinating party cannot verify the reported hit rate of each queried party, thus failing to guarantee the authenticity of the hit rate data.

[0040] To address the issue of not being able to know or accurately know the specific hit rate of query data in each queried party in privacy computing anonymous data sharing scenarios, this application provides a data statistics method, apparatus, device, and storage medium. For the hit rate statistics dimension, a first zero-sum random number is added and bound to a second zero-sum random number related to the zero-sum ring of a single query. This ensures the credibility of the specific hit rate of the queried party. Furthermore, by statistically combining the first zero-sum random number in the result and canceling out the second zero-sum random number in the anonymous query result of a single query, the hit rate statistics of the queried party are obtained. Therefore, it is not necessary for each queried party to report its own hit rate statistics individually; the specific hit rate of each queried party can be accurately known.

[0041] The following will be combined with the appendix Figures 1 to 8 This application describes in detail the data statistics methods, apparatus, computer equipment, and storage media of the embodiments thereof. It should be noted that these embodiments are not intended to limit the scope of this application.

[0042] First, the data statistics system of the data statistics method provided in the embodiments of this application will be described.

[0043] like Figure 1As shown, the data statistics system includes a querying party 101, a coordinating party 102, and an anonymity alliance. The anonymity alliance may include multiple queryees 103, such as queryees 1 to 4. Specifically, the coordinating party 102 establishes a communication connection between the querying party 101 and the queryees 103. In this embodiment, the querying party 101 can be an internet system, the queryee can be a financial institution, and the coordinating party 102 can be a system with privacy computing technology, used to provide anonymity query services.

[0044] The following sections will provide a detailed explanation of each module in its data statistics system.

[0045] The query party 101 is used to anonymize the original data to be queried using the same anonymization algorithm as the Anonymity Consortium, and then sends a second anonymity statistics query request to the coordinator 102.

[0046] Coordinator 102 is used to send a first anonymity statistics query request to multiple queried parties in the anonymity alliance. In this embodiment of the application, the first anonymity statistics query request may be determined based on a second anonymity statistics query request, or it may be generated by coordinator 102 itself based on service requirements.

[0047] In some embodiments of this application, if the first stealth statistics query request is generated by the coordinator 102 itself based on service requirements, the first stealth statistics query request may carry the service period information of the hit statistics data that the coordinator 102 wants to query. In this case, the first stealth statistics query request may be a request specifically for querying the hit statistics data of the queried party. Based on this, the coordinator 102 may send the first stealth statistics query request of the service period information of the first service period to multiple queried parties in the stealth alliance.

[0048] In some other embodiments of this application, the first anonymity statistics query request is determined by the first anonymity statistics query request. In this case, since the information carried in the second anonymity statistics query request is different, the function of the second anonymity statistics query request is also different. Based on this, when the coordinator 102 receives the second anonymity statistics query request, it can identify whether the second anonymity statistics query request is the first query in the current service period, so as to determine the function of the first anonymity statistics query request. The following will describe them separately.

[0049] In some embodiments, the second anonymity statistics query request may carry the original, de-identified data to be queried. In this case, the second anonymity statistics query request may be a request not specifically for querying the hit statistics of the queried party, that is, a request from the querying party 101 to query the anonymity query results corresponding to the original data to be queried.

[0050] Based on this, coordinator 102 needs to determine whether the second cloaking statistics query request is the first query within the current service period.

[0051] When the second anonymous statistical query request is the first query within a new service period, the first anonymous statistical query request is not only a request to query the anonymous query results corresponding to the data to be queried, but also a request to query the hit statistics of the queried party within the second service period. In this case, the first anonymous statistical query request may carry the original data to be queried and the statistical fields in the second anonymous statistical query request. The statistical fields are used to indicate the start of the statistical process for the hit statistics of the queried party.

[0052] If the second anonymous statistical query request is a non-first query within a new service cycle, the first anonymous statistical query request is only used to query the anonymous query results corresponding to the data to be queried. In this case, the first anonymous statistical query request may carry the original data to be queried in the first anonymous statistical query request.

[0053] Based on the three different situations mentioned above, the content included in the statistical query results is also different. The coordinator 102 also handles the statistical query results corresponding to different first-anonymous statistical query requests in different ways, as shown below.

[0054] In some embodiments, when the first anonymous statistical query request is specifically for querying the hit statistics of the queried party, the statistical query result may only include a first zero and a random number. In this case, the coordinator 102 can be used to summarize the hit data of each query of the queried party within the first service period and the second zero and random number used to obfuscate the hit data of each query to obtain the summary query result of the queried party within the first service period; and use the first zero and random number in the statistical query result to cancel out the zero and random number in the summary query result to obtain the hit statistics of the queried party within the first service period.

[0055] In other embodiments, when the first anonymity statistical query request is a request to query the anonymity query results corresponding to the data to be queried and the hit statistics of the queried party within the second service period, the statistical query results, in addition to including the first zero and random number, also include the hit data queried when the queried party first executes the query task in the current service period. In this case, the coordinator 102 can be used to summarize the statistical query results and the anonymity query results of the queried party, so as to offset the second zero and random number in the anonymity query results used to obfuscate the hit data of each query within the historical service period using the first zero and random number in the statistical query results, thereby obtaining the hit statistics of the queried party within the second service period; wherein, the second service period is a period consisting of the historical service period and the target time period, and the target time period is the time period from the start time of the current service period to the time of receiving the second anonymity statistical query request. The coordinator 102 can also be used to retain the hit statistics of the queried party within the second service period and send the hit data queried when the queried party first executes the query task in the current service period to the querying party 101.

[0056] In some other embodiments, when the first anonymous statistical query request is a request to query the anonymous query results corresponding to the data to be queried, the statistical query results will include the hit data found when the queried party first executes the query task in the current service period, that is, the hit data corresponding to the original data to be queried after anonymization. At this time, the coordinator 102 can be used to send the hit data found when the queried party first executes the query task in the current service period to the querying party 101.

[0057] The queried party 103 in the stealth alliance is used to receive the first stealth statistics query request sent by the coordinator 102. Based on the above, the actions taken to respond to the first stealth statistics query request vary depending on its purpose, as detailed below.

[0058] In some embodiments, if the first anonymity statistical query request is specifically for querying the hit statistics of the queried party, the first anonymity statistical query request carries service period information. The first anonymity statistical query request is used to request the queried party to query zero-sum random numbers within the first service period corresponding to the service period information. In this case, the queried party 103 can use the service period information to obtain each second zero-sum random number used by the queried party to obfuscate the hit data of each query within the first service period; the summation of the negative number of each second zero-sum random number within the first service period is determined as the first zero-sum random number. And send the statistical query result including only the first zero-sum random number to the coordinator 102.

[0059] In other embodiments, when the first anonymity statistics query request is a request to query the anonymity query results corresponding to the data to be queried and the hit statistics of the queried party within the second service period, the first anonymity statistics query request carries the de-identified original data to be queried and statistical fields. Based on this, the queried party 103 can use the statistical fields to obtain the second zero-sum random number used by the queried party to obfuscate the hit data of each query in the historical service period; determine the negative sum of each second zero-sum random number of the queried party in the historical service period as the first zero-sum random number; and obtain the hit data queried by the queried party when it first executes the query task in the current service period based on the de-identified original data to be queried; and obtain the statistical query results by obfuscating the hit data queried by the queried party in the current service period through the first zero-sum random number.

[0060] In some other embodiments, when the first anonymity statistical query request is a request to query the anonymity query result corresponding to the data to be queried, the first anonymity statistical query request carries the original data to be queried after desensitization. Based on this, the queried party 103 can use the original data to be queried to obtain the hit data queried when the queried party first executes the query task in the current service period; by obfuscating the hit data queried by the queried party in the current service period with zero-sum random numbers determined by multiple queried parties in the anonymity alliance through a zero-sum random algorithm, the statistical query result is obtained. At this time, the statistical query result in this embodiment can be a regular anonymity query result, and its zero-sum random number can also be regarded as the second zero-sum random number as understood above.

[0061] Therefore, for scenarios where the first anonymous statistical query request is specifically for querying the hit statistics of the queried party, i.e., the hit statistics scenario, a first zero-sum random number can be added and bound to a second zero-sum random number related to the zero-sum ring of a single query. This can ensure the credibility of the specific hit situation of the queried party. By using the first zero-sum random number in the statistical combination result to cancel out the second zero-sum random number in the anonymous query result of a single query, the hit statistics of the queried party can be obtained. Thus, it is not necessary for each queried party to report its hit statistics separately, and the specific hit situation of each queried party can be known.

[0062] For anonymous query data sharing scenarios, anonymous queries can be divided into two periodic dimensions: single query results and hit statistics. Zero-sum ring technology is applied to each dimension. Specifically, for the single anonymous query dimension, a second zero-sum random number is constructed from multiple queried parties within the anonymous alliance to obfuscate the hit data of the queried parties, ensuring the privacy of the single anonymous query while allowing the acquisition of the single query zero-sum ring by summarizing the second query results. For the hit statistics dimension, a first zero-sum random number is added to interfere with the hit data within the service period and bound to the single query zero-sum ring, ensuring the credibility of the queried party's specific hit situation. Then, the first query results, including the first zero-sum random number, are summarized with the second query results related to the single query zero-sum ring, automatically eliminating the zero-sum random number and obtaining the hit statistics for the queried parties. Therefore, it is possible to know the specific hit situation of each queried party without requiring each party to report its own hit statistics.

[0063] It should be noted that the data statistics system provided in this application embodiment can be applied to anonymous data sharing application scenarios. Privacy computing, as a key technology for data element circulation, can be applied in the financial sector, as well as in application scenarios where financial institutions, internet systems, and privacy computing technology systems conduct anonymous alliance-like collaborations.

[0064] Based on the above data statistics system, the following is combined with... Figure 2 The data statistics method provided in the embodiments of this application will be described in detail.

[0065] Figure 2 A flowchart illustrating a data statistics method provided in an embodiment of this application.

[0066] like Figure 2 As shown, this data statistics method can be applied to, for example... Figure 1 The coordinating party shown in the figure, the data collection method may specifically include the following steps:

[0067] Step 210: Send a first anonymity statistical query request to multiple queried parties in the Anonymity Alliance; Step 220: Receive the statistical query results sent by the queried parties, the statistical query results include a first zero-sum random number, the first zero-sum random number is the negative sum of all second zero-sum random numbers of the queried party within the service period; Step 230: Determine the hit statistics of the queried parties based on the statistical query results and the anonymity query results of the queried parties.

[0068] In this embodiment of the application, if the queried party has four second zero-sum random numbers within the service period, i.e., N 11 N 12 N 13 and N 14The relationship between the first zero-sum random number and the second zero-sum random number is shown in the following formula (1).

[0069] N 11 +N 12 +N 13 +N 14 +N 15 =0 (1)

[0070] The first zero and the random number can be represented by the following formula (2).

[0071] N 15＝ -N 11 -N 12 -N 13 -N 14 (2)

[0072] Based on this, the anonymous query results of the queried party in this service period are obtained. The anonymous query results include the hit data of each query by the queried party in this service period and a second zero-sum random number used to obfuscate the hit data of each query. It can be understood that the anonymous query results include the hit data of each query by the queried party in this service period after being obfuscated by the second zero-sum random number. Based on this, by statistically analyzing the first zero-sum random number in the query results, and using the principle of the above formula (1), the second zero-sum random number in the anonymous query results of the queried party in this service period can be canceled out, and the hit statistics of the queried party in this service period, i.e., 4 queries, can be obtained.

[0073] Therefore, for the hit statistics scenario, a first zero-sum random number is added and bound to a second zero-sum random number related to the zero-sum ring of a single query. This ensures the reliability of the specific hit situation of the queried party. By statistically combining the first zero-sum random number in the result and canceling out the second zero-sum random number in the anonymous query result of a single query, the hit statistics of the queried party can be obtained. Thus, it is not necessary for each queried party to report its hit statistics separately, and the specific hit situation of each queried party can be known.

[0074] The steps described above are explained in detail below.

[0075] In some embodiments of this application, the first stealth statistical query request carries service period information. The first stealth statistical query request is used to request the queried party to query a zero-sum random number within a first service period corresponding to the service period information. The service period includes the first service period. The second zero-sum random number is a zero-sum random number used by the queried party to obfuscate the hit data of each query within the first service period. The first zero-sum random number is the negative sum of all the second zero-sum random numbers within the first service period.

[0076] In this embodiment, the service period can be a preset statistical duration for calculating the hit rate of the queried party, such as 24 hours a day. Taking one day as an example, the first service period could be 24 hours from July 2nd, and the service period information could be July 2nd. In this case, the first anonymity statistical query request is used to request the queried party to query a first zero-sum random number within July 2nd. The second zero-sum random number can include a zero-sum random number used by the queried party within July 2nd to obfuscate the hit rate data for each query, i.e., N. 11 N 12 N 13 and N 14 Based on this, the first zero-sum random number within July 2nd can be obtained using the above formula (2).

[0077] Based on this, when the anonymity query results include hit data for each query by the queried party within the first service period, as well as a second zero and a random number used to obfuscate the hit data for each query, the aforementioned step of determining the hit statistics of the queried party based on the statistical query results and the anonymity query results of the queried party can specifically include:

[0078] The hit data of each query of the queried party within the first service period and the second zero and random number used to confuse the hit data of each query are summarized to obtain the summary query results of the queried party within the first service period; by statistically analyzing the first zero and random number in the query results, the zero and random number in the summary query results are canceled out to obtain the hit statistics of the queried party within the first service period.

[0079] Taking July 2nd as an example of the first service period mentioned above, July 2nd includes four anonymous query results: Anonymous Query Result 1, Anonymous Query Result 2, Anonymous Query Result 3, and Anonymous Query Result 4. Among them, Anonymous Query Result 1 includes results obtained via N... 11 The obfuscated hit data of the first query, the cloaked query result 2 includes data via N 12 The obfuscated hit data of the second query, the cloaked query result 3 includes data via N 13 The obfuscated third query hit data, the cloaked query result 4 includes data via N 14 The hit data of the obfuscated fourth query. Based on this, the results of the anonymous query 1, anonymous query 2, anonymous query 3 and anonymous query 4 are first summarized, that is, added together, to obtain the summary query result. Then, by statistically analyzing the first zero and random number in the query result, and using the principle of the above formula (1), the second zero and random number in the anonymous query result of the queried party in this service period can be canceled out, so as to obtain the summary result of the hit statistics of the queried party in this service period, that is, the four queries.

[0080] In some embodiments of this application, the first stealth statistics query request is determined by a second stealth statistics query request sent by the querying party. The second stealth statistics query request is the first request to execute the query task within the current service period; the service period includes the previous historical service period.

[0081] The statistical query results also include the hit data when the queried party first executes the query task in the current service cycle;

[0082] The second zero-sum random number is a zero-sum random number used by the queried party to obfuscate the hit data of each query within the historical service period;

[0083] The first zero-sum random number is the negative sum of zero-sum random numbers used by the queried party to obfuscate the hit data of each query in the historical service period; the first zero-sum random number is used to obfuscate the hit data of the queried party's query in the current service period.

[0084] Based on this, the anonymity query results include hit data for each query performed by the queried party within the historical service period, as well as a second zero and a random number used to obfuscate the hit data for each query. The steps described above for determining the hit statistics of the queried party based on the statistical query results and the anonymity query results of the queried party may specifically include:

[0085] The statistical query results and the anonymous query results of the queried party are summarized. The first zero and random number in the statistical query results are used to offset the second zero and random number in the anonymous query results, which is used to obfuscate the hit data of each query in the historical service period, so as to obtain the hit statistics of the queried party in the second service period.

[0086] The second service period is a period consisting of the historical service period and the target time period, which is the time period from the start time of the current service period to the time when the second cloaking statistics query request is received.

[0087] It should be noted that the hit statistics of the queried party include the hit statistics of the queried party within the second service period; wherein, the second service period is the period consisting of the previous service period and the target time period, and the target time period is the time period consisting of the start time of the current service period to the time of receiving the first cloaking statistics query request.

[0088] In this embodiment of the application, the second service period is described using the historical service period as July 1st, the receipt time of the first cloaking statistics query request as 00:10 on July 2nd, and the current service period as July 2nd with the start time of the current service period as 00:00 on July 2nd. Figure 4As shown, the historical service period is July 1st, the current service period is July 2nd, and the receiving time is 00:10 on July 2nd. Based on the above, it can be determined that the query for the first anonymity statistics request is the first query within the current service period. In this case, the second service period is from 00:00 on July 1st to 00:10 on July 2nd. Similarly, taking the historical service period as July 2nd, the receiving time for the first anonymity statistics query request as 00:20 on July 3rd, and the current service period as July 3rd with its start time as 00:00 on July 3rd as an example, the second service period will be explained. The historical service period is July 2nd, the current service period is July 3rd, and the receiving time is 00:20 on July 3rd. In this case, we can assume that the query for the first anonymity statistics query request is the first query within the current service period. In this case, the second service period is from 00:00 on July 2nd to 00:20 on July 3rd.

[0089] In this embodiment, the current service period can be 24 hours from July 2nd, and the historical service period can be 24 hours from July 1st. Based on this, the second anonymity statistical query request can carry the original query data, such as "Is Zhang San on the blacklist of overdue payments?" If the second anonymity statistical query request is the first query within July 2nd, the first anonymity statistical query request can be sent to each of the multiple queried parties in the anonymity alliance, carrying the original query data and obfuscated query data used to obfuscate the original query data, such as "Are Zhang San, Li Si, and Wang Wu on the blacklist of overdue payments?". The statistical query result sent by any one of the multiple queried parties as queried party 1 is received. The statistical query result includes a first zero and a random number N. 15 The obfuscated hit data obtained when the queried party performs the query task for the first time in the current service period is the hit data for "whether Zhang San, Li Si, and Wang Wu are on the blacklist of overdue payments". Here, the first zero-sum random number is the negative sum of four second zero-sum random numbers from the queried party's historical service period. That is, the four second zero-sum random numbers are the zero-sum random numbers from the anonymous query results sent by the queried party on July 1st in the historical service period. There are four second zero-sum random numbers, i.e., N. 11 N 12 N 13 and N 14 The relationship between the first zero-sum random number and the second zero-sum random number is shown in the above formula (1). The first zero-sum random number can be calculated using the above formula (2). One stealth query result can correspond to one second zero-sum random number. Based on this, if there are four stealth query results, each stealth query result includes the hit data of the query data in the query party for each query in the historical service period, which is confused by a second zero-sum random number.

[0090] Based on this, the statistical query results and the anonymous query results of the queried party are summarized. The summation method can be addition. In this case, the first zero-sum random number will cancel out the four second zero-sum random numbers, thus obtaining the statistical data of the hit rate of the queried party in these 5 queries.

[0091] In this way, anonymous queries can be divided into two periodic dimensions: single query results and hit statistics. Zero-sum ring technology is applied to each dimension. Specifically, for the single anonymous query dimension, a second zero-sum random number is constructed from multiple queried parties in the anonymous alliance to obfuscate the hit data of the queried parties, ensuring the privacy of the single anonymous query while allowing the acquisition of the single query zero-sum ring through the aggregation of anonymous query results. For the hit statistics dimension, a first zero-sum random number is added to interfere with the hit data within the service period and bound to the single query zero-sum ring, ensuring the credibility of the specific hit situation of the queried parties. Then, the statistical query results including the first zero-sum random number are aggregated with the anonymous query results related to the single query zero-sum ring, automatically eliminating the zero-sum random number and obtaining the hit statistics of the queried parties. Therefore, the specific hit situation of each queried party can be obtained without each queried party individually reporting its hit statistics. Based on this embodiment, involving step 210, in one or more possible embodiments, before sending the data to be queried corresponding to the first anonymity statistical query request to multiple queried parties, it is necessary to determine whether the query of the first anonymity statistical query request is the first query within the current service period. If it is the first query within the current service period, the statistical process for the hit statistics of the queried parties can be initiated; otherwise, if it is not the first query within the current service period, multiple queried parties in the anonymity alliance can be triggered to generate zero-sum random numbers through a zero-sum random algorithm, which is equivalent to the second zero-sum random number constructed in the dimension of a single anonymity query. Based on this, before step 210, the data statistics method may also include:

[0092] Upon receiving a second stealth statistics query request from the querying party, the receiving time of the second stealth statistics query request is compared with the start time of the current service period;

[0093] If the reception time occurs after the start time, determine whether any other second cloaking statistics query requests were received during the time period between the start time and the reception time.

[0094] If no other second stealth statistics query request is received within the time period between the determined start time and the receiving time, the second stealth statistics query request is determined as the first request to execute the query task in the current service cycle.

[0095] In this embodiment, we will still take the example of the current service period being 24 hours from July 2nd and the historical service period being 24 hours from July 1st. If the receiving time of the first cloaking statistics query request is 00:10 on July 2nd, since the start time of the current service period is 00:00 on July 2nd, that is, the receiving time is after the start time, we can further determine whether other second cloaking statistics query requests were received between 00:00 on July 2nd and 00:10 on July 2nd. If no other second cloaking statistics query requests were received, it is determined that there were no other second cloaking statistics query requests before the receiving time in the current service period. At this time, it can be determined that the query for the second cloaking statistics query request is the first query in the current service period, and thus it is classified as a dimension for hit statistics.

[0096] Conversely, if there are other second stealth statistical query requests before the start time or before the start time within the current service period, multiple queried parties in the stealth alliance can be triggered to generate zero-sum random numbers using a zero-sum random algorithm. This is equivalent to constructing a second zero-sum random number in the dimension of a single stealth query, in order to obfuscate the hit data obtained by the queried party when it first executes the query task in the current service period using the second zero-sum random number.

[0097] Therefore, stealth queries can be divided into two periodic dimensions: single query results and hit statistics. This allows for subsequent binding with the single query zero-sum cycle, ensuring the reliability of the specific hit situation of the queried party.

[0098] In one or more possible embodiments, on the one hand, in order to distinguish whether the first stealth statistics query request is the first query in the current service period, and on the other hand, in order to accurately trigger the queried party to start the statistical process of the hit statistics of the queried party, the data to be queried can be improved. That is, the data to be queried carries a statistical field used to indicate the start of the statistical process of the hit statistics of the queried party. This enables the queried party to determine the first zero and random number based on the second zero and random number when the statistical field is identified. Based on this, before the step of sending the data to be queried corresponding to the first stealth statistics query request to the queried party in the stealth alliance, the data statistics method may also include steps 2401 and 2402.

[0099] Step 2401: Based on the first cloaking statistics query request, construct a query message corresponding to the first cloaking statistics query request.

[0100] In this embodiment, the query message can be encrypted data of the original data to be queried that the querying party wants to query, carried in the first anonymity statistics query request, or it can be the full data, that is, including the original data to be queried that the querying party wants to query and multiple obfuscated data to be queried by the coordinator to obfuscate the original data to be queried in order not to expose the original search conditions and original query data of the querying party. In this embodiment, the original data to be queried is data that has been desensitized using the same desensitization algorithm as the Anonymity Consortium. The original data to be queried in the second anonymity statistics query request is obfuscated by the obfuscated data corresponding to the desensitization algorithm to obtain the query message. The query message can include the original data to be queried and multiple obfuscated data to be queried. For example, the original data to be queried is denoted as 1, and the obfuscated data to be queried can be 2-100. In this case, the query message can include 1-100. Thus, the original search conditions of the querying party can be concealed.

[0101] Step 2402: Add a statistics field to the query message to obtain the data to be queried corresponding to the second stealth statistics query request; wherein, the statistics field is used to indicate the start of the statistical process for the hit statistics of the queried party, so that the queried party can determine the first zero-sum random number based on the second zero-sum random number when it recognizes the statistics field, and use the negative sum of the zero-sum random numbers used by the queried party to confuse the hit data of each query in the historical service period as the first zero-sum random number, and use the first zero-sum random number to confuse the hit data of the queried party in the current service period.

[0102] In this embodiment of the application, the coordinator will add a statistical field, such as statistics=1, to the query message to indicate that the statistical process of the hit statistics of the queried party has been started.

[0103] In one or more possible embodiments, the number of queries and the number of anonymous query results within a service period can be the same, resulting in a number of anonymous query results equal to the number of queries, and thus a number of second zero-sum random numbers. However, there are special scenarios, such as when the queried party fails to provide query services due to platform issues, meaning the coordinator fails to receive anonymous query results once or several times within a service period, or when the hit data for the queried party in the anonymous query results is null, the number of second zero-sum random numbers is less than the number of queries. Therefore, the number of queries within a service period can also be greater than the number of anonymous query results. Since there is a one-to-one correspondence between anonymous query results and second zero-sum random numbers, the number of queries within a service period can also be greater than the number of second zero-sum random numbers.

[0104] Based on this, in the previous service cycle of this application embodiment, the number of queries is M, and the number of stealth query results is P, where M is an integer greater than or equal to 1, and P is equal to M or a positive integer less than M; a stealth query result includes a second zero-sum random number, which is determined by multiple queried parties in the stealth alliance through a zero-sum random algorithm.

[0105] Next, regarding step 220, in one or more possible embodiments, the statistical query results not only participate in the calculation of the hit statistics of the queried party, but also serve as the query results for the first anonymous statistical query request from the querying party. Based on this, after receiving the statistical query results sent by the queried party, before, after, or simultaneously with the step of summarizing the statistical query results and anonymous query results of the queried party, the hit data obtained by the queried party when it first executed the query task in the current service cycle is sent to the querying party.

[0106] In this way, the process of completing the query process and simultaneously compiling the hit data can be carried out, saving interactive resources and improving statistical efficiency.

[0107] It should be noted that the second zero-sum random number in this embodiment is determined by multiple queried parties in the stealth alliance through a zero-sum random algorithm.

[0108] In this embodiment, the queried party sums the second zero-sum random numbers within the historical service period. For example, if the queried party 1 provided four anonymous query results to the queried party in the previous service period, the second zero-sum random number for each query would be N. 11 N 12 N 13 N 14 The first zero-sum random number for the current service period is N. 15 =-N 11 -N 12 -N 13 -N 14 The values ​​for other queries are obtained in the same way.

[0109] The feasibility of deriving the values ​​of the first zero and random number for the queried parties 1 to 4 will be explained in detail below.

[0110] The zero-sum cycle of a single query by query parties 1 to 4 in the historical service period can be shown as follows:

[0111] N 11 +N 21 +N 31 +N 41 =0;

[0112] N 12 +N22 +N 32 +N 42 =0;

[0113] N 13 +N 23 +N 33 +N 43 =0;

[0114] N 14 +N 24 +N 34 +N 44 =0;

[0115] The values ​​of the first zero and random number for queries 1 to 4 in the current service period can be as follows:

[0116] N 15＝ -N 11 -N 12 -N 13 -N 14 ;

[0117] N 25＝ -N 21 -N 22 -N 23 -N 24 ;

[0118] N 35＝ -N 31 -N 32 -N 33 -N 34 ;

[0119] N 45＝ -N 41 -N 42 -N 43 -N 44 ;

[0120] The process of canceling out the second zero and random number by summarizing the first zero and random number in the query results is shown in the following formula (3):

[0121] N 15 +N 25 +N 35 +N 45 =(-N 11 -N 12 -N 13 -N 14 )+(-N 21 -N 22 -N 23 -N 24 )+(-N 31 -N 32 -N33 -N 34 )+(-N 41 -

[0122] N 42 -N 43 -N 44 )=-(N 11 +N 12 +N 13 +N 14 +N 21 +N 22 +N 23 +N 24 +N 31 +N 32 +N 33 +N 34 +N 41 +N 42 +N 43 +N 44 )

[0123] =-[(N 11 +N 21 +N 31 +N 41 )+(N 12 +N 22 +N 32 +N 42 )+(N 13 +N 23 +N 33 +N 43 )+(N 14 +N 24 +N 34 +N 44 (3)

[0124] From the above, we know that the sum of the zeros and random numbers in the parentheses in formula (3) is 0. Therefore, we can obtain N. 15 +N 25 +N 35 +N 45 =0. Therefore, the value of the first zero-sum random number meets the requirement of a single query zero-sum cycle.

[0125] Based on this, after receiving the statistical query results, the coordinating party sums the statistical query results and the anonymous query results of the queried party, which can eliminate the confusion effect of zero and random numbers. The specific proof process is as follows: Taking the queried party 1 as an example for derivation: Because, N 15 =-N 11 -N 12 -N 13 -N 14 Therefore, N 11 +N 12+N 13 +N 14 +N 15 =0. Therefore, by summing the statistical query results and the anonymous query results of the queried party 1, the coordinator can eliminate the influence of zero and random numbers and obtain the hit statistics of the queried party.

[0126] Furthermore, because the first zero-sum random number is bound to the second zero-sum random number in the zero-sum ring of a single query, if any party tampers with the data, the results of a single query cannot be successfully aggregated. Therefore, it can prevent malicious parties from tampering with the data.

[0127] As mentioned above, there are some special scenarios in the embodiments of this application. For example, the queried party may fail to provide query services due to platform issues, that is, the coordinator may fail to receive the anonymous query results once or several times within a service cycle. In this case, the value of the first zero and random number will not be affected by the special scenario. The feasibility of deriving the value of the first zero and random number in the special scenario will be explained in detail.

[0128] A single query zero-sum cycle in a historical service period can be represented as follows:

[0129] N 11 +N 21 +N 31 +N 41 =0;

[0130] N 12 +N 22 +N 32 +N 42 =0;

[0131] N 13 +N 23 +0+N 43 =0;

[0132] N 14 +N 24 +N 34 +N 44 =0;

[0133] The possible values ​​for the first zero and random number in the current service period are as follows:

[0134] N 15 =-N 11 -N 12 -N 13 -N 14 ;

[0135] N 25 =-N 21 -N 22 -N 23 -N24 ;

[0136] N 35 =-N 31 -N 32 -0-N 34 ;

[0137] N 45 =-N 41 -N 42 -N 43 -N 44 ;

[0138] The process of canceling out the second zero and random number by summarizing the first zero and random number in the query results is shown in the following formula (4):

[0139] N 15 +N 25 +N 35 +N 45 =(-N 11 -N 12 -N 13 -N 14 )+(-N 21 -N 22 -N 23 -N 24 )+(-N 31 -N 32 -0-N 34 )+(-N 41 -N 42 -

[0140] N 43 -N 44 )=-(N 11 +N 12 +N 13 +N 14 +N 21 +N 22 +N 23 +N 24 +N 31 +N 32 +0+N 34 +N 41 +N 42 +N 43 +N 44 )

[0141] =-[(N 11 +N 21 +N 31 +N 41 )+(N 12 +N 22 +N 32 +N42 )+(N 13 +N 23 +0+N 43 )+(N 14 +N 24 +N 34 +N 44 )]

[0142] =0 (4)

[0143] Where, N 11 +N 12 +N 13 +N 14 +N 15 =0, N 31 +N 32 +0+N 34 +N 35 =0.

[0144] This demonstrates that even in special scenarios, such as when querying abnormalities or when the number of queried entities changes, the feasibility of obtaining the first zero and the random number can still be guaranteed.

[0145] It should be noted that, after step 230, the hit statistics of the queried party determined in this embodiment can be used to calculate the contribution of the queried party.

[0146] Based on the above data statistics system, the following is combined with... Figure 3 The data statistics method provided in the embodiments of this application will be described in detail.

[0147] Figure 3 A flowchart illustrating a data statistics method provided in an embodiment of this application.

[0148] like Figure 3 As shown, this data statistics method can be applied to, for example... Figure 1 The stealth alliance shown here uses a data collection method that may specifically include the following steps:

[0149] Step 310: Receive the first stealth statistics query request sent by the coordinator; Step 320: Based on the first stealth statistics query request, determine the first zero-sum random number as the sum of the negative numbers of each second zero-sum random number of the queried party within the service period; Step 330: Send the statistics query result to the coordinator, the statistics query result including the first zero-sum random number.

[0150] The steps described above are explained in detail below.

[0151] First, regarding step 320, in one or more possible embodiments, the first stealth statistics query request carries service period information. The first stealth statistics query request is used to request the queried party to query zero and random numbers within a first service period corresponding to the service period information; the service period includes the first service period. Based on this, step 320 may specifically include:

[0152] Based on the service period information, obtain the second zero and random numbers used by the queried party to obfuscate the hit data of each query within the first service period;

[0153] The negative sum of all the second zero-sum random numbers within the first service period of the queried party is determined as the first zero-sum random number.

[0154] In this embodiment of the application, if the queried party has 4 second zero-sum random numbers in the first service period, i.e., N 11 N 12 N 13 and N 14 The relationship between the first zero-sum random number and the second zero-sum random number is shown in formula (1) above. The first zero-sum random number is calculated using formula (2) above.

[0155] In another or more possible embodiments, the first stealth statistics query request is determined by the second stealth statistics query request sent by the querying party. The first stealth statistics query request carries a statistics field, which is used to indicate the start of a statistical process for the hit statistics of the queried party. The second stealth statistics query request is the first request to execute the query task within the current service period. The first stealth statistics query request is used to request the queried party to query zero and random numbers within the historical service period and to query the hit data queried by the queried party within the current service period. The historical service period is the previous service period of the current service period.

[0156] In this embodiment, any party in the stealth alliance can match its query data with local data to obtain the hit status data of the query data in the query party, such as 1 for a hit and 0 for a miss. Then, the first zero-sum random number can be determined with reference to the above formula (2), and the hit status data of the query data in the query party can be obfuscated by the first zero-sum random number to obtain the statistical query result, and the statistical query result is sent to the coordinator.

[0157] In this way, anonymous queries can be divided into two periodic dimensions: single query results and hit statistics. Zero-sum ring technology is applied to each dimension. Specifically, for the single anonymous query dimension, a second zero-sum random number is constructed from multiple queried parties in the anonymous alliance to obfuscate the hit data of the queried parties, ensuring the privacy of the single anonymous query while allowing the acquisition of the single query zero-sum ring through the aggregation of anonymous query results. For the hit statistics dimension, a first zero-sum random number is added to interfere with the hit data within the service period and bound to the single query zero-sum ring, ensuring the credibility of the specific hit situation of the queried parties. Then, the statistical query results including the first zero-sum random number are aggregated with the anonymous query results related to the single query zero-sum ring, automatically eliminating the zero-sum random number and obtaining the hit statistics of the queried parties. Therefore, the specific hit situation of each queried party can be obtained without each queried party individually reporting its hit statistics.

[0158] Based on this, on the one hand, to distinguish whether the first anonymous statistical query request is the first query within the current service period, and on the other hand, to accurately trigger the queried party to initiate the statistical process for the hit statistics of the queried party, the data to be queried can be improved. That is, the data to be queried can carry a statistical field to indicate the initiation of the statistical process for the hit statistics of the queried party. This allows the queried party to determine the first zero-sum random number based on the second zero-sum random number when the statistical field is identified. Based on this, before step 320, the data statistics method may also include:

[0159] Perform field identification on the data to be queried;

[0160] If the data to be queried includes statistical fields, the second zero-sum random number is obtained based on the statistical fields to obfuscate the hit data of each query in the historical service period; the negative sum of the second zero-sum random numbers of the querying party in the historical service period is determined as the first zero-sum random number.

[0161] In this embodiment, before determining the first zero-sum random number, it can be identified whether the data to be queried includes statistical fields such as statistics=1. If it does, the first zero-sum random number is determined by the above formula (2).

[0162] If the data to be queried does not contain statistical fields, a second zero-sum random number is determined by multiple query subjects in the anonymity consortium using a zero-sum random algorithm. This second zero-sum random number is then used to obfuscate the hit data of the data to be queried among the query subjects, resulting in an anonymous query result for the data to be queried, which is then sent to the coordinator. In this embodiment, if the data to be queried does not contain statistical fields (e.g., statistics=1), or if it does, the second zero-sum random number can be determined by multiple query subjects in the anonymity consortium using a zero-sum random algorithm.

[0163] Furthermore, the first anonymous statistical query request also carries the original, de-identified data to be queried. Based on this, before sending the statistical query results to the coordinator, the method may further include:

[0164] Based on the anonymized original query data, obtain the hit data of the query target when it first executes the query task in the current service cycle;

[0165] By obfuscating the hit rate data of the query by the queried party within the current service period with the first zero and a random number, statistical query results are obtained.

[0166] Therefore, the dual-period zero-sum ring data statistics method for anonymous query data sharing scenarios provided in this application can divide anonymous queries into two periodic dimensions: single query results and hit statistics. Zero-sum ring technology is applied to each period to statistically analyze the relevant results. For the former, in each anonymous query, a zero-sum ring is constructed between different queried parties to obfuscate their respective query results. After the coordinator receives the data returned by each queried party, all data is summed to eliminate zero-sum parameters, resulting in the final summary result. For the latter, a new zero-sum ring for hit statistics within the service period, namely the first zero-sum random number, is added. This first zero-sum random number is bound to the single anonymous query result summary zero-sum ring. This achieves automatic elimination of zero-sum obfuscation parameters, eliminates the need for individual reporting by each queried party, and ensures the credibility of hit data from all parties.

[0167] To better illustrate the data statistics method provided in the embodiments of this application, combined with Figure 5 The data statistics system in the embodiments of this application will be described in detail as performing data statistics methods.

[0168] based on Figure 1 The data statistics system shown demonstrates a data statistics method for performing privacy-preserving computations in an anonymous data sharing scenario.

[0169] like Figure 5As shown, in step 1, if there are 4 queries within a historical service period, such as July 1st, the second zero-sum random number for each query can be determined through multiple queried parties in the Anonymous Alliance using a zero-sum random algorithm. For example, taking queried party 1, the second zero-sum random number for each query is N. 11 N 12 N 13 N 14 .

[0170] Step 2: The querying party sends the first anonymous statistics query request to the coordinating party, such as "Is Zhang San on the blacklist of overdue payments?"

[0171] Step 3: Upon receiving a first anonymous statistical query request from the querying party, such as "Is Zhang San on the blacklist of overdue payments?", the coordinating party compares the receipt time of the first anonymous statistical query request with the start time of the current service period. If the receipt time is after the start time, the coordinating party determines whether there are other first anonymous statistical query requests within the current service period before the receipt time. If it is determined that there are no other first anonymous statistical query requests within the current service period before the receipt time, the coordinating party determines that the query for the first anonymous statistical query request is the first query within the current service period.

[0172] Step 4: If the coordinator determines that the query for the first anonymous statistics query request is the first query within the current service period, it constructs a query message corresponding to the first anonymous statistics query request; and adds a statistics field to the query message to obtain the data to be queried corresponding to the first anonymous statistics query request.

[0173] Step 5: The coordinator sends the query data corresponding to the first stealth statistics query request to multiple query subjects in the stealth alliance.

[0174] Step 6: Receive the statistical query results sent by the queried party 1, and send the statistical query results back to the querying party. The statistical query results include the hit rate data of the queried data in the queried party and a first zero-sum random number, which can be N. 15 =-N 11 -N 12 -N 13 -N 14 .

[0175] Step 7: Summarize the statistical query results and the anonymous query results for the queried party to obtain the query result summary data; then, cancel out the second zero and random number by using the first zero and random number in the query result summary data to obtain the hit statistics for queried party 1. The same applies to other queried parties, and will not be elaborated further here.

[0176] Therefore, by summing the results returned by the queried party 1 for each query, the coordinator can eliminate the influence of zero-sum random numbers and obtain statistical data on the hit rate of the queried party 1. Furthermore, because the zero-sum cycle of the hit statistics is bound to the zero-sum cycle of a single query, if any queried party tampers with the data, the results of that single query cannot be successfully summarized. This prevents malicious parties from tampering with the data.

[0177] This application also provides a data statistics device. (Specifically combined with...) Figure 6 A detailed explanation will be provided.

[0178] Figure 6 This is a schematic diagram of the structure of a data statistics device provided in one embodiment of this application.

[0179] In some embodiments of this application, Figure 6 The data statistics device shown can be set up as follows: Figure 1 The coordinating parties are shown.

[0180] like Figure 6 As shown, the data statistics device 60 may specifically include:

[0181] The sending module 601 is used to send the first cloaking statistics query request to multiple queried parties in the cloaking alliance;

[0182] The receiving module 602 is used to receive the statistical query results sent by the queried party. The statistical query results include a first zero and random number, which is the negative sum of all second zero and random numbers of the queried party within the service period.

[0183] The determination module 603 is used to determine the hit statistics of the queried party based on the statistical query results and the anonymous query results of the queried party.

[0184] In this embodiment of the application, for the hit statistics scenario, a first zero-sum random number is added and bound to a second zero-sum random number related to the zero-sum ring of a single query. This can ensure the credibility of the specific hit situation of the queried party. By statistically combining the first zero-sum random number in the result and canceling the second zero-sum random number in the anonymous query result of a single query, the hit statistics of the queried party can be obtained. Thus, it is not necessary for each queried party to report its hit statistics separately, and the specific hit situation of each queried party can be known.

[0185] The data statistics device 60 in the embodiments of this application will be described in detail below.

[0186] In one or more optional embodiments, the first stealth statistics query request carries service period information. The first stealth statistics query request is used to request the queried party to query zero and random numbers within a first service period corresponding to the service period information; the service period includes the first service period.

[0187] The second zero-sum random number is a zero-sum random number used by the queried party to obfuscate the hit data of each query within the first service period;

[0188] The first zero-sum random number is the negative sum of all the second zero-sum random numbers within the first service period of the queried party.

[0189] In one or more optional embodiments, the determining module 603 may be specifically used to, when the stealth query result includes the hit data of each query of the queried party within the first service period and the second zero and random number used to obfuscate the hit data of each query, summarize the hit data of each query of the queried party within the first service period and the second zero and random number used to obfuscate the hit data of each query, to obtain the summary query result of the queried party within the first service period;

[0190] By using the first zero and random number in the statistical query results to cancel out the zero and random number in the summary query results, the hit statistics of the queried party in the first service period are obtained.

[0191] In one or more optional embodiments, the first stealth statistics query request is determined by the second stealth statistics query request sent by the querying party, and the second stealth statistics query request is the first request to execute the query task within the current service period; the service period includes the previous historical service period of the current service period;

[0192] The statistical query results also include the hit data when the queried party first executes the query task in the current service cycle;

[0193] The second zero-sum random number is a zero-sum random number used by the queried party to obfuscate the hit data of each query within the historical service period;

[0194] The first zero-sum random number is the negative sum of zero-sum random numbers used by the queried party to obfuscate the hit data of each query in the historical service period; the first zero-sum random number is used to obfuscate the hit data of the queried party's query in the current service period.

[0195] In one or more optional embodiments, the determining module 603 may be specifically used to, when the anonymity query result includes hit data of each query of the queried party within the historical service period and a second zero-sum random number used to obfuscate the hit data of each query, summarize the statistical query result and the anonymity query result of the queried party, so as to offset the second zero-sum random number used to obfuscate the hit data of each query within the historical service period in the anonymity query result by using the first zero-sum random number in the statistical query result, thereby obtaining the hit statistics of the queried party within the second service period;

[0196] The second service period is a period consisting of the historical service period and the target time period, which is the time period from the start time of the current service period to the time when the second cloaking statistics query request is received.

[0197] In one or more optional embodiments, the data statistics device 60 in this application embodiment may further include a comparison module, which is used to compare the reception time of the second cloaking statistics query request with the start time of the current service period when a second cloaking statistics query request is received from the querying party.

[0198] The determination module 603 is used to determine whether other second cloaking statistics query requests were received during the time period between the start time and the reception time when the reception time occurs after the start time.

[0199] The determination module 603 is used to determine the second stealth statistics query request as the first query task to be executed in the current service cycle if no other second stealth statistics query request is received within the time period between the determination start time and the reception time.

[0200] In one or more optional embodiments, the data statistics device 60 in this application embodiment further includes a construction module, which is used to construct a query message corresponding to the first cloaking statistics query request according to the first cloaking statistics query request;

[0201] In this embodiment of the application, the data statistics device 60 further includes a statistics module, which is used to add statistics fields to the query message to obtain a second cloaking statistics query request;

[0202] The statistical field is used to indicate the start of a statistical process for the hit statistics of the queried party. When the queried party recognizes the statistical field, it uses the negative sum of zero and random numbers used to obfuscate the hit data of each query in the historical service period as the first zero and random number, and uses the first zero and random number to obfuscate the hit data of the queried party in the current service period.

[0203] In one or more alternative embodiments, the sending module 601 can also be used to send to the querying party the hit data obtained when the queried party first executes the query task in the current service cycle.

[0204] In one or more alternative embodiments, when the hit data of the queried party in the stealth query result is null, the number of second zeros and random numbers is less than the number of queries.

[0205] In one or more alternative embodiments, the second zero-sum random number is determined by multiple queried parties in the stealth consortium using a zero-sum random algorithm.

[0206] This application also provides a data statistics device. (Specifically combined with...) Figure 7 A detailed explanation will be provided.

[0207] Figure 7 This is a schematic diagram of the structure of a data statistics device provided in one embodiment of this application.

[0208] In some embodiments of this application, Figure 7 The data statistics device shown can be set up as follows: Figure 1 The party being queried in the Anonymous Alliance is shown.

[0209] like Figure 7 As shown, the data statistics device 70 may specifically include:

[0210] Receiver module 701 is used to receive the first stealth statistics query request sent by the coordinator;

[0211] The determination module 702 is used to determine the first zero-sum random number as the sum of the negative numbers of each second zero-sum random number of the queried party within the service period, based on the first cloaking statistics query request.

[0212] The sending module 703 is used to send statistical query results to the coordinator. The statistical query results include the first zero and a random number.

[0213] In this embodiment of the application, for the hit statistics scenario, a first zero-sum random number is added and bound to a second zero-sum random number related to the zero-sum ring of a single query. This can ensure the credibility of the specific hit situation of the queried party. By statistically combining the first zero-sum random number in the result and canceling the second zero-sum random number in the anonymous query result of a single query, the hit statistics of the queried party can be obtained. Thus, it is not necessary for each queried party to report its hit statistics separately, and the specific hit situation of each queried party can be known.

[0214] The data statistics device 70 in the embodiments of this application will be described in detail below.

[0215] In one or more optional embodiments, the data statistics device 70 in this application embodiment may further include an acquisition module, which is used to carry service period information in the first stealth statistics query request. The first stealth statistics query request is used to request the queried party to query zero-sum random numbers within the first service period corresponding to the service period information. If the service period includes the first service period, the module acquires each second zero-sum random number used by the queried party to confuse the hit data of each query within the first service period according to the service period information.

[0216] The determination module 702 can also be used to determine the negative sum of each second zero-sum random number within the first service period of the queried party as the first zero-sum random number.

[0217] In one or more optional embodiments, the first stealth statistics query request is determined by the second stealth statistics query request sent by the querying party. The first stealth statistics query request carries a statistics field, which is used to indicate the start of a statistical process for statistical data on the hit status of the queried party. The second stealth statistics query request is the first request to execute a query task within the current service period. The first stealth statistics query request is used to request the queried party to query zero and random numbers within the historical service period and to query the hit status data queried by the queried party within the current service period. The historical service period is the previous service period of the current service period.

[0218] Based on this, module 702 can be specifically used to obtain, according to the statistical field, the second zero and random number of the query subject used to obfuscate the hit data of each query in the historical service period;

[0219] The negative sum of all second zero-sum random numbers within the historical service period of the queried party is determined as the first zero-sum random number.

[0220] In one or more optional embodiments, the data statistics device 70 in this application embodiment may further include an acquisition module, which is used to acquire the hit data of the queried party when it first executes the query task in the current service cycle, based on the de-identified original query data.

[0221] In this embodiment, the data statistics device 70 may further include a confusion module, which is used to confuse the hit data of the query by the queried party in the current service period with a first zero and a random number to obtain statistical query results.

[0222] Based on the same inventive concept, this application also provides a computer device. (Specifically combined with...) Figure 8 A detailed explanation will be provided.

[0223] Figure 8 This is a schematic diagram of the structure of a computer device provided in one embodiment of this application.

[0224] like Figure 8 As shown, the computer device may include at least one of the following as described in the embodiments of this application: an electronic device, a server. The computer device may include a processor 801 and a memory 802 storing computer program instructions.

[0225] Specifically, the processor 801 may include a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0226] Memory 802 may include mass storage for data or instructions. For example, and not limitingly, memory 802 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 802 may include removable or non-removable (or fixed) media. Where appropriate, memory 802 may be internal or external to the integrated gateway disaster recovery device. In a particular embodiment, memory 802 is non-volatile solid-state memory. In a particular embodiment, memory 802 includes solid-state storage (ROM). Where appropriate, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0227] The processor 801 reads and executes computer program instructions stored in the memory 802 to implement any of the data statistics methods in the above embodiments.

[0228] In one example, the computer device may also include a communication interface 803 and a bus 810. Wherein, as... Figure 8 As shown, the processor 801, memory 802, and communication interface 803 are connected through bus 810 and complete communication with each other.

[0229] The communication interface 803 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0230] Bus 810 includes hardware, software, or both, that couples components of a flow control device together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Enhanced Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), HyperTransport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 810 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.

[0231] The computer device can execute the data statistics method described in the embodiments of this application, thereby achieving a combination Figures 1 to 7 The data statistical methods and apparatus described.

[0232] Furthermore, in conjunction with the data statistics methods in the above embodiments, this application embodiment can provide a computer-readable storage medium for implementation. This computer-readable storage medium stores computer program instructions; when executed by a processor, these computer program instructions implement any of the data statistics methods in the above embodiments.

[0233] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0234] The functional blocks shown in the above block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0235] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0236] The above are merely specific embodiments of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A data statistics method, characterized in that, include: Send the first stealth statistics query request to multiple queried parties in the stealth alliance; Receive statistical query results sent by the queried party, the statistical query results include a first zero-sum random number, the first zero-sum random number is the negative sum of all second zero-sum random numbers of the queried party within the service period, and the second zero-sum random number is the zero-sum random number used by the queried party to confuse the hit data of each query within the service period; Based on the statistical query results and the anonymous query results of the queried party, the hit statistics of the queried party are determined. The anonymous query results include the hit data of the queried party for each query within the service period after being obfuscated by the second zero and random number.

2. The method according to claim 1, characterized in that, The first stealth statistics query request carries service period information. The first stealth statistics query request is used to request the queried party to query zero and random numbers within a first service period corresponding to the service period information; the service period includes the first service period. The second zero-sum random number is a zero-sum random number used by the queried party to obfuscate the hit data of each query within the first service period; The first zero-sum random number is the negative sum of all the second zero-sum random numbers of the queried party within the first service period.

3. The method according to claim 2, characterized in that, The stealth query result includes the hit data of each query by the queried party within the first service period, and a second zero and a random number used to obfuscate the hit data of each query. The step of determining the hit statistics of the queried party based on the statistical query results and the anonymous query results of the queried party includes: The hit data of each query of the queried party within the first service period, as well as the second zero and random number used to obfuscate the hit data of each query, are summarized to obtain the summary query results of the queried party within the first service period. The zero and random number in the statistical query result are used to cancel out the zero and random number in the summary query result to obtain the hit statistics of the queried party in the first service period.

4. The method according to claim 1, characterized in that, The first stealth statistics query request is determined by the second stealth statistics query request sent by the querying party. The second stealth statistics query request is the first request to execute the query task within the current service period; the service period includes the previous historical service period of the current service period. The statistical query results also include hit data obtained when the queried party first executes the query task in the current service cycle; The second zero-sum random number is a zero-sum random number used by the queried party to obfuscate the hit data of each query within the historical service period; The first zero-sum random number is the negative sum of zero-sum random numbers used by the queried party to obfuscate the hit data of each query in the historical service period; the first zero-sum random number is used to obfuscate the hit data of the query by the queried party in the current service period.

5. The method according to claim 4, characterized in that, The stealth query results include hit data for each query by the queried party within the historical service period, and a second zero and a random number used to obfuscate the hit data for each query. The step of determining the hit statistics of the queried party based on the statistical query results and the anonymous query results of the queried party includes: The statistical query results and the anonymous query results of the queried party are summarized, and the first zero-sum random number in the statistical query results is used to offset the second zero-sum random number in the anonymous query results used to obfuscate the hit data of each query within the historical service period, so as to obtain the hit statistics of the queried party in the second service period. The second service period is a period consisting of the historical service period and the target time period, and the target time period is the time period from the start time of the current service period to the time of receiving the second stealth statistics query request.

6. The method according to claim 4, characterized in that, The method further includes: Upon receiving a second stealth statistics query request from the querying party, the receiving time of the second stealth statistics query request is compared with the start time of the current service period; If the receiving time occurs after the start time, determine whether any other second stealth statistics query requests were received during the time period between the start time and the receiving time; If no other second stealth statistics query request is received within the time period between the start time and the reception time, the second stealth statistics query request is determined as the first request to execute the query task within the current service period.

7. The method according to claim 4, characterized in that, Before sending the first cloaking statistics query request to multiple queried parties in the cloaking alliance, the method further includes: Based on the first cloaking statistics query request, construct a query message corresponding to the first cloaking statistics query request; Add a statistics field to the query message to obtain the second cloaking statistics query request; The statistical field is used to indicate the start of a statistical process for the hit statistics of the queried party, so that when the queried party recognizes the statistical field, it takes the negative sum of zero and random numbers used to confuse the hit data of each query in the historical service period as the first zero and random number, and uses the first zero and random number to confuse the hit data of the queried party in the current service period.

8. The method according to claim 4, characterized in that, After receiving the statistical query results sent by the queried party, the method further includes: Send to the querying party the hit data obtained when the queried party first executes the query task in the current service cycle.

9. The method according to claim 3 or 5, characterized in that, If the hit data of the queried party in the stealth query result is empty, the number of the second zero and the random number is less than the number of queries.

10. The method according to any one of claims 1 to 7, characterized in that, The second zero-sum random number is determined by multiple queried parties in the stealth alliance using a zero-sum random algorithm.

11. A data statistics method, characterized in that, include: Receive the first stealth statistics query request sent by the coordinator; According to the first stealth statistics query request, the sum of the negative numbers of each second zero-sum random number of the queried party within the service period is determined as the first zero-sum random number. The second zero-sum random number is the zero-sum random number used by the queried party to confuse the hit data of each query within the service period. The coordinator sends statistical query results to the coordinator, the statistical query results including the first zero and random number, so that the coordinator can determine the hit statistics of the queried party based on the statistical query results and the anonymous query results of the queried party, the anonymous query results including the hit data of the queried party for each query within the service period after being obfuscated by the second zero and random number.

12. The method according to claim 11, characterized in that, The first stealth statistics query request carries service period information. The first stealth statistics query request is used to request the queried party to query zero and random numbers within a first service period corresponding to the service period information; the service period includes the first service period. The step of determining the first zero-sum random number as the negative sum of all second zero-sum random numbers within the service period of the queried party according to the first anonymity statistical query request includes: Based on the service period information, obtain each second zero and random number used by the queried party to obfuscate the hit data of each query within the first service period; The negative sum of all the second zero-sum random numbers of the queried party within the first service period is determined as the first zero-sum random number.

13. The method according to claim 11, characterized in that, The first stealth statistics query request is determined by the second stealth statistics query request sent by the querying party. The first stealth statistics query request carries a statistics field, which is used to indicate the start of the statistical process for the hit statistics of the queried party. The second stealth statistics query request is the first request to execute the query task within the current service cycle. The first stealth statistics query request is used to request the queried party to query zero and random numbers in the historical service period and query the hit data of the queried party in the current service period, wherein the historical service period is the previous service period of the current service period; The step of determining the first zero-sum random number as the negative sum of all second zero-sum random numbers within the service period of the queried party according to the first anonymity statistical query request includes: Based on the statistical fields, obtain the second zero and random number used by the queried party to obfuscate the hit data of each query within the historical service period; The negative sum of all the second zero-sum random numbers within the historical service period of the queried party is determined as the first zero-sum random number.

14. The method according to claim 13, characterized in that, The first anonymous statistical query request also carries the original, de-identified data to be queried; before sending the statistical query result to the coordinator, the method further includes: Based on the anonymized original query data, obtain the hit data obtained by the queried party when it first executes the query task in the current service cycle; The statistical query results are obtained by obfuscating the hit data of the query by the queried party within the current service period using the first zero and random number.

15. A data statistics device, characterized in that, include: The sending module is used to send the first cloaking statistics query request to multiple queried parties in the cloaking alliance; The receiving module is used to receive the statistical query results sent by the queried party. The statistical query results include a first zero-sum random number, which is the negative sum of all second zero-sum random numbers of the queried party within the service period. The second zero-sum random number is a zero-sum random number used by the queried party to confuse the hit data of each query within the service period. The determination module is used to determine the hit statistics of the queried party based on the statistical query results and the anonymous query results of the queried party. The anonymous query results include the hit data of the queried party for each query within the service period after being obfuscated by the second zero and random number.

16. A data statistics device, characterized in that, include: The receiving module is used to receive the first stealth statistics query request sent by the coordinator; The acquisition module is used to determine the negative sum of each second zero-sum random number of the queried party within the service period as the first zero-sum random number based on the first cloaking statistics query request. The second zero-sum random number is the zero-sum random number used by the queried party to confuse the hit data of each query within the service period. The sending module is used to send statistical query results to the coordinator. The statistical query results include the first zero and random number, so that the coordinator can determine the hit statistics of the queried party based on the statistical query results and the anonymous query results of the queried party. The anonymous query results include the hit data of the queried party for each query within the service period after being obfuscated by the second zero and random number.

17. A computer device, characterized in that, The computer device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, it implements the data statistics method as described in any one of claims 1-10, or the data statistics method as described in any one of claims 11-14.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the data statistics method as described in any one of claims 1-10, or the data statistics method as described in any one of claims 11-14.

19. A computer program product, characterized in that, It includes a computer program, which, when executed by a processor, implements the data statistics method as described in any one of claims 1-10, or implements the data statistics method as described in any one of claims 11-14.

Images