CN119440861A

CN119440861A - User data joint reporting system

Info

Publication number: CN119440861A
Application number: CN202510039132.3A
Authority: CN
Inventors: 郑植; 徐崚峰; 吴中彪; 王欢; 张骏仪; 于新利; 侯敏; 岳丰; 刘殿兴; 师建兴; 黄美艺; 罗安扬; 郑阿敏
Original assignee: Citic Corp Of China; Citic Securities Co ltd
Current assignee: Citic Corp Of China; Citic Securities Co ltd
Priority date: 2025-01-10
Filing date: 2025-01-10
Publication date: 2025-02-14
Anticipated expiration: 2045-01-10
Also published as: CN119440861B

Abstract

The embodiment of the disclosure discloses a user data joint reporting system. The system comprises a joint reporting client, a joint reporting server, joint reporting sub-clients and joint reporting sub-servers, wherein the joint reporting server is configured to respond to receiving joint reporting task starting information sent by the joint reporting client and load user associated data, the joint reporting task starting information is respectively sent to the joint reporting sub-servers corresponding to equipment information sets, classification and combination processing are carried out on the user associated data according to the received reporting category information to obtain user combined associated information sets, the reporting category information is sent to the joint reporting sub-servers corresponding to the equipment information sets, and the joint reporting information is generated based on the user combined associated information sets. The embodiment improves the CPU utilization rate of each participant and the safety of the user related data.

Description

User data joint reporting system

Technical Field

The embodiment of the disclosure relates to the technical field of computers, in particular to a user data joint reporting system.

Background

The user data joint reporting refers to that a data reporting party (parent company) joins each party (subsidiary company), performs summary calculation on user related data of each party, and generates reporting information. At present, user data joint reporting mainly obtains user related data of each participant through a data reporting party plaintext, performs data processing on the user related data of each participant in a unified manner according to a data verification rule locally, performs summarization calculation on the processed user related data in the data reporting party local plaintext to obtain reporting information, and reports the reporting information in a form of a table or a file.

However, in practice, it is found that when the above manner is adopted to perform user data joint reporting, the following technical problems often exist:

The data reporting party obtains the user related data of each participant in a clear text mode, the clear text carries out summarization calculation on the processed user related data, and the user related data of each participant are all exposed to the data reporting party, so that the safety of the user related data of each participant is lower. And the processing and summarizing calculation of all data are carried out by the data reporting party, so that the CPU utilization rate of each participant is lower, and the CPU utilization resources of each participant are wasted.

The above information disclosed in this background section is only for enhancement of understanding of the background of the inventive concept and, therefore, may contain information that does not form the prior art that is already known to those of ordinary skill in the art in this country.

Disclosure of Invention

The disclosure is in part intended to introduce concepts in a simplified form that are further described below in the detailed description. The disclosure is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

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

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, respective joint reporting sub-clients, and respective joint reporting sub-servers, the joint reporting client configured to transmit joint reporting task start information to the joint reporting server in response to detecting a selection operation acting on a joint reporting task start control, transmit reporting category information corresponding to the selected reporting category selection control to the joint reporting server in response to detecting a selection operation acting on a reporting category selection control, the joint reporting server configured to load user-related data in response to receiving the joint reporting task start information transmitted by the joint reporting client, and acquire a set of device information, transmit the joint reporting task start information to respective joint reporting sub-servers corresponding to respective device information in the set of device information in response to detecting a selection operation acting on a reporting category selection control, process the user-related data in response to detecting a respective reporting category selection control, to transmit the selected reporting category information corresponding to the joint reporting service control, the joint reporting server is configured to transmit the joint reporting task start information corresponding to the joint reporting client, load user-related data in accordance with a first preset data load source, and acquire a set of device information, transmit the joint reporting task start information to respective device information, process the respective user-related data in response to received from the joint reporting sub-related data set, and combine the respective user-related data is associated with respective user-related information in response to the respective user-related sub-server, and the joint reporting sub-information is configured to receive the respective user-related information, the method comprises the steps of displaying a data confirmation control on a data loading page, sending data confirmation information to the joint reporting sub-server in response to detection of selection operation acting on the data confirmation control, enabling each joint reporting sub-server in the joint reporting sub-server to be configured to load a sub-user associated information set from a second preset data loading source in response to receiving joint reporting task starting information sent by the joint reporting sub-server, enabling the sub-user associated information set to be normalized in response to receiving the data confirmation information sent by a joint reporting sub-client corresponding to the joint reporting sub-server, obtaining normalized sub-user associated information set to serve as a standard sub-user associated information set, enabling the standard sub-user associated information set to be classified and combined according to the received reporting category information in response to receiving the reporting category information sent by the joint reporting sub-server, and generating the sub-user associated information set based on the sub-user associated information set.

The above embodiments of the present disclosure have the following beneficial effects that 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 the user related data are improved, so that the waste of the resources used by the CPU of each participant is reduced. Specifically, the reasons for the lower CPU utilization rate of each participant and the lower safety of the user-related data of each participant and the waste of the resources used by each participant CPU are that the data reporting party obtains the user-related data of each participant in the clear text, and the clear text performs the summarization calculation on the processed user-related data, and the user-related data of each participant is totally exposed to the data reporting party, so that the safety of the user-related data of each participant is lower. And the processing and summarizing calculation of all data are carried out by the data reporting party, so that the CPU utilization rate of each participant is lower, and the CPU utilization resources of each participant are wasted. 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 joint reporting client is configured to first send joint reporting task opening information to the joint reporting server in response to detecting a selection operation acting on a joint reporting task opening control. Therefore, the joint reporting server can be informed to start the joint reporting task. And then, responding to the detection of the selection operation acting on the reporting category selection control in each reporting category selection control, and sending the reporting category information corresponding to the selected reporting category selection control to the combined reporting server. Thus, the combined reporting server user can be informed of the selected reporting category. The joint reporting server is configured to firstly, in response to receiving joint reporting task starting information sent by the joint reporting client, load user associated data according to a first preset data loading source and acquire a device information set. Thus, the original data and the equipment information set corresponding to the reporting task can be obtained. And then, the joint reporting task starting information is respectively sent to each joint reporting sub-server corresponding to each piece of equipment information in the equipment information set. Therefore, each combined reporting sub-server can know that the reporting task is started, and can prepare the original data corresponding to the reporting task. And then, classifying and combining the user associated data according to the received reporting category information to obtain the user combined associated information set. Thus, the user merging associated information set can be obtained and can be used for generating the joint report information. And finally, combining the associated information sets based on the users to generate the combined reporting information. Therefore, each piece of combined report information can be obtained, wherein the combined report information in each piece of combined report information can represent the data fragments of each piece of user associated information with higher risk exposure. Each of the above-mentioned individual joint reporting sub-clients is configured to first display a data confirmation control on a data loading page 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. Thus, the user can be enabled to select the data confirmation control. And then, in response to detecting the selection operation acting on the data confirmation control, sending the data confirmation information to the joint reporting sub-server. Therefore, the combined reporting server can know that the original data uploaded by the combined reporting sub-server is correct. Each of the above-mentioned individual joint reporting sub-servers is configured to first load a sub-user association information set from a second preset data loading source in response to receiving the joint reporting task start information sent by the above-mentioned joint reporting server. Therefore, the original data of the combined reporting sub-server corresponding to the reporting task can be obtained. And then, in response to receiving the data confirmation information sent by the joint reporting sub-client corresponding to the joint reporting sub-server, carrying out standardization processing on the sub-user associated information set to obtain the standardized sub-user associated information set as a standard sub-user associated information set. Thus, a standard set of sub-user association information can be obtained. The standard sub-user associated information set may be a normalized sub-user associated information set. And then, responding to the received reporting category information sent by the combined reporting server, and carrying out classification and combination processing on the standard sub-user associated information set according to the received reporting category information to obtain each sub-user combined associated information set. Thus, the combined associated information set of each sub-user can be obtained. The above sub-user merging associated information sets may be sets obtained by classifying and merging standard sub-user associated information sets according to preset classification information included in the reporting category information. And finally, combining the associated information sets based on the sub-users to generate sub-combined reporting information. Thus, each sub-joint report information can be obtained. The sub-joint reporting information in the sub-joint reporting information can represent data fragments of the related information of each standard sub-user with higher risk exposure. Because the realized user data joint reporting system can combine the data reporting party (joint reporting server) and each participant (each joint reporting sub-server), each participant participates in the processing of the execution data and the generation of reporting information, rather than only one party of the data reporting party processes all the data and generates reporting information, the utilization rate of the CPU of each participant is improved, and the waste of the CPU used resources of each participant is reduced. And the data reporting party and the data of each participant exchange data in a secret state (fragmentation state). In the data processing process, the data reporting party does not know the data queried by each participant, and the original data of the data reporting party is not exposed to each participant. In the process of generating the report information, any one of the data reporting party and each participant cannot deduce the original data of other parties according to the data of the data reporting party and each participant, so that the safety of the user related data of each participant is improved.

Drawings

The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by reference to the following detailed description when taken in conjunction with the accompanying drawings. The same or similar reference numbers will be used throughout the drawings to refer to the same or like elements. It should be understood that the figures are schematic and that elements and components are not necessarily drawn to scale.

FIG. 1 is a schematic diagram of some embodiments of a user data consolidated delivery system according to the present disclosure;

fig. 2 is a timing diagram of some embodiments of a user data consolidated delivery system according to the present disclosure.

Detailed Description

Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete. It should be understood that the drawings and embodiments of the present disclosure are for illustration purposes only and are not intended to limit the scope of the present disclosure.

It should be noted that, for convenience of description, only the portions related to the present invention are shown in the drawings. Embodiments of the present disclosure and features of embodiments may be combined with each other without conflict.

It should be noted that the terms "first," "second," and the like in this disclosure are merely used to distinguish between different devices, modules, or units and are not used to define an order or interdependence of functions performed by the devices, modules, or units.

It should be noted that references to "one", "a plurality" and "a plurality" in this disclosure are intended to be illustrative rather than limiting, and those of ordinary skill in the art will appreciate that "one or more" is intended to be understood as "one or more" unless the context clearly indicates otherwise.

The names of messages or information interacted between the various devices in the embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of such messages or information.

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

Fig. 1 illustrates a schematic diagram of some embodiments of a user data consolidated delivery system according to the present disclosure.

As shown in fig. 1, 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 joint delivery client 3 may be a delivery system client of a parent company. The joint reporting server 4 may be a reporting system server of a parent company. The joint reporting sub-clients 1 may be reporting system clients of the respective sub-companies of the parent company. The joint reporting sub-server 2 may be a reporting system server of each sub-company of the parent company. The joint reporting server 4 is respectively in communication connection with the joint reporting client 3 and each joint reporting sub-server 2. The joint reporting sub-servers in the joint reporting sub-servers 2 are in one-to-one correspondence with the joint reporting sub-clients in the joint reporting sub-clients 1. The joint reporting sub-server in each joint reporting sub-server 2 is in communication connection with the joint reporting sub-client in each joint reporting sub-client 1.

Referring now to fig. 2, a timing diagram of a user data consolidated reporting system of the present disclosure is shown.

As shown in FIG. 2, the user data joint reporting system comprises each joint reporting sub-client, each joint reporting sub-server, a joint reporting client and a joint reporting server. The step of interaction among the above-mentioned each joint messaging sub-client, each joint messaging sub-server, the joint messaging client and the joint messaging server may include the steps of:

In some embodiments, the federated reporting client may be configured to perform the steps of:

In step 201, the joint reporting client sends the joint reporting task opening information to the joint reporting server in response to detecting the selection operation acting on the joint reporting task opening control.

In some embodiments, the joint reporting client may send the joint reporting task opening information to the joint reporting server in response to detecting a selection operation acting on the joint reporting task opening control. The control for opening the joint reporting task can be a control for opening the joint reporting task. The selection operation may be, but is not limited to, one of clicking, sliding. The above-mentioned combined report task opening information may be a prompt message for prompting that the combined report task has been opened. In practice, in response to detecting a selection operation acting on the joint reporting task opening control, the joint reporting client may use a data transmission protocol, and the joint reporting task opening information is sent to the joint reporting server. The data transmission protocol may be, but is not limited to, one of the following, HTTPS protocol, FTP protocol, webSocket protocol.

Step 202, the joint reporting server responds to receiving joint reporting task starting information sent by the joint reporting client, loads user associated data according to a first preset data loading source, and acquires a device information set.

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 associated data according to a first preset data loading source, and acquire a device information set. 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 report task may be a task of reporting the respective users with higher risk exposure amounts of the parent company and the respective subsidiary companies to the parent company. The user-related data may be user-related data associated with a messaging task. The user-associated data may include a set of user-base information, a set of user-associated information, and a set of abnormal and canonical user name information. The set of user base information may characterize individual base information for individual users. The user basic information in the user basic information set may include each field and a field value corresponding to each field. The various fields described above may include, but are not limited to, a user name field, a user credential type field, a user credential code field, whether it is an associated party field, an associated user name field, an associated value field, whether it is the same domain field, a domain classification field, a provisioning user name field. The above-mentioned whether is the association party field can characterize whether there is an association relation between the user corresponding to the user name field in the user association information and the company corresponding to the execution subject. For example, whether the field value corresponding to the association party field is "1-yes" or "0-no" may be mentioned. The above-mentioned association user name field may characterize a user name having an association relationship with a company corresponding to the subject of execution. The set of user-associated information may be individual value-related information characterizing individual users. The user association information in the user association information set may include each association field and a field value corresponding to each association field. The various associated fields described above may include, but are not limited to, a plurality of user name fields, user credential type fields, user credential code fields, business category code fields, associated value fields. For example, the business category code field may characterize a transaction category code and the associated value field may characterize a risk exposure. The abnormal and canonical user name information set may characterize a correspondence between an abnormal user name and a canonical user name. The abnormal and canonical user name information in the abnormal and canonical user name information set may include an abnormal user name and a canonical user name corresponding to the abnormal user name. The abnormal user name may be a user name whose naming is not standard. The device information set may be each device participating in a joint reporting task. Each device may include a respective consolidated reporting sub-server. The device information in the respective device information may include, but is not limited to, device node name information, company name corresponding to the device, sub-company certificate type corresponding to the device, and sub-company certificate code corresponding to the device. The device node name information may include level attribute information of a company to which the device corresponds. For example, the level attribute information may be a subsidiary or a parent. In practice, the joint reporting server may obtain the device information set from the associated database.

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

And the first step is to load the user basic information set, the user associated information set and the abnormal and standard user name information set into the memory according to the first preset data loading source.

Second, for each user-associated information in the user-associated information set, the following data cleansing step is performed:

And a first sub-step, carrying out standardization processing on the user associated information according to a preset keyword set to obtain the user associated information after standardization processing. The preset keyword set may represent each preset keyword that may not be included in a field value corresponding to a user name field in the user association information. For example, the preset keywords in the respective preset keywords may be, but not limited to, one of business departments, branch offices, branches. In practice, the joint reporting server may delete each preset keyword included in the field value corresponding to the user name field in the user associated information, so as to normalize the user associated information, and obtain normalized user associated information.

And a second sub-step of determining whether an associated user name field included in the normalized user association information is empty in response to determining that the normalized user association information satisfies a preset association condition. The preset association condition may be whether the field value corresponding to the association party field in the normalized user association information is "1-yes".

And a third sub-step of performing information filling processing on the normalized user-related information in response to determining that the related user name field included in the normalized user-related information is empty, and obtaining the information-filled user-related information as standard user-related information. In practice, first, in response to determining that the user basic information set includes user basic information corresponding to the user related information, the joint reporting server may fill each field value corresponding to an associated user related field included in the user basic information set corresponding to the user related information into normalized user related information. The associated user related fields may include, but are not limited to, a plurality of associated user name fields, associated user credential type fields, and associated user credential code fields. Then, in response to determining that the user basic information corresponding to the user associated information does not exist in the user basic information set, information filling can be performed on associated user related fields included in the normalized user associated information according to filling information submitted by a user. The padding information may be each field value corresponding to the associated user-related field submitted by the user.

And a fourth sub-step of determining the normalized user-associated information as standard user-associated information in response to determining that the associated user name field included in the normalized user-associated information is not null.

And thirdly, determining the obtained standard user association information as a standard user association information set.

And step four, determining the standard user association information set, the user basic information set and the abnormal and standard user name information set as user association data.

Step 203, the joint reporting server sends the joint reporting task opening information to each joint reporting sub-server corresponding to each piece of equipment information in the equipment information set.

In some embodiments, the joint reporting server may send the joint reporting task start information to each joint reporting sub-server corresponding to each piece of equipment information in the equipment information set.

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 starting information sent by the joint reporting server.

In some embodiments, in response to receiving the joint reporting task start information sent by the joint reporting server, each joint reporting sub-server of the respective joint reporting sub-servers may load a sub-user association information set from a second preset data loading source. The sub-user associated information set may be a user associated information set in the joint reporting sub-server. The sub-user association information in each sub-user association information in the sub-user association information set may include each field and a field value corresponding to each field. For example. The fields in the respective fields may be a user name field, a user credential type field, a user credential code field, a business category code field, or an associated value field. The second predetermined data loading source may be a data storage source.

In some optional implementations of some embodiments, each of the above-mentioned respective joint reporting sub-servers may be further configured to perform the following steps to enable loading, from a second preset data loading source, a set of sub-user associated information in response to receiving the joint reporting task activation information sent by the above-mentioned joint reporting server:

and step one, loading the sub-user associated information set into the memory according to the second preset data loading source.

And secondly, performing data verification processing on the sub-user associated information set to obtain a data verification result. The data verification result may be a verification success or a verification failure representing the sub-user associated information set. The data verification process may be a process of determining whether the data type of each field included in each piece of sub-user association information in the sub-user association information set is normalized. In practice, for each sub-user associated information in the sub-user associated information set, each of the above-mentioned respective joint reporting sub-servers may be further configured to perform the following steps to perform data verification processing on the sub-user associated information set, to obtain a data verification result:

A first substep, for each field in the sub-user association information, in response to determining that a field corresponding to the field in the preset field and data type information set and a data type included in the data type information are different from a data type corresponding to the field, increasing the preset count value by 1. The preset field and the data type information set may represent a correspondence between the field and the data type. The preset field and the data type information in the preset field and the data type information set may include a field and a data type corresponding to the field. For example, the data type may be, but is not limited to, one of an int type, a string type, a char type, a float type. The preset count value may be the number of unnormalized fields in the record of the associated information of each sub-user. The initial value of the preset count value may be 0.

And a second sub-step of determining the success of the verification as a data verification result in response to determining that the obtained preset count value is 0.

And a third sub-step of determining a verification failure as a data verification result in response to determining that the obtained preset count value is greater than 0.

And thirdly, responding to the fact that the data verification result represents verification success, and sending the data loading success information to the joint reporting sub-client corresponding to the joint reporting sub-server.

And fourthly, responding to the fact that the data verification result represents verification failure, and sending data loading failure information to the joint reporting sub-client corresponding to the joint reporting sub-server. The data loading failure information may be a prompt message prompting the user that verification of the sub-user associated information set loaded from the second preset data loading source fails.

In 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.

In some embodiments, each of the above-mentioned individual joint reporting sub-clients may display 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 above-mentioned joint reporting sub-client. The data confirmation control may be a control for confirming data without errors. The data loading success information may be prompt information of successful verification of prompt data sent by the joint reporting sub-server corresponding to the joint reporting sub-client.

And step 206, the joint reporting client responds to the detection of the selection operation of the reporting category selection control in each reporting category selection control, and sends the reporting category information corresponding to the selected reporting category selection control to the joint reporting server.

In some embodiments, the above-mentioned combined reporting client may send, in response to detecting a selection operation acting on a reporting category selection control in each reporting category selection control, reporting category information corresponding to the selected reporting category selection control to the above-mentioned combined reporting server. The above-mentioned various newspaper-sending category selection controls may be various controls for selecting a newspaper-sending category. The reporting category selection controls in the reporting category selection controls are in one-to-one correspondence with the reporting category information in the reporting category information. The selection operation may be, but is not limited to, click, slide, drop down box selection. The respective report category information may be a respective report category selected by the user. For example, the reporting category information can be a single client category of the same industry, and the characterization gathers and sums the user association information sets of all the participants according to the fields of client name, the fields of the same field, the business category code field, the association value field and the like. Each party may include the joint reporting server and each joint reporting sub-server.

The specific setting of the execution sequence of step 205 and step 206 is not limited. Step 205 may be performed prior to step 206, may be performed after step 206, or may be performed simultaneously with step 206.

And step 207, the joint reporting server performs classification and combination processing on the user associated data according to the received reporting category information to obtain a user combined associated information set.

In some embodiments, the joint reporting server may classify and combine the user associated data according to the received reporting category information, to obtain each user combined associated information set. Wherein the user merging associated information sets in the user merging associated information sets are in one-to-one correspondence with the reporting category information in the reporting category information. The above-mentioned user-associated information sets may be sets obtained by classifying and combining the user-associated information sets included in the user-associated data according to preset classification information included in the reporting category information. The fields included in the user merging associated information in different sets in the user merging associated information sets may be different.

In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to implement, according to the received respective reporting category information, classification and merging processing on the user associated data, to obtain respective user merged associated information sets:

First, acquiring a preset field value and a coding relation information set. The preset field value and the code relation information set may represent a relation between the field value and a code corresponding to the field value. The preset field value and the coding relationship information in the preset field value and coding relationship information set may include a field value and a code corresponding to the field value.

And secondly, transmitting the preset field value and the coding relation information set to each joint reporting sub-server in the joint reporting sub-servers.

Third, for each piece of the report category information, executing the following steps:

And a first execution step, wherein the classification processing is carried out on each standard user associated information in the standard user associated information set according to the preset classification information included in the reporting category information, so as to obtain each user associated information set. The reporting category information in each reporting category information may include preset classification information. The preset classification information included in the respective report type information may be different. The standard user association information in the standard user association information set may include each field and a field value corresponding to each field. The preset classification information may include respective classification fields. The user association information sets in the respective user association information sets may include respective standard user association information. In practice, the joint reporting server may use a GROUP BY tool to GROUP the standard user association information according to the classification characters to obtain each user association information set. For example, when the report category information characterizes a single client category of the same industry, each of the classification fields included in the preset classification information may be a client name field, a field of the same domain, a service category code field, and an associated value field.

A second execution step of executing, for each of the respective sets of user-associated information, the steps of:

And a first sub-step, carrying out merging processing on each field value corresponding to the user association value field in each standard user association information in the user association information set to obtain merged user association value information. The combined user association value information may be user association value information obtained by summing up field values corresponding to the user association value fields in the standard user association information. In practice, the joint reporting server may determine the sum of the field values corresponding to the user association value fields in the standard user association information as the combined user association value information.

And a second sub-step of determining any one of the standard user association information in the user association information set as target user association information.

And a third sub-step of changing the determined target user association information according to the combined user association value information, the preset field value and the coding relation information set to obtain changed user association information as user combined association information. The change user related information may be target user related information after the change processing. In practice, first, the joint reporting server may determine, as the domain classification code, a preset field value of the preset field value and a code included in the code relationship information set, and a code corresponding to the domain classification field value. The domain classification field value may be a field value corresponding to a domain classification field in the target user associated information. Then, the preset field value and the code included in the code relationship information corresponding to the supplied user name field value in the above-mentioned preset field value and code relationship information set may be determined as the supplied user name code. The value of the provisioning username field may be a field value corresponding to a provisioning username field in the target user association information. Then, the preset user name and the code included in the code information corresponding to the user name field value in the preset user name and code information set may be determined as the user name code. The user name field value may be a field value corresponding to a user name field in the target user related information. The preset user name and code information set can represent the corresponding relation between the user name information and the code. The preset user name and code information in the preset user name and code information set may include codes corresponding to the user name information and the user name field value. Then, the field value corresponding to the domain classification field in the target user associated information may be replaced with the domain classification code, the field value corresponding to the provisioning user name field may be replaced with the provisioning user name code, the field value corresponding to the user associated value field may be replaced with the combined user associated value information, and the field value corresponding to the user name field may be replaced with the user name code, so as to perform a modification process on the determined target user associated information, and obtain modified user associated information as user combined associated information.

And thirdly, executing the step of determining the obtained user merging association information as a user merging association information set.

Step 208, the joint reporting service terminal generates each joint reporting information based on the combined associated information set of each user.

In some embodiments, the joint reporting server may generate each joint reporting information based on the set of combined associated information of each user. The joint reporting information in the joint reporting information can represent each data fragment of the relevant information of each user with higher risk exposure. In practice, the joint reporting server may generate each joint reporting information by various manners based on the combination of the associated information sets by each user.

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 each user merging the associated information set:

for each user merging associated information set in the above-mentioned individual user merging associated information sets, the following steps are executed:

And the first step, carrying out data segmentation processing on each user merging associated information in the user merging associated information set to obtain each reserved segmented data and each exchange segmented data set. The reserved partition data in the reserved partition data may be each data fragment of the association information combined for each user reserved locally. Each piece of exchange division data in the exchange division data set can be each piece of data of the combined information of the combination of each user performing the piece exchange with the joint reporting sub-server. And the exchange division data sets in the exchange division data sets correspond to the joint reporting sub-server in the joint reporting sub-servers.

And step two, the exchange division data sets are respectively sent to the joint reporting sub-servers.

And thirdly, responding to the received sub-exchange split data sets corresponding to the reserved split data sent by the combined reporting sub-server, and generating the combined split data as combined reporting information based on the reserved split data and the sub-exchange split data sets. The combined reporting information may be reporting fragment information generated by combining the combined reporting server and each combined reporting sub-server. The report fragment information may include each report field and each field value data fragment corresponding to each report field. The respective reporting fields may be respective fields included in the user merge association information set. The data fragments of each field value may be each data fragment of each field value corresponding to each reporting field. In practice, in response to receiving each sub-exchange split data set corresponding to each reserved split data sent by each joint reporting sub-server, the joint reporting server may generate, through a preset joint reporting information generation interface, each joint split data as joint reporting information based on each reserved split data and each sub-exchange split data set. The preset joint reporting information generation interface can be an interface for each participant to cooperatively calculate while protecting the private data of each participant. For the joint reporting server, the input of the preset joint reporting information generating interface may be the identification information of the joint reporting server, the reserved split data and the sub-exchange split data sets, and the output may be the joint split data. The identification information of the joint reporting server may be an IP address of the joint reporting server.

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

The first step, responding to the received data query request information sent by the joint reporting sub-server in the joint reporting sub-server, generating each query result information according to a user basic information set and an abnormal and standard user name information set included in the user associated data, and sending the query result information to the joint reporting sub-server. The data query request information in the data query request information may be request information for querying standard user name information corresponding to user name information to be normalized in the joint reporting server. The user name information to be normalized may be a field value corresponding to a user name field included in the sub-user association information in the joint reporting sub-server. The data query request information may include encrypted user name information. The encrypted user name information can be obtained by encrypting the user name information to be normalized by adopting an MD5 encryption algorithm through the joint reporting sub-server. The sub-user associated information may be included in a sub-user associated information set in the joint reporting sub-server. The query result information in the query result information may represent whether or not standard user name information corresponding to the encrypted user name information exists in the user base 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 user basic information set is standard user name information. In practice, in response to receiving the data query request information sent by the joint reporting sub-server in the joint reporting sub-servers, the joint reporting sub-server may use a preset trace query interface to generate query result information according to a user basic information set and an abnormal and standard user name information set included in the user associated data. The preset trace query interface may be an interface in which a trace query protocol is encapsulated. The input of the preset trace query interface can be a user basic information set, an abnormal and standard user name information set and encrypted user name information, and the output can be query result information.

And secondly, in response to receiving the equipment configuration information sent by the joint reporting client, updating the equipment information set according to the equipment configuration information to obtain an updated equipment information set. Wherein the above device configuration information may characterize adding device information, deleting device information, or modifying device information. The device configuration information may include configuration type information, device node name information, a user name corresponding to the device, a user credential type corresponding to the device, and a user credential code corresponding to the device. The configuration type information may be an add device type, a delete device type, or a modify device type. The device name information may characterize a subsidiary server side identifier. The updated device information set may be an updated device information set.

And thirdly, determining the obtained updated device information set as a device information set.

In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps, to implement, 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:

And firstly, checking the equipment configuration information to obtain check result information. The verification result information may be a result obtained by verifying the device configuration information. The verification result information may be verification success or verification failure. In practice, in response to determining that the user name corresponding to the device included in the device configuration information exists in each field value corresponding to the supplied user name field, the joint reporting server may determine that the verification is successful as verification result information. In response to determining that the user name corresponding to the device included in the device configuration information does not exist in the respective field values corresponding to the provisioning user name field, a verification failure may be determined as verification result information. The field values corresponding to the provisioning username field may be field values corresponding to the provisioning username field in the set of user-associated information.

And a second step of executing the following steps in response to determining that the verification result information represents that the verification is successful:

And a first updating step of deleting the device information corresponding to the device configuration information in the device information set in response to determining that the configuration type information included in the device configuration information is the deleted device information, so as to update the device information set to obtain an updated device information set.

A second updating step of, in response to determining that the configuration type information included in the above-described device configuration information is added device information, performing the steps of:

And a first sub-step of determining the equipment node name information, the user name corresponding to the equipment, the user certificate type corresponding to the equipment and the user certificate code corresponding to the equipment, which are included in the equipment configuration information, as equipment information.

And a second sub-step of adding the determined device information to the device information set to update the device information set to obtain an updated device information set.

And a third updating step of replacing the device node name information, the device name corresponding to the user name, the device corresponding user certificate type and the device corresponding user certificate code included in the device information corresponding to the device configuration information with the device node name information, the device corresponding user name, the device corresponding user certificate type and the device corresponding user certificate code included in the device configuration information in response to determining that the configuration type information included in the device configuration information is the device modification information. The device information may be device information included in the device information set.

And thirdly, responding to the fact that the verification result information represents verification failure, and sending verification failure prompt information to the joint reporting client. The verification failure prompt information may be prompt information for prompting a user to verify failure of the device configuration information.

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 merging associated information in the user merging associated information set to obtain each reserved segmented data and each exchange segmented data set:

The first step, initializing a preset user segmentation information set with preset segmentation values. The preset dividing value may be the number of each participant participating in the joint reporting task. The preset user division information set may be a set for storing user division information. The user dividing information may be a data fragment obtained by dividing the user merging related information into data. In practice, the joint reporting server may void the preset user segmentation information sets with preset segmentation values, so as to initialize the preset user segmentation information sets with preset segmentation values.

Second, for each user merging associated information in the user merging associated information set, executing the following steps:

And a first sub-step, carrying out data segmentation processing on the user merging related information according to the preset segmentation value to obtain user segmentation information with the preset segmentation value. The preset division value pieces of user division information can be all data fragments obtained by carrying out data division on the user combination association information.

And a second sub-step of adding the obtained preset division value number of user division information to the preset division value number of preset user division information sets respectively.

And thirdly, determining any one of the obtained preset user segmentation information sets with preset segmentation values as reserved segmentation data. The reserved segmentation data may be a preset user segmentation information set reserved at the joint reporting server.

And step four, determining each preset user segmentation information set which is different from the reserved segmentation data in the preset segmentation value sets as each exchange segmentation data. The exchange division data may be each preset user division information set for exchanging data with each joint reporting sub-server.

And fifthly, determining each piece of determined exchange partition data as an exchange partition data set.

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 merging related information according to the preset segmentation value, so as to obtain a preset segmentation value of user segmentation information:

The first step, splitting each field value in the field values included in the user merging associated information into a random number with preset segmentation values as a random number sequence, and obtaining each random number sequence. Wherein, the field value in each field value included in the user merging association information corresponds to the random number sequence in each random number sequence one by one. The sum of the random numbers in the random number sequence may be equal to the field value corresponding to the random number sequence.

Second, based on the obtained random number sequences, the following combination steps are performed:

a first combining step of, in response to determining that any one of the respective random number sequences is non-null, performing the steps of:

A first sub-step of arbitrarily selecting a random number from each of the random number sequences to obtain each random number.

And a second sub-step of determining each obtained random number as user segmentation information.

And a third sub-step of deleting each random number in the obtained random numbers from the corresponding random number sequences to update the random number sequences so as to obtain updated random number sequences. Wherein each updated random number sequence is each random number sequence from which each random number is deleted.

And a fourth sub-step of re-executing the combining step based on each random number sequence by using each updated random number sequence as each random number sequence.

And a second combining step of determining the obtained user segmentation information as a preset segmentation value number of user segmentation information in response to determining that any one of the random number sequences is null.

Optionally, the above-mentioned joint reporting server may be further configured to perform the following steps:

for each of the above-described respective delivery category information, the following steps are performed:

The first step, according to preset ordering information, ordering processing is carried out on each piece of combined segmentation data represented by the combined reporting information corresponding to the reporting category information, and an ordering segmentation data sequence is obtained. The preset sorting information may represent a sorting algorithm, a sorting mode and a sorting value. The above-described ordering may be in ascending or descending order. The ranking value may be indicative of taking a predetermined number of the joint segmentation data that are top ranked. Here, the specific setting of the preset numerical values is not limited. In practice, the joint reporting server may perform, through a preset multiparty secure ordering interface, ordering processing on each joint segmentation data represented by the joint reporting information corresponding to the reporting category information according to preset ordering information, to obtain an ordering segmentation data sequence. The preset multiparty safe sorting interface may be a collaborative computing interface encapsulating a sorting algorithm based on multiparty safe computing. For the joint reporting server, the input of the preset multiparty safety ordering interface may be preset ordering information, each joint segmentation data, and the identification information of the joint reporting server, and the output may be an ordering segmentation data sequence. For each joint reporting sub-server in each joint reporting sub-server, the input of the preset multiparty safety ordering interface can be preset ordering information, each sub-joint segmentation data, and the identification information of the joint reporting sub-server, and the output can be a sub-ordering segmentation data sequence. The sub-joint segmentation data may be each joint segmentation data generated by the joint reporting sub-server.

And secondly, responding to the received sub-sequence segmentation data sequences sent by the combined reporting sub-servers, and carrying out aggregation processing on the sequence segmentation data sequences and the sub-sequence segmentation data sequences to obtain an aggregation segmentation data sequence. The aggregate division data sequence may be a sequence obtained by aggregating the sequence of ordered division data and each field value corresponding to each aggregate field in each sub-sequence of ordered division data. The sequence of ordered partitions includes the same respective aggregate fields as each of the sub-sequences of ordered partitions. The aggregation fields may be fields included in a user merge association information set corresponding to the report type information. In practice, the joint reporting server may be further configured to perform the following aggregation step, so as to implement, in response to receiving each sub-ordered split data sequence sent by each joint reporting server, aggregation processing is performed on the ordered split data sequence and each sub-ordered split data sequence, to obtain an aggregated split data sequence:

a first aggregation step of, for each of the sequence of sorted divided data, performing the steps of:

and a first sub-step of determining each piece of sub-sequence division data corresponding to the sequence division data in each sub-sequence division data sequence as each piece of sequence division data to be aggregated.

And a second sub-step of determining, for each aggregation field in the sequence division data, a sum of a field value corresponding to the aggregation field in the sequence division data and each field value corresponding to the aggregation field in the sequence division data to be aggregated as an aggregation field value, thereby obtaining each aggregation field value.

And a third sub-step of determining the aggregation fields and the aggregation field values corresponding to the aggregation fields as aggregation segmentation data.

And a second aggregation step of determining each obtained aggregated and partitioned data as an aggregated and partitioned data sequence.

And thirdly, decoding the obtained aggregation segmentation data sequence to obtain a decoding segmentation data sequence. The decoded segmented data sequence may be each piece of aggregated segmented data after decoding. When the report type information characterizes a single client in the same industry, the decoding split data in the decoding split data sequence may include, but is not limited to, one of a domain classification field, a field value corresponding to the domain classification field, a provisioning user name field, a field value corresponding to the provisioning user name field, a field value corresponding to the user name field, an association value field, and a field value corresponding to the association value field.

And step four, carrying out association processing on each decoding segmentation data in the decoding segmentation data sequence and each standard user association information in the standard user association information set to obtain each associated user information. In practice, for each piece of the decoded and segmented data, the joint reporting server may determine, as each piece of standard user association information corresponding to the decoded and segmented data, each piece of standard user association information having a target field value, which is a field value corresponding to a user name field in the pieces of standard user association information. The target field value may be a field value corresponding to a user name field in the decoded and divided data.

And fifthly, determining the obtained relevant user information as the reporting information.

In some optional implementations of some embodiments, the joint reporting server may be further configured to perform the following steps to perform decoding processing on the obtained aggregated-split data sequence to obtain a decoded-split data sequence:

first, for each of the aggregated-partitioned data in the aggregated-partitioned data sequence, performing the steps of:

And a first sub-step of determining the preset field value of the corresponding field classification code in the preset field value and coding relation information set and the preset field value included in the coding relation information as target field classification field values. The domain classification code may be a field value corresponding to a domain classification field in the aggregated and partitioned data.

And a second sub-step of determining the preset field value corresponding to the supplied user name code in the code relation information set and the preset field value included in the code relation information as the target supplied user name field value. The provisioning username code may be a field value corresponding to a provisioning username field in the aggregated and partitioned data.

And a third sub-step, wherein the preset field value of the corresponding user name code in the preset user name and code information set and the user name information included in the code relation information can be determined as the target user name field value. The user name code may be a field value corresponding to a user name field in the aggregated and divided data.

And a fourth sub-step of replacing a field value corresponding to the domain classification field in the aggregated and divided data with the target domain classification field value, replacing a field value corresponding to the provisioning user name field with the target provisioning user name field value, and replacing a field value corresponding to the user name field with the target user name field value to obtain decoded and divided data.

And a second step of determining each obtained decoded split data as a decoded split data sequence.

Step 209, the joint reporting server sends the reporting category information to each joint reporting sub-server corresponding to each piece of equipment information in the equipment information set.

In some embodiments, the joint reporting server may send the reporting category information to each joint reporting sub-server corresponding to each 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.

The specific setting of the execution sequence of step 208 and step 209 is not limited. Step 208 may be performed prior to step 209, may be performed after step 209, or may be performed simultaneously with step 209.

In step 210, each of the joint reporting sub-clients sends data confirmation information to the joint reporting sub-server in response to detecting the selection operation acting on the data confirmation control.

In some embodiments, each of the individual federated reporting sub-clients may send data confirmation information to the federated reporting sub-server in response to detecting a selection operation acting on the data confirmation control. The data confirmation information may be a prompt message for prompting the joint reporting server to joint reporting sub-server to upload data without errors.

Step 211, each of the joint reporting sub-servers performs normalization processing on the sub-user association information set in response to receiving the data acknowledgement information sent by the joint reporting sub-client corresponding to the joint reporting sub-server, and obtains the normalized sub-user association information set as a standard sub-user association information set.

In some embodiments, each of the above-mentioned combined reporting sub-service ends may perform normalization processing on the sub-user association information set in response to receiving the data acknowledgement information sent by the combined reporting sub-client corresponding to the above-mentioned combined reporting sub-service end, so as to obtain the normalized sub-user association information set as the standard sub-user association information set. The standard sub-user associated information set may be a normalized sub-user associated information set.

In the process of adopting the technical scheme to solve the first technical problem, the second technical problem is often accompanied by the fact that the data reporting party locally processes the user-related data of each participant according to the data verification rule, and the data processing efficiency is lower and the safety of the user-related data of each participant is lower due to the fact that the data amount of the user-related data of each participant is more and the data verification rule is more and more complex. In order to solve the second technical problem, the conventional solution is generally to select partial data from the user related data of each participant for data processing. The inventor considers the disadvantage of selecting part of the data from the user related data of each participant for data processing. Also in combination with the advantages of the data processing aspects owned by the inventors, we decided to employ the following solutions:

In some optional implementations of some embodiments, each of the above-mentioned respective joint reporting sub-servers may be further configured to perform the following steps, so as to implement, in response to receiving the data acknowledgement information sent by the joint reporting sub-client corresponding to the joint reporting sub-server, normalization processing is performed on the sub-user association information set, and the normalized sub-user association information set is obtained as a standard sub-user association information set:

And firstly, encrypting each field value corresponding to the user name field in each sub-user associated information to obtain each piece of encrypted user name information. Wherein the sub-user associated information is sub-user associated information included in the sub-user associated information set. The encrypted user name information may be each field value corresponding to the user name field in the encrypted sub-user associated information. In practice, the joint reporting sub-server may use an MD5 encryption algorithm to encrypt each field value corresponding to a user name field in the sub-user association information set, so as to obtain each encrypted user name information.

Second, for each piece of the above-described individual piece of encrypted user name information, the following steps are performed:

and a first sub-step of determining the encrypted user name information and the preset query prompt information as data query request information. The preset inquiry prompt information may be prompt information for prompting the joint reporting server to inquire related data in the joint reporting server. The related data may be a user basic information set in the joint reporting server or the abnormal and standard user name information set. The data query request information may be a request for querying the related data.

And a second sub-step of sending the data query request information to the joint reporting server.

And a third sub-step, responding to the public key sent by the joint reporting server, and performing blinding processing on the encrypted user name information according to the public key and a preset random number to obtain blinded encrypted user name information. The blind encrypted user name information may be encrypted user name information encrypted by the public key. The public key may be a public key generated by the joint reporting server through an 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 may perform data conversion processing on the encrypted user name information through a preset data conversion interface, so as to obtain converted user name information. Then, a product of a first numerical power of the preset random number and a remainder of the converted user name information taking a remainder of the second numerical value may be determined as blind encrypted user name information. The predetermined data conversion interface may be an interface for converting the encrypted user name information into an integer number.

And a fourth sub-step, the blind encrypted user name information is sent to the joint reporting server, so that the joint reporting server performs signature processing on the blind encrypted user name information according to a private key.

And a fifth sub-step, in response to receiving the signature blind user encryption information sent by the joint reporting server, performing blind removal processing on the signature blind user encryption information according to the preset random number to obtain identification information corresponding to the encrypted user name information. The signature blind user encryption information can be obtained by the joint reporting server through signature processing of the blind encryption user name information according to a private key. The identification information may be a data ID of the standard user name information corresponding to the encrypted user name information in the related data of the joint reporting server. In practice, the joint reporting sub-server may determine, as the identification information corresponding to the encrypted user name information, a remainder of the quotient of the signature blind user encryption information and the preset random number that is obtained by taking the second numerical value.

And a sixth sub-step of sending the data request information to the joint reporting server. The data request information may be a prompt message for prompting the joint reporting server to generate a random number sequence.

And a seventh substep, in response to receiving the random number sequence sent by the joint reporting server, performing blind positioning processing on each random number in the random number sequence according to the preset random number and the identification information, and obtaining each blind random number as a blind random number sequence. The random number sequence may be each random number randomly generated by the joint reporting server. The number of the random numbers is equal to the number of data lines of the related data. The blind random number sequence may be a blind random number sequence. In practice, the joint reporting sub-server may determine, as the blind random number, a sum of each random number in the random number sequence and a first numerical power of the preset random number, and obtain each blind random number as the blind random number sequence.

And an eighth sub-step of transmitting the blind random number sequence to the joint reporting server.

And a ninth substep, in response to receiving the query result information sent by the joint reporting server, performing blind removal processing on each piece of encryption standard name information included in the query result information according to the preset random number to obtain target standard name information. The query result information may be signed user name information of each specification. The target specification name information may be specification user name information obtained by blind removal of a signature specification user name marked as the identification information. In practice, first, the joint reporting sub-server may determine, as the target encryption specification name information, the encryption specification name information with the line labeled as the identification information in the encryption specification name information. Then, the first numerical power of the above-described target encryption specification name information may be determined as target specification name information.

And a tenth sub-step of determining the obtained target specification name information as specification user name information corresponding to the encrypted user name information.

And thirdly, replacing each field value corresponding to the user name field in each piece of sub-user associated information with each piece of obtained standard user name information, so as to normalize the sub-user associated information set, and obtaining a normalized sub-user associated information set as a standard sub-user associated information set.

The related content of the first step to the third step of the above technical solution is taken as an invention point of the embodiments of the present disclosure, which solves the second technical problem that the processing efficiency of data is low and the security of the user related data of each participant is low. Factors causing low processing efficiency of data and low safety of user-related data are often as follows, the data reporting party performs data processing on the user-related data of each participant locally according to the data verification rule, and the data verification rule is complex and complex due to the large data quantity of the user-related data of each participant. If the above factors are solved, the effects of improving the processing efficiency of the data and the safety of the data related to the user can be achieved. In order to achieve the effect, the blind signature method based on asymmetric encryption is introduced, each participant blindly inquires the data ID, and the data reporting party signs the blinded inquire ID of each participant, so that the data reporting party does not know the specific content inquired by each participant, and each participant cannot acquire the original data of the data reporting party, thereby improving the safety of the data reporting party and the related data of each participant user. And the data reporting party does not need to provide complex check rules, so that the processing efficiency of the data is improved.

The specific setting of the execution sequence of step 209 and step 211 is not limited. Step 209 may be performed prior to step 211, may be performed after step 211, or may be performed simultaneously with step 211.

Step 212, each of the combined reporting sub-servers responds to receiving the reporting category information sent by the combined reporting server, and classifies and combines the standard sub-user associated information sets according to the received reporting category information to obtain the combined associated information sets of the sub-users.

In some embodiments, each of the above-mentioned combined reporting sub-service ends may respond to receiving the reporting category information sent by the above-mentioned combined reporting service end, and perform classification and combination processing on the above-mentioned standard sub-user association information set according to the received reporting category information, so as to obtain each sub-user combination association information set. The above sub-user merging associated information sets may be sets obtained by classifying and merging standard sub-user associated information sets according to preset classification information included in the reporting category information. Here, in response to receiving the respective reporting category information sent by the joint reporting server, the specific step of classifying and combining the standard sub-user associated information sets according to the received respective reporting category information to obtain the respective sub-user combined associated information sets may refer to step 207, where the step of classifying and combining the user associated data according to the received respective reporting category information by the joint reporting server to obtain the respective user combined associated information sets is not repeated herein.

Step 213, each of the sub-service terminals of the combined report generates the combined report information of each sub-user based on the combined associated information set of each sub-user.

In some embodiments, each of the above-mentioned respective combined reporting sub-servers may generate respective sub-combined reporting information based on the above-mentioned respective sub-user-combined association information sets. The sub-joint reporting information in the sub-joint reporting information can represent each data fragment of the related information of each standard sub-user with higher risk exposure.

In some optional implementations of some embodiments, each of the respective consolidated reporting sub-servers may be further configured to perform the following steps to enable generation of respective sub-consolidated reporting information based on the respective sub-user consolidated association information set:

for each sub-user merging associated information set in the obtained sub-user merging associated information sets, executing the following steps:

And the first step, carrying out data segmentation processing on the sub-user merging associated information in the sub-user merging associated information set to obtain each reserved sub-segmentation data and each exchange sub-segmentation data set. The reserved sub-split data may be a set of data fragments reserved at the joint reporting sub-server. The specific step of performing data segmentation processing on the sub-user merging related information in the sub-user merging related information set to obtain each reserved sub-segmented data and each exchange sub-segmented data set may refer to the joint reporting server to perform data segmentation processing on each user merging related information in the user merging related information set to obtain each reserved segmented data and each exchange segmented data set, which is not described herein again.

And step two, the sub-division data sets of each exchange are respectively sent to the joint reporting server and each sub-exchange server. The switch sub-servers may be different from the joint reporting sub-servers in the joint reporting sub-servers.

And thirdly, responding to the received exchange segmentation data set corresponding to the sub-user merging association information set sent by the joint reporting server and each exchange sub-segmentation data set sent by each exchange sub-server, and generating each sub-joint segmentation data as sub-joint reporting information according to the received exchange segmentation data set, each exchange sub-segmentation data set and each reserved sub-segmentation data. In practice, in response to receiving the exchange segmentation data set corresponding to the sub-user merging association information set sent by the joint reporting server and each exchange segmentation data set sent by each exchange sub-server, the joint reporting sub-server may generate, through the preset joint reporting information generation interface, each sub-joint segmentation data as sub-joint reporting information according to the received exchange segmentation data set, each exchange segmentation data set and each reserved sub-segmentation data. For the joint reporting sub-server, the input of the preset joint reporting information generating interface may be the identification information of the joint reporting sub-server, the exchange segmentation data set, the exchange segmentation data sets and the reserved segmentation data, and the output may be the joint segmentation data. The identification information of the combined reporting sub-server may be an IP address of the combined reporting sub-server.

In the process of adopting the technical scheme to solve the first technical problem, the third technical problem is often accompanied by that when the number of all the participants participating in the joint reporting of data is large, the user related data is large, when the user related data with risks is large, the reporting information is presented in the form of a table or a file, and the user cannot intuitively check all the user related data with risks, so that the experience of the management user is poor. In order to solve the third technical problem, the conventional solution is generally to only present user related data with higher risk level. While the inventors consider the disadvantage of presenting only user-related data with a higher risk level. Also in combination with the advantages of the data visualization process owned by the inventors, we decided to employ the following solution:

optionally, the joint reporting client may be further configured to perform the steps of:

The method includes the steps of firstly, responding to detection of selection operation of the report information viewing control in each report information viewing control, and displaying each report information monitoring template selection control. Wherein, the newspaper information viewing control of the above respective newspaper information viewing controls and reporting category information corresponding to each reporting category information. And the newspaper sending information viewing control in each newspaper sending information viewing control corresponds to the newspaper sending information in each newspaper sending information. The above-mentioned various pieces of report information monitoring template selection controls may be various controls for selecting various pieces of report information monitoring templates. The report information monitoring templates may be monitoring templates for visually monitoring report information.

And secondly, responding to the detection of the selection operation of the report information monitoring template selection control acting on each report information monitoring template selection control, and acquiring the report information corresponding to the selected report information viewing control. In practice, first, the above-mentioned joint reporting client may determine, as the reporting information ID corresponding to the selected reporting information viewing control, the preset reporting information of the preset reporting information and the reporting information ID included in the control information corresponding to the reporting information viewing control ID in the control information set. Then, the delivery information corresponding to the delivery information ID corresponding to the selected delivery information viewing control may be determined as the delivery information corresponding to the selected delivery information viewing control. The newsletter viewing control ID may be the ID of the selected newsletter viewing control. The report information ID may represent report information corresponding to the report information viewing control ID. The preset report information and the control information set may represent a correspondence relationship between the report information viewing control ID and the report information ID. The preset report information and control information in the preset report information and control information set may include a report information viewing control ID and a report information ID corresponding to the report information viewing control ID.

Thirdly, selecting a report information monitoring template corresponding to the control according to the selected report information monitoring template, and carrying out data normalization processing on the report information corresponding to the selected report information checking control to obtain report information after the data normalization processing. The report information monitoring template may include each normalized field and each normalization method corresponding to each normalized field. The normalization methods may be normalization functions. Here, the specific setting of each normalization method is not limited. For example, the normalization method may be y= (x-min)/(max-min). Where x may be a field value of a field corresponding to the normalization method. The min may be a minimum field value of a field corresponding to the normalization method. max may be the maximum field value of the field corresponding to the normalization method. y may be the normalized x. In this case, y may have a value of [0,1]. In practice, for each normalized field in each normalized field included in the report information monitoring template, first, the joint report client may input each field value corresponding to the normalized field in the report information into a normalization function corresponding to the normalized field, to obtain each normalized field value. And then, replacing each field value corresponding to the normalized field in the report information with each normalized field value so as to perform data normalization processing on the report information corresponding to the selected report information checking control, thereby obtaining the report information after the data normalization processing.

And fourthly, selecting a reporting information monitoring template corresponding to the control according to the selected reporting information monitoring template, and performing data aggregation processing on the reporting information subjected to the data normalization processing to obtain the reporting information subjected to the data aggregation processing. The report information monitoring template may further include an aggregation function. For example, the aggregation function may be SUM (SUM), COUNT (COUNT), average (AVG), maximum (MAX), minimum (MIN), or the like. In practice, the combined reporting client can perform data aggregation processing on the reporting information after the data normalization processing according to the aggregation function included in the reporting information monitoring template to obtain the reporting information after the data aggregation processing.

And fifthly, selecting a reporting information monitoring template corresponding to the control according to the selected reporting information monitoring template, and performing data conversion processing on the reporting information after the data aggregation processing to obtain the reporting information after the data conversion processing. The report information monitoring template may further include a data conversion field and a data conversion algorithm. The data conversion field may be a field in which a data type needs to be converted. For example, the data conversion algorithm may be a hot independent code that can convert text type data to numeric type data.

And sixthly, selecting a report information monitoring template corresponding to the control according to the selected report information monitoring template, and visually monitoring the report information after the data conversion processing. The report information monitoring template can further comprise a visual chart type. For example, the visualization chart type may be a bar chart, pie chart, thermodynamic diagram, dashboard, or the like. Thus, the user can more intuitively view the newspaper information.

The related contents of the first step to the sixth step of the above technical solution are taken as an invention point of the embodiments of the present disclosure, which solves the third technical problem that the user cannot intuitively view the related data of each user with risk, thereby resulting in poor experience of the management user. Factors causing poor user experience are often as follows, when the number of all the participants participating in the joint reporting of data is large, the user related data is large, when the user related data with risk is large, the reporting information is presented in the form of a table or a file, and the user cannot intuitively check all the user related data with risk. If the above factors are solved, the effect of improving the user experience can be achieved. In order to achieve the effect, the visual monitoring report information is introduced, a user can select a proper monitoring template according to own requirements, the monitoring template performs visual processing on report data, and further data integration is performed on the report information, so that the efficiency of further analyzing the report data is improved. And the newspaper information is displayed in a visual chart form, so that a user can more intuitively check related data of each user with risk in the newspaper information, and the experience of the user is enhanced.

In some embodiments, the clients, servers 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"), the internet (e.g., the internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed networks.

The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

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 that may be used include Field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems-on-a-chip (SOCs), complex Programmable Logic Devices (CPLDs), and the like.

The foregoing description is only of the preferred embodiments of the present disclosure and description of the principles of the technology being employed. It will be appreciated by those skilled in the art that the scope of the invention in the embodiments of the present disclosure is not limited to the specific combination of the above technical features, but encompasses other technical features formed by any combination of the above technical features or their equivalents without departing from the spirit of the invention. Such as the above-described features, are mutually substituted with (but not limited to) the features having 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 each field and a field value corresponding to each field;

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 the 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 of the reporting category information corresponds to the sub-user combined association information set in each of the obtained sub-user combined association information sets; and each of the joint reporting sub-servers 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:

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:

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.