TW201923647A - Traceable multi-party data processing method, apparatus and device - Google Patents

Abstract

The embodiment of the present specification discloses a traceable multi-party data processing method, apparatus and device, for each data provider, the corresponding identification data, i.e., the traceability identifier, can be defined regarding the data to be encrypted, as traceability basis, the identification data can function to identify the data to be encrypted and the data provider from which the data to be encrypted comes. Further, after the encrypted data is generated by performing encryption processing on the data to be encrypted and the traceability identifier, the encrypted data may be sent to the data processing platform. Then, the data processing platform can realize the traceability of the data according to the identification data.

Description

Traceable multi-party data processing method, device and equipment

The present application relates to the field of computer technology, and in particular, to a method, a device, and a device for processing multi-party data that can be traced.

At present, with the development of big data, fusion processing of multi-party data is also possible. In the existing multi-party data fusion scenario, different data providers perform joint calculations without exposing the original data. In this process, in order to avoid data leakage, different data providers usually encrypt their data, and the corresponding data platform performs data processing based on the encrypted ciphertext data. In the above scenario, it may be necessary to determine the original source of the data in the data processing results. Based on this, we need an effective source tracing method for multiparty data.

The embodiments of the present specification provide multi-party data processing methods, devices, and equipment that can be traced to perform effective and accurate data traceability in a multi-party data processing scenario. An embodiment of the present specification provides a method for processing multi-party data that can be traced, including: 增加 for data to be encrypted, adding a traceability identifier corresponding to the data to be encrypted; 加密 encrypting the data to be encrypted and the traceability identifier to generate encrypted data Sending the encrypted data including the traceability identifier to a data processing platform for multi-party data fusion processing. Another traceable multi-party data processing method provided by the embodiment of this specification includes: receiving encrypted data including a traceability identifier sent by a data provider; determining a traceability identifier in the encrypted data; 数据 data fusion calculation processing for the encryption To generate a data fusion result including the traceability identifier, so as to trace the encrypted data in the data fusion result according to the traceability identifier. A traceable multi-party data processing device provided by an embodiment of this specification includes: an identification module, for data to be encrypted, adding a traceability identification corresponding to the data to be encrypted; an encryption module, for the data to be encrypted and the The traceability identification is encrypted to generate encrypted data; a sending module sends the encrypted data including the traceability identification to a data processing platform for multi-party data fusion processing. Another type of multi-party data processing device provided by the embodiments of this specification includes: a receiving module, which receives encrypted data sent by the data provider and includes a traceability identifier; a determination module, which determines the traceability identifier in the encrypted data; processing A module performs data fusion calculation processing for the encryption to generate a data fusion result including the traceability identifier, so as to trace the encrypted data in the data fusion result according to the traceability identifier. Correspondingly, an embodiment of the present specification also provides a traceable multi-party data processing device, including: a processor and a memory, wherein: the memory stores a traceable multi-party data processing program; the processor calls a memory The traceable multi-party data processing program stored in the body and executes: For the data to be encrypted, add a traceability identifier corresponding to the data to be encrypted; 加密 encrypt the data to be encrypted and the source identification to generate encrypted data; The encrypted data including the traceability identifier is sent to a data processing platform for multi-party data fusion processing. The embodiment of the present specification also provides another traceable multi-party data processing device, including: a processor and a memory, wherein: the memory stores a traceable multi-party data processing program; the processor calls the memory Stored and traceable multi-party data processing program, and execute: receive encrypted data sent by the data provider that contains the traceability identification; determine the traceability identification in the encrypted data; 进行 perform data fusion calculation processing for the encryption to generate the The data fusion result of the traceability identification, so as to trace the encrypted data in the data fusion result according to the traceability identification. The at least one of the above technical solutions adopted in the embodiments of this specification can achieve the following beneficial effects: For each data provider, for the data to be encrypted, corresponding identification data can be defined, that is, the traceability identification, and the identification data is used as the basis for traceability , Can play a role in identifying the data to be encrypted and the data provider from which the data to be encrypted originated. Further, after encrypting the data to be encrypted and the traceability identification to generate encrypted data, the encrypted data can be sent to a data processing platform, and then the data processing platform can implement the traceability of the encrypted data according to the traceability identification. The traceability identification is associated with the original field. In this way, during the data fusion process, the traceability identification will be passed to the final data fusion result, and based on the traceability identification, the fusion result can be traced to the source, and its traceability accuracy Can reach field level.

In order to make the purpose, technical solution, and advantages of the present application clearer, the technical solution of the present application will be clearly and completely described in combination with specific embodiments of the present application and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative efforts shall fall within the protection scope of the present application. Multi-party data fusion processing can be considered based on data provided by multiple data providers such as: maximum statistics (max), minimum statistics (min), average calculation (average), cumulative value calculation (sum), Data processing such as count is not specifically limited here. For example: the financial platform is connected with multiple banks. In this case, the financial platform can obtain the user's credit record data at each bank and perform multi-party data fusion processing in order to calculate the user's comprehensive credit score. Based on this example, for any bank, it is not desirable to make the user data in the bank public, so each bank will encrypt some or all of the user's credit record data, and the encrypted data will be sent to the financial platform. The corresponding data fusion algorithm calculates the credit score. In the process, the personal data of the user is encrypted, so the relevant information of the user will not be exposed. In the above example, the encrypted credit record data may contain data of different dimensions (such as: loan amount, repayment frequency, income level, etc.), and the different dimensions can affect the degree of user's comprehensive credit score (that is, weight) It's usually different. In actual applications, financial platforms may adjust weights in different dimensions in order to optimize data fusion algorithms. However, for encrypted credit record data, it is difficult for a financial platform to determine the dimensions corresponding to the encrypted credit record data, that is, it is difficult to trace the source of the data. For this reason, in one or more embodiments in this specification, a method for processing multi-party data with traceable source is provided. In the scenario of multi-party data fusion, accurate data from different data providers can be realized. Traceability, traceability accuracy can reach the field level. It should be noted that the above-mentioned traceable multi-party data processing method can adopt the architecture shown in FIG. 1. The architecture may include at least: a data provider, a data processing platform, and a trusted third party. Among them: The data provider mentioned in (1) may be considered as a bank, website, telecommunication operator, etc. used to provide data. In some embodiments, the data provider may also be different departments within the same enterprise or organization. In other embodiments, the data provider may also be an individual user. Of course, it is not specifically limited here. Different data providers send data to the data processing platform, so that the data processing platform performs multi-party data fusion processing. The data processing platform described above is used for multi-party data fusion calculation processing (such as the financial platform in the above example). In actual applications, in order to adapt to the processing of huge amounts of data, the data processing platform can usually adopt a decentralized / cluster architecture. The trusted third parties mentioned above can be considered as third-party websites, institutions, etc. used to provide encryption keys, such as: Key Management Center (KMC). During the encryption process, the data provider or data processing platform can use the key provided by a trusted third party for encryption / decryption processing. The encryption method may specifically be symmetric or asymmetric encryption, and the corresponding decryption method may be used for processing when decrypting, which will not be described in detail here. Based on the above-mentioned architecture shown in FIG. 1, the traceable multi-party data processing method in the embodiment of the present specification will be specifically explained below. First, as shown in FIG. 2 on the data provider side, the multi-party data processing method based on traceable data on the data provider side may include the following steps: Step S201: For the data to be encrypted, add a traceability identifier corresponding to the data to be encrypted . The to-be-encrypted data may be considered to be data to be sent by a data provider to a data processing platform for data fusion processing, such as: a string to be encrypted, a field value, an encoding, or a picture to be encrypted. Multimedia data such as video, audio, video, etc. Of course, the specific will be determined according to the needs of the actual application. In the following description, the form of data to be encrypted will be used as an example for illustration, which should not be used as a limitation on this application. The traceability identification mentioned in is used to identify the data to be encrypted in order to trace the source during the fusion process. In practical applications, the traceability identifier can be defined by the data provider. As a feasible way in the embodiments of this specification, the traceability identifier can be used to reflect the type or attribute characteristics of the data to be encrypted. For example, in a simple example, the traceability identifier of the data to be encrypted is A-2, and the traceability identifier can represent the The type of data to be encrypted is A-2. As another feasible way in the embodiment of the present specification, the traceability identifier can be used as the number of the field to which the data to be encrypted belongs. For example, in a simple example, the traceability identifier of the data to be encrypted is 0100. Encrypted data has a field number of 0100. Of course, only the possible situations of the traceability identification are listed here. In practical applications, the character form and the meaning of the traceability identification can usually be determined according to the needs of the actual application, and it is not specifically limited here. Step S203: Encrypt the data to be encrypted and the traceability identifier to generate encrypted data. In the embodiment of the present specification, the traceability identifier matches the data to be encrypted, and is used as the basis for traceability. After being matched and bound with the data to be encrypted, it is encrypted together. The encryption method may specifically adopt salt-added encryption. In this case, a traceability identifier may be added to the salt, and salt-encryption processing may be performed on the salt including the traceability identifier. Of course, in practical applications, the way of matching and binding between the traceability identifier and the data to be encrypted can be to insert the traceability identifier into the beginning or end of the data to be encrypted in the form of a string to form a "traceability identifier + to be encrypted" Data "or" data to be encrypted + traceability identification ". Of course, such an approach should not constitute a limitation on this application. Step S205: Send the encrypted data including the traceability identifier to a data processing platform for multi-party data fusion processing. In the actual data fusion scenario, for each data provider, the encrypted data containing the traceability basis (that is, the traceability identification) is sent to the data processing platform. In this way, the data processing platform is performing data fusion processing. In the process, accurate data traceability can be achieved. Through the above steps, for each data provider, for the data to be encrypted, corresponding identification data can be defined, and the identification data can be used as a source of traceability to identify the data to be encrypted and the source of the data to be encrypted. The role of the data provider. Further, after encrypting the encrypted data and the identification data to generate encrypted data, the encrypted data can be sent to a data processing platform, and then the data processing platform can implement the traceability of the encrypted data according to the identification data. For the foregoing, it should be noted that the data to be encrypted contains the original field. Specifically, as a possible way in the embodiment of the present specification, the data provider may use a data table storage structure for data storage. In the actual data fusion process, the data provider usually sends the data stored in the data table to the data processing platform for data fusion processing. Under the storage structure of a data table, each column of data in the data table represents data having the same commonality. The column name used to describe the characteristics of the data in the column is a field (field, in the embodiment of the present application, To distinguish it from descriptions such as "encrypted fields", the fields before encryption are referred to as "original fields"). That is, in the embodiment of the present specification, the traceability identifier is matched with the field. Therefore, the data provider can encrypt the original field and the traceability identifier that matches the original field to form encrypted data. This allows field-level traceability. Then, combining the above, the data provider can encrypt the data as shown in Figure 3. In FIG. 3, each data provider provides data to be encrypted (ie, data to be encrypted), and these data to be encrypted may be original fields to be encrypted. The data provider can use a salting encryption algorithm to encrypt the original field, that is, add salt to the original field, and the added salt contains the traceability identifier. For example: in FIG. 3, the traceability identifier "0100" as a part of the salt, and the remaining portion "Aaa" in the salt together constitute a salt; similarly, the traceability identifier "0001" and "Bbb" together constitute a salt. However, it should be noted that the traceability identification shown in Figure 3 and the rest of the salt are encrypted results obtained after the encryption operation is performed. In order to facilitate understanding, "0100" and "0001" are used in Figure 3 , "Aaa", "Bbb", etc. On this basis, the data provider can use a key provided by a trusted third party for encryption (the encryption method is not limited to symmetric encryption or asymmetric encryption) to form encrypted data (including encrypted fields). At this time, the encrypted field The bits include: the encrypted salt (the traceability identifier + the remainder of the salt) and the ciphertext information (the ciphertext information can be considered as the original field generated after encryption processing, as shown in Figure 3 11 * f and 22 * e). What needs to be explained here is that in some application scenarios with high data security requirements, when encrypting the field to be encrypted and its salt, the encryption method for the traceability identification in the salt and the rest of the salt and the The encryption method of the encryption field can be inconsistent. In a simple example, the encryption method can be: Md5 (Md5 (the field to be encrypted + the remainder of the salt) + traceability identification) It can be seen that for the field to be encrypted and the remaining part of the salt, Md5 is encrypted first, and then it is encrypted. The encryption result and the traceability identification are encrypted for another Md5. The encrypted data obtained by such an encryption method can be decrypted by the data processing platform using the corresponding key to obtain the traceability identification, and the field is still in an encrypted state, thereby ensuring the security of the field. Of course, in addition to the encryption method shown in the above example, you can also use a partial encryption algorithm, use the encryption algorithm A for "the field to be encrypted + the remainder of the salt" for partial encryption, and use the encryption algorithm for "source identification" Method B performs partial encryption. The specific encryption method can be determined according to the needs of the actual application. In other possible application scenarios, in the salt, the traceability identification is set at the specified location. Then, after decrypting the encryption results of the salt and the field to be encrypted, the data processing platform can learn the corresponding traceability through the specified location of the salt. Logo. Of course, this method can be applied in scenarios where data security requirements are not high, and this should not constitute a limitation on this application. Second, on the data processing platform side As shown in FIG. 4, the traceable multi-party data processing method based on the data processing platform side can include the following steps: Step S401: Receive encrypted data sent by the data provider that contains the traceability identification. In the embodiment of this specification, the data processing platform will receive encrypted data sent from different data providers. Of course, for the content of the traceability identification and encrypted data, please refer to the foregoing content, which will not be repeated here. Step S403: Determine a traceability identifier in the encrypted data.源 The traceability identification is used as the traceability basis in the subsequent fusion processing process. After receiving the encrypted data from the data provider, the data processing platform can determine the traceability identification contained in the encrypted data for traceability processing in the subsequent process. It can be understood that, in the foregoing embodiment, the data provider uses the encryption key of a trusted third party for encryption, then the data processing platform can use the decryption key corresponding to the trusted third party to decrypt the encrypted data. To determine the traceability identifier.实际 In actual application, the data processing platform can record the traceability identification obtained after decryption. Step S405: Perform data fusion calculation processing on the encrypted data to generate a data fusion result including the traceability identifier, so as to trace the encrypted data in the data fusion result according to the traceability identifier. In the embodiment of this specification, the aforementioned fusion processing method may be adopted to perform fusion calculation processing on encrypted data and obtain the required data fusion result (for example, the user's comprehensive credit score in the foregoing example). Of course, it should be understood that in the process of data fusion processing, the encrypted data may undergo multiple encryption-decryption-fusion processing processes.需要 It needs to be explained here that in the process of performing fusion calculation processing, the fusion calculation processing is usually performed on the data part of the encrypted data other than the traceability identifier. This also ensures that the traceability identifier is continuously transmitted during the fusion computing process, and retains its data format. When tracing, the tracing can be realized in the fusion result after the fusion calculation process based on the recorded traceability identification. Specifically, in some practical application scenarios, corresponding to the foregoing content shown in FIG. 3, the traceability identifier, as part of the salt, matches the field in the data table (that is, the aforementioned original field). Therefore, for the data processing platform, corresponding to the content shown in FIG. 3, the schematic diagram of the data processing platform's fusion processing of encrypted data can be shown in FIG. 5. In Figure 5, the data processing platform will determine the salt (and the traceability identifier contained in the salt) contained in the encrypted field, and the corresponding ciphertext information. It should be understood that in the actual data fusion processing, the data processing platform may perform multiple encryption / decryption processing (usually based on the encrypted UDF function) based on the ciphertext information, and finally obtain the corresponding data fusion result. In this process, the traceability identification will be continuously transmitted. Then, for the final data fusion result (usually displayed in the form of an output table), according to the recorded traceability identifier, it can be known that the data fusion result (which has been decrypted) includes traceability identifiers from two different sources. That is, the traceability identifiers 0100 and 0001 originating from the data provider A and the data provider B. It is worth noting that in FIG. 5, the two types of traceability identifiers are combined and expressed as 01000001. In this way, when the data processing platform needs to query the traceability identifiers, two traceability identifiers can be obtained according to the set character length. Of course, it should be understood that the representation manner shown in FIG. 5 is only an example. In practical applications, different representation forms may also be adopted, such as setting a separator between different traceability identifiers. This should not constitute a limitation on this application. What needs to be explained here is that since the data provider uses the key of a trusted third party during the encryption phase, when the data processing platform decrypts the encrypted data, it will also use the corresponding key of the trusted third party for decryption . In addition, the data processing platform also uses the key of a trusted third party in the process of encrypting / decrypting the ciphertext information multiple times. Of course, the process of using the key for encryption / decryption belongs to the prior art, and is not repeated here. The above are several embodiments of the traceable multi-party data processing method provided by the present application. Based on the same idea, this application also provides an embodiment of the traceable multi-party data processing device. As shown in FIG. On the other hand, the traceable multi-party data processing device includes: an identification module 601 that adds a traceability identifier corresponding to the data to be encrypted for the data to be encrypted; an encryption module 602 that encrypts the data to be encrypted and the traceability identifier To generate encrypted data; a sending module 603 that sends the encrypted data including the traceability identifier to a data processing platform for multi-party data fusion processing. Further, the identification module 601 uses a salting algorithm for the data to be encrypted, adds salt to the data to be encrypted, and adds a traceability identifier corresponding to the data to be encrypted to the salt. . The encryption module 602 uses a key provided by a trusted third party to encrypt the data to be encrypted and the salt including the traceability identifier to generate encrypted data; wherein the encrypted data includes encrypted data , The salt containing the traceability identifier, and the ciphertext information corresponding to the data to be encrypted. In the embodiment of this specification, on the data processing platform side, an embodiment of a traceable multi-party data processing device is also provided. As shown in FIG. 7, it specifically includes: a receiving module 701, which receives a traceability identifier sent by a data provider Encrypted data; determination module 702 determines the traceability identification in the encrypted data; processing module 703 performs data fusion calculation processing for the encryption to generate a data fusion result containing the traceability identification, so as to be based on the traceability Identifies the traceability of the encrypted data in the data fusion result. Further, the encrypted data includes an encrypted salt containing a traceability identifier, and ciphertext information corresponding to the data to be encrypted; the determining module 702 decrypts the encrypted data to determine that it is included in the encrypted data; State the traceability identification in the salt and record it. (2) The processing module 703 performs fusion calculation processing on the encrypted data of the non-traceable identifier. The processing module 703 performs traceability according to the recorded traceability identifier in the decryption result obtained after decrypting the data fusion result. The determination module 702 / processing module 703 uses a key provided by a trusted third party for decryption. In the 1990s, for a technical improvement, it can be clearly distinguished whether it is an improvement in hardware (for example, the improvement of circuit structures such as diodes, transistors, switches, etc.) or an improvement in software (for method and process Improve). However, with the development of technology, the improvement of many methods and processes can be regarded as a direct improvement of the hardware circuit structure. Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by a hardware entity module. For example, a programmable logic device (Programmable Logic Device, PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. It is programmed by the designer to "integrate" a digital system on a PLD, without having to ask a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of making integrated circuit chips manually, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used in program development and writing, and requires compilation. The previous original code must also be written in a specific programming language. This is called the Hardware Description Language (HDL). There is not only one kind of HDL, but many types, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog are commonly used. Those skilled in the art should also be clear that the hardware circuit that implements the logic method flow can be easily obtained by simply programming the method flow into the integrated circuit with the above-mentioned several hardware description languages. The controller may be implemented in any suitable way, for example, the controller may take the form of a microprocessor or processor and a computer-readable storage of computer-readable program code (such as software or firmware) executable by the (micro) processor. Media, logic gates, switches, application specific integrated circuits (ASICs), programmable logic controllers and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20 and Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art also know that, in addition to implementing the controller in pure computer-readable program code, it is entirely possible to make the controller use logic gates, switches, dedicated integrated circuits, programmable logic controllers, and Embedded in the form of a microcontroller, etc. to achieve the same function. Therefore, the controller can be considered as a hardware component, and the device included in the controller for implementing various functions can also be considered as a structure in the hardware component. Or even, a device for implementing various functions can be regarded as a structure that can be both a software module implementing the method and a hardware component.的 The system, device, module, or unit described in the above embodiments may be implemented by a computer chip or entity, or a product with a certain function. A typical implementation is a computer. Specifically, the computer may be, for example, a personal computer, a laptop, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or A combination of any of these devices. For the convenience of description, when describing the above device, the functions are divided into various units and described separately. Of course, when implementing the present application, the functions of each unit may be implemented in the same software or multiple software and / or hardware.的 Those skilled in the art should understand that the embodiments of the present invention may be provided as a method, a system, or a computer program product. Therefore, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including, but not limited to, magnetic disk memory, CD-ROM, optical memory, etc.) containing computer-usable program codes. . The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of the process and / or block in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing device to generate a machine, so that instructions generated by the processor of the computer or other programmable data processing device can be used to generate instructions. Means for realizing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams. These computer program instructions may also be stored in a computer-readable memory that can guide a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including a command device, The instruction device implements the functions specified in a flowchart or a plurality of processes and / or a block or a block of the block diagram. These computer program instructions can also be loaded on a computer or other programmable data processing device, so that a series of operating steps can be performed on the computer or other programmable device to generate a computer-implemented process, which can be executed on the computer or other programmable device. The instructions provide steps for implementing the functions specified in one or more flowcharts and / or one or more blocks of the block diagrams.计算 In a typical configuration, a computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory. Memory may include non-permanent memory, random access memory (RAM), and / or non-volatile memory in computer-readable media, such as read-only memory (ROM) or flash memory ( flash RAM). Memory is an example of a computer-readable medium. Computer-readable media include permanent and non-permanent, removable and non-removable media. Information can be stored by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), Read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only disc read-only memory (CD-ROM), digital versatile disc ( DVD) or other optical storage, magnetic tape cartridges, magnetic tape storage or other magnetic storage devices, or any other non-transmitting media, can be used to store information that can be accessed by computing devices. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves. It should also be noted that the terms "including," "including," or any other variation thereof are intended to encompass non-exclusive inclusion, so that a process, method, product, or device that includes a series of elements includes not only those elements but also Other elements not explicitly listed, or those that are inherent to such a process, method, product, or device. Without more restrictions, the elements defined by the sentence "including a ..." do not exclude the existence of other identical elements in the process, method, product or equipment including the elements.技术 Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, this application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Moreover, this application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk memory, CD-ROM, optical memory, etc.) containing computer-usable code. . This application can be described in the general context of computer-executable instructions executed by a computer, such as program modules. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform specific transactions or implement specific abstract data types. The present application can also be practiced in a decentralized computing environment. In these decentralized computing environments, transactions are performed by a remote processing device connected through a communication network. In a distributed computing environment, program modules can be located in local and remote computer storage media, including storage devices.的 Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. In particular, for the system embodiment, since it is basically similar to the method embodiment, the description is relatively simple. For the relevant part, refer to the description of the method embodiment. The above descriptions are merely examples of the present application and are not intended to limit the present application. For those skilled in the art, this application may have various modifications and changes. Any modification, equivalent replacement, or improvement made within the spirit and principle of this application shall be included in the scope of the patent application for this application.

601‧‧‧Identification Module

602‧‧‧ Encryption Module

603‧‧‧ sending module

701‧‧‧Receiving module

702‧‧‧ Determine the module

703‧‧‧Processing Module

The drawings described here are used to provide a further understanding of the present application and constitute a part of the present application. The schematic embodiments of the present application and the description thereof are used to explain the present application, and do not constitute an improper limitation on the present application. In the drawings: FIG. 1 is a schematic diagram of an architecture based on a traceable multi-party data processing process provided by an embodiment of the specification; FIG. 2 is a traceable multi-party data processing process at a data provider side provided by an embodiment of the specification; Figure 3 is a schematic diagram of data encryption provided by a data provider according to an embodiment of the specification; Figure 4 is a traceable multi-party data processing process on a data processing platform side provided by an embodiment of the specification; Figure 5 is provided by an embodiment of the specification Schematic diagram of data fusion processing performed by the data processing platform; FIG. 6 is a structural diagram of a traceable multi-party data processing device on the data provider side provided by the embodiment of the present specification; FIG. 7 is a data processing platform side provided by the embodiment of the present specification Schematic diagram of a traceable multi-party data processing device.

Claims (18)

A traceable multi-party data processing method, the method includes: for data to be encrypted, adding a traceability identification corresponding to the data to be encrypted; 加密 encrypting the data to be encrypted and the traceability identification to generate encrypted data; including the traceability identification The encrypted data is sent to a data processing platform for multi-party data fusion processing. The method according to claim 1, adding a traceability identifier corresponding to the data to be encrypted, specifically includes: using a salting algorithm for the data to be encrypted, and adding salt on the basis of the data to be encrypted; in the salt Add a traceability identifier corresponding to the data to be encrypted. The method according to claim 2, encrypting the to-be-encrypted data and the traceability identifier to generate encrypted data, specifically including: using a key provided by a trusted third party to the to-be-encrypted data and including the traceability identifier The encrypted salt is encrypted to generate encrypted data; The encrypted data includes the encrypted salt containing the traceability identifier and the ciphertext information corresponding to the data to be encrypted. A traceable multi-party data processing method, the method includes: receiving encrypted data sent by a data provider including a traceability identifier; determining a traceability identifier in the encrypted data; 进行 performing a data fusion calculation process on the encrypted data to generate the traceability identifier Data fusion result, so as to trace the encrypted data in the data fusion result according to the source identification. The method according to claim 4, the encrypted data includes an encrypted salt containing a traceability identification, and ciphertext information corresponding to the data to be encrypted; determining the traceability identification in the encrypted data, including: the encryption The data is decrypted and the traceability identification contained in the salt is determined and recorded. According to the method described in claim 5, performing data fusion calculation processing on the encrypted data specifically includes: 进行 performing fusion calculation processing on the encrypted data that is not traceable. According to the method described in claim 5, tracing the encrypted data in the data fusion result according to the traceability identifier specifically includes: 中 In the decryption result obtained after decrypting the data fusion result, perform the record according to the recorded traceability identifier. Traceability. The method described in claim 5 or 7 uses the following methods for decryption, which specifically include: Decryption using a key provided by a trusted third party. A traceable multi-party data processing device includes: 源 an identification module that adds a traceability identifier corresponding to the data to be encrypted for the data to be encrypted; an encryption module that encrypts the data to be encrypted and the traceability identifier to generate encrypted data A sending module sends the encrypted data including the traceability identification to a data processing platform for multi-party data fusion processing. The device according to claim 9, the identification module uses a salting algorithm for the data to be encrypted, adds salt to the data to be encrypted, and adds traceability corresponding to the data to be encrypted to the salt Logo. The device according to claim 10, the encryption module uses the key provided by a trusted third party to encrypt the data to be encrypted and the salt containing the traceability identification to generate encrypted data; wherein the encrypted data It contains the encrypted salt, which contains the traceability identifier, and the ciphertext information corresponding to the data to be encrypted. A traceable multi-party data processing device includes: ： a receiving module that receives encrypted data including a traceability identification sent by a data provider; a determination module that determines a traceability identification in the encrypted data; a processing module that performs data on the encryption The fusion calculation process generates a data fusion result including the traceability identifier, so as to trace the encrypted data in the data fusion result according to the traceability identifier. The device according to claim 12, the encrypted data includes an encrypted salt containing a traceability identifier, and ciphertext information corresponding to the data to be encrypted; the determination module decrypts the encrypted data to determine that the Traceability identification in this salt and record. The device according to claim 13, the processing module performs fusion calculation processing on the encrypted data of the non-traceable identity. The apparatus according to claim 13, the processing module, in the decryption result obtained after decrypting the data fusion result, traces the source according to the recorded traceability identifier. The device according to claim 13 or 15, the determining module or the processing module is decrypted using a key provided by a trusted third party. A traceable multi-party data processing device includes a processor and a memory, wherein: the memory stores a traceable multi-party data processing program; the processor calls a traceable multi-party data processing program stored in the memory, And execute: for the data to be encrypted, add a traceability identification corresponding to the data to be encrypted; 加密 encrypt the data to be encrypted and the traceability identification to generate encrypted data; 发送 send the encrypted data containing the traceability identification to a data processing platform, For multi-party data fusion processing. A traceable multi-party data processing device includes a processor and a memory, wherein: the memory stores a traceable multi-party data processing program; the processor calls a traceable multi-party data processing program stored in the memory, And execute: receiving the encrypted data containing the traceability identification sent by the data provider; determining the traceability identification in the encrypted data; 进行 performing data fusion calculation processing for the encryption to generate a data fusion result containing the traceability identification, so as to The encrypted data in the data fusion result is traced.