CN114979253A - Data push decision-making method and device - Google Patents
Data push decision-making method and device Download PDFInfo
- Publication number
- CN114979253A CN114979253A CN202210487697.4A CN202210487697A CN114979253A CN 114979253 A CN114979253 A CN 114979253A CN 202210487697 A CN202210487697 A CN 202210487697A CN 114979253 A CN114979253 A CN 114979253A
- Authority
- CN
- China
- Prior art keywords
- user
- target
- data
- decision
- encrypting
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 41
- 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 9
- 238000007405 data analysis Methods 0.000 claims description 5
- 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
- 238000006467 substitution reaction Methods 0.000 description 1
Images
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 a data push decision device. When a data pushing party needs to inquire whether target data are allowed to be pushed to a target user, the data pushing party can send a query request at least comprising a plurality of user identifications to a pushing decision-making party, wherein the plurality of user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data; and then, a response message generated by the push decision-making party based on the decision information corresponding to each of the plurality of user identifications can be received from the push decision-making party, and target decision information is obtained according to the response message, wherein the target decision information is used for indicating whether target data are allowed to be pushed to the target user.
Description
Technical Field
One or more embodiments of the present specification relate to the field of computers, and in particular, to a data pushing method and apparatus.
Background
In some technical scenarios, before a data pushing party pushes target data to a user, a pushing decision party corresponding to the target data needs to query whether to allow the target data to be pushed to the user, and if and only if the pushing decision party allows the target data to be pushed to the user, the data pushing party pushes the target data to the user. However, whether the data push party pushes the target data to the user may not be willing to let the push decision party know it accurately because of the privacy of the user.
Disclosure of Invention
One or more embodiments of the present specification 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 are allowed to be pushed to a target user is required to be inquired, sending an inquiry request at least comprising a plurality of user identifications to a pushing decision-making party, wherein the plurality of user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data; and receiving a response message generated by the push decision maker based on the decision information corresponding to the user identifications respectively, and acquiring 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.
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 includes a second ciphertext obtained by encrypting the first ciphertext with a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting the decision information corresponding to the user identifiers with a third symmetric key corresponding to the user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with the second symmetric key. The obtaining of the objective 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 a possible embodiment, the user identifier is a hash value calculated by adding salt to the user information as the privacy 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 an inquiry request sent by a data pushing party when the data pushing party needs to inquire whether target data are allowed to be pushed to a target user, wherein the inquiry request comprises a plurality of user identifications, the plurality of user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data; and generating a response message based on the decision information corresponding to each of the plurality of user identifications, 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 the target data is allowed 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 includes a second ciphertext obtained by encrypting the first ciphertext with a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting the decision information corresponding to the user identifiers with a third symmetric key corresponding to the user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with the second symmetric key.
In a possible embodiment, the user identifier is a hash value calculated by adding salt to the user information as the privacy data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
In one possible implementation, the push decision-maker is a traffic aggregation platform, the method further comprising: and determining whether the plurality of user identifications are located in a first set which is maintained in advance and corresponds to the target data, if so, sending the query request to a data provider of the target data, and enabling the data provider to return decision information corresponding to the plurality of user identifications.
In a third aspect, a data pushing decision device is provided and is deployed on a data pusher. The device comprises: the data sending unit is configured to send a query request at least comprising a plurality of user identifications to a push decision maker when whether target data are allowed to be pushed to a target user is required to be queried, wherein the plurality of user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data; a data receiving unit configured to receive, from the push decision maker, a response message generated by the push decision maker based on decision information corresponding to each of the plurality of user identifications; 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 includes a second ciphertext obtained by encrypting the first ciphertext with a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting the decision information corresponding to the user identifiers with a third symmetric key corresponding to the user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with 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 a possible embodiment, the user identifier is a hash value calculated by adding salt to the user information as the privacy 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 and is deployed on a push decision party. The device comprises: the data receiving unit is configured to receive an inquiry request sent by a data pushing party when the data pushing party needs to inquire whether target data are allowed to be pushed to a target user, wherein the inquiry request comprises a plurality of user identifications, the plurality of user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data; the data generation unit is configured to generate a response message based on the 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 the target data is allowed 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 includes a second ciphertext obtained by encrypting the first ciphertext with a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting the decision information corresponding to the user identifiers with a third symmetric key corresponding to the user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with the second symmetric key.
In a possible embodiment, the user identifier is a hash value calculated by adding salt to the user information as the privacy data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
In one possible embodiment, the push decision-making 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 located in a first set corresponding to the target data, 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/instructions which, when executed in a computing device, the 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/instructions and a processor that, when executing the computer program/instructions, performs the method of any one of the first or second aspects.
By the method and the apparatus provided in one or more embodiments of the present specification, when a data push party needs to query a push decision party whether to allow target data to be pushed to a target user, a query request sent to the push decision party includes a plurality of user identifiers including a target user identifier corresponding to the target user, and the push decision party returns a response message to the data push party based on decision information corresponding to each of the plurality of user identifiers, so that the data push party can obtain target decision information corresponding to the target user identifier based on the response message, and then determine whether to push the target data to the target user according to the target decision information. In the decision process, the push decision-making party cannot accurately know the target user requested to be queried by the data push-making party because the query request contains a plurality of user identifiers, that is, cannot accurately know whether the data push-making party pushes the target data to the target user.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of an exemplary provided technical scenario 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 specification;
fig. 3 is a schematic diagram of a data push decision device provided in an embodiment of the present disclosure;
fig. 4 is a schematic diagram of another data pushing apparatus provided in an embodiment of the present specification.
Detailed Description
Various non-limiting embodiments provided by the present specification are described in detail below with reference to the attached figures.
In some technical scenarios, before a data push party pushes target data to a user, a push decision party corresponding to the target data needs to query whether to allow the user to push the target data, and if and only if the push decision party allows the user to push the target data, the data push party pushes the target data to the user. Referring to the technical scenario exemplarily provided in fig. 1, various audio/video media may serve as a data provider, and an advertiser may serve as a data provider; wherein an advertiser may provide targeted data advertising material to each media in anticipation of each media presenting the advertising material to users 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 serving as data pushers, such as a data pusher a1 to a data pusher An, and connect m advertisers serving as data providers, such as a data provider B1 to a data provider Bm; before each media pushes the advertisement material provided by the advertiser to its user, it is usually necessary to query the traffic aggregation platform as a push decision party or the advertiser to which the advertisement material belongs whether to allow the corresponding advertisement material to be delivered to the user.
Whether a data push pushes targeted data to a user may involve user privacy and may not be willing to let the push decision-maker know. Therefore, in this embodiment, a data push decision method and an apparatus are provided, when a data push party needs to query a push decision party whether to allow pushing of target data to a target user, a query request sent to the push decision party includes a plurality of user identifiers including a target user identifier corresponding to the target user, and the push decision party returns a response message to the data push party based on decision information corresponding to each of the plurality of user identifiers, so that the data push party can obtain target decision information corresponding to the target user identifier based on the response message, and then determine whether to push the target data to the target user according to the target decision information. In the decision making process, the push decision maker cannot accurately know the target user requested to be queried by the data push maker because the query request contains a plurality of user identifications, that is, cannot know whether the data push maker pushes the target data to the target user.
Fig. 2 is a flowchart of a data push decision method provided in an embodiment of the present specification. The data push and push decision maker involved in the method may each be implemented as any device, 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 push party needs to query whether to allow the target data to be pushed to the target user, a query request at least including a plurality of user identifiers is sent to the push decision party, where the plurality of user identifiers includes the target user identifier of the target user.
The user identification may be, for example, an account number of the user registered in the data push party, or may also be user information such as an identification number, a name, a telephone number, a mail address, and the like. Alternatively, in view of the foregoing that various user information belongs to the private data, the user identifier may also be generated by encrypting the user information as the private data, for example, the user identifier may also 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 value salt corresponding to the User information User id a may be generated first to salt the User id a, calculate a hash value anonymous id a of the salted User id a, and use the anonymous id a as the User identifier of the User a. It is to be understood that the user identification may also be obtained by processing the user information in other ways; in addition, the following description mainly exemplifies that the target user identifier is anonymous id a as an example to illustrate the technical solution in the embodiment of the present specification.
When the data pushing party needs to inquire whether the pushing decision party allows the target data to be pushed to the user A, the data pushing party can also obtain other user identifications except the anonymous id A, and adds the obtained other user identifications and the target user identification anonymous id A into the inquiry request; the user identification anonymous id B may also be obtained and added to the query request, for example. The aforementioned User identification anonymous id B may be obtained based on corresponding User information User id B, which may be User information of User B registered at the data push, or User id B may also be other data generated based on User id a and having the same or similar data structure as User id a, i.e. User id B may also not be User information of a real User registered at the data push.
The query request may further include a first ciphertext E (key1, anonymous id a) obtained by encrypting the user identifier anonymous id a with the first symmetric key1 by the data pusher. The query request may further include indication information for indicating the target data, for example, the indication information may specifically include an identifier of a data provider of the target data and a unique identifier assigned to the target data by the data provider of 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 identifications.
The data push party and the data provider of the target data can perform crowd planning through security matching, for example, a first set which is composed of a large number of user identifications approved by both the data push party and the data provider is constructed for the target data, and the first set can be stored to the traffic aggregation platform in association with indication information of the target data. 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 party may both be received by the traffic aggregation platform, and then 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, the traffic aggregation platform or the data provider of the target data acquires decision information corresponding to each of the plurality of user identifiers in the query requests.
When the push decision party is the traffic aggregation platform, the traffic aggregation platform may determine the decision information corresponding to each of the plurality of user identifiers based on a pre-configured decision rule corresponding to the target data, and then perform the foregoing step 24 based on the decision information corresponding to each of the plurality of user identifiers; or, the traffic aggregation platform may also continue to forward the query request to the data provider of the target data, so that the data provider of the target data determines, based on a pre-configured decision rule corresponding to the target data, 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 performs step 24.
And the decision information corresponding to the user identification is used for indicating whether the pushing decision party allows the target data to be pushed to the user corresponding to the user identification. For example, when the value of the decision information corresponding to the user identifier is a true value true or a first predetermined value, the representation allows to push 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 a true value false or a second predetermined value, the representation does not allow to push the target data to the user corresponding to the user identifier.
When the push decision party is a data provider of the target data, the query request sent by the data push party may be forwarded to the data provider of the target data through the traffic aggregation platform, or may be directly sent to the data provider of the target data without passing through the traffic aggregation platform; the data provider of the target data may determine the decision information corresponding to each of the plurality of user identifiers based on the pre-configured decision rule corresponding to the target data, and then proceed to the foregoing step 24.
The response message may specifically include decision information corresponding to each of the plurality of user identities. For example, the response message may include decision information Value a corresponding to anonymous id a and decision information Value B corresponding to anonymous id B.
In the case where the query request includes, in addition to the plurality of user identifications, a first ciphertext obtained by encrypting the target user identification 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 the 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. For example, in the case that the query request includes a first ciphertext encrypted by encrypting the destination 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 (key2, E (key1, anonymous id a)); the push decision-making party may further encrypt the user identifier anonymous id a in the query request by using the second symmetric key2 to obtain a third symmetric key E (key2, anonymous id a), encrypt the user identifier anonymous id B in the query request by using the second symmetric key2 to obtain a third symmetric key E (key2, anonymous id B), and encrypt the decision information Value a corresponding to anonymous id a by using the third symmetric key E (key2, anonymous id a) corresponding to anonymous id a to obtain a decision information ciphertext E (key2, anonymous id a), Value a), encrypt the decision information Value B corresponding to anonymous id B by using the third symmetric key E (key2, anonymous id B) corresponding to anonymous id B to obtain a decision information Value B (key 2), and obtain a decision information Value B (Value 35b); further, a response message is generated that includes the decision information ciphertext E (key2, anonymous id a) corresponding to the second ciphertext E (key2, E (key1, anonymous id a)), and the decision information ciphertext E (key2, anonymous id B), and Value B) corresponding to the anonymous id B.
Next, in step 26, the push decision party sends a response message to the data push party.
Finally, in step 28, the data push obtains the objective decision information based on the response message.
When the response message includes the decision information corresponding to each of the plurality of user identifiers, the data push party may 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 the decision information ciphertext corresponding to each of the plurality of user identifiers, the data push party may decrypt the second ciphertext using the first symmetric key to obtain the target key, and further decrypt the decision information ciphertext corresponding to the target user identifier using the target key to obtain the target decision information indicating whether to allow the target data to be pushed to the target user. For example, as described above, in the case that the response message includes the decision information ciphertext E (key2, E (key1, anonymous id a)), the decision information ciphertext E (key2, anonymous id a), Value a) corresponding to anonymous id a, and the decision information ciphertext E (key2, anonymous id B), Value B) corresponding to anonymous id B, the data push may decrypt the second ciphertext E (key2, E (key1, anonymous id a)) by using the first symmetric key1 to obtain the target key, which is substantially the same as the third key E (key2, anonymous id a) obtained by encrypting the anonymous id a by using the second key 2; next, the decision information ciphertext E (key2, anonymous id a), Value a) corresponding to the anonymous id a may be decrypted by using the target key E (key2, 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 referring to the data pushing party described in the foregoing exemplary description can be understood that the data pushing party can only decrypt the decision information ciphertext corresponding to the target user identifier, and cannot decrypt the decision information corresponding to each of the user identifiers other than the target user identifier, so that it can be avoided that the data pushing party knows too much whether the pushing decision party allows pushing the target data to other users.
It can be understood that the data push party needs to decide whether to perform the pushing of the target data to the target user based on the target decision information obtained by the data push party, for example, when the target decision information obtained by the data push party is true value or the aforementioned first predetermined value, the data push party needs to continue to perform the pushing of the target data to the target user corresponding to the target user identifier.
Through the above embodiments, when the data push party needs to inquire whether to allow the target data to be pushed to a certain target user, it can be avoided that the push decision party including the traffic aggregation platform and the data provider accurately knows whether the data push party pushes the target data to the target user, and it can also be avoided that the data push party excessively knows whether the push decision party including the traffic aggregation platform and the data provider allows the target data to be pushed to other users other than the target user.
Based on the same concept as the foregoing method embodiment, this specification embodiment further provides a data pushing decision device, where the device is deployed on a data pushing party. As shown in fig. 3, the apparatus includes: a data sending unit 32, configured to send, when it is required to query whether to allow target data to be pushed to a target user, a query request including at least a plurality of user identifiers to a push decision maker, where the plurality of user identifiers include a target user identifier corresponding to the target user, and the user identifier is generated by encrypting user information serving as private data; a data receiving unit 34 configured to receive, from the push decision maker, a response message generated by the push decision maker based on decision information corresponding to each of the plurality of user identifications; 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 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 includes a second ciphertext obtained by encrypting the first ciphertext with a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting the decision information corresponding to the user identifiers with a third symmetric key corresponding to the user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with the second symmetric key. The data analysis 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 a possible embodiment, the user identifier is a hash value calculated by adding salt to the user information as the privacy data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
Based on the same concept as the foregoing method embodiment, this specification embodiment further provides a data push decision device, where the device is deployed on 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, an inquiry request sent when it is required to inquire whether to allow target data to be pushed to a target user, where the inquiry request includes a plurality of user identifiers, where the plurality of user identifiers include a target user identifier corresponding to the target user, and the user identifier is generated by encrypting user information that is 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 identifications; 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 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 includes a second ciphertext obtained by encrypting the first ciphertext with a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting the decision information corresponding to the user identifiers with a third symmetric key corresponding to the user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with the second symmetric key.
In a possible embodiment, the user identifier is a hash value calculated by adding salt to the user information as the privacy data.
In a possible implementation manner, the query request further includes indication information for indicating the target data.
In one possible embodiment, the push decision-making 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 located in a first set corresponding to the target data, 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 skilled in the art will recognize that in one or more of the examples described above, the functions described in this specification can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, a computer program corresponding to these functions may be stored in a computer-readable medium or transmitted as one or more instructions/codes on the computer-readable medium, so that when the computer program corresponding to these functions is executed by a computer, the method described in any one of the embodiments of the present specification is implemented by the computer.
Also provided in embodiments of the present specification is a computer-readable storage medium having a computer program stored thereon, which, when executed on a computing device, performs the method steps performed by a data push or a push decision maker in any of the embodiments of the present specification.
Embodiments of the present specification further provide a computing device, including a memory and a processor, where the memory stores executable codes, and the processor executes the executable codes to implement the method steps performed by a data pushing party or a pushing decision party in any one of the embodiments of the present specification.
The embodiments in the present description are described in a progressive manner, and the same and similar parts in the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may 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 may also be possible or may be advantageous.
The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.
Claims (20)
1. A data push decision method is applied to a data push party, and comprises the following steps:
when whether target data are allowed to be pushed to a target user is required to be inquired, sending an inquiry request at least comprising a plurality of user identifications to a pushing decision-making party, wherein the user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data;
and receiving a response message generated by the push decision maker based on the decision information corresponding to the user identifications respectively, and acquiring 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.
2. The method of claim 1, further comprising a first ciphertext obtained by encrypting the target ue 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 the decision information corresponding to the user identifications by using third symmetric keys corresponding to the user identifications, wherein the third key corresponding to the user identification is obtained by encrypting the user identification by using the second symmetric key;
the obtaining of the objective 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. The method of claim 1, wherein the user identifier is a hash value calculated by adding salt to the user information as the privacy data.
4. The method according to any one of claims 1-3, further comprising indication information in the query request for indicating the target data.
5. A data push decision-making method is applied to a push decision-making party, and comprises the following steps:
receiving a query request sent by a data pushing party when the data pushing party needs to query whether target data pushing to a target user is allowed or not, wherein the query request comprises a plurality of user identifications, the user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data;
and generating a response message based on the decision information corresponding to each of the plurality of user identifications, 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 the target data is allowed to be pushed to the target user.
6. The method of claim 5, further comprising a first ciphertext obtained by encrypting the target ue with a first symmetric key; the response message includes a second ciphertext obtained by encrypting the first ciphertext with a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting the decision information corresponding to the user identifiers with a third symmetric key corresponding to the user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with the second symmetric key.
7. The method of claim 5, wherein the user identifier is a hash value calculated by adding salt to the user information as the privacy data.
8. The method of claim 5, further comprising indication information for indicating the target data in the query request.
9. The method of any of claims 5-8, the push decision party being a traffic aggregation platform, the method further comprising: and determining whether the plurality of user identifications are located in a first set which is maintained in advance and corresponds to the target data, if so, sending the query request to a data provider of the target data, and enabling the data provider to return decision information corresponding to the plurality of user identifications.
10. A data pushing decision-making device deployed on a data pushing side, the device comprising:
the data sending unit is configured to send a query request at least comprising a plurality of user identifications to a push decision maker when whether target data are allowed to be pushed to a target user is required to be queried or not, wherein the plurality of user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data;
a data receiving unit configured to receive, from the push decision maker, a response message generated by the push decision maker based on decision information corresponding to each of the plurality of user identifications;
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.
11. The apparatus of claim 10, further comprising a first ciphertext obtained by encrypting the target ue 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 the decision information corresponding to the user identifications by using third symmetric keys corresponding to the user identifications, wherein the third key corresponding to the user identification is obtained by encrypting the user identification 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.
12. The apparatus according to claim 10, wherein the user identifier is a hash value calculated by adding salt to the user information as the privacy data.
13. The apparatus according to any of claims 10-12, further comprising indication information for indicating the target data in the query request.
14. A data push decision device deployed at a push decision party, the device comprising:
the data receiving unit is configured to receive an inquiry request sent by a data pushing party when the data pushing party needs to inquire whether target data are allowed to be pushed to a target user, wherein the inquiry request comprises a plurality of user identifications, the plurality of user identifications comprise target user identifications corresponding to the target user, and the user identifications are generated by encrypting user information serving as private data;
the data generation unit is configured to generate a response message based on the 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 the target data is allowed to be pushed to the target user.
15. The apparatus of claim 14, further comprising a first ciphertext obtained by encrypting the target ue with a first symmetric key; the response message includes a second ciphertext obtained by encrypting the first ciphertext with a second symmetric key, and a plurality of decision information ciphertexts obtained by encrypting the decision information corresponding to the user identifiers with a third symmetric key corresponding to the user identifiers, where the third key corresponding to the user identifier is obtained by encrypting the user identifier with the second symmetric key.
16. The apparatus of claim 14, wherein the user identifier is a hash value calculated by adding salt to user information as privacy data.
17. The apparatus of claim 14, further comprising indication information for indicating the target data in the query request.
18. The apparatus of any of claims 14-17, the push decision party 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 located in a first set corresponding to the target data, 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.
19. 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-9.
20. A computing device comprising a memory having stored therein a computer program and a processor that, when executing the computer program, implements the method of any of claims 1-9.
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 true CN114979253A (en) | 2022-08-30 |
| CN114979253B 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 (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150012965A1 (en) * | 2012-02-17 | 2015-01-08 | Nec Corporation | Information processing device for handling privacy information, information processing system for handling privacy information, and information processing method and program for handling privacy information |
| 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 |
-
2022
- 2022-05-06 CN CN202210487697.4A patent/CN114979253B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150012965A1 (en) * | 2012-02-17 | 2015-01-08 | Nec Corporation | Information processing device for handling privacy information, information processing system for handling privacy information, and information processing method and program for handling privacy information |
| 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 |
|---|---|
| CN114979253B (en) | 2024-03-12 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108123800B (en) | Key management method, key management device, computer equipment and storage medium | |
| CN109146481B (en) | Method, medium and device for automatically importing account private key of blockchain wallet and blockchain system | |
| US9391965B2 (en) | Data search device, data search method, data search program, data registration device, data registration method, data registration program, and information processing device | |
| CN107801165B (en) | Business short message pushing method and device, computer equipment and storage medium | |
| EP2798809B1 (en) | Dynamic pseudonymization method for user data profiling networks and user data profiling network implementing the method | |
| US20140281521A1 (en) | Method, System, Network Server And Storage Medium For Anonymous Dating | |
| US20150271153A1 (en) | Information management using proxy re-encryption | |
| JP6326173B1 (en) | Data transmission / reception system and data transmission / reception method | |
| JP2009529714A (en) | Method and system for decryptable and searchable encryption | |
| CN109376172B (en) | Data acquisition method and system based on block chain | |
| US20130067227A1 (en) | System and Method for Anonymous Digital Communication | |
| CN108632237A (en) | A kind of position service method based on the anonymity of more Anonymizers | |
| CN111177769A (en) | Private data protection list query method and related list query system | |
| US10063655B2 (en) | Information processing method, trusted server, and cloud server | |
| 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 | |
| CN114142995A (en) | Key secure distribution method and device for block chain relay communication network | |
| US7865715B2 (en) | Increasing peer privacy | |
| CN109842554B (en) | Routing method, device, equipment and storage medium of equipment service | |
| CN114979253B (en) | Data push decision method, device, medium and equipment | |
| CN108737077B (en) | Information processing method, device and system | |
| CN115408435A (en) | Data query method and device | |
| KR20210046578A (en) | Systems and methods to protect data | |
| CN113783847B (en) | Message interaction method, device, computer 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 |