CN114979253B - Data push decision method, device, medium and equipment - Google Patents
Data push decision method, device, medium and equipment Download PDFInfo
- Publication number
- CN114979253B CN114979253B CN202210487697.4A CN202210487697A CN114979253B CN 114979253 B CN114979253 B CN 114979253B CN 202210487697 A CN202210487697 A CN 202210487697A CN 114979253 B CN114979253 B CN 114979253B
- Authority
- CN
- China
- Prior art keywords
- target
- data
- user
- decision
- party
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 230000004044 response Effects 0.000 claims abstract description 53
- 230000002776 aggregation Effects 0.000 claims description 22
- 238000004220 aggregation Methods 0.000 claims description 22
- 150000003839 salts Chemical class 0.000 claims description 13
- 238000004590 computer program Methods 0.000 claims description 8
- 238000007405 data analysis Methods 0.000 claims description 4
- 230000008569 process Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000004048 modification Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
- H04L63/0435—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption
Abstract
The embodiment of the specification provides a data push decision method and device. When the data pushing party needs to inquire whether to allow pushing of target data to target users, the data pushing party can send an inquiry request at least comprising a plurality of user identifiers to a pushing decision party, wherein the plurality of user identifiers comprise target user identifiers corresponding to the target users, and the user identifiers are generated by encrypting user information serving as privacy data; and then receiving response messages generated by the push decision-making party based on the decision information corresponding to the user identifications, and acquiring target decision-making information according to the response messages, wherein the target decision-making information is used for indicating whether to allow the target data to be pushed to the target user.
Description
Technical Field
One or more embodiments of the present disclosure relate to the field of computers, and in particular, to a data pushing method and apparatus.
Background
In some technical scenarios, before pushing target data to a user, a pushing decision-making party corresponding to the target data needs to be queried to determine whether to allow pushing of the target data to the user, and if and only if the pushing decision-making party allows pushing of the target data to the user, the data pushing party pushes the target data to the user. Whether or not the data pushing party pushes target data to the user may be unwilling to make the pushing decision party accurately aware of the user privacy concerns.
Disclosure of Invention
One or more embodiments of the present disclosure provide a data push decision method and apparatus.
In a first aspect, a data push decision method is provided, which is applied to a data push party. The method comprises the following steps: when whether target data is allowed to be pushed to a target user or not is required to be queried, a query request which at least comprises a plurality of user identifiers is sent to a pushing decision party, the plurality of user identifiers comprise target user identifiers corresponding to the target user, and the user identifiers are generated by encrypting user information serving as privacy data; and receiving response messages generated by the pushing decision party based on the decision information corresponding to the user identifiers from the pushing decision party, and acquiring target decision information according to the response messages, wherein the target decision information is used for indicating whether the target data is allowed to be pushed to the target user or not.
In a possible implementation manner, the query request further includes a first ciphertext obtained by encrypting the target user identifier with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key. The obtaining the target decision information according to the response message includes: decrypting the second ciphertext by using the first symmetric key to obtain a target key; and decrypting the decision information ciphertext corresponding to the target user identifier by using the target key to obtain the target decision information.
In one possible implementation, the user identifier is a hash value calculated by adding salt to user information as the private data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
In a second aspect, a data push decision method is provided, which is applied to a push decision party. The method comprises the following steps: receiving a query request sent by a data pushing party when whether target data is allowed to be pushed to a target user or not needs to be queried, wherein the query request comprises a plurality of user identifiers, the plurality of user identifiers comprise target user identifiers corresponding to the target user, and the user identifiers are generated by encrypting user information serving as privacy data; generating a response message based on the decision information corresponding to each of the plurality of user identifiers, and sending the response message to the data pushing party, so that the data pushing party obtains target decision information based on the response message, wherein the target decision information is used for indicating whether to allow the target data to be pushed to the target user.
In a possible implementation manner, the query request further includes a first ciphertext obtained by encrypting the target user identifier with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key.
In one possible implementation, the user identifier is a hash value calculated by adding salt to user information as the private data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
In a possible implementation manner, the push decision party is a traffic aggregation platform, and the method further includes: and determining whether the plurality of user identifiers are positioned in a first set which is maintained in advance and corresponds to the target data, and if so, sending the query request to a data provider of the target data so that the data provider returns decision information corresponding to the plurality of user identifiers.
In a third aspect, a data push decision device is provided, deployed at a data push party. The device comprises: the data sending unit is configured to send a query request at least comprising a plurality of user identifiers to a pushing decision party when whether target data is allowed to be pushed to a target user needs to be queried, wherein the plurality of user identifiers comprise target user identifiers corresponding to the target user, and the user identifiers are generated by encrypting user information serving as privacy data; a data receiving unit configured to receive, from the push decision party, a response message generated by the push decision party based on decision information corresponding to each of the plurality of user identities; and the data analysis unit is configured to acquire target decision information according to the response message, wherein the target decision information is used for indicating whether the target data is allowed to be pushed to the target user or not.
In a possible implementation manner, the query request further includes a first ciphertext obtained by encrypting the target user identifier with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key. The data analysis unit is configured to decrypt the second ciphertext by using the first symmetric key to obtain a target key; and decrypting the decision information ciphertext corresponding to the target user identifier by using the target key to obtain the target decision information.
In one possible implementation, the user identifier is a hash value calculated by adding salt to user information as the private data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
In a fourth aspect, a data push decision device is provided, deployed at a push decision party. The device comprises: the data receiving unit is configured to receive a query request sent by a data pushing party when whether target data is allowed to be pushed to a target user or not is required to be queried, wherein the query request comprises a plurality of user identifiers, the plurality of user identifiers comprise target user identifiers corresponding to the target user, and the user identifiers are generated by encrypting user information serving as privacy data; a data generating unit configured to generate a response message based on decision information corresponding to each of the plurality of user identifications; and the data sending unit is configured to send the response message to the data pushing party, so that the data pushing party obtains target decision information based on the response message, wherein the target decision information is used for indicating whether to allow the target data to be pushed to the target user.
In a possible implementation manner, the query request further includes a first ciphertext obtained by encrypting the target user identifier with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key.
In one possible implementation, the user identifier is a hash value calculated by adding salt to user information as the private data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
In a possible implementation manner, the push decision party is a traffic aggregation platform, and the apparatus further includes: and the set query unit is configured to determine whether the plurality of user identifiers are in a first set corresponding to the target data, which is maintained in advance, and if so, send the query request to a data provider of the target data, so that the data provider returns decision information corresponding to each of the plurality of user identifiers.
In a fifth aspect, there is provided a computer readable storage medium having stored thereon a computer program/instruction which, when executed in a computing device, performs the method of any of the first or second aspects.
In a sixth aspect, there is provided a computing device comprising a memory having stored therein a computer program/instruction and a processor implementing the method according to any of the first or second aspects when executing the computer program/instruction.
Through the method and the device provided in one or more embodiments of the present disclosure, when a data pushing party needs to query a pushing decision party whether to allow pushing target data to a target user, the query request sent by the pushing decision party includes a plurality of user identifiers including target user identifiers corresponding to the target user, and the pushing decision party returns a response message to the data pushing party based on decision information corresponding to each of the plurality of user identifiers, so that the data pushing party can acquire target decision information corresponding to the target user identifiers based on the response message, so as to decide whether to push the target data to the target user according to the target decision information. In the decision process, the pushing decision party cannot accurately acquire the target user requested to be queried by the data pushing party because the query request comprises a plurality of user identifiers, namely, cannot accurately acquire whether the data pushing party pushes target data to the target user.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present description, the drawings that are needed in the description of the embodiments will be briefly introduced below, it being obvious that the drawings in the following description are only some embodiments of the present invention, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic diagram of a technical scenario exemplarily provided in an embodiment of the present specification;
FIG. 2 is a flowchart of a data push decision method provided in an embodiment of the present disclosure;
FIG. 3 is a schematic diagram of a data push decision device according to an embodiment of the present disclosure;
fig. 4 is a schematic diagram of another data pushing device provided in the embodiment of the present disclosure.
Detailed Description
Various non-limiting embodiments provided by the present specification are described in detail below with reference to the attached drawings.
In some technical scenarios, before pushing target data to a user, a pushing decision-making party corresponding to the target data needs to be queried to determine whether to allow pushing of the target data to the user, and if and only if the pushing decision-making party allows pushing of the target data to the user, the data pushing party pushes the target data to the user. Referring to the technical scenario exemplarily provided in fig. 1, various audio and video media may be used as a data pusher, and an advertiser may be used as a data provider; wherein the advertiser may provide advertising material to each media as targeted data in anticipation of each media presenting the advertising material to a user of each media. More specifically, taking a typical RTA (real time application programming interface) advertisement as An example, the traffic aggregation platform may connect n media of the data pushers A1 to An and m of the data providers B1 to Bm as advertisers of the data pushers; before each media pushes an advertisement material provided by an advertiser to its user, it is often necessary to query the traffic aggregation platform, which is the pushing decision-making party, or the advertiser to which the advertisement material belongs, whether the corresponding advertisement material is allowed to be delivered to the user.
Whether the data pushing party pushes target data to the user may involve user privacy and be unwilling to make the pushing decision party aware. Therefore, in the embodiment of the present disclosure, when a data pushing party needs to query a pushing decision party whether to allow pushing target data to a target user, the data pushing party sends a query request to the pushing decision party, where the query request includes a plurality of user identifiers including target user identifiers corresponding to the target user, and the pushing decision party returns a response message to the data pushing party based on decision information corresponding to the plurality of user identifiers, so that the data pushing party can acquire target decision information corresponding to the target user identifiers based on the response message, so as to determine whether to push the target data to the target user according to the target decision information. In the decision process, the pushing decision party cannot accurately acquire the target user requested to be queried by the data pushing party because the query request comprises a plurality of user identifiers, namely cannot acquire whether the data pushing party pushes target data to the target user.
Fig. 2 is a flowchart of a data push decision method provided in the embodiment of the present disclosure. The data pusher and the pushing decision maker involved in the method may each be implemented as any apparatus, platform, device or cluster of devices having computing/processing capabilities. As shown in fig. 2, the method may include, but is not limited to, the following steps 22-28.
In step 22, when the data pushing party needs to query whether to allow pushing of the target data to the target user, a query request including at least a plurality of user identities is sent to the pushing decision party, wherein the plurality of user identities includes the target user identity of the target user.
The user identifier may be, for example, an account number of the user registered with the data pusher, or may also be user information such as an identification card number, a name, a telephone number, a mail address, and the like. Alternatively, in view of the fact that the foregoing various user information belongs to the private data, the user identifier may be generated by encrypting the user information as the private data, for example, the user identifier may be a hash value calculated by adding salt to the user information as the private data. For example, for the User information User id a of the User a, a numerical salt corresponding to the User information User id a may be generated to salt the User id a, a hash value anonymous id a of the salted User id a may be calculated, and the anonymous id a may be used as the User identifier of the User a. It will be appreciated that the user identification may also be obtained by processing the user information in other ways; in addition, the technical solution in the embodiment of the present specification will be mainly exemplified by taking the target user identification being anonymous id a.
When the data pushing party needs to inquire whether the pushing decision party allows pushing target data to the user A, the data pushing party can acquire other user identifications except the anonymous id A and add the acquired other user identifications and the target user identification anonymous id A into an inquiry request; for example, the user identification anonymous id B may also be obtained and added to the query request. The aforementioned User identification anonymous id B may be obtained based on corresponding User information User id B, and the User id B may be User information of the User B registered in the data pusher, or the User id B may also be other data generated based on the User id a and having the same or similar data structure as the User id a, i.e. the User id B may not be User information of the real User registered in the data pusher.
The data pushing party can encrypt the user identifier anonymous id a by using a first symmetric key1 in the query request to obtain a first ciphertext E (key 1, anonymous id a). In addition, the query request may further include indication information for indicating the target data, where the indication information may include, for example, an identifier of a data provider of the target data and a unique identifier allocated by the data provider of the target data to the target data.
Next, in step 24, the push decision-maker generates a response message based on the decision information corresponding to each of the plurality of user identities.
The data pusher and the data provider of the target data may be crowd-contoured by secure matching, for example, to construct a first set of target data comprising a plurality of user identities that are recognized by both the data pusher and the data provider, which may be stored in association with the indication information of the target data to the traffic aggregation platform. The traffic aggregation platform and the data provider of the target data may both serve as push decision-making parties, however, query requests sent by the data push parties may be received by the traffic aggregation platform, so that the traffic aggregation platform may determine, based on indication information included in the query requests received by the traffic aggregation platform, whether a plurality of user identifiers in the query requests belong to a first set associated with the indication information in the query requests, and if so, obtain decision information corresponding to each of the plurality of user identifiers in the query requests by the traffic aggregation platform or the data provider of the target data.
When the pushing decision-making party is a traffic aggregation platform, the traffic aggregation platform may determine decision information corresponding to each of the plurality of user identifiers based on a pre-configured decision rule corresponding to the target data, and further execute the foregoing step 24 based on the decision information corresponding to each of the plurality of user identifiers; or, the traffic aggregation platform may continue forwarding the query request to the data provider of the target data, so that the data provider of the target data determines, based on the preconfigured decision rule corresponding to the target data, the decision information corresponding to each of the plurality of user identifiers and returns the decision information to the traffic aggregation platform, so that the traffic aggregation platform executes the step 24.
And the decision information corresponding to the user identifier is used for indicating whether the pushing decision party allows pushing the target data to the user corresponding to the user identifier. For example, when the value of the decision information corresponding to the user identifier is true value true or a first preset value, the representation allows pushing the target data to the user corresponding to the user identifier, and when the value of the decision information corresponding to the user identifier is true value false or a second preset value, the representation does not allow pushing the target data to the user corresponding to the user identifier.
When the pushing decision-making party is a data provider of the target data, the query request sent by the data pushing party can be forwarded to the data provider of the target data through the flow aggregation platform, and can also be directly sent to the data provider of the target data without passing through the flow aggregation platform; the data provider of the target data may determine the decision information corresponding to each of the plurality of user identities based on the preconfigured decision rule corresponding to the target data, and further proceed to step 24.
The response message may specifically include decision information corresponding to each of the plurality of user identifiers. For example, the response message may include decision information Value a corresponding to the anonymous id a and decision information Value B corresponding to the anonymous id B.
In addition to the plurality of user identities, the query request further includes a first ciphertext obtained by encrypting the target user identity using the first symmetric key 1. The response message may specifically include a second ciphertext obtained by encrypting the first ciphertext with the second symmetric key2, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers with a third symmetric key corresponding to each of the plurality of user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with the second symmetric key. Illustratively, in the case where the query request includes a first ciphertext encrypted obtained by encrypting the target user identifier anonymous id a with the first symmetric key1, the push decision party may encrypt the first ciphertext encrypted with the second symmetric key2 to obtain a second ciphertext E (key 2, E (anonymous id a)); the pushing decision party may also encrypt the user identifier of the query request with the second symmetric key2 to obtain a third symmetric key E (key 2, anonymous id a), encrypt the user identifier of the query request with the second symmetric key2 to obtain a third symmetric key E (key 2, anonymous id B), encrypt the decision information Value a corresponding to the anonymous id a with the third symmetric key E (key 2, anonymous id a) corresponding to the anonymous id a to obtain a decision information ciphertext E (key 2, anonymous id a), encrypt the decision information Value B corresponding to the anonymous id B with the third symmetric key E (key 2, anonymous id B) corresponding to the anonymous id B to obtain a decision information ciphertext E (Value B); further, a response message including a second ciphertext E (key 2, E (anonymous id a)), a decision information ciphertext E (key 2, anonymous id a), value a) corresponding to the anonymous id a, and a decision information ciphertext E (key 2, anonymous id B), value B) corresponding to the anonymous id B is generated.
Next, at step 26, the push decision sends a response message to the data pusher.
Finally, at step 28, the data pusher obtains the target decision information based on the response message.
When the response message includes decision information corresponding to each of the plurality of user identifiers, the data pushing party can directly extract the target decision information corresponding to the target user from the decision information corresponding to each of the plurality of user identifiers.
When the response message includes the second ciphertext and decision information ciphertext corresponding to each of the plurality of user identifiers, the data pushing party can decrypt the second ciphertext by using the first symmetric key to obtain a target key, and further decrypt the decision information ciphertext corresponding to the target user identifier by using the target key to obtain target decision information for indicating whether to allow pushing of target data to the target user. For example, as described above, when the response message includes the second ciphertext E (key 2, E (key 1, anonymous id a)), the decision information ciphertext E (key 2, anonymous id a), value a) corresponding to the anonymous id a, and the decision information ciphertext E (key 2, anonymous id B), value B) corresponding to the anonymous id B, the data pusher may decrypt the second ciphertext E (key 2, E (key 1, anonymous id a)) using the first symmetric key1 to obtain the target key, where the target key is substantially the same as the second key2 encrypting the anonymous id a to obtain the third key E (key 2, anonymous id a); then, the decision information ciphertext E (key 2, anonymous id a), value a) corresponding to the anonymous id a can be decrypted by using the target key E (key 2, anonymous id a), so as to obtain the target decision information Value a corresponding to the anonymous id a. The process of obtaining the target decision information corresponding to the target user identifier by the data pushing party according to the foregoing exemplary description may be understood that the data pushing party may only decrypt the decision information ciphertext corresponding to the target user identifier, and may not decrypt the decision information corresponding to each of the other user identifiers except the target user identifier in the plurality of user identifiers, so that it may be avoided that the data pushing party may learn too much whether the pushing decision party is allowed to push the target data to other users.
It may be appreciated that the data pushing party needs to decide whether to perform pushing the target data to the target user according to the obtained target decision information, for example, when the obtained target decision information is true or the first predetermined value, the data pushing party needs to continue performing pushing the target data to the target user corresponding to the target user identifier.
Through the above embodiments, when the data pushing party needs to query whether to allow pushing of target data to a certain target user, the pushing decision party including the traffic aggregation platform and the data provider can be prevented from accurately knowing whether to push the target data to the target user, and the data pushing party can be prevented from excessively knowing whether the pushing decision party including the traffic aggregation platform and the data provider allows pushing of target data to other users than the target user.
Based on the same conception as the foregoing method embodiment, the present disclosure further provides a data push decision device, which is deployed on a data push party. As shown in fig. 3, the apparatus includes: a data sending unit 32 configured to send, to a pushing decision party, a query request including at least a plurality of user identifiers when it is required to query whether to allow pushing of target data to a target user, where the plurality of user identifiers include target user identifiers corresponding to the target user, and the user identifiers are generated by encrypting user information serving as private data; a data receiving unit 34 configured to receive, from the push decision party, a response message generated by the push decision party based on the decision information corresponding to each of the plurality of user identities; and a data parsing unit 36 configured to obtain target decision information according to the response message, where the target decision information is used to indicate whether to allow pushing the target data to the target user.
In a possible implementation manner, the query request further includes a first ciphertext obtained by encrypting the target user identifier with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key. The data parsing unit 36 is configured to decrypt the second ciphertext by using the first symmetric key to obtain a target key; and decrypting the decision information ciphertext corresponding to the target user identifier by using the target key to obtain the target decision information.
In one possible implementation, the user identifier is a hash value calculated by adding salt to user information as the private data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
Based on the same conception as the foregoing method embodiment, the present disclosure further provides a data push decision device, which is deployed at a push decision party. As shown in fig. 4, the apparatus includes: a data receiving unit 42, configured to receive, from a data pushing party, a query request sent when it needs to query whether to allow pushing of target data to a target user, where the query request includes a plurality of user identifiers, where the plurality of user identifiers includes a target user identifier corresponding to the target user, and the user identifiers are generated by encrypting user information serving as private data; a data generating unit 44 configured to generate a response message based on the decision information corresponding to each of the plurality of user identities; and a data sending unit 46 configured to send the response message to the data pushing party, so that the data pushing party obtains target decision information based on the response message, where the target decision information is used to indicate whether to allow the target data to be pushed to the target user.
In a possible implementation manner, the query request further includes a first ciphertext obtained by encrypting the target user identifier with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key.
In one possible implementation, the user identifier is a hash value calculated by adding salt to user information as the private data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
In a possible implementation manner, the push decision party is a traffic aggregation platform, and the apparatus further includes: and the set query unit is configured to determine whether the plurality of user identifiers are in a first set corresponding to the target data, which is maintained in advance, and if so, send the query request to a data provider of the target data, so that the data provider returns decision information corresponding to each of the plurality of user identifiers.
Those of skill in the art will appreciate that in one or more of the examples described above, the functions described herein may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the computer programs corresponding to these functions may be stored in a computer readable medium or transmitted as one or more instructions/codes on a computer readable medium, so that the computer programs corresponding to these functions are executed by a computer, by which the methods described in any of the embodiments of the present specification are implemented.
There is also provided in embodiments of the present specification a computer readable storage medium having stored thereon a computer program which, when executed in a computing device, performs the method steps performed by the data pushing party or the pushing decision party in any of the embodiments of the present specification.
The embodiment of the present specification also provides a computing device, including a memory and a processor, where the memory stores executable code, and the processor executes the executable code to implement method steps performed by a data pushing party or a pushing decision party in any one embodiment of the present specification.
In this specification, each embodiment is described in a progressive manner, and the same and similar parts in each embodiment are referred to each other, and each embodiment is mainly described in a different point from other embodiments. In particular, for the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments in part.
The foregoing describes specific embodiments of the present disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims can be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
The foregoing embodiments have been provided for the purpose of illustrating the general principles of the present invention in further detail, and are not to be construed as limiting the scope of the invention, but are merely intended to cover any modifications, equivalents, improvements, etc. based on the teachings of the invention.
Claims (12)
1. A data push decision method, applied to a data push party, the method comprising:
when whether target data is allowed to be pushed to a target user or not needs to be queried, a query request which at least comprises a plurality of user identifiers is sent to a pushing decision party, wherein the plurality of user identifiers comprise target user identifiers corresponding to the target user, the user identifiers are hash values obtained by adding salt to user information serving as privacy data and then calculating, and the query request also comprises indication information used for indicating the target data;
and receiving response messages generated by the pushing decision party based on the decision information corresponding to the user identifiers from the pushing decision party, and acquiring target decision information according to the response messages, wherein the target decision information is used for indicating whether the target data is allowed to be pushed to the target user or not.
2. The method of claim 1, wherein the query request further includes a first ciphertext obtained by encrypting the target user identifier with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key;
the obtaining the target decision information according to the response message includes:
decrypting the second ciphertext by using the first symmetric key to obtain a target key;
and decrypting the decision information ciphertext corresponding to the target user identifier by using the target key to obtain the target decision information.
3. A data push decision method, applied to a push decision party, the method comprising:
receiving a query request sent by a data pushing party when whether target data is allowed to be pushed to a target user or not is required to be queried from the data pushing party, wherein the query request comprises a plurality of user identifiers, the plurality of user identifiers comprise target user identifiers corresponding to the target user, the user identifiers are hash values obtained by adding salt to user information serving as privacy data and then calculating, and the query request also comprises indication information for indicating the target data;
generating a response message based on the decision information corresponding to each of the plurality of user identifiers, and sending the response message to the data pushing party, so that the data pushing party obtains target decision information based on the response message, wherein the target decision information is used for indicating whether to allow the target data to be pushed to the target user.
4. The method of claim 3, further comprising encrypting the target user identification with a first symmetric key to obtain a first ciphertext; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key.
5. The method of any of claims 3-4, the push decision maker being a traffic aggregation platform, the method further comprising: and determining whether the plurality of user identifiers are positioned in a first set which is maintained in advance and corresponds to the target data, and if so, sending the query request to a data provider of the target data so that the data provider returns decision information corresponding to the plurality of user identifiers.
6. A data push decision device deployed at a data push party, the device comprising:
the data sending unit is configured to send a query request at least comprising a plurality of user identifiers to a pushing decision party when whether target data is allowed to be pushed to a target user needs to be queried, wherein the plurality of user identifiers comprise target user identifiers corresponding to the target user, the user identifiers are hash values obtained by adding salt to user information serving as privacy data and then calculating, and the query request also comprises indication information for indicating the target data;
a data receiving unit configured to receive, from the push decision party, a response message generated by the push decision party based on decision information corresponding to each of the plurality of user identities;
and the data analysis unit is configured to acquire target decision information according to the response message, wherein the target decision information is used for indicating whether the target data is allowed to be pushed to the target user or not.
7. The apparatus of claim 6, the query request further comprising a first ciphertext obtained by encrypting the target user identification with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key;
the data analysis unit is specifically configured to decrypt the second ciphertext by using the first symmetric key to obtain a target key; and decrypting the decision information ciphertext corresponding to the target user identifier by using the target key to obtain the target decision information.
8. A data push decision device deployed at a push decision party, the device comprising:
the data receiving unit is configured to receive a query request sent by a data pushing party when whether target data is allowed to be pushed to a target user or not is required to be queried, wherein the query request comprises a plurality of user identifiers, the plurality of user identifiers comprise target user identifiers corresponding to the target user, the user identifiers are hash values obtained by adding salt to user information serving as privacy data and then calculating, and the query request also comprises indication information for indicating the target data;
a data generating unit configured to generate a response message based on decision information corresponding to each of the plurality of user identifications;
and the data sending unit is configured to send the response message to the data pushing party, so that the data pushing party obtains target decision information based on the response message, wherein the target decision information is used for indicating whether to allow the target data to be pushed to the target user.
9. The apparatus of claim 8, the query request further comprising a first ciphertext obtained by encrypting the target user identification with a first symmetric key; the response message comprises a second ciphertext obtained by encrypting the first ciphertext by using a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting decision information corresponding to each of the plurality of user identifiers by using a third symmetric key corresponding to each of the plurality of user identifiers, wherein the third key corresponding to the user identifier is obtained by encrypting the user identifier by using the second symmetric key.
10. The apparatus of any of claims 8-9, the push decision maker being a traffic aggregation platform, the apparatus further comprising: and the set query unit is configured to determine whether the plurality of user identifiers are in a first set corresponding to the target data, which is maintained in advance, and if so, send the query request to a data provider of the target data, so that the data provider returns decision information corresponding to each of the plurality of user identifiers.
11. A computer readable storage medium having stored thereon a computer program which, when executed in a computing device, performs the method of any of claims 1-5.
12. A computing device comprising a memory and a processor, the memory having stored therein a computer program which, when executed by the processor, implements the method of any of claims 1-5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210487697.4A CN114979253B (en) | 2022-05-06 | 2022-05-06 | Data push decision method, device, medium and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210487697.4A CN114979253B (en) | 2022-05-06 | 2022-05-06 | Data push decision method, device, medium and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114979253A CN114979253A (en) | 2022-08-30 |
| CN114979253B true CN114979253B (en) | 2024-03-12 |
Family
ID=82981578
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210487697.4A Active CN114979253B (en) | 2022-05-06 | 2022-05-06 | Data push decision method, device, medium and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114979253B (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107592217A (en) * | 2017-09-01 | 2018-01-16 | 北京奇虎科技有限公司 | A kind of user identification method and device |
| CN108712379A (en) * | 2018-04-08 | 2018-10-26 | 北京奇艺世纪科技有限公司 | Data push method and device |
| CN111008325A (en) * | 2020-03-10 | 2020-04-14 | 支付宝(杭州)信息技术有限公司 | Data query method, device, electronic equipment and system |
| CN113886887A (en) * | 2021-10-25 | 2022-01-04 | 支付宝(杭州)信息技术有限公司 | Data query method and device based on multi-party security calculation |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013121790A1 (en) * | 2012-02-17 | 2013-08-22 | 日本電気株式会社 | Information processing device for handling privacy information, information processing system for handling privacy information, and information processing method and program for handling privacy information |
-
2022
- 2022-05-06 CN CN202210487697.4A patent/CN114979253B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107592217A (en) * | 2017-09-01 | 2018-01-16 | 北京奇虎科技有限公司 | A kind of user identification method and device |
| CN108712379A (en) * | 2018-04-08 | 2018-10-26 | 北京奇艺世纪科技有限公司 | Data push method and device |
| CN111008325A (en) * | 2020-03-10 | 2020-04-14 | 支付宝(杭州)信息技术有限公司 | Data query method, device, electronic equipment and system |
| CN113886887A (en) * | 2021-10-25 | 2022-01-04 | 支付宝(杭州)信息技术有限公司 | Data query method and device based on multi-party security calculation |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114979253A (en) | 2022-08-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10778633B2 (en) | Differential privacy for message text content mining | |
| CN107801165B (en) | Business short message pushing method and device, computer equipment and storage medium | |
| CN109146481B (en) | Method, medium and device for automatically importing account private key of blockchain wallet and blockchain system | |
| US20150040245A1 (en) | Privacy-preserving matching service | |
| CN110086817B (en) | Reliable user service system and method | |
| CN109981633B (en) | Method, apparatus and computer-readable storage medium for accessing server | |
| US20140172830A1 (en) | Secure search processing system and secure search processing method | |
| CN109376172B (en) | Data acquisition method and system based on block chain | |
| CN107196919B (en) | Data matching method and device | |
| CN111177769A (en) | Private data protection list query method and related list query system | |
| CN107196918B (en) | Data matching method and device | |
| WO2019179625A1 (en) | Distributed data storage network nodes and methods | |
| CN112860790B (en) | Data management method, system and device | |
| CN116633701B (en) | Information transmission method, apparatus, computer device and storage medium | |
| CN114979253B (en) | Data push decision method, device, medium and equipment | |
| CN109842554B (en) | Routing method, device, equipment and storage medium of equipment service | |
| CN112907268A (en) | Attribution method, apparatus, device and medium | |
| CN112395633B (en) | Method and device for carrying out data statistics by combining multiple parties for protecting privacy | |
| CN110049067B (en) | Transmission method and device of session key and computer-readable storage medium | |
| CN111049787B (en) | Information association method, device, system and computer readable storage medium | |
| CN107193884B (en) | Data matching method and device | |
| CN111404901A (en) | Information verification method and device | |
| CN116095155A (en) | Data push decision method and device | |
| CN113783847B (en) | Message interaction method, device, computer equipment and storage medium | |
| CN116150445B (en) | Batch information query method, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |