CN110598386A - Data processing method, device and equipment based on block chain and storage medium - Google Patents

Data processing method, device and equipment based on block chain and storage medium Download PDF

Info

Publication number
CN110598386A
CN110598386A CN201910922075.8A CN201910922075A CN110598386A CN 110598386 A CN110598386 A CN 110598386A CN 201910922075 A CN201910922075 A CN 201910922075A CN 110598386 A CN110598386 A CN 110598386A
Authority
CN
China
Prior art keywords
user
data
application program
blockchain
friend
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
Application number
CN201910922075.8A
Other languages
Chinese (zh)
Other versions
CN110598386B (en
Inventor
潘雄飞
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Tencent Technology Shenzhen Co Ltd
Original Assignee
Tencent Technology Shenzhen Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tencent Technology Shenzhen Co Ltd filed Critical Tencent Technology Shenzhen Co Ltd
Priority to CN201910922075.8A priority Critical patent/CN110598386B/en
Publication of CN110598386A publication Critical patent/CN110598386A/en
Application granted granted Critical
Publication of CN110598386B publication Critical patent/CN110598386B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/44—Program or device 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/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/45—Structures or tools for the administration of authentication
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

The application discloses a data processing method, a data processing device, data processing equipment and a data processing storage medium based on a block chain, and belongs to the technical field of block chains. The method comprises the following steps: receiving a friend relation data acquisition request of a first application program, wherein the friend relation data acquisition request comprises an application identifier of the first application program, a block chain account identifier of a first user and an application identifier of a second application program; verifying the validity of the blockchain account identifier of the first user; and when the validity verification of the blockchain account identification of the first user passes, acquiring target friend relationship data from the target blockchain based on the blockchain account identification of the first user. Through the process, the friend relationship data of the same user in different application programs can be linked based on the block chain account identification, sharing of the friend relationship data in different application programs is achieved, the data processing effect is good, and the use experience of the user on each application program is improved.

Description

Data processing method, device and equipment based on block chain and storage medium
Technical Field
The present disclosure relates to the field of block chain technologies, and in particular, to a data processing method, apparatus, device, and storage medium based on a block chain.
Background
With the continuous development and improvement of internet technology, terminals such as mobile phones and computers become indispensable parts in life, and various application programs can be installed in the terminals. The user can establish friend relationships with other users in any application program, so that the friends can better play games, communicate and the like. Data related to a friend relationship generated by a user in any application program is stored in a background server of the application program.
However, data related to a friend relationship, which is generated by the same user in different application programs, is usually stored in different background servers, and the data cannot be shared, so that the data processing effect is poor.
Disclosure of Invention
The embodiment of the application provides a data processing method, a device, equipment and a storage medium based on a block chain, which can be used for solving the problem of poor data processing effect in the related art. The technical scheme is as follows:
in one aspect, an embodiment of the present application provides a data processing method based on a blockchain, where the method is applied to any node device in a blockchain system, where multiple node devices in the blockchain system are configured with a target blockchain, and the target blockchain is used to store friend relationship data in multiple applications, and the method includes:
receiving a friend relation data acquisition request of a first application program, wherein the friend relation data acquisition request comprises an application identifier of the first application program, a block chain account identifier of a first user bound with a user identifier of the first user and an application identifier of a second application program;
verifying the validity of the blockchain account identifier of the first user;
when the validity of the blockchain account identifier of the first user passes the verification, target friend relationship data is obtained from the target blockchain based on the blockchain account identifier of the first user, and the target friend relationship data is friend relationship data in the second application program corresponding to the blockchain account identifier of the first user.
In another aspect, a data processing apparatus based on a block chain is provided, the apparatus including:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a friend relationship data acquisition request of a first application program, and the friend relationship data acquisition request comprises an application identifier of the first application program, a block chain account identifier of a first user bound with a user identifier of the first user and an application identifier of a second application program;
the verification module is used for verifying the validity of the block chain account identifier of the first user;
and the obtaining module is used for obtaining target friend relationship data from the target block chain based on the block chain account identifier of the first user when the validity verification of the block chain account identifier of the first user passes, wherein the target friend relationship data is friend relationship data in the second application program corresponding to the block chain account identifier of the first user.
In a possible implementation manner, the obtaining module is configured to obtain, from the target blockchain, candidate friend relationship data corresponding to the blockchain account identifier of the first user based on the blockchain account identifier of the first user; and acquiring friend relation data in the second application program from the candidate friend relation data based on the application identifier of the second application program.
In a possible implementation manner, the friend relationship data includes friend relationship establishing data and friend relationship releasing data, and the obtaining module is configured to obtain all friend relationship establishing data and all friend relationship releasing data corresponding to the blockchain account identifier of the first user from the target blockchain; and for any friend relation establishing data in all friend relation establishing data, when friend relation releasing data corresponding to the friend relation establishing data does not exist in all friend relation releasing data, taking the friend relation establishing data as candidate friend relation data corresponding to the block chain account identifier of the first user.
In a possible implementation manner, the verification module is further configured to perform permission verification on the first application program and the second application program based on the application identifier of the first application program and the application identifier of the second application program; and when the authority verification of the first application program and the second application program passes, performing validity verification on the blockchain account identification of the first user.
In a possible implementation manner, the receiving module is further configured to receive a registration request of any user, where the registration request of any user includes an identity of the any user;
the device further comprises:
the generating module is used for generating a block chain account identifier of any user corresponding to the identity identifier of any user based on the identity identifier of any user;
the feedback module is used for feeding back the blockchain account identification of any user to any user;
a storage module to store the blockchain account identification of the any user in the blockchain system.
In a possible implementation manner, the receiving module is further configured to receive friend relationship data in any application program, where the friend relationship data includes an application identifier of the any application program, a blockchain account identifier of a second user, and a blockchain account identifier of a third user;
the verification module is further used for verifying friend relationship data in any application program;
the storage module is further configured to store the friend relationship data in any application program on the target block chain when the verification of the friend relationship data in any application program passes.
In one possible implementation manner, the friend relationship data in any application program is generated by a server of any application program, and the server of any application program is used for storing the binding relationship between the user identifier and the blockchain account identifier of each user in any application program.
In another aspect, a computer device is provided, which includes a processor and a memory, where at least one program code is stored in the memory, and the at least one program code is loaded and executed by the processor to implement any one of the above mentioned data processing methods based on blockchains.
In another aspect, a computer-readable storage medium is provided, in which at least one program code is stored, and the at least one program code is loaded and executed by a processor to implement any of the above-mentioned data processing methods based on a blockchain.
The technical scheme provided by the embodiment of the application at least has the following beneficial effects:
the method comprises the steps that friend relationship data in a plurality of application programs are stored in a target block chain in advance, and when a friend relationship data acquisition request of a first application program is received, a target friend relationship in a second application program is acquired from the target block chain based on a block chain account identification of a user bound with the user identification of the user. Through the process, the friend relationship data of the same user in different application programs can be linked based on the block chain account identification, so that the friend relationship data of different application programs can be shared, the data processing effect is good, and the use experience of the user on each application program can be improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of a plurality of blocks in a block chain according to an embodiment of the present disclosure;
fig. 2 is a schematic diagram of an implementation environment of a data processing method based on a blockchain according to an embodiment of the present application;
fig. 3 is a flowchart of a data processing method based on a block chain according to an embodiment of the present application;
fig. 4 is a schematic diagram of an interface for displaying target friend relationship data by a terminal of a first user according to an embodiment of the present application;
FIG. 5 is a diagram illustrating a data processing process according to an embodiment of the present disclosure;
fig. 6 is a schematic diagram of a data processing apparatus based on a block chain according to an embodiment of the present application;
fig. 7 is a schematic diagram of a data processing apparatus based on a block chain according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a server provided in an embodiment of the present application;
fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application.
Detailed Description
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
First, several terms referred to in the present application will be explained.
The block chain system: refers to a system that employs block chain Technology (Blockchain Technology) to store data. The block chain technology is also called as distributed book technology, is an internet database technology, and is characterized in that centralization and public transparency are achieved, and everyone can participate in database recording. Blockchain technology may be a distributed infrastructure and computing approach that utilizes blockchain data structures to authenticate and store data, utilizes distributed node consensus algorithms to generate and update data, cryptographically secures data transmission and access, and utilizes intelligent contracts composed of automated script code to program and manipulate data. The data stored in the blockchain system has high stability and reliability, and the blockchain system is a non-tampered and trusted database. Therefore, compared with the traditional method that the friend relationship data in the application program is stored by directly utilizing the background server of the application program, the friend relationship data is stored by adopting the block chain system, and the data security and reliability are improved.
The blockchain system can comprise a plurality of node devices, and data can be shared between the node devices. Each node device can receive input information during normal operation, and maintain shared data in the blockchain system based on the received input information. In order to ensure information intercommunication in the blockchain system, information connection can exist between each node device in the blockchain system, and information transmission can be carried out between the node devices through the information connection. For example, when an arbitrary node device in the blockchain system receives input information, the arbitrary node device may send a block generated based on the input information to other node devices in the blockchain system, and perform a consensus process on the block by the other node devices, and when the consensus of the block by the other node devices passes, the arbitrary node device in the blockchain system adds the block to the blockchain, so that data stored on each node device in the blockchain system are consistent.
TABLE 1
Node device name Node device identification
Node device 1 117.114.151.174
Node device 2 117.116.189.145
… …
Node device N 119.123.789.258
Each node device in the blockchain system has a node device identifier corresponding thereto, and each node device in the blockchain system can store node device identifiers of other node devices in the blockchain system, so that the generated block is broadcast to other node devices in the blockchain system according to the node device identifiers of the other node devices in the subsequent process. Each node device may maintain a node device identifier list as shown in table 1, and store the node device name and the node device identifier in the node device identifier list correspondingly. The node device identifier may be an IP (internet protocol) address or any other information that can be used to identify the node device, and table 1 only illustrates the IP address as an example.
Each node device in the blockchain system is configured with at least one identical blockchain. Each block chain is composed of a plurality of blocks, fig. 1 is a schematic diagram of a plurality of blocks in a block chain provided in the embodiment of the present application, a starting block includes a block header and a block main body, an input information characteristic value, a version number, a timestamp and a difficulty value are stored in the block header, and input information is stored in the block main body; the next block of the starting block takes the starting block as a parent block, the next block also comprises a block head and a block main body, the block head stores the input information characteristic value of the current block, the block head characteristic value of the parent block, the version number, the timestamp and the difficulty value, and the like, so that the block data stored in each block in the block chain is associated with the block data stored in the parent block, and the safety of the input information in the block is ensured.
Block height: the number of blocks linked to the main chain, i.e. the number of blocks connected to the block chain.
A consensus algorithm: the method refers to a mathematical algorithm for establishing trust and obtaining rights and interests among different node devices in a block chain system. In the block chain system, the verification and confirmation of the transaction can be completed in a short time through the voting of the special node devices, and if a plurality of node devices with irrelevant benefits can achieve the consensus, all the node devices in the system can also achieve the consensus.
It is noted that the terms first, second and the like in the description and in the claims of the present application are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used is interchangeable under appropriate circumstances such that the embodiments of the application described herein are capable of operation in sequences other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
Fig. 2 is a schematic diagram of an implementation environment of a data processing method based on a blockchain according to an embodiment of the present application. The implementation environment may include: a terminal 21, a server 22 and a blockchain system 23. The blockchain system 23 includes a plurality of node devices 230.
Among them, the terminal 21 may be installed with various applications, for example, a game application or a communication application, etc. The user may initiate a friend relationship processing instruction in an application program of the terminal 21, and then the terminal 21 sends the friend relationship processing instruction to the server 22, and the server 22 performs validity verification on the friend relationship processing instruction. The user may also initiate a friend relationship data obtaining request in the application program of the terminal 21, and then the terminal 21 sends the friend relationship data obtaining request to the blockchain system 23.
Server 22 may be a backend server for an application that provides backend services for the application. The server 22 may provide an installation package for the application program applicable to various operating systems for downloading and installation on the terminal 21. The server 22 stores user data relating to each registered user, such as the user identification of the user and the binding relationship between the user identification and the blockchain account identification. The server 22 may receive the friend relationship processing instruction sent by the terminal 21, generate friend relationship data when the validity of the friend relationship processing instruction is verified, and then send the friend relationship data to the blockchain system 23.
In some alternative embodiments, the server 22 itself may also operate and store data as one or more node devices in the blockchain system 23.
A plurality of node devices 230 in the blockchain system 23 may be configured with a target blockchain. The target block chain is used for storing friend relation data in a plurality of application programs. The target block chain in the block chain system 23 is composed of a plurality of blocks, and the adjacent blocks have an association relationship, so that data in any block can be detected by the next block when being tampered, thereby preventing the data in the block chain from being tampered, and ensuring the security and reliability of the data in the block chain. Node device 230 in blockchain system 23 may store buddy relationship data on the target blockchain; the node device 230 may further obtain the friend relationship data from the target block chain, and send the friend relationship data to the terminal 21.
In one possible implementation, the terminal 21 may be a smart device such as a cell phone, a tablet, a personal computer, or the like. The server 22 may be a server, a server cluster composed of a plurality of servers, or a cloud computing service center. The node device 230 refers to a computer device, and the computer device may be a terminal or a server, which is not limited in this embodiment of the present application.
The terminal 21 and the server 22 establish a communication connection through a wired and/or wireless network, the terminal 21 and the blockchain system 23 establish a communication connection through a wired and/or wireless network, and the server 22 and the blockchain system 23 establish a communication connection through a wired and/or wireless network. The wired network may be a metropolitan area network, a local area network, an optical fiber network, and the like, and the Wireless network may be a mobile communication network or a Wireless Fidelity (WiFi).
It should be understood by those skilled in the art that the terminal 21, the server 22 and the blockchain system 23 are only examples, and other existing or future terminals, servers or blockchain systems may be suitable for the present application and are included in the scope of the present application and are herein incorporated by reference.
Based on the implementation environment shown in fig. 2, an embodiment of the present application provides a data processing method based on a blockchain, which is applied to any node device in a blockchain system as an example. Fig. 3 is a flowchart of a data processing method based on a block chain according to an embodiment of the present disclosure, and as shown in fig. 3, the method according to the embodiment of the present disclosure may include the following steps:
301. the first node device generates a blockchain account identification of any user based on a registration request of any user, and stores the blockchain account identification of any user in a blockchain system.
Wherein, any user refers to any user initiating a registration request; the registration request is used for indicating that any user needs to register in the blockchain system, and the registration request of any user comprises the identity of any user. The user id is used to identify the unique social identity of the user, for example, the user id may be a name of the user, an id document number of the user, a communication number of the user, or the like. The blockchain account identifier is used for identifying the unique identity of the user in the blockchain system, and the blockchain account identifier can be generated based on the identity of the user. It should be noted that, for the same user, the user may have different user ids in different applications, but the user only has one id and the id only has one blockchain account id. The user identifier is used to identify registration information of the user in the application program, such as a registration account, a login password, and the like.
The specific implementation process of step 301 may include steps 301A to 301C:
step 301A: the first node device receives a registration request of any user.
The registration request of any user can be sent to the blockchain system by the terminal of any user. The terminal of any user may be installed with an application or web page capable of initiating a registration request, in which a registration entry for registering in the blockchain system is laid out. Before sending a registration request of any user to the blockchain system, a terminal of any user needs to acquire the registration request of any user.
In a possible implementation manner, the process of acquiring, by a terminal of any user, a registration request of any user may be: when the terminal of any user detects the triggering operation of any user on the registration entrance, the identity of any user is obtained, and the registration request of any user is generated based on the identity of any user. The method for acquiring the identity of any user by the terminal of any user may be acquiring an identity manually filled by any user, or acquiring an identity imported by any user, and the like, which is not limited in the embodiment of the present application.
In one possible implementation manner, the process of the first node device receiving the registration request of any user may be: after a terminal of any user sends a user identifier of any user to a blockchain system, a management node device in the blockchain system receives a registration request of any user; the management node equipment inquires a block chain for storing a block chain account identifier in a block chain system based on a registration request of any user; the management node equipment sends the registration request of any user to the first node equipment configured with the block chain; the first node device receives a registration request of any user. In this embodiment of the present application, a node device that receives a registration request of any user sent by a management node device is taken as a first node device.
In a possible implementation manner, in order to ensure data security in a process in which the management node device sends a registration request of any user to the first node device, before the management node device sends the registration request of any user to any first node device, the management node device may encrypt the registration request of any user according to a public key of any first node device, and then send obtained encrypted data to any first node device. After receiving the encrypted data, the any first node device may decrypt the encrypted data according to the private key to obtain a registration request of the any user. The method can effectively avoid the registration request of any user from being tampered, and improves the transmission security of the registration request of any user.
It should be noted that the management node device may send a registration request of any user to one or more first node devices, and each first node device is configured with a blockchain for storing a blockchain account identifier, so that whichever first node device receives the registration request of any user can execute the following steps 301B and 301C based on the registration request of any user.
Step 301B: the first node device generates a blockchain account identifier of any user corresponding to the identity identifier of any user based on the identity identifier of any user, and feeds the blockchain account identifier of any user back to any user.
In one possible implementation manner, the process of generating, by the first node device, the blockchain account identifier of any user corresponding to the identity identifier of any user based on the identity identifier of any user may be implemented based on an intelligent contract in the blockchain system. In a possible implementation manner, the identity of any user may be used as a trigger manner of an intelligent contract, and when the identity of any user is obtained, the intelligent contract may be automatically triggered, so that the first node device executes the process of generating the block chain account identity of any user corresponding to the identity of any user based on the identity of any user; and when the identity of any user is not acquired, the intelligent contract is not triggered. The content of the intelligent contract is not limited in the embodiment of the present application.
In a possible implementation manner, the first node device may verify the identity of any user before generating the blockchain account identity of any user corresponding to the identity of any user, and when the verification passes, generate the blockchain account identity of any user corresponding to the identity of any user. The embodiment of the present application does not limit the way in which the first node device verifies the identity of any user, for example, when the identity of any user includes the name of any user and the identity document number of any user, the first node device may verify whether the name of any user matches the identity document number, and the like.
After the first node device generates the blockchain account identifier of any user corresponding to the identity identifier of any user, the blockchain account identifier of any user can be fed back to any user, so that any user can know the blockchain account identifier of himself in the blockchain system. After the user knows the blockchain account identifier of the user in the blockchain system, the user identifier and the blockchain account identifier can be bound in any application program, and the server of the application program stores the binding relationship between the user identifier and the blockchain account identifier.
Step 301C: the first node device stores the blockchain account identification of any user in the blockchain system.
After the first node device generates the blockchain account identifier of any user, the blockchain account identifier of any user can be stored in the blockchain for storing the blockchain account identifier in the blockchain system. The storing process may include the following two steps:
step 1: the first node device generates a target tile based on the blockchain account identification of any user.
In the blockchain technology, data may be stored in the blocks in the form of electronic records, and in this embodiment of the application, when a packaging condition is met, the first node device may package the blockchain account identifier of any user to generate a target block. The meeting of the packing condition may be to meet a time interval required for packing data or to meet a data quantity required for packing data, which is not limited in the embodiment of the present application.
In one possible implementation, the process of the first node device generating the target block may be as follows:
the first node device takes the block chain account identification of any user as input information, stores the input information into a memory pool, and updates a hash tree used for recording the input information; and then, updating the updating time stamp to the time when new input information is received, trying different random numbers, and calculating the characteristic value for multiple times, so that the calculated characteristic value can satisfy the following formula:
SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))<TARGET
wherein, SHA256 is a characteristic value algorithm used for calculating a characteristic value; version is version information of the relevant block protocol in the block chain; the prev _ hash is a block head characteristic value of a parent block of the target block, and the parent block of the target block is a block with the largest block height on the current block chain; merkle _ root is a characteristic value of the input information; ntime is the update time of the update timestamp; nbits is the current difficulty, is a fixed value within a period of time, and is determined again after exceeding a fixed time period; x is a random number; TARGET is a feature threshold, which can be determined from nbits.
Thus, when the random number meeting the formula is obtained through calculation, the information can be correspondingly stored, and a block header and a block main body are generated to obtain the target block.
It should be noted that the above description of the target block generation process is only an exemplary description of one block generation method, and the embodiment of the present application does not limit which block generation method is specifically adopted.
Step 2: the first node device adds the target block to a blockchain for storing a blockchain account identification based on a consensus mechanism.
The blockchain system may perform consensus on the target block to determine whether the data in the target block is accurate, i.e., to verify the data in the target block. In a possible implementation manner, after the first node device generates the target block, the first node device may send the target block to other node devices respectively according to node device identifiers of other node devices in the blockchain system, the other node devices may verify the target block, and broadcast verification results in the blockchain system respectively, and when the number of node devices that pass the verification result in the blockchain system is greater than a reference ratio or greater than a reference number, the first node device may determine that the target block commonly identifies, and then add the target block to a blockchain for storing a blockchain account identifier in the blockchain system. The reference proportion refers to a proportion that the number of the node devices passing the verification result accounts for the number of all the node devices in the block chain system, and the reference proportion may be set empirically or may be freely adjusted according to an application scenario, which is not limited in the embodiment of the present application. For example, the reference ratio may be set to 1/3 or the like. Likewise, the reference number may be set empirically, or may be freely adjusted according to the total number of all node devices in the blockchain system, for example, the reference number may be set to 100, and so on. The consensus process described above may be implemented based on a consensus mechanism, which may be, for example, a workload proving mechanism, a rights proving mechanism, or the like. It should be noted that the above-mentioned consensus process is only an exemplary description, and the embodiments of the present application do not limit this.
Through the above steps 1 and 2, the first node device may store the blockchain account identifier of any user in the blockchain for storing the blockchain account identifier, and synchronize the blockchain account identifier of any user to each node device configured with the blockchain for storing the blockchain account identifier.
When the first node device receives a registration request of a user each time, the first node device may generate a blockchain account id of the user through the above steps 301A to 301C, and then the blockchain account id of the user is stored in a blockchain for storing the blockchain account id. The block chain account id stored in the block chain is not allowed to be tampered, and only a new block in which a new block chain account id is stored is allowed to be added to the block chain. The block characteristic value of the new block is related to the block characteristic value of the previous block, so that the purpose of connecting the blocks which are adjacent in the block chain in series is realized, and the tampering of any data in the block chain can be detected by tracing the block characteristic value stored in the next block. The blockchain account identification of each user is stored in the blockchain system, so that the validity verification of the received blockchain account identification of the user can be conveniently carried out.
302. And the second node equipment receives friend relation data in any application program.
The friend relationship data comprises an application identifier of any application program and blockchain account identifiers of two users related in the friend relationship data. The two users referred to herein may be referred to as a second user and a third user, respectively, for correspondence with the claims. That is to say. The friend relationship data includes an application identification of any one of the application programs, a blockchain account identification of the second user, and a blockchain account identification of the third user. The second user may refer to a user who actively applies for establishing a friend relationship with a third user or deleting the friend relationship. The friend relation data refers to data related to friend relations, and includes but is not limited to friend relation establishing data and friend relation releasing data. The friend relationship establishing data refers to data for establishing a friend relationship between two users in a non-friend relationship, and may include data such as a time stamp for establishing the friend relationship, a place for establishing the friend relationship, and the like; the friend relationship release data is data for releasing a friend relationship between two users having a friend relationship, and may include data such as a time stamp for releasing a friend relationship, a place for releasing a friend relationship, and the like.
In one possible implementation, the buddy relationship data in any application is generated by a server of the any application. The process of receiving the buddy relationship data in any application by the second node device may include steps 302A to 302D:
step 302A: and the server of any application program receives a friend relationship processing instruction of the second user in the any application program.
The friend relation processing instruction may include a user identifier of the second user, a user identifier of the third user, an application identifier of the any application program, and a friend relation processing type. The friend relationship processing type comprises friend relationship establishment and friend relationship release. The second user refers to a user who initiates the friend relationship processing instruction, and the third user refers to a user who establishes or releases the friend relationship with the second user.
In one possible implementation manner, the process of the server receiving the friend relationship processing instruction of the second user in any application program may be: when the terminal of the second user detects that the second user initiates a friend relationship processing instruction in any application program, the terminal of the second user sends the friend relationship processing instruction to the server, and therefore the server receives the friend relationship processing instruction of the second user in any application program. The terminal of the second user refers to a terminal of the second user logging in any application program. In one possible implementation manner, the case where the terminal of the second user detects that the second user initiates the friend relationship processing instruction in any application program includes, but is not limited to, the following two cases:
the first condition is as follows: when the terminal of the second user detects the triggering operation of the second user on the friend relationship processing entry in the virtual role introduction interface of the third user, the terminal of the second user can be considered to detect that the second user initiates a friend relationship processing instruction in any application program.
The virtual character introduction interface of the third user refers to an interface for introducing relevant information of the virtual character of the third user. The friend relationship processing entry may refer to a friend relationship establishing entry or a friend relationship releasing entry. Specifically, when the third user and the second user are in a non-friend relationship, a friend relationship establishing entry may be displayed in the interface; when the third user and the second user are in a friend relationship, a friend relationship releasing entry may be displayed in the interface. When the second user triggers the friend relationship processing entry, it may be considered that the terminal of the second user detects that the second user initiates a friend relationship processing instruction in any application program. It should be noted that, in the embodiment of the present application, the form of the friend relationship processing entry is not limited, for example, the friend relationship processing entry may be in the form of a button or an icon.
Case two: when the terminal of the second user detects that the second user operates the target of the virtual role of the third user, the terminal of the second user can be considered to detect that the second user initiates a friend relationship processing instruction in any application program.
The target operation may refer to any operation corresponding to the friend relationship processing instruction, which is preset by the second user and stored in the server, or may refer to a default operation corresponding to the friend relationship processing instruction, which is stored in the server. For example, the target operation may be that the second user clicks the virtual character of the third user, or that the second user performs a sliding operation in the virtual character of the third user from bottom to top, or the like.
When the terminal of the second user detects the operation of the second user corresponding to the friend relationship processing instruction, the second user can be considered to trigger the friend relationship processing instruction, and at this time, the terminal of the second user detects that the second user initiates the friend relationship processing instruction in any application program. It should be noted that the target operations corresponding to the friend relationship establishing instruction and the friend relationship releasing instruction may be the same or different, and this is not limited in the embodiment of the present application.
Step 302B: and the server of any application program carries out validity verification on the friend relation processing instruction, and generates friend relation data in any application program based on the friend relation processing instruction when the validity verification of the friend relation processing instruction passes.
After receiving the friend relation processing instruction, the server firstly verifies the validity of the friend relation processing instruction so as to verify whether the friend relation processing instruction is valid. When the validity verification passes, the server generates friend relation data in any application program based on the friend relation processing instruction; when the validity verification fails, the server may send error information to the terminal of the second user, where the error information is used to prompt that the second user cannot generate new friend relationship data.
In one possible implementation manner, the process of verifying the validity of the friend relationship processing instruction by the server may be: the server acquires data generated by the second user in the application program according to the user identification of the second user in the friend relationship processing instruction; and analyzing whether the second user has the authority to initiate a friend relationship processing instruction or not according to the data generated by the second user in the application program. When the data generated by the second user in the application program indicates that the second user has no permission to initiate the friend relationship processing instruction, determining that the validity verification of the friend relationship processing instruction fails; when the data generated by the second user in the application program indicates that the second user has the right to initiate the friend relationship processing instruction, it may be determined that the validity of the friend relationship processing instruction is verified to be passed.
The method for analyzing whether the second user has the right to initiate the friend relationship processing instruction according to the data generated by the second user in the application program by the server is not limited in the embodiment of the application. For example, the server may analyze whether the second user has the right to initiate the friend relationship processing instruction according to a credit score in data generated by the second user in the application program, and when the credit score is not higher than a credit threshold, it indicates that the second user has no right to initiate the friend relationship processing instruction; and when the credit score is higher than the credit threshold value, the second user is allowed to initiate a friend relation processing instruction.
When the validity of the friend relationship processing instruction is verified, the server may generate friend relationship data in any application program based on the friend relationship processing instruction, where the friend relationship data includes an application identifier of the any application program, a blockchain account identifier of the second user, and a blockchain account identifier of the third user. Specifically, based on the friend relationship processing instruction, the process of generating the friend relationship data in any application program by the server may be: the server acquires a block chain account identifier of the second user corresponding to the user identifier of the second user and a block chain account identifier of the third user corresponding to the user identifier of the third user based on the user identifier of the second user and the user identifier of the third user in the friend relationship processing instruction; and generating friend relation data in any application program based on the block chain account identification of the second user, the block chain account identification of the third user and the friend relation processing type. It should be noted that the server stores the binding relationship between the user identifier of each user and the blockchain account identifier in any application program, and the storage form of the binding relationship between the user identifier of each user and the blockchain account identifier in the embodiment of the present application is not limited, for example, the storage form may be a list form.
In one possible implementation manner, the process of generating, by the server, friend relationship data in any application program based on the blockchain account identifier of the second user, the blockchain account identifier of the third user, and the friend relationship processing type includes: when the friend relationship processing type is friend relationship establishment, the server generates friend relationship establishment data in any application program based on the block chain account identification of the second user and the block chain account identification of the third user; and when the friend relationship processing type is friend relationship release, generating friend relationship release data in any application program based on the block chain account identification of the second user and the block chain account identification of the third user.
In a possible implementation manner, when the friend relationship processing type is to establish a friend relationship, the server may further send a friend relationship processing instruction to a terminal of a third user before generating friend relationship establishment data of any application program, so as to obtain response information of the third user fed back by the terminal of the third user; when the response information indicates that the third user does not agree to add the second user as a friend, the server may send a response that the adding of the friend fails to the terminal of the second user. When the response information indicates that the third user agrees to add the second user as a friend, the server may generate friend relationship establishing data in any application program, and at this time, the friend relationship establishing data may further include association data of the second user and the third user. For example, the intimacy of the second user and the third user, the number of times the second user and the third user are teamed for playing, and the like.
It should be noted that, after the server generates the friend relationship data, the server may store the friend relationship data of the application program in the server, so as to provide the friend relationship data of the application program for the login user of the application program.
Step 302C: and the server of any application program sends the friend relationship data in any application program to the blockchain system.
After the server generates the friend relationship data, the server can send the friend relationship data to the block chain system, so that the block chain system stores the friend relationship data.
Step 302D: and the second node equipment in the block chain system receives the friend relation data in any application program.
After the server sends the friend relationship data to the blockchain system, the second node device in the blockchain system can receive the friend relationship data. The second node device may refer to any node device configured with a target blockchain for storing buddy relationship data in a plurality of applications. The second node device may be the same as or different from the first node device, and this is not limited in this embodiment of the application.
303. And the second node equipment verifies the friend relationship data in any application program, and stores the friend relationship data in any application program on the target block chain when the verification of the friend relationship data in any application program passes.
After receiving the friend relationship data in any application program, the second node device can verify the friend relationship data in any application program, and when the verification is passed, the second node device stores the friend relationship data in any application program on the target block chain; when the verification fails, error information can be fed back to the server of any application program.
In a possible implementation manner, the verifying, by the second node device, the buddy relationship data in any application program may include steps 303A and 303B:
step 303A: the second node device carries out authority verification on any application program based on the application identification of any application program in the friend relationship data, and when the authority verification of any application program fails, the second node device indicates that the friend relationship data in any application program fails to verify; when the authority verification of any one application passes, step 303B is performed.
In a possible implementation manner, the second node device may perform, based on the application identifier of any application program, the process of performing permission verification on any application program by: and the second node equipment calls an authentication service to carry out authority verification on the application identification of any application program. The authentication service may be a CA (digital Certificate Authority) service or other services. Taking the authentication service as the CA service as an example, since the CA service issues digital certificates for all application programs that have successfully signed a contract, when the second node device receives a friend relationship processing request of any application program, the second node device may invoke the CA service to authenticate the digital certificate of any application program, and when the authentication of the digital certificate passes, it indicates that the authority verification of any application program passes, and at this time, the second node device may perform step 303B.
Step 303B: the second node equipment carries out validity verification on the blockchain account identification of the second user and the blockchain account identification of the third user, and when the validity verification fails, the verification of the friend relationship data in any application program is proved to fail; when the validity verification passes, the verification of the friend relationship data in any application program is indicated to pass.
In one possible implementation manner, the process of verifying the validity of the blockchain account identifier of the second user and the validity of the blockchain account identifier of the third user by the second node device may be: the second node device matches the blockchain account identification of the second user and the blockchain account identification of the third user with blockchain account identifications stored in a blockchain system, and when the blockchain account identification of the second user and the blockchain account identification of the third user are successfully matched, the validity verification of the blockchain account identification of the second user and the validity verification of the blockchain account identification of the third user are passed; when the match between the blockchain account identifier of the second user and/or the blockchain account identifier of the third user fails, it indicates that the validity verification of the blockchain account identifier of the second user and the validity verification of the blockchain account identifier of the third user do not pass, and at this time, the second node device may refuse to store the friend relationship data in any application program.
When the verification of the friend relation data in any application program passes, the second node device stores the friend relation data in any application program on the target block chain. This storing process can be referred to as step 301C in detail, and is not described herein again.
When the second node device receives the buddy relationship data in any application program each time, the buddy relationship data in any application program can be stored on the target block chain through the above steps 302 to 303. The friend relation data stored in the target block chain is not allowed to be tampered, and only a new block storing new friend relation data is allowed to be added to the target block chain. The block characteristic value of the new block is related to the block characteristic value of the previous block, so that the purpose of connecting the blocks which are adjacent in the block chain in series is realized, and the tampering of any data in the first block chain can be detected by tracing the block characteristic value stored in the next block. It should be noted that through the above steps, the friend relationship data of the same user in different application programs can be linked through the blockchain account id, so that it is convenient to subsequently search the friend relationship data of the user in each application program in the target blockchain based on the blockchain account id of the user.
304. The third node device receives a friend relationship data acquisition request of the first application program.
The friend relation data acquisition request comprises an application identifier of a first application program, a block chain account identifier of a first user bound with a user identifier of the first user and an application identifier of a second application program. The first user refers to a user who initiates the friend relationship data acquisition request, the first application program refers to an application program which the first user logs in currently, and the second application program refers to an application program which is to acquire the friend relationship. The second application may refer to at least one application selected by the first user, or may refer to at least one application defaulted by the terminal of the first user. The default at least one application program of the terminal of the first user may refer to at least one application program having an association relationship with the first application program. It should be noted that, when there is at least one application selected by the first user, the at least one application selected by the first user may be used as the second application; when there is no at least one application selected by the first user, at least one application defaulted by the terminal of the first user may be used as the second application.
The friend relationship data acquisition request of the first application program can be sent to the blockchain system by the terminal of the first user. The terminal of the first user firstly obtains a friend relationship data obtaining request and then sends the friend relationship data obtaining request to the block chain system. In one possible implementation manner, the manner for the terminal of the first user to obtain the friend relationship data obtaining request includes, but is not limited to, the following three manners:
the first method is as follows: when the terminal of the first user detects that the first user is converted from the unregistered state to the logged-in state, namely when the first user successfully logs in the first application program, the terminal of the first user automatically acquires a friend relationship data acquisition request.
The second method comprises the following steps: a terminal of a first user displays a data acquisition entry in an interface of a first application program; and when the triggering operation of the data acquisition entry is detected, the terminal of the first user acquires a friend relationship data acquisition request.
The data acquisition entry may be in the form of a button or an icon. The condition that the terminal of the first user detects the trigger operation of the data acquisition entry may be different according to a type of the terminal of the first user, which is not limited in the embodiment of the present application. For example, when the terminal of the first user detects the trigger operation of the data acquisition entry, the terminal of the first user may detect a pressure touch operation of the data acquisition entry, or the terminal of the first user may detect a click operation of the data acquisition entry. The click operation may be a click operation performed by a mouse, or a click operation performed by a keyboard to input a shortcut key.
The third method comprises the following steps: reference time intervals for refreshing friend relationship data are preset, and a terminal of a first user automatically acquires a friend relationship data acquisition request every other reference time interval.
The reference time interval may be set empirically or may be freely adjusted according to the type of the application program, which is not limited in the embodiment of the present application. For example, the reference time interval may be set to 2 minutes, etc.
After the terminal of the first user acquires the friend relationship data acquisition request, the terminal of the first user can send the friend relationship acquisition request to the block chain system, and therefore the third node device in the block chain system can receive the friend relationship acquisition request. The third node device may refer to any node device configured with the target blockchain. The third node device may be the same as the first node device and/or the second node device, or may be different from the first node device and/or the second node device, which is not limited in this embodiment of the application.
After receiving the friend relationship data obtaining request of the first application, the third node device may perform system verification on the friend relationship data obtaining request, and then perform step 305 when the system verification is passed. The process of the third node device performing system verification on the friend relationship data acquisition request may be: the third node equipment sends the friend relationship data acquisition request to the verification node equipment in the block chain system; when receiving a friend relation data acquisition request, at least one verification node device verifies whether the friend relation data acquisition request meets a verification strategy or not, and returns a verification passing message to a third node device after the verification is passed; and the third node equipment receives the verification passing message returned by one or more verification node equipment, and when the received verification passing message meets the verification strategy, the verification passing message indicates that the validity of the friend relationship data acquisition request is passed. The verification policy may specify the number of verification node devices used for verification, a verification method, a verification passing condition, and the like. The verification mode can be used for verifying whether the friend relationship data acquisition request is generated according to a preset format, whether the essential information such as the block chain account identification of the first user is omitted, and the like; the verification passing condition may be a minimum number of verification node devices that pass verification, a minimum proportion of all node devices of the blockchain system occupied by the verification node devices that pass verification, or the like. The reliability of the friend relation data acquisition request can be improved by performing system verification on the friend relation data acquisition request. For example, assuming that the verification policy specifies that at least 5 verification node devices are required to perform verification and at least 3 verification node devices are required to pass the verification, the third node device sends a friend relationship data acquisition request to the 5 verification node devices, and when a verification passing message returned by the at least 3 verification node devices is received, it indicates that the validity of the friend relationship data acquisition request passes the verification.
In one possible implementation manner, when the system verification of the friend relationship data acquisition request is passed by the third node device, the third node device may perform permission verification on the first application program and the second application program based on the application identifier of the first application program and the application identifier of the second application program in the friend relationship data acquisition request; when the first application program and the second application program pass the authority verification, step 305 is executed again. The process of authority verification can be detailed in step 303A, and is not described herein again.
305. And the third node equipment performs validity verification on the blockchain account identification of the first user.
In one possible implementation manner, the process of verifying the validity of the blockchain account identifier of the first user by the third node device may be: the third node device matches the blockchain account identifier of the first user with the blockchain account identifier stored in the blockchain system, and when the blockchain account identifier of the first user is successfully matched, the validity verification of the blockchain account identifier of the first user is passed, at this time, step 306 is executed; when the match of the blockchain account identifier of the first user fails, it indicates that the validity verification of the blockchain account identifier of the first user fails, and at this time, error reporting information may be fed back to the terminal of the first user.
306. And when the validity of the blockchain account identifier of the first user passes the verification, the third node equipment acquires target friend relationship data from the target blockchain based on the blockchain account identifier of the first user.
And the target friend relationship data is friend relationship data in a second application program corresponding to the block chain account identifier of the first user. Based on the target friend relation data, the friend relation data of the first user in the second application program can be obtained, and therefore sharing of the friend relation data in different application programs is achieved.
In one possible implementation manner, the process of the third node device obtaining the target buddy relationship data from the target blockchain may include the following two steps:
step 1: and the third node equipment acquires candidate friend relation data corresponding to the blockchain account identifier of the first user from the target blockchain based on the blockchain account identifier of the first user.
In one possible implementation manner, the process of the third node device obtaining the candidate friend relationship data corresponding to the blockchain account identifier of the first user from the target blockchain may be: the third node equipment acquires all friend relation establishing data and all friend relation releasing data corresponding to the block chain account identification of the first user from the target block chain; and for any friend relation establishing data in all friend relation establishing data, when friend relation releasing data corresponding to the friend relation establishing data does not exist in all friend relation releasing data, taking the friend relation establishing data as candidate friend relation data corresponding to the block chain account identifier of the first user.
Specifically, the process of the third node device obtaining all friend relationship establishing data and all friend relationship releasing data corresponding to the blockchain account identifier of the first user from the target blockchain may be: and the third node equipment acquires all blocks corresponding to the block chain account identification of the first user from the target block chain, and acquires all friend relationship establishing data and all friend relationship releasing data corresponding to the block chain account identification of the first user from all the blocks.
When the friend relation release data corresponding to the friend relation establishment data exists in all the friend relation release data, it is indicated that the friend relation establishment data is invalid, that is, the friend relation corresponding to the friend relation establishment data is released. When the friend relation release data corresponding to the friend relation establishment data does not exist in all the friend relation release data, it is indicated that the friend relation establishment data is valid, that is, the friend relation corresponding to the friend relation establishment data still exists. The candidate friend relation data obtained through the process refers to the relevant data of the user with friend relation still existing with the first user.
Step 2: and the third node equipment acquires friend relation data in the second application program from the candidate friend relation data based on the application identifier of the second application program.
And obtaining friend relation data in the second application program corresponding to the application identifier of the second application program from the candidate friend relation data, and taking the friend relation data in the second application program as target friend relation data. The obtained target friend relation data is the related data of the user with the friend relation still existing in the second application program of the first user.
It should be noted that the application identifier of the second application program may not be included in the friend relationship data obtaining request. In this case, the third node device takes the friend relationship data other than the friend relationship data in the first application in the candidate friend relationship data as the target friend relationship data. The target friend relationship data at this time refers to the related data of the user with the friend relationship still existing in each application program except the first application program of the first user stored in the first blockchain.
After obtaining the target friend relationship data, the third node device may send the obtained target friend relationship data to the terminal of the first user, so that the terminal of the first user displays the target friend relationship data. In this way, the first user can learn the related data of the users still having friend relationships in the second application program from the first application program, and directly play games and communicate with the users without adding the user as a friend again, which is beneficial to improving the use experience of the first user on the first application program.
An interface for the terminal of the first user to display the target friend relationship data may be as shown in fig. 4, where three target friend relationship data are displayed in fig. 4, and each target friend relationship data includes a blockchain account identifier of a user having a friend relationship with the first user, a source for establishing the friend relationship, and a timestamp for establishing the friend relationship. The source for establishing the friend relationship may be any second application program except the first application program.
As shown in fig. 5, the user a initiates an instruction for establishing a friend relationship with the user B in the application program, the relationship chain check module in the server checks the instruction for establishing the friend relationship, and when the check is passed, response information of the user B is obtained; and when the response information indicates that the user B agrees to add the user A as the friend, the server calls the relation chain calculation module, the relation chain calculation module acquires the relation data of the user A and the user B, and the friend relation data is generated. Then the relation chain calculation module in the server can locally store the friend relation data and can send the friend relation data to the block chain system; after receiving the friend relationship data, any node device in the blockchain system can perform authority verification on the application program and validity verification on the blockchain account identification of the user through an authentication service module in the node device, and after the verification is passed, the friend relationship data can be stored in a target blockchain through a friend relationship service module in the node device.
When a node device in the blockchain system receives a friend relationship data acquisition request, authority verification is carried out on an application program and validity verification is carried out on a blockchain account identifier of a user through an authentication service module in the node device, and after the verification is passed, target friend relationship data is acquired through a friend relationship service module in the node device; the node equipment sends the target friend relation data to the terminal of the user A through a friend relation acquisition module of the terminal of the user A. In addition, the server may also send the locally stored friend relationship data to the terminal of the user a through the friend relationship obtaining module of the terminal of the user a. By the method, the friend relation data can be stably stored and maintained for a long time without being limited by operators and regional conditions of application programs, the method is beneficial to establishing a long-term stable friend relation in the virtual world for users, and the requirement of the users for long-term friend making of the virtual world is met.
In one possible implementation manner, the third node device may further receive a historical friend relationship data query request of the first application program, and obtain the target historical friend relationship data based on the historical friend relationship data query request. The historical friend relationship data query request comprises a blockchain account identification of the first user and a blockchain account identification of the fourth user. The fourth user is at least one user other than the first user. The process of the third node device for acquiring the target historical friend relationship data based on the historical friend relationship data query request may be: the third node equipment acquires all friend relation data corresponding to the block chain account identification of the first user from the target block chain based on the block chain account identification of the first user; and taking the friend relation data corresponding to the block chain account identification of the fourth user in all the friend relation data as target historical friend relation data. The obtained target historical friend relation data refers to all historical friend relation data of the first user and the fourth user in each application program stored in the target block chain, and includes all friend relation establishing data and all friend relation releasing data of the first user and the fourth user in each application program. After obtaining the target historical friend relationship data, the third node device may send the target historical friend relationship data to the terminal of the first user, and the terminal of the first user displays the target historical friend relationship data, so that the first user can know all historical friend relationship data generated by the first user and the fourth user in each application program.
In the embodiment of the application, friend relationship data in a plurality of application programs are stored in a target block chain in advance, and when a friend relationship data acquisition request of a first application program is received, a target friend relationship in a second application program is acquired from the target block chain based on a block chain account identifier of a user bound with the user identifier of the user. Through the process, the friend relationship data of the same user in different application programs can be linked based on the block chain account identification, so that the friend relationship data of different application programs can be shared, the data processing effect is good, and the use experience of the user on each application program can be improved.
Based on the same technical concept, fig. 6 is a schematic diagram of a data processing apparatus based on a block chain according to an embodiment of the present application, and referring to fig. 6, the apparatus includes:
a receiving module 601, configured to receive a friend relationship data obtaining request of a first application program, where the friend relationship data obtaining request includes an application identifier of the first application program, a blockchain account identifier of the first user bound to a user identifier of the first user, and an application identifier of a second application program;
a verification module 602, configured to perform validity verification on the blockchain account identifier of the first user;
an obtaining module 603, configured to obtain, when the validity of the blockchain account identifier of the first user passes the verification, target friend relationship data from the target blockchain based on the blockchain account identifier of the first user, where the target friend relationship data is friend relationship data in the second application program corresponding to the blockchain account identifier of the first user.
In a possible implementation manner, the obtaining module 603 is configured to obtain candidate friend relationship data corresponding to a blockchain account identifier of a first user from a target blockchain based on the blockchain account identifier of the first user; and acquiring friend relation data in the second application program from the candidate friend relation data based on the application identifier of the second application program.
In a possible implementation manner, the friend relationship data includes friend relationship establishing data and friend relationship releasing data, and the obtaining module 603 is configured to obtain all friend relationship establishing data and all friend relationship releasing data corresponding to the block chain account identifier of the first user from the target block chain; and for any friend relation establishing data in all friend relation establishing data, when friend relation releasing data corresponding to the friend relation establishing data does not exist in all friend relation releasing data, taking the friend relation establishing data as candidate friend relation data corresponding to the block chain account identifier of the first user.
In a possible implementation manner, the verification module 602 is further configured to perform permission verification on the first application program and the second application program based on the application identifier of the first application program and the application identifier of the second application program; and when the authority verification of the first application program and the second application program passes, performing validity verification on the blockchain account identification of the first user.
In a possible implementation manner, the receiving module 601 is further configured to receive a registration request of any user, where the registration request of any user includes an identity of any user;
fig. 7 is a block chain-based data processing apparatus according to an embodiment of the present application, and referring to fig. 7, the apparatus further includes:
a generating module 604, configured to generate, based on the identity of any user, a blockchain account identity of any user corresponding to the identity of any user;
a feedback module 605, configured to feed back the blockchain account identifier of any user to any user;
a storage module 606 for storing the blockchain account identification of any user in the blockchain system.
In a possible implementation manner, the receiving module 601 is further configured to receive friend relationship data in any application program, where the friend relationship data includes an application identifier of any application program, a blockchain account identifier of a second user, and a blockchain account identifier of a third user;
the verification module 602 is further configured to verify friend relationship data in any application program;
the storage module 606 is further configured to store the buddy relationship data in any application program on the target block chain when the verification of the buddy relationship data in any application program passes.
In one possible implementation manner, the friend relationship data in any application program is generated by a server of any application program, and the server of any application program is used for storing the binding relationship between the user identifier and the blockchain account identifier of each user in any application program.
In the embodiment of the application, friend relationship data in a plurality of application programs are stored in a target block chain in advance, and when a friend relationship data acquisition request of a first application program is received, a target friend relationship in a second application program is acquired from the target block chain based on a block chain account identifier of a user bound with the user identifier of the user. Through the process, the friend relationship data of the same user in different application programs can be linked based on the block chain account identification, so that the friend relationship data of different application programs can be shared, the data processing effect is good, and the use experience of the user on each application program can be improved.
It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.
Fig. 8 is a schematic structural diagram of a server provided in an embodiment of the present application, where the server may refer to any node device in the foregoing embodiment, or may refer to a server in the foregoing embodiment. The server may generate large differences due to different configurations or performances, and may include one or more processors (CPUs) 801 and one or more memories 802, where the one or more memories 802 store at least one program code, and the at least one program code is loaded and executed by the one or more processors 801 to implement the data Processing method based on the blockchain provided by the above-described method embodiments. Of course, the server may also have components such as a wired or wireless network interface, a keyboard, and an input/output interface, so as to perform input/output, and the server may also include other components for implementing the functions of the device, which are not described herein again.
Fig. 9 is a schematic structural diagram of a terminal according to an embodiment of the present application. The terminal may refer to any node device in the foregoing embodiments, or may refer to any terminal in the foregoing embodiments. The terminal may be: a smart phone, a tablet computer, an MP3 player (Moving Picture Experts Group Audio Layer III, motion video Experts compression standard Audio Layer 3), an MP4 player (Moving Picture Experts Group Audio Layer IV, motion video Experts compression standard Audio Layer 4), a notebook computer, or a desktop computer. A terminal may also be referred to by other names such as user equipment, portable terminal, laptop terminal, desktop terminal, etc.
Generally, a terminal includes: a processor 901 and a memory 902.
Processor 901 may include one or more processing cores, such as a 4-core processor, an 8-core processor, and so forth. The processor 901 may be implemented in at least one hardware form of a DSP (Digital Signal Processing), an FPGA (Field-Programmable Gate Array), and a PLA (Programmable Logic Array). The processor 901 may also include a main processor and a coprocessor, where the main processor is a processor for processing data in an awake state, and is also called a Central Processing Unit (CPU); a coprocessor is a low power processor for processing data in a standby state. In some embodiments, the processor 901 may be integrated with a GPU (Graphics Processing Unit), which is responsible for rendering and drawing the content required to be displayed by the display screen. In some embodiments, the processor 901 may further include an AI (Artificial Intelligence) processor for processing computing operations related to machine learning.
Memory 902 may include one or more computer-readable storage media, which may be non-transitory. The memory 902 may also include high-speed random access memory, as well as non-volatile memory, such as one or more magnetic disk storage devices, flash memory storage devices. In some embodiments, a non-transitory computer readable storage medium in the memory 902 is used to store at least one instruction for execution by the processor 901 to implement the blockchain based data processing method provided by the method embodiments in the present application.
In some embodiments, the terminal may further include: a peripheral interface 903 and at least one peripheral. The processor 901, memory 902, and peripheral interface 903 may be connected by buses or signal lines. Various peripheral devices may be connected to the peripheral interface 903 via a bus, signal line, or circuit board. Specifically, the peripheral device includes: at least one of a radio frequency circuit 904, a touch display screen 905, a camera assembly 906, an audio circuit 907, a positioning assembly 908, and a power supply 909.
The peripheral interface 903 may be used to connect at least one peripheral related to I/O (Input/Output) to the processor 901 and the memory 902. In some embodiments, the processor 901, memory 902, and peripheral interface 903 are integrated on the same chip or circuit board; in some other embodiments, any one or two of the processor 901, the memory 902 and the peripheral interface 903 may be implemented on a separate chip or circuit board, which is not limited by this embodiment.
The Radio Frequency circuit 904 is used for receiving and transmitting RF (Radio Frequency) signals, also called electromagnetic signals. The radio frequency circuitry 904 communicates with communication networks and other communication devices via electromagnetic signals. The radio frequency circuit 904 converts an electrical signal into an electromagnetic signal to transmit, or converts a received electromagnetic signal into an electrical signal. Optionally, the radio frequency circuit 904 comprises: an antenna system, an RF transceiver, one or more amplifiers, a tuner, an oscillator, a digital signal processor, a codec chipset, a subscriber identity module card, and so forth. The radio frequency circuit 904 may communicate with other terminals via at least one wireless communication protocol. The wireless communication protocols include, but are not limited to: metropolitan area networks, various generation mobile communication networks (2G, 3G, 4G, and 5G), Wireless local area networks, and/or WiFi (Wireless Fidelity) networks. In some embodiments, the radio frequency circuit 904 may also include NFC (Near Field Communication) related circuits, which are not limited in this application.
The display screen 905 is used to display a UI (User Interface). The UI may include graphics, text, icons, video, and any combination thereof. When the display screen 905 is a touch display screen, the display screen 905 also has the ability to capture touch signals on or over the surface of the display screen 905. The touch signal may be input to the processor 901 as a control signal for processing. At this point, the display 905 may also be used to provide virtual buttons and/or a virtual keyboard, also referred to as soft buttons and/or a soft keyboard. In some embodiments, the display 905 may be one, disposed on the front panel of the terminal; in other embodiments, the number of the display panels 905 may be at least two, and the two display panels are respectively disposed on different surfaces of the terminal or are in a folding design; in still other embodiments, the display 905 may be a flexible display, disposed on a curved surface or on a folded surface of the terminal. Even more, the display screen 905 may be arranged in a non-rectangular irregular figure, i.e. a shaped screen. The Display panel 905 can be made of LCD (liquid crystal Display), OLED (Organic Light-Emitting Diode), and the like.
The camera assembly 906 is used to capture images or video. Optionally, camera assembly 906 includes a front camera and a rear camera. Generally, a front camera is disposed at a front panel of the terminal, and a rear camera is disposed at a rear surface of the terminal. In some embodiments, the number of the rear cameras is at least two, and each rear camera is any one of a main camera, a depth-of-field camera, a wide-angle camera and a telephoto camera, so that the main camera and the depth-of-field camera are fused to realize a background blurring function, and the main camera and the wide-angle camera are fused to realize panoramic shooting and VR (Virtual Reality) shooting functions or other fusion shooting functions. In some embodiments, camera assembly 906 may also include a flash. The flash lamp can be a monochrome temperature flash lamp or a bicolor temperature flash lamp. The double-color-temperature flash lamp is a combination of a warm-light flash lamp and a cold-light flash lamp, and can be used for light compensation at different color temperatures.
Audio circuit 907 may include a microphone and a speaker. The microphone is used for collecting sound waves of a user and the environment, converting the sound waves into electric signals, and inputting the electric signals to the processor 901 for processing, or inputting the electric signals to the radio frequency circuit 904 for realizing voice communication. For the purpose of stereo sound collection or noise reduction, a plurality of microphones can be arranged at different parts of the terminal respectively. The microphone may also be an array microphone or an omni-directional pick-up microphone. The speaker is used to convert electrical signals from the processor 901 or the radio frequency circuit 904 into sound waves. The loudspeaker can be a traditional film loudspeaker or a piezoelectric ceramic loudspeaker. When the speaker is a piezoelectric ceramic speaker, the speaker can be used for purposes such as converting an electric signal into a sound wave audible to a human being, or converting an electric signal into a sound wave inaudible to a human being to measure a distance. In some embodiments, audio circuit 907 may also include a headphone jack.
The positioning component 908 is used to locate the current geographic Location of the terminal to implement navigation or LBS (Location Based Service). The positioning component 908 may be a positioning component based on the GPS (Global positioning system) of the united states, the beidou system of china, the graves system of russia, or the galileo system of the european union.
The power supply 909 is used to supply power to each component in the terminal. The power source 909 may be alternating current, direct current, disposable or rechargeable. When power source 909 comprises a rechargeable battery, the rechargeable battery may support wired or wireless charging. The rechargeable battery may also be used to support fast charge technology.
In some embodiments, the terminal also includes one or more sensors 910. The one or more sensors 910 include, but are not limited to: acceleration sensor 911, gyro sensor 912, pressure sensor 913, fingerprint sensor 914, optical sensor 915, and proximity sensor 916.
The acceleration sensor 911 may detect the magnitude of acceleration on three coordinate axes of a coordinate system established with the terminal. For example, the acceleration sensor 911 may be used to detect the components of the gravitational acceleration in three coordinate axes. The processor 901 can control the touch display 905 to display the user interface in a landscape view or a portrait view according to the gravitational acceleration signal collected by the acceleration sensor 911. The acceleration sensor 911 may also be used for acquisition of motion data of a game or a user.
The gyroscope sensor 912 can detect the body direction and the rotation angle of the terminal, and the gyroscope sensor 912 and the acceleration sensor 911 cooperate to acquire the 3D motion of the user on the terminal. The processor 901 can implement the following functions according to the data collected by the gyro sensor 912: motion sensing (such as changing the UI according to a user's tilting operation), image stabilization at the time of photographing, game control, and inertial navigation.
The pressure sensor 913 may be disposed at a side frame of the terminal and/or at a lower layer of the touch display 905. When the pressure sensor 913 is disposed on the side frame of the terminal, the user's holding signal to the terminal may be detected, and the processor 901 performs left-right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor 913. When the pressure sensor 913 is disposed at a lower layer of the touch display 905, the processor 901 controls the operability control on the UI interface according to the pressure operation of the user on the touch display 905. The operability control comprises at least one of a button control, a scroll bar control, an icon control and a menu control.
The fingerprint sensor 914 is used for collecting a fingerprint of the user, and the processor 901 identifies the user according to the fingerprint collected by the fingerprint sensor 914, or the fingerprint sensor 914 identifies the user according to the collected fingerprint. Upon recognizing that the user's identity is a trusted identity, processor 901 authorizes the user to perform relevant sensitive operations including unlocking the screen, viewing encrypted information, downloading software, paying, and changing settings, etc. The fingerprint sensor 914 may be disposed on the front, back, or side of the terminal. When a physical key or vendor Logo is provided on the terminal, the fingerprint sensor 914 may be integrated with the physical key or vendor Logo.
The optical sensor 915 is used to collect ambient light intensity. In one embodiment, the processor 901 may control the display brightness of the touch display 905 based on the ambient light intensity collected by the optical sensor 915. Specifically, when the ambient light intensity is high, the display brightness of the touch display screen 905 is increased; when the ambient light intensity is low, the display brightness of the touch display screen 905 is turned down. In another embodiment, the processor 901 can also dynamically adjust the shooting parameters of the camera assembly 906 according to the ambient light intensity collected by the optical sensor 915.
A proximity sensor 916, also known as a distance sensor, is typically provided on the front panel of the terminal. The proximity sensor 916 is used to collect the distance between the user and the front face of the terminal. In one embodiment, when the proximity sensor 916 detects that the distance between the user and the front face of the terminal gradually decreases, the processor 901 controls the touch display 905 to switch from the bright screen state to the dark screen state; when the proximity sensor 916 detects that the distance between the user and the front surface of the terminal gradually becomes larger, the processor 901 controls the touch display 905 to switch from the breath screen state to the bright screen state.
Those skilled in the art will appreciate that the configuration shown in fig. 9 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components may be used.
In an exemplary embodiment, a computer readable storage medium is further provided, in which at least one program code is stored, and the at least one program code is loaded and executed by a processor of a computer device to implement any one of the above block chain based data processing methods.
Alternatively, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), a magnetic tape, a floppy disk, an optical data storage device, and the like.
It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship.
The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims (10)

1. A data processing method based on a blockchain is applied to any node device in a blockchain system, a target blockchain is configured for a plurality of node devices in the blockchain system, and the target blockchain is used for storing friend relationship data in a plurality of application programs, and the method comprises the following steps:
receiving a friend relation data acquisition request of a first application program, wherein the friend relation data acquisition request comprises an application identifier of the first application program, a block chain account identifier of a first user bound with a user identifier of the first user and an application identifier of a second application program;
verifying the validity of the blockchain account identifier of the first user;
when the validity of the blockchain account identifier of the first user passes the verification, target friend relationship data is obtained from the target blockchain based on the blockchain account identifier of the first user, and the target friend relationship data is friend relationship data in the second application program corresponding to the blockchain account identifier of the first user.
2. The method of claim 1, wherein obtaining target buddy relationship data from the target blockchain based on the blockchain account identification of the first user comprises:
acquiring candidate friend relation data corresponding to the blockchain account identifier of the first user from the target blockchain based on the blockchain account identifier of the first user;
and acquiring friend relation data in the second application program from the candidate friend relation data based on the application identifier of the second application program.
3. The method of claim 2, wherein the buddy relationship data comprises buddy relationship setup data and buddy relationship release data, and wherein obtaining candidate buddy relationship data corresponding to the blockchain account identifier of the first user from the target blockchain comprises:
acquiring all friend relation establishing data and all friend relation releasing data corresponding to the block chain account identification of the first user from the target block chain;
and for any friend relation establishing data in all friend relation establishing data, when friend relation releasing data corresponding to the friend relation establishing data does not exist in all friend relation releasing data, taking the friend relation establishing data as candidate friend relation data corresponding to the block chain account identifier of the first user.
4. The method of claim 1, wherein after receiving the request for obtaining the buddy relationship data of the first application, the method further comprises:
performing permission verification on the first application program and the second application program based on the application identification of the first application program and the application identification of the second application program;
and when the authority verification of the first application program and the second application program passes, performing validity verification on the blockchain account identification of the first user.
5. The method of claim 1, wherein prior to validating the first user's blockchain account identification, the method further comprises:
receiving a registration request of any user, wherein the registration request of any user comprises an identity of any user;
generating a blockchain account identification of any user corresponding to the identity identification of any user based on the identity identification of any user, and feeding back the blockchain account identification of any user to any user;
store the blockchain account identification of the any user in the blockchain system.
6. The method of claim 1, wherein prior to receiving the request for the acquisition of the buddy relationship data of the first application, the method further comprises:
receiving friend relation data in any application program, wherein the friend relation data comprise an application identifier of the application program, a block chain account identifier of a second user and a block chain account identifier of a third user;
and verifying the friend relationship data in any application program, and storing the friend relationship data in any application program on the target block chain when the friend relationship data in any application program passes verification.
7. The method according to claim 6, wherein the friend relationship data in any application program is generated by a server of any application program, and the server of any application program is used for storing the binding relationship between the user identifier and the blockchain account identifier of each user in any application program.
8. An apparatus for data processing based on a blockchain, the apparatus comprising:
the system comprises a receiving module, a sending module and a processing module, wherein the receiving module is used for receiving a friend relationship data acquisition request of a first application program, and the friend relationship data acquisition request comprises an application identifier of the first application program, a block chain account identifier of a first user bound with a user identifier of the first user and an application identifier of a second application program;
the verification module is used for verifying the validity of the block chain account identifier of the first user;
and the obtaining module is used for obtaining target friend relationship data from the target block chain based on the block chain account identifier of the first user when the validity verification of the block chain account identifier of the first user passes, wherein the target friend relationship data is friend relationship data in the second application program corresponding to the block chain account identifier of the first user.
9. A computer device comprising a processor and a memory, the memory having stored therein at least one program code, the at least one program code being loaded and executed by the processor to implement the method of blockchain based data processing according to any one of claims 1 to 7.
10. A computer-readable storage medium having stored therein at least one program code, the at least one program code being loaded and executed by a processor, to implement the method of blockchain-based data processing according to any one of claims 1 to 7.
CN201910922075.8A 2019-09-27 2019-09-27 Block chain-based data processing method, device, equipment and storage medium Active CN110598386B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910922075.8A CN110598386B (en) 2019-09-27 2019-09-27 Block chain-based data processing method, device, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910922075.8A CN110598386B (en) 2019-09-27 2019-09-27 Block chain-based data processing method, device, equipment and storage medium

Publications (2)

Publication Number Publication Date
CN110598386A true CN110598386A (en) 2019-12-20
CN110598386B CN110598386B (en) 2023-05-30

Family

ID=68864159

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910922075.8A Active CN110598386B (en) 2019-09-27 2019-09-27 Block chain-based data processing method, device, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN110598386B (en)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111737764A (en) * 2020-07-31 2020-10-02 支付宝(杭州)信息技术有限公司 Method and device for generating description information
CN112131489A (en) * 2020-09-28 2020-12-25 青岛海尔科技有限公司 Friend relationship management method, system, storage medium and electronic device
CN112153624A (en) * 2020-10-14 2020-12-29 中国联合网络通信集团有限公司 Roaming method and device
CN112491914A (en) * 2020-12-04 2021-03-12 山西特信环宇信息技术有限公司 Block chain bidirectional authentication method, communication method and system

Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105681161A (en) * 2015-08-20 2016-06-15 腾讯科技（深圳）有限公司 Method, device and system for adding friend account
CN106100981A (en) * 2016-08-22 2016-11-09 布比（北京）网络技术有限公司 Social network data exchange method and device
US20170132630A1 (en) * 2015-11-11 2017-05-11 Bank Of America Corporation Block chain alias for person-to-person payments
CN107451485A (en) * 2017-06-02 2017-12-08 阿里巴巴集团控股有限公司 A kind of data processing method and equipment based on block chain
CN108712395A (en) * 2018-04-27 2018-10-26 腾讯科技（深圳）有限公司 Account management method, device, server based on block chain and storage medium
CA3061638A1 (en) * 2017-04-28 2018-11-01 Anonos Inc. Systems and methods for enforcing centralized privacy controls in de-centralized systems
CN108833255A (en) * 2018-04-27 2018-11-16 深圳市元征科技股份有限公司 Communication means, system and block chain node device based on block chain
CN108985930A (en) * 2018-06-13 2018-12-11 湖南搜云网络科技股份有限公司 Information processing method and device, block chain node and storage medium
CN109120669A (en) * 2018-07-03 2019-01-01 泰链（厦门）科技有限公司 Method, medium and system based on the internet P2P building block chain
CN109471903A (en) * 2018-10-25 2019-03-15 深圳壹账通智能科技有限公司 Sharing method, device and the computer equipment of block chain information
CN109584096A (en) * 2019-01-30 2019-04-05 翟红鹰 Master and apprentice's social contact method, terminal device and storage medium based on block chain
CN109617952A (en) * 2018-11-28 2019-04-12 立旃（上海）科技有限公司 Customer relationship method for building up and device based on block chain
CN110008743A (en) * 2019-03-26 2019-07-12 阿里巴巴集团控股有限公司 Data attribute identification method, device and equipment in a kind of piece of chain type account book
CN110035052A (en) * 2018-12-28 2019-07-19 阿里巴巴集团控股有限公司 A kind of method, apparatus that checking historical transactional information and electronic equipment
CN110163604A (en) * 2019-04-29 2019-08-23 华中科技大学 A kind of block chain assets transfer method based on multi-party verification
US20190386975A1 (en) * 2017-06-19 2019-12-19 Alibaba Group Holding Limited Authentication method and device, and blockchain-based authentication data processing method and device

Patent Citations (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105681161A (en) * 2015-08-20 2016-06-15 腾讯科技（深圳）有限公司 Method, device and system for adding friend account
US20170132630A1 (en) * 2015-11-11 2017-05-11 Bank Of America Corporation Block chain alias for person-to-person payments
CN106100981A (en) * 2016-08-22 2016-11-09 布比（北京）网络技术有限公司 Social network data exchange method and device
CA3061638A1 (en) * 2017-04-28 2018-11-01 Anonos Inc. Systems and methods for enforcing centralized privacy controls in de-centralized systems
CN107451485A (en) * 2017-06-02 2017-12-08 阿里巴巴集团控股有限公司 A kind of data processing method and equipment based on block chain
US20190386975A1 (en) * 2017-06-19 2019-12-19 Alibaba Group Holding Limited Authentication method and device, and blockchain-based authentication data processing method and device
CN108712395A (en) * 2018-04-27 2018-10-26 腾讯科技（深圳）有限公司 Account management method, device, server based on block chain and storage medium
CN108833255A (en) * 2018-04-27 2018-11-16 深圳市元征科技股份有限公司 Communication means, system and block chain node device based on block chain
CN108985930A (en) * 2018-06-13 2018-12-11 湖南搜云网络科技股份有限公司 Information processing method and device, block chain node and storage medium
CN109120669A (en) * 2018-07-03 2019-01-01 泰链（厦门）科技有限公司 Method, medium and system based on the internet P2P building block chain
CN109471903A (en) * 2018-10-25 2019-03-15 深圳壹账通智能科技有限公司 Sharing method, device and the computer equipment of block chain information
CN109617952A (en) * 2018-11-28 2019-04-12 立旃（上海）科技有限公司 Customer relationship method for building up and device based on block chain
CN110035052A (en) * 2018-12-28 2019-07-19 阿里巴巴集团控股有限公司 A kind of method, apparatus that checking historical transactional information and electronic equipment
CN109584096A (en) * 2019-01-30 2019-04-05 翟红鹰 Master and apprentice's social contact method, terminal device and storage medium based on block chain
CN110008743A (en) * 2019-03-26 2019-07-12 阿里巴巴集团控股有限公司 Data attribute identification method, device and equipment in a kind of piece of chain type account book
CN110163604A (en) * 2019-04-29 2019-08-23 华中科技大学 A kind of block chain assets transfer method based on multi-party verification

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
宋俊典;戴炳荣;蒋丽雯;赵尧;李超;王晓强;: "基于区块链的数据治理协同方法", 计算机应用 *
张宁;赵爽;: "融合精算定价的互助保险区块链实现", 保险职业学院学报 *

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111737764A (en) * 2020-07-31 2020-10-02 支付宝(杭州)信息技术有限公司 Method and device for generating description information
CN112906064A (en) * 2020-07-31 2021-06-04 支付宝(杭州)信息技术有限公司 Method and device for generating description information
CN112906064B (en) * 2020-07-31 2022-05-17 支付宝(杭州)信息技术有限公司 Method and device for generating description information
US11387990B2 (en) 2020-07-31 2022-07-12 Alipay (Hangzhou) Information Technology Co., Ltd. Method and apparatus for generating description information
CN112131489A (en) * 2020-09-28 2020-12-25 青岛海尔科技有限公司 Friend relationship management method, system, storage medium and electronic device
CN112153624A (en) * 2020-10-14 2020-12-29 中国联合网络通信集团有限公司 Roaming method and device
CN112491914A (en) * 2020-12-04 2021-03-12 山西特信环宇信息技术有限公司 Block chain bidirectional authentication method, communication method and system
CN112491914B (en) * 2020-12-04 2022-06-24 山西特信环宇信息技术有限公司 Block chain bidirectional authentication method, communication method and system

Also Published As

Publication number Publication date
CN110598386B (en) 2023-05-30

Similar Documents

Publication Publication Date Title
CN110687821B (en) Intelligent home control system and method based on block chain
CN108614878B (en) Protocol data management method, device, storage medium and system
CN110598386B (en) Block chain-based data processing method, device, equipment and storage medium
CN110597924B (en) Block chain-based user identification processing method, device, equipment and storage medium
CN111340482B (en) Conflict detection method, device, node equipment and storage medium
CN110689460A (en) Traffic accident data processing method, device, equipment and medium based on block chain
CN110826103B (en) Method, device, equipment and storage medium for processing document authority based on blockchain
CN108769992B (en) User authentication method, device, terminal and storage medium
CN110602206A (en) Data sharing method and device based on block chain and storage medium
CN111355732B (en) Link detection method and device, electronic equipment and storage medium
CN111339086A (en) Block processing method, and data query method and device based on block chain
CN110581891A (en) Game data processing method, device, equipment and storage medium based on block chain
CN111339181B (en) Block storage method, block storage device, node equipment and storage medium
CN111414598B (en) Monitoring method, device and equipment based on block chain and storage medium
CN110543502A (en) Credit data processing method, device and equipment based on block chain and storage medium
CN111212074B (en) Blockchain-based qualification identification method, device, equipment and storage medium
CN112583806A (en) Resource sharing method, device, terminal, server and storage medium
CN110532324B (en) Block chain-based bulletin information display method, device, equipment and storage medium
CN110889264B (en) Multimedia information processing method, device, equipment and storage medium
CN110727894B (en) Target material setting method, device, equipment and storage medium
CN111970298A (en) Application access method and device, storage medium and computer equipment
CN111866140A (en) Fusion management apparatus, management system, service calling method, and medium
CN110597840A (en) Partner relationship establishing method, device, equipment and storage medium based on block chain
CN114900559A (en) Management system, terminal, management method, and storage medium
CN111131619B (en) Account switching processing method, device and system

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