User Data Joint Reporting System

Abstract

The embodiment of the present disclosure discloses a user data joint reporting system. A specific implementation of the system includes: a joint reporting client, a joint reporting server, each joint reporting sub-client and each joint reporting sub-server; and the joint reporting server is configured to load user-related data in response to receiving the joint reporting task start information sent by the joint reporting client; send the joint reporting task start information to each joint reporting sub-server corresponding to the device information set; classify and merge the user-related data according to each received reporting category information to obtain each user merged association information set; send each reporting category information to each joint reporting sub-server corresponding to the device information set; generate each joint reporting information based on each user merged association information set. This implementation improves the CPU utilization of each participant and the security of user-related data.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular to a user data joint reporting system. Background Art

[0002] Joint reporting of user data means that the data reporter (parent company) jointly with various participating parties (subsidiaries) summarizes and calculates the user-related data of each party and generates reporting information. At present, joint reporting of user data mainly involves the data reporter obtaining the user-related data of each participating party in plain text, uniformly processing the user-related data of each participating party locally according to data verification rules, and summarizing and calculating the processed user-related data in plain text locally on the data reporter to obtain reporting information, and reporting the reporting information in the form of a table or file.

[0003] However, in practice, it is found that when the above method is used for joint reporting of user data, the following technical problems often occur:

[0004] The data reporting party obtains the user-related data of each participant in plain text, and performs summary calculations on the processed user-related data in plain text. The user-related data of each participant is fully exposed to the data reporting party, resulting in low security of the user-related data of each participant. In addition, the processing and summary calculation of all data are performed by the data reporting party, resulting in low CPU utilization of each participant, wasting the CPU usage resources of each participant.

[0005] The above information disclosed in this Background section is only for enhancement of understanding of the background of the inventive concept and therefore it may contain information that does not form the prior art that is already known in this country to a person of ordinary skill in the art. Summary of the invention

[0006] The content of this disclosure is used to introduce concepts in a brief form, which will be described in detail in the detailed implementation section below. The content of this disclosure is not intended to identify the key features or essential features of the technical solution claimed for protection, nor is it intended to limit the scope of the technical solution claimed for protection.

[0007] Some embodiments of the present disclosure propose a user data joint reporting system to solve one or more of the technical problems mentioned in the above background technology section.

[0008] In a first aspect, some embodiments of the present disclosure provide a user data joint reporting system, including a joint reporting client, a joint reporting server, various joint reporting sub-clients, and various joint reporting sub-servers; and the above-mentioned joint reporting client is configured to, in response to detecting a selection operation acting on a joint reporting task start control, send joint reporting task start information to the above-mentioned joint reporting server; in response to detecting a selection operation acting on a reporting category selection control in each reporting category selection control, send reporting category information corresponding to the selected reporting category selection control to the above-mentioned joint reporting server; the above-mentioned joint reporting server The terminal is configured to, in response to receiving the joint reporting task start information sent by the above-mentioned joint reporting client, load the user-related data according to the first preset data loading source, and obtain the device information set; send the above-mentioned joint reporting task start information to each joint reporting sub-server corresponding to each device information in the above-mentioned device information set; classify and merge the above-mentioned user-related data according to each received reporting category information to obtain each user merged association information set; send the above-mentioned each reporting category information to each joint reporting sub-server corresponding to each device information in the above-mentioned device information set; based on the above-mentioned each user combined association information set and associating the information sets to generate various joint submission information; each of the above-mentioned joint submission sub-clients is configured to display a data confirmation control on the data loading page in response to receiving a data loading success message sent by the joint submission sub-server corresponding to the above-mentioned joint submission sub-client; in response to detecting a selection operation acting on the above-mentioned data confirmation control, send the data confirmation information to the above-mentioned joint submission sub-server; each of the above-mentioned joint submission sub-servers is configured to load the data from the second preset data in response to receiving a joint submission task start message sent by the above-mentioned joint submission server. The source loads the sub-user associated information set; in response to receiving the data confirmation information sent by the joint reporting sub-client corresponding to the above-mentioned joint reporting sub-server, the sub-user associated information set is normalized to obtain the normalized sub-user associated information set as the standard sub-user associated information set; in response to receiving each reporting category information sent by the above-mentioned joint reporting server, the standard sub-user associated information set is classified and merged according to each reporting category information received to obtain each sub-user merged associated information set; based on the above-mentioned each sub-user merged associated information set, each sub-joint reporting information is generated.

[0009] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the user data joint reporting system of some embodiments of the present disclosure, the CPU utilization rate of each participant and the security of user-related data are improved, thereby reducing the waste of CPU resources used by each participant. Specifically, the reasons for the low CPU utilization rate of each participant, the low security of user-related data of each participant, and the waste of CPU resources used by each participant are: the data reporter obtains the user-related data of each participant in plain text, and summarizes and calculates the processed user-related data in plain text, and the user-related data of each participant is all exposed to the data reporter, resulting in low security of the user-related data of each participant. Moreover, the processing and summary calculation of all data are performed by the data reporter, resulting in low CPU utilization rate of each participant and wasting CPU resources used by each participant. Based on this, the user data joint reporting system of some embodiments of the present disclosure includes a joint reporting client, a joint reporting server, each joint reporting sub-client and each joint reporting sub-server; and the above-mentioned joint reporting client is configured to first, in response to detecting a selection operation acting on the joint reporting task start control, send the joint reporting task start information to the above-mentioned joint reporting server. In this way, the joint reporting server can be notified to start the joint reporting task. Then, in response to detecting a selection operation acting on the reporting category selection control in each reporting category selection control, the reporting category information corresponding to the selected reporting category selection control is sent to the above-mentioned joint reporting server. In this way, the joint reporting server can be notified of the reporting category selected by the user. The above-mentioned joint reporting server is configured to first, in response to receiving the joint reporting task start information sent by the above-mentioned joint reporting client, load user-related data according to the first preset data loading source, and obtain a device information set. In this way, the original data and device information set corresponding to the reporting task can be obtained. Then, the above-mentioned joint reporting task activation information is sent to each joint reporting sub-server corresponding to each device information in the above-mentioned device information set. In this way, each joint reporting sub-server can know that the reporting task has been activated and can prepare the original data corresponding to the reporting task. Afterwards, according to the received reporting category information, the above-mentioned user-related data is classified and merged to obtain each user-merged associated information set. In this way, each user-merged associated information set can be obtained, which can be used to generate each joint reporting information. Finally, based on the above-mentioned each user-merged associated information set, each joint reporting information is generated. In this way, each joint reporting information can be obtained, wherein the joint reporting information in the above-mentioned each joint reporting information can represent the data fragments of each user-related information with a higher risk exposure.Each of the above-mentioned joint reporting sub-clients is configured to first, in response to receiving the data loading success information sent by the joint reporting sub-server corresponding to the above-mentioned joint reporting sub-client, display the data confirmation control on the data loading page. Thus, the user can select the data confirmation control. Then, in response to detecting the selection operation acting on the above-mentioned data confirmation control, the data confirmation information is sent to the above-mentioned joint reporting sub-server. Thus, the above-mentioned joint reporting server can know that the original data uploaded by the joint reporting sub-server is correct. Each of the above-mentioned joint reporting sub-servers is configured to first, in response to receiving the joint reporting task start information sent by the above-mentioned joint reporting server, load the sub-user association information set from the second preset data loading source. Thus, the original data of the joint reporting sub-server corresponding to the reporting task can be obtained. Then, in response to receiving the data confirmation information sent by the joint reporting sub-client corresponding to the above-mentioned joint reporting sub-server, the sub-user association information set is normalized, and the sub-user association information set after normalization is obtained as the standard sub-user association information set. Thus, a standard sub-user associated information set can be obtained. The above-mentioned standard sub-user associated information set can be a sub-user associated information set after normalization. Afterwards, in response to receiving each reporting category information sent by the above-mentioned joint reporting service end, the above-mentioned standard sub-user associated information set is classified and merged according to each reporting category information received, so as to obtain each sub-user merged associated information set. Thus, each sub-user merged associated information set can be obtained. The above-mentioned each sub-user merged associated information set can be each set obtained by classifying and merging the standard sub-user associated information set according to each preset classification information included in each reporting category information. Finally, based on the above-mentioned each sub-user merged associated information set, each sub-joint reporting information is generated. Thus, each sub-joint reporting information can be obtained. The sub-joint reporting information in the above-mentioned each sub-joint reporting information can represent the data fragments of each standard sub-user associated information with a higher risk exposure. Also, because the user data joint reporting system implemented can unite the data reporter (joint reporting server) and each participant (each joint reporting sub-server), each participant participates in the data processing and reporting information generation, instead of only the data reporter processing all data and generating reporting information, thus improving the CPU utilization of each participant and reducing the waste of CPU resources of each participant. And the data of the data reporter and each participant are exchanged in a confidential state (fragmented state). During the data processing process, the data reporter does not know the data queried by each participant, and the original data of the data reporter will not be exposed to each participant.Moreover, during the process of generating reported information, neither the data reporter nor any of the participating parties can deduce the original data of other parties based on their own data, thereby improving the security of user-related data of each participating party. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. Throughout the accompanying drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and that components and elements are not necessarily drawn to scale.

[0011] Figure 1 is a schematic diagram of the structure of some embodiments of the user data joint reporting system according to the present disclosure;

[0012] Figure 2 It is a timing diagram of some embodiments of the user data joint reporting system according to the present disclosure. DETAILED DESCRIPTION

[0013] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0014] It should also be noted that, for ease of description, only the parts related to the invention are shown in the drawings. In the absence of conflict, the embodiments and features in the embodiments of the present disclosure can be combined with each other.

[0015] It should be noted that the concepts such as "first" and "second" mentioned in the present disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0016] It should be noted that the modifications of "one" and "plurality" mentioned in the present disclosure are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0017] The names of the messages or information exchanged between multiple devices in the embodiments of the present disclosure are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0018] The present disclosure will be described in detail below with reference to the accompanying drawings and in conjunction with embodiments.

[0019] Figure 1 A schematic diagram of the structure of some embodiments of the user data joint reporting system according to the present disclosure is shown.

[0020] like Figure 1 As shown, the user data joint reporting system provided by the present disclosure may include: each joint reporting sub-client 1, each joint reporting sub-server 2, a joint reporting client 3 and a joint reporting server 4. The above-mentioned joint reporting client 3 may be a reporting system client of the parent company. The above-mentioned joint reporting server 4 may be a reporting system server of the parent company. The above-mentioned each joint reporting sub-client 1 may be each reporting system client of each subsidiary of the above-mentioned parent company. The above-mentioned each joint reporting sub-server 2 may be each reporting system server of each subsidiary of the above-mentioned parent company. The above-mentioned joint reporting server 4 is respectively connected to the above-mentioned joint reporting client 3 and the above-mentioned each joint reporting sub-server 2 in communication. The joint reporting sub-servers in the above-mentioned each joint reporting sub-server 2 correspond to the joint reporting sub-clients in the above-mentioned each joint reporting sub-client 1 one by one. The joint reporting sub-servers in the above-mentioned each joint reporting sub-server 2 are connected to the joint reporting sub-clients in the above-mentioned each joint reporting sub-client 1 in communication.

[0021] Reference below Figure 2 , which shows a timing diagram of a user data joint reporting system disclosed in the present invention.

[0022] like Figure 2 As shown, a user data joint reporting system includes: each joint reporting sub-client, each joint reporting sub-server, a joint reporting client and a joint reporting server. The interaction steps between the above-mentioned each joint reporting sub-client, each joint reporting sub-server, the joint reporting client and the joint reporting server may include the following steps:

[0023] In some embodiments, the joint filing client may be configured to perform the following steps:

[0024] Step 201 , in response to detecting a selection operation on a control for starting a joint reporting task, the joint reporting client sends joint reporting task start information to the joint reporting server.

[0025] In some embodiments, the joint reporting client may send the joint reporting task start information to the above-mentioned joint reporting server in response to detecting a selection operation acting on the joint reporting task start control. The above-mentioned joint reporting task start control may be a control for starting the joint reporting task. The above-mentioned selection operation may be, but not limited to, one of the following: click, slide. The above-mentioned joint reporting task start information may be a prompt message indicating that the joint reporting task has been started. In practice, in response to detecting a selection operation acting on the joint reporting task start control, the above-mentioned joint reporting client may adopt a data transmission protocol, and the joint reporting task start information is sent to the above-mentioned joint reporting server. The above-mentioned data transmission protocol may be, but not limited to, one of the following: HTTPS protocol, FTP protocol, WebSocket protocol.

[0026] Step 202: In response to receiving the joint reporting task start information sent by the joint reporting client, the joint reporting server loads the user-related data and obtains the device information set according to the first preset data loading source.

[0027] In some embodiments, in response to receiving the joint reporting task start information sent by the joint reporting client, the joint reporting server may load user-related data and obtain a device information set according to a first preset data loading source. The first preset data loading source may be a data storage source. The data storage source may be a database or a text file. For example, the file type of the text file may be a CSV type or a TXT type. The reporting task may be a task of reporting each user with a higher risk exposure of the parent company and each subsidiary to the parent company. The user-related data may be user-related data associated with the reporting task. The user-related data may include a user basic information set, a user-related information set, and an abnormal and standard user name information set. The user basic information set may represent each basic information of each user. The user basic information in the user basic information set may include each field and the field value corresponding to each field. The fields may include but are not limited to multiple of the following: user name field, user certificate type field, user certificate code field, whether it is an associated party field, associated user name field, associated value field, whether it is the same field field, field classification field, and supply user name field. The above-mentioned "whether it is an associated party" field can represent whether the user corresponding to the user name field in the user association information has an associated relationship with the company corresponding to the execution subject. For example, the field value corresponding to the "whether it is an associated party" field can be "1-yes" or "0-no". The above-mentioned associated user name field can represent the user name that has an associated relationship with the company corresponding to the execution subject. The above-mentioned user association information set can be information related to each value representing each user. The user association information in the above-mentioned user association information set can include each associated field and the field value corresponding to each associated field. The above-mentioned each associated field can include but is not limited to multiple items of the following: user name field, user certificate type field, user certificate code field, business category code field, and associated value field. For example, the business category code field can represent the transaction category code, and the associated value field can represent the risk exposure amount. The above-mentioned abnormal and standard user name information set can represent the corresponding relationship between the abnormal user name and the standard user name. The abnormal and standard user name information in the above-mentioned abnormal and standard user name information set can include the abnormal user name and the standard user name corresponding to the abnormal user name. The above-mentioned abnormal user name can be a user name with an irregular name. The above-mentioned device information set can be each device participating in the joint reporting task. Each of the above-mentioned devices may include each joint reporting sub-server. The device information in the above-mentioned device information may include but is not limited to: device node name information, company name corresponding to the device, subsidiary certificate type corresponding to the device, and subsidiary certificate code corresponding to the device. The above-mentioned device node name information may include level attribute information of the company corresponding to the device. For example, the level attribute information may be a subsidiary or a parent company.In practice, the above-mentioned joint reporting server can obtain the device information set from the associated database.

[0028] In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to load user-related data according to a first preset data loading source in response to receiving the joint reporting task start information sent by the joint reporting client:

[0029] The first step is to load the user basic information set, the user association information set and the abnormal and standard user name information set into the memory according to the above-mentioned first preset data loading source.

[0030] In the second step, for each user association information in the above user association information set, perform the following data cleaning steps:

[0031] The first sub-step is to perform normalization processing on the user association information according to a preset keyword set to obtain normalized user association information. The preset keyword set may represent various preset keywords that cannot be included in the field value corresponding to the user name field in the user association information. For example, the preset keywords in each preset keyword may be, but not limited to, one of the following: business department, branch company, sub-branch. In practice, the joint reporting service end may delete each preset keyword included in the field value corresponding to the user name field in the user association information to perform normalization processing on the user association information to obtain normalized user association information.

[0032] In the second sub-step, in response to determining that the normalized user association information satisfies the preset association condition, determining whether the associated user name field included in the normalized user association information is empty. The preset association condition may be that the field value corresponding to the associated party field in the normalized user association information is "1-yes".

[0033] The third sub-step is, in response to determining that the associated user name field included in the normalized user association information is empty, performing information filling processing on the normalized user association information, and obtaining the user association information after information filling processing as standard user association information. In practice, first, in response to determining that the user basic information corresponding to the user association information exists in the above-mentioned user basic information set, the above-mentioned joint reporting service end can fill each field value corresponding to the associated user related field included in the user basic information corresponding to the above-mentioned user association information in the above-mentioned user basic information set into the normalized user association information. The above-mentioned associated user related field may include but is not limited to multiple of the following: associated user name field, associated user certificate type field, associated user certificate code field. Then, in response to determining that the user basic information corresponding to the above-mentioned user association information does not exist in the above-mentioned user basic information set, the associated user related field included in the above-mentioned normalized user association information can be filled with information according to the filling information submitted by the user. The above-mentioned filling information can be each field value corresponding to the above-mentioned associated user related field submitted by the user.

[0034] The fourth sub-step is, in response to determining that the associated user name field included in the normalized user association information is not empty, determining the normalized user association information as standard user association information.

[0035] The third step is to determine the obtained individual pieces of standard user association information as a standard user association information set.

[0036] In the fourth step, the standard user association information set, the basic user information set and the abnormal and standard user name information set are determined as user association data.

[0037] Step 203: the joint reporting server sends the joint reporting task start information to each joint reporting sub-server corresponding to each device information in the device information set.

[0038] In some embodiments, the joint reporting server may send the joint reporting task start information to each joint reporting sub-server corresponding to each device information in the device information set.

[0039] Step 204: each of the joint reporting sub-servers loads the sub-user associated information set from the second preset data loading source in response to receiving the joint reporting task start information sent by the joint reporting server.

[0040] In some embodiments, in response to receiving the joint reporting task start information sent by the above-mentioned joint reporting server, each of the above-mentioned joint reporting sub-servers can load a sub-user association information set from a second preset data loading source. Among them, the above-mentioned sub-user association information set can be a user association information set in the above-mentioned joint reporting sub-server. The sub-user association information in each sub-user association information in the above-mentioned sub-user association information set can include each field and the field value corresponding to each field. For example. The field in each field can be a user name field, a user certificate type field, a user certificate code field, a business category code field or an associated value field. The above-mentioned second preset data loading source can be a data storage source.

[0041] In some optional implementations of some embodiments, each of the above-mentioned joint reporting sub-servers may be further configured to perform the following steps to load the sub-user association information set from the second preset data loading source in response to receiving the joint reporting task start information sent by the above-mentioned joint reporting server:

[0042] The first step is to load the sub-user association information set into the memory according to the second preset data loading source.

[0043] The second step is to perform data verification processing on the above-mentioned sub-user association information set to obtain a data verification result. The above-mentioned data verification result may be a characterization of whether the verification of the above-mentioned sub-user association information set is successful or failed. The above-mentioned data verification processing may be a process for determining whether the data type of each field included in each sub-user association information in the sub-user association information set is standardized. In practice, for each sub-user association information in the above-mentioned sub-user association information set, each of the above-mentioned joint reporting sub-servers may be further configured to perform the following steps to perform data verification processing on the above-mentioned sub-user association information set to obtain a data verification result:

[0044] First sub-step: For each field in the above sub-user association information, in response to determining that the data type included in the field and data type information corresponding to the above field in the preset field and data type information set is different from the data type corresponding to the above field, add 1 to the preset count value. The above preset field and data type information set can represent the correspondence between the field and the data type. The preset field and data type information in the above preset field and data type information set can include the field and the data type corresponding to the field. For example, the data type can be but is not limited to one of the following: int type, string type, char type, float type. The above preset count value can be the number of non-standard fields recorded in the above each sub-user association information. The initial value of the above preset count value can be 0.

[0045] In a second sub-step, in response to determining that the obtained preset count value is 0, determining verification success as a data verification result.

[0046] A third sub-step, in response to determining that the obtained preset count value is greater than 0, determining a verification failure as a data verification result.

[0047] The third step is, in response to determining that the above data verification result indicates that the verification is successful, sending data loading success information to the joint reporting sub-client corresponding to the above joint reporting sub-server.

[0048] In the fourth step, in response to determining that the data verification result indicates a verification failure, a data loading failure message is sent to the joint reporting sub-client corresponding to the joint reporting sub-server. The data loading failure message may be a prompt message that prompts the user that the sub-user associated information set loaded from the second preset data loading source has failed to be verified.

[0049] Step 205: each of the joint reporting sub-clients displays a data confirmation control on the data loading page in response to receiving the data loading success information sent by the joint reporting sub-server corresponding to the joint reporting sub-client.

[0050] In some embodiments, each of the above-mentioned joint reporting sub-clients may display a data confirmation control on the data loading page in response to receiving a data loading success message sent by the joint reporting sub-server corresponding to the above-mentioned joint reporting sub-client. The above-mentioned data confirmation control may be a control for confirming that the data is correct. The above-mentioned data loading success message may be a prompt message sent by the joint reporting sub-server corresponding to the above-mentioned joint reporting sub-client indicating that the data verification is successful.

[0051] Step 206 , in response to detecting a selection operation on a reporting category selection control among the reporting category selection controls, the joint reporting client sends the reporting category information corresponding to the selected reporting category selection control to the joint reporting server.

[0052] In some embodiments, the above-mentioned joint reporting client can respond to the detection of the selection operation of the reporting category selection control in each reporting category selection control, and send the reporting category information corresponding to the selected reporting category selection control to the above-mentioned joint reporting server. Among them, the above-mentioned each reporting category selection control can be each control for selecting a reporting category. The reporting category selection control in the above-mentioned each reporting category selection control corresponds to the reporting category information in each reporting category information one by one. The above-mentioned selection operation can be but not limited to: click, slide, drop-down box selection. The above-mentioned each reporting category information can be each reporting category selected by the user. For example, the reporting category information can be a single customer category of the same industry, which represents that the user association information set of each participant is summarized and summed according to the fields such as the customer name field, whether it is the same field field, the business category code field, and the associated value field. The above-mentioned each participant may include the above-mentioned joint reporting server and the above-mentioned each joint reporting sub-server.

[0053] It should be noted that the specific setting of the execution order of step 205 and step 206 is not limited. Step 205 can be executed before step 206, or after step 206, or at the same time as step 206.

[0054] Step 207, the joint reporting server classifies and merges the user-related data according to the received reporting category information to obtain a combined related information set of each user.

[0055] In some embodiments, the joint reporting service end may classify and merge the user-related data according to the received reporting category information to obtain each user-merged associated information set. The user-merged associated information sets in each user-merged associated information set correspond to the reporting category information in each reporting category information. The user-merged associated information sets may be sets obtained by classifying and merging the user-related information sets included in the user-related data according to each preset classification information included in each reporting category information. The fields included in the user-merged associated information in different sets of the user-merged associated information sets may be different.

[0056] In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to classify and merge the user-related data according to the received reporting category information to obtain a combined association information set for each user:

[0057] The first step is to obtain a set of preset field value and encoding relationship information. The above-mentioned set of preset field value and encoding relationship information can represent the relationship between the field value and the encoding corresponding to the field value. The preset field value and encoding relationship information in the above-mentioned set of preset field value and encoding relationship information can include the field value and the encoding corresponding to the field value.

[0058] The second step is to send the above-mentioned preset field value and coding relationship information set to each of the above-mentioned joint reporting sub-servers.

[0059] Step 3: For each of the above-mentioned reporting categories, perform the following steps:

[0060] The first execution step is to classify each standard user association information in the above standard user association information set according to the preset classification information included in the above reporting category information to obtain each user association information set. Among them, the reporting category information in each of the above reporting category information may include preset classification information. The preset classification information included in each of the above reporting category information may be different. The standard user association information in the above standard user association information set may include each field and the field value corresponding to each field. The above preset classification information may include each classification field. The user association information set in the above each user association information set may include each standard user association information. In practice, the above joint reporting service end may use the GROUP BY tool to group the above each standard user association information according to the above classification characters to obtain each user association information set. For example, when the reporting category information represents a single customer category in the same industry, the classification fields included in the preset classification information may be: customer name field, whether it is the same field field, business category code field, and associated value field.

[0061] The second execution step is to execute the following steps for each user association information set in the above user association information sets:

[0062] In the first sub-step, each field value corresponding to the user-associated value field in each standard user-associated information in the user-associated information set is merged to obtain merged user-associated value information. The merged user-associated value information may be the user-associated value information obtained by summing up each field value corresponding to the user-associated value field in each standard user-associated information. In practice, the joint reporting server may determine the sum of each field value corresponding to the user-associated value field in each standard user-associated information as the merged user-associated value information.

[0063] The second sub-step is to determine any one of the standard user association information in the above user association information set as the target user association information.

[0064] The third sub-step is to change the determined target user association information according to the above-mentioned merged user association value information, the above-mentioned preset field value and the coding relationship information set, and obtain the changed user association information as the user merged association information. Among them, the above-mentioned changed user association information can be the target user association information after the change processing. In practice, first, the above-mentioned joint reporting service end can determine the preset field value corresponding to the field classification field value in the above-mentioned preset field value and the coding relationship information set and the code included in the coding relationship information as the field classification code. Among them, the above-mentioned field classification field value can be the field value corresponding to the field classification field in the above-mentioned target user association information. Then, the preset field value corresponding to the supply user name field value in the above-mentioned preset field value and the coding relationship information set and the code included in the coding relationship information can be determined as the supply user name code. Among them, the above-mentioned supply user name field value can be the field value corresponding to the supply user name field in the above-mentioned target user association information. Afterwards, the preset user name corresponding to the user name field value in the preset user name and coding information set and the code included in the coding information can be determined as the user name code. Among them, the above-mentioned user name field value can be the field value corresponding to the user name field in the above-mentioned target user association information. The above-mentioned preset user name and code information set can represent the correspondence between user name information and code. The preset user name and code information in the above-mentioned preset user name and code information set can include user name information and the code corresponding to the user name field value. Afterwards, the field value corresponding to the domain classification field in the above-mentioned target user association information can be replaced with the above-mentioned domain classification code, the field value corresponding to the supply user name field can be replaced with the above-mentioned supply user name code, the field value corresponding to the user association value field can be replaced with the above-mentioned merged user association value information, and the field value corresponding to the user name field can be replaced with the above-mentioned user name code, so as to change the determined target user association information and obtain the changed user association information as the user merged association information.

[0065] The third execution step is to determine the obtained respective user combined association information as a user combined association information set.

[0066] Step 208: The joint reporting server generates each joint reporting information based on the combined associated information sets of each user.

[0067] In some embodiments, the joint reporting service end may generate each joint reporting information based on the above-mentioned combined related information set of each user. The joint reporting information in each joint reporting information may represent each data fragment of the related information of each user with a higher risk exposure. In practice, the joint reporting service end may generate each joint reporting information based on the above-mentioned combined related information set of each user in various ways.

[0068] In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to generate each joint reporting information based on the above-mentioned combined associated information sets of each user:

[0069] For each user combined association information set in the above-mentioned user combined association information sets, perform the following steps:

[0070] In the first step, data segmentation is performed on each user merged association information in the above user merged association information set to obtain each reserved segmented data and each exchange segmented data set. The reserved segmented data in the above each reserved segmented data may be each data fragment of each user merged association information retained locally. The exchange segmented data in the above exchange segmented data set may be each data fragment of each user merged association information that is exchanged with the joint reporting sub-server. The exchange segmented data set in the above each exchange segmented data set corresponds to the joint reporting sub-server in the above each joint reporting sub-server.

[0071] The second step is to send each of the exchange segmentation data sets mentioned above to each of the joint reporting sub-servers mentioned above respectively.

[0072] In the third step, in response to receiving the respective sub-exchange segmented data sets corresponding to the respective reserved segmented data sent by the respective joint reporting sub-servers, based on the respective reserved segmented data and the respective sub-exchange segmented data sets, the respective joint segmented data are generated as joint reporting information. The above-mentioned joint reporting information may be reporting fragment information jointly generated by the above-mentioned joint reporting server and the above-mentioned respective joint reporting sub-servers. The above-mentioned reporting fragment information may include respective reporting fields and respective field value data fragments corresponding to the respective reporting fields. The above-mentioned respective reporting fields may be respective fields included in the user merged association information in the above-mentioned user merged association information set. The above-mentioned respective field value data fragments may be respective data fragments of respective field values ​​corresponding to the respective reporting fields. In practice, in response to receiving the respective sub-exchange segmented data sets corresponding to the respective reserved segmented data sent by the respective joint reporting sub-servers, the above-mentioned joint reporting server may generate the respective joint segmented data as joint reporting information based on the respective reserved segmented data and the respective sub-exchange segmented data sets through a preset joint reporting information generation interface. The preset joint reporting information generation interface may be an interface for each participant to perform collaborative computing while protecting their own private data. For the joint reporting server, the input of the preset joint reporting information generation interface may be the identification information of the joint reporting server, the respective reserved segmented data, and the respective sub-exchange segmented data sets, and the output may be the respective joint segmented data. Among them, the identification information of the joint reporting server may be the IP address of the joint reporting server.

[0073] In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps:

[0074] The first step is to generate each query result information in response to receiving each data query request information sent by the joint reporting sub-server in each of the above-mentioned joint reporting sub-servers, according to the user basic information set and the abnormal and standard user name information set included in the above-mentioned user association data, and send each query result information to the above-mentioned joint reporting sub-server. Among them, the data query request information in each of the above-mentioned data query request information can be a request information for querying the standard user name information corresponding to the user name information to be standardized in the above-mentioned joint reporting server. The above-mentioned user name information to be standardized can be a field value corresponding to the user name field included in the sub-user association information in the above-mentioned joint reporting sub-server. The above-mentioned data query request information can include encrypted user name information. The above-mentioned encrypted user name information can be obtained by encrypting the user name information to be standardized by the above-mentioned joint reporting sub-server using the MD5 encryption algorithm. The above-mentioned sub-user association information can be included in the sub-user association information set in the above-mentioned joint reporting sub-server. The query result information in each of the above-mentioned query result information can indicate whether there is standard user name information corresponding to the above-mentioned encrypted user name information in the user basic information set or the abnormal and standard user name information set. It should be noted that each field value corresponding to the user name field in the above-mentioned user basic information set is the standardized user name information. In practice, in response to receiving each data query request information sent by the joint reporting sub-server in each of the above-mentioned joint reporting sub-servers, the above-mentioned joint reporting server can use a preset anonymous query interface to generate each query result information according to the user basic information set and the abnormal and standardized user name information set included in the above-mentioned user-related data. The above-mentioned preset anonymous query interface can be an interface that encapsulates the anonymous query protocol. The input of the above-mentioned preset anonymous query interface can be the user basic information set, the abnormal and standardized user name information set and the encrypted user name information, and the output can be the query result information.

[0075] In the second step, in response to receiving the device configuration information sent by the above-mentioned joint reporting client, the device information set is updated according to the above-mentioned device configuration information to obtain an updated device information set. Among them, the above-mentioned device configuration information can represent the addition of device information, deletion of device information or modification of device information. The above-mentioned device configuration information may include configuration type information, device node name information, user name corresponding to the device, user certificate type corresponding to the device, and user certificate code corresponding to the device. The above-mentioned configuration type information may be adding a device type, deleting a device type or modifying a device type. The above-mentioned device name information may represent the subsidiary server identification. The above-mentioned updated device information set may be an updated device information set.

[0076] In the third step, the obtained updated device information set is determined as the device information set.

[0077] In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to update the device information set according to the device configuration information in response to receiving the device configuration information sent by the joint reporting client to obtain an updated device information set:

[0078] The first step is to verify the above-mentioned device configuration information to obtain verification result information. Among them, the above-mentioned verification result information can be the result after verifying the above-mentioned device configuration information. The above-mentioned verification result information can be a successful verification or a failed verification. In practice, in response to determining that the user name corresponding to the device included in the above-mentioned device configuration information exists in the various field values ​​corresponding to the supply user name field, the above-mentioned joint reporting service end can determine the successful verification as the verification result information. In response to determining that the user name corresponding to the device included in the above-mentioned device configuration information does not exist in the various field values ​​corresponding to the above-mentioned supply user name field, the failure of the verification can be determined as the verification result information. The various field values ​​corresponding to the above-mentioned supply user name field can be the various field values ​​corresponding to the supply user name field in the above-mentioned user association information set.

[0079] In the second step, in response to determining that the verification result information indicates that the verification is successful, the following steps are performed:

[0080] In the first updating step, in response to determining that the configuration type information included in the device configuration information is to delete device information, the device information corresponding to the device configuration information in the device information set is deleted to update the device information set to obtain an updated device information set.

[0081] The second updating step, in response to determining that the configuration type information included in the above device configuration information is to add device information, execute the following steps:

[0082] In the first sub-step, the device node name information, the user name corresponding to the device, the user certificate type corresponding to the device and the user certificate code corresponding to the device included in the above device configuration information are determined as device information.

[0083] The second sub-step is to add the determined device information to the device information set to update the device information set to obtain an updated device information set.

[0084] In a third updating step, in response to determining that the configuration type information included in the above device configuration information is to modify device information, the device node name information, the user name corresponding to the device, the user certificate type corresponding to the device, and the user certificate code corresponding to the device included in the device information corresponding to the above device configuration information are replaced with the device node name information, the user name corresponding to the device, the user certificate type corresponding to the device, and the user certificate code corresponding to the device included in the above device configuration information. The above device information may be the device information included in the above device information set.

[0085] In the third step, in response to determining that the verification result information indicates a verification failure, a verification failure prompt message is sent to the joint reporting client, wherein the verification failure prompt message may be a prompt message that prompts the user that the verification of the device configuration information has failed.

[0086] In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to implement data segmentation processing on each user combined associated information in the user combined associated information set to obtain each retained segmented data and each exchange segmented data set:

[0087] For each user combined association information set in the above-mentioned user combined association information sets, perform the following steps:

[0088] The first step is to initialize the preset segmentation value and the preset user segmentation information set. The preset segmentation value may be the number of participants in the joint reporting task. The preset user segmentation information set may be a set for storing user segmentation information. The user segmentation information may be data fragments obtained after data segmentation of the user combined associated information. In practice, the joint reporting server may empty the preset segmentation value and the preset user segmentation information set to initialize the preset segmentation value and the preset user segmentation information set.

[0089] In the second step, for each user merged association information in the above user merged association information set, perform the following steps:

[0090] In the first sub-step, the user combined association information is subjected to data segmentation processing according to the preset segmentation value to obtain preset segmentation value pieces of user segmentation information. The preset segmentation value pieces of user segmentation information may be data fragments obtained after data segmentation of the user combined association information.

[0091] In the second sub-step, the obtained preset segmentation value user segmentation information are added to the preset segmentation value preset user segmentation information set respectively.

[0092] The third step is to determine any one of the obtained preset segmentation value preset user segmentation information sets as the reserved segmentation data. The reserved segmentation data may be the preset user segmentation information set reserved in the joint reporting service end.

[0093] Step 4: determine each preset user segmentation information set different from the above-mentioned reserved segmentation data in the above-mentioned preset segmentation value preset user segmentation information sets as each exchange segmentation data. Wherein, the above-mentioned each exchange segmentation data can be each preset user segmentation information set for data exchange with the above-mentioned each joint reporting sub-server.

[0094] The fifth step is to determine the determined exchange segmentation data as an exchange segmentation data set.

[0095] In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to perform data segmentation processing on the user combined association information according to the preset segmentation value to obtain user segmentation information of the preset segmentation value:

[0096] In the first step, each field value in each field value included in the above user combined association information is split into a preset split value number of random numbers as a random number sequence to obtain each random number sequence. Among them, the field value in each field value included in the above user combined association information corresponds to the random number sequence in each random number sequence. The sum of each random number in the random number sequence can be equal to the field value corresponding to the above random number sequence.

[0097] In the second step, based on the obtained random number sequences, the following combination steps are performed:

[0098] In the first combining step, in response to determining that any one of the random number sequences is not empty, the following steps are performed:

[0099] In the first sub-step, a random number is arbitrarily selected from each of the random number sequences to obtain each random number.

[0100] The second sub-step is to determine each obtained random number as user segmentation information.

[0101] The third sub-step is to delete each of the obtained random numbers from the corresponding random number sequence to update each random number sequence to obtain each updated random number sequence, wherein each updated random number sequence is a random number sequence after deleting each of the random numbers.

[0102] The fourth sub-step is to use the above-mentioned updated random number sequences as respective random number sequences, and based on the respective random number sequences, execute the above-mentioned combining step again.

[0103] The second combining step is, in response to determining that any one of the random number sequences is empty, determining each obtained user segmentation information as a preset segmentation value number of user segmentation information.

[0104] Optionally, the joint reporting server may be further configured to perform the following steps:

[0105] For each of the above submission categories, perform the following steps:

[0106] The first step is to sort the various joint segmented data represented by the joint reporting information corresponding to the above-mentioned reporting category information according to the preset sorting information to obtain a sorted segmented data sequence. Among them, the preset sorting information can represent the sorting algorithm, sorting method and sorting value. The above-mentioned sorting method can be ascending or descending. The above-mentioned sorting value can represent the preset numerical joint segmented data with the top ranking. Here, there is no limitation on the specific setting of the above-mentioned preset numerical value. In practice, the above-mentioned joint reporting server can sort the various joint segmented data represented by the joint reporting information corresponding to the above-mentioned reporting category information according to the preset sorting information through the preset multi-party security sorting interface to obtain a sorted segmented data sequence. The above-mentioned preset multi-party security sorting interface can be a collaborative computing interface that encapsulates a sorting algorithm based on multi-party secure computing. For the above-mentioned joint reporting server, the input of the above-mentioned preset multi-party security sorting interface can be the preset sorting information, the various joint segmented data, and the identification information of the above-mentioned joint reporting server, and the output can be a sorted segmented data sequence. For each of the joint reporting sub-servers, the input of the preset multi-party secure sorting interface may be preset sorting information, each sub-joint segmentation data, and identification information of the joint reporting sub-server, and the output may be a sub-sorting segmentation data sequence. The above-mentioned each sub-joint segmentation data may be each joint segmentation data generated by the joint reporting sub-server.

[0107] The second step is, in response to receiving each sub-sorted segmented data sequence sent by each of the above-mentioned joint reporting sub-servers, aggregating the above-mentioned sorted segmented data sequence and each of the above-mentioned sub-sorted segmented data sequences to obtain an aggregated segmented data sequence. Among them, the above-mentioned aggregated segmented data sequence can be a sequence obtained by aggregating each field value corresponding to each aggregation field in the sorted segmented data sequence and each of the above-mentioned sub-sorted segmented data sequences. The individual aggregation fields included in the above-mentioned sorted segmented data sequence are the same as the individual aggregation fields included in each of the above-mentioned sub-sorted segmented data sequences. The above-mentioned individual aggregation fields can be the individual fields included in the user merged association information set corresponding to the above-mentioned reporting category information. In practice, the above-mentioned joint reporting server can be further configured to perform the following aggregation steps to achieve, in response to receiving each sub-sorted segmented data sequence sent by each of the above-mentioned joint reporting server, aggregating the above-mentioned sorted segmented data sequence and each of the above-mentioned sub-sorted segmented data sequences to obtain an aggregated segmented data sequence:

[0108] In the first aggregation step, for each sorted segmentation data in the above sorted segmentation data sequence, the following steps are performed:

[0109] In the first sub-step, each sub-sorted segmented data corresponding to the sorted segmented data in each sub-sorted segmented data sequence is determined as each sorted segmented data to be aggregated.

[0110] In the second sub-step, for each aggregate field in each aggregate field in the above-mentioned sorted and segmented data, the sum of the field value corresponding to the above-mentioned aggregate field in the above-mentioned sorted and segmented data and the respective field values ​​corresponding to the above-mentioned aggregate field in the above-mentioned each sorted and segmented data to be aggregated is determined as the aggregate field value, so as to obtain each aggregate field value.

[0111] In a third sub-step, each of the above-mentioned aggregate fields and each of the aggregate field values ​​corresponding to the above-mentioned aggregate fields are determined as aggregate segmentation data.

[0112] In the second aggregation step, each of the obtained aggregated segmented data is determined as an aggregated segmented data sequence.

[0113] The third step is to decode the obtained aggregate segmented data sequence to obtain a decoded segmented data sequence. The decoded segmented data sequence may be the decoded aggregate segmented data. When the reported category information represents a single customer in the same industry, the decoded segmented data in the decoded segmented data sequence may include but is not limited to one of the following: field classification field, field classification field corresponding field value, supply user name field, supply user name field corresponding field value, user name field, user name field corresponding field value, associated value field, associated value field corresponding field value.

[0114] The fourth step is to associate each decoded segmented data in the above decoded segmented data sequence with each standard user associated information in the above standard user associated information set to obtain each associated user information. In practice, for each decoded segmented data in the above decoded segmented data, the above joint reporting server can determine each standard user associated information whose field value corresponding to the user name field in the above standard user associated information is the target field value as each standard user associated information corresponding to the above decoded segmented data. The above target field value can be the field value corresponding to the user name field in the above decoded segmented data.

[0115] The fifth step is to determine the obtained information of each associated user as the reporting information.

[0116] In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to decode the obtained aggregated segmented data sequence to obtain a decoded segmented data sequence:

[0117] In the first step, for each aggregated segmentation data in the above aggregated segmentation data sequence, perform the following steps:

[0118] In the first sub-step, the preset field value corresponding to the field classification code in the preset field value and coding relationship information set and the preset field value included in the coding relationship information are determined as the target field classification field value. The field classification code can be the field value corresponding to the field classification field in the aggregated segmentation data.

[0119] In a second sub-step, the preset field value corresponding to the supply user name code in the above-mentioned preset field value and coding relationship information set and the preset field value included in the coding relationship information can be determined as the target supply user name field value. The above-mentioned supply user name code can be the field value corresponding to the supply user name field in the above-mentioned aggregated segmented data.

[0120] In the third sub-step, the preset field value corresponding to the user name code in the preset user name and code information set and the user name information included in the code relationship information can be determined as the target user name field value. The user name code can be the field value corresponding to the user name field in the aggregated segmentation data.

[0121] In the fourth sub-step, the field value corresponding to the domain classification field in the above-mentioned aggregated segmented data can be replaced with the above-mentioned target domain classification field value, the field value corresponding to the supply user name field can be replaced with the above-mentioned target supply user name field value, and the field value corresponding to the user name field can be replaced with the above-mentioned target user name field value to obtain decoded segmented data.

[0122] In the second step, each obtained decoded segmented data is determined as a decoded segmented data sequence.

[0123] Step 209: the joint reporting server sends each reporting category information to each joint reporting sub-server corresponding to each device information in the device information set.

[0124] In some embodiments, the joint reporting server may send the reporting category information to the joint reporting sub-servers corresponding to the device information according to a data transmission protocol. The data transmission protocol may be, but is not limited to, one of the following: HTTPS protocol, FTP protocol, WebSocket protocol.

[0125] It should be noted that the specific setting of the execution order of step 208 and step 209 is not limited. Step 208 can be executed before step 209, or after step 209, or simultaneously with step 209.

[0126] Step 210: In response to detecting a selection operation on the data confirmation control, each of the joint reporting sub-clients sends data confirmation information to the joint reporting sub-server.

[0127] In some embodiments, each of the above-mentioned joint reporting sub-clients may send data confirmation information to the above-mentioned joint reporting sub-server in response to detecting a selection operation on the above-mentioned data confirmation control. The above-mentioned data confirmation information may be prompt information prompting the above-mentioned joint reporting server that the data uploaded by the joint reporting sub-server is correct.

[0128] Step 211, each of the joint reporting sub-servers, in response to receiving data confirmation information sent by the joint reporting sub-client corresponding to the joint reporting sub-server, normalizes the sub-user association information set to obtain the normalized sub-user association information set as the standard sub-user association information set.

[0129] In some embodiments, each of the above-mentioned joint reporting sub-servers may, in response to receiving data confirmation information sent by the joint reporting sub-client corresponding to the above-mentioned joint reporting sub-server, perform normalization processing on the sub-user association information set to obtain the normalized sub-user association information set as the standard sub-user association information set. The above-mentioned standard sub-user association information set may be the normalized sub-user association information set.

[0130] In the process of adopting technical solutions to solve the above-mentioned technical problem one, the following technical problem two is often accompanied: the data reporting party uniformly processes the user-related data of each participant locally according to the data verification rules. Since the amount of user-related data of each participant is large and the data verification rules are numerous and complicated, the data processing efficiency is low and the security of the user-related data of each participant is low. In response to the above-mentioned technical problem two, the conventional solution is generally to select part of the user-related data of each participant for data processing. The inventor took into account the shortcomings of selecting part of the user-related data of each participant for data processing. In combination with the inventor's advantages in data processing, we decided to adopt the following solution:

[0131] In some optional implementations of some embodiments, each of the above-mentioned joint reporting sub-servers may be further configured to perform the following steps to achieve normalization of the sub-user association information set in response to receiving data confirmation information sent by the joint reporting sub-client corresponding to the above-mentioned joint reporting sub-server, and obtain the normalized sub-user association information set as the standard sub-user association information set:

[0132] The first step is to encrypt each field value corresponding to the user name field in each sub-user association information to obtain each encrypted user name information. Among them, the above-mentioned each sub-user association information is each sub-user association information included in the above-mentioned sub-user association information set. The above-mentioned each encrypted user name information can be each field value corresponding to the user name field in each encrypted sub-user association information. In practice, the above-mentioned joint reporting sub-server can use the MD5 encryption algorithm to encrypt each field value corresponding to the user name field in the above-mentioned sub-user association information set to obtain each encrypted user name information.

[0133] In the second step, for each encrypted user name information in the above encrypted user name information, perform the following steps:

[0134] In the first sub-step, the encrypted user name information and the preset query prompt information are determined as data query request information. The preset query prompt information may be prompt information for prompting the joint reporting server to query the relevant data in the joint reporting server. The relevant data may be a user basic information set or a set of abnormal and standard user name information in the joint reporting server. The data query request information may be a request for querying the relevant data.

[0135] The second sub-step is to send the above data query request information to the above joint reporting server.

[0136] The third sub-step is, in response to receiving the public key sent by the joint reporting service end, blinding the encrypted user name information according to the public key and the preset random number to obtain the blinded encrypted user name information. The blinded encrypted user name information may be the encrypted user name information encrypted by the public key. The public key may be the public key generated by the joint reporting service end through the RSA asymmetric encryption algorithm. The public key may include a first value and a second value. The greatest common divisor of the first value and the second value is 1. The preset random number may be a random number randomly generated by a random number generation algorithm. In practice, first, the joint reporting sub-server end may perform data conversion processing on the encrypted user name information through a preset data conversion interface to obtain the converted user name information. Then, the product of the first value power of the preset random number and the remainder of the modulus of the converted user name information to the second value may be determined as the blinded encrypted user name information. The preset data conversion interface may be an interface for converting the encrypted user name information into an integer value.

[0137] The fourth sub-step is to send the blinded encrypted user name information to the joint reporting server, so that the joint reporting server can sign the blinded encrypted user name information according to the private key.

[0138] The fifth sub-step, in response to receiving the signature blinded user encrypted information sent by the above-mentioned joint reporting server, deblinds the above-mentioned signature blinded user encrypted information according to the above-mentioned preset random number to obtain identification information corresponding to the above-mentioned encrypted user name information. Among them, the above-mentioned signature blinded user encrypted information can be obtained by the above-mentioned joint reporting server signing the above-mentioned blinded encrypted user name information according to the private key. The above-mentioned identification information can be the data ID of the standard user name information corresponding to the above-mentioned encrypted user name information in the relevant data of the above-mentioned joint reporting server. In practice, the above-mentioned joint reporting sub-server can determine the remainder of the quotient of the above-mentioned signature blinded user encrypted information and the above-mentioned preset random number modulo the above-mentioned second value as the identification information corresponding to the above-mentioned encrypted user name information.

[0139] The sixth sub-step is to send the data request information to the joint reporting server. The data request information may be prompt information for prompting the joint reporting server to generate a random number sequence.

[0140] The seventh sub-step, in response to receiving the random number sequence sent by the above-mentioned joint reporting server, performs blind positioning processing on each random number in the above-mentioned random number sequence according to the above-mentioned preset random number and the above-mentioned identification information, and obtains each blinded random number as a blinded random number sequence. Among them, the above-mentioned random number sequence can be each random number randomly generated by the above-mentioned joint reporting server. The number of the above-mentioned each random number is equal to the number of data rows of the above-mentioned related data. The above-mentioned blinded random number sequence can be a blinded random number sequence. In practice, the above-mentioned joint reporting sub-server can determine the sum of each random number in the above-mentioned random number sequence and the first numerical power of the above-mentioned preset random number as a blinded random number, and obtain each blinded random number as a blinded random number sequence.

[0141] The eighth sub-step is to send the above-mentioned blinded random number sequence to the above-mentioned joint reporting server.

[0142] The ninth sub-step, in response to receiving the query result information sent by the above-mentioned joint reporting server, performs a blinding process on each encrypted specification name information included in the above-mentioned query result information according to the above-mentioned preset random number to obtain the target specification name information. Among them, the above-mentioned query result information can be each signed specification user name information. The above-mentioned target specification name information can be the specification user name information obtained after blinding the signed specification user name whose row mark is the above-mentioned identification information. In practice, first, the above-mentioned joint reporting sub-server can determine the encrypted specification name information whose row mark is the above-mentioned identification information in the above-mentioned each encrypted specification name information as the target encrypted specification name information. Then, the first numerical power of the above-mentioned target encrypted specification name information can be determined as the target specification name information.

[0143] The tenth sub-step is to determine the obtained target standard name information as the standard user name information corresponding to the above-mentioned encrypted user name information.

[0144] The third step is to replace each field value corresponding to the above user name field in the above each sub-user association information with each obtained standard user name information, so as to normalize the above sub-user association information set, and obtain the sub-user association information set after normalization as the standard sub-user association information set.

[0145] The first to third steps of the above technical solution are an inventive point of the embodiment of the present disclosure, which solves the above technical problem 2 "resulting in low data processing efficiency and low security of user-related data of each participant". The factors that lead to low data processing efficiency and low security of user-related data are often as follows: the data reporting party uniformly processes the user-related data of each participant locally according to the data verification rules. Since the amount of user-related data of each participant is large and the data verification rules are numerous and complex. If the above factors are solved, the effect of improving data processing efficiency and the security of user-related data can be achieved. In order to achieve this effect, the present disclosure introduces a blind signature method based on asymmetric encryption, each participant blinds their own query data ID, and the data reporter signs the blinded query ID of each participant, so that the data reporter does not know the specific content queried by each participant, and each participant cannot obtain the original data of the data reporter, thereby improving the security of the data reporter and the user-related data of each participant. And the data reporter does not need to provide complex verification rules, thereby improving the data processing efficiency.

[0146] It should be noted that the specific setting of the execution order of step 209 and step 211 is not limited. Step 209 can be executed before step 211, or after step 211, or simultaneously with step 211.

[0147] Step 212, each of the joint reporting sub-servers, in response to receiving each reporting category information sent by the joint reporting server, classifies and merges the standard sub-user associated information set according to the received each reporting category information to obtain each sub-user merged associated information set.

[0148] In some embodiments, each of the above-mentioned joint reporting sub-servers can, in response to receiving each reporting category information sent by the above-mentioned joint reporting server, classify and merge the above-mentioned standard sub-user associated information set according to each received reporting category information to obtain each sub-user merged associated information set. Among them, the above-mentioned each sub-user merged associated information set can be each set obtained by classifying and merging the standard sub-user associated information set according to each preset classification information included in each reporting category information. Here, in response to receiving each reporting category information sent by the above-mentioned joint reporting server, classify and merge the above-mentioned standard sub-user associated information set according to each received reporting category information to obtain each sub-user merged associated information set. The specific steps can refer to the step in step 207 where the above-mentioned joint reporting server classifies and merges the above-mentioned user associated data according to each received reporting category information to obtain each user merged associated information set, which will not be repeated here.

[0149] Step 213: Each of the joint reporting sub-servers generates each sub-joint reporting information based on the combined associated information set of each sub-user.

[0150] In some embodiments, each of the above-mentioned joint reporting sub-servers may generate each sub-joint reporting information based on the above-mentioned combined associated information set of each sub-user, wherein the sub-joint reporting information in the above-mentioned sub-joint reporting information may represent each data fragment of associated information of each standard sub-user with a higher risk exposure.

[0151] In some optional implementations of some embodiments, each of the above-mentioned joint reporting sub-servers may be further configured to perform the following steps to generate each sub-joint reporting information based on the above-mentioned combined associated information sets of each sub-user:

[0152] For each sub-user combined association information set in each obtained sub-user combined association information set, perform the following steps:

[0153] The first step is to perform data segmentation processing on the sub-user merged association information in the above sub-user merged association information set to obtain each reserved sub-segmented data and each exchanged sub-segmented data set. The above each reserved sub-segmented data may be a set of data fragments retained in the above joint reporting sub-server. Here, the specific steps of performing data segmentation processing on the sub-user merged association information in the above sub-user merged association information set to obtain each reserved sub-segmented data and each exchanged sub-segmented data set can refer to the steps of performing data segmentation processing on each user merged association information in the above user merged association information set by the above joint reporting server to obtain each reserved segmented data and each exchanged segmented data set, which will not be repeated here.

[0154] The second step is to send the above-mentioned exchange sub-segmented data sets to the above-mentioned joint reporting server and each exchange sub-server respectively. The above-mentioned each exchange sub-server may be a joint reporting sub-server among the above-mentioned joint reporting sub-servers that is different from the above-mentioned joint reporting sub-server.

[0155] The third step is to generate each sub-joint segmented data as sub-joint reporting information according to the received exchange segmented data set, each exchange sub-segmented data set and each reserved sub-segmented data in response to receiving the exchange segmented data set corresponding to the sub-user combined association information set sent by the joint reporting server and each exchange sub-segmented data set sent by each exchange sub-server, through the preset joint reporting information generation interface, the joint reporting sub-server can generate each sub-joint segmented data as sub-joint reporting information according to the received exchange segmented data set, each exchange sub-segmented data set and each reserved sub-segmented data in response to receiving the exchange segmented data set corresponding to the sub-user combined association information set sent by the joint reporting server and each exchange sub-segmented data set sent by each exchange sub-server. For the joint reporting sub-server, the input of the preset joint reporting information generation interface can be the identification information of the joint reporting sub-server, the exchange segmented data set, each exchange sub-segmented data set and each reserved sub-segmented data, and the output can be each sub-joint segmented data. Among them, the identification information of the above-mentioned joint reporting sub-server can be the IP address of the above-mentioned joint reporting sub-server.

[0156] In the process of adopting technical solutions to solve the above-mentioned technical problem one, the following technical problem three is often accompanied: when the number of parties participating in the joint reporting of data is large, resulting in a large amount of user-related data. When there are a large amount of user-related data at risk, it leads to a large amount of reporting information. The reporting information is presented in the form of tables or files, resulting in users being unable to intuitively view the relevant data of each user at risk, resulting in a poor management user experience. For the above-mentioned technical problem three, the conventional solution is generally: only present user-related data with a higher risk level. The inventor took into account the disadvantages of only presenting user-related data with a higher risk level. In combination with the inventor's advantages in data visualization processing, we decided to adopt the following solution:

[0157] Optionally, the joint reporting client may be further configured to perform the following steps:

[0158] The first step is to display each reporting information monitoring template selection control in response to detecting a selection operation acting on the reporting information viewing control in each reporting information viewing control. The reporting information viewing control in each reporting information viewing control corresponds to the reporting category information in each reporting category information. The reporting information viewing control in each reporting information viewing control corresponds to the reporting information in each obtained reporting information. The each reporting information monitoring template selection control can be each control for selecting each reporting information monitoring template. The each reporting information monitoring template can be each monitoring template for visually monitoring the reporting information.

[0159] In the second step, in response to detecting the selection operation of the reporting information monitoring template selection control in each reporting information monitoring template selection control, the reporting information corresponding to the selected reporting information viewing control is obtained. In practice, first, the joint reporting client can determine the reporting information ID included in the preset reporting information and control information corresponding to the reporting information viewing control ID in the preset reporting information and control information set as the reporting information ID corresponding to the selected reporting information viewing control. Then, the reporting information corresponding to the reporting information ID corresponding to the selected reporting information viewing control can be determined as the reporting information corresponding to the selected reporting information viewing control. The reporting information viewing control ID can be the ID of the selected reporting information viewing control. The reporting information ID can represent the reporting information corresponding to the reporting information viewing control ID. The preset reporting information and control information set can represent the corresponding relationship between the reporting information viewing control ID and the reporting information ID. The preset reporting information and control information in the preset reporting information and control information set can include the reporting information viewing control ID and the reporting information ID corresponding to the reporting information viewing control ID.

[0160] The third step is to select the reporting information monitoring template corresponding to the control according to the selected reporting information monitoring template, perform data normalization processing on the reporting information corresponding to the selected reporting information viewing control, and obtain the reporting information after data normalization processing. Among them, the above-mentioned reporting information monitoring template may include each normalization field and each normalization method corresponding to each normalization field. The above-mentioned each normalization method may be a normalization function. Here, there is no limitation on the specific settings of the above-mentioned each normalization method. For example, the normalization method may be y=(x-min) / (max-min). Among them, x may be the field value of the field corresponding to the normalization method. min may be the minimum field value of the field corresponding to the normalization method. max may be the maximum field value of the field corresponding to the normalization method. y may be x after normalization processing. At this time, the value range of y may be [0,1]. In practice, for each normalized field in each normalized field included in the above-mentioned reporting information monitoring template, first, the above-mentioned joint reporting client can input each field value corresponding to the above-mentioned normalized field in the above-mentioned reporting information into the normalization function corresponding to the above-mentioned normalized field to obtain each normalized field value. Then, each field value corresponding to the above-mentioned normalized field in the above-mentioned reporting information can be replaced with each normalized field value to perform data normalization processing on the reporting information corresponding to the selected reporting information viewing control to obtain the reporting information after data normalization processing.

[0161] The fourth step is to select the reporting information monitoring template corresponding to the control according to the selected reporting information monitoring template, perform data aggregation processing on the reporting information after data normalization processing, and obtain the reporting information after data aggregation processing. The above-mentioned reporting information monitoring template may also include an aggregation function. For example, the aggregation function may be sum (SUM), count (COUNT), average (AVG), maximum value (MAX), minimum value (MIN), etc. In practice, the above-mentioned joint reporting client may perform data aggregation processing on the reporting information after data normalization processing according to the aggregation function included in the above-mentioned reporting information monitoring template, and obtain the reporting information after data aggregation processing.

[0162] In the fifth step, according to the selected reporting information monitoring template, the reporting information corresponding to the control is selected, and data conversion processing is performed on the reporting information after data aggregation processing to obtain the reporting information after data conversion processing. Among them, the above-mentioned reporting information monitoring template may also include a data conversion field and a data conversion algorithm. The above-mentioned data conversion field may be a field whose data type needs to be converted. For example, the data conversion algorithm may be a hot single encoding, which can convert text type data into numeric type data.

[0163] Step 6: According to the selected reporting information monitoring template, select the reporting information monitoring template corresponding to the control, and perform visual monitoring on the reporting information after data conversion. The above-mentioned reporting information monitoring template may also include a visualization chart type. For example, the visualization chart type may be a bar chart, a pie chart, a heat map, a dashboard, etc. Thus, the user can view the reporting information more intuitively.

[0164] The relevant contents of the first to sixth steps of the above technical solution are an inventive point of the embodiment of the present disclosure, which solves the above technical problem three "causing users to be unable to intuitively view the relevant data of each user with risks, resulting in a poor user experience of management". The factors that lead to poor user experience are often as follows: when the number of participants participating in the joint reporting of data is large, resulting in a large amount of user-related data, when there are a large number of user-related data with risks, resulting in a large amount of reported information, and presenting the reported information in the form of a table or file, resulting in the user being unable to intuitively view the relevant data of each user with risks. If the above factors are solved, the effect of improving the user experience can be achieved. In order to achieve this effect, the present disclosure introduces visual monitoring reporting information, and users can select appropriate monitoring templates according to their needs. The monitoring template visualizes the reported data, further integrates the reported information, and improves the efficiency of further analyzing the reported data. The reported information is displayed in the form of a visual chart, and the user can more intuitively view the relevant data of each user with risks in the reported information, thereby enhancing the user experience.

[0165] The above-mentioned embodiments of the present disclosure have the following beneficial effects: through the user data joint reporting system of some embodiments of the present disclosure, the CPU utilization rate of each participant and the security of user-related data are improved, thereby reducing the waste of CPU resources used by each participant. Specifically, the reasons for the low CPU utilization rate of each participant, the low security of user-related data of each participant, and the waste of CPU resources used by each participant are: the data reporter obtains the user-related data of each participant in plain text, and summarizes and calculates the processed user-related data in plain text, and the user-related data of each participant is all exposed to the data reporter, resulting in low security of the user-related data of each participant. Moreover, the processing and summary calculation of all data are performed by the data reporter, resulting in low CPU utilization rate of each participant and wasting CPU resources used by each participant. Based on this, the user data joint reporting system of some embodiments of the present disclosure includes a joint reporting client, a joint reporting server, each joint reporting sub-client and each joint reporting sub-server; and the above-mentioned joint reporting client is configured to first, in response to detecting a selection operation acting on the joint reporting task start control, send the joint reporting task start information to the above-mentioned joint reporting server. In this way, the joint reporting server can be notified to start the joint reporting task. Then, in response to detecting a selection operation acting on the reporting category selection control in each reporting category selection control, the reporting category information corresponding to the selected reporting category selection control is sent to the above-mentioned joint reporting server. In this way, the joint reporting server can be notified of the reporting category selected by the user. The above-mentioned joint reporting server is configured to first, in response to receiving the joint reporting task start information sent by the above-mentioned joint reporting client, load user-related data according to the first preset data loading source, and obtain a device information set. In this way, the original data and device information set corresponding to the reporting task can be obtained. Then, the above-mentioned joint reporting task activation information is sent to each joint reporting sub-server corresponding to each device information in the above-mentioned device information set. In this way, each joint reporting sub-server can know that the reporting task has been activated and can prepare the original data corresponding to the reporting task. Afterwards, according to the received reporting category information, the above-mentioned user-related data is classified and merged to obtain each user-merged associated information set. In this way, each user-merged associated information set can be obtained, which can be used to generate each joint reporting information. Finally, based on the above-mentioned each user-merged associated information set, each joint reporting information is generated. In this way, each joint reporting information can be obtained, wherein the joint reporting information in the above-mentioned each joint reporting information can represent the data fragments of each user-related information with a higher risk exposure.Each of the above-mentioned joint reporting sub-clients is configured to first, in response to receiving the data loading success information sent by the joint reporting sub-server corresponding to the above-mentioned joint reporting sub-client, display the data confirmation control on the data loading page. Thus, the user can select the data confirmation control. Then, in response to detecting the selection operation acting on the above-mentioned data confirmation control, the data confirmation information is sent to the above-mentioned joint reporting sub-server. Thus, the above-mentioned joint reporting server can know that the original data uploaded by the joint reporting sub-server is correct. Each of the above-mentioned joint reporting sub-servers is configured to first, in response to receiving the joint reporting task start information sent by the above-mentioned joint reporting server, load the sub-user association information set from the second preset data loading source. Thus, the original data of the joint reporting sub-server corresponding to the reporting task can be obtained. Then, in response to receiving the data confirmation information sent by the joint reporting sub-client corresponding to the above-mentioned joint reporting sub-server, the sub-user association information set is normalized, and the sub-user association information set after normalization is obtained as the standard sub-user association information set. Thus, a set of standard sub-user associated information can be obtained. The above-mentioned set of standard sub-user associated information can be a set of sub-user associated information after normalization. Afterwards, in response to receiving each reporting category information sent by the above-mentioned joint reporting service end, the above-mentioned set of standard sub-user associated information is classified and merged according to each reported category information received, so as to obtain each sub-user merged associated information set. Thus, each sub-user merged associated information set can be obtained. The above-mentioned each sub-user merged associated information set can be each set obtained by classifying and merging the standard sub-user associated information set according to each preset classification information included in each reporting category information. Finally, each sub-joint reporting information is generated based on the above-mentioned each sub-user merged associated information set. Thus, each sub-joint reporting information can be obtained. The sub-joint reporting information in the above-mentioned each sub-joint reporting information can represent the data fragments of each standard sub-user associated information with a higher risk exposure. Also, because the user data joint reporting system implemented can unite the data reporter (joint reporting server) and each participant (each joint reporting sub-server), each participant participates in the data processing and reporting information generation, instead of only the data reporter processing all data and generating reporting information, thus improving the CPU utilization of each participant and reducing the waste of CPU resources of each participant. And the data of the data reporter and each participant are exchanged in a confidential state (fragmented state). During the data processing process, the data reporter does not know the data queried by each participant, and the original data of the data reporter will not be exposed to each participant.Moreover, during the process of generating reported information, neither the data reporter nor any of the participating parties can deduce the original data of other parties based on their own data, thereby improving the security of user-related data of each participating party.

[0166] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0167] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0168] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0169] The above descriptions are only some preferred embodiments of the present disclosure and an explanation of the technical principles used. Those skilled in the art should understand that the scope of the invention involved in the embodiments of the present disclosure is not limited to the technical solutions formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above inventive concept. For example, the above features are replaced with (but not limited to) technical features with similar functions disclosed in the embodiments of the present disclosure.

Claims

1. A user data joint reporting system, comprising a joint reporting client, a joint reporting server, each joint reporting sub-client and each joint reporting sub-server; and the joint reporting client is configured to, in response to detecting a selection operation acting on a joint reporting task start control, send joint reporting task start information to the joint reporting server; in response to detecting a selection operation acting on a reporting category selection control in each reporting category selection control, send reporting category information corresponding to the selected reporting category selection control to the joint reporting server; The joint reporting server is configured to, in response to receiving the joint reporting task start information sent by the joint reporting client, load the user-related data according to the first preset data loading source, and obtain the device information set; send the joint reporting task start information to each joint reporting sub-server corresponding to each device information in the device information set; classify and merge the user-related data according to each received reporting category information to obtain each user merged association information set; send each reporting category information to each joint reporting sub-server corresponding to each device information in the device information set; generate each joint reporting information based on each user merged association information set; Each of the joint reporting sub-clients is configured to, in response to receiving a data loading success message sent by the joint reporting sub-server corresponding to the joint reporting sub-client, display a data confirmation control on the data loading page; in response to detecting a selection operation acting on the data confirmation control, send data confirmation information to the joint reporting sub-server; Each of the joint reporting sub-servers is configured to, in response to receiving the joint reporting task start information sent by the joint reporting server, load the sub-user association information set from the second preset data loading source; in response to receiving the data confirmation information sent by the joint reporting sub-client corresponding to the joint reporting sub-server, normalize the sub-user association information set to obtain the normalized sub-user association information set as the standard sub-user association information set; in response to receiving each reporting category information sent by the joint reporting server, classify and merge the standard sub-user association information set according to the received each reporting category information to obtain each sub-user merged association information set; and generate each sub-joint reporting information based on the each sub-user merged association information set.

2. The user data joint reporting system according to claim 1, wherein: The joint reporting server is further configured to: According to the first preset data loading source, a user basic information set, a user association information set, and an abnormal and standard user name information set are loaded into the memory, wherein the user basic information in the user basic information set includes various fields and field values ​​corresponding to various fields; For each user association information in the user association information set, perform the following data cleaning steps: According to a preset keyword set, the user-related information is normalized to obtain normalized user-related information; In response to determining that the normalized user association information meets the preset association condition, determining whether the associated user name field included in the normalized user association information is empty; In response to determining that the associated user name field included in the normalized user association information is empty, performing information filling processing on the normalized user association information to obtain the user association information after the information filling processing as standard user association information; In response to determining that the associated user name field included in the normalized user association information is not empty, determining the normalized user association information as standard user association information; Determine the obtained individual standard user association information as a standard user association information set; The standard user association information set, the user basic information set and the abnormal and standard user name information set are determined as user association data.

3. The user data joint reporting system according to claim 1, wherein: Each of the joint reporting sub-servers is further configured to: According to the second preset data loading source, the sub-user association information set is loaded into the memory; Performing data verification processing on the sub-user association information set to obtain a data verification result; In response to determining that the data verification result indicates a successful verification, sending a data loading success message to the joint reporting sub-client corresponding to the joint reporting sub-server; In response to determining that the data verification result indicates a verification failure, data loading failure information is sent to the joint reporting sub-client corresponding to the joint reporting sub-server.

4. The user data joint reporting system according to claim 2, wherein: The joint reporting server is further configured to: In response to receiving each data query request information sent by the joint reporting sub-servers among the joint reporting sub-servers, generating each query result information according to the user basic information set and the abnormal and standard user name information set included in the user association data, and sending each query result information to the joint reporting sub-server; In response to receiving the device configuration information sent by the joint reporting client, updating the device information set according to the device configuration information to obtain an updated device information set; The obtained updated device information set is determined as the device information set.

5. The user data joint reporting system according to claim 4, wherein: The device configuration information includes configuration type information, device node name information, user name corresponding to the device, user certificate type corresponding to the device, and user certificate code corresponding to the device; and the joint reporting server is further configured to: Performing verification processing on the device configuration information to obtain verification result information; In response to determining that the verification result information indicates that the verification is successful, performing the following steps: In response to determining that the configuration type information included in the device configuration information is to delete device information, deleting the device information corresponding to the device configuration information in the device information set, so as to update the device information set and obtain an updated device information set; In response to determining that the configuration type information included in the device configuration information is adding device information, performing the following steps: Determine the device node name information, the user name corresponding to the device, the user certificate type corresponding to the device, and the user certificate code corresponding to the device included in the device configuration information as the device information; Adding the determined device information to the device information set to update the device information set to obtain an updated device information set; In response to determining that the configuration type information included in the device configuration information is modified device information, replacing the device node name information, the user name corresponding to the device, the user certificate type corresponding to the device, and the user certificate code corresponding to the device included in the device information corresponding to the device configuration information with the device node name information, the user name corresponding to the device, the user certificate type corresponding to the device, and the user certificate code corresponding to the device included in the device configuration information, so as to update the device information set to obtain an updated device information set, wherein the device information is the device information included in the device information set; In response to determining that the verification result information indicates a verification failure, verification failure prompt information is sent to the joint reporting client.

6. The user data joint reporting system according to claim 2, wherein: The reporting category information in each reporting category information includes preset classification information, the standard user association information in the standard user association information set includes each field and a field value corresponding to each field; and the joint reporting server is further configured to: Get the preset field value and encoding relationship information set; Sending the preset field value and the coding relationship information set to each of the joint reporting sub-servers; For each of the various types of reporting information, perform the following steps: According to the preset classification information included in the reported category information, classify each standard user association information in the standard user association information set to obtain each user association information set, wherein the preset classification information includes each classification field, and the user association information set in each user association information set includes each standard user association information; For each user association information set in the respective user association information sets, the following steps are performed: Merging the field values ​​corresponding to the user association value fields in the standard user association information in the user association information set to obtain merged user association value information; Determine any one of the standard user association information in the user association information set as the target user association information; According to the merged user association value information, the preset field value and the coding relationship information set, the determined target user association information is changed to obtain the changed user association information as the user merged association information; The obtained respective user combined association information is determined as a user combined association information set.

7. The user data joint reporting system according to claim 1, wherein: The joint reporting server is further configured to: For each user combined association information set in each user combined association information set, the following steps are performed: Performing data segmentation processing on each user combined associated information in the user combined associated information set to obtain each retained segmented data and each exchange segmented data set; Sending each of the exchange segmentation data sets to each of the joint reporting sub-servers respectively; In response to receiving the respective sub-exchange segmented data sets corresponding to the respective reserved segmented data sent by the respective joint reporting sub-servers, the respective joint segmented data are generated as joint reporting information based on the respective reserved segmented data and the respective sub-exchange segmented data sets.

8. The user data joint reporting system according to claim 5, wherein: The reporting category information in each reporting category information corresponds to the sub-user combined association information set in each obtained sub-user combined association information set; and each joint reporting sub-server in each joint reporting sub-server is further configured to: For each sub-user combined association information set in each obtained sub-user combined association information set, perform the following steps: Performing data segmentation processing on the sub-user combined association information in the sub-user combined association information set to obtain each reserved sub-segmented data set and each exchanged sub-segmented data set; Sending the respective exchange sub-segmented data sets to the joint reporting server and the respective exchange sub-servers, respectively, wherein the respective exchange sub-servers are the respective joint reporting sub-servers among the respective joint reporting sub-servers that are different from the joint reporting sub-server; In response to receiving the exchange segmentation data set corresponding to the sub-user merged association information set sent by the joint reporting server, and the individual exchange sub-segmentation data sets sent by the individual exchange sub-servers, the individual sub-joint segmentation data are generated as sub-joint reporting information based on the received exchange segmentation data set, the individual exchange sub-segmentation data sets and the individual retained sub-segmentation data.

9. The user data joint reporting system according to claim 7, wherein: The joint reporting server is further configured to: For each user combined association information set in each user combined association information set, the following steps are performed: Initialize the preset segmentation value and the preset user segmentation information set; For each user combined association information in the user combined association information set, the following steps are performed: According to the preset segmentation value, data segmentation processing is performed on the user combined association information to obtain user segmentation information of the preset segmentation value; Adding the obtained preset segmentation value user segmentation information to the preset segmentation value preset user segmentation information set respectively; Determine any one of the obtained preset segmentation value preset user segmentation information sets as the reserved segmentation data; Determine each preset user segmentation information set different from the reserved segmentation data in the preset segmentation value number of preset user segmentation information sets as each exchange segmentation data; The determined exchange segmentation data are determined as an exchange segmentation data set.

10. The user data joint reporting system according to claim 4, wherein: The joint reporting server is further configured to: For each of the various types of reporting information, perform the following steps: According to the preset sorting information, each joint segmented data represented by the joint reporting information corresponding to the reporting category information is sorted to obtain a sorted segmented data sequence; In response to receiving each sub-sorted segmented data sequence sent by each joint reporting sub-server, aggregating the sorted segmented data sequence and each sub-sorted segmented data sequence to obtain an aggregated segmented data sequence; Decoding the obtained aggregated segmented data sequence to obtain a decoded segmented data sequence; Associating each decoded segmented data in the decoded segmented data sequence with each standard user associated information in the standard user associated information set to obtain each associated user information; The obtained information of each associated user is determined as the reporting information.

Images