CN112163009A - User side data acquisition method and device, electronic equipment and storage medium - Google Patents
User side data acquisition method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN112163009A CN112163009A CN202011064345.5A CN202011064345A CN112163009A CN 112163009 A CN112163009 A CN 112163009A CN 202011064345 A CN202011064345 A CN 202011064345A CN 112163009 A CN112163009 A CN 112163009A
- Authority
- CN
- China
- Prior art keywords
- user
- information
- data acquisition
- preset
- identification
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2457—Query processing with adaptation to user needs
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/31—User authentication
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
- G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2221/00—Indexing scheme relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/21—Indexing scheme relating to G06F21/00 and subgroups addressing additional information or applications relating to security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F2221/2141—Access rights, e.g. capability lists, access control lists, access tables, access matrices
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Databases & Information Systems (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computational Linguistics (AREA)
- Data Mining & Analysis (AREA)
- Storage Device Security (AREA)
Abstract
The invention relates to the technical field of big data, and provides a user side data acquisition method, a device, electronic equipment and a storage medium, wherein the method comprises the following steps: receiving a first user end identification, a second user end identification to be acquired and an object to be acquired; the method comprises the steps of obtaining first user information and second user information, generating an authorization certificate when the first user is determined to meet preset authority requirements and a data acquisition request is legal, sending the authorization certificate to the second user to generate an authorization code, and sending the authorization code to the first user so that the first user can acquire data. According to the method and the device, the first user side is determined to be the authority user and the data acquisition request is legal according to the first user side information, the second user side information and the object to be acquired, so that the phenomenon of excessive or illegal data acquisition is avoided, and the data safety is improved. The invention also relates to the field of blockchains, wherein the scheme is implemented based on blockchains, and the first user terminal and the second user terminal are both nodes in the blockchains.
Description
Technical Field
The invention relates to the technical field of big data, in particular to a user side data acquisition method and device, electronic equipment and a storage medium.
Background
At present, an acquisition scheme for user information of a third-party application program is simple, and in the process of acquiring the user information, only an acquisition request needs to be sent to the third-party application program, the information of a user is directly acquired after the user agrees, whether excessive or illegal acquisition is performed cannot be judged, so that some important and sensitive information is leaked, and the safety of the user information cannot be ensured.
Disclosure of Invention
In view of the above, it is necessary to provide a user-side data collection method, device, electronic device, and storage medium, in which the first user side is determined to be an authorized user and the data collection request is legal according to the first user-side information, the second user-side information, and the corresponding object to be collected, so that the phenomenon of collecting the second user-side data excessively or illegally is avoided, and the security of the second user-side data is improved.
A first aspect of the present invention provides a method for collecting data at a user end, where the method includes:
receiving a data acquisition request sent by a first user end, wherein the data acquisition request comprises a first user end identifier, a second user end identifier to be acquired and an object to be acquired;
acquiring first user end information according to the first user end identification, and acquiring second user end information according to the second user end identification;
verifying whether the first user side meets a preset authority requirement or not according to the first user side information, and judging whether the data acquisition request is legal or not according to the first user side information, the second user side information and the object to be acquired;
when the first user side is determined to meet the preset authority requirement and the data acquisition request is determined to be legal, generating an authorization certificate according to the second user side identification and the data acquisition request;
and sending the authorization certificate to the second user end, receiving an authorization code generated by the second user end according to the authorization certificate, and sending the authorization code to the first user end so that the first user end performs data acquisition on the object to be acquired.
A second aspect of the present invention provides a user-side data acquisition device, including:
the device comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a data acquisition request sent by a first user terminal, and the data acquisition request comprises a first user terminal identification, a second user terminal identification to be acquired and an object to be acquired;
the acquisition module is used for acquiring first user end information according to the first user end identification and acquiring second user end information according to the second user end identification;
the verification module is used for verifying whether the first user side meets the preset authority requirement or not according to the first user side information and judging whether the data acquisition request is legal or not according to the first user side information, the second user side information and the object to be acquired;
the generating module is used for generating an authorization certificate according to the second user terminal identification and the data acquisition request when the first user terminal is determined to meet the preset authority requirement and the data acquisition request is determined to be legal;
and the sending module is used for sending the authorization certificate to the second user terminal, receiving an authorization code generated by the second user terminal according to the authorization certificate, and sending the authorization code to the first user terminal so that the first user terminal can carry out data acquisition on the object to be acquired.
A third aspect of the present invention provides an electronic device, where the electronic device includes a processor and a memory, and the processor is configured to implement the user-side data collection method when executing a computer program stored in the memory.
A fourth aspect of the present invention provides a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the method for acquiring data at a user end.
In summary, according to the user-side data collection method, the device, the electronic device and the storage medium of the present invention, on one hand, whether the first user side meets the preset authority requirement is verified according to the first user-side information, and whether the data collection request is legal is judged according to the first user-side information, the second user-side information and the object to be collected, so that it is ensured that the first user side is an authority user, and the object to be collected, collected by the first user side, meets the preset first condition and the preset second condition at the same time, thereby avoiding the phenomenon of excessively or illegally collecting the second user-side data, and improving the security of the second user-side data; on the other hand, by counting the acquisition frequency of the object to be acquired of the second user end, which is sent by the first user end, and comparing the acquisition frequency with a preset acquisition frequency threshold, when the acquisition frequency is greater than or equal to the preset acquisition frequency threshold, it may be that the first user end performs illegal acquisition on the data of the second user end, so that the security of the data of the second user end is ensured.
In addition, when the user identification code of the first user end is not identified in the preset database, the credit degree of the first user end is determined to be not in accordance with the preset authority requirement, the first user end is refused to collect the data of the second user end, and the safety of the data of the second user end is improved.
Drawings
Fig. 1 is a first flowchart of a method for collecting data at a user end according to an embodiment of the present invention.
Fig. 2 is a schematic structural diagram for acquiring information of a first user equipment according to an embodiment of the present invention.
Fig. 3 is a schematic structural diagram of acquiring second user-side information according to an embodiment of the present invention.
Fig. 4 is a schematic structural diagram for verifying whether the first user side meets the preset permission requirement according to an embodiment of the present invention.
Fig. 5 is a schematic diagram of a first structure for determining whether the data acquisition request is legal according to an embodiment of the present invention.
Fig. 6 is a schematic structural diagram of a second embodiment for determining whether the data acquisition request is legal.
Fig. 7 is a schematic structural diagram of generating an authorization credential according to an embodiment of the present invention.
Fig. 8 is a second flowchart of a method for collecting data at a user end according to an embodiment of the present invention.
Fig. 9 is a structural diagram of a client data acquisition device according to a second embodiment of the present invention.
Fig. 10 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention.
Detailed Description
In order that the above objects, features and advantages of the present invention can be more clearly understood, a detailed description of the present invention will be given below with reference to the accompanying drawings and specific embodiments. It should be noted that the embodiments of the present invention and features of the embodiments may be combined with each other without conflict.
Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. The terminology used in the description of the invention herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.
Example one
Fig. 1 is a first flowchart of a method for collecting data at a user end according to an embodiment of the present invention.
In this embodiment, the user-side data collection method may be applied to an electronic device, and for an electronic device that needs to perform user-side data collection, the user-side data collection function provided by the method of the present invention may be directly integrated on the electronic device, or may be run in the electronic device in the form of a Software Development Kit (SKD).
As shown in fig. 1 to 8, the user-side data collection method, applied to a server, specifically includes the following steps, and according to different requirements, the order of the steps in the flowchart may be changed, and some steps may be omitted.
S11, receiving a data acquisition request sent by a first user terminal, wherein the data acquisition request comprises a first user terminal identification, a second user terminal identification to be acquired and an object to be acquired.
In this embodiment, the first user may be a service, the service sends a data acquisition request to the service, the service may be a security management platform, the first user identifier may be used to uniquely identify the first user, the second user identifier is used to uniquely identify the second user, and the object to be acquired may be a system authority name of the second user corresponding to data that needs to be acquired by the first user.
S12, obtaining first user end information according to the first user end identification, and obtaining second user end information according to the second user end identification.
In this embodiment, the first user information includes a first user name, a category, a system authority name, an application scenario identification code corresponding to each system authority name, and the like, and the first user information is obtained according to the first user identifier.
In this embodiment, the second user information includes a second user device number, a signed privacy protocol, a system authority name, an application scenario identification code corresponding to each system authority name, and the like, and the second user information is obtained according to the second user identifier.
Referring to fig. 2, optionally, the obtaining the first user information according to the first user identifier includes:
s121, matching the first user terminal identification with the user terminal identification in the first database;
s122, when the first target ue identity matched with the first ue identity is matched in the first database, acquiring first target information associated with the first target ue identity as first ue information.
Referring to fig. 3, optionally, the obtaining the second user information according to the second user identifier includes:
s123, matching the second user terminal identification with the user terminal identification in the second database;
s124, when a second target ue identity matching the second ue identity is matched in the second database, acquiring second target information associated with the second target ue identity as second ue information.
In this embodiment, since the information of the first user is pre-stored in a first database, and the information of the second user is pre-stored in a second database, the first user identifier is matched with the user identifier pre-stored in the first database, and when a first target user identifier matched with the first user identifier is matched in the first database, all information associated with the first target user identifier may be acquired as the first user information; and matching the second user end identification with the user end identification pre-stored in the second database, and when a second target user end identification matched with the second user end identification is matched in the second database, acquiring all information associated with the second target user end identification as the second user end information.
S13, verifying whether the first user terminal meets the preset authority requirement according to the first user terminal information, and judging whether the data acquisition request is legal according to the first user terminal information, the second user terminal information and the object to be acquired.
In this embodiment, an authority requirement may be preset, where the preset authority requirement is set according to a credit degree of the first user, specifically, the credit degree is that the server collects multiple historical scores of each first user from multiple preset data sources by using a web crawler technology, where the historical scores may be scores of the users, and calculates a final score according to a preset rule for the collected multiple historical scores every preset period, specifically, the preset rule may be an average value of the multiple historical scores or a sum of the multiple historical scores, determines a credit degree of each first user according to the final score, compares the credit degree score of each first user with a preset credit degree threshold, and selects the first user whose credit degree score is greater than or equal to the preset credit degree threshold, and determining that the screened first user side is the user side meeting the authority requirement, and storing the user side meeting the authority requirement into a preset database.
Referring to fig. 4, optionally, the verifying whether the first user equipment meets the preset permission requirement according to the first user equipment information includes:
s131, extracting a user identification code in the first user terminal information;
s132, identifying whether an identification code matched with the user identification code exists in the first database;
s133, when the target identification code matched with the user identification code exists in the first database, determining that the first user side meets the preset authority requirement; or
S134, when the target identification code matched with the user identification code does not exist in the first database, determining that the first user terminal does not meet the preset authority requirement.
In this embodiment, since a user identification code of a first user side meeting an authority requirement is stored in a preset database, the user identification code is used to uniquely identify the first user side, when a target identification code matched with the identification code of the first user side is identified in the first database, it is determined that the first user side meets the preset authority requirement, and when the target identification code matched with the user identification code of the first user side is not identified in the first database, it is determined that the credit degree of the first user side does not meet the preset authority requirement, the first user side is rejected to acquire data of a second user side, and the security of data of the second user side is improved.
Referring to fig. 5, optionally, the determining whether the data acquisition request is legal according to the first user-side information, the second user-side information, and the object to be acquired includes:
s135, identifying a first application scene identification code of the object to be acquired;
s136, extracting all second application scene identification codes meeting a preset first condition from the first user terminal information;
s137, matching the first application scene identification code with all the second application scene identification codes;
s138, when the first target application scenario identifier matched with the first application scenario identifier is matched in all the second application scenario identifiers, extracting all third application scenario identifiers meeting a preset second condition from the second user information;
s139, matching the first target application scene identification code with all the third application scene identification codes;
s1310, when the second target application scenario identifier matching the first target application scenario identifier is matched with the third application scenario identifiers, determining that the data collection request is legal.
In this embodiment, a first condition may be preset, where the preset first condition may be whether all the second application scenarios pass security audit permission.
In this embodiment, a second condition may be preset, where the preset second condition may be one or a combination of more than one of the following conditions:
whether the second user terminal allows the first application scene of the object to be acquired;
whether the second user signs a privacy agreement with the first application scenario.
For example, the first application scene identification code represents a usage scene of the object to be acquired, for example, if the object to be acquired is an address authority, the application scene identification code corresponding to the address authority is: and A, scene.
Extracting all the second application scenario identification codes which pass the security audit permission from the first user terminal information comprises the following steps: scene A: address authority, scenario B: reading position information, scene C: and calling, matching A scenes in all the second application scene identification codes, and judging whether the A scenes are allowed by the second user terminal or signed with a privacy agreement.
Extracting all third application scenario identification codes allowed by the second user terminal or signed with a privacy protocol from the second user terminal comprises the following steps: scene A: address authority, scenario B: reading position information, D scene: and calling, matching the scene A in all the third application scene identification codes, and determining that the data acquisition is legal.
In this embodiment, since the second application scenario identification code meets a preset first condition, it is determined that the second application scenario identification code passes a security audit permit, the third application scenario identification code meets a preset second condition, it is determined that the third application scenario identification code is allowed by the second user terminal or has signed a privacy protocol, after the first application scenario is identified, the first application scenario identification code is matched in all the second application scenario identification codes that pass the security audit permit, it is determined that the first user terminal has security audit on collecting the corresponding first application scenario to be collected, and has authority to collect, and the first application scenario identification code is matched in all the third application scenario identification codes that pass the second user terminal or have signed the privacy protocol, it is determined that the second user terminal allows the user terminal that has been security audit to collect, the first user end which is safely checked can be ensured to be capable of carrying out data acquisition, so that the safety of the second user end data and the accuracy of the first user end data acquisition are improved.
Referring to fig. 6, optionally, the determining whether the data acquisition request is legal according to the first user-side information, the second user-side information, and the object to be acquired further includes:
s1311, when the first target application scenario identifier matching the first application scenario identifier is not matched in all the second application scenario identifiers, determining that the first application scenario identifier accessed by the first user does not meet the preset first condition.
S1312, when the second target application scene id matched with the first target application scene id is not matched in all the third application scene ids, determining that the first target application scene id does not meet the preset second condition.
S1313, when the first application scenario identifier accessed by the first user does not meet the preset first condition, and/or when the first target application scenario identifier does not meet the preset second condition, determining that the data acquisition request is illegal.
In this embodiment, whether the first user side meets a preset permission requirement is verified according to the first user side information, and whether the data acquisition request is legal is judged according to the first user side information, the second user side information and a corresponding object to be acquired, so that the first user side is ensured to be a permission user, and the object to be acquired, acquired by the first user side, meets a preset first condition and a preset second condition, thereby avoiding a phenomenon that the second user side data is excessively or illegally acquired, and improving the security of the second user side data.
And S14, when the first user terminal is determined to meet the preset authority requirement and the data acquisition request is determined to be legal, generating an authorization certificate according to the second user terminal identification and the data acquisition request.
In this embodiment, after determining that the data acquisition request is legal, a corresponding authorization credential is generated according to the second user identifier and the data acquisition request.
As shown in fig. 7, preferably, the generating an authorization credential according to the second user identifier and the data collection request includes:
s141, acquiring an encryption algorithm and key information;
s142, calculating an encryption key for encryption according to the encryption algorithm and the key information, and encrypting the second user end identification through the encryption key to obtain the encrypted second user end identification;
s143, generating an authorization certificate corresponding to the data acquisition request according to the encrypted second user terminal identification and the key information.
In this embodiment, after it is determined that the first user meets the preset permission requirement and the data acquisition request is legal, an authorization credential corresponding to the data acquisition request is generated according to the encrypted second user identifier and the key information, so that the security of data in the data acquisition process is improved.
And S15, sending the authorization certificate to the second user terminal, receiving an authorization code generated by the second user terminal according to the authorization certificate, and sending the authorization code to the first user terminal so that the first user terminal can perform data acquisition on the object to be acquired.
In this embodiment, after generating the corresponding authorization credential, the authorization credential is sent to the second user, the second user generates an authorization code according to the content in the authorization credential, and returns the authorization code to the server, the server sends the authorization code to the first user, and when receiving the authorization code, the first user decodes the data acquisition request according to the authorization code, and performs data acquisition on the object to be acquired after decoding.
Referring to fig. 8, optionally, before sending the authorization credential to the second client, the method further comprises:
s151, counting the acquisition frequency of the object to be acquired, which is sent by the first user end in a preset period;
s152, comparing the acquisition frequency with a preset acquisition frequency threshold;
s153, when the acquisition frequency is smaller than the preset acquisition frequency threshold, sending the authorization certificate to the second user end; or
And S154, when the acquisition frequency is greater than or equal to the preset acquisition frequency threshold, sending a data acquisition rejection request to the first user terminal.
In this embodiment, by counting the acquisition frequency of the object to be acquired of the second user sent by the first user and comparing the acquisition frequency with a preset acquisition frequency threshold, when the acquisition frequency is greater than or equal to the preset acquisition frequency threshold, it may be that the first user performs illegal acquisition on the data of the second user, and sends a data acquisition rejection request to the first user, thereby ensuring the security of the data of the second user.
In summary, in the client data collection method according to this embodiment, a data collection request sent by a first client is received, where the data collection request includes a first client identifier, a second client identifier to be collected, and an object to be collected; acquiring first user end information according to the first user end identification, and acquiring second user end information according to the second user end identification; verifying whether the first user side meets a preset authority requirement or not according to the first user side information, and judging whether the data acquisition request is legal or not according to the first user side information, the second user side information and the object to be acquired; when the first user side is determined to meet the preset authority requirement and the data acquisition request is determined to be legal, generating an authorization certificate according to the second user side identification and the data acquisition request; and sending the authorization certificate to the second user end, receiving an authorization code generated by the second user end according to the authorization certificate, and sending the authorization code to the first user end so that the first user end performs data acquisition on the object to be acquired.
In this embodiment, on one hand, whether the first user side meets the preset authority requirement is verified according to the first user side information, and whether the data acquisition request is legal is judged according to the first user side information, the second user side information and the corresponding object to be acquired, so that the first user side is ensured to be an authority user, and the object to be acquired by the first user side simultaneously meets the preset first condition and the preset second condition, thereby avoiding the phenomenon of excessively or illegally acquiring the second user side data, and improving the security of the second user side data, on the other hand, by counting the acquisition frequency of the object to be acquired of the second user side sent by the first user side, and comparing the acquisition frequency with the preset acquisition frequency threshold, when the acquisition frequency is greater than or equal to the preset acquisition frequency threshold, the first user side may collect the data of the second user side in violation, so that the security of the data of the second user side is ensured.
In addition, when the user identification code of the first user end is not identified in the preset database, the credit degree of the first user end is determined to be not in accordance with the preset authority requirement, the first user end is refused to collect the data of the second user end, and the safety of the data of the second user end is improved.
The present invention also relates to the field of blockchains, where the user-side data acquisition method described in this embodiment is implemented based on blockchains, where a first user side and a second user side are both nodes in a blockchain, and a device for executing the user-side data acquisition method may also be a node on a blockchain, and before executing the user-side data acquisition, common identification verification needs to be performed on the first user side and the second user side through a blockchain.
Example two
Fig. 9 is a structural diagram of a client data acquisition device according to a second embodiment of the present invention.
In some embodiments, the client data collection device 20 may include a plurality of functional modules composed of program code segments. The program codes of the program segments in the client data collection apparatus 20 can be stored in the memory of the electronic device and executed by the at least one processor to perform the functions of the client data collection (described in detail in fig. 1 to 8).
In this embodiment, the user-side data collecting device 20 may be divided into a plurality of functional modules according to the functions executed by the user-side data collecting device. The functional module may include: the device comprises a receiving module 201, an obtaining module 202, a verifying module 203, a generating module 204, a sending module 205, a counting module 206 and a comparing module 207. The module referred to herein is a series of computer program segments capable of being executed by at least one processor and capable of performing a fixed function and is stored in memory. In the present embodiment, the functions of the modules will be described in detail in the following embodiments.
The receiving module 201 is configured to receive a data acquisition request sent by a first user, where the data acquisition request includes a first user identifier, a second user identifier to be acquired, and an object to be acquired.
In this embodiment, the first user may be a service, the service sends a data acquisition request to the service, the service may be a security management platform, the first user identifier may be used to uniquely identify the first user, the second user identifier is used to uniquely identify the second user, and the object to be acquired may be a system authority name of the second user corresponding to data that needs to be acquired by the first user.
An obtaining module 202, configured to obtain first user information according to the first user identifier, and obtain second user information according to the second user identifier.
In this embodiment, the first user information includes a first user name, a category, a system authority name, an application scenario identification code corresponding to each system authority name, and the like, and the first user information is obtained according to the first user identifier.
In this embodiment, the second user information includes a second user device number, a signed privacy protocol, a system authority name, an application scenario identification code corresponding to each system authority name, and the like, and the second user information is obtained according to the second user identifier.
Optionally, the obtaining first user equipment information according to the first user equipment identifier includes:
matching the first user terminal identification with the user terminal identification in the first database;
and when a first target user side identifier matched with the first user side identifier is matched in the first database, acquiring first target information associated with the first target user side identifier as first user side information.
Optionally, the obtaining second user equipment information according to the second user equipment identifier includes:
matching the second user terminal identification with the user terminal identification in a second database;
and when a second target user side identifier matched with the second user side identifier is matched in the second database, acquiring second target information associated with the second target user side identifier as second user side information.
In this embodiment, since the information of the first user is pre-stored in a first database, and the information of the second user is pre-stored in a second database, the first user identifier is matched with the user identifier pre-stored in the first database, and when a first target user identifier matched with the first user identifier is matched in the first database, all information associated with the first target user identifier may be acquired as the first user information; and matching the second user end identification with the user end identification pre-stored in the second database, and when a second target user end identification matched with the second user end identification is matched in the second database, acquiring all information associated with the second target user end identification as the second user end information.
The verification module 203 is configured to verify whether the first user side meets a preset permission requirement according to the first user side information, and determine whether the data acquisition request is legal according to the first user side information, the second user side information, and the object to be acquired.
In this embodiment, an authority requirement may be preset, where the preset authority requirement is set according to a credit degree of the first user, specifically, the credit degree is that the server collects multiple historical scores of each first user from multiple preset data sources by using a web crawler technology, where the historical scores may be scores of the users, and calculates a final score according to a preset rule for the collected multiple historical scores every preset period, specifically, the preset rule may be an average value of the multiple historical scores or a sum of the multiple historical scores, determines a credit degree of each first user according to the final score, compares the credit degree score of each first user with a preset credit degree threshold, and selects the first user whose credit degree score is greater than or equal to the preset credit degree threshold, and determining that the screened first user side is the user side meeting the authority requirement, and storing the user side meeting the authority requirement into a preset database.
Optionally, the verifying module 203 verifies whether the first user side meets a preset permission requirement according to the first user side information includes:
extracting a user identification code in the first user terminal information;
identifying whether an identification code matching the user identification code exists in the first database;
when a target identification code matched with the user identification code exists in the first database, determining that the first user side meets a preset authority requirement; or
And when the target identification code matched with the user identification code does not exist in the first database, determining that the first user side does not meet the preset authority requirement.
In this embodiment, since a user identification code of a first user side meeting an authority requirement is stored in a preset database, the user identification code is used to uniquely identify the first user side, when a target identification code matched with the identification code of the first user side is identified in the first database, it is determined that the first user side meets the preset authority requirement, and when the target identification code matched with the user identification code of the first user side is not identified in the first database, it is determined that the credit degree of the first user side does not meet the preset authority requirement, the first user side is rejected to acquire data of a second user side, and the security of data of the second user side is improved.
Optionally, the determining, by the verification module 203, whether the data acquisition request is legal according to the first user-side information, the second user-side information, and the object to be acquired includes:
identifying a first application scene identification code of the object to be acquired;
extracting all second application scene identification codes meeting a preset first condition from the first user terminal information;
matching the first application scene identification code with all the second application scene identification codes;
when a first target application scene identification code matched with the first application scene identification code is matched in all the second application scene identification codes, extracting all third application scene identification codes meeting a preset second condition from the second user terminal information;
matching the first target application scene identification code with all the third application scene identification codes;
and when the second target application scene identification code matched with the first target application scene identification code is matched in all the third application scene identification codes, determining that the data acquisition request is legal.
In this embodiment, a first condition may be preset, where the preset first condition may be whether all the second application scenarios pass security audit permission.
In this embodiment, a second condition may be preset, where the preset second condition may be one or a combination of more than one of the following conditions:
whether the second user terminal allows the first application scene of the object to be acquired;
whether the second user signs a privacy agreement with the first application scenario.
For example, the first application scene identification code represents a usage scene of the object to be acquired, for example, if the object to be acquired is an address authority, the application scene identification code corresponding to the address authority is: and A, scene.
Extracting all the second application scenario identification codes which pass the security audit permission from the first user terminal information comprises the following steps: scene A: address authority, scenario B: reading position information, scene C: and calling, matching A scenes in all the second application scene identification codes, and judging whether the A scenes are allowed by the second user terminal or signed with a privacy agreement.
Extracting all third application scenario identification codes allowed by the second user terminal or signed with a privacy protocol from the second user terminal comprises the following steps: scene A: address authority, scenario B: reading position information, D scene: and calling, matching the scene A in all the third application scene identification codes, and determining that the data acquisition is legal.
In this embodiment, since the second application scenario identification code meets a preset first condition, it is determined that the second application scenario identification code passes a security audit permit, the third application scenario identification code meets a preset second condition, it is determined that the third application scenario identification code is allowed by the second user terminal or has signed a privacy protocol, after the first application scenario is identified, the first application scenario identification code is matched in all the second application scenario identification codes that pass the security audit permit, it is determined that the first user terminal has security audit on collecting the corresponding first application scenario to be collected, and has authority to collect, and the first application scenario identification code is matched in all the third application scenario identification codes that pass the second user terminal or have signed the privacy protocol, it is determined that the second user terminal allows the user terminal that has been security audit to collect, the first user end which is safely checked can be ensured to be capable of carrying out data acquisition, so that the safety of the second user end data and the accuracy of the first user end data acquisition are improved.
Further, when a first target application scene identification code matched with the first application scene identification code is not matched in all the second application scene identification codes, it is determined that the first application scene identification code accessed by the first user terminal does not meet the preset first condition.
Further, when a second target application scene identification code matched with the first target application scene identification code is not matched in all the third application scene identification codes, it is determined that the first target application scene identification code does not meet the preset second condition.
Further, when the first application scene identification code accessed by the first user terminal does not conform to the preset first condition and/or when the first target application scene identification code does not conform to the preset second condition, the data acquisition request is determined to be illegal.
In this embodiment, whether the first user side meets a preset permission requirement is verified according to the first user side information, and whether the data acquisition request is legal is judged according to the first user side information, the second user side information and a corresponding object to be acquired, so that the first user side is ensured to be a permission user, and the object to be acquired, acquired by the first user side, meets a preset first condition and a preset second condition, thereby avoiding a phenomenon that the second user side data is excessively or illegally acquired, and improving the security of the second user side data.
A generating module 204, configured to generate an authorization credential according to the second user identifier and the data acquisition request when it is determined that the first user meets the preset permission requirement and it is determined that the data acquisition request is legal.
In this embodiment, after determining that the data acquisition request is legal, a corresponding authorization credential is generated according to the second user identifier and the data acquisition request.
Preferably, the generating module 204 generates an authorization credential according to the second user identifier and the data acquisition request includes:
acquiring an encryption algorithm and key information;
calculating an encryption key for encryption according to the encryption algorithm and the key information, and encrypting the second user end identification through the encryption key to obtain an encrypted second user end identification;
and generating an authorization certificate corresponding to the data acquisition request according to the encrypted second user terminal identification and the key information.
In this embodiment, after it is determined that the first user meets the preset permission requirement and the data acquisition request is legal, an authorization credential corresponding to the data acquisition request is generated according to the encrypted second user identifier and the key information, so that the security of data in the data acquisition process is improved.
A sending module 205, configured to send the authorization credential to the second user, receive an authorization code generated by the second user according to the authorization credential, and send the authorization code to the first user, so that the first user performs data acquisition on the object to be acquired.
In this embodiment, after generating the corresponding authorization credential, the authorization credential is sent to the second user, the second user generates an authorization code according to the content in the authorization credential, and returns the authorization code to the server, the server sends the authorization code to the first user, and when receiving the authorization code, the first user decodes the data acquisition request according to the authorization code, and performs data acquisition on the object to be acquired after decoding.
Optionally, before sending the authorization credential to the second user, the user-side data collecting apparatus further includes:
a counting module 206, configured to count an acquisition frequency of the object to be acquired, where the acquisition frequency is sent by the first user end within a preset period;
a comparison module 207, configured to compare the acquisition frequency with a preset acquisition frequency threshold;
the sending module 205 is further configured to send the authorization credential to the second user end when the acquisition frequency is smaller than the preset acquisition frequency threshold; or
The sending module 205 is further configured to send a data collection rejection request to the first user end when the collection frequency is greater than or equal to the preset collection frequency threshold.
In this embodiment, by counting the acquisition frequency of the object to be acquired of the second user sent by the first user and comparing the acquisition frequency with a preset acquisition frequency threshold, when the acquisition frequency is greater than or equal to the preset acquisition frequency threshold, it may be that the first user performs illegal acquisition on the data of the second user, and sends a data acquisition rejection request to the first user, thereby ensuring the security of the data of the second user.
In summary, the user-side data acquisition apparatus in this embodiment receives a data acquisition request sent by a first user, where the data acquisition request includes a first user identifier, a second user identifier to be acquired, and an object to be acquired; acquiring first user end information according to the first user end identification, and acquiring second user end information according to the second user end identification; verifying whether the first user side meets a preset authority requirement or not according to the first user side information, and judging whether the data acquisition request is legal or not according to the first user side information, the second user side information and the object to be acquired; when the first user side is determined to meet the preset authority requirement and the data acquisition request is determined to be legal, generating an authorization certificate according to the second user side identification and the data acquisition request; and sending the authorization certificate to the second user end, receiving an authorization code generated by the second user end according to the authorization certificate, and sending the authorization code to the first user end so that the first user end performs data acquisition on the object to be acquired.
In this embodiment, on one hand, whether the first user side meets the preset authority requirement is verified according to the first user side information, and whether the data acquisition request is legal is judged according to the first user side information, the second user side information and the corresponding object to be acquired, so that the first user side is ensured to be an authority user, and the object to be acquired by the first user side simultaneously meets the preset first condition and the preset second condition, thereby avoiding the phenomenon of excessively or illegally acquiring the second user side data, and improving the security of the second user side data, on the other hand, by counting the acquisition frequency of the object to be acquired of the second user side sent by the first user side, and comparing the acquisition frequency with the preset acquisition frequency threshold, when the acquisition frequency is greater than or equal to the preset acquisition frequency threshold, the first user side may collect the data of the second user side in violation, so that the security of the data of the second user side is ensured.
In addition, when the user identification code of the first user end is not identified in the preset database, the credit degree of the first user end is determined to be not in accordance with the preset authority requirement, the first user end is refused to collect the data of the second user end, and the safety of the data of the second user end is improved.
EXAMPLE III
Fig. 10 is a schematic structural diagram of an electronic device according to a third embodiment of the present invention. In the preferred embodiment of the present invention, the electronic device 3 comprises a memory 31, at least one processor 32, at least one communication bus 33 and a transceiver 34.
It will be appreciated by those skilled in the art that the configuration of the electronic device shown in fig. 10 does not constitute a limitation of the embodiment of the present invention, and may be a bus-type configuration or a star-type configuration, and the electronic device 3 may include more or less hardware or software than those shown, or different component arrangements.
In some embodiments, the electronic device 3 is an electronic device capable of automatically performing numerical calculation and/or information processing according to instructions set or stored in advance, and the hardware thereof includes but is not limited to a microprocessor, an application specific integrated circuit, a programmable gate array, a digital processor, an embedded device, and the like. The electronic device 3 may also include a client device, which includes, but is not limited to, any electronic product that can interact with a client through a keyboard, a mouse, a remote controller, a touch pad, or a voice control device, for example, a personal computer, a tablet computer, a smart phone, a digital camera, and the like.
It should be noted that the electronic device 3 is only an example, and other existing or future electronic products, such as those that can be adapted to the present invention, should also be included in the scope of the present invention, and are included herein by reference.
In some embodiments, the memory 31 is used for storing program codes and various data, such as the user-side data acquisition device 20 installed in the electronic device 3, and realizes high-speed and automatic access to programs or data during the operation of the electronic device 3. The Memory 31 includes a Read-Only Memory (ROM), a Programmable Read-Only Memory (PROM), an Erasable Programmable Read-Only Memory (EPROM), a One-time Programmable Read-Only Memory (OTPROM), an electronically Erasable rewritable Read-Only Memory (Electrically-Erasable Programmable Read-Only Memory (EEPROM)), an optical Read-Only disk (CD-ROM) or other optical disk Memory, a magnetic disk Memory, a tape Memory, or any other medium readable by a computer capable of carrying or storing data.
In some embodiments, the at least one processor 32 may be composed of an integrated circuit, for example, a single packaged integrated circuit, or may be composed of a plurality of integrated circuits packaged with the same or different functions, including one or more Central Processing Units (CPUs), microprocessors, digital Processing chips, graphics processors, and combinations of various control chips. The at least one processor 32 is a Control Unit (Control Unit) of the electronic device 3, connects various components of the electronic device 3 by using various interfaces and lines, and executes various functions and processes data of the electronic device 3 by running or executing programs or modules stored in the memory 31 and calling data stored in the memory 31.
In some embodiments, the at least one communication bus 33 is arranged to enable connection communication between the memory 31 and the at least one processor 32 or the like.
Although not shown, the electronic device 3 may further include a power supply (such as a battery) for supplying power to each component, and optionally, the power supply may be logically connected to the at least one processor 32 through a power management device, so as to implement functions of managing charging, discharging, and power consumption through the power management device. The power supply may also include any component of one or more dc or ac power sources, recharging devices, power failure detection circuitry, power converters or inverters, power status indicators, and the like. The electronic device 3 may further include various sensors, a bluetooth module, a Wi-Fi module, and the like, which are not described herein again.
It is to be understood that the described embodiments are for purposes of illustration only and that the scope of the appended claims is not limited to such structures.
The integrated unit implemented in the form of a software functional module may be stored in a computer-readable storage medium. The software functional module is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, an electronic device, or a network device) or a processor (processor) to execute parts of the methods according to the embodiments of the present invention.
In a further embodiment, in conjunction with fig. 9, the at least one processor 32 may execute an operating device of the electronic device 3 and various installed application programs (such as the user-side data acquisition device 20), program codes, and the like, for example, the above modules.
The memory 31 has program code stored therein, and the at least one processor 32 can call the program code stored in the memory 31 to perform related functions. For example, the modules shown in fig. 9 are program codes stored in the memory 31 and executed by the at least one processor 32, so as to implement the functions of the modules for the purpose of data acquisition at the user end.
In one embodiment of the present invention, the memory 31 stores a plurality of instructions executed by the at least one processor 32 to implement the functions of user-side data collection.
Specifically, the at least one processor 32 may refer to the description of the relevant steps in the embodiments corresponding to fig. 1 to fig. 8, which is not repeated herein.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the modules is only one logical functional division, and other divisions may be realized in practice.
Further, the computer-readable storage medium may be non-volatile or volatile.
Further, the computer-readable storage medium mainly includes a storage program area and a storage data area, wherein the storage program area may store an operating system, an application program required for at least one function, and the like; the storage data area may store data created according to the use of the blockchain node, and the like.
The block chain referred by the application is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. A block chain (Blockchain), which is essentially a decentralized database, is a series of data blocks associated by using a cryptographic method, and each data block contains information of a batch of network transactions, so as to verify the validity (anti-counterfeiting) of the information and generate a next block. The blockchain may include a blockchain underlying platform, a platform product service layer, an application service layer, and the like.
The modules described as separate parts may or may not be physically separate, and parts displayed as modules may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, functional modules in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional module.
It will be evident to those skilled in the art that the invention is not limited to the details of the foregoing illustrative embodiments, and that the present invention may be embodied in other specific forms without departing from the spirit or essential attributes thereof. The present embodiments are therefore to be considered in all respects as illustrative and not restrictive, the scope of the invention being indicated by the appended claims rather than by the foregoing description, and all changes which come within the meaning and range of equivalency of the claims are therefore intended to be embraced therein. Any reference sign in a claim should not be construed as limiting the claim concerned. Furthermore, it is obvious that the word "comprising" does not exclude other elements or that the singular does not exclude the plural. A plurality of units or means recited in the apparatus claims may also be implemented by one unit or means in software or hardware. The terms first, second, etc. are used to denote names, but not any particular order.
Finally, it should be noted that the above embodiments are only for illustrating the technical solutions of the present invention and not for limiting, and although the present invention is described in detail with reference to the preferred embodiments, it should be understood by those skilled in the art that modifications or equivalent substitutions may be made on the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention.
Claims (10)
1. A method for collecting data at a user side is characterized by comprising the following steps:
receiving a data acquisition request sent by a first user end, wherein the data acquisition request comprises a first user end identifier, a second user end identifier to be acquired and an object to be acquired;
acquiring first user end information according to the first user end identification, and acquiring second user end information according to the second user end identification;
verifying whether the first user side meets a preset authority requirement or not according to the first user side information, and judging whether the data acquisition request is legal or not according to the first user side information, the second user side information and the object to be acquired;
when the first user side is determined to meet the preset authority requirement and the data acquisition request is determined to be legal, generating an authorization certificate according to the second user side identification and the data acquisition request;
and sending the authorization certificate to the second user end, receiving an authorization code generated by the second user end according to the authorization certificate, and sending the authorization code to the first user end so that the first user end performs data acquisition on the object to be acquired.
2. The client data collecting method of claim 1, wherein the determining whether the data collecting request is legal according to the first client information, the second client information and the object to be collected comprises:
identifying a first application scene identification code of the object to be acquired;
extracting all second application scene identification codes meeting a preset first condition from the first user terminal information;
matching the first application scene identification code with all the second application scene identification codes;
when a first target application scene identification code matched with the first application scene identification code is matched in all the second application scene identification codes, extracting all third application scene identification codes meeting a preset second condition from the second user terminal information;
matching the first target application scene identification code with all the third application scene identification codes;
and when the second target application scene identification code matched with the first target application scene identification code is matched in all the third application scene identification codes, determining that the data acquisition request is legal.
3. The client-side data collection method of claim 1, wherein the generating an authorization credential according to the second client-side identifier and the data collection request comprises:
acquiring an encryption algorithm and key information;
calculating an encryption key for encryption according to the encryption algorithm and the key information, and encrypting the second user end identification through the encryption key to obtain an encrypted second user end identification;
and generating an authorization certificate corresponding to the data acquisition request according to the encrypted second user terminal identification and the key information.
4. The method for data collection at a user end according to claim 1, wherein before the sending the authorization credential to the second user end, the method further comprises:
counting the acquisition frequency of the object to be acquired, which is sent by the first user end in a preset period;
comparing the acquisition frequency with a preset acquisition frequency threshold;
when the acquisition frequency is smaller than the preset acquisition frequency threshold, the authorization certificate is sent to the second user end; or
And when the acquisition frequency is greater than or equal to the preset acquisition frequency threshold, sending a data acquisition rejection request to the first user terminal.
5. The user-side data collecting method according to claim 1, wherein the obtaining first user-side information according to the first user-side identifier includes:
matching the first user terminal identification with the user terminal identification in the first database;
and when a first target user side identifier matched with the first user side identifier is matched in the first database, acquiring first target information associated with the first target user side identifier as first user side information.
6. The method for acquiring client data according to claim 1, wherein the acquiring second client information according to the second client identifier comprises:
matching the second user terminal identification with the user terminal identification in a second database;
and when a second target user side identifier matched with the second user side identifier is matched in the second database, acquiring second target information associated with the second target user side identifier as second user side information.
7. The user-side data collection method of claim 1, wherein the verifying whether the first user side meets a preset permission requirement according to the first user-side information comprises:
extracting a user identification code in the first user terminal information;
identifying whether an identification code matching the user identification code exists in the first database;
when a target identification code matched with the user identification code exists in the first database, determining that the first user side meets a preset authority requirement; or
And when the target identification code matched with the user identification code does not exist in the first database, determining that the first user side does not meet the preset authority requirement.
8. A user side data acquisition device, the device comprising:
the device comprises a receiving module, a processing module and a processing module, wherein the receiving module is used for receiving a data acquisition request sent by a first user terminal, and the data acquisition request comprises a first user terminal identification, a second user terminal identification to be acquired and an object to be acquired;
the acquisition module is used for acquiring first user end information according to the first user end identification and acquiring second user end information according to the second user end identification;
the verification module is used for verifying whether the first user side meets the preset authority requirement or not according to the first user side information and judging whether the data acquisition request is legal or not according to the first user side information, the second user side information and the object to be acquired;
the generating module is used for generating an authorization certificate according to the second user terminal identification and the data acquisition request when the first user terminal is determined to meet the preset authority requirement and the data acquisition request is determined to be legal;
and the sending module is used for sending the authorization certificate to the second user terminal, receiving an authorization code generated by the second user terminal according to the authorization certificate, and sending the authorization code to the first user terminal so that the first user terminal can carry out data acquisition on the object to be acquired.
9. An electronic device, characterized in that the electronic device comprises a processor and a memory, and the processor is configured to implement the user-side data collection method according to any one of claims 1 to 7 when executing the computer program stored in the memory.
10. A computer-readable storage medium, on which a computer program is stored, wherein the computer program, when executed by a processor, implements the user-side data collection method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011064345.5A CN112163009A (en) | 2020-09-30 | 2020-09-30 | User side data acquisition method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011064345.5A CN112163009A (en) | 2020-09-30 | 2020-09-30 | User side data acquisition method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112163009A true CN112163009A (en) | 2021-01-01 |
Family
ID=73862391
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011064345.5A Pending CN112163009A (en) | 2020-09-30 | 2020-09-30 | User side data acquisition method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112163009A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113132362A (en) * | 2021-03-31 | 2021-07-16 | 青岛中瑞汽车服务有限公司 | Trusted authorization method, trusted authorization device, electronic equipment and storage medium |
| CN115952515A (en) * | 2022-12-05 | 2023-04-11 | 广州柏瀚信息科技有限公司 | Data security processing method and device based on big data |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110636043A (en) * | 2019-08-16 | 2019-12-31 | 中国人民银行数字货币研究所 | File authorization access method, device and system based on block chain |
| CN111064757A (en) * | 2020-03-18 | 2020-04-24 | 腾讯科技（深圳）有限公司 | Application access method and device, electronic equipment and storage medium |
| CN111131263A (en) * | 2019-12-26 | 2020-05-08 | 支付宝(杭州)信息技术有限公司 | Data viewing method and device |
| CN111680274A (en) * | 2020-03-03 | 2020-09-18 | 支付宝(杭州)信息技术有限公司 | Resource access method, device and equipment |
-
2020
- 2020-09-30 CN CN202011064345.5A patent/CN112163009A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110636043A (en) * | 2019-08-16 | 2019-12-31 | 中国人民银行数字货币研究所 | File authorization access method, device and system based on block chain |
| CN111131263A (en) * | 2019-12-26 | 2020-05-08 | 支付宝(杭州)信息技术有限公司 | Data viewing method and device |
| CN111680274A (en) * | 2020-03-03 | 2020-09-18 | 支付宝(杭州)信息技术有限公司 | Resource access method, device and equipment |
| CN111064757A (en) * | 2020-03-18 | 2020-04-24 | 腾讯科技（深圳）有限公司 | Application access method and device, electronic equipment and storage medium |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113132362A (en) * | 2021-03-31 | 2021-07-16 | 青岛中瑞汽车服务有限公司 | Trusted authorization method, trusted authorization device, electronic equipment and storage medium |
| CN113132362B (en) * | 2021-03-31 | 2022-03-22 | 青岛中瑞汽车服务有限公司 | Trusted authorization method, trusted authorization device, electronic equipment and storage medium |
| CN115952515A (en) * | 2022-12-05 | 2023-04-11 | 广州柏瀚信息科技有限公司 | Data security processing method and device based on big data |
| CN115952515B (en) * | 2022-12-05 | 2023-09-26 | 广州柏瀚信息科技有限公司 | Data security processing method and device based on big data |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112367246B (en) | Message pushing method and device, electronic equipment and storage medium | |
| US10594738B2 (en) | Rotation of authorization rules in memory of authorization system | |
| CN111383021B (en) | Node management method, device, equipment and medium based on block chain network | |
| CN112528251B (en) | User account authority management method, device, equipment and readable medium | |
| CN112163009A (en) | User side data acquisition method and device, electronic equipment and storage medium | |
| CN110661779B (en) | Block chain network-based electronic certificate management method, system, device and medium | |
| CN111798302A (en) | Quota updating method and device based on micro service, electronic equipment and storage medium | |
| CN114626033B (en) | Implementation method and terminal of data security room | |
| CN110969723B (en) | Data management method, detection device, server, and computer-readable storage medium | |
| CN111814181B (en) | System authority authorization method and device, electronic equipment and storage medium | |
| CN108540335B (en) | Management method and management device for equipment analysis report | |
| CN114416490A (en) | Monitoring alarm method and device based on block chain, electronic equipment and storage medium | |
| US20160299490A1 (en) | Method for the Enabling of Machine Functions on a Spinning-Mill Machine | |
| KR20210083457A (en) | Electronic vote record management system based on blockchain | |
| CN114331661A (en) | Data verification method and device, electronic equipment and storage medium | |
| CN112364307B (en) | Software authorization method and related equipment | |
| CN112132588B (en) | Data processing method and device based on block chain, routing equipment and storage medium | |
| CN110866069B (en) | Identity management metadata processing method and system based on block chain | |
| CN113360868A (en) | Application program login method and device, computer equipment and storage medium | |
| CN113488128A (en) | Block chain-based electronic medical record retrieval method and device and related equipment | |
| JP2004015495A5 (en) | ||
| CN111654591A (en) | Picture tamper-proofing method, computer equipment and storage medium | |
| CN112037062A (en) | Transaction consensus method, device, electronic equipment and readable storage medium | |
| CN113438598B (en) | Terminal positioning method and device, computer equipment and storage medium | |
| CN114978529A (en) | Block chain-based identity verification method and related equipment |
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 |